You are not logged in.
Does it have to do with systems?
Here's a screenshot of the error:
http://x.iaesr.com/~/img/Arch/booterror.jpg
joe@trusktr.io - joe at true skater dot io.
Offline
Offline
If you use labels in fstab, it caused me issues.
Offline
@barko So just to double check: I should mount only / and /boot the chroot? Then after using fdisk I mkinitcpio will automatically compile into my root? (I'm new to chroot).
@ImNtReal I'm using UUIDs in fstab. Hmmm...
joe@trusktr.io - joe at true skater dot io.
Offline
Ok, here we go:
1) boot from CD downloaded from here
2) fdisk -l (you will see partitions, check them for root and boot)
After that do this:
mkdir /mnt/arch
mount /dev/sdaX /mnt/arch
cd /mnt/arch
mount /dev/sdaY boot/
mount -t proc proc proc/
mount -t sysfs sys sys/
mount -o bind /dev dev/
chroot /mnt/arch /bin/bashAnd when you are in chroot, run this:
mkinitcpio -p linuxReboot and you will be ok. ![]()
Last edited by barko (2012-06-05 17:39:26)
Offline
Thanks @barko. I'll try it when I get home... I also have another system that hasn't been updated yet. How do I update it and make sure this doesn't happen? On the system that is messed up, I tried the 'mkinitcpio...' command like the news says to do on the Arch homepage, but that obviously didn't work.
I think pacman should have some special mechanism of retrieving info on which packages to upgrade first or in which order... That way whenever a system update happens, pacman will automatically upgrade those packages in order and output a special message at the end of upgrade if more steps are needed.
joe@trusktr.io - joe at true skater dot io.
Offline
EDIT: Question already answered.
Last edited by ANOKNUSA (2012-06-05 17:53:18)
Offline