System unbootable after upgrade: unable to find root device.

young lust · 2013-06-09 13:07:19

i did

pacman -Su

resulting in

:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...

Packages (1): filesystem-2013.05-2

Total Installed Size: 0.01 MiB
Net Upgrade Size: -0.30 MiB

warning: /etc/group installed as /etc/group.pacnew
warning: /etc/gshadow installed as /etc/gshadow.pacnew
warning: directory permissions differ on /home/
filesystem: 777 package: 755

what do those warnings mean?

Trilby · 2013-06-09 13:10:42

young lust, that means everything worked as expected. Congratulations, you've upgraded. I also saw the permission difference on (at least) one of my machines. I have a hunch what it is from - but it's harmless.

The pacnew files are also common, see the pacman wiki on what you should do with those.

young lust · 2013-06-09 13:54:57

Dudes. I cant boot system after that update
Error: device uuid=xzzzxxxxxxxxxxxxxxx not found. Skipping fsck.
Unable to find root device uuid=xxxxxxxxxx.
You are being dropped to a recov shell. help me

WonderWoofy · 2013-06-09 13:57:35

This should have nothing to do with UUIDs or modification of the bootloader... so I'm not sure this is the same problem at all. Can you check your UUIDs against what you have in your bootloader?

young lust · 2013-06-09 14:12:08

WonderWoofy wrote:

This should have nothing to do with UUIDs or modification of the bootloader... so I'm not sure this is the same problem at all. Can you check your UUIDs against what you have in your bootloader?

im a nigga, man!!! how i can check this?

jakobcreutzfeldt · 2013-06-09 14:20:11

young lust wrote:

im a nigga, man!!! how i can check this?

WTF does that mean?

WonderWoofy · 2013-06-09 14:29:29

Boot a live media and check it out man... I don't really know what that means either.

Xyne · 2013-06-09 14:31:49

Split from /usr upgrade thread as there is nothing to indicate that it is related so far.

jakobcreutzfeldt wrote:

young lust wrote:
im a nigga, man!!! how i can check this?
WTF does that mean?

The meaning of the word entirely depends on context, but there is very little here so I can't tell if it was just mildly inappropriate or completely inappropriate.

@young lust
Avoid such language and remain factual in your replies. This is a technical forum, not your Facebook wall.

Please use [code] tags as well to post the commands, output and file contents.

$ echo "this is an example of code tags"

Stebalien · 2013-06-09 18:08:36

blkid

ronnylov · 2013-06-09 18:57:00

I am having the same issue. Booting install media and using lsblk shows that the root device is present by the same UUID and it is mountable too. It boots GRUB but stops at the very same message as described in this thread.

Not sure what to do now. Reconfigure GRUB perhaps?

Scimmia · 2013-06-09 19:01:59

ronnylov, have you tried rebuilding your initramfs?

ronnylov · 2013-06-09 20:52:20

When trying to rebuild initramfs I get warning when generating the fallback image:

==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: bfa

But generation of images was successful and the system now boots correctly!
Thanks for the help!

WonderWoofy · 2013-06-09 21:12:19

Those are warnings not errors.

okubax · 2013-06-09 23:21:44

young lust wrote:

WonderWoofy wrote:
This should have nothing to do with UUIDs or modification of the bootloader... so I'm not sure this is the same problem at all. Can you check your UUIDs against what you have in your bootloader?
im a nigga, man!!! how i can check this?

/\
Downright offensive

adduu · 2013-06-20 04:15:20

Those pacman warnings are just fine. Don't worry about them. My system wasn't booting up. I was stupid enough to close the terminal window before seeing if everything went well after upgrade. So I just chroot my system using latest arch release. But still kernel was not getting upgraded. The problem was with the kmod package. I re-installed it. Kernel upgrade went fine after that.

Arch Linux

#1 2013-06-09 13:07:19

System unbootable after upgrade: unable to find root device.

#2 2013-06-09 13:10:42

Re: System unbootable after upgrade: unable to find root device.

#3 2013-06-09 13:54:57

Re: System unbootable after upgrade: unable to find root device.

#4 2013-06-09 13:57:35

Re: System unbootable after upgrade: unable to find root device.

#5 2013-06-09 14:12:08

Re: System unbootable after upgrade: unable to find root device.

#6 2013-06-09 14:20:11

Re: System unbootable after upgrade: unable to find root device.

#7 2013-06-09 14:29:29

Re: System unbootable after upgrade: unable to find root device.

#8 2013-06-09 14:31:49

Re: System unbootable after upgrade: unable to find root device.

#9 2013-06-09 18:08:36

Re: System unbootable after upgrade: unable to find root device.

#10 2013-06-09 18:57:00

Re: System unbootable after upgrade: unable to find root device.

#11 2013-06-09 19:01:59

Re: System unbootable after upgrade: unable to find root device.

#12 2013-06-09 20:52:20

Re: System unbootable after upgrade: unable to find root device.

#13 2013-06-09 21:12:19

Re: System unbootable after upgrade: unable to find root device.

#14 2013-06-09 23:21:44

Re: System unbootable after upgrade: unable to find root device.

#15 2013-06-20 04:15:20

Re: System unbootable after upgrade: unable to find root device.

Board footer