Parity drive dropped off array

[baracas]

My parity drive dropped off the array.  After i noticed it gathered logs and diags and shutdown they system, then watched it boot up on a live monitor.  The shutdown was very slow as if something was hung.  After bootup getting a message that the parity disk is disabled.

 

My instict was to just run a party sinc after reboot but I decided not to till I attempted to glean some information as to what happened.

Its been long time since I've had to troubleshoot this box (unraid has just run without incident for years its seem) so i'm a little rusty.

 

If I'm not misstaken, I think i've seens errors like ACPI BIOS Error (bug): Could not resolve symbol before.  Thought they were likely loose sata cables or something, but never knocked a drive out of the array before. 

 

Just looking for opinion, worst case im out a parity drive, but i don't want to make things worse by trying to rebuild parity when i shoudn't have to i don't think.  idk.

 

So if anyone's board on this holiday morning.....

p67-diagnostics-20230704-0425.zip syslog.txt WDC_WD40EZRZ-22GXCB0_WD-WCC7K1JKSDT4-20230704-0425 parity (sdb) - DISK_DSBL.txt

[JorgeB]

Looks more like a power/connection problem, replace cables and re-sync parity.

[baracas]

Thanks thats what i thought, iv'e replaced most of the sata cables but whenever i reboot it, which typically a week or so, this happens right as its rebooting:

 

Jul 7 01:16:32 p67 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT3._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330) Jul 7 01:16:32 p67 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT3._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529) Jul 7 01:16:32 p67 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330) Jul 7 01:16:32 p67 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529) Jul 7 01:16:32 p67 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330) Jul 7 01:16:32 p67 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529) Jul 7 01:16:32 p67 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330) Jul 7 01:16:32 p67 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT1._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529)

 

So then Unraid registers a unclean shutdown and wants to run parity check.  Until i figure it out, I might not bother running parity, or maybe just not reboot it as often

p67-diagnostics-20230707-0127.zip

[JorgeB]

1 hour ago, baracas said:

Jul 7 01:16:32 p67 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT3._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330) Jul 7 01:16:32 p67 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT3._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529) Jul 7 01:16:32

These are a BIOS issue, look for a BIOS update, but hey are harmless expect for the log spam.

 

1 hour ago, baracas said:

So then Unraid registers a unclean shutdown and wants to run parity check.

Start by giving it more time, go to Settings -> Disk Settings -> Shutdown Timeout and set it to 150sec, if the same stop the array instead of rebooting and time how long it takes to stop.

[baracas]

Seems my cache drive doesn't want to unmount. ..ever.  It might be something docker related or something else idk.  I replaced all but 1 of the sata cables, and thats probably the one i didn't.  Took 30 min on this shutdown.  Killed all the processes but idk.  Ive seen a few shutdown issues in the forums thats sound similar. 

p67-diagnostics-20230710-1912.zip syslog.txt

[JorgeB]

7 hours ago, baracas said:

Seems my cache drive doesn't want to unmount.

This is known issue, you can update to v6.12.3-rc2 to test, should be fixed, need to switch to the next branch.