Hello Everyone,

 

I have been having ongoing issues with RC8 you can see my previous thread here:

http://lime-technology.com/forum/index.php?topic=24467.0

 

One of my drives Redballed but I know for a fact that the drive is still good, So I was copying data to the drive directly via it's independent drive share. I had an issue with Sabnzbd, so I rebooted unraid, unraid frooze up on me, so I had no choice but to perform a restart manually.

 

When Unraid RC8 came back up, The drive that had been previously red balled was now showing as OK, and 300 gigabytes of data from that drive are now missing.

 

Is there any chance that I can get that data back?

 

Thank You

I did some more research and found this forum post:

 

http://lime-technology.com/forum/index.php?topic=5087.msg47070#msg47070

 

Gonna try it out and see if it works.

 

Thanks

Start with a -check. See my sig.

 

 

You can try with scan-whole-partition if that doesn't work.

What makes you think the drive is fine? If you're on a protected install and a drive is offline you can still copy to the disk share but the data doesn't goto the drive, you're relying on the parity safety net. I'm not sure exactly what occurred but drives don't show as bad for no reason, you're playing with fire...

Hello BLKMGK,

 

The drive is brand new, and while I know that in itself does not mean the drive is good, allow me to explain further.

 

1. The drive passes S.M.A.R.T.

2. The drive passed a full Pre-clear.

3. The drive was completely successful in doing a full rebuild from a failed drive.

 

If you would like to know more about the drive, please read this thread

http://lime-technology.com/forum/index.php?topic=24467.0

 

I am fairly certain you will come to the same conclusion I have. I honestly believe the issue is more to do with RC8 than my drive.

 

I beleive you are correct in regards to the parity. I believe what happened is since the drive was showing as red balled, I was copying to parity instead of the actual drive, and when I rebooted, I lost that data. As I was unable to recover the data that I had lost, by running the reiserfsck command.

 

I would be happy to hear your input in the matter though.

 

Thanks for taking a look.

No, you weren't copying to parity but the parity drive was flipping bits so that it could do a parity calc and figure out what was supposed to be on the missing drive. Why it's disappeared and you're left with everything as if it were never there is a mystery and doesn't fit with my understanding of how unRAID works. I've copied and moved files with a drive missing - as in pulled from my system - and it's never gone missing upon a reboot. Yes, this was with RC8a. Something's not right with this scenario, perhaps it's the direct drive share? Has anyone else tried doing this? The drive shares should be as protected as anything else.

 

As for the drive - I've not seen anyone having issues with RC8a where drives go red for no reason. While the drive may have tested fine that still doesn't rule out cabling or mobo hardware. Something isn't right if it went red and especially if it's gone red more than once. The system had issues writing to the drive, the problem is what caused those issues and it could be multiple different things. IF I were having those kinds of issues I'd set the drive aside, try another, and if it too had issues I'd go further down the data path hardware wise.

I would wager that because the drive is now green and not red without a rebuild  (unraid didn't have to rebuild it the data putting that 300MB into the rebuild).. because of that. it knows nothing about the now lost data..  that is until you test parity.. it will probably fail and then it probably has no clue where to put that data...

 

I would try to run a parity check with correct set to off. see if you get any errors....

 

It is possible you might not have good parity anymore and your parity might be corrupt.

there is also a slight possibility that you can put a new 2tb in the slot that was red and rebuild the lost data if you have not already messed up the parity.

there is also a good chance that if any other drive fails right now, it will NOT be able to rebuild it based on the now bad parity info.

 

I would not try to rebuild the drive that WAS red drive. i would try a new drive to prevent any further data loss.

in the end you might have to rebuild parity.

I appreciate your replies guys :-)

 

At this point I gave up on recovering the data, I was able to recover about half of it that I had backed up on a older small drive.

I can't yet replace the drive as I don't have a viable replacement for it right now, but I have run a full parity check on it over night after copying the recovered data back to it, and it completed the parity rebuild.

 

So it looks like everything is good to go for now. If I have any more write errors to that drive, I will RMA it.

 

Thanks