[solved]If you update it, it will crash?!

bredin · 2009-04-13 11:34:05

Like every time I've updated arch, it would crash. And today was not an exception!

I get this when I try to boot my computer:

:: Loading Initramfs
ERROR: Failed to parse block device name for ' /dev/disk/by-uuid/1a8cd0a1-a7cc-45d3-9c4c-8602d14911a7'
ERROR: Unable to create/detect root device ' /dev/disk/by-uuid/1a8cd0a1-a7cc-45d3-9c4c-8602d14911a7'
Dropping to recovery shell... type 'exit' to reboot
NOTE: klibc contans no 'ls' binary, use 'echo *' instead

If the device ' /dev/disk/by-uuid/1a8cd0a1-a7cc-45d3-9c4c-8602d14911a7' gets created while you are here, try adding 'rootdelay=8' or higher to the kernel command-line
ramfs$

So I added rootdelay=8 tp /boot/grub/menu.lst using parted magic, but it didn't work.

Last edited by bredin (2009-04-13 14:51:20)

Xyne · 2009-04-13 13:02:26

Do you mean that it really just crashed during the update, or do you mean that it just won't boot after you shut down?.

Anyway, use a livecd to boot the computer, mount your system and check the pacman log to figure out wtf happened and how you can fix it. If you can't get it working, post more info (what did you update, what kind of setup do you have (raid? lvm? leprechauns and gremlins?, what lines do you have in your grub configuration, etc).

*edit*
corrected for misinterpretation of OP

Last edited by Xyne (2009-04-13 13:19:57)

wonder · 2009-04-13 13:21:25

take a look in /etc/mkinitcpio.conf in HOOKS list and see if you have udev. you need udev in there if you want to use those UUID in /etc/fstab
if not add after base and run mkinitcpio -p kernel26

schuay · 2009-04-13 13:34:04

bredin wrote:

So I added rootdelay=8 tp /boot/grub/menu.lst using parted magic, but it didn't work.

You don't need a livecd to edit menu.lst, just press "e" on the line you want to edit while in the grub menu on boot. My personal quick fix would to be use /dev/sdaX instead of UUID. Oh and if your install crashes after every update, you must be doing something wrong

Last edited by schuay (2009-04-13 13:34:43)

bredin · 2009-04-13 13:56:26

Just did what you said schuay after hearing that UUID conflicted with udev. So now my system is up and running again Something strange happend to. The idle memory usage dropped from 134 to 86mb :S everything seems to be running just fine to!

Last edited by bredin (2009-04-13 13:57:13)

schuay · 2009-04-13 15:18:30

by the way - editing through the grub menu doesn't make the changes permanent! you still need to edit your menu.lst manually afterwards. good to hear its working.

bredin · 2009-04-13 15:34:56

I edited my files with partedmagic

Preston C. · 2009-04-14 00:02:18

I have had a very similar problem after upgrading yesterday. The kernel and the fallback failed while being installed it had something to do with RAID, then it said FATAL, on both the kernel and the fallback.

Is there anyway to access pacman.log from the boot screen? So that I can give you a more thorough report.

Or even more, is there a way to fix it, .

I get the same error message as bredin, just more of them, when trying to boot. It is causing a real problem because I can't boot and get to my files.

In case it helps, I do have another hard drive in the system, but have not setup a RAID configuration in the BIOS. Although, when in KDE I can see the other hard drive, but can't access it- it is /dev/sda, while Arch is /dev/sdb.

Bretin, do you have more than one hard drive in your system?

I think the overall problem has something to with my RAID setup, if you could call it that, in Arch. Although, I don't know. Help is appreciated.

[Edit]- I have just seen that even more people are having this problem, I will look at their threads.

Last edited by Preston C. (2009-04-14 00:05:22)

schuay · 2009-04-14 06:59:06

Preston C. wrote:

I have had a very similar problem after upgrading yesterday. The kernel and the fallback failed while being installed it had something to do with RAID, then it said FATAL, on both the kernel and the fallback.

Either use the device naming scheme instead of UUID, or boot using a livecd, mount your root filesystem somewhere and edit /etc/mkinitcpio.conf and remove raid from the HOOKS line if you don't use raid.

Preston C. · 2009-04-14 22:47:41

schuay wrote:

Either use the device naming scheme instead of UUID, or boot using a livecd, mount your root filesystem somewhere and edit /etc/mkinitcpio.conf and remove raid from the HOOKS line if you don't use raid.

Thank you schuay, very much. I would like to use the second method. Would you mind answering these questions? I posted them on another thread, but didn't get a reply. It seems that this is the method- edit mkinitcpio.conf and then build the new kernel. I do not know how to do these things. Also, if I do the two things just mentioned do I also need to edit grub?

- Is it possible to access /etc/mkinitcpio.conf from the boot menu?
- Last, how did you build the latest kernel? I already have it installed, just not built.

Many Thanks,
Preston

Here is the thread, with the same problem I am having- http://bbs.archlinux.org/viewtopic.php?id=69550 . whaler said something about editing grub file, I don't know if it is necessary though after editing hooks and building the kernel? One of the good things about Linux is that you can usually fix the problem, .

schuay · 2009-04-15 19:13:12

sorry - seems like I didn't read your first post thoroughly enough, changing the grub naming scheme won't help with a broken initcpio..

i see you already got an answer on the other post - I'd also go with option 2 from http://wiki.archlinux.org/index.php/Ker … all_kernel , but you don't necessarily need to revert to the old kernel..
mount your existing system and chroot into it like the wiki says, edit your mkinitcpio.conf and pacman -S kernel26.

if that works you should be back to a bootable system

Arch Linux

#1 2009-04-13 11:34:05

[solved]If you update it, it will crash?!

#2 2009-04-13 13:02:26

Re: [solved]If you update it, it will crash?!

#3 2009-04-13 13:21:25

Re: [solved]If you update it, it will crash?!

#4 2009-04-13 13:34:04

Re: [solved]If you update it, it will crash?!

#5 2009-04-13 13:56:26

Re: [solved]If you update it, it will crash?!

#6 2009-04-13 15:18:30

Re: [solved]If you update it, it will crash?!

#7 2009-04-13 15:34:56

Re: [solved]If you update it, it will crash?!

#8 2009-04-14 00:02:18

Re: [solved]If you update it, it will crash?!

#9 2009-04-14 06:59:06

Re: [solved]If you update it, it will crash?!

#10 2009-04-14 22:47:41

Re: [solved]If you update it, it will crash?!

#11 2009-04-15 19:13:12

Re: [solved]If you update it, it will crash?!

Board footer