Bugzilla – Bug 222471
udev links wrong on DM Raid 1
Last modified: 2006-11-21 20:13:50 UTC
After creating a fakeRAID with 2 mirrored disks last last disk gets the EDD id 80, which has to be the devicemapper device. Guess: As the mbr signature is stored on both disks, the las disk wins, as its the last that is read. This way we can't reliably check which device has to be used as boot device.
What does: /lib/udev/vol_id --export <device> print for the raid-members?
Alex, please test
Ok, here's the output to comment #1: /lib/udev/vol_id --export /dev/disk/by-id/raid-isw_cidadbhgaj_TestRAID ==> /dev/disk/by-id/raid-isw_cidadbhgaj_TestRAID: unknown volume typ /lib/udev/vol_id --export /dev/disk/by-id/ata-HDT722516DLA380_VDK91BTC024GGR ==> ID_FS_USAGE=raid ID_FS_TYPE=isw_raid_member ID_FS_VERSION=1.1.00 ID_FS_UUID= ID_FS_LABEL= ID_FS_LABEL_SAFE= /lib/udev/vol_id --export /dev/disk/by-id/ata-SAMSUNG_SP0812C_0693J1FWC08152 ==> ID_FS_USAGE=raid ID_FS_TYPE=isw_raid_member ID_FS_VERSION=1.1.00 ID_FS_UUID= ID_FS_LABEL= ID_FS_LABEL_SAFE= /lib/udev/vol_id --export /dev/disk/by-id/scsi-SATA_HDT722516DLA380_VDK91BTC024GGR ==> ID_FS_USAGE=raid ID_FS_TYPE=isw_raid_member ID_FS_VERSION=1.1.00 ID_FS_UUID= ID_FS_LABEL= ID_FS_LABEL_SAFE= /lib/udev/vol_id --export /dev/disk/by-id/scsi-SATA_SAMSUNG_SP0812C0693J1FWC08152 ==> ID_FS_USAGE=raid ID_FS_TYPE=isw_raid_member ID_FS_VERSION=1.1.00 ID_FS_UUID= ID_FS_LABEL= ID_FS_LABEL_SAFE= I hope this is sufficient. If not, feel free to request more.
Please try this in: # BIOS Enhanced Disk Device -KERNEL=="*[!0-9]", IMPORT{program}="edd_id --export $tempnode" +KERNEL=="*[!0-9]", ENV{ID_FS_USAGE}!="raid", IMPORT{program}="edd_id --export $tempnode" in: /etc/udev/rules.d/60-persistent-storage.rules and see what links are created after reboot.
Stefan, is #5 helping?
Currently doing a few tests, will provide feedback soon.
Ok, #5 didn't really help with this problem. But we've made a fix for yast2-bootloader, so now one can install properly to dmraids. A new package of yast2-bootloader will be available, too. As this fix solves the problem, I close this bug FIXED.