- May 12, 2017
- 2
- 0
- 510
Hello fellow Techies - looking for some bright ideas here to possibly get 1 of the 2 drives in this RAID set to be accessible again. I have only set up one Raid 0 set ever in my travels and I would like to pass this by some of you more experienced RAID'ers to see if a possible solution exists. I am an IT guy myself so possible answers don't have to be intricate. Right then!
We have this old WD MyBook Live DUO POS 6TB device whose enclosure took a crap on itself. Heat is my guess personally these things were blazing hot after trying to get the software to recognize the unit. The drives were yanked and slaved to other machines and all Windows 7 64-bit machines show the drives like this:
Both Drives show up in disk mgmt, both show "healthy" primary partitions and both are accessible to DISKPART. However, no volumes populate, drive letters cannot be assigned and some commands are unsuccessful. BREAK has no effect, converting to MBR doesn't work (although I assume that is because of the 2.2TB cap on MBR parts), and converting to Dynamic simply wipes out the lead reserved partition of the 5. Assuming it destroyed that one because of GPT structure.
So my guess is that this used to be a mirrored array as opposed to striped, and I'm not sure those DUO's could even be configured as JBOD - however I would think the partition layout would not be the way it is if THAT were the case. But no one knows for certain. Now I don't really know what all transpires when a RAID set is created or how anything is formatted partition layout wise, so running a bunch of utilities similar to /fixboot such and such or running it through SPINRITE (these are spindle drives) and burning all that time is not what I wanted to do without some minor feedback and checking. Because maybe there is a quick simple answer from someone whose experienced this. I also will probably just start messing with one disk as I probably have a viable second disk in case of emergency or disk utility foul up. My worry is if I foul up one disk and the other was actually a bad disk then I've lost both.
I would also like to assume that only ONE of these disks could be considered "bad" as it is unlikely both failed simultaneously. Meaning whatever is happening is more likely to be some raid formatting issue or something to the like. If I can undo that mystery operation maybe I can salvage the drive's data. I know my current machine which is housing the drives is Sata 6Gb capable so it's not a platform issue either. And obviously if I can see the drive is not a UEFI There is no horrible "clicking of death" and here is the kicker: Speccy informs me all S.M.A.R.T. data is GOOD status on both drives, and Raid Type lists "none"...
So, Tom's Nation -- Any bright ideas to try??
-Thanks in advance
Ryno
We have this old WD MyBook Live DUO POS 6TB device whose enclosure took a crap on itself. Heat is my guess personally these things were blazing hot after trying to get the software to recognize the unit. The drives were yanked and slaved to other machines and all Windows 7 64-bit machines show the drives like this:
Both Drives show up in disk mgmt, both show "healthy" primary partitions and both are accessible to DISKPART. However, no volumes populate, drive letters cannot be assigned and some commands are unsuccessful. BREAK has no effect, converting to MBR doesn't work (although I assume that is because of the 2.2TB cap on MBR parts), and converting to Dynamic simply wipes out the lead reserved partition of the 5. Assuming it destroyed that one because of GPT structure.
So my guess is that this used to be a mirrored array as opposed to striped, and I'm not sure those DUO's could even be configured as JBOD - however I would think the partition layout would not be the way it is if THAT were the case. But no one knows for certain. Now I don't really know what all transpires when a RAID set is created or how anything is formatted partition layout wise, so running a bunch of utilities similar to /fixboot such and such or running it through SPINRITE (these are spindle drives) and burning all that time is not what I wanted to do without some minor feedback and checking. Because maybe there is a quick simple answer from someone whose experienced this. I also will probably just start messing with one disk as I probably have a viable second disk in case of emergency or disk utility foul up. My worry is if I foul up one disk and the other was actually a bad disk then I've lost both.
I would also like to assume that only ONE of these disks could be considered "bad" as it is unlikely both failed simultaneously. Meaning whatever is happening is more likely to be some raid formatting issue or something to the like. If I can undo that mystery operation maybe I can salvage the drive's data. I know my current machine which is housing the drives is Sata 6Gb capable so it's not a platform issue either. And obviously if I can see the drive is not a UEFI There is no horrible "clicking of death" and here is the kicker: Speccy informs me all S.M.A.R.T. data is GOOD status on both drives, and Raid Type lists "none"...
So, Tom's Nation -- Any bright ideas to try??
-Thanks in advance
Ryno
Facebook
Twitter
Instagram