Hi Guys,

 

Really hoping someone can help.

 

A week ago I added a new 5th disk to my array as I was running out of space, this disk was added successfully..

A couple of days later I noticed it had errors on it so checked the logs and saw it had bad sectors so I took it out hoping the store would replace it but they needed for a couple of days for testing, so I ended up buying  another disk and as I was pre-clearing the new disk to replace the other drive I just bought a week ago in the array I lost another disk fml . now I cannot do anything I cannot bring my array online (Too many wrong and/or missing disks!)

 

Please can someone tell me there is way of fixing this, I have to much data that I don't want to lose..

 

 

Thanks in advance

 

nas-diagnostics-20170515-2248.zip

Edited May 15, 20179 yr by MxFox

First, do not panic.  It is very unlikely that you have lost any data!  The first thing you need to do is to upload the diagnostics file.    'Tools'   >>>   'Diagnostics'.  Then settle back and wait for a response.  Stop any uploads to the array, whether by you or some automated process, until you can get this resolved.   

You should post your diagnostics file (Tools -> diagnostics)

 

I will tell you that it is unusual for so many drives to fail in short proximity.  It is much more common that you have cabling problems, PSU problems, controller problems, or something like that. In those situations, you can typically correct the problem and access the data on the disks that appeared to fail.

 

Be careful, as trying to recover without a sound strategy puts you at more risk for loss than leaving things alone, and allowing time for knowledgeable forum members to review your logs and give you advice.

 

Is there any data on the 5th drive that you returned to the store that you are worried about? If so, I would retrieve the disk before they run their diagnostics. Their diagnostics may write to the disk and eliminate any chance of recovering that data. But for drives in your hands, I think a little patience will likely yield a good outcome.

22 minutes ago, Frank1940 said:

First, do not panic.  It is very unlikely that you have lost any data!  The first thing you need to do is to upload the diagnostics file.    'Tools'   >>>   'Diagnostics'.  Then settle back and wait for a response.  Stop any uploads to the array, whether by you or some automated process, until you can get this resolved.   

Thank you, I have added the Diagnostic file, yes i have stopped all uploads and have not tried to fix the issue either just in case i make it worse...,

24 minutes ago, bjp999 said:

You should post your diagnostics file (Tools -> diagnostics)

 

I will tell you that it is unusual for so many drives to fail in short proximity.  It is much more common that you have cabling problems, PSU problems, controller problems, or something like that. In those situations, you can typically correct the problem and access the data on the disks that appeared to fail.

 

Be careful, as trying to recover without a sound strategy puts you at more risk for loss than leaving things alone, and allowing time for knowledgeable forum members to review your logs and give you advice.

 

Is there any data on the 5th drive that you returned to the store that you are worried about? If so, I would retrieve the disk before they run their diagnostics. Their diagnostics may write to the disk and eliminate any chance of recovering that data. But for drives in your hands, I think a little patience will likely yield a good outcome.

thank you for the reply, i only lost one drive but unfortunately since i added the new drive a week ago and that had issue i went to swap it out and now while pre-clearing the new drive again i lost an old drive i think its just bad timing, i have checked all my cabling and the controller and all seems in order, thanks for the advice  

This is most likely from the missing disk:

 

May 15 22:47:01 NAS kernel: ata2: softreset failed (1st FIS failed)
May 15 22:47:01 NAS kernel: ata2: limiting SATA link speed to 1.5 Gbps
May 15 22:47:01 NAS kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 15 22:47:01 NAS kernel: ata2.00: link online but device misclassified
May 15 22:47:01 NAS kernel: ata2: link online but 1 devices misclassified, device detection might fail

 

Try again using a different SATA port, also replace both cables just to rule them out, unless you can get it back online and the disk is in good shape it will not be possible to recover any data from disks 1 and 5.

I can comment on the disks in the array.

 

No bad or pending sectors - which is good!

 

TDW (Seagate 2T):

 

The value of 30 is low. But the value of 7 (worst it has been) is very low. This indicates the drive's ability to correct data read from the disk surface. Normally the value should be around 100. I would be looking to replace this drive in the not too distant future.

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
195 Hardware_ECC_Recovered  0x001a   030   007   000    Old_age   Always       -       63507896

 

374 (Seagate 2T)

 

Looks ok - but following is a little unusual. The value and worst are both "1". Never seen values so close to zero! But I don't think this is a serious problem. Loading and retracting the heads is not a typical sign of disk failure. And I think this rating is based on the 231,478 number, not based on any mechanical issues. Some drives have setting to decrease the frequency of head parking and slow down this number.

 

I'd keep an eye on it, but not as concerning as drive above IMO.

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
193 Load_Cycle_Count        0x0032   001   001   000    Old_age   Always       -       231478

 

TZ2 (WD 2T)

 

Similar to drive above. WD is sort of notorious for driving this attribute up, but even so, almost 690,000 head parks is very high. Again, never seen this cause a drive failure of any kind.
 

I'd keep an eye on it, but not as concerning as drive above IMO.

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
193 Load_Cycle_Count        0x0032   001   001   000    Old_age   Always       -       689605

 

Other drives are new. No issues.

 

Bottom line, I don't see anything overly concerning with the drives that are recognized. I expect you'd be able to get all or most of the data of of these drives.

Hi johnnie.black and bjp999,

 

thanks for you reply,

 

@johnnie Blask. its a hardware array so i would assume if it was cabling i would lose all 4 disks as it one cable into the motherboard but will double check everything is nice and tight.

 

@bjp999, thanks for check the rest of the disk, they are all very full about 100GB free on each one hence me trying to add another disk to the array, the disk that are currently there are also very old ..

 

So im assuming that my DISK1 has failed it's broken i'm not getting it back, is there a way to remove DISK5 as it is new and i did not have much data on it ? i can try make unraid think that there was only one disk failure and then i can add the new drive to disk1 so it can get rebuilt ?

 

Other than that what would i need to do to bring this array on line again ?

 

Thanks..

Edited May 16, 20179 yr by MxFox

40 minutes ago, MxFox said:

is there a way to remove DISK5 as it is new and i did not have much data on it ? i can try make unraid think that there was only one disk failure and then i can add the new drive to disk1 so it can get rebuilt ?

 

No, if you can get disk1 online and depending on if there were any changes to the array after it went offline, you may still be able to recover data from disks 1 and 5.

 

If you can't get disk1 online you'll lose all data from both disks 1 and 5.

Hi guys,

 

Thanks for everyone's advice, input and just general trying to help...

 

So i have been able to test a bit further this evening and have found that DISK1 is completely dead if i swap disk 1 for a new disk the array picks it up instantly..

 

So am i safe to assume i have lost all my data on DISK1?

 

is there is nothing i can do to make unraid rebuild the new disk, is there no hacks where i can in the config file remove disk 5 so it looks like i only had one disk fail and hopefully get unraid to rebuild DISK1?

 

thanks in advance

1 minute ago, MxFox said:

is there is nothing i can do to make unraid rebuild the new disk, is there no hacks where i can in the config file remove disk 5 so it looks like i only had one disk fail and hopefully get unraid to rebuild DISK1?

 

You could but without disk5 parity won't be valid and it would only rebuild garbage.