Error during boot: Gave up waiting for root file system device

    • Resolved
    • OMV 4.x
    • Error during boot: Gave up waiting for root file system device

      Hi everyone.
      I tried to boot with a new installation of OMV4, but I got this error:


      I got this error even with my OMV3 installation.
      sdh1 is the partition where OMV is installed.
      Also what's this AE_NOT_FOUND error?

      Why I-m getting this? How can I resolve it? :(
      Intel G4400 - Asrock H170M Pro4S - 8GB ram - 2x4TB WD RED in RAID1 - ZFS Mirror 2x6TB Seagate Ironwolf
      OMV 4.1.4 - Kernel 4.14 backport 3 - omvextrasorg 4.1.2

      The post was edited 1 time, last by Blabla ().

    • I have already the latest bios on my motherboard, so I will ignore this error,What it worry me is what it came after:
      • 1 tablet loading failure. -> this seems a big problem
      • sdh1 does not exist -> gparted can see it and it's the OMV partition. Should I tell the system to wait more?
      Intel G4400 - Asrock H170M Pro4S - 8GB ram - 2x4TB WD RED in RAID1 - ZFS Mirror 2x6TB Seagate Ironwolf
      OMV 4.1.4 - Kernel 4.14 backport 3 - omvextrasorg 4.1.2
    • This is the content of /etc/fstab



      # /etc/fstab: static file system information.
      #
      # Use 'blkid' to print the universally unique identifier for a
      # device; this may be used with UUID= as a more robust way to name devices
      # that works even if disks are added and removed. See fstab(5).
      #
      # <file system> <mount point> <type> <options> <dump> <pass>
      # / was on /dev/sdh1 during installation
      UUID=227eb144-f8ce-4fa5-bfce-0a601f3f53d3 / ext4 errors=remount-ro 0 1
      # swap was on /dev/sdh5 during installation
      UUID=44246d14-323d-414f-8326-a5e92ca9bd4a none swap sw 0 0
      tmpfs /tmp tmpfs defaults 0 0
      Intel G4400 - Asrock H170M Pro4S - 8GB ram - 2x4TB WD RED in RAID1 - ZFS Mirror 2x6TB Seagate Ironwolf
      OMV 4.1.4 - Kernel 4.14 backport 3 - omvextrasorg 4.1.2

      The post was edited 3 times, last by Blabla ().

    • Since one table seems damaged, should I use gparted to check and repair every tablet of every hard disk?

      Also I don't get why bbut my previeus post is blocked:

      This is the content of /etc/fstab

      # /etc/fstab: static file system information.
      #
      # Use 'blkid' to print the universally unique identifier for a
      # device; this may be used with UUID= as a more robust way to name devices
      # that works even if disks are added and removed. See fstab(5).
      #
      # <file system> <mount point> <type> <options> <dump> <pass>
      # / was on /dev/sdh1 during installation
      UUID=227eb144-f8ce-4fa5-bfce-0a601f3f53d3 / ext4 errors=remount-ro 0 1
      # swap was on /dev/sdh5 during installation
      UUID=44246d14-323d-414f-8326-a5e92ca9bd4a none swap sw 0 0
      tmpfs /tmp tmpfs defaults 0 0
      Intel G4400 - Asrock H170M Pro4S - 8GB ram - 2x4TB WD RED in RAID1 - ZFS Mirror 2x6TB Seagate Ironwolf
      OMV 4.1.4 - Kernel 4.14 backport 3 - omvextrasorg 4.1.2
    • Error during boot

      After some research I found that the 1 table load failures is because of the motherboard, so we can ignore that error.

      Now my only problem is "gave up for root file system device" error, I really don't know how to solve it :(

      Send by my Sony XZ1 using Tapatalk
      Intel G4400 - Asrock H170M Pro4S - 8GB ram - 2x4TB WD RED in RAID1 - ZFS Mirror 2x6TB Seagate Ironwolf
      OMV 4.1.4 - Kernel 4.14 backport 3 - omvextrasorg 4.1.2
    • Udate: the problem is with the SD card, it seems to be too slow or something.
      I installed OMV on a test hdd that I have (I avoided it since it's in the point of death and only used it for test) and everything is fine now.
      Intel G4400 - Asrock H170M Pro4S - 8GB ram - 2x4TB WD RED in RAID1 - ZFS Mirror 2x6TB Seagate Ironwolf
      OMV 4.1.4 - Kernel 4.14 backport 3 - omvextrasorg 4.1.2
    • I've reinstalled OMV4 on the SD card as a second try, now this is fstab file>

      Source Code

      1. # /etc/fstab: static file system information.
      2. #
      3. # Use 'blkid' to print the universally unique identifier for a
      4. # device; this may be used with UUID= as a more robust way to name devices
      5. # that works even if disks are added and removed. See fstab(5).
      6. #
      7. # <file system> <mount point> <type> <options> <dump> <pass>
      8. # / was on /dev/sdg1 during installation
      9. UUID=18c95934-7c19-4788-8042-ade803ef3706 / ext4 errors=remount-ro 0 1
      10. # swap was on /dev/sdg5 during installation
      11. UUID=d24e1951-9742-442c-a9dc-0979a92fc48b none swap sw 0 0
      12. tmpfs /tmp tmpfs defaults 0 0
      Display All
      So I should comment the UUID line and add a new one with
      /dev/disk/by-uuid/18c95934-7c19-4788-8042-ade803ef3706 ext4 errors=remount-ro 0 1
      right?

      P.S. I mounted the SD card on OMV, but if I open fspab with nano I can only read it, I can't write :( The same from windows (I shared etc on windows)
      Intel G4400 - Asrock H170M Pro4S - 8GB ram - 2x4TB WD RED in RAID1 - ZFS Mirror 2x6TB Seagate Ironwolf
      OMV 4.1.4 - Kernel 4.14 backport 3 - omvextrasorg 4.1.2

      The post was edited 1 time, last by Blabla ().

    • Look at what I posted - it has the UUID line commented out and the new line added in.

      Are you running nano as the root user? Only root can write to that file.

      The other possibility (not sure because you didn't fully disclose how you are doing this) would be to remount the rootfs as read/write:

      sudo mount -o remount,rw /dev/disk/by-uuid/18c95934-7c19-4788-8042-ade803ef3706 /

      Then edit fstab with nano.
      OMV 4.x - ASRock Rack C2550D4I - 16GB ECC - Silverstone DS380
    • Docker can be a bit of a learning curve. Depends on how well the containers you wish to use are documented. The ones from linuxserver.io are OK, at least the docs are uniformly presented.

      I'm still new at dockers. But one thing I have found so far is they don't seem to be as fully configurable as the same software manually installed via packages. Or maybe I am missing something.

      One example is the Deluge docker from linuxserver.io (I have not tired others yet). Doesn't seem to be as fully configurable regarding where it will drop files while downloading, moving files when done to another location, etc. I will admit I need to spend more time with it though.
      OMV 4.x - ASRock Rack C2550D4I - 16GB ECC - Silverstone DS380
    • Yeah, I'm thining if it's better to use deluge and sonarr manually installed or with docker. But for that I'll open a topic in the right section, I don't want to go OT :)
      Intel G4400 - Asrock H170M Pro4S - 8GB ram - 2x4TB WD RED in RAID1 - ZFS Mirror 2x6TB Seagate Ironwolf
      OMV 4.1.4 - Kernel 4.14 backport 3 - omvextrasorg 4.1.2
    • Not sure why, I' trying to boot from my old installation (OMV3),
      I had the same error with it too, So I edited the fgstab file like this:

      Source Code

      1. # /etc/fstab: static file system information.
      2. #
      3. # Use 'blkid' to print the universally unique identifier for a
      4. # device; this may be used with UUID= as a more robust way to name devices
      5. # that works even if disks are added and removed. See fstab(5).
      6. #
      7. # <file system> <mount point> <type> <options> <dump> <pass>
      8. # / was on /dev/sde1 during installation
      9. #UUID=3ea78407-b370-43c7-ae25-290c365a4927 / ext4 errors=remount-ro 0 1
      10. /dev/disk/by-uuid/3ea78407-b370-43c7-ae25-290c365a4927 / ext4 errors=remount-ro 0 1
      11. # swap was on /dev/sde5 during installation
      12. UUID=462536b4-33a7-439b-8ed3-13e27998acdb none swap sw 0 0
      13. tmpfs /tmp tmpfs defaults 0 0
      14. # >>> [openmediavault]
      15. UUID=8d1d82dc-45af-438d-9c7c-271640aed5b2 /media/8d1d82dc-45af-438d-9c7c-271640aed5b2 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.use$
      16. /dev/disk/by-label/Test1 /srv/dev-disk-by-label-Test1 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=v$
      17. /dev/disk/by-label/Test2 /srv/dev-disk-by-label-Test2 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=v$
      18. /srv/dev-disk-by-label-Test1:/srv/dev-disk-by-label-Test2 /srv/d4dbecef-0281-42f7-a4ea-92d88e62f9c0 fuse.mergerfs defaults,allow_other,direct_io,$
      19. # <<< [openmediavault]
      Display All
      but I get the error "/dev/disk/by-uuid/3ea78407-b370-43c7-ae25-290c365a4927 doesn't exist".

      why that? :(
      Intel G4400 - Asrock H170M Pro4S - 8GB ram - 2x4TB WD RED in RAID1 - ZFS Mirror 2x6TB Seagate Ironwolf
      OMV 4.1.4 - Kernel 4.14 backport 3 - omvextrasorg 4.1.2
    • I have been having the same issue with no luck trying the fixes posted here. My issue was that during install, the root filesystem was installed on "/dev/hdh1" and after install, that became "/dev/hdg1". after reading several fixes that didn't work, what ended up as the fix for my issue was:

      edit the file

      Source Code

      1. /boot/grub/grub.cfg
      and i found a few instances of "/dev/hdh(1 and 5)" which were then changed to "/dev/hdg(1 and 5)

      Just in case someone has the same issue.
      OMV1: OMV 2.2.1 - Intel Xeon "E5530" @ 2.4 GHz - 48 GB DDR3 ECC 800 - 18.19 TB Software Raid 5

      Desktop:
      Win 10 Pro - AMD A10-5800 APU @ 3.8 GHz - 16 GB DDR 3 1866 - 600 GB