Unraid Server Hanging Issue with ACPI Errors in Syslog

[mmjaberi]

Hello Unraid community,

 

I am experiencing an issue with my Unraid server where it hangs whenever I move large amounts of data to the server sometimes when I ping the server IP address I am getting reply, but I can't access unraid web console or even ssh to the server. The server becomes unresponsive, and I have to shut it down manually and restart it each time this happens. While investigating the issue, I came across several ACPI-related errors in the syslog. I'm not sure if these errors are directly related to the hanging issue, but I'm hoping that resolving them might help improve my server's stability and performance.

 

Here are the ACPI-related errors I found in the syslog: ( Please check the attached Unraid logs)

 

• ACPI BIOS Error (bug): Failure creating named object [_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20220331/dsfield-184)
• ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20220331/dswload2-477)
• ACPI Error: Aborting method _SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20220331/psparse-529)

 

To troubleshoot these errors, I have tried the following steps:

• Checked RAM and CPU utilization during file transfers (both under 10%).
• Updated the BIOS to the latest version.

 

Unfortunately, the errors persist, and my server continues to hang during large file transfers.

I would greatly appreciate any assistance or suggestions from the community to help resolve these ACPI errors and the server hanging issue.

My hardware configuration is as follows:

 

• Motherboard:  ASUS ROG MAXIMUS Z790 HERO.
• BIOS Version:  0816
• CPU: Intel Core I9 139000K 3.00GHz 
• RAM: Corsair Vengeance DDR5 128GB
• Pool Devices: 1 KINGSTON NVMe 2TB

 

 

Thank you for your help!

 

syslog.txt

Edited April 5, 2023 by mmjaberi

[JorgeB]

7 hours ago, mmjaberi said:

I'm not sure if these errors are directly related to the hanging issue

Unlikely, these are usually the result of a BIOS bug, sometimes any installed hardware can also help caused them, like a GPU, but it's still a BIOS problem.

[mmjaberi]

I do have GPU installed on the motherboard .

Is there any fix available for this bug or work around. 

[JorgeB]

BIOS update is your best bet, when a new one is available.

[mmjaberi]

What about the hanging thing 😅😅, how can I fix this issue.

One more thing I forgot to mention here, when the server hangs I can see on the screen the following error message:

“Kernel Panic Not Syncing… etc” is this something related to USB flash drive?

Edited April 6, 2023 by mmjaberi

[JorgeB]

Enable the syslog server and post that after a crash, but with all the log spamming it will be more difficult to see the issue.

[mmjaberi]

Then I am gonna upgrade the Bios first to cross out the previous issue ACPI error, then will re-try the scenario and will post the logs here afterwards.

 

Thanks for the support.

[mmjaberi]

Even after upgrading my BIOS to the latest version, I continue to encounter the error mentioned below, which I've also removed from the attached log file.

 

Apr  7 02:56:10 MJ-unRaid kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20220331/dsfield-184)
Apr  7 02:56:10 MJ-unRaid kernel: ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20220331/dswload2-477)
Apr  7 02:56:10 MJ-unRaid kernel: ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20220331/psparse-529)

 

 

This time, I noticed a 'BTRFS' error that I believe might be related to my primary issue. However, unlike before, the server did not hang or become unresponsive this time around. I'm uncertain whether the BIOS update resolved the problem or if there's another underlying issue at play.

 

Apr  6 21:38:55 MJ-unRaid kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 395 off 24314224640 csum 0xaad58a8b expected csum 0x54912a6a mirror 1
Apr  6 21:38:55 MJ-unRaid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 114, gen 0

 

Any thoughts or suggestions would be appreciated.

 

syslog.txt

[steveme]

Im having a simliar problem. the only thing that fixes it for me is to restart the server. but it basically is happening everyday right now. I updated the bios recently and the intel me and still having this error after. My mobo is a rog b660-i

 

Apr  6 17:03:19 EstradaNAS kernel: ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20220331/psparse-529)
Apr  6 17:03:19 EstradaNAS kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20220331/dsfield-184)

 

[steveme]

Interesting im able to replicate this error when i click on the Dashboard page. if i dont go to that page i dont think the error shows up.

[mmjaberi]

3 hours ago, steveme said:

Im having a simliar problem. the only thing that fixes it for me is to restart the server. but it basically is happening everyday right now. I updated the bios recently and the intel me and still having this error after. My mobo is a rog b660-i

 

Apr  6 17:03:19 EstradaNAS kernel: ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20220331/psparse-529)
Apr  6 17:03:19 EstradaNAS kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20220331/dsfield-184)

 

 

Could you tell me how you were able to upgrade the Intel ME 🧐? 

