View Issue Details

IDProjectCategoryView StatusLast Update
0003637CentOS-5anacondapublic2009-07-02 13:27
Reporterreppep 
PrioritynormalSeveritymajorReproducibilityalways
Status newResolutionopen 
Product Version5.3 
Target VersionFixed in Version 
Summary0003637: anaconda cannot handle dmraid devices
DescriptionI inherited a PE 1950 with a couple 750gb SATA disks, apparently configured as a mirror with dmraid.

When I try to kickstart this system, it fails to install because it cannot find either hda or sda -- kickstart snippet:

bootloader --location=mbr --driveorder=sda
zerombr
clearpart --all --initlabel --drives=sda
part /boot --asprimary --fstype=ext2 --ondisk=sda --size=256
part / --asprimary --fstype=ext3 --ondisk=sda --size=8092
part swap --asprimary --fstype=ext3 --ondisk=sda --size=8092
part /var --fstype=ext3 --ondisk=sda --size=4096
part /home --fstype=ext3 --ondisk=sda --size=100 --grow

I also saw an error in text mode, something like "ERROR: only one device argument allowed".


So I tried a manual install, and see the system finds '/dev/mapper/ddf1_Virtual Disk 0', which is *NOT* what I want to install on. I should be able to destroy the dmraid device and install onto the raw SATA disks, but anaconda (Disk Druid?) will not let me -- the Delete operation does nothing. Checking "Hide RAID device/LVM Volume Group Members" made not visible difference.

I will try booting into rescue mode and using 'dd' to destroy the mirror relationship, but both kickstarting onto the raw disks and manually deleting the RAID set in DD should work.
TagsNo tags attached.

Activities

2009-05-22 16:08

 

centos-dmraid.png (50,594 bytes)
centos-dmraid.png (50,594 bytes)

2009-05-22 16:26

 

reppep

reppep

2009-05-22 16:27

reporter   ~0009383

Attaching the kickstart error message too (apparently the device not found is what caused kickstart to give up, rather than this error):

ERROR: only one argument allowed for this option
chip

chip

2009-06-01 09:43

reporter   ~0009412

workaround (use rescue console):

dmraid -r -D
reppep

reppep

2009-06-01 14:56

reporter   ~0009415

Interesting. I'll try that if I see this problem again (unlikely). I did `dd` /dev/zero over both disks, but the system still showed me a virtual disk instead of the raw disks. I eventually pulled one, installed onto /dev/sda, and then inserted the other.
reppep

reppep

2009-06-04 13:58

reporter   ~0009439

"dmraid -r -D" & "dmraid -r -E" don't do anything, either with both disks mounted from within CentOS 5.3 running from sda, or booted into rescue mode (with just sda available, or after I inserted sdb too).

[root@sara00 ~]# dmraid -r
/dev/sda: ddf1, ".ddf1_disks", GROUP, ok, 487063552 sectors, data@ 0
/dev/sdb: ddf1, ".ddf1_disks", GROUP, ok, 487063552 sectors, data@ 0
[root@sara00 ~]# dmraid -r -D
/dev/sda: ddf1, ".ddf1_disks", GROUP, ok, 487063552 sectors, data@ 0
/dev/sdb: ddf1, ".ddf1_disks", GROUP, ok, 487063552 sectors, data@ 0
[root@sara00 ~]# dmraid -r
/dev/sda: ddf1, ".ddf1_disks", GROUP, ok, 487063552 sectors, data@ 0
/dev/sdb: ddf1, ".ddf1_disks", GROUP, ok, 487063552 sectors, data@ 0
[root@sara00 ~]# dmraid -r -E
Do you really want to erase "ddf1" ondisk metadata on /dev/sda ? [y/n] :y
ERROR: ddf1: seeking device "/dev/sda" to 127999999737856
ERROR: writing metadata to /dev/sda, offset 249999999488 sectors, size 0 bytes returned 0
ERROR: erasing ondisk metadata on /dev/sda
Do you really want to erase "ddf1" ondisk metadata on /dev/sdb ? [y/n] :y
ERROR: ddf1: seeking device "/dev/sdb" to 127999999737856
ERROR: writing metadata to /dev/sdb, offset 249999999488 sectors, size 0 bytes returned 0
ERROR: erasing ondisk metadata on /dev/sdb
reppep

reppep

2009-06-04 14:22

reporter   ~0009440

Is it this dmraid bug?

https://rhn.redhat.com/errata/RHBA-2008-0749.html

My symptoms aren't an exact match, but also in erasing disks...

[root@sara00 ~]# rpm -q dmraid
dmraid-1.0.0.rc13-33.el5
chip

chip

2009-06-05 09:56

reporter   ~0009443

The same workaround works fine for me. Our hardware includes isw (Intel Software RAID).

2009-07-02 11:04

 

2009-07-02 11:04

 

dmraid_r_E.png (74,953 bytes)
dmraid_r_E.png (74,953 bytes)
chip

chip

2009-07-02 11:07

reporter   ~0009549

have a look at those attachments:
http://bugs.centos.org/file_download.php?file_id=728&type=bug
http://bugs.centos.org/file_download.php?file_id=729&type=bug
reppep

reppep

2009-07-02 13:27

reporter   ~0009551

So there's a(nother?) bug, because as you can see from my 06-04 comment, the same command failed for me.

Issue History

Date Modified Username Field Change
2009-05-22 16:08 reppep New Issue
2009-05-22 16:08 reppep File Added: centos-dmraid.png
2009-05-22 16:26 reppep File Added: kickstart-error-argument.png
2009-05-22 16:27 reppep Note Added: 0009383
2009-06-01 09:43 chip Note Added: 0009412
2009-06-01 14:56 reppep Note Added: 0009415
2009-06-04 13:58 reppep Note Added: 0009439
2009-06-04 14:22 reppep Note Added: 0009440
2009-06-05 09:56 chip Note Added: 0009443
2009-07-02 11:04 chip File Added: only_one_argument_allowed_for_this_option.png
2009-07-02 11:04 chip File Added: dmraid_r_E.png
2009-07-02 11:07 chip Note Added: 0009549
2009-07-02 13:27 reppep Note Added: 0009551