Bug#396483: d-i testing image 31Oct06 on amd64 failed on reboot
Hello Clive,
On Wednesday 01 November 2006 01:16, Clive Menzies wrote:
> Comments/Problems:
> VFS Cannot open root device "hda13" or unknown-block(0,0)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VVVFS Unable to mount root fs on
> unknown-block(0,0)
In general that means that the initrd fails to load the drivers needed to
access the hard disk, OR, if there are multiple disk controllers in the
system, that device names are assigned differently during the boot than
during the installation.
The messages you show here are insufficient to diagnose this. You'll need
to look back to check:
- is the driver needed for your disk controller being loaded
- is the disk recognized
- as what is it recognized
- are the partitions seen
Are you dropped into a debug shell when the failure occurs? If you are,
check if the modules needed are loaded (cat /proc/modules), check if the
disk devices are listed in /dev/.
> I should mention that this was previously a PV in an LVM setup. I'd
> already removed the partition from the VG and formatted it (I thought)
> as ext3 but the d-i read it as type LVM; so I formatted it again as
> ext3 during the install.
Hmm. Did you also remove the LVM metadata from it? That could have
something to do with it, though I doubt it.
Any messages in the scrollback on the console related to LVM?
If you need to fix anything (like manually include a module in the
initrd), use the installer's rescue mode.
Cheers,
FJP
Reply to: