Bug#478228: grub-probe: can't handle (raid) md-devices
Hey Felix Sorry for needing so much time - too much work. mdraids with default 0.90 format works fine with grub2 as long as you aren't installing grub in a chroot to it, That is a common case for repair, if your system fails to boot but have booted your system with it. Ok So please recreate your /boot md with default format 0.90 There was a problem with 0.90, but I already forgot it. I also don't want to go back. Format 1.x ist the actual format, a new program should support the actual format (and I don't know how to go back ) and make sure it's fully synced i.e. /proc/mdstat shows [UU] grub-probe has problems with missing devices or not fully synced raids. It is synced Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#478228: grub-probe: can't handle (raid) md-devices
reassign 492897 grub2 #forgot that it applies to whole grub2 not just grub-probe thanks Hello, Am Sonntag, den 03.08.2008, 21:09 +0200 schrieb Thomas Rösch: Hey Felix Sorry for needing so much time - too much work. No problem, thanks for replying to both mails. mdraids with default 0.90 format works fine with grub2 as long as you aren't installing grub in a chroot to it, That is a common case for repair, if your system fails to boot Yeah chroots are needed, but I couldn't get it to work as I played with mdraid 1 and 5 for testing grub on it. There was a problem with 0.90, but I already forgot it. I also don't want to go back. Format 1.x ist the actual format, a new program should support the actual format (and I don't know how to go back ) #492897 is the cloned bug, for the wishlist request to support this. I don't know where /dev/md/6 come from. See #475585 As I tried the whole mdraid stuff out I always had both forms mdN and md/N As long as you have a /dev/mdN without / everything is fine for grub-probe I don't try grub-install , because I have no time to repair my system, if It do not work. :-( It won't work anyway with the super 1.X format. grub-setup is able to detect this and warn about (see the message from Robert about this in this report) But grub-probe doestn't use that code, it uses only the code real grub uses. As I cloned the bug I wanted to leave it open for the case you've still problems with super 0.90. But I leave it now to Robert if he wants to close it or retitle it to sth. like grub-probe fails to warn about unsupported super 1.X I looked a bit at the Code but using the one grub-setup is using isn't that easy in grub-probe, because grub-probe has to care about LVM devices too. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#478228: grub-probe: can't handle (raid) md-devices
clone 478228 -1 retitle -1 grub2 should support mdraid 1.X format of superblock severity -1 wishlist thanks /proc/mdstat: md9 : active raid1 sdc9[3] sda9[2] 979952 blocks super 1.0 [2/2] [UU] md6 : active raid10 sdb6[0] sdd6[3] sdc6[2] sda6[1] 97658880 blocks super 1.0 128K chunks 2 near-copies [4/4] [] Guntsche Michael said yesterday on grub-devel now, that grub2 can only handle the default 0.90 superblock format but as you can see above you are using 1.0 even for /boot man mdadm says: The difference between 0.90 and 1.X is that 0.90 only supports 28 devices and 2 TB. The difference between 1.0, 1.1 and 1.2 is only the position where it's stored on the devices. mdraids with default 0.90 format works fine with grub2 as long as you aren't installing grub in a chroot to it, but have booted your system with it. So please recreate your /boot md with default format 0.90 and make sure it's fully synced i.e. /proc/mdstat shows [UU] grub-probe has problems with missing devices or not fully synced raids. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#478228: grub-probe: can't handle (raid) md-devices
On Tue, Jul 29, 2008 at 07:24:09PM +0200, Felix Zielcke wrote:
Guntsche Michael said yesterday on grub-devel now, that grub2 can only handle
the default 0.90
superblock format but as you can see above you are using 1.0 even for /boot
But we have a check for this:
/* FIXME: Also support version 1.0. */
if (sb.major_version != 0 || sb.minor_version != 90)
{
grub_error (GRUB_ERR_NOT_IMPLEMENTED_YET,
Unsupported RAID version: %d.%d,
sb.major_version, sb.minor_version);
return 0;
}
isn't this message reflected in grub-probe -vv output?
--
Robert Millan
The DRM opt-in fallacy: Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#478228: grub-probe: can't handle (raid) md-devices
From: Robert Millan [EMAIL PROTECTED]
But we have a check for this:
/* FIXME: Also support version 1.0. */
if (sb.major_version != 0 || sb.minor_version != 90)
{
grub_error (GRUB_ERR_NOT_IMPLEMENTED_YET,
Unsupported RAID version: %d.%d,
sb.major_version, sb.minor_version);
return 0;
}
isn't this message reflected in grub-probe -vv output?
I saw this today during my mdraid debuginng.
But in the whole Bugreport there's only Scanning for RAID devices and only once
Unsupported RAID version, yours.
But I now read again mdadm(8)
I should have just pasted that part in my mail before.
1.0 stores the superblock at the end of the device.
It doestn't say where 0.90 stores it but the grub code for it looks like it's
in the beginning of it.
1.1 stores it in the start.
1.2 stores it 4K from start.
This is a bit tricky to check all 4 formats.
(that's why I CC the cloned bug.)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#478228: grub-probe can't handle (raid) md-devices
Hello, grub-probe: info: opening md6 /home/rmh/hacking/grub/debian/upload/grub2-1.96+20080704/kern/disk.c:220: Opening `md6'... /home/rmh/hacking/grub/debian/upload/grub2-1.96+20080704/kern/disk.c:299: Opening `md6' failed. /home/rmh/hacking/grub/debian/upload/grub2-1.96+20080704/kern/disk.c:312: Closing `md6'. grub-probe: error: unknown device md6 Hmm, I don't know how it should look like. So please update grub-common (and better grub-pc also) to 1.96+20080724-2 which should be in the next days in testing on the mirrors. Recreate your devicemap with grub-mkdevicemap --no-floppy and please check your raid config with mdadm. You should be using /dev/md6 devices and not /dev/md/6, because the latter aren't yet supported by grub-probe Try again grub-install and if it fails then again grub-probe -vv I hope that the output then isn't the same as you had. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#478228: Debian bug #478228 grub-probe can't handle (raid) md-devices
From: Thomas Rösch [EMAIL PROTECTED] Hello, I am sorry, i have removed this version and use the old grub again since some month. grub-probe is in grub-common and the old grub depends on it since version 0.97-33 So can you please make sure you have grub-common 1.96+20080704-2 installed and then please try grub-probe again, as you did on your report? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#478228: grub-probe can't handle (raid) md-devices
Urm sorry, i think my last mail wasn't that clear :) I forgot that you did reported this against grub-legacy. You can install grub-common without problems with an old grub-legacy even if it's 0.97-33 It only contains grub-probe and grub-mkdevicemap [0] and it doestn't conflict with any package. If it still fails then please show grub-probe -vv output. Thanks. [0] http://packages.debian.org/sid/amd64/grub-common/filelist -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#478228: Debian bug #478228 grub-probe can't handle (raid) md-devices
retitle 478228 grub-probe: can't handle (raid) md-devices reassign 478228 grub-common thanks Is this still an issue with 1.96+20080704-2 currently in testing/unstable ? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
