CaptainTivo Posted October 5, 2018 Share Posted October 5, 2018 Yesterday I removed a disk to shrink my array and started a parity sync. About an hour later I got emails saying that several disk were overheating (50+ degrees C). I rushed home to find that a fan in the lower drive compartment had failed. I replaced the fan and restarted the array. The parity sync restarted and everything seemed fine. This morning I woke up to this email. And the Dashboard shows the parity disk in the "Faulty" column. Yet, when I go to "Fix Common Problems" nothing is showing. In the past, while rebuilding parity, Fix Common Problems has reported a warning not a fail. I don't see anything interesting in the logs. Should I be worried? unRAID Status: Notice [TOWER] - array health report [FAIL] Event: unRAID Status Subject: Notice [TOWER] - array health report [FAIL] Description: Array has 11 disks (including parity & cache) Importance: alert Parity - HGST_HUH728080ALE600_VKGWSJWX (sdg) - active 35 C [DISK INVALID] Disk 1 - WDC_WD20EARS-00MVWB0_WD-WCAZA4336067 (sdc) - standby [OK] Disk 2 - WDC_WD30EZRX-00DC0B0_WD-WCC1T1078908 (sdd) - active 32 C [OK] Disk 3 - HGST_HDN724040ALE640_PK1334PCJZXT9S (sdj) - active 36 C [OK] Disk 4 - WDC_WD30EZRX-00DC0B0_WD-WMC1T2463685 (sdb) - active 31 C [OK] Disk 5 - WDC_WD20EARS-00MVWB0_WD-WCAZA0765138 (sdf) - standby [OK] Disk 6 - WDC_WD30EZRX-00D8PB0_WD-WCC4N0899764 (sde) - active 31 C [OK] Disk 7 - WDC_WD30EZRX-00DC0B0_WD-WCC1T1338318 (sdl) - active 36 C [OK] Disk 8 - HGST_HDN724040ALE640_PK2334PCJWEV4B (sdk) - active 38 C [OK] Disk 9 - WDC_WD80EZAZ-11TDBA0_2TKWM5ZD (sdh) - active 34 C [OK] Cache - WDC_WDS500G2B0A-00SM50_181850802503 (sdm) - standby [OK] Parity sync / Data rebuild in progress. Total size: 8 TB Elapsed time: 7 hours, 30 minutes Current position: 2.44 TB (30.5 %) Estimated speed: 97.4 MB/sec Estimated finish: 15 hours, 51 minutes Sync errors corrected: 0 tower-diagnostics-20181005-0618.zip Link to comment
JonathanM Posted October 5, 2018 Share Posted October 5, 2018 3 minutes ago, CaptainTivo said: Should I be worried? Nope. The message is accurate, until the parity build completes your array is unprotected, thus FAIL, and the disk that is causing the fail is the parity, thus the DISK INVALID part. When the build is done successfully, the status will change. Link to comment
CaptainTivo Posted October 5, 2018 Author Share Posted October 5, 2018 8 hours ago, jonathanm said: Nope. The message is accurate, until the parity build completes your array is unprotected, thus FAIL, and the disk that is causing the fail is the parity, thus the DISK INVALID part. When the build is done successfully, the status will change. Thank you. I think I actually knew that but forgot :-) Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.