After reviewing the Support bundle the issue you are dealing with is a puncture of the VD. The minimum thing I would recommend to resolve this would be to back up the data and  delete the disk group. Replace all the failed drives. When it is saying disk 7 the failed disk is actually HDD 6. Then recreate the VD with the new drives. Then you will need to go in and update the firmware on the Controllers and the firmware on the hard drives. Now what I would fully recommend you do is back up all of the data of the entire array and reconfigure it with one large RAID array. Then just split it up with Virtual disks rather than each one have its own RAID level. You will see better performance when you have more drives in the disk group rather than having it split up the way it is currently setup. Please let me know if you have any other questions and I would be happy to help you out.
 Greetings! We have an MD3000i that has been in operation for some time. It's configured with 15 x 750GB SAS drives, and recently we've experienced a couple of drive failures, including 1 of the 2 hot spares in the chassis. Initially this chassis was configured with: - RAID 6 array (named RAID6-1) with 5 drives - slots 0,1,2,3,4 - RAID10 array (named RAID 10-1) with 4 drives - slots 7,8,9,10 - RAID10 array  (named RAID10-2) with 4 drives - slots 11,12,13,14 - 2 drives labeled as hot spares - slots 5,6 A couple of weeks ago, we experienced a drive failure in the RAID 6 array. What was interesting is that neither of the hot spare drives automatically replaced the failed drive in the RAID 6 array. As a precaution, we migrated all the data off of the RAID 6 array, deleted the virtual disk and recreated it as a RAID 10 array. This left us with a configuration of: - RAID10 array (named RAID 10-1) with 4 drives - slots 7,8,9,10 - RAID10 array  (named RAID10-2) with 4 drives - slots 11,12,13,14 - RAID10 array  (named RAID10-3) with 4 drives - slots 1,2,3,4 - 2 drives labeled as hot spares - slots 5,6 - failed drive - slot 0 Today, I started receiving warnings about a failed RAID 10-2 array. In this case  the hot spare in slot 5 came up as failed, and the 2nd hot spare in slot 6 became active to rebuild the failed RAID 10 array.  So now we are looking at 3 failed drives in the array but that's not really my question ... just some background. During the rebuild process on RAID 10-2 I started receiving warnings about unreadable sectors. A report shows 38 unreadable sectors that have both a failure type of Logical and Physical. Here is where I am a bit confused ... The unreadable sectors report is stating that the unreadable sectors are coming from a Virtual Disk that is on the RAID 10-2 array . This is the array that rebuilt today. The drives in this array are now - slots 11,12,13,6 (with 6 being the hot spare) *BUT* the unreadable sector report is stating the Physical Disk location is  Enclosure 0, Slot 7  The storage profile report shows: ###  RAID 10-2 0,14       0,12 [mirrored pair with physical disk at enclosure 0, slot 11]        0,13       0,11 [mirrored pair with physical disk at enclosure 0, slot 12]        0,6 [hot spare physical disk is sparing for physical disk at 0, 14]    0,14      ####  So I have a couple of questions: 1. Is the unreadable sectors report reporting slots numbers that start at 1 instead of 0. That would make the hot spare that just came into use the drive with unreadable sectors 2. The storage profile report does not show a mirror for slot 0,13  This disk was mirroring to the drive in slot 0,14 Shouldn't 13 & 6 be mirroring each other now?  To be on the safe side, we are migrating all data off of the RAID 10-2 array to the recently created RAID 10-3 array. We're also thinking about deleting the RAID 10-2 array and making it a RAID 1 array, so that we can utilize the remaining drives as chassis hot spares (while we await delivery of replacement drives we have already ordered). Any insight or suggestions on this are appreciated. Thanks!Gene 
MD3000i unreadable sectors