In this case /boot is in the /-Filesystem which itself is into LVM:
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Debian GNU/Linux, with Linux 3.1.0-1-amd64' --class debian --class gnu-linux --class gnu --class os {
load_video
set gfxpayload=keep
insmod gzio
insmod lvm
insmod part_msdos
insmod xfs
set root='(vg0-root)'
search --no-floppy --fs-uuid --set=root af14a1aa-52e2-4a95-8d49-733722fe7949
echo 'Loading Linux 3.1.0-1-amd64 ...'
linux /boot/vmlinuz-3.1.0-1-amd64 root=/dev/mapper/vg0-root ro rootdelay=9
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.1.0-1-amd64
}
-- Package-specific info:
** Kernel log: boot messages should be attached
** Model information
sys_vendor: LENOVO
product_name: 20555WG
product_version: ThinkPad T500
chassis_vendor: LENOVO
chassis_version: Not Available
bios_vendor: LENOVO
bios_version: 6FET56WW (2.02 )
board_vendor: LENOVO
board_name: 20555WG
board_version: Not Available
15:00.4 System peripheral [0880]: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter [1180:0592] (rev 11)
Subsystem: Lenovo ThinkPad T61 [17aa:20ca]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 32, Cache Line Size: 64 bytes
Interrupt: pin C routed to IRQ 18
Region 0: Memory at f4802000 (32-bit, non-prefetchable) [size=256]
Capabilities: <access denied>
Kernel driver in use: r592
15:00.5 System peripheral [0880]: Ricoh Co Ltd xD-Picture Card Controller [1180:0852] (rev 11)
Subsystem: Lenovo Device [17aa:20cb]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 32, Cache Line Size: 64 bytes
Interrupt: pin C routed to IRQ 18
Region 0: Memory at f4802400 (32-bit, non-prefetchable) [size=256]
Capabilities: <access denied>
Kernel driver in use: r852
** USB devices:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 17ef:4807 Lenovo UVC Camera
Bus 002 Device 002: ID 0bdb:1900 Ericsson Business Mobile Networks BV F3507g Mobile Broadband Module
Bus 004 Device 002: ID 08ff:2810 AuthenTec, Inc. AES2810
Bus 004 Device 003: ID 0a5c:2145 Broadcom Corp. Bluetooth with Enhanced Data Rate II
Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages linux-image-3.1.0-1-amd64 depends on:
ii debconf [debconf-2.0] 1.5.40
ii initramfs-tools [linux-initramfs-tool] 0.99
ii linux-base 3.3
ii module-init-tools 3.16-1
Versions of packages linux-image-3.1.0-1-amd64 recommends:
ii firmware-linux-free 3
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20111122065448.3492.18287.reportbug@excelsior.lab. swapon.de">http://lists.debian.org/20111122065448.3492.18287.reportbug@excelsior.lab. swapon.de
Wait, not ok at all. Do you have a bootloader installed?
Thanks for writing,
Jonathan
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20111122074051.GA17478@elie.hsd1.il.comcast.net">h ttp://lists.debian.org/20111122074051.GA17478@elie.hsd1.il.comcast.net
> > Loading Linux 3.1.0-1-amd64 ...
> > Loading initial ramdisk ...
> > error: couldn't read file.
> [...]
> > load_video
> > set gfxpayload=keep
> > insmod gzio
> > insmod lvm
> > insmod part_msdos
> > insmod xfs
> > set root='(vg0-root)'
> > search --no-floppy --fs-uuid --set=root af14a1aa-52e2-4a95-8d49-733722fe7949
> > echo 'Loading Linux 3.1.0-1-amd64 ...'
> > linux /boot/vmlinuz-3.1.0-1-amd64 root=/dev/mapper/vg0-root ro rootdelay=9
> > echo 'Loading initial ramdisk ...'
> > initrd /boot/initrd.img-3.1.0-1-amd64
>
> Looks ok...
>
> [...]
> > pn grub-pc 1.99-12
>
> Wait, not ok at all. Do you have a bootloader installed?
>
> Thanks for writing,
> Jonathan
I have booted Kernel 3.0.0-1-amd64 again, which works. No clue why reportbug
shows grub-pc as purged. When I query with dpkg everything looks fine:
$ dpkg -l "grub*"
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Description
+++-=====================================-=====================================-================================================== ========================================
un grub <none> (no description available)
ii grub-common 1.99-12 GRand Unified Bootloader (common files)
un grub-coreboot <none> (no description available)
un grub-doc <none> (no description available)
un grub-efi <none> (no description available)
un grub-efi-amd64 <none> (no description available)
un grub-efi-ia32 <none> (no description available)
un grub-emu <none> (no description available)
un grub-ieee1275 <none> (no description available)
un grub-legacy <none> (no description available)
un grub-legacy-doc <none> (no description available)
un grub-linuxbios <none> (no description available)
ii grub-pc 1.99-12 GRand Unified Bootloader, version 2 (PC/BIOS version)
ii grub-pc-bin 1.99-12 GRand Unified Bootloader, version 2 (PC/BIOS binaries)
un grub-yeeloong <none> (no description available)
un grub2 <none> (no description available)
ii grub2-common 1.99-12 GRand Unified Bootloader (common files for version 2)
Again, I can boot with kernel 3.0.0-1-amd64 without problems, but
3.1.0-1-amd64 doesn't work.
/-Filesystem (XFS) is at an Logical Volume and /boot is on it. As far as I can
see, everything in /boot looks good:
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20111122095055.GA5394@excelsior.lab.swapon.de">htt p://lists.debian.org/20111122095055.GA5394@excelsior.lab.swapon.de