I'm in the process of getting my unraid pc setup, currently only has 3x 8TB drives (1 as parity).

 

For around a week I've been downloading zip files (up to 200gb) from a backup service as one hard drive got fried during the setup... 

 

I've was unzipping one of the archives and suddenly the drives seem to have stopped responding completely.

 

Can't view the shares, all docker containers are not working, no logs show in Unraid dashboard and no smart data is shown for the drives.

 

Smart data report just says:

 

smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.10.28-Unraid] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

Smartctl open device: /dev/sdh failed: No such device

 

It appears this is affecting both drives at the same time.

 

Oddly it appears Unraid OS is unaware of this as both drives show as "normal operation", although I did get an email notification with:

 

Quote

Event: Unraid array errors
Subject: Warning [ABC] - array has errors
Description: Array has 2 disks with read errors
Importance: warning

Disk 1 - TOSHIBA_HDWG180_123 (sdf) (errors 2320)
Disk 2 - TOSHIBA_HDWG180_456 (sdh) (errors 2320)

 

I'm getting used to Unraid and still in trial period, any advice for handling this best? Not sure if best to try reboot and check connections or if that might cause further issues?

 

Edited September 7, 20214 yr by Dansgalaxy

Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.
 

Attached

 

Edited September 8, 20214 yr by Dansgalaxy

How are these disks attached?

Either directly to motherboard or via a sata card in pci-e (I can't confirm without shutting off and pulling drives out which drive is connected where).

Unfortunately your log space was full and those diagnostics didn't get all of syslog.

 

Can you get syslog, zip it, and attach?

The syslog I'm seeing is the same (with no data in latest):

 

-rw-r--r--  1 root   root         0 Sep  7 23:23 syslog

-rw-r--r--  1 root   root 125849600 Sep  2 04:40 syslog.1

 

 

Looks like log must have filled several days ago judging by timestamps.

 

You should go to Scheduler and turn off mover logging.

 

Then I guess you will have to reboot and post new diagnostics

 

 

Well it seems rebooting fixed it oddly. Drives working again and parity check running.

Any tips on what to look out for so have suitable logs if it fails again?

You can see how full log is on Dashboard. No reason to log mover unless you are trying to diagnose a mover problem. Mover entries in log show filenames.