I tried using Windows PE and placed the Intel ME upgrade package in it for the upgrade, but it didn't work for me 🤯 and I ended up upgrading the BIOS only 

 

[steveme]

9 hours ago, mmjaberi said:

 

Could you tell me how you were able to upgrade the Intel ME 🧐? 

I tried using Windows PE and placed the Intel ME upgrade package in it for the upgrade, but it didn't work for me 🤯 and I ended up upgrading the BIOS only 

 

i downloaded the office tool from intel. I couldn't get the updater to work from the asus website.

[mmjaberi]

do you mean intel AMT tool (Active Management Technology)?

 

I couldn't find anything called office tool in intel website. BTW did you also use Windows PE install the upgrade ?

Edited April 7, 2023 by mmjaberi

[steveme]

20 hours ago, mmjaberi said:

do you mean intel AMT tool (Active Management Technology)?

 

I couldn't find anything called office tool in intel website. BTW did you also use Windows PE install the upgrade ?

Sorry that must have been a autocorrect typo. Here is one of the things i installed. intel site I also installed a chipset intel update from their site. not sure if you have a asus mobo. But this is the forum post that set me in the right direction. I will also note that i updated my bios first and then the ME drivers. Even though it says not to do that everything worked successfully after.

 

Even though my unraid server is still giving me these issues. I don't think they are related

[mmjaberi]

It's not related, I think it's bug as I read it in many online forums 🤓...

Just wanted to know how did managed upgrade ME driver. I'm trying to figure out how to upgrade the Intel ME firmware on my ASUS ROG MAXIMUS Z790 HERO motherboard, as I'm running UNRAID OS exclusively on the server. The Intel ME driver is a Windows executable package, which I can't run in UNRAID.

 

I've attempted to use a bootable Windows PE (Preinstalled Environment) with the package included, but that didn't work either.

Has anyone with a similar setup managed to upgrade their Intel ME firmware 🤔?

 

Any suggestions on how to approach this issue would be greatly appreciated. 🤝

 

Edited April 8, 2023 by mmjaberi

[steveme]

18 minutes ago, mmjaberi said:

It's not related, I think it's bug as I read it in many online forums 🤓...

Just wanted to know how did managed upgrade ME driver. I'm trying to figure out how to upgrade the Intel ME firmware on my ASUS ROG MAXIMUS Z790 HERO motherboard, as I'm running UNRAID OS exclusively on the server. The Intel ME driver is a Windows executable package, which I can't run in UNRAID.

 

I've attempted to use a bootable Windows PE (Preinstalled Environment) with the package included, but that didn't work either.

Has anyone with a similar setup managed to upgrade their Intel ME firmware 🤔?

 

Any suggestions on how to approach this issue would be greatly appreciated. 🤝

 

heres the link to the forum post i followed. rog forum i also ended up installing windows 11 bootable on a usb thumbstick but not sure if that was a factor vs using a PE.

Edited April 8, 2023 by steveme

[mmjaberi]

I managed to upgrade the Intel ME driver and all other Intel drivers, but it didn't change anything. 🙄 😔

 

Thank you very much @steveme  for the guidance. 😇

[steveme]

8 hours ago, mmjaberi said:

I managed to upgrade the Intel ME driver and all other Intel drivers, but it didn't change anything. 🙄 😔

 

Thank you very much @steveme  for the guidance. 😇

Found another thread on this but no action as of yet. forum post

Im curious are you using a NVIDIA Card for transcoding with your system?

 

[mmjaberi]

13 hours ago, steveme said:

Found another thread on this but no action as of yet. forum post

Im curious are you using a NVIDIA Card for transcoding with your system?

 

Yes, I am using "NVIDIA GeForce RTX 3070" for transcoding.

 

[kylelavery88]

Curious if you ever solved the ACPI-related errors. Having the same issues.

[mmjaberi]

On 11/3/2023 at 6:48 AM, kylelavery88 said:

Curious if you ever solved the ACPI-related errors. Having the same issues.

It was fixed for few days, again I started seeing it back in the logs after upgrading to 6.12

Edited November 4, 2023 by mmjaberi

[kylelavery88]

Not sure if this would apply to your situation, but after much research I discovered that my ACPI errors were being caused by Plex Media Server. The errors started after I installed an RTX 3060 for transcoding and quickly started filling up the system logs. Ended up doing extra work by updating BIOS, Unraid, and Plex to no avail. 

 

After digging into the logs for Plex and finding audio-related codec errors, the solution for me was to delete Plex's codecs folder. The ACPI errors stopped immediately and have yet to come back.

 

For those who may find this useful, the folder location is:

appdata\Plex-Media-Server\Library\Application Support\Plex Media Server\Codecs

 

Plex will automatically redownload the necessary codecs when restarting the docker container.