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

Bug#396483: d-i testing image 31Oct06 on amd64 failed on reboot



Hi Frans

I've repeated the install with the same result on reboot.  Below I've
attempted to provide some more information but as a mere aspiring geek
rather than the real McCoy, I fear it's not as much as you would like.
If you give me a little more guidance I can still get into the install
which I've left in its current state.

Incidentally, I've installed using the debian on this laptop from the
testing netinst.iso from 31/7/06 and varius other images without ever
encountering this problem.  Both grml and ubuntu edgy have been
installed within the last few days.

On (01/11/06 10:24), Clive Menzies wrote:
> On (01/11/06 06:32), Frans Pop wrote:
> > 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 ouput of lspci includes:
00:0.1 IDE interfaces Via Technologies etc
and there's only the one

> > 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/.
> 
> No it just hangs - needs the power button to recover

I booted with the install disk mounted /hda13 and chrooted into it
cat /proc/modules didn't show 'no such device' or something like that

the devices are listed OK including /dev/hda13

> > 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?
> 
> I think so; I installed grml immediately afterwards on the same
> partition and that rebooted without a hitch.  So there is the
> possibility the inconsistency righted itself; a repeat attempt with d-i
> will reveal more.

This time /hda13 showed up as ext3 before the install and I formatted it
as such.

> > If you need to fix anything (like manually include a module in the 
> > initrd), use the installer's rescue mode.
> 
> I'll try that (if I can get my head around what to do :))

Including a module in the initrd was a bit beyond my competence and
knowledge but if you can give me an idiot's guide, I'll do what I can :)

I hope this is of some use.

Regards

Clive

-- 
www.clivemenzies.co.uk ...
...strategies for business





Reply to: