[SOLVED] Both parity drives disabled amor the same time

[Fredrick]

Hi guys,

I'm on vacation but got some concerning notifications from unRAID l night. Both my parity drives had been disabled within the same minute, I've got errors all over and a warning on my cache drive.

 

I'm afraid to stop the array or reboot.

 

Any advice?

 

Attached screenshot

 

 

Edited July 14, 2021 by Fredrick

[JorgeB]

Please post the diagnostics: Tools -> Diagnostics

[Fredrick]

Diagnostics attached, thanks

 

EDIT: Diagnostics removed.

 

 

Edited July 14, 2021 by Fredrick

[6of6]

The Unraid WebUI is not reliable. Might be this time... I would be shitting if I saw that in the morning.

 

Wait... I've seen that shit. Relax... You have a backup and everything will be fine after another vacation spent restoring everything from the backup. My wife would say it's no problem at all, and I need to cut the lawn.

 

6

[JorgeB]

1 hour ago, 6of6 said:

The Unraid WebUI is not reliable.

The OP's issue has nothing to do with the GUI, it's not the first time you post the same wrong information, please stop.

[JorgeB]

There were errors in multiple disks:

 

Jul  3 21:43:36 Tower kernel: md: disk4 read error, sector=8177890032
Jul  3 21:43:36 Tower kernel: md: disk1 read error, sector=8177890032
Jul  3 21:43:36 Tower kernel: md: disk2 read error, sector=8177890032
Jul  3 21:43:36 Tower kernel: md: disk6 read error, sector=8177890032
Jul  3 21:43:36 Tower kernel: md: disk8 read error, sector=8177890032
Jul  3 21:43:36 Tower kernel: md: disk0 read error, sector=8177890032
Jul  3 21:43:36 Tower kernel: md: disk29 read error, sector=8177890032

 

Also the cache device, could be a connection/power problem or HBA problem.

[JorgeB]

Forgot to mention, unrelated to this issue but the server was running out of RAM for some time before this, you should also look into that.

[Fredrick]

I ended up shutting the system down from vacation. When I came back I re-seated all cables to SAS-expanders and booted again. Parity was marked as invalid. 

 

I did a read-check of the array which went without errors. Then I stopped the array, unassigned the parity drives, started the array, stopped the array, assigned parity drives again. It re-built both parity drives without errors, and is seemingly running well now. 

 

I'll pay attention to the RAM usage going forward. Thanks.