Hi,
I have a weird problem which I don't understand how it occurs..
My mainboard is Asrock C2750D4I with a LSI SAS2008 card which is detected as SAS9211-8i. Also I have an Intel Expander connected to this, and currently 20 disks are connected to the expander. I'm currently using 12 of them in an active RAIDZ2 pool with 8 of them not assigned to any pool yet.
The disks I'm using in the pool are all new WD Red 6 TB disks.
I'm using the pool for mainly media storage ( for TV shows/movies ).. I use sabnzbd or deluge for downloading and sickrage and plex for cataloging.
One day, deluge said there was an error in a torrent. Which was around 500 GBs ( one torrent file, mind you ). I am not sure but it was around 80%-90% before error occurred. When I rehashed the torrent it said it's now 0,04%.. Of course I'm confused because as far as I know it was about 200 files. When I checked the directory I found only three files. All the other files were gone.
Another day, sabnzbd said it cannot write a parity file on the disk, which I don't understand because it could write another parity file just fine into same directory. When I checked, the main cause for this error is generally because the path + filename is too long for the filesystem.. That's why I checked another parity file.
When all of these happening there were no errors logged.
But, after this failures I scrubbed the pool. Here is the scan result:
scan: scrub repaired 508K in 59h33m with 0 errors on Mon Nov 6 11:46:40 2017
As you can see there were some problems but they're fixed. I also saw some CAM errors and also saw three disks as repairing while scrub was running. But as a result there are no read/write or checksum errors noted in status because most probably parity information was enough to fix those errors. I should mention BTW, I'm using 32 GB of ECC RAM, so I don't think this is caused by bad RAM.
What do you think? What may be the cause of the errors? How could an error like this happens?
I have a weird problem which I don't understand how it occurs..
My mainboard is Asrock C2750D4I with a LSI SAS2008 card which is detected as SAS9211-8i. Also I have an Intel Expander connected to this, and currently 20 disks are connected to the expander. I'm currently using 12 of them in an active RAIDZ2 pool with 8 of them not assigned to any pool yet.
The disks I'm using in the pool are all new WD Red 6 TB disks.
I'm using the pool for mainly media storage ( for TV shows/movies ).. I use sabnzbd or deluge for downloading and sickrage and plex for cataloging.
One day, deluge said there was an error in a torrent. Which was around 500 GBs ( one torrent file, mind you ). I am not sure but it was around 80%-90% before error occurred. When I rehashed the torrent it said it's now 0,04%.. Of course I'm confused because as far as I know it was about 200 files. When I checked the directory I found only three files. All the other files were gone.
Another day, sabnzbd said it cannot write a parity file on the disk, which I don't understand because it could write another parity file just fine into same directory. When I checked, the main cause for this error is generally because the path + filename is too long for the filesystem.. That's why I checked another parity file.
When all of these happening there were no errors logged.
But, after this failures I scrubbed the pool. Here is the scan result:
scan: scrub repaired 508K in 59h33m with 0 errors on Mon Nov 6 11:46:40 2017
As you can see there were some problems but they're fixed. I also saw some CAM errors and also saw three disks as repairing while scrub was running. But as a result there are no read/write or checksum errors noted in status because most probably parity information was enough to fix those errors. I should mention BTW, I'm using 32 GB of ECC RAM, so I don't think this is caused by bad RAM.
What do you think? What may be the cause of the errors? How could an error like this happens?
