Bug#396483: d-i testing image 31Oct06 on amd64 failed on reboot
Hi Frans On (01/11/06 06:32), Frans Pop wrote: 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. Being a laptop, multiple disk controllers are unlikely, so I'll repeat the install and try to get you more info 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 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? 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. 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 :)) Regards Clive -- www.clivemenzies.co.uk ... ...strategies for business -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#396483: d-i testing image 31Oct06 on amd64 failed on reboot
Package: installation-reports Boot method: CD Image version: http://www.debian.org/devel/debian-installer/amd64/debian-testing-amd64-netinst.iso Date: 23:15 (GMT) 31 0ct 06 Machine: Acer Aspire 1524WLMi Processor: amd athlon 64 / 3400+ Memory:512Mb Partitions: Disk /dev/hda: 60.0 GB, 60011642880 bytes 255 heads, 63 sectors/track, 7296 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 1 255 2048256 12 Compaq diagnostics /dev/hda2 * 256153710297665c W95 FAT32 (LBA) /dev/hda31538729646259167+ f W95 Ext'd (LBA) /dev/hda515382072 4297356c W95 FAT32 (LBA) /dev/hda636484285 5124703+ 8e Linux LVM /dev/hda742864407 979933+ 82 Linux swap / Solaris /dev/hda84408632815430401 8e Linux LVM /dev/hda963297296 7775428+ 83 Linux /dev/hda10 20732078 48163+ 83 Linux /dev/hda11 20792139 489951 8e Linux LVM /dev/hda12 21402309 1365493+ 82 Linux swap / Solaris /dev/hda13 26913282 4755208+ 83 Linux /dev/hda14 32833647 2931862 83 Linux /dev/hda15 23102690 3060351 83 Linux Partition table entries are not in disk order Test install is on /dev/hda13 Output of lspci -nn and lspci -vnn: [EMAIL PROTECTED]:~$ lspci -nn 00:00.0 Host bridge [0600]: VIA Technologies, Inc. K8M800 Host Bridge [1106:0204] 00:00.1 Host bridge [0600]: VIA Technologies, Inc. K8M800 Host Bridge [1106:1204] 00:00.2 Host bridge [0600]: VIA Technologies, Inc. K8M800 Host Bridge [1106:2204] 00:00.3 Host bridge [0600]: VIA Technologies, Inc. K8M800 Host Bridge [1106:3204] 00:00.4 Host bridge [0600]: VIA Technologies, Inc. K8M800 Host Bridge [1106:4204] 00:00.7 Host bridge [0600]: VIA Technologies, Inc. K8M800 Host Bridge [1106:7204] 00:01.0 PCI bridge [0604]: VIA Technologies, Inc. VT8237 PCI bridge [K8T800/K8T890 South] [1106:b188] 00:0a.0 Ethernet controller [0200]: Linksys, A Division of Cisco Systems [AirConn] INPROCOMM IPN 2220 Wireless LAN Adapter (rev 01) [17fe:2220] 00:0b.0 CardBus bridge [0607]: Texas Instruments PCI7420 CardBus Controller [104c:ac8e] 00:0b.1 CardBus bridge [0607]: Texas Instruments PCI7420 CardBus Controller [104c:ac8e] 00:0b.2 FireWire (IEEE 1394) [0c00]: Texas Instruments PCI7x20 1394a-2000 OHCI Two-Port PHY/Link-Layer Controller [104c:802e] 00:0c.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet [10ec:8169] (rev 10) 00:10.0 USB Controller [0c03]: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller [1106:3038] (rev 80) 00:10.1 USB Controller [0c03]: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller [1106:3038] (rev 80) 00:10.2 USB Controller [0c03]: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller [1106:3038] (rev 80) 00:10.3 USB Controller [0c03]: VIA Technologies, Inc. USB 2.0 [1106:3104] (rev 82) 00:11.0 ISA bridge [0601]: VIA Technologies, Inc. VT8235 ISA Bridge [1106:3177] 00:11.1 IDE interface [0101]: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571] (rev 06) 00:11.5 Multimedia audio controller [0401]: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller [1106:3059] (rev 50) 00:11.6 Communication controller [0780]: VIA Technologies, Inc. AC'97 Modem Controller [1106:3068] (rev 80) 00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration [1022:1100] 00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map [1022:1101] 00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller [1022:1102] 00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control [1022:1103] 01:00.0 VGA compatible controller [0300]: nVidia Corporation NV36 [GeForce FX Go5700] [10de:0347] (rev a1) $ lspci -vnn //attached as file lspci-vnn Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [o] Detect network card:[o] Configure network: [o] Detect CD: [o] Load installer modules: [o] Detect hard drives: [o] Partition hard drives: [o] Install base system:[o] Clock/timezone setup: [o] User/password setup:[o] Install tasks: [o] Install boot loader:[ ] Overall install:[E] Comments/Problems: I aborted the grub install as this is one of several systems on this box and I maintain grub from my production system; I chose to proceed without a bootloader. The install was very slick up to the reboot - the system seemed to find the kernel to boot but didn't
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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
