Unable to find root device - after updating

glitch · 2012-06-01 20:38:43

Hey guys!

I'm having the same problem but nothing posted above has worked. Is there anyone else stil unable to get this sorted??

mayuresh · 2012-06-04 15:50:51

This is my first day with Arch Linux, though not with Linux and I ran into this issue after installation.

I followed the instructions on this thread, though that has not solved my problem.

I first installed using the installation CD and later on did a re-install from CD by selecting remote repositories with the hope that the issue gets resolved. It still is not resolved.

Would appreciate any help.

ignorant · 2012-06-09 18:02:25

Upgraded to kernel 3.3.8 last night, try to boot today, this exact problem. It threw me into the initramfs recovery shell.

`shutdown`? no. `halt`? no. `reboot`? nope. `logout`? no. `exit`? nope. Ctrl+D ... panic: attempting to kill init. (In retrospect, maybe I could have `init 0`'d it?)

I did a hard reboot, and the system actually booted on the next try. Everything seems fine, but I'm kind of scared to reboot now. Hoping to figure out the source of the problem. After reading this thread, it looks like just running mkinitcpio again only sometimes works.

Terminator · 2012-06-09 19:35:20

Try to reinstall linux after the chroot. So do what pineapple-biku said, but also reinstall linux:

pacman -Syyu udev mkinitcpio linux
mkinitcpio -p linux
reboot

edit: The module not found errors and the fact that for some it works if they install linux-lts suggest something is wrong with the kernel.

Last edited by Terminator (2012-06-09 19:36:43)

masteryod · 2012-06-09 21:25:35

for future reference:

https://wiki.archlinux.org/index.php/Pa … nger_boot..

Last edited by masteryod (2012-06-09 21:27:39)

ignorant · 2012-06-10 05:35:40

Thank you, master yoda. I shall try.

"Do, or do not. There is no try."

Yessir!

ignorant · 2012-06-10 16:35:41

Seems to have worked. Thank you, Terminator and Master Yoda.

Pennypacker · 2012-06-10 19:00:51

Hi all!

I'm still eager to know what is causing this. I'm having a VPS with Arch on and there I can't mount any ISO image just reinstall the with an old Arch build on. So I'm waiting to upgrade Kernel until someone has fixed this.

falconindy · 2012-06-10 21:14:01

Caused by.... not reading the news? Not taking care of safe initramfs creation before rebooting? There's no bug here. At least, none that's been reported to me.

Pennypacker · 2012-06-10 21:31:16

Well I red the news and upgraded my system as announced. But the initramfs creation didn't went so well even though I ran mkinitcpio -p linux once more after all upgrading. Got my laptop running via mounting from CD. But for me it looks like there might be a bug.

paranoos · 2012-06-11 20:36:37

I too noticed the news and did the updates accordingly. Things went well at that time. My system broke on a more recent update. (Besides, I don't use udev in my mkinitcpio config)

I encountered this problem after updating; linux (3.3.7-1 -> 3.3.8-1), mkinitcpio-busybox (1.19.4-2 -> 1.20.1-1), and mkinitcpio (0.9.0-2 -> 0.9.2-1) among others.

My mkinitcpio config is customized for my system to be extremely lean and fast:

MODULES="sata-nv sd-mod ext4"
BINARIES=""
FILES=""
HOOKS="base"
COMPRESSION="cat"

When the system didn't work, I booted the install CD to rebuild the image, and I also built the default config with udev autodetection just in case. The rebuilt custom image still didn't boot, but the autodetect image did. I compared the output of lsinitcpio for the two images to see if maybe I'm missing a module for the new kernel, but besides sr-mod and pata-amd (which I don't need since my configuration is for sata), nearly everything seemed to be usb or sound related.

I will try to investigate further, but does the forum have any tips for me?

paranoos · 2012-06-11 23:24:10

Alright, I have (temporarily) fixed my issue by adding the udev hook, but this should not be necessary for my setup.

lsinitcpio reveals that there are no extra modules added to the image with the udev hook, but /dev/sda1 cannot be found without it.

Unfortunately, my usb keyboard doesn't work at the prompt following the error message (adding the usbinput hook does not fix this), so I cannot investigave /dev to see what devices do exist, and I don't have a PS/2 keyboard handy at the moment.

If memory serves, there used to be a message at bootup saying something like "/dev/sda1 not found, creating node", and the script presumably ran an mknod command. Perhaps this functionality has been removed in mkinitcpio 0.9.2?

unixbhaskar · 2012-06-14 05:50:35

After having gone through the entire thread and did few thing menltioned in the thread..still I am landed in "recovery shell"...what the heck!

Now what I did?

Chroot'ing to Arch

get usb in

then

build linux-kernel

then

put the usb into the hook

then

reboot

Still failing!!!

Kindly suggest what more has to be done to get it work!!

ewaller · 2012-06-14 06:14:12

unixbhaskar wrote:

After having gone through the entire thread and did few thing menltioned in the thread..still I am landed in "recovery shell"...what the heck!

I am not a doctor, but those I know are pretty clear. If a patient has a symptom, the first diagnoses should rule out the common causes, before moving to the exotic ones.

This thread is about the exotic. Did you verify that your grub configuration correctly identifies the boot disk? If you are using UUIDs, is it possible the UUID for the root partition has now changed?

If you are not using UUIDs, did the BIOS somehow reorder your disks?

unixbhaskar · 2012-06-14 08:28:17

ewaller wrote:

unixbhaskar wrote:
After having gone through the entire thread and did few thing menltioned in the thread..still I am landed in "recovery shell"...what the heck!
I am not a doctor, but those I know are pretty clear. If a patient has a symptom, the first diagnoses should rule out the common causes, before moving to the exotic ones.
This thread is about the exotic. Did you verify that your grub configuration correctly identifies the boot disk? If you are using UUIDs, is it possible the UUID for the root partition has now changed?
If you are not using UUIDs, did the BIOS somehow reorder your disks?

I am impressed by your query!

Now let me tell you..what I find out I have separate boot physicall partition..I run Slackware,Gentoo,Arch,Debian,Scientific Linux and Fedora....all physicall partition..and I boot through Fedora grub..

And I have had cross check the grub entry and find out the UUID by chrooting to Arch and typing bklid binary ...Then put it back to the grub enlisting.

Okay let me five you my UUID list entry :

bhaskar@Fedora_13:55:47_Thu Jun 14:~> sudo /sbin/blkid
[sudo] password for bhaskar:
/dev/sda1: LABEL="ARCH" UUID="9db5a364-ee86-4c57-8252-bfff8581e4b6" TYPE="ext4"
/dev/sda2: LABEL="Fedora-boot" UUID="ff94a6b0-3eee-4dc9-83e0-cbde449e93d7" TYPE="ext3"
/dev/sda3: UUID="kiCF1K-xTxV-t2Yu-CrBX-oENB-1kSn-6UY4Va" TYPE="LVM2_member"
/dev/sda5: UUID="X2MDAl-EaD9-s0kY-FbpZ-X6Wo-GowQ-yvTu1z" TYPE="LVM2_member"
/dev/sda6: LABEL="Fedora" UUID="7945ae6e-7061-4153-a5a1-ab9f60f693ae" TYPE="ext4"
/dev/sda7: UUID="61147c93-cf06-4d45-8204-b79b5b5d19a4" TYPE="swap"
/dev/sda8: LABEL="Slackware" UUID="77de30c7-fb6a-42d8-9cc3-7bd29e2cba06" TYPE="ext4"
/dev/sda9: LABEL="Gentoo" UUID="d83b45ce-ce1c-4678-9663-b884bab6f5cb" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda10: LABEL="Debian" UUID="1c0feb69-e586-4b2a-b774-176066a12e00" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda11: LABEL="ScientificLinux" UUID="7dedb9fe-8d77-4c93-bdbd-3297281041be" TYPE="ext4"
/dev/sda12: LABEL="openSUSE" UUID="924f28b3-8cda-4d7e-a833-c7687580e113" TYPE="ext4"
/dev/sda13: UUID="1Ke3cG-vv1Y-vgi6-Sszr-r3nz-xbQx-QzFyp1" TYPE="LVM2_member"
/dev/mapper/home-home: UUID="9fa403bf-858d-4ce2-9b5e-03bdeb2e9406" TYPE="ext3"
/dev/mapper/data-lvmdata: UUID="569e992f-3782-4689-8abf-85b59af4ba17" TYPE="ext3"

Here is my grub:
set default="0"
menuentry 'Fedora (3.4.0-1.fc17.i686)' --class fedora --class gnu-linux --class gnu --class os {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos2)'
search --no-floppy --fs-uuid --set=root ff94a6b0-3eee-4dc9-83e0-cbde449e93d7
echo 'Loading Fedora (3.4.0-1.fc17.i686)'
linux /vmlinuz-3.4.0-1.fc17.i686 root=UUID=7945ae6e-7061-4153-a5a1-ab9f60f693ae ro rd.md=0 rd.lvm=0 rd.dm=0 KEYTABLE=us SYSFONT=latarcyrheb-sun16 rhgb rd.luks=0 LANG=en_US.UTF-8
echo 'Loading initial ramdisk ...'
initrd /initramfs-3.4.0-1.fc17.i686.img
}
#menuentry 'Fedora (3.3.7-1.fc17.i686)' --class fedora --class gnu-linux --class gnu --class os {
# load_video
# set gfxpayload=keep
# insmod gzio
# insmod part_msdos
# insmod ext2
# set root='(hd0,msdos2)'
# search --no-floppy --fs-uuid --set=root ff94a6b0-3eee-4dc9-83e0-cbde449e93d7
# echo 'Loading Fedora (3.3.7-1.fc17.i686)'
# linux /vmlinuz-3.3.7-1.fc17.i686 root=UUID=7945ae6e-7061-4153-a5a1-ab9f60f693ae ro rd.md=0 rd.lvm=0 rd.dm=0 KEYTABLE=us SYSFONT=latarcyrheb-sun16 rhgb rd.luks=0 LANG=en_US.UTF-8
# echo 'Loading initial ramdisk ...'
# initrd /initramfs-3.3.7-1.fc17.i686.img
#}

### BEGIN /etc/grub.d/30_os-prober ###0
menuentry 'Arch-Linux (on /dev/sda1)' --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root 9db5a364-ee86-4c57-8252-bfff8581e4b6
linux /boot/vmlinuz-linux root=UUID=9db5a364-ee86-4c57-8252-bfff8581e4b6 vga=791
initrd /boot/initramfs-linux.img
}
menuentry 'Debian GNU/Linux with kernel 2.6.32-5-686 (on /dev/sda10)' --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos10)'
search --no-floppy --fs-uuid --set=root 1c0feb69-e586-4b2a-b774-176066a12e00
linux /boot/vmlinuz-2.6.32-5-686 root=UUID=1c0feb69-e586-4b2a-b774-176066a12e00 ro vga=791
initrd /boot/initrd.img-2.6.32-5-686
}
menuentry 'Scientific Linux (on /dev/sda11)' --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos11)'
search --no-floppy --fs-uuid --set=root 7dedb9fe-8d77-4c93-bdbd-3297281041be
linux /boot/vmlinuz-2.6.32-220.17.1.el6.i686 ro root=UUID=7dedb9fe-8d77-4c93-bdbd-3297281041be rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet crashkernel=auto
initrd /boot/initramfs-2.6.32-220.17.1.el6.i686.img
}
menuentry 'openSUSE 12.1 (i586) (on /dev/sda12)' --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos12)'
search --no-floppy --fs-uuid --set=root 924f28b3-8cda-4d7e-a833-c7687580e113
linux /boot/vmlinuz-3.2.9-jng4-desktop root=/dev/sda12
initrd /boot/initrd-3.2.9-jng4-desktop

}
menuentry 'Slackware-Linux (on /dev/sda8)' --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos8)'
search --no-floppy --fs-uuid --set=root 77de30c7-fb6a-42d8-9cc3-7bd29e2cba06
linux /boot/vmlinuz root=/dev/sda8 ro vt.default_utf8=0 vga = normal
}
menuentry 'Gentoo release 2.0.3 (on /dev/sda9)' --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos9)'
search --no-floppy --fs-uuid --set=root d83b45ce-ce1c-4678-9663-b884bab6f5cb
linux /boot/kernel-genkernel-x86-3.2.1-gentoo-r2 dolvm root=/dev/sda9 vga=791
initrd /boot/initramfs-genkernel-x86-3.2.1-gentoo-r2
}

Let me know if you want anything else!

-Bhaskar

Terminator · 2012-06-14 09:56:00

unixbhaskar wrote:

KindlyAfter having gone through the entire thread and did few thing menltioned in the thread..still I am landed in "recovery shell"...what the heck!
Now what I did?
Chroot'ing to Arch
get usb in
then
build linux-kernel
then
put the usb into the hook
then
reboot
Still failing!!!
suggest what more has to be done to get it work!!

You might want to read the thread again, you did not do what was suggested here. Also
what'
s
with
the
newlines
?

unixbhaskar · 2012-06-14 10:23:28

Terminator wrote:

unixbhaskar wrote:
KindlyAfter having gone through the entire thread and did few thing menltioned in the thread..still I am landed in "recovery shell"...what the heck!
Now what I did?
Chroot'ing to Arch
get usb in
then
build linux-kernel
then
put the usb into the hook
then
reboot
Still failing!!!
suggest what more has to be done to get it work!!
You might want to read the thread again, you did not do what was suggested here. Also
what'
s
with
the
newlines
?

Dude..what i wasn't done?? point me out explicitly...would be nice if you can...

Terminator · 2012-06-14 10:53:40

1) The thread suggest to reinstall udev, linux and mkinitcpio (probably that's not the problem)
2) After reinstalling these things, you should run 'mkinitcpio -p linux'. That will be the problem, definitely because you added a hook. After editing mkinitcpio.conf, you should always run 'mkinitcpio -p linux' again.

