Short version: After creating a ext4 filesystem on an 8TB drive, I reboot, am notified there are errors, and then the drive does not mount automatically.
I've been working on setting up the HC2, done this set up a couple times and kept notes to verify I could reproduce it and I didn't miss something. Here's my whole process from the start, just in case it's relevant.
- Download and Install on SD Card with Etcher
- OMV_4_Odroid_XU4_HC1_HC2.img.xz
- Attach drive and SD card, start it up.
- Wait 30+ minutes
- Login to web gui
- General Settings > Change web admin password
- Set Date and Time
- Specify ethernet on network - probably not necessary, but helpful for monitoring
- Monitoring - turn on
- Update Management - ran update. Saw errors in dialog while upgrading. "Bad Gateway"
- To check on this I SSH'd in as root. Ran apt-get -f install - saw 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. and decided to move on.
- Reboot
- Check for updates again. Nothing to be updated.
- OMV-Extras - enabled Docker CE
- Installed Docker-gui via commandline (because the past few times I did it the "right" way caused this error "Failed to execute XPath query '/config/services/docker'" and I (right or wrong) learned from this thread just to install via the commandline with apt-get install openmediavault-docker-gui
- Reboot. (Maybe superstitiously)
- Disks > Edit
- Set spindown, noise vs. performance level, etc
- File Systems > Create
- set up as ext4 with the name "eighttb"
- Mount the filesystem via the gui - everything looks good. The Device is /dev/sda1 the label is eighttb
- Restart - the gui has a popup with "an error occurred" and only an "ok" button - doesn't let me see the error.
- Upon reboot, the filesystem is not mounted.
Looking in OMV under FileSystems, two filesystems appear related to the drive:
/dev/disk/by-label/eighttb
and
/dev/sda1
See here:
IIRC, the "/by-label/" thing is like a shortcut in the fstab? But for some reason I had the following problem in previous attempts to get this done. When I set up share folders, upon reboot the ../by-label/... mount was referenced but missing, while the sda1 listing was not referenced and unmounted.
I tried a few things on previous attempts to fix like
omv-mkconf fstab
omv-mkconf systemd
mount -a
And adding mount -a to a scheduled job (see more on that below) but wasn't able to solve it. Perhaps I missed something.
I dug through the syslog briefly and pulled a couple excerpts that may be helpful (total guesswork here, so apologies if it's useless):
Mar 17 11:04:14 odroidxu4 systemd[1]: apt-daily.timer: Adding 29min 31.747306s random time.
Mar 17 11:04:15 odroidxu4 kernel: [ 229.851883] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Mar 17 11:04:15 odroidxu4 kernel: [ 229.851908] sd 0:0:0:0: [sda] tag#0 Sense Key : 0x2 [current]
Mar 17 11:04:15 odroidxu4 kernel: [ 229.851928] sd 0:0:0:0: [sda] tag#0 ASC=0x4 ASCQ=0x1
Mar 17 11:04:15 odroidxu4 kernel: [ 229.851939] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x88 88 00 00 00 00 03 a3 81 2a 00 00 00 00 08 00 00
Mar 17 11:04:15 odroidxu4 kernel: [ 229.851948] print_req_error: I/O error, dev sda, sector 15628052992
Mar 17 11:04:15 odroidxu4 systemd-udevd[375]: worker [474] terminated by signal 9 (Killed)
Mar 17 11:04:15 odroidxu4 systemd-udevd[375]: worker [474] failed while handling '/devices/platform/soc/soc:usb3-0/12000000.dwc3/xhci-hcd.3.auto/usb4/4-1/4-1:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda1'
Mar 17 11:04:16 odroidxu4 systemd[1]: Started Beep after system start.
Mar 17 11:04:42 odroidxu4 monit[1826]: 'mountpoint_srv_dev-disk-by-label-eighttb' status failed (1) -- /srv/dev-disk-by-label-eighttb is not a mountpoint
Mar 17 11:05:00 odroidxu4 CRON[2251]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 17 11:05:13 odroidxu4 monit[1826]: 'mountpoint_srv_dev-disk-by-label-eighttb' status failed (1) -- /srv/dev-disk-by-label-eighttb is not a mountpoint
Mar 17 11:05:41 odroidxu4 systemd[1]: dev-disk-by\x2dlabel-eighttb.device: Job dev-disk-by\x2dlabel-eighttb.device/start timed out.
Mar 17 11:05:41 odroidxu4 systemd[1]: Timed out waiting for device dev-disk-by\x2dlabel-eighttb.device.
Mar 17 11:05:41 odroidxu4 systemd[1]: Dependency failed for File System Check on /dev/disk/by-label/eighttb.
Mar 17 11:05:41 odroidxu4 systemd[1]: Dependency failed for /srv/dev-disk-by-label-eighttb.
Mar 17 11:05:41 odroidxu4 systemd[1]: srv-dev\x2ddisk\x2dby\x2dlabel\x2deighttb.mount: Job srv-dev\x2ddisk\x2dby\x2dlabel\x2deighttb.mount/start failed with result 'dependency'.
Mar 17 11:05:41 odroidxu4 systemd[1]: Startup finished in 8.641s (kernel) + 5min 6.645s (userspace) = 5min 15.287s.
Mar 17 11:05:41 odroidxu4 systemd[1]: systemd-fsck@dev-disk-by\x2dlabel-eighttb.service: Job systemd-fsck@dev-disk-by\x2dlabel-eighttb.service/start failed with result 'dependency'.
Mar 17 11:05:41 odroidxu4 systemd[1]: dev-disk-by\x2dlabel-eighttb.device: Job dev-disk-by\x2dlabel-eighttb.device/start failed with result 'timeout'.
Mar 17 11:05:43 odroidxu4 monit[1826]: 'mountpoint_srv_dev-disk-by-label-eighttb' status failed (1) -- /srv/dev-disk-by-label-eighttb is not a mountpoint
Mar 17 11:06:13 odroidxu4 monit[1826]: 'mountpoint_srv_dev-disk-by-label-eighttb' status failed (1) -- /srv/dev-disk-by-label-eighttb is not a mountpoint
Mar 17 11:06:43 odroidxu4 monit[1826]: 'mountpoint_srv_dev-disk-by-label-eighttb' status failed (1) -- /srv/dev-disk-by-label-eighttb is not a mountpoint
Mar 17 11:07:14 odroidxu4 monit[1826]: 'mountpoint_srv_dev-disk-by-label-eighttb' status failed (1) -- /srv/dev-disk-by-label-eighttb is not a mountpoint
Mar 17 11:07:44 odroidxu4 monit[1826]: 'mountpoint_srv_dev-disk-by-label-eighttb' status failed (1) -- /srv/dev-disk-by-label-eighttb is not a mountpoint
Mar 17 11:08:14 odroidxu4 monit[1826]: 'mountpoint_srv_dev-disk-by-label-eighttb' status failed (1) -- /srv/dev-disk-by-label-eighttb is not a mountpoint
Mar 17 11:08:44 odroidxu4 monit[1826]: 'mountpoint_srv_dev-disk-by-label-eighttb' status failed (1) -- /srv/dev-disk-by-label-eighttb is not a mountpoint
Alles anzeigen
Sooooooo...
I've been very close to having the whole NAS set up with 5 docker containers running and configured, then hit this snag. I've learned a lot tracking it down, but... ready to fix it and move on.
I tried what was suggested in this thread, which creating a scheduled job of mount -a on reboot. This did mount the drive, but after my docker containers started, which meant they didn't work. So that solution didn't work for me.
Insights and kind instructions are appreciated!