Unsolved
This post is more than 5 years old
1 Message
0
18194
December 18th, 2014 13:00
MD3000 USM_UNREADABLE_SECTORS_EXIST
Hello:
I have a legacy MD3000 Storage Array directly attached to an NX1950 running the Windows 2003 Unified Storage Operating System. In late November, I discovered that there were two drive failures and that a third drive was in critical shape.
New drives were ordered but were not delivered until earlier this week. Over the prior weekend, the affected disk volume became unavailable to our users on the network. I ran the Diagnostics, got a report from the Recovery Guru, and began following the guidelines.
I replaced two of the failed hard drives. The HotSpare drive had already failed over. Using MDSM, the drives show up as Optimal but "Unassigned". Another drive [0,12] shows up as Failed but "Assigned". Using MDSM, there are no drives listed when invoking the Modify/Replace Physical Disks option.
Firmware package version for the Storage Array = 07.35.31.60
MDSM software for the Storage Array = 03.35.G6.50
After looking through numerous forum posts, using SMcli I ran the following command:
start physicaldisk [0,x] initialize ; where x is the disk ID of the first drive listed on the Guru report. The response was Error 410 . . . inappropriate for the requested operation
Next, I ran the following command using SMcli:
start physicaldisk [0,x] reconstruct ; where x is the disk ID of the first drive listed on the Guru report. The response was Error 400 - . . . .referenced disk group does not exist
Next, I ran the following command using SMcli:
Show diskgroup [2] ;
The response showed the two newly inserted physical disks as "missing".
So, now I'm stuck with having to recover over 1.5 Tb of data on this Disk Group and of course, there is no backup. No warranty, either, nor any option to revive the warranty as support for this device has been dropped.
I have attached the latest results of the Support Report.
Is there anything that can be done to salvage this data?