Re: Bug#597563: grub-common: grub-probe segfaults scanning lvm devices

[Matthew Gabeler-Lee <cheetah@fastcat.org>]

[-- Attachment #1: Type: text/plain, Size: 1676 bytes --]

On 1/8/2011 18:34, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> Sorry, I've noticed that I've looked into the wrong place all the long.
> md2 is fine. I suppose it's a problem with md0 (all mdraid are assembled
> at the beginning). Since md0 is raid1, its misassembly wouldn't have any
> influence (we don't write to devices). mdstat lists both md0 and md1 as
> having no duplicate indices. I would need info on md0 for this (now
> minor) remaining bug.
$ sudo mdadm -QD /dev/md0
/dev/md0:
         Version : 0.90
   Creation Time : Mon Mar 27 14:03:04 2006
      Raid Level : raid1
      Array Size : 2008000 (1961.27 MiB 2056.19 MB)
   Used Dev Size : 2008000 (1961.27 MiB 2056.19 MB)
    Raid Devices : 4
   Total Devices : 4
Preferred Minor : 0
     Persistence : Superblock is persistent

     Update Time : Sat Jan  8 18:35:47 2011
           State : clean
  Active Devices : 4
Working Devices : 4
  Failed Devices : 0
   Spare Devices : 0

            UUID : 9364f7a2:d74695d5:7d8db3a0:3b5f9e48
          Events : 0.10758124

     Number   Major   Minor   RaidDevice State
        0       8       17        0      active sync   /dev/sdb1
        1       8       33        1      active sync   /dev/sdc1
        2       8        1        2      active sync   /dev/sda1
        3       8       49        3      active sync   /dev/sdd1

Output of "for i in a b c d ; do sudo dd if=/dev/sd${i}1 
of=sd${i}1.last64k.img skip=$((2008000)) bs=1024 count=64 ; done" is attached.

-- 
	-Matt
"Reality is that which, when you stop believing in it, doesn't go away".
                 -- Philip K. Dick
GPG pubkey fingerprint: A57F B354 FD30 A502 795B 9637 3EF1 3F22 A85E 2AD1


[-- Attachment #2: last64k.md0.tar.bz2 --]
[-- Type: application/octet-stream, Size: 455 bytes --]