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 - Be Quiet Pure Power 11 400 CM - Nanoxia Deep Silence 4 - 6TB Seagate Ironwolf - RAIDZ1 3x10TB WD - OMV 5 - Proxmox Kernel

    Einmal editiert, zuletzt von 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 - Be Quiet Pure Power 11 400 CM - Nanoxia Deep Silence 4 - 6TB Seagate Ironwolf - RAIDZ1 3x10TB WD - OMV 5 - Proxmox Kernel

  • Find a way to examine /etc/fstab and see what's there for the boot device mount.

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

  • This is the content of /etc/fstab



    Intel G4400 - Asrock H170M Pro4S - 8GB ram - Be Quiet Pure Power 11 400 CM - Nanoxia Deep Silence 4 - 6TB Seagate Ironwolf - RAIDZ1 3x10TB WD - OMV 5 - Proxmox Kernel

    3 Mal editiert, zuletzt von 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


    Intel G4400 - Asrock H170M Pro4S - 8GB ram - Be Quiet Pure Power 11 400 CM - Nanoxia Deep Silence 4 - 6TB Seagate Ironwolf - RAIDZ1 3x10TB WD - OMV 5 - Proxmox Kernel

  • 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 - Be Quiet Pure Power 11 400 CM - Nanoxia Deep Silence 4 - 6TB Seagate Ironwolf - RAIDZ1 3x10TB WD - OMV 5 - Proxmox Kernel

  • 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 - Be Quiet Pure Power 11 400 CM - Nanoxia Deep Silence 4 - 6TB Seagate Ironwolf - RAIDZ1 3x10TB WD - OMV 5 - Proxmox Kernel

  • I wouldn't give up so fast.


    Try editing /etc/fstab as follows:


    #UUID=227eb144-f8ce-4fa5-bfce-0a601f3f53d3 / ext4 errors=remount-ro 0 1


    /dev/disk/by-uuid/227eb144-f8ce-4fa5-bfce-0a601f3f53d3 / ext4 errors=remount-ro 0 1

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

  • I've reinstalled OMV4 on the SD card as a second try, now this is fstab file>

    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 - Be Quiet Pure Power 11 400 CM - Nanoxia Deep Silence 4 - 6TB Seagate Ironwolf - RAIDZ1 3x10TB WD - OMV 5 - Proxmox Kernel

    Einmal editiert, zuletzt von 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.

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

  • Great! now is working! thanks a lot!

    Intel G4400 - Asrock H170M Pro4S - 8GB ram - Be Quiet Pure Power 11 400 CM - Nanoxia Deep Silence 4 - 6TB Seagate Ironwolf - RAIDZ1 3x10TB WD - OMV 5 - Proxmox Kernel

  • First thing that I've installed :) Now I only have to undestarand how to use docker since I never used it

    Intel G4400 - Asrock H170M Pro4S - 8GB ram - Be Quiet Pure Power 11 400 CM - Nanoxia Deep Silence 4 - 6TB Seagate Ironwolf - RAIDZ1 3x10TB WD - OMV 5 - Proxmox Kernel

  • 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.

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

  • 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 - Be Quiet Pure Power 11 400 CM - Nanoxia Deep Silence 4 - 6TB Seagate Ironwolf - RAIDZ1 3x10TB WD - OMV 5 - Proxmox Kernel

  • 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:

    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 - Be Quiet Pure Power 11 400 CM - Nanoxia Deep Silence 4 - 6TB Seagate Ironwolf - RAIDZ1 3x10TB WD - OMV 5 - Proxmox Kernel

  • 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


    Code
    /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.

    OMV: OMV 6 - Intel I7-4770 @ 3.4 GHz - 16 GB DDR3 1600 - 31.8 TB MDADM RAID 6


    Desktop:
    Win 10 Pro - AMD RYZEN 5 3600X @4.2 - 32 GB DDR 4 3600 - 4 TB NVME

    Win 10 Pro - I7-4770k @ 4.3 GHz - 16 GB DDR 3 1600 Samsung 960 Evo 500 (X2) Raid-0

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!