• Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About diqipib

  • Rank
    Junior Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hmm ... My ESXI doesn't show ip either, but the virtual machine is working nonetheless. I found ip by looking into the web interface of the router.
  2. @luchuma GREAT THANKS MAN ! I really wonder myself how I could be so careless! I recreated a virtual machine 5 times and every time I got the same result ! Shaaaame on me !
  3. @luchuma Thank's for the answer. I checked my "pat" file md5. Redownloaded it again from server. As I see, it's md5 are equal. md5: 57748c2d9bed639403fca13de64eba03 *DSM_DS3615xs_23739.pat And as I see on server there is md5 for this file - https://archive.synology.com/download/DSM/release/6.2/23739/DSM_DS3615xs_23739.pat.md5 So my file "pat" file looks correct. Please, can You inform me what vm config should I show ? I have several files: I attached XPEnology.vmx. If other files are required, please inform me. XPEnology.vmx
  4. Good afternoon. Please tell me why during installation I constantly get an error of 13 ? I try to install DSM 6.2.2 (tried with DSM_DS3615xs_23739.pat / DSM_DS3615xs_24922.pat) on ESXI 6.0. I searched in a subject and in the Internet. Everywhere they write that this is due to the incorrectly set VID and PID. But the topic header does not indicate a change in VID and PID, and in theory should they be set in the VMDK file? I upload it to ESXI without changes. But after starting the virtual machine, its contents are constantly changing! Namely, the CID and db.longContentID are changing. What am I doing wrong ? P.S That's what I see in changed vmdk:
  5. @flyride , yes, of course you are right ! In the end, I can even get the certificate artificially and install it with the same DSM functionality, but the fact is that the old version of DSM 5.1.7 is slowly starting to get glitches, because Synology stops supporting it and the built-in functionality stops working. So, something else may "fall off" tomorrow and no one will fix it. It makes me sad. In addition, an alternative way to obtain a certificate is more time consuming. And DSM for me is in simplicity and convenience. If I have to use an alternative, then it already makes sense to abandon DSM in favor of other solutions. Maybe I'm wrong, but I see it like this.
  6. By the way, I forgot to clarify. I felt the need to switch to 6.2.2, because in 6.1.7, even with update 3, the DSM functionality for receiving letsencrypt certificate stopped working for me. In a loop, it reports an error and offers to log into DSM.
  7. @IG-88 Thank you so much for such a detailed answer! Now the reason is clear. So I have to either buy a SATA controller, or use alternatives like FreeNAS. It's a pity. Loved the beautiful design of XPenology. ) Although, I will try to write Jun. Maybe he could offer an option.
  8. @bearcat, I used dmesg with su rights. "dmesg | grep SATA" returns this: Maybe it can help ? Any ideas ? ) Below is the full result of dmesg: I replaced real sn and macs with XXXXXXXXX / YYYYYYYYYY
  9. @bearcat U r right. My fault. Do I understand correctly that then I have no chance to start 6.2.2 ? After all, Synology built in signing file protection and since extra.lzma from 6.2.2 doesn’t include my driver, I can't add it from another extra.lzma from previous versions, cause it has another sign that doesn't match new bootloader ? Am I wrong ? Please, can You tell me how to find controller ID ? Now I installed DSM 6.1.7-15284 again. What shall I do next ? It sounds like I still have chances. )) It's good. So life can still surprise us.
  10. bearcat, thanks for Your answer ! 1) So the problem is in SATA controller ? 2) Hm. I checked BIOS settings. That's what I see: 3) Previously I successfully used loader 1.02b DS3615xs with DSM 6.1.7. I thought, if motherboard doesn't support AHCI, it can't run DSM at all (I mean any version of it). Am I wrong ?
  11. Greetings, gentlemen. I decided that creating a new topic does not make sense if I have the same problem as the author. As I understand it, this is a fairly common situation: I read these messages, but have not yet found an answer how to solve the problem. So I'll try to give a description of my system, if more detailed information is required, I will be glad to provide it: Processor: Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz (2 cores) Mother board: Gigabyte GA-G31M-ES2L Memory: KVR667D2N5/2G (x2) I tried to install DSM 6.2.2 with loader DS3615xs 1.03b (fresh install) from this topic As usual, I flashed the image on a USB flash drive, booted from it and through the console replaced VID and PID in GRUB.cfg. Web interface started but I see the same picture - No Hard Disk Found on DS3615xs. After searching the internet I found this topic. I tried to replace extra.lzma with file from here and zImage and rd.gz from file DSM_DS3615xs_24922.pat, but still get the same result. Tell me, please, are there any chances to start DSM 6.2.2 on my system or is there no point in trying further ?
  12. den3001, вот как. Тогда вдвойне благодарю за информацию ! ) Пойду соберу DSM-ку как было и париться не буду. Как допилят, так и буду думать о переходе ). Большое спасибо !
  13. Понял. Крайне благодарен. Значит пока не судьба мне погонять новую DSM. ) Придётся затариваться новой материнкой.
  14. 1) Да. Вы правы. Именно так. Для 918+ я использовал 1.03a2, а для 3615 и 3617 - 1.03b 2) Флешки менял уже. И причём тут они ? Ведь раз я вижу веб интерфейс, значит загрузка с флешки уже прошла успешно. 3) Так это ж древние мамки у них UEFI и не пахнет. Так что я по любому в legacy. А что - новый загрузчик только UEFI поддерживает ?
  15. Господа, попробовал на двух материнках Asus P5G41T-M LX2/GB и Gigabyte GA-945GCMX-52. На новом загрузчике 1.03b всё время получаю сообщение в веб морде, что диски не найдены. На загрузчике и для 918+ модели устройство вообще в сети не появляется, а на 3615 и 3617 захожу в веб интерфейс и везде вижу сообщение с предложением переподключить диск. Подскажите пожалуйста, что я делаю не так ? Неужели в новом загрузчике нет дров под мой диск ? В старом же всё заводилось с пол пинка ? P.S На флешке VID и PID прописаны, в BIOS режим для дисков Enchanced SATA выбран. (Пробовал выставлять IDE - разницы никакой)