Jump to content

I woke up to see 4000 read errors on parity drive


michael123

Recommended Posts

Posted
Jan 28 03:00:24 Vault kernel: md: disk0 read error, sector=4459498392
Jan 28 03:00:24 Vault kernel: md: disk0 read error, sector=4459498400
Jan 28 03:00:24 Vault kernel: md: disk0 read error, sector=4459498408
Jan 28 03:00:24 Vault kernel: md: disk0 read error, sector=4459498416
Jan 28 03:00:24 Vault kernel: md: disk0 read error, sector=4459498424
Jan 28 03:00:24 Vault kernel: md: disk0 read error, sector=4459498432
Jan 28 03:00:24 Vault kernel: md: disk0 read error, sector=4459498440
Jan 28 03:00:24 Vault kernel: md: disk0 read error, sector=4459498448
Jan 28 03:00:24 Vault kernel: md: disk0 read error, sector=4459498456
Jan 28 03:00:24 Vault kernel: md: disk0 read error, sector=4459498464
Jan 28 03:00:24 Vault kernel: md: disk0 read error, sector=4459498472
Jan 28 03:00:24 Vault kernel: md: disk0 read error, sector=4459498480
Jan 28 03:00:24 Vault kernel: md: disk0 read error, sector=4459498488

 

Posted

Disk looks fine, recommend running an extended SMART test and swapping cables/backplane with another disk just to rule it out, if no issues on the SMART test keep monitoring.

Posted

How? I ran parity maybe 5-6 times with zero errors..

Couldn't it be a driver issue?

 

Anyway, how serious is this?

I mean so there were these errors.. I indeed looked into SMART and the disk was healthy. I already kicked off a new parity check 4 hours ago

Could it cause anything?

 

Posted
1 minute ago, johnnie.black said:

For now it didn't cause any issues, but it might if it happens again, already said what you can do to try to find what caused them.

 

Thanks, how could I know if it did?

 

Posted

..and how can I know that this is not a SW issue? In the case of 6.4.0 Upgrade, it is clearly said that S3 Sleep is causing the issue... and I had lockups.. indeed looks like it caused something.. or the unraid driver in 6.4.0 is less resilient to this kind of 'noise'

 

 

Posted
43 minutes ago, michael123 said:

Thanks, how could I know if it did?

If for the example disk disk got disabled.

 

4 minutes ago, michael123 said:

..and how can I know that this is not a SW issue?

Read errors are always hardware related, could be the disk, cables, controller, power supply, etc, not possible to be caused by software.

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...