You are not logged in.
Pages: 1
I have restored an Arch Linux Backup on a newly partitioned drive, which has different partitions than before. However, it will not boot. I get a kernel panic.
For a while, it said:
Mounted root (ext3 filesystem) readonly.
kinit: init not found!
Kernel panic - not syncing: Attempting to kill init!
Now, it says:
Mounted root (ext3 filesystem) readonly.
kinit: console not found!
Kernel panic - not syncing: Attempting to kill init!
/etc/mtab
/dev/sda7 / ext3 rw 0 0
none /dev ramfs rw 0 0
none /proc proc rw 0 0
none /sys sysfs rw 0 0
none /proc/bus/usb usbfs rw 0 0
none /dev/pts devpts rw 0 0
none /dev/shm tmpfs rw 0 0
/dev/sda6 /boot ext3 rw 0 0
/dev/sda8 /home ext3 rw 0 0
gvfs-fuse-daemon /home/sorin/.gvfs fuse.gvfs-fuse-daemon rw,nosuid,nodev,user=s$
none /proc/fs/vmblock/mountPoint vmblock rw 0 0/etc/fstab
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <$
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 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
/dev/sda5 swap swap defaults 0 0
/dev/sda6 /boot ext3 defaults 0 1
/dev/sda7 / ext3 defaults 0 1
/dev/sda8 /home ext3 defaults 0 1
sshfs#backup@saturnus:/home/backup/mercurius/arch-linux /var/backup fuse default/boot/grub/menu.lst
# Config file for GRUB - The GNU GRand Unified Bootloader
# /boot/grub/menu.lst
# DEVICE NAME CONVERSIONS
#
# Linux Grub
# -------------------------
# /dev/fd0 (fd0)
# /dev/hda (hd0)
# /dev/hdb2 (hd1,1)
# /dev/hda3 (hd0,2)
#
# FRAMEBUFFER RESOLUTION SETTINGS
# +-------------------------------------------------+
# | 640x480 800x600 1024x768 1280x1024
# ----+--------------------------------------------
# 256 | 0x301=769 0x303=771 0x305=773 0x307=775
# 32K | 0x310=784 0x313=787 0x316=790 0x319=793
# 64K | 0x311=785 0x314=788 0x317=791 0x31A=794
# 16M | 0x312=786 0x315=789 0x318=792 0x31B=795
# +-------------------------------------------------+
# general configuration:
timeout 5
default 0
color light-blue/black light-cyan/blue
# boot sections follow
# each is implicitly numbered from 0 in the order of appearance below
#
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
#
#-*
# (0) Arch Linux
title Arch Linux
root (hd0,5)
kernel /vmlinuz26 root=/dev/sda7 ro intel-wireless vga=792
initrd /kernel26.img
# (1) Arch Linux
title Arch Linux Fallback
root (hd0,5)
kernel /vmlinuz26 root=/dev/sda7 ro
initrd /kernel26-fallback.img
# (1) Windows
#title Windows
#rootnoverify (hd0,0)
#makeactive
#chainloader +1/boot/grub/device.map
(fd0) /dev/fd0
(hd0) /dev/sdaLast edited by SpookyET (2008-05-09 21:16:17)
Offline
In you menu.lst you are telling the kernel that the root (/) is on /dev/sda6 but /etc/mtab shows it to be on /dev/sda7, try changing the kernel line to
kernel /vmlinuz26 root=/dev/sda7 ro intel-wireless vga=792Also, I don't think you need 'intel-wireless' in there on an installed system.
Offline
In you menu.lst you are telling the kernel that the root (/) is on /dev/sda6 but /etc/mtab shows it to be on /dev/sda7, try changing the kernel line to
kernel /vmlinuz26 root=/dev/sda7 ro intel-wireless vga=792Also, I don't think you need 'intel-wireless' in there on an installed system.
I fixed that. It's an old paste. Still the same issue.
Offline
Is the /etc/mtab you posted from the backup image? If so can you also post the partition scheme you have on the new disk?
Offline
Is the /etc/mtab you posted from the backup image? If so can you also post the partition scheme you have on the new disk?
No, it's not from the backup image. I had to fix fstab and mtab in order for the "grub-install" command to work. Grub was installed successfully, and it attempts to boot until I get the kinit problem.
Offline
Fixed. Most backup tutorials and articles tell you to not back up dev. dev is not fully recreated. It's pseudo ramfs.
You must back up:
/dev/console
/dev/null
/dev/zero
Your snapshot will not boot without those files.
Offline
Mounted root (ext3 filesystem) readonly.
kinit: console not found!
Kernel panic - not syncing: Attempting to kill init!
I think this means that your new disk is missing the console device node. If you boot a cd, mount the drive (eg /mnt/dik) and then
mkdir /mnt/disk/dev
mknod -m 600 /mnt/disk/dev/console c 5 1
mknod -m 666 /mnt/disk/dev/null c 1 3(source)
EDIT: you beat me to it
Last edited by ghostHack (2008-05-09 21:17:47)
Offline
Pages: 1