September 20, 20169 yr Hi folks, I added a new 5TB HGST drive to my 6.2.0-rc4 server that will eventually be my new parity drive. The pre-clear is running very slow. From what I can tell from the gui, the disk being pre-cleared is spinning down. I've attached the diagnostics. Pre-clear is 2016.08.26b, which I believe was the latest available when I started the pre-clear a week ago. Please let me know if there's anything else I can attach to help diagnose. Note the average vs the current speed in the pre-clear. server1-diagnostics-20160920-0535.zip
September 20, 20169 yr Author ############################################################################################################################ # # # unRAID Server Pre-Clear of disk /dev/sdc # # Cycle 1 of 1, partition start on sector 64. # # # # # # Step 1 of 5 - Pre-read in progress: (53% Done) # # # # # # # # # # # # # # # # # # # # ** Time elapsed: 183:47:08 | Current speed: 152 MB/s | Average speed: 4 MB/s # # # ############################################################################################################################ # Cycle elapsed time: 183:47:26 | Total elapsed time: 183:47:26 # ############################################################################################################################ ############################################################################################################################ # # # S.M.A.R.T. Status # # # # # # ATTRIBUTE INITIAL STATUS # # 5-Reallocated_Sector_Ct 0 - # # 9-Power_On_Hours 23 - # # 194-Temperature_Celsius 31 - # # 196-Reallocated_Event_Count 0 - # # 197-Current_Pending_Sector 0 - # # 198-Offline_Uncorrectable 0 - # # 199-UDMA_CRC_Error_Count 0 - # # # # # # # # # # # ############################################################################################################################ # SMART overall-health self-assessment test result: PASSED # ###########################################################################################################################?
September 20, 20169 yr You should post the diagnostics file (Tools->Diagnostics) so that we can see what (if anything) is being recorded to the syslog (as well as other useful diagnostic information).
September 20, 20169 yr Author You should post the diagnostics file (Tools->Diagnostics) so that we can see what (if anything) is being recorded to the syslog (as well as other useful diagnostic information). Sorry, it says it's attached, am I misreading it?
September 20, 20169 yr You should post the diagnostics file (Tools->Diagnostics) so that we can see what (if anything) is being recorded to the syslog (as well as other useful diagnostic information). Sorry, it says it's attached, am I misreading it? Sorry - I was looking at your second post and missed it being present on the first one. One thing I notice is that the syslog is full of messages of the form Sep 12 12:48:01 Server1 crond[1495]: exit status 127 from user root /usr/local/sbin/monitor &> /dev/null Not sure what is causing these but they are definitely unusual. I could not see anything relating to the drive being precleared, but with so many of the message above it is possible I missed it.
September 20, 20169 yr Author Ok, I think that's coming from this: # Generated system monitoring schedule: */1 * * * * /usr/local/sbin/monitor &> /dev/null Not sure if I can safely remove that, I'm assuming it's from some system monitoring. I killed it for now, which seems to have stopped it.
September 20, 20169 yr You have to stop the current operation, and then restart it increasing the read size to something greater than 256MB.
September 20, 20169 yr Author Woah, thanks, did that and it's flying, 6% already. Thanks, and sorry if I missed that in the documentation somewhere.
Archived
This topic is now archived and is closed to further replies.