CupCak3

Anyone, please? Thanks!

I've ran 4 preclears on my new Samsung 2TB F3 HD203WI. No problems except for the following errors: Oct 8 12:28:03 Tower preclear_disk-start[4799]: 1 Raw_Read_Error_Rate 0x002f 252 252 051 Pre-fail Always - 0 Oct 10 07:21:47 Tower preclear_disk-start[5998]: 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 38 Oct 12 00:20:50 Tower preclear_disk-start[30688]: 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 64 Oct 13 08:42:33 Tower preclear_disk-finish[4552]: 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 94 Oct 15 05:30:19 Tower preclear_disk-finish[14054]: 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 121 Oct 8 12:28:03 Tower preclear_disk-start[4799]: 200 Multi_Zone_Error_Rate 0x002a 252 252 000 Old_age Always - 0 Oct 10 07:21:47 Tower preclear_disk-start[5998]: 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 3 Oct 12 00:20:50 Tower preclear_disk-start[30688]: 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 4 Oct 13 08:42:33 Tower preclear_disk-finish[4552]: 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 4 Oct 15 05:30:19 Tower preclear_disk-finish[14054]: 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 5 Is it OK for me to use this drive? I'm very much concerned with the always rising Raw_Read_Error_Rate numbers. Thanks!

Sorry for the late reply but work and family time have taken me away the past couple days. I have 5 disks and put all the reports in one txt file. Each disk is separated by ----- starting with sda then sdb.. etc. Thanks for the help; its much appreciated! I know, I know. My old APC died and I haven't bothered replacing it. Definitely need to get that taken care of sooner than later Dumb question; how do I figure out the block #? I haven't "fixed" the error yet. smarta.txt

I think I may have had a power outage since my last parity check. Would you rather see the results from the long or short smart tests? Thanks for the help and your prompt response!

I’m currently using Unraid 4.5.3 and Unmenu 1.3 Last night I queued a bunch of files to transfer via FTP and didn’t check again until the next morning. What I did not bother to verify beforehand is that I had enough free space. When I woke up this morning, I found the FTP client still transferring files. After watching it for a min. or two, I saw that the transfer was failing b/c the drives are full and client restarting the transfer! I quickly calculated this happened 900-1000 times looking at the syslog transfer times. I so then started a parity check without correction to ensure there were no problems with my drives. It found one error pretty close to the beginning and none after that. How do I find which drive and file has the parity error? Could a non-hard drive issue have caused this? Is there anyway to verify if a hard drive is going bad aside from fixing the parity and waiting to see if I find more errors in future checks? I was really hoping this is something I would not have to deal with until a much later time... the oldest drive is less than two years old and they all have active cooling on them. Thanks!

Nice find Joe. What are you planning to use for HDD mounting in the 5.25" bays? I've seen some nice 5.25" hotswapable mounts which look decent but requires 3 bays and would not make efficient use of the available bays

Joe, thanks for the quick response. I figured the drive was OK but just wanted to make sure.

These are the results after running preclear on a new 2TB Samsung drive for use as my parity drive. ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 55c55 < 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 0 --- > 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 10 72c72 < 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 1 --- > 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 3 ============================================================================ Should I be worried and run through preclear again or am I looking too much into this? Thanks!

Export your shares as "read-only." Use read-write for when you are actually writing, or write to the disk-shares (exported as read-write, but hidden, or define a different user for writing. Lots of possibilities. wow, that is almost embarrassingly easy... looks like I have some reading to do! Thanks! Joe L.

I was afraid of that Does anyone know if there anyway to turn these writing "features" off? Is there a player which does not utilize them? Like I said before, it's not a huge deal, I'd just like to minimize some wear on things. Thanks!

Thank you for the quick response Rob I'm not currently running any addons to the server. When doing some trials on the disk writes, I close everything but the player which would have access at the time to the drive (including the window with the directory listing...I know a bit overkill...). The files I'm playing are encoded in x264 within an mkv container. I've played the files with WMP, MPC, and video lan. Each player has the same "issue". ffdshow is used to decode audio and video. The writes to the disk do not happen while video is not streaming. Thanks again.

I've been lurking for a while but this is the first time I've had a question I could not find an answer to... I've noticed that while I'm streaming a movie from my array that writes also occur to the array (data drive and parity of course...). Does anyone know what is causing the writes to the drive while watching a movie and is there any way to stop it? I'm not hugely concerned but anything I can do to decrease "wear" on the parity drive, I'm all for. This probably doesn't make a difference but I'm using the Pro version of the latest beta. Thanks!