You are not logged in.
Pages: 1
Hello Archers,
This is my first installation of Arch. The system was up, until a recent update (pacman -Syu). Now I get the following error at boot:
root (hd0,0)
Filesystem type is ext2fs, partition type 0x83
kernal /vmlinuz_linux root=/dev/disk/by-uuid/32fb...
Error 15: File not found
I used Arches autopartition function, to the root partition is sda3, the boot partition is sda1. The uuid in the root= line points to sda3, which is a jfs filesystem.
I've tried editing the grub/menu.lst file, trying different root partitions. None allow arch to boot. There is an sdb partition with a Windows recovery OS.
Any ideas?
Thank you in advance for helping.
Last edited by kjonas (2012-03-22 21:00:37)
Offline
Just to get some obvious things out of the way, the line should say
kernel /vmlinuz-linux <blah blah blah>
- you have a typo or two there.
Did you check if you do have the needed files in your /boot?
Offline
Thank you for your reply karol. You're right in pointing out that I've made some transcription errors. Those are not in the original error. I've run:
# find /boot -name 'vmlinuz-linux'
# find / -name 'vmlinuz-linux'
Nothing turns up. Right now the system is running from a usb drive. Is the answer so simple as to be that I somehow deleted this file?
Last edited by kjonas (2012-03-18 02:22:56)
Offline
More likely /boot wasn't mounted when you did the update.
Chroot into your system, make sure to mount /boot and regenerate the kernel image.
Offline
Do you want to chroot into the system first, then mount and regenerate the kernal? I've read the chroot section of the wiki, as well as a few how tos, but it's still not quite clear what Chroot does. Am I sort of breaking into my own system? Why does the wiki instruct you to make a new directory before mounting?
Thanks for your advice.
Offline
chroot first, then run mkinitcpio.
You don't have to create a new directory if you already have one that suits you. You simply have to mount the device somewhere, the mountpoint has to exist.
If you want more info wrt to what chroot is, try googling around e.g. http://webcache.googleusercontent.com/s … pl&client=
Offline
Okay. So I ran
mount /dev/sda1 /mnt/boot and got the error: /mnt/boot does not exist.
So then
mkdir /mnt/boot
mount /dev/sda1 /mnt/boot
mkinitcpioWhich returns
==> ERROR: '/lib/modules/3.0-Arch' is not a valid kernel directory.
Does that mean I should mount the root directory instead? When I try, there's an error because it is a jfs file system.
Offline
P.S. thanks for the link, it is really helpful.
Offline
For anyone who might run into a similar problem, here is the code I used to mount the /boot partition and regenerate the kernal;
mount /dev/sda3 /mnt ##mounts the /root partition
mount /dev/sda1 /mnt/boot ##mounts /boot
mount -t proc none /mnt/proc ##brings over any processes necessary, none are needed
mount -t sysfs none /mnt/sys ##brings over system files, non needed
mount --bind /dev /mnt/dev
chroot /mnt ##changes root to the mounted partition
pacman -S util-linux-ng
pacman -Syu linux
mkinitcpio -p linux
umount /-f /mnt ## unmount the partition
rebootOffline
Pages: 1