JorgeB

Sorry about that, I use adblocker so don't see them, post edited.

I'd really like to see an option to display slow sectors, I've been using MHDD, it's the first thing I do on any new disk, before preclear, any disk with abnormal slow sectors doesn't go in my servers, because in my experience these will turn to bad blocks sooner rather then later, and until that happens SMART looks perfect. Also use it when I suspect a disk has developed some, e.g., parity check slows down considerably, unfortunately MHDD is not practical to run on server installed disks because it only works with onboard ports in IDE mode, doesn't work in AHCI or HBAs. Here's an example of a recent one, WD Green 3TB, parity check took 3 more hours than usual, after identifying disk, had several zones with read speeds <1MB/s, replaced it and used it for a while on my test server, after 3 or 4 parity checks had a lot of pending sectors. Perfect SMART report before it was replaced: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 1512 3 Spin_Up_Time 0x0027 176 174 021 Pre-fail Always - 6200 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 102 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 683 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 55 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 4 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 98 194 Temperature_Celsius 0x0022 126 117 000 Old_age Always - 24 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0

Note that when adding a new disk unRAID will always say that it's going to be cleared next to the start button, the difference is that when starting the array a precleared disk is not cleared. P.S. just found that v6.2-beta clears a new disk online, this does not replace preclear as a way of stress testing a new disk.

Thanks!

Agree that it shouldn't be a problem, but most disks, including this one, have a max operating temperature of 60C.

That would be better, 2 clicks instead of 3, was just thinking that I would really like to have it in the main bar, I know the space is limited but for my NAS only servers that don't use dockes/vms there's still a lot of space and would just need a single click, naturally this should be optional as many users don't have the space or would not want it there.

SMART looks fine, at least once reached 57C, not ideal but not over the limit, so it should be fine.

Request: Option for selecting which page displays by default when clicking the plugin. I find that except for the initial config 99% of the time I want the "Control" page, so it would be nice to have the option. Thx.

Parity2 rebuild will take a wile, approximately the same as a parity check, the data disk will be added instantly if successfully precleared.

Don't remember seeing that error before, you can try the new beta plugin: http://lime-technology.com/forum/index.php?topic=39985.msg453938#msg453938

Are your disks reiserfs or xfs? Reiserfs is known to cause erratic write speeds even with empty disks and timeouts with almost full disks.

I believe that attribute does not mean the disk is bad for sure, and I've seen many disks here on the forum, especially Seagates, with much larger values and still ok, but it's certainly not good, if you can get a new one go for it.

Agree, looks better.

I like your choices, including the command_timeout attribute, maybe also high_fly_writes, though this one is mostly for seagates, on the other hand the more attributes are displayed the more confusing it is for less experienced users...

Yes, but that those values are the same on all Seagates (or at least most recent models), it's not because of internal testing.

For the 1st two the important thing here is that both new and old values are the same, they come near threshold from new, e.g., a single end-to-end error will trigger a SMART failing now. The 3rd attribute is temperature, it will trigger a SMART failure at 45C, after the disk cools down it will show "failed in the past". So all looks good, nothing to worry about.

There are two different plugins, the original one on the first post uses the old script and it's not v6.2 compatible, the new beta is: http://lime-technology.com/forum/index.php?topic=39985.msg453938#msg453938

Yes it did! With a preclear going it just took 1 or 2 seconds more than usual to start the array after a new config. Thanks! Great work!

For me only while writing, no issues when it’s reading. Pretty sure is the sync command hanging the webui. When it hangs stoping the array, status line on the WebGUI displays "syncing..."

For me only while writing, no issues when it’s reading.

That sounds like a good idea, because normally stopping the array during a preclear sometimes also takes a long time.

Do what gfjardim asked a few posts above and upload your log.

I didn’t want to stop the 3 disks that are preclearing on that server so I was trying it on my test server, and I see now that it only hanged because I assigned the disk to array and started it after starting the preclear. As long as I’m not starting a new array for the first time I can start the array with a preclear going, so this is a very specific use case, still attached log in case you want to have a look. BTW, is there a command I can use to see the progress of the 3 preclears that I have going on the hanged server? preclear.disk.beta.txt

You can only preclear unassigned disks, I'm preclearing 3 disks and trying to start the array with another disk.

ok