Hi,
I am struggling to install OMV 3.x from openmediavault_3.0.86-amd64.iso onto a USB drive, which will become the boot device for my DIY NAS. But when the install process gets to the point of selecting a drive onto which OMV will be installed, at the Partition Disks step of the installation, the USB drive does not appear in the list. What should I do?
Here's some background information:
Hardware
- Motherboard: Supermicro X11SSH-F-O
- Future boot USB drive: 16GB MX-ES brand SLC USB3.0 drive, currently formatted as FAT 32. VERY IMPORTANT: This drive will occupy USB Port 10 on the motherboard, which is a completely internal USB port designed for housing a boot USB.
- RAM: 16 GB (2 x Crucial 8 GB DDR 4 2400 ECC #CT2K8G4WFS824A)
- Other mass storage: 3 x 4TB WD Red SATA drives (12 TB total)
Experience So Far
- Initially I created an installation boot USB by copying the install iso to a USB 2.0 drive. I did this on one of my Macs using the dd command in CLI.
- I then tried to install OMV from this drive. First I inserted the drive into one of the system's external USB 2.0 ports. Then I modified the BIOS to make USB the first choice for booting. Then I booted up the system. But after initial boot up, it just showed a blank screen and never moved from it.
- Then I created another installation boot USB on another device. Only this time, instead of using the CLI dd command, I used the unetbootin app. Previously I had tried unsuccessfully to use this app on an iMac running OS X Yosemite; the program never initialized its main window properly. This is why I used the dd command instead. But this time I installed unetbootin on a MacBook running MacOS Sierra, and the program worked.
- Nonetheless, when I used this installation USB drive instead of the original one, I got the same results as before: nothing but a blank screen.
- Up until this point I had been assuming the MB would look at available USB drives and choose the one that was bootable. Now I began to think that maybe the system was just confused by two USB drives being present. So I removed the future boot USB drive from USB Port 10 and rebooted. This time the installation actually began successfully.
- Because of this, I believe the earlier problem was not due to using dd instead of unetbootin; instead, the problem was due to having a second USB drive present at boot up.
- But now, when I get to the Partition Disks step, the system only lists the SATA drives. Of course: initially they are the only target locations available. So I go a few steps back in the installation procedure, insert the future boot USB in Port 10, and continue the process. The drive still does not appear among the Partition Disk choices. This is where I am stuck.
What should I do next?