rdagitz Posted June 27, 2023 Share Posted June 27, 2023 About every 24 to 48 hours one of my Unraid servers keeps locking up. I cannot access it via web, ssh or anything. There is also no output to a connected monitor. I have to force shut down the server. When restarted, the log is recreated and I have no information to track down the problem. This problem began when I upgraded to 6.12, but in doing so I also updated some plugins updated dockers and had to recreate the cache drives (The btrfs partitions corrupted so I switched them to a zfs raid1 and restored the appdata from a backup.) With all of these changes, I cannot tell if the issue is hardware, a memory leak of a docker app, the upgrade to 6.12 or what. Is there some other log that I can dive into to find the issue? I am attaching the diagnostics just in case there is something I am missing from them. server-diagnostics-20230627-0802.zip Quote Link to comment
rdagitz Posted June 27, 2023 Author Share Posted June 27, 2023 I did a little more digging and found a warning one time from Fix Common Problems Quote macvlan call traces found If I rescan the system, the warning is not there. Thoughts? Quote Link to comment
JorgeB Posted June 27, 2023 Share Posted June 27, 2023 Since you're still using macvlan try switching to ipvlan, since macvlan call traces will usually end up crashing the server, and they will be gone after a reboot. Quote Link to comment
rdagitz Posted June 27, 2023 Author Share Posted June 27, 2023 I found the following directions on another posting and walked through them: Quote To do this: go to SETTINGS > DOCKER with advanced view toggled (top right) set Enable Docker: No, then set Docker custom network type: ipvlan Once complete: set Enable Docker: Yes to restart docker service. Will let you know how things go. Quote Link to comment
rdagitz Posted June 29, 2023 Author Share Posted June 29, 2023 This server is still behaving strangely, even after changing to ipvlan. Upon one restart I noticed this in a section of a log: Quote Jun 29 15:33:58 JonesServer kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT2._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330) Jun 29 15:33:58 JonesServer kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT2._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529) Jun 29 15:33:58 JonesServer kernel: ata3.00: ATA-9: MB2000GCWDA, HPGD, max UDMA/133 Jun 29 15:33:58 JonesServer kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330) Jun 29 15:33:58 JonesServer kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529) Jun 29 15:33:58 JonesServer kernel: ata5.00: ATA-9: MB2000GCWDA, HPGD, max UDMA/133 Jun 29 15:33:58 JonesServer kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT3._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330) Jun 29 15:33:58 JonesServer kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT3._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529) Jun 29 15:33:58 JonesServer kernel: ata4.00: ATA-9: MB2000GCWDA, HPGD, max UDMA/133 Jun 29 15:33:58 JonesServer kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330) Jun 29 15:33:58 JonesServer kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT1._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529) Jun 29 15:33:58 JonesServer kernel: ata2.00: ATA-9: MB2000GCWDA, HPGD, max UDMA/133 Jun 29 15:33:58 JonesServer kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330) Jun 29 15:33:58 JonesServer kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529) Jun 29 15:33:58 JonesServer kernel: ata6.00: supports DRM functions and may not be fully accessible Jun 29 15:33:58 JonesServer kernel: ata6.00: ATA-11: Samsung SSD 860 EVO 500GB, RVT04B6Q, max UDMA/133 Jun 29 15:33:58 JonesServer kernel: ata5.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 32), AA Jun 29 15:33:58 JonesServer kernel: ata6.00: 976773168 sectors, multi 1: LBA48 NCQ (depth 32), AA Jun 29 15:33:58 JonesServer kernel: ata3.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 32), AA Jun 29 15:33:58 JonesServer kernel: ata5.00: Features: NCQ-prio Jun 29 15:33:58 JonesServer kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330) Jun 29 15:33:58 JonesServer kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529) Jun 29 15:33:58 JonesServer kernel: ata4.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 32), AA Jun 29 15:33:58 JonesServer kernel: ata2.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 32), AA Jun 29 15:33:58 JonesServer kernel: ata3.00: Features: NCQ-prio Jun 29 15:33:58 JonesServer kernel: ata1.00: supports DRM functions and may not be fully accessible Jun 29 15:33:58 JonesServer kernel: ata1.00: ATA-11: Samsung SSD 870 EVO 500GB, SVT01B6Q, max UDMA/133 Jun 29 15:33:58 JonesServer kernel: ata4.00: Features: NCQ-prio Jun 29 15:33:58 JonesServer kernel: ata2.00: Features: NCQ-prio Jun 29 15:33:58 JonesServer kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330) Jun 29 15:33:58 JonesServer kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529) Jun 29 15:33:58 JonesServer kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT2._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330) Jun 29 15:33:58 JonesServer kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT2._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529) Jun 29 15:33:58 JonesServer kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT3._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330) Jun 29 15:33:58 JonesServer kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT3._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529) Jun 29 15:33:58 JonesServer kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330) Jun 29 15:33:58 JonesServer kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT1._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529) Jun 29 15:33:58 JonesServer kernel: ata1.00: 976773168 sectors, multi 1: LBA48 NCQ (depth 32), AA Jun 29 15:33:58 JonesServer kernel: ata5.00: configured for UDMA/133 Jun 29 15:33:58 JonesServer kernel: ata6.00: Features: Trust Dev-Sleep NCQ-sndrcv Jun 29 15:33:58 JonesServer kernel: ata2.00: configured for UDMA/133 Jun 29 15:33:58 JonesServer kernel: ata3.00: configured for UDMA/133 Jun 29 15:33:58 JonesServer kernel: ata4.00: configured for UDMA/133 Jun 29 15:33:58 JonesServer kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330) Jun 29 15:33:58 JonesServer kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529) Jun 29 15:33:58 JonesServer kernel: ata6.00: supports DRM functions and may not be fully accessible Jun 29 15:33:58 JonesServer kernel: ata1.00: Features: Trust Dev-Sleep NCQ-sndrcv Jun 29 15:33:58 JonesServer kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330) Jun 29 15:33:58 JonesServer kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529) These are the only "errors" on the syslog (and these appear to be something for which the kernel is looking and moving on). The log is cleared upon reboot. Are there no persistent logs that I can use to figure out what is going on? Quote Link to comment
itimpi Posted June 29, 2023 Share Posted June 29, 2023 4 minutes ago, rdagitz said: This server is still behaving strangely, even after changing to ipvlan. Upon one restart I noticed this in a section of a log: These are the only "errors" on the syslog (and these appear to be something for which the kernel is looking and moving on). The log is cleared upon reboot. Are there no persistent logs that I can use to figure out what is going on? To get persistent logs you need to use the syslog server. Quote Link to comment
rdagitz Posted July 2, 2023 Author Share Posted July 2, 2023 Turns out that my "locking up" problem is something to do with docker vlans and an issue with Unraid 6.12. Downgraded to Unraid 6.11.3 and am waiting on the issue to be resolved. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.