You are not logged in.
Hi,
I'm having an issue with the kernel. I get this weird error while booting:
Booting the kernel.
:: running early hook [udev]
:: running hook [udev]
:: Triggering uevents...
ERROR: device '' not found. Skipping fsck.
ERROR: Unable to find root device ''.
You are being dropped to a recovery shell
Type 'exit' to try and continue booting
sh: can't access tty: job control turned off
[rootfs /]# _I don't have the slightest idea what to type in that shell, so I exit (^D) and get an error with its shell, another one and finally a kernel panic. Do I have to report the other two error as well? I think this might be related to a recent change in my syslinux.cfg. I wanted to add hibernation cabability to my arch, so I added "resume=/dev/sda2" (my swap) to kernel options. It should not yield such a result though. As a matter of fact, I get it even if I remove that parameter at runtime. For now, I managed to boot with Fallback Initramfs.
Here is syslinux.cfg, as well:
# Config file for Syslinux -
# /boot/syslinux/syslinux.cfg
#
# Comboot modules:
# * menu.c32 - provides a text menu
# * vesamenu.c32 - provides a graphical menu
# * chain.c32 - chainload MBRs, partition boot sectors, Windows bootloaders
# * hdt.c32 - hardware detection tool
# * reboot.c32 - reboots the system
# * poweroff.com - shutdown the system
#
# To Use: Copy the respective files from /usr/lib/syslinux to /boot/syslinux.
# If /usr and /boot are on the same file system, symlink the files instead
# of copying them.
#
# If you do not use a menu, a 'boot:' prompt will be shown and the system
# will boot automatically after 5 seconds.
#
# Please review the wiki: https://wiki.archlinux.org/index.php/Syslinux
# The wiki provides further configuration examples
DEFAULT arch
PROMPT 1 # Set to 1 if you always want to display the boot: prompt
TIMEOUT 50
# You can create syslinux keymaps with the keytab-lilo tool
#KBDMAP de.ktl
# Menu Configuration
# Either menu.c32 or vesamenu32.c32 must be copied to /boot/syslinux
UI menu.c32
#UI vesamenu.c32
# Refer to http://syslinux.zytor.com/wiki/index.php/Doc/menu
MENU TITLE Arch Linux
#MENU BACKGROUND splash.png
MENU COLOR border 30;44 #40ffffff #a0000000 std
MENU COLOR title 1;36;44 #9033ccff #a0000000 std
MENU COLOR sel 7;37;40 #e0ffffff #20ffffff all
MENU COLOR unsel 37;44 #50ffffff #a0000000 std
MENU COLOR help 37;40 #c0ffffff #a0000000 std
MENU COLOR timeout_msg 37;40 #80ffffff #00000000 std
MENU COLOR timeout 1;37;40 #c0ffffff #00000000 std
MENU COLOR msg07 37;40 #90ffffff #a0000000 std
MENU COLOR tabmsg 31;40 #30ffffff #00000000 std
# boot sections follow
#
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
#
#-*
# (0) Arch Linux
LABEL arch
MENU LABEL Arch Linux
LINUX ../vmlinuz-linux
APPEND root=/dev/disk/by-uuid/dc891acc-9ff7-4d95-bba4-bc2e502301e7 ro
APPEND resume=/dev/sda2
INITRD ../initramfs-linux.img
# (1) Arch Linux Fallback
LABEL archfallback
MENU LABEL Arch Linux Fallback
LINUX ../vmlinuz-linux
APPEND root=/dev/disk/by-uuid/dc891acc-9ff7-4d95-bba4-bc2e502301e7 ro
INITRD ../initramfs-linux-fallback.img
# (2) Windows
#LABEL windows
#COM32 chain.c32
#APPEND hd0 0
LABEL hdt
MENU LABEL HDT (Hardware Detection Tool)
COM32 hdt.c32
LABEL reboot
MENU LABEL Reboot
COM32 reboot.c32
LABEL off
MENU LABEL Power Off
COMBOOT poweroff.comAny ideas?
Thank you,
rubik
Last edited by rubik (2012-07-22 10:03:59)
Offline
Just a question, why are you using relatives paths ?
https://balaskas.gr
Linux System Engineer - Registered Linux User #420129
Offline
That's the default configuration. I only changed a couple of things, minor ones. Relative paths were defaults. I just checked for update and updated the kernel to 3.4.6-1 and that seemed to solve it. That's weird though...
Offline
I suggest that you only use one APPEND line per entry.
e.g.
APPEND root=/dev/disk/by-uuid/dc891acc-9ff7-4d95-bba4-bc2e502301e7 ro resume=/dev/sda2Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Oh thank you. I didn't know that.
Offline
Also, don't use "root=/dev/disk/by-uuid/...", that's just wrong. Udev kicks in after the bootloader phase.
https://wiki.archlinux.org/index.php/Sy … nux_Config
Here's mine:
LABEL arch
MENU LABEL Arch Linux
LINUX ../vmlinuz-linux
APPEND root=UUID=978e3e81-8048-4ae1-8a06-aa727458e8ff ro quiet vga=current
INITRD ../initramfs-linux.imgAnd don't forget to mark it as solved.
I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).
Offline
I'm surprised. That's default config. I will do as you suggested! Thanks!
Offline
I could be wrong. I mean, it does work with /dev/sdaX, so why not with /dev/disk/by-uuid/* ? Unfortunately, I couldn't find any example on syslinux.org, so you will have to rely on the wiki and my word that "root=UUID=..." works fine.
By the way, the default config uses "root=/dev/sda3". If you don't believe me, click the "Download from Mirror" and see for yourself.
I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).
Offline
I checked it and you are absolutely right, but I can assure you that when I installed it I only changed PROMPT and some names, but nothing else. Probably I installed an old version of syslinux during ArchLinux installation (second last iso was 2011...), then I upgraded it later. Now that I changed syslinux config I can reboot and see what happens.
Offline