Hi Phillip, Dmraid does in fact match the disks' serial numbers read from the device and the metadata to create raid sets. So, if the numbers don't match (as is it appears to be in this case), the raid set won't be recognized by dmraid. The serial number for sdb does look fishy and it could be interacting strangely with the library isspace() function used to strip out the whitespace (if some of the strange characters are control characters). This may be the reason why the raid set is recognized under Windows. Adam Cetnerowski Intel Technology Poland -----Original Message----- From: ataraid-list-bounces@xxxxxxxxxx [mailto:ataraid-list-bounces@xxxxxxxxxx] On Behalf Of Phillip Susi Sent: Monday, June 23, 2008 11:17 PM To: ATARAID (eg, Promise Fasttrak,Highpoint 370) related discussions Subject: Why are spaces removed from the disk serial number? I am investigating a bug report from a user where dmraid fails to recognize their array because one of the disks serial numbers does not appear to match the serial number recorded in the disk table slot for their isw raid ( which works fine in windows ). It looks like dmraid reads the serial number from the disk with an inquiry command, then removes whitespace characters from it. Why is this and could this be the cause of the problem? Also, it appears that the disk serial number contains non ascii characters. Is this normally allowed and how should they be interpreted? UTF-8? The full bug report can be found here: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/138130 _______________________________________________ Ataraid-list mailing list Ataraid-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/ataraid-list _______________________________________________ Ataraid-list mailing list Ataraid-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/ataraid-list
