You are not logged in.
I upgraded my system today and after restarting it gives a message "root device 'dev/disk/by-uuid/....' doesn't exist, attempting to create it
error: failed to parse block device data for 'dev/disks/by-uuid/...'
error: unable to detect or create root device '.....'
you are being dropped to a recovery shell.
Today's upgrade was big, it upgraded udev and the kernel. Anyone have an idea what the problem might be?
Last edited by leberyo (2010-02-03 01:04:43)
Offline
Hmm... boot with your live cd and edit your /etc/fstab to use /dev/sdxy format rather than uuids. I've never understood why uuid's have been so popular...
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
I already tried that, any other idea?
Offline
Sorry if this seems silly but everyone makes mistakes.... Is your /etc/fstab, etc correct i.e. - do you have a leading "/" before the dev? I ask because the error message you posted doesn't show this.
Last edited by davidm (2010-02-03 01:08:06)
Offline
yes /dev/sda1 etc.
Offline
hmm, maybe go ahead and just post your /etc/fstab and the output of 'fdisk -l' and someone may see something that might help.
Offline
Here is my fstab:
#
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <pass>
devpts /dev/pts devpts defaults 0 0
shm /dev/shm tmpfs nodev,nosuid 0 0
#/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
#/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
#/dev/fd0 /media/fl auto user,noauto 0 0
#UUID=8C6085FC6085ED70 /mnt/windows ntfs-3g defaults,noatime 0 0
/dev/sda2 /boot ext3 defaults 0 1
/dev/sda3 / ext4 defaults,noatime 0 1
/dev/sda5 /tmp ext4 defaults,nosuid,nodev 0 1
/dev/sda6 /var ext4 defaults,nosuid,nodev 0 1
/dev/sda7 /usr ext4 defaults,noatime,rw,nodev 0 1
/dev/sda8 swap swap defaults 0 0
/dev/sda9 /home ext4 defaults,noatime,nosuid,nodev 0 1
fdisk -l doesn't output anything. I'm using Mint Linux livecd at the moment...
Offline
You know I also removed lvm2 and mdam packages because I didn't think I needed them. Lvm2 is the large volume manager and mdam was the package that handles raid I think. Could that be the reason?
Offline
LVM2=logical volume manager, I thought it was large volume manager. I'm thinking this is what's not letting me boot, me deleting this package. But how can I re-add this package when I can't boot into the system at all???
Offline
I had the same problem when I complied 2.6.32-7 manually. I just went back to -5
Offline
How can I go back???
Offline
Have you tried pacman -S lvm2?
Last edited by SBL (2010-02-03 08:20:59)
Any sufficiently advanced technology is indistinguishable from magic.
Offline
Can you mount your drive with the live medium? I always check for hardware issues before anything else just in case. If you can mount it, you should be able to fix the issue with a chroot and the appropriate commands. The wiki will be your friend here more than I can though. I'm sure someone else would be able to tell you exactly what to do but I can point you the the page: http://wiki.archlinux.org/index.php/Chroot
Offline
Just a tip, but -if you have one- what's the content of /boot/grub/menu.lst ?
Offline
Yes, you are totally right.
But how was he able to post his /etc/fstab, if he can't see the partitions ? So I thought maybe he can post his menu.lst too..
Anyway, sorry if I misunderstood something.
Offline
I'm using a mint Linux livecd that's how I mount the disks. I honestly don't think there's anything wrong with the disks. I did a ls -l /'dev/disks/by-uuid in mint and all the disks are there.
Offline
From the livecd, mount the root filesystem under /mnt. Then do "mount --bind /dev /mnt/dev" and finally "chroot /mnt". You should now be inside your arch system, and able to run "pacman -S lvm mdadm".
Offline
How do I mount the root file system? "mount /dev/sda3 /mnt" something like that?
Did that, it says pacman command not found. Probably because I've split my filesystem into different partitions. Would Pacman be under /usr which is sda7 for me.
Last edited by leberyo (2010-02-03 20:37:00)
Offline
I remounted my different partitions and was able to re-install lvm2 and mdadm. I still get the same boot error. I've read elsewhere that the new udev is the problem. How can I restore the previous udev?
Last edited by leberyo (2010-02-03 20:46:33)
Offline
Wow this is becoming painful. Tried to install the old udev that's in my pacman cache, it now gives me another error;
error: failed to prepare transaction (conflicting files)
udev: /lib/udev/rules.d/64-md-raid.rules exist in filesystem
....no packages were upgraded
How can I fix this?
You fix by also downgrading mdadm package. Downgraded both mdadm and udev to one prior versions and still the same boot error..
Last edited by leberyo (2010-02-03 20:58:51)
Offline
Downgraded kernel, udev, mdadm still boot error !!!
Offline
Wow this is becoming painful. Tried to install the old udev that's in my pacman cache, it now gives me another error;
error: failed to prepare transaction (conflicting files)
udev: /lib/udev/rules.d/64-md-raid.rules exist in filesystem....no packages were upgraded
How can I fix this?
You fix by also downgrading mdadm package. Downgraded both mdadm and udev to one prior versions and still the same boot error..
pacman's -f option will force the install in this case.
Offline
try modules="... ext3 ext4" in /etc/mkinitcpio (line 7) and
mkinitcpio -p kernel26
Offline