Bug#698215: linux-image-3.2.0-4-amd64: Grub fails loading with cannot read the linux header
Package: src:linux Version: 3.2.35-2 Severity: important Hi everybody, I'm rather clueless on this error. Grub refuses to boot the current Wheezy kernel on this box. The message is cannot read the linux header. 3.2.0-3-amd64 boots without problems. I reinstalled the kernel package as well as grub-pc and ran update-grub without problems. debsums -sa does not report any modified files for the kernel package or any grub package installed. So I'm a bit clueless. The box is an rather old Intel Core2 6300 box. Could that be the problem? Could this kernel be incompatible with the processor? Cheers, Christopher -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: product_name: product_version: chassis_vendor: chassis_version: bios_vendor: Intel Corp. bios_version: MQ96510J.86A.1458.2006.1017.1151 board_vendor: Intel Corporation board_name: DG965MQ board_version: AAD37419-302 ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 82P965/G965 Memory Controller Hub [8086:29a0] (rev 02) Subsystem: Intel Corporation Device [8086:514d] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 0 Capabilities: access denied Kernel driver in use: agpgart-intel 00:01.0 PCI bridge [0604]: Intel Corporation 82P965/G965 PCI Express Root Port [8086:29a1] (rev 02) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 Memory behind bridge: e050-e05f Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: access denied Kernel driver in use: pcieport 00:02.0 VGA compatible controller [0300]: Intel Corporation 82G965 Integrated Graphics Controller [8086:29a2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:514d] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 48 Region 0: Memory at e030 (32-bit, non-prefetchable) [size=1M] Region 2: Memory at d000 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at 2110 [size=8] Expansion ROM at unassigned [disabled] Capabilities: access denied Kernel driver in use: i915 00:02.1 Display controller [0380]: Intel Corporation 82G965 Integrated Graphics Controller [8086:29a3] (rev 02) Subsystem: Intel Corporation Device [8086:514d] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Region 0: Memory at e020 (32-bit, non-prefetchable) [size=1M] Capabilities: access denied 00:03.0 Communication controller [0780]: Intel Corporation 82P965/G965 HECI Controller [8086:29a4] (rev 02) Subsystem: Intel Corporation Device [8086:514d] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 11 Region 0: Memory at e0426100 (64-bit, non-prefetchable) [size=16] Capabilities: access denied 00:19.0 Ethernet controller [0200]: Intel Corporation 82566DC Gigabit Network Connection [8086:104b] (rev 02) Subsystem: Intel Corporation Device [8086:0001] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 46 Region 0: Memory at e040 (32-bit, non-prefetchable) [size=128K] Region 1: Memory at e0424000 (32-bit, non-prefetchable) [size=4K] Region 2: I/O ports at 20e0 [size=32] Capabilities: access denied Kernel driver in use: e1000e 00:1a.0 USB controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 [8086:2834] (rev
Bug#698215: linux-image-3.2.0-4-amd64: Grub fails loading with cannot read the linux header
Control: reassign -1 grub-pc 1.99-26 Control: tag -1 moreinfo On Tue, 2013-01-15 at 11:51 +0100, Christopher Huhn, GSI wrote: Package: src:linux Version: 3.2.35-2 Severity: important Hi everybody, I'm rather clueless on this error. Grub refuses to boot the current Wheezy kernel on this box. The message is cannot read the linux header. 3.2.0-3-amd64 boots without problems. I reinstalled the kernel package as well as grub-pc and ran update-grub without problems. debsums -sa does not report any modified files for the kernel package or any grub package installed. So I'm a bit clueless. The box is an rather old Intel Core2 6300 box. Could that be the problem? Could this kernel be incompatible with the processor? [...] This is Debian - we carry on supporting hardware until it's turned to rust (well almost). Anyway if GRUB is complaining then the kernel isn't running yet, is it? I'm reassigning this in the hope that GRUB maintainers can debug it. However, the bug reporting instructions for GRUB say: MAKE SURE YOU ARE RUNNING THE LATEST VERSION The grub packages never update the installed version of GRUB automatically, except if you choose a device in the debconf prompt `GRUB install devices', which is currently only implemented for grub-pc. Because of this, you need to make sure you're running the LATEST VERSION of GRUB before you report a bug. Use grub-install to update it, and then check if the bug still applies. Debugging problems we already fixed makes us waste valuable time, so please try to avoid it. They will also want to know: 1. The contents of /proc/mounts, /boot/grub/device.map, and /proc/mdstat (if present) 2. Listings (ls -l) of /dev/disk/by-id and /dev/disk/by-uuid 3. Output of 'debconf-show grub-pc' Ben. -- Ben Hutchings Quantity is no substitute for quality, but it's the only one we've got. signature.asc Description: This is a digitally signed message part
Bug#698215: linux-image-3.2.0-4-amd64: Grub fails loading with cannot read the linux header
Hi, On 15.01.2013 14:26, Ben Hutchings wrote: This is Debian - we carry on supporting hardware until it's turned to rust (well almost). Anyway if GRUB is complaining then the kernel isn't running yet, is it? No, it was not. Because of this, you need to make sure you're running the LATEST VERSION of GRUB before you report a bug. Use grub-install to update it, and then check if the bug still applies. Debugging problems we already fixed makes us waste valuable time, so please try to avoid it. This exactly was not the case - and fixed my problem. Shame on me. I still think it's strange that the old grub could run 3.2.0-3 but not 3.2.0-4. That's why the kernel was my first suspect. Unfortunately this means that I may have to update grub with each release (or kernel?) upgrade on a couple of servers (~ 1000), automatically choosing the proper boot device, which is normally handled for me by FAI at install time and may be cumbersome eg. for software RAIDs. Please close this bug. Sorry for the inconvenience. Kind regards, Christopher smime.p7s Description: S/MIME Cryptographic Signature
Bug#698215: linux-image-3.2.0-4-amd64: Grub fails loading with cannot read the linux header
On Tue, 2013-01-15 at 15:40 +0100, Christopher Huhn wrote: Hi, On 15.01.2013 14:26, Ben Hutchings wrote: This is Debian - we carry on supporting hardware until it's turned to rust (well almost). Anyway if GRUB is complaining then the kernel isn't running yet, is it? No, it was not. Because of this, you need to make sure you're running the LATEST VERSION of GRUB before you report a bug. Use grub-install to update it, and then check if the bug still applies. Debugging problems we already fixed makes us waste valuable time, so please try to avoid it. This exactly was not the case - and fixed my problem. Shame on me. I still think it's strange that the old grub could run 3.2.0-3 but not 3.2.0-4. That's why the kernel was my first suspect. Unfortunately this means that I may have to update grub with each release (or kernel?) upgrade on a couple of servers (~ 1000), automatically choosing the proper boot device, which is normally handled for me by FAI at install time and may be cumbersome eg. for software RAIDs. This should be remembered by debconf (grub-pc/install_devices variable). I'm not sure whether there's a good way to get that information outside of a package maintainer script, though. Please close this bug. Sorry for the inconvenience. Well, if this is a widespread problem then I think grub-pc must reinstall when the package is upgraded from a version has this bug. We cannot have upgrades resulting in an unbootable system. Were these systems initially installed with squeeze, or an earlier version? Ben. -- Ben Hutchings Quantity is no substitute for quality, but it's the only one we've got. signature.asc Description: This is a digitally signed message part
Bug#698215: linux-image-3.2.0-4-amd64: Grub fails loading with cannot read the linux header
On Tue, Jan 15, 2013 at 03:40:49PM +0100, Christopher Huhn wrote: Unfortunately this means that I may have to update grub with each release (or kernel?) upgrade on a couple of servers (~ 1000), automatically choosing the proper boot device, By default, grub-pc auto-reinstalls itself. Perhaps it's installing to the wrong place; use 'dpkg-reconfigure grub-pc' to change that. which is normally handled for me by FAI at install time and may be cumbersome eg. for software RAIDs. It's entirely possible that FAI fails to tell the grub-pc packaging where to install GRUB in future. -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698215: linux-image-3.2.0-4-amd64: Grub fails loading with cannot read the linux header
Unfortunately this means that I may have to update grub with each release (or kernel?) upgrade on a couple of servers (~ 1000), automatically choosing the proper boot device, which is normally handled for me by FAI at install time and may be cumbersome eg. for software RAIDs. This should be remembered by debconf (grub-pc/install_devices variable). I'm not sure whether there's a good way to get that information outside of a package maintainer script, though. 'debconf-get-selections | grep grub-pc/install_devices' ? Unfortunately this is not/set used by FAI, at least not by the scripts we use which may not be up to date. Please close this bug. Sorry for the inconvenience. Well, if this is a widespread problem then I think grub-pc must reinstall when the package is upgraded from a version has this bug. We cannot have upgrades resulting in an unbootable system. Were these systems initially installed with squeeze, or an earlier version? According to the FAI logs this machine has been (re)installed with Squeeze roughly a year ago. The installed grub version was 1.98+20100804-14+squeeze1. I have only observed the problem on this particular box, but I did not do many Wheezy upgrades until now. Cheers, Christopher smime.p7s Description: S/MIME Cryptographic Signature
Bug#698215: linux-image-3.2.0-4-amd64: Grub fails loading with cannot read the linux header
On Tue, Jan 15, 2013 at 04:43:51PM +0100, Christopher Huhn wrote: 'debconf-get-selections | grep grub-pc/install_devices' ? Yes. Unfortunately this is not/set used by FAI, at least not by the scripts we use which may not be up to date. In that case this is a dangerous bug in FAI (or your scripts) which needs to be fixed. grub-pc has no practical way to work around this as some people set this situation up intentionally. -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698215: linux-image-3.2.0-4-amd64: Grub fails loading with cannot read the linux header
Unfortunately this is not/set used by FAI, at least not by the scripts we use which may not be up to date. In that case this is a dangerous bug in FAI (or your scripts) which needs to be fixed. grub-pc has no practical way to work around this as some people set this situation up intentionally. The relevant code is here: https://github.com/faiproject/fai/blob/master/examples/simple/scripts/GRUB_PC/10-setup I assume that everyone starts his FAI config from this example script. So the solution would be to preseed the boot_device via debconf-set-selection and dpkg-reconfigure grub-pc afterwards? Cheers, Christopher smime.p7s Description: S/MIME Cryptographic Signature
