Error Message, after update from 6.1 to 7.0: ata1.00: Read log 0x00 page 0x00 failed, Emask 0x1

[Lisa Miller]

Host System:
* Linux Mint Debian Edition 4

Guest System:
* Linux Mint 21

After Uninstall Virtual Box 6.1 and installing Virtual Box 7.0, the guest OS don't boot and I got the follow two error messages:

Code: Select all

ata1.00: Read log 0x00 page 0x00 failed, Emask 0x1
ata1.00: Read log 0x00 page 0x00 failed, Emask 0x1

And the guest system, don't boot.

How to fix this ?

[CAYRE]

run
/sbin/vboxconfig

[Lisa Miller]

run
/sbin/vboxconfig

In the place there is a link pointing to the following destination:

Code: Select all

/usr/lib/virtualbox/postinst-common.sh

The file can be executed with the following call:

Code: Select all

sudo /usr/lib/virtualbox/postinst-common.sh

During the execution there were the following markings:

Code: Select all

vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.

After doing this above, I am still get the same two error messages.

[Lisa Miller]

Now found a solution for me.

After update from VirtualBox 6.1 to 7.0, need to disable the 3d acceleration.

The follow is working also:
* create a new VM by useing the old VM hard disk

Perhaps its possible to enable this again if you do the follow:
* disable 3d acceleration
* uninstall the old 6.1 guest extensions
* install the 7.0 guest extensions

[Lisa Miller]

How to update the the installed guest extension on guest system from 6.1 to 7.0 ?

[Lisa Miller]

How to update the the installed guest extension on guest system from 6.1 to 7.0 ?

* start the guest vm
* press Strg + Pos 1
* select from this menu "add guest add ins".

That will update the guest add ins.

Remark:
* After than the guest vm is booting again. The booth errormessages above, dont chnge by this.

Question?
After installation of new guest add ins, I am getting a CD symbol from guest add ins.
Can I delete this symbol from desktop or does it be need for anything?

[scottgus1]

After installation of new guest add ins, I am getting a CD symbol from guest add ins.
Can I delete this symbol from desktop or does it be need for anything?

The Guest Additions comes on a CD image ISO through the VM's CD drive. If you eject the CD from the drive, the icon may go away.

Please note, we like to keep to one subject per topic, so please start new topics for further questions you may have if not related to the original question. Thanks!

[Lisa Miller]

After installation of new guest add ins, I am getting a CD symbol from guest add ins.
Can I delete this symbol from desktop or does it be need for anything?

The Guest Additions comes on a CD image ISO through the VM's CD drive. If you eject the CD from the drive, the icon may go away.

A does the Guest Add ins CD need to be still inserted, after installing the guest add on add ins ?

[scottgus1]

No. Once the GAs have been installed, the "CD" can be ejected.

[Lisa Miller]

No. Once the GAs have been installed, the "CD" can be ejected.

THX

[4qigK9gxYceX]

I am experiencing the same issue booting VM with Syslinux PXE 6.04-pre1 and EFI enabled as per screenshot.
I have 3D acceleration disabled and no extensions installed.
Was anyone able to fix this?

VirtualBox Version 7.0.8 r156879

Screenshot from 2023-07-13 13-13-01.png (6.47 KiB) Viewed 5907 times

[scottgus1]

I have 3D acceleration disabled and no extensions installed.

Thanks for trying the posted ideas above! Unfortunately, those ideas may have been coincidences, if you tried the same things and the VM failed to boot.

Please try making a brand new VM with the same OS and see if it boots. Also try a VM with a standard Ubuntu OS. Please report what happens with both.

[4qigK9gxYceX]

Thanks for the suggestion.

I have created brand new VM with Ubuntu 22 LTS selected as OS. I have no actual OS installed and no drive connected because I am testing my PXE setup.
The issue does not appear on newly created VM.

[scottgus1]

brand new VM with Ubuntu 22 LTS ... The issue does not appear on newly created VM.

Interesting! See if you can compare settings differences between the new working VM and the failing VM.

Also try the Syslinux PXE in a new VM, instead of Ubuntu.

[4qigK9gxYceX]

This issue in question is github/torvalds/linux/commit/fc5c8aa7bc4977205e0ceb93425075f8a8f49501
Not sure why posting URL is not allowed, but add .com to github domain there.

However, some devices lie about this support and using the DMA version
of the command fails, generating the warning message "READ LOG DMA EXT
failed, trying PIO". Since READ LOG PAGE DMA EXT is an optional command,
this warning is not at all important but may be scary for the user.
Change ata_read_log_page() to suppres this warning and to print an
error message if both DMA and PIO attempts failed.

Steps to reproduce:

• Attach a disk to IDE (PIIX4) or SATA (ACHI) controller.

• Tick Solid-state Drive checkbox in drive properties. This triggers the error.

• Boot and see the error.

• Shutdown the machine.

• Untick Solid-state Drive checkbox in drive properties.

• Boot. No error displayed.

VirtualBox Version 7.0.8 r156879 (Qt5.15.3) on Ubuntu 22 LTS x64 5.19.0-46-generic