Buffalo Forums

Products => Storage => Topic started by: nadamsmasd on June 25, 2018, 07:43:30 AM

Title: 1 failed drive in RAID 10 pair caused 2nd drive to be marked bad
Post by: nadamsmasd on June 25, 2018, 07:43:30 AM
I have a situation with my Terastation TS-XEL. Drive 1 in the unit failed, and when it did so, drive 2 in the unit also got marked as bad. Initially, I thought that drive 1 was just locking up the controller for the pair, but after removing the failed drive, drive 2 is still marked as having an error. Since these two drives were one of the 2 mirrored pairs, the RAID array will not mount.

I have checked drive 2 with another computer, including doing a bad sector scan, and everything comes up good. My belief is that it's an issue with the partition tables or something else that got corrupted when drive 1 started failing.

Are there any tricks to getting this drive back online so I can rebuild the array?
Title: Re: 1 failed drive in RAID 10 pair caused 2nd drive to be marked bad
Post by: davo on June 25, 2018, 08:35:27 AM
Do you have a backup?
Title: Re: 1 failed drive in RAID 10 pair caused 2nd drive to be marked bad
Post by: nadamsmasd on June 25, 2018, 08:42:53 AM
Quote from: davo on June 25, 2018, 08:35:27 AM
Do you have a backup?

Fairly certain you know the answer to that already. The data was not deemed to be important until it was no longer available.  ::)

My alternate plan is to scan the drive with an undelete program and see if I can recover anything. But I thought I'd ask first if there was any way to get the Terastation to see the drive as "good" again.
Title: Re: 1 failed drive in RAID 10 pair caused 2nd drive to be marked bad
Post by: oxygen8 on June 25, 2018, 10:03:13 AM
try ufsexplorer with the 2. disk
Browser ID: smf (is_webkit)
Templates: 1: Printpage (default).
Sub templates: 4: init, print_above, main, print_below.
Language files: 1: index+Modifications.english (default).
Style sheets: 0: .
Hooks called: 64 (show)
Files included: 27 - 1055KB. (show)
Memory used: 719KB.
Tokens: post-login.
Queries used: 14.

[Show Queries]