bugGNU GRUB - Bugs: bug #39528, Can't boot grub2 when 7 software...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #39528: Can't boot grub2 when 7 software raid-1 arrays exist

Submitter:  Wesley <pa4wdh>
Submitted:  Fri 19 Jul 2013 05:18:46 PM UTC
   
 
Category:  Booting Severity:  Major
Priority:  5 - Normal Item Group:  Software Error
Status:  None Privacy:  Public
Assigned to:  None Originator Name: 
Open/Closed:  Closed Release:  other
Release:  Reproducibility:  None
Planned Release:  None

Sat 20 Jul 2013 09:49:07 AM UTC, comment #3: 

Marking as closed then.

Andrei Borzenkov <arvidjaar>
Group Member
Sat 20 Jul 2013 09:04:19 AM UTC, comment #2: 

Just tested with the current trunk and it indeed boots without problems.

Wesley <pa4wdh>
Sat 20 Jul 2013 05:23:41 AM UTC, comment #1: 

I cannot reproduce it in QEMU using current trunk - grub has no problem accessing filesystem on MD RAID1 with 7 raids in total. I used your command to recreate each MD. Could you test using current trunk?

Andrei Borzenkov <arvidjaar>
Group Member
Fri 19 Jul 2013 05:18:46 PM UTC, original submission:  

Hi All,

The grub release i'm using is 2.00 (i could only choose 1.x from the menu).
On my system i have multiple partitions which are made into 7 linux software raid-1 devices.
When all 7 devices are created it does not boot because it can't read the filesystems on md0 and md1. md0 contains /boot. Grub2 gives a rescue prompt, and when the prefix is set to (hd0,1)/grub2 it is able to boot. (hd0,1 is the real device which together with hd1,1 forms md0)

My confguration:
These are the partitions of sda, sdb are the same:
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes, 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0xf96d7342

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1            2048      264191      131072   fd  Linux raid autodetect
/dev/sda2          264192     8652799     4194304   fd  Linux raid autodetect
/dev/sda3         8652800  1953525167   972436184    5  Extended
/dev/sda5         8654848   428085247   209715200   fd  Linux raid autodetect
/dev/sda6       428087296   847517695   209715200   fd  Linux raid autodetect
/dev/sda7       847519744  1266950143   209715200   fd  Linux raid autodetect
/dev/sda8      1266952192  1686382591   209715200   fd  Linux raid autodetect
/dev/sda9      1686384640  1953525167   133570264   fd  Linux raid autodetect

/dev/sda1 and /dev/sdb1 are /dev/md0 which is mounted at /boot
/dev/sda2 and /dev/sdb2 are /dev/md1 which is mounted at /
Partitions sdX5 to sdX9 are /dev/md5-9 where i intend to use LVM but they are now formatted with ext3.

These are the md devices from /proc/mdstat:
md1 : active raid1 sdb2[1] sda2[0]
      4194240 blocks [2/2] [UU]

md5 : active raid1 sdb5[1] sda5[0]
      209715136 blocks [2/2] [UU]

md6 : active raid1 sdb6[1] sda6[0]
      209715136 blocks [2/2] [UU]

md7 : active raid1 sdb7[1] sda7[0]
      209715136 blocks [2/2] [UU]

md8 : active raid1 sdb8[1] sda8[0]
      209715136 blocks [2/2] [UU]

md9 : active raid1 sdb9[1] sda9[0]
      133570176 blocks [2/2] [UU]

md0 : active raid1 sdb1[1] sda1[0]
      131008 blocks [2/2] [UU]

When i reboot i end up in a rescue shell, and this a log such a rescue session:

GRUB loading.
Welcome to GRUB!

error: file `/grub2/i386-pc/normal.mod' not found.
Entering rescue mode...
grub rescue> ls
(md/md8) (md/md7) (md/md6) (md/md5) (md/md1) (md/md0) (md/md9) (hd0) (hd0,msdos
9) (hd0,msdos8) (hd0,msdos7) (hd0,msdos6) (hd0,msdos5) (hd0,msdos2) (hd0,msdos1
) (hd1) (hd1,msdos9) (hd1,msdos8) (hd1,msdos7) (hd1,msdos6) (hd1,msdos5) (hd1,m
sdos2) (hd1,msdos1) (hd2) (hd3) (hd4) (hd5) (hd6) (hd7) (hd8) (hd9) (hd10) (hd1
1) (hd12) (hd13) (hd14) (hd15)
grub rescue> ls (md/md0)/
error: unknown filesystem.
grub rescue> ls (hd0,1)/
./ ../ lost+found/ grub2/ boot vmlinuz-3.8.13 .keep vmlinuz-3.8.13-64bit
grub rescue> set prefix=(hd0,1)/grub2
grub rescue> insmod normal
grub rescue> normal
grub> ls (md/md0)/
error: unknown filesystem.
grub> insmod mdraid09
grub> ls (md/md0)/
error: unknown filesystem.
grub> ls (hd0,1)/
lost+found/ grub2/ boot vmlinuz-3.8.13 vmlinuz-3.8.13-64bit
grub> linux (hd0,1)/vmlinuz-3.8.13-64bit $kernel_parameters
grub> boot

$kernel_parameters is a variable i set with all required kernel parameters:
root=/dev/md1 console=ttyS0,19200n8 clocksource=hpet

If i remove the raid-1 configuration for /dev/md9 the systems boots without problems. If i create the array again it fails in the same way as described above.

To delete an array i use:
mdadm --zero-superblock /dev/sda9
mdadm --zero-superblock /dev/sdb9
I don't actually delete the partitions, just doing this makes the system boot.
To create it again:
mdadm --create -l 1 -n 2 --metadata=0.9 /dev/md9 /dev/sda9 /dev/sdb9

Best regards,
Wesley

Wesley <pa4wdh>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by arvidjaar (Posted a comment)
  • -email is unavailable- added by pa4wdh (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

     

    Follows 1 latest change.

    Date Changed by Updated Field Previous Value => Replaced by
    2013-07-20 arvidjaar Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-02a9.
    Corresponding source code