Re: Bug#649563: linux-image-3.1.0-1-amd64 can't load initial ramdisk anymore
On 22.11.11 01:40, Jonathan Nieder wrote:
> > 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:
$ ls -l /boot/
total 46976
-rw-r--r-- 1 root root 124738 Jul 5 05:09 config-2.6.39-2-amd64
-rw-r--r-- 1 root root 125263 Aug 27 19:54 config-3.0.0-1-amd64
-rw-r--r-- 1 root root 127216 Nov 14 09:35 config-3.1.0-1-amd64
drwxr-xr-x 3 root root 8192 Nov 22 06:27 grub
-rw-r--r-- 1 root root 11073606 Aug 7 06:07 initrd.img-2.6.39-2-amd64
-rw-r--r-- 1 root root 11230400 Nov 21 17:18 initrd.img-3.0.0-1-amd64
-rw-r--r-- 1 root root 11332592 Nov 22 06:27 initrd.img-3.1.0-1-amd64
-rw-r--r-- 1 root root 1887188 Jul 5 05:09 System.map-2.6.39-2-amd64
-rw-r--r-- 1 root root 2007368 Aug 27 19:54 System.map-3.0.0-1-amd64
-rw-r--r-- 1 root root 2033352 Nov 14 09:35 System.map-3.1.0-1-amd64
-rw-r--r-- 1 root root 2690384 Jul 5 05:04 vmlinuz-2.6.39-2-amd64
-rw-r--r-- 1 root root 2705680 Aug 27 19:49 vmlinuz-3.0.0-1-amd64
-rw-r--r-- 1 root root 2725040 Nov 14 09:21 vmlinuz-3.1.0-1-amd64
Really no clue what happens here.
Regards
Friedemann
Reply to: