Hi all,

 

Just purchased unraid and have only just completed my first build and move of 20TB of data into the array. All went smoothly with the copying of the data from  seven NTFS formatted disks (one at a time into the array). The approach I took was to copy each disk, stop the array and add the disk into the array (without parity enabled).

 

The parity create process is underway right now. During this one of the disks (close to full), has reported an error via eMail. I logged in and found it has an error counter of 31 against it. The smart status has a reallocated sector count of 1 and a Current pending sector count of 1.

 

The syslog is showing 31 errors such as:

 

Sep 22 23:05:19 Moose kernel: md: disk3 read error, sector=4878286352

Sep 22 23:05:19 Moose kernel: md: multiple disk errors, sector=4878286352

Sep 22 23:05:19 Moose kernel: md: disk3 read error, sector=4878286360

Sep 22 23:05:19 Moose kernel: md: multiple disk errors, sector=4878286360

Sep 22 23:05:19 Moose kernel: md: disk3 read error, sector=4878286368

etc.

 

 

There are 31 of these pairs of messages all for different sector numbers (seems to agree with the error count in the Main Tab).

 

Parity creation is still running and it's due to complete in another 4 hours.

 

I don't understand how I have 31 different sector errors, but only 1 pending sector count and what I should do next.

 

Thanks. Even though it's early days for me with Unraid, and I have lots of learning to do, I'm very pleased to have made the move from my old solution which was Windows based.

 

Could I have some advice please as to an appropriate course of action.

 

Edit: Also forgot to add, I am currently running version 6.1.9

Do you still have backups of what's on that disk?

 

Also, you should always post the diagnostics.

Hi

 

Thanks for the reply. I don't have backups as I was moving the data into the array from my old solution one disk at a time. Whilst there is a large amount of data on the disk (nearly 3TB), none of it is critical. It'll be a pain to recreate and I'd like to avoid that if possible.

 

Please forgive the noobie question (I've only just started using Unraid), but what sort of diagnostics would be helpful when posting questions?

 

Tools -> Diagnostics - attach zip

 

If you have a spare I would stop the parity sync, replace that disk with a new one, mount the old one on the cache slot (or using the unassigned devices plugin), copy all data you can to the new disk, start new parity sync.

 

You should be able to copy most of the data, then depending on how adventurous you are with your disks you can try and run a few preclear cycles and check if pending sectors go to and stay at 0.

 

 

Please forgive the noobie question (I've only just started using Unraid), but what sort of diagnostics would be helpful when posting questions?

Using the Tools->Diagnostics menu option (or typing in the diagnostics command at the command line) gives you the diagnostics file that is wanted.

Thanks very much for your replies. There's lots for me to learn, so I truly appreciate your assistance.

 

Here is the attached diagnostic file

 

moose-diagnostics-20160923-0102.zip

It really look like a disk error, also disk shows multiple read errors in the past, I would never use it again, even if pending sectors goes to 0.

 

 

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       90%     33225         583321145
# 2  Short offline       Completed without error       00%     30427         -
# 3  Short offline       Completed without error       00%     21291         -
# 4  Extended offline    Completed without error       00%     13578         -
# 5  Short offline       Completed without error       00%     13570         -
# 6  Extended offline    Aborted by host               90%     12863         -
# 7  Short offline       Completed without error       00%     12863         -
# 8  Extended offline    Completed: read failure       90%     12855         2909754224
# 9  Short offline       Completed: read failure       90%     12855         2909754224
#10  Short offline       Completed: read failure       90%     12855         2909754224
#11  Extended offline    Completed: read failure       50%     12780         2909754224
#12  Short offline       Completed without error       00%     12777         -
#13  Extended offline    Completed: read failure       90%     12774         132032744
#14  Short offline       Completed without error       00%     12773         -
#15  Extended offline    Completed: read failure       90%     12634         2909770568
#16  Short offline       Completed: read failure       90%     12634         2909770568
#17  Extended offline    Completed without error       00%     10414         -
#18  Short offline       Completed without error       00%     10407         -
#19  Short offline       Completed without error       00%     10405         -
7 of 8 failed self-tests are outdated by newer successful extended offline self-test # 4

Thanks for all your help. I'll buy a new disk tomorrow and send that one to the bin.