Your message dated Wed, 15 Sep 2010 19:47:18 +0200
with message-id <1284572838.29930.3.ca...@localhost>
and subject line Re: Update to 1.98+20100720-1 and 1.98+20100722-1
has caused the Debian Bug report #575429,
regarding grub-pc: The filesystem containing /boot/grub does not support UUIDs
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
575429: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575429
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: grub-pc
Version: 1.98-1
Severity: normal
Hi,
On a new machine, I wanted to test the daily-build (Monday 22) of Squeeze
installer
for amd64.
The machine has 2 SATA hard drives, are mounted in RAID1 soft by Linux.
I have a RAID1 partition "md0" to "/boot", the root is mounted on a logical
volume,
it uses the same partition RAID1 "md1".
The installation is successfully completed, except for installing the boot
loader
grub2 (version 1.98-1).
Through the console, I have this:
# grub-install --recheck --no-floppy --modules="mdraid raid" /dev/md0
/usr/sbin/grub-probe: error: no mapping exists for `md0'.
/usr/sbin/grub-probe: error: no mapping exists for `md0'.
/usr/sbin/grub-setup: error: no mapping exists for `md0'.
# grub-install --recheck --no-floppy /dev/sda
/usr/sbin/grub-probe: error: no mapping exists for `md0'.
Auto-detection of a filesystem module failed.
Please specify the module with the option `--modules' explicitly.
# grub-install --recheck --no-floppy --modules="mdraid raid" /dev/sda
/usr/sbin/grub-probe: error: no mapping exists for `md0'.
/usr/sbin/grub-probe: error: no mapping exists for `md0'.
/usr/sbin/grub-probe: error: no mapping exists for `md0'.
You attempted a cross-disk install, but the filesystem containing
/boot/grub does not support UUIDs.
# grub-install --recheck --no-floppy --modules="mdraid raid
search_fs_uuid" /dev/sda
/usr/sbin/grub-probe: error: no mapping exists for `md0'.
/usr/sbin/grub-probe: error: no mapping exists for `md0'.
/usr/sbin/grub-probe: error: no mapping exists for `md0'.
You attempted a cross-disk install, but the filesystem containing
/boot/grub does not support UUIDs.
There is this in the file "/boot/grub/device.map":
(hd0) /dev/sda
(hd1) /dev/sdb
The matching of UUID and devices is good:
# blkid
/dev/sdb1: UUID="248d7222-1d79-dd61-2766-b0f63e142f70" LABEL="eole2:0"
TYPE="linux_raid_member"
/dev/sdb2: UUID="76644d49-c5f7-9ab6-fe74-81c94fa9616e" LABEL="eole2:1"
TYPE="linux_raid_member"
/dev/mapper/VG0-swap: UUID="88469241-b7d3-4e85-97b5-d33a56bfd2fd"
TYPE="swap"
/dev/sda1: UUID="248d7222-1d79-dd61-2766-b0f63e142f70" LABEL="eole2:0"
TYPE="linux_raid_member"
/dev/sda2: UUID="76644d49-c5f7-9ab6-fe74-81c94fa9616e" LABEL="eole2:1"
TYPE="linux_raid_member"
/dev/md0: UUID="157deef1-ea8f-4611-9021-5e2fabcd84cf" TYPE="ext3"
/dev/md1: UUID="rNyfNa-5mXA-Ne77-Z15k-KpWA-kFzL-nZbp3h" TYPE="LVM2_member"
/dev/mapper/VG0-root: UUID="6e5c349c-d880-4329-a15c-e192aee4954a"
TYPE="ext4"
The file "/etc/fstab" (created by installer) contains:
/dev/mapper/VG0-root / ext4 errors=remount-ro 0 1
UUID=157deef1-ea8f-4611-9021-5e2fabcd84cf /boot ext3 0 2
The command "grub-probe" is no more reassuring:
# grub-probe -d /dev/md0 -tabstraction
grub-probe: error: no mapping exists for `md0'.
I read the bug report #554790 on Grub2 and UUID, but it is February.
Does Grub2 (version 1.98-1) manages UUIDs?
I was not able to set Grub2 with the "/dev/disk/by-id".
Regards.
-- Package-specific info:
*********************** BEGIN /proc/mounts
/dev/hda /cdrom iso9660 ro,relatime 0 0
/dev/VG0/root / ext4 rw,relatime,barrier=1,data=ordered 0 0
/dev/md0 /boot ext3 rw,nosuid,nodev,noexec,noatime,errors=continue,data=ordered
0 0
*********************** END /proc/mounts
*********************** BEGIN /boot/grub/device.map
(hd0) /dev/sda
(hd1) /dev/sdb
*********************** END /boot/grub/device.map
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages grub-pc depends on:
ii debconf [debconf-2.0] 1.5.28 Debian configuration management sy
ii grub-common 1.98-1 GRand Unified Bootloader, version
ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib
ii ucf 3.0025 Update Configuration File: preserv
grub-pc recommends no packages.
Versions of packages grub-pc suggests:
pn desktop-base <none> (no description available)
-- debconf information:
grub-pc/kopt_extracted: false
grub2/kfreebsd_cmdline:
* grub-pc/install_devices:
grub-pc/postrm_purge_boot_grub: false
* grub2/linux_cmdline:
grub2/kfreebsd_cmdline_default: quiet
* grub2/linux_cmdline_default: quiet
grub-pc/chainload_from_menu.lst: true
--- End Message ---
--- Begin Message ---
Version: 1.98+20100722-1
Am Mittwoch, den 15.09.2010, 17:34 +0200 schrieb Frédéric Massot:
> Le 15/09/2010 14:31, Alexander Kurtz a écrit :
> > Am Dienstag, den 27.07.2010, 22:02 +0200 schrieb Frederic MASSOT:
> >> I update grub-common and grub-pc to 1.98+20100720-1 and then to
> >> 1.98+20100722-1.
> >>
> >> I have no error message, Grub detects two HDD and the system reboot well
> >> for two versions.
> >
> > So you do no longer experience this problem?
>
> Yes, these versions fixes the bug.
>
> To supplement, I tested the latest Squeeze version (1.98+20100804-4) and
> the system boot successfully.
signature.asc
Description: This is a digitally signed message part
--- End Message ---
