Numerous errors like this - kernel: md: disk1 read error, sector=6074046160

Unraid is still reading the correct disk capacity, but Sonarr, Lidarr, Radarr and Immich are all reporting missing files.

 

It can't be hardware related, as the odds of 4 drives all having physical issues is unlikely. 

 

What might have happened, and can I recover my data?

tower-diagnostics-20250512-2022.zip

Edited May 13, 20251 yr by DCox88

You have completely filled log space, and those logs are missing from diagnostics probably because they rolled over.

 

What do you get from command line with this?

ls /var/log/syslog*

 

Quote

unrelated disks.

56 minutes ago, DCox88 said:

can't be hardware related

 

These are all on this controller:

04:00.0 SATA controller [0106]: JMicron Technology Corp. JMB58x AHCI SATA controller [197b:0585]
	Subsystem: JMicron Technology Corp. Device [197b:0000]
	Kernel driver in use: ahci
	Kernel modules: ahci

 

12 minutes ago, trurl said:

 

These are all on this controller:

04:00.0 SATA controller [0106]: JMicron Technology Corp. JMB58x AHCI SATA controller [197b:0585]
	Subsystem: JMicron Technology Corp. Device [197b:0000]
	Kernel driver in use: ahci
	Kernel modules: ahci

 

I just actually took a look at the connections, and I can confirm that the five drives that encountered errors were all plugged into that controller. I have another controller I'm going to try swapping in, and redoing the parity check with corrections turned off.

 

Going off the last parity check, I guess I'll be back in about 20 hours.

20 minutes ago, trurl said:

You have completely filled log space, and those logs are missing from diagnostics probably because they rolled over.

 

What do you get from command line with this?

ls /var/log/syslog*

 

 

I'd like to try to get those other logs before you reboot.

ls: cannot access 'var/log/syslog*': No such file or directory

Edited May 13, 20251 yr by DCox88

33 minutes ago, DCox88 said:

ls: cannot access 'var/log/syslog*

Looks like you must have left out the beginning / in the path.

 

Better if you copy/paste from a code block instead of trying to type it yourself. Bad things can happen if you get certain command lines wrong.

1 hour ago, trurl said:

What do you get from command line with this?

ls /var/log/syslog*

Thanks for that.

ls /var/log/syslog*
/var/log/syslog

Did you already reboot since getting those earlier diagnostics?

Yes. The system had become unresponsive. After completing the reboot, the system seem to detect my files again.

 

Everything seems to be accounted for in my -arr suite.

Those logs are gone then.