Your message dated Thu, 02 Nov 2006 00:10:29 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#396483: d-i testing image 31Oct06 on amd64 failed on reboot
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
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 * 256 1537 10297665 c W95 FAT32
(LBA)
/dev/hda3 1538 7296 46259167+ f W95 Ext'd
(LBA)
/dev/hda5 1538 2072 4297356 c W95 FAT32
(LBA)
/dev/hda6 3648 4285 5124703+ 8e Linux LVM
/dev/hda7 4286 4407 979933+ 82 Linux swap /
Solaris
/dev/hda8 4408 6328 15430401 8e Linux LVM
/dev/hda9 6329 7296 7775428+ 83 Linux
/dev/hda10 2073 2078 48163+ 83 Linux
/dev/hda11 2079 2139 489951 8e Linux LVM
/dev/hda12 2140 2309 1365493+ 82 Linux swap /
Solaris
/dev/hda13 2691 3282 4755208+ 83 Linux
/dev/hda14 3283 3647 2931862 83 Linux
/dev/hda15 2310 2690 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. VT82xxxxx UHCI USB
1.1 Controller [1106:3038] (rev 80)
00:10.1 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB
1.1 Controller [1106:3038] (rev 80)
00:10.2 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx 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 recognise /dev/hda13
as root.
Here's the last three lines of the boot messages:
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)
Here's the relevant entry from the grub/menu.lst:
root (hd0,12)
kernel /vmlinuz root=/dev/hda13 ro
savedefault
boot
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.
Regards
Clive
--
www.clivemenzies.co.uk ...
...strategies for business
--- End Message ---
--- Begin Message ---
On Wednesday 01 November 2006 22:53, Clive Menzies wrote:
> 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.
After getting some expert advice the cause seems to be simple.
Could it be you've forgotten to add an "initrd" line in your
/boot/grub/menu.lst? The default Debian kernels need to be booted from an
initrd.
As I trust my advisor in this, I'm closing this report. If this is not the
cause, please reply and we'll reopen.
Cheers,
FJP
--- End Message ---