masteryod wrote:

for future reference:
https://wiki.archlinux.org/index.php/Pa … nger_boot..

Good luck.

unixbhaskar · 2012-06-14 10:56:43

Terminator wrote:

1) The thread suggest to reinstall udev, linux and mkinitcpio (probably that's not the problem)
2) After reinstalling these things, you should run 'mkinitcpio -p linux'. That will be the problem, definitely because you added a hook. After editing mkinitcpio.conf, you should always run 'mkinitcpio -p linux' again.
masteryod wrote:
for future reference:
https://wiki.archlinux.org/index.php/Pa … nger_boot..

Good luck.

I did all what you have mentioned...now trying one more time..for your confidence's sake

ewaller · 2012-06-14 13:19:22

unixbhaskar wrote:

[
Let me know if you want anything else!
-Bhaskar

No, I'd say you have it covered. Carry on...

BTW, you do get around. At least 8 distros installed

unixbhaskar · 2012-06-15 04:33:20

unixbhaskar wrote:

Terminator wrote:
1) The thread suggest to reinstall udev, linux and mkinitcpio (probably that's not the problem)
2) After reinstalling these things, you should run 'mkinitcpio -p linux'. That will be the problem, definitely because you added a hook. After editing mkinitcpio.conf, you should always run 'mkinitcpio -p linux' again.
masteryod wrote:
for future reference:
https://wiki.archlinux.org/index.php/Pa … nger_boot..

Good luck.
I did all what you have mentioned...now trying one more time..for your confidence's sake

Okay, Terminator buddy...your confidence spill on me I get over it ...It was a little typo in the hook that creating this saga!! You deserve a pint dude!! cheers!

BTW why the hell Gnome is not coming up...oh me! oh my! This should be al together speparate thread..

Last edited by unixbhaskar (2012-06-15 04:36:15)

giowck · 2012-06-15 16:17:22

pineapple-biku thank you!

I upgraded linux and after reboot the system failed to boot.

I hope it won't break like this at every kernel upgrade.
Is this common or just bad luck? What's the cause?

masteryod · 2012-06-15 17:19:53

giowck wrote:

I hope it won't break like this at every kernel upgrade.
Is this common or just bad luck? What's the cause?

I had this only once in couple of years as I use Arch (strangely it was about two weeks ago so maybe there was a bug).

giowck · 2012-06-16 08:49:49

masteryod wrote:

giowck wrote:
I hope it won't break like this at every kernel upgrade.
Is this common or just bad luck? What's the cause?
I had this only once in couple of years as I use Arch (strangely it was about two weeks ago so maybe there was a bug).

OK, found that Yaourt was the problem (depmod not found), see https://bugs.archlinux.org/task/27334

Which aur wrapper is better? packer will do it?

masteryod · 2012-06-16 10:28:53

giowck wrote:

OK, found that Yaourt was the problem (depmod not found), see https://bugs.archlinux.org/task/27334
Which aur wrapper is better? packer will do it?

And that's why I don't trust Yaourt and never use it, also that's why I do -Syu with pacman - pacman is official Arch Linux package manager. Packer is working for me very well but still I use it just to manage AUR packages. As their names indicates, these are helpers not pacman replacements

Last edited by masteryod (2012-06-16 10:30:19)

Arch Linux

#26 2012-06-01 20:38:43

Re: Unable to find root device - after updating

#27 2012-06-04 15:50:51

Re: Unable to find root device - after updating

#28 2012-06-09 18:02:25

Re: Unable to find root device - after updating

#29 2012-06-09 19:35:20

Re: Unable to find root device - after updating

#30 2012-06-09 21:25:35

Re: Unable to find root device - after updating

#31 2012-06-10 05:35:40

Re: Unable to find root device - after updating

#32 2012-06-10 16:35:41

Re: Unable to find root device - after updating

#33 2012-06-10 19:00:51

Re: Unable to find root device - after updating

#34 2012-06-10 21:14:01

Re: Unable to find root device - after updating

#35 2012-06-10 21:31:16

Re: Unable to find root device - after updating

#36 2012-06-11 20:36:37

Re: Unable to find root device - after updating

#37 2012-06-11 23:24:10

Re: Unable to find root device - after updating

#38 2012-06-14 05:50:35

Re: Unable to find root device - after updating

#39 2012-06-14 06:14:12

Re: Unable to find root device - after updating

#40 2012-06-14 08:28:17

Re: Unable to find root device - after updating

#41 2012-06-14 09:56:00

Re: Unable to find root device - after updating

#42 2012-06-14 10:23:28

Re: Unable to find root device - after updating

#43 2012-06-14 10:53:40

Re: Unable to find root device - after updating

#44 2012-06-14 10:56:43

Re: Unable to find root device - after updating

#45 2012-06-14 13:19:22

Re: Unable to find root device - after updating

#46 2012-06-15 04:33:20

Re: Unable to find root device - after updating

#47 2012-06-15 16:17:22

Re: Unable to find root device - after updating

#48 2012-06-15 17:19:53

Re: Unable to find root device - after updating

#49 2012-06-16 08:49:49

Re: Unable to find root device - after updating

#50 2012-06-16 10:28:53

Re: Unable to find root device - after updating

Board footer