November 8, 20205 yr Hi all, Been using Unraid for 6months now, and successfully dealt with a failed disk couple months ago. I got really worried yesterday when I got 7 read errors on 2 disks (disk 1 and disk 2). When I stopped the array, these 2 disks along with a unassigned device could not be detected by the system. Below are some details. below is an unassigned device (expected to fail soon). syslog was full of these, spammed every couple seconds for almost a day and half... tower-syslog-20201108-0739.zip Since the system was not detecting 3 HDDs, I restarted the server in safe mode. All 3 missing HDDs came back. So I started running extended SMART tests on each. disk 1 smart 2020-11-08.txt disk 2 smart 2020-11-08.txt unassigned smart 2020-11-08.txt All 3 HDDs which went missing completed SMART with no issues. My Disk 1 is new, only used for couple of months, but it still has many "pre-fail" and "old-age"... My Disk 2 is not new, but hasn't been heavily used, but it also has many "pre-fail" and "old-age"... My unassigned device disk is expected to fail any day now. but there's nothing critical on it and shouldn't cause any havoc on the system. But even this one came back as fine... So basically, after completing SMART tests without error. I've rebooted the system to be running normally. All 3 HDDs were detected, and many dockers and VMs started automatically without issue. The parity check is scheduled for later today. So that happened... What I'm wondering is that how worried should I be? and what preventative measures should I take?
November 9, 20205 yr Author Hi Jorge, thank you for taking an interest in this. I've attached the diagnostic report. Also, the parity check completed without any errors. tower-diagnostics-20201110-1026.zip
November 10, 20205 yr Community Expert Those diags are after rebooting, and the syslog you posted before is incomplete and doesn't show the beginning of the problem, did you save the complete diags before rebooting?
November 10, 20205 yr Author 1 hour ago, JorgeB said: Those diags are after rebooting, and the syslog you posted before is incomplete and doesn't show the beginning of the problem, did you save the complete diags before rebooting? unfortunately no. if it happens again, I'll do that for sure. Anything else to note?
November 10, 20205 yr Community Expert Just that the disks look fine, so likely a controller or power/connection problem, my money would be on a controller issue, since it's quite common with Ryzen boards and v6.8.
November 10, 20205 yr Author 13 hours ago, JorgeB said: Just that the disks look fine, so likely a controller or power/connection problem, my money would be on a controller issue, since it's quite common with Ryzen boards and v6.8. Thank you Jorge. That's a relief, I was really worried for my data for a while because the error spread to multiple disks.
Archived
This topic is now archived and is closed to further replies.