Error during boot: Gave up waiting for root file system device
-
- gelöst
- OMV 4.x
- Blabla
-
-
Get the latest BIOS:
https://lists.debian.org/debian-user/2017/04/msg00698.html -
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?
-
Find a way to examine /etc/fstab and see what's there for the boot device mount.
-
This is the content of /etc/fstab
Zitat
# /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 -
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
Zitat# /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 -
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
-
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. -
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
-
I've reinstalled OMV4 on the SD card as a second try, now this is fstab file>
Code
Alles anzeigen# /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/sdg1 during installation UUID=18c95934-7c19-4788-8042-ade803ef3706 / ext4 errors=remount-ro 0 1 # swap was on /dev/sdg5 during installation UUID=d24e1951-9742-442c-a9dc-0979a92fc48b none swap sw 0 0 tmpfs /tmp tmpfs defaults 0 0
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)
-
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.
-
Great! now is working! thanks a lot!
-
Don't forget to use the Flash Memory plugin.
-
First thing that I've installed Now I only have to undestarand how to use docker since I never used it
-
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.
-
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
-
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:Code
Alles anzeigen# /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/sde1 during installation #UUID=3ea78407-b370-43c7-ae25-290c365a4927 / ext4 errors=remount-ro 0 1 /dev/disk/by-uuid/3ea78407-b370-43c7-ae25-290c365a4927 / ext4 errors=remount-ro 0 1 # swap was on /dev/sde5 during installation UUID=462536b4-33a7-439b-8ed3-13e27998acdb none swap sw 0 0 tmpfs /tmp tmpfs defaults 0 0 # >>> [openmediavault] UUID=8d1d82dc-45af-438d-9c7c-271640aed5b2 /media/8d1d82dc-45af-438d-9c7c-271640aed5b2 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.use$ /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$ /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$ /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,$ # <<< [openmediavault]
but I get the error "/dev/disk/by-uuid/3ea78407-b370-43c7-ae25-290c365a4927 doesn't exist".
why that?
-
The UUID differs?
-
The UUID differs?
ok, tried to edit the file again, not sure what was different, but after saving it now OMV booted
-
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
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.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!