Ok I'll try to make this post condense. Been using unraid for years. Just built new system, some old and new HDD. Been using new system successfully for weeks. Parity checks have taken about 12 hours to complete, 26TB in system 13 HDD including Parity. Just recently file transfer seems fast but access to folders seem a bit slow, compared to my last and very old system.

 

Decided to do parity check Disk 1, I did leave the check mark next to 'Write Corrections to Parity Disk', which i'm not sure how this will affect things. The check says it's going to take 700 days to complete and shows almost as many Errors as Writes, but NO red ball next to drive 1.

 

So what does that mean? Please help, let me know what I should do next. Thanks. I tried to attach my systlog, but the forum is saying it's too big. The zip file is over 1mb. The file itself is 19mb. That seems excessive. Should I be concerned?

 

Your post was entirely too condensed. 

 

What version of unRAID are your running?

 

What is this 'parity check Disk 1'?  Parity checks are run on the entire array.

 

Which disk is showing errors?

 

What I would suspect from your description thus far is that you have at least one hard disk that is failing.  (Based on the fact that write speed is unaffected while read speed is slow when you access a shared folder---which requires accessing a disk with a read problem to get files information about files on that disk.)

Gotcha. V6.0-rc5.

 

I ran a parity check and disk 1 showed as many errors as writes.

 

So if I have a failing disk should I just replace the disk and rebuild it? I'm only asking because when I did the parity check I left 'Write corrections to parity disk' check marked and I wasn't sure if that affected the parity?

 

Or should I use Putty and transfer the files from that disk to another one, or is that data on disk 1 now corrupted?

Post a SMART report. Put the syslog on pastebin or dropbox or google docs, or the file sharing service of your liking.

You can get the SMART report by clicking on the 'Disk 1' on the 'Main' page.  There will be a download 'Download SMART Report' Button there.

Thanks frank, I was gonna ask how to do that. I read the tutorial on Smart report, but it didn't seem to work, but then again I don't know much about command line stuff.

 

Here is the link to my syslog.

 

https://www.dropbox.com/s/9t4hih2tyzuer0d/tower-syslog-20150626-1105.zip?dl=0

tower-smart-report-disk1-20150626-1457.zip

It seems now I can't even open folders without it taking quite a while or even 'not responding'. I can't even play music from the Unraid.

Replace disk1. After the rebuild and subsequent parity check completes then run pre-clear in the faulty disk.

Cool thanks. Just so I'm clear.

 

Shut down unraid > remove old drive and replace with new one > start up unraid > mount new drive and rebuild drive > after rebuild run parity check > if everything checks out I can install the old drive in a new slot and run pre-clear on the old disk if I want to reuse it?

 

I have couple other questions. What do the red hands on the smart drive page mean? And does it matter that I'm using two different file systems, reiserfs and xfs?

Cool thanks. Just so I'm clear.

 

Shut down unraid > remove old drive and replace with new one > start up unraid > mount new drive and rebuild drive > after rebuild run parity check > if everything checks out I can install the old drive in a new slot and run pre-clear on the old disk if I want to reuse it?

Yes.

SMART

I have couple other questions. What do the red hands on the smart drive page mean?

SMART status? Show a sceen-shot.

And does it matter that I'm using two different file systems, reiserfs and xfs?

Does NOT matter. My old disks use RFS and my new ones use XFS.

OK Thanks a bunch people. Rebuilt the drive in like less than 3 hours. Ran a parity check and it found 5 errors, I assume that's not uncommon. The parity check took about 13 hours. So all is good. WOO HOO.

 

I think I'll just trash the old drive. Also after the parity check I don't get any red hands for my smart drives.

Parity check should find zero errors; although, having a few after a rebuild is not uncommon. Run parity check again.

Ok will do. Thanks.

When you run a parity and it finds errors where do you find out where these errors were found, in the syslog or does the parity script output to a file that is saved? After my re-build I found 3 or 5 errors and wanted to re-visit that.

 

I'm using V6 and it says it on the main page, 5 errors found.

I'm using V6 and it says it on the main page, 5 errors found.

 

Yea, got that but if that's all the information there is available on the errors then there isn't much to go on to fix it, is there?

 

I have no idea. I'm no expert.

The syslog will log the parity errors but it has no way of knowing which disk because of the way single parity works.