Description of problem: * jMicro metadata processing mistreats bios-entered label somehow, and ends up with a Ctrl-A (char-code 1) as the last character of the label. * isw does not know RAID5 mode. Version-Release number of selected component (if applicable): kernel-2.6.20-1.2949.fc7 dmraid-1.0.0.rc14-2.fc7 device-mapper-1.02.17-6.fc7 device-mapper-libs-1.02.17-6.fc7 device-mapper-multipath-0.4.7-5 device-mapper-libs-1.02.17-6.fc7 How reproducible: Mode "RAID5" does not work, others apparently do. Steps to Reproduce: 1. Have "Abit AB9 Pro" board with lattest BIOS and 4+2 SATA-disks attached. 2. Configure jMicro interface to be in RAID mode, and configure it to have mirrored disks with a label. 3. Configure sysboard ICH8R to be in RAID mode, and try various disk setups.. Actual results: * jMicro /dev/mapper/ labels are rather ugly... * FC6 didn't understand this ISW at all, currect versions of dmraid do.. Expected results: * No "^A" in jMicro labels... * ISW RAID5 support (would be nice) Additional info: "dmraid -n" dumps in attachments.
Created attachment 148927 [details] dmraid -n dump of ISW in RAID5 mode + jMicro dump
Created attachment 148928 [details] dmraid -n dump of ISW in RAID0 mode + jMicro dump
Created attachment 148929 [details] dmraid -n dump of ISW in RAID1 mode + jMicro dump
Created attachment 148930 [details] dmraid -n dump of ISW in RAID10 mode + jMicro dump
I suspect that the jMicro label reading runs looking for zero-terminated string, and thus runs over the 16 character array for the label to whatever is behind it. The jMicro volume labels are padded with spaces, which did produce mighty odd looking results in /dev/mapper/ when the label is shorter than 16 characters. That "Ctrl-A" is there then also at 17th position of the label string. Should the DMRAID tool be modified to drop/mutate non-printable characters ? Turning them all to underscores or hyphens ? What about "/" in the label ?
Jmicron label bug still present in fc7 test 3. Bug prevents grub installation and prevents bootup after installation. There's a patch on the ataraid list. Please put it in: https://www.redhat.com/archives/ataraid-list/2007-February/msg00003.html
Based on the date this bug was created, it appears to have been reported against rawhide during the development of a Fedora release that is no longer maintained. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained. If this bug remains in NEEDINFO thirty (30) days from now, we will automatically close it. If you can reproduce this bug in a maintained Fedora version (7, 8, or rawhide), please change this bug to the respective version and change the status to ASSIGNED. (If you're unable to change the bug's version or status, add a comment to the bug and someone will change it for you.) Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again.
This bug has been in NEEDINFO for more than 30 days since feedback was first requested. As a result we are closing it. If you can reproduce this bug in the future against a maintained Fedora version please feel free to reopen it against that version. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp