snailium

Transition Members
  • Content Count

    11
  • Joined

  • Last visited

Community Reputation

5 Neutral

About snailium

  • Rank
    Newbie

Recent Profile Visitors

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

  1. I just had the same mystery disk missing problem. Google search landed here. Here is my situation. I do have 8 x 2TB SAS drives + 2 x SATA drives. 9 of them form an SHR2 pool and 1 of them is used as hot spare. HBA is LSI 9207-8i (FW 20.00.07.00), running on ESXi with PCIe passthrough. Between HBA and HDD, I used an IBM SAS expander to make HBA accept more than 8 drives. After a power loss, 2 x SAS drives are missing. I thought it might be disk failure. Since I have one hot spare, so I added another 2TB SATA drive to fix the pool. After a few day
  2. 2021-08-17T08:28:35.374Z| vmx| | I005: USB: Found device [name:synoboot.vmdk vid:0e0f pid:0005 speed:super family:storage virtPath:usb_xhci:3 deviceType:virtual-storage info:0000001 version:3], connected to usb_xhci port 3. The vid and pid for virtual mass storage don't change in ESXi 7.0. From the previous serial.log, there is no OS can be selected to boot. I'm not sure where the problem is. But it worth a try to change VM compatibility (from 7.0 to 6.7).
  3. It seems grub (bootloader) didn't find any valid boot entry. So, DSM is not loaded. Can you please also share "vmware.log"?
  4. Can you share the "serial.out" file under your VM directory?
  5. I would recommend adding a serial port in the VM options, dump the output to a log file. After booting your VM, keep checking the serial log file for hints (you can access the log file from datastore). It may tell you which driver has issue. P.S. double check "secure boot" option, it needs to remain disabled.
  6. Which network adapter are you using? You should use e1000e, not vmxnet3, because DSM doesn't have driver for vmxnet3.
  7. It is not the boot option. I mean if you use BIOS mode, there is no support on booting from USB drive. At least, I didn't have it work that way. Maybe you can find some other solution to make the VM boot from USB using BIOS mode.
  8. It sounds the network driver problem. Did you choose "e1000e" for the virtual network adapter? Or maybe try IG-88's extension for additional network driver?
  9. The ".bin" file was a typo, but it seems I cannot edit the post. Here the ".bin" means synoboot.img you just patched in Step 1a. I don't think ESXi VM can boot from virtual USB storage in BIOS mode. It has to be in EFI mode. Also, there is no CSM in ESXi's EFI mode. I haven't tried v1.03b loader, but I don't think it will work.
  10. If you have configured virtual disk, you'd better using a virtual SATA controller. I'm actually using PCIe passthrough to attach my LSI 9211-8i to the VM, so the VM natively see 10 disks.
  11. I know there are tutorials for installing DSM on ESXi as "virtualization" by creating virtual SATA drive. I ran into DSM upgrade problem (Error 13) using that method. Finally, I've dicovered a way to let ESXi create an emulated USB storage for the loader (the BAREMETAL way)! 1. Get the loader. Either take Jun's loader 1.04b and do some customization, or take the modified loader here. 1a. Modify VID/PID grub.cfg If you are using the modified loader, the VID/PID has already been fixed. Skip to the next step. If you are using original 1.04b loader, follow th