January 28, 20188 yr Author 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
January 28, 20188 yr Author BTW, why Temp is not shown for Parity drive (I see '*'), while when entering SMART I see 28 degrees Celsius ?
January 28, 20188 yr Author diagnostics I see it happened at 3:00, when CA Backup/Restore ran vault-diagnostics-20180128-0632.zip
January 28, 20188 yr Community Expert 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.
January 28, 20188 yr Author It is something SW.. the coincidence of 3:00am is weird..That's when Mover job is run, when CA appdata Backup ran (you see it in the logs)
January 28, 20188 yr Author 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?
January 28, 20188 yr Community Expert 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.
January 28, 20188 yr Author 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?
January 28, 20188 yr Author ..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'
January 28, 20188 yr Community Expert 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.