[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#297232: kernel-image-2.6.10-1-k7: kernel panic on boot, now all installed kernels fail (backup recovery required)



Package: kernel-image
Version: 2.6.10-1-k7

Hello everyone,

After installing kernel-image-2.6.10-1-k7, i tried to reboot, but the following
error occurs:

  pivot_root: No such file or directory
  /sbin/init: 431: cannot open dev/console: No such file
  kernel panic: Attempted to kill init!

The serious thing: after rebooting, i tried to boot the old kernel-image-2.6.8-2-686
(still the one from base-install), which now fails with the same error!
In a nutshell: i cannot boot anymore and need to restore my system backup!

After booting a rescue system, i found pivot_root in /mnt/hda1/sbin and console
in /mnt/hda1/dev, where /mnt/hda1 is the root partition of the system in question,
so the files are indeed present, but the kernel somehow couldn't find them.

I've already read something similar somewhere, but can't remember where.
Perhaps my hardware/software report might help. I have installed the same
system (same package versions etc.) on a second machine (little older, other
mainboard), where 2.6.10-1-k7 runs fine.

The machine in question is equipped with an ASUS A7N8X-Deluxe mainboard,
CPU is Athlon-XP, chipset is nForce2, including a SiliconImage SATA controller.
Graphics device is a GeForce4 (MSI TI-4200). No further cards, all pci slots are empty.

The installed system is Debian-unstable, all packages up-to-date, as of 2005-2-28.
I have not installed any kernel module yet, my /usr/src directory still contains nothing.

Linux is installed on a normal IDE harddisk, and a second harddisk is SATA,
where a Win32 and my backup system (Knoppix) is installed on. All Linux patritions
are formatted with ext3. None of the SATA partitions is mounted at Debian boot (with
the 'auto' mount option in /etc/fstab), because fsck always fails on them, even with
kernel-image-2.6.8-2-686, but this is another topic. I can live with mounting them later,
which works fine because the SiliconImage SATA driver is loaded/initialized somewhen
later - after fsck..

If i may help, i'll do what i can.

Regards,

Oliver 'Bloody' Lange.





Reply to: