ACPI Errors on New Build

Hi All,

I just built a nice HP Z840 with Manjaro Linux. Everything is updated, but I still get the errors below. I have been using a HP Z820 that doesn’t show any of these errors. My concern is that 3 days ago the machine rebooted when I clicked on a link. After logging in the 3 drives were unmountable on Linux, but still mountable on Windows 11. I hope it’s not related, but I don’t really trust this machine now. I am currently backing up my drives in Win11, then plan to put the drives back in my 4 yr old Z820 for now.

Any thoughts or ideas are greatly appreciated.

HP Z840
Samsung SSD 990 PRO 4TB (OpSys) - Thought a 4 yr old Intel DC P4600 Series SSD was the issue, so I replaced
Intel Xeon E5-2699 v4 - 2 physical processors; 44 cores across 2 NUMA nodes; 88 threads
264 GB RAM - Reseated all RAM
10 GB NVIDIA GeForce RTX 3080/PCIe/SSE2
WD Drives 6, 10 TB

Best Regards,

Gerry

hpz840workstation ~]$ sudo dmesg

          [   14.020080] ACPI Error: Needed [Buffer/String/Package], found [Integer] 000000003f5d9806 (20240322/exresop-557)
          [   14.020087] ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [Index] (20240322/dswexec-433)
          [   14.020092] ACPI Error: Aborting method \_SB.WMIV.WVPO due to previous error (AE_AML_OPERAND_TYPE) (20240322/psparse-529)
          [   14.020098] ACPI Error: Aborting method \_SB.WMIV.WMPV due to previous error (AE_AML_OPERAND_TYPE) (20240322/psparse-529)
          [   14.021381] ACPI Error: Needed [Buffer/String/Package], found [Integer] 000000002c5b58a7 (20240322/exresop-557)
          [   14.021385] ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [Index] (20240322/dswexec-433)
          [   14.021389] ACPI Error: Aborting method \_SB.WMIV.WVPO due to previous error (AE_AML_OPERAND_TYPE) (20240322/psparse-529)
          [   14.021394] ACPI Error: Aborting method \_SB.WMIV.WMPV due to previous error (AE_AML_OPERAND_TYPE) (20240322/psparse-529)
          [   14.022562] ACPI Error: Needed [Buffer/String/Package], found [Integer] 000000007d841b48 (20240322/exresop-557)
          [   14.022565] ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [Index] (20240322/dswexec-433)
          [   14.022569] ACPI Error: Aborting method \_SB.WMIV.WVPO due to previous error (AE_AML_OPERAND_TYPE) (20240322/psparse-529)
          [   14.022574] ACPI Error: Aborting method \_SB.WMIV.WMPV due to previous error (AE_AML_OPERAND_TYPE) (20240322/psparse-529)
          [   14.023767] ACPI Error: Needed [Buffer/String/Package], found [Integer] 000000002de27ad7 (20240322/exresop-557)
          [   14.023772] ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [Index] (20240322/dswexec-433)
          [   14.023776] ACPI Error: Aborting method \_SB.WMIV.WVPO due to previous error (AE_AML_OPERAND_TYPE) (20240322/psparse-529)
          [   14.023781] ACPI Error: Aborting method \_SB.WMIV.WMPV due to previous error (AE_AML_OPERAND_TYPE) (20240322/psparse-529)

Please edit your post to use proper formatting for terminal output. It’s a bit difficult to read otherwise:

1 Like

I tried guys, but I don’t really follow what you want us to do. I would guess most of us don’t code for a living, so we don’t fully understand formatting. We only post 3 or 4 times per year.

Sorry again for incorrect formatting,

Gerry

Judging by your next sentence - you were in Windows when it happened

This means the NTFS filesystem has not been properly unmounted - caused by the sudden reboot - thus a dirty bit is set and Linux refuse to mount using ntfs3 kernel driver.

As for the ACPI messages - these are likely safe to ignore.

1 Like

Thank you for your reply.

I was in Manjaro when the sudden reboot and no mount happened. I should have sent that in as the issue, but I needed access to the files quickly.

I tried Windows to see if the drives would mount because I picked up a HP Z840 for cheap and it happened to have Windows on it.

Regards,

Gerry

Does the motherboard have the latest BIOS installed?

https://support.hp.com/gb-en/drivers/hp-z840-workstation/6978842
Type: BIOS
Version: 02.59 Rev.A
Operating systems:Linux
Release date:May 5, 2022
File name: sp140179.tgz

Thank you for your reply.

Kind of, I did download and install the current BIOS, but it shows a date of March 31, 2022. I have 02.59 (no Rev.A), but dated March 31, 2022. Download and extract to see the same thing. I downloaded yours and still see the March BIN file.

Regards,

Gerry

BIOS_Reverts2Mar312022

linux-aarhus,

My error message is attached below. Is this an easy fix before I start copying 5TB of data back to these working drives from my Backup disk, without a reformat of course.

Regards,

Gerry

NoMount2_AfterSuddenReboot_Nov2024

Boot Windows.
Run a file system check.
Make sure you power down Windows fully - no fast startup.

1 Like

Thanks to everyone who responded. The Windows File System Scan/Check worked like a charm.

That spare $200 HP Z840 I picked up for parts has already proven invaluable. I might keep it for awhile.

Regards,

Gerry

If you plan to keep using the NTFS (Windows) file system, you should also keep some sort of Windows OS ready to use, because whenever this file system becomes corrupted for whatever reason, the only sure way to repair it is by using native Windows tools - like you did here.
Linux can use the file system, but in case of problems, Windows tools are the only way to recover it.

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.