Bug 755647 - grub2-mkdevicemap creates bad /boot/grub2/device.map on RAID configuration
Summary: grub2-mkdevicemap creates bad /boot/grub2/device.map on RAID configuration
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: grub2
Version: 16
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-21 17:19 UTC by Reinhard Jentsch
Modified: 2012-06-02 13:05 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-02 13:05:43 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Reinhard Jentsch 2011-11-21 17:19:00 UTC
Description of problem:
/dev/sda and /dev/sdb are bound together to a RAID0 array where Fedora 16 and Windows 7 is installed sdc stands alone
-------------------------------------------
mdadm --detail /dev/md126
/dev/md126:
      Container : /dev/md127, member 0
     Raid Level : raid0
     Array Size : 1953519616 (1863.02 GiB 2000.40 GB)
   Raid Devices : 2
  Total Devices : 2

          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

     Chunk Size : 128K


           UUID : be09e1ec:bdb4985e:3a0f1c77:78800e3e
    Number   Major   Minor   RaidDevice State
       1       8       16        0      active sync   /dev/sdb
       0       8        0        1      active sync   /dev/sda
-------------------------------------
fdisk -l /dev/md126

Disk /dev/md126: 2000.4 GB, 2000404086784 bytes
2 heads, 4 sectors/track, 488379904 cylinders, total 3907039232 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 131072 bytes / 262144 bytes
Disk identifier: 0xbf6ea034

      Device Boot      Start         End      Blocks   Id  System
/dev/md126p1   *        2048      206847      102400    7  HPFS/NTFS/exFAT
/dev/md126p2          206848  1258495999   629144576    7  HPFS/NTFS/exFAT
/dev/md126p3      1258496000  1259519999      512000   83  Linux
/dev/md126p4      1259520000  3907039231  1323759616    5  Extended
/dev/md126p5      1259522048  3907039231  1323758592   8e  Linux LVM
-----------------------------------------
executing grub2-mkdevicemap creates following device.map file

(hd0)	/dev/disk/by-id/ata-SAMSUNG_HD103SJ_S246J90B409134
(hd1)	/dev/disk/by-id/ata-SAMSUNG_HD103SJ_S246J9FB401127
(hd2)	/dev/disk/by-id/ata-ST31000528AS_9VP0XBMF

How reproducible:
always

Steps to Reproduce:
1.# grub2-mkdevicemap
  
Actual results:
device.map refers to
/dev/sda (by-id) as hd0
/dev/sdb (by-id) as hd1
/dev/sdc (by-id) as hd2

Expected results:
device.map should refer to
/dev/md126 (raid0) as hd0
/dev/sdc as hd1


Additional info:

This "bad" device.map produces an
"/sbin/grub2-probe: error: no such disk." error
when using grub2-mkconfig
and further a broken os-prober entry for Windows 7

editing device.map to

(hd0)   /dev/md126                                        
(hd1)   /dev/disk/by-id/ata-ST31000528AS_9VP0XBMF

solves those issues


thanks
Reinhard

Comment 1 Mads Kiilerich 2012-04-16 22:11:55 UTC
The grub used in f17 should automatically detect the right devices without using device.map.

Comment 2 Vladimir Serbinenko 2012-06-02 10:18:02 UTC
The version in F17 doesn't even have grub-mkdevicemap so obviously it doesn't have this bug.


Note You need to log in before you can comment on or make changes to this bug.