rickardk

Thanks!

Upgrading 2x WDC WD10EACS to 2x WDC WD20EARX Method: - First Parity-Check - Upgrade/Rebuild - Second Parity-Check # Disk 1 First Parity-Check: No errors Upgrade/rebuild without errors Second Parity-Check: Finding 6 errors I just ignored this and moved on to the second disk # Disk 2 First Parity-Check: No errors Upgrade/rebuild without errors Second Parity-Check: Finding 7 errors Both times the errors appeared within the first second after starting the second Parity-Check Does this mean that the rebuild failed in some way or is it something else? RAM is good (48 hours of Memtest) and I get no Parity-Check errors after writing 1 TB + of data to the new disks

Thanks! Just replaced the disk and rebuild started.

Dec 4 14:16:26 UNRAID2 kernel: sd 5:0:0:0: [sdt] Attached SCSI disk (Drive related) Dec 4 14:16:26 UNRAID2 kernel: ata20: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related) Dec 4 14:16:26 UNRAID2 kernel: ata20.00: qc timeout (cmd 0xec) (Drive related) Dec 4 14:16:26 UNRAID2 kernel: ata20.00: failed to IDENTIFY (I/O error, err_mask=0x4) (Errors) Dec 4 14:16:26 UNRAID2 kernel: ata20: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related) Dec 4 14:16:26 UNRAID2 kernel: ata20.00: ATA-8: WDC WD20EADS-00R6B0, 01.00A01, max UDMA/133 (Drive related) Dec 4 14:16:26 UNRAID2 kernel: ata20.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA (Drive related)

Server disabled disk 3 while my movie scrapper was updating nfo-files (on all disks). Reiserfsck on disk3 returned no errors and no SMART errors. Can it be a controller going bad on me? This was yesterday and since then I had to hard reboot two times cause the machine stopped responding. In unmenus syslog-viewer I can see a couple of red areas. Please can anyone tell me what to do. Syslog attached syslog-2011-12-04.txt

Thanks for the fast answer. And thanks for myMain!! I will replace thoose disks asap.

Could you guys give me some advice on this one? Time to replace some disks? If so, can I swap them (1TB/2TB) out for WD10/20EARS disks without problems?

There is now a separate installable package for the disk drive overtemp shutdown of the unRAID server. I made it a separate package so it could perform its check every 5 minutes rather than once an hour. - If you have the "powerdown" package developed by WeeboTech, it will use it. - If you do not, and you have a recent version of unRAID with its version of "powerdown" it will use it and if the array is not stopped after 5 minutes it will force a poweroff after attempting to stop the array. - If you have an older version of unRAID, it will attempt to stop the server cleanly and then use the poweroff command. There is a configuration variable for an early "Warning" message threshold temperature and a separate "Overtemp Shutdown" threshold. There is also a variable to set the e-mail address to send those alerts. Use the check-for-updates button on the user-scripts page to get the new package. Have fun. It looks like this: Joe L. Fantastic!!! Thanks again for all the effort you have put into unMENU.

Thanks again!!

Is there a way to let unraid_notify-2.5.5 make use of the unMENU package for the powerdown add-on instead of the powerdown supplied by lime-tech? Just entering powerdown seems to default to the one supplied by lime-tech.

Great!! Yes, I think one temp for warning and another one for shutdown should cover.

Great work with the new unMENU. I'm still using v1.2 and will update today. I have one question though: Are the unRAID Status Alert package (or another package) able to run the Power down script (http://lime-technology.com/wiki/index.php?title=Powerdown_script) when the temperature (on any disk) exceeds a user configurable value. I use unraid_notify that is able to do that now.

Does it work with latest 4.5beta11?

http://lime-technology.com/forum/index.php?topic=3391.0 Does 4.5-beta2 solve this issue?

# Choose the critical disk temp. (in celsius) that will cause unraid_notify to execute an external # command (like powerdown - see: http://lime-technology.com/wiki/index.php?title=Powerdown_script ) CriticalDiskTemp = 37 CriticalDiskCommand = powerdown This should power down my machine when 37 C is reached right? Does not work if a file is open (like watching a video file). I guess I'm doing something wrong. The powerdown script is installed and working when executed manually with "powerdown" trough telnet. # Choose the maximum temp. (in celsius) a disk may get before an error will message will be sent. MaxDiskTemp = 30 This does send me an email though. Values set low just for testing...