Hello. Please help me solve the problem.
I had VirtualBox Version 6.1.18 installed. It ran Windows 7x64 OS.
Today I updated VirtualBox to version 7.0.14 and the virtual machine started giving an error when starting:
A disc read error occurred
Press Ctrl+Alt+Del to restart.
If anything, the contents of the Logs folder in the application
A disc read error occurred
-
- Volunteer
- Posts: 874
- Joined: 14. Sep 2019, 16:51
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: WIN11,10, 7, Linux (various)
- Location: United Kingdom
Re: A disc read error occurred
Image files need to be uploaded using the attachments Tab, as you did with the log files so I can't comment on the 'unknown' error message.
However there are some configuration issues that would be worth dealing with before you retry the VM:
According to the VBox.log You have upgraded the VirtualBox installation to 7.0.14, but the Extension Pack has not been upgraded and is still Version 6.0.18. It is essential that these match; and especially so for the significant design/coding changes implemented in 7.0.x
You might also need to increase the CPU Core allocation from 1 to 2 as 64-bit OS VMs usually need 2 cores to perform effectively.
Try running the VM again after making the above changes and if you still get errors, please submit another updated VBox.Log
However there are some configuration issues that would be worth dealing with before you retry the VM:
According to the VBox.log You have upgraded the VirtualBox installation to 7.0.14, but the Extension Pack has not been upgraded and is still Version 6.0.18. It is essential that these match; and especially so for the significant design/coding changes implemented in 7.0.x
You might also need to increase the CPU Core allocation from 1 to 2 as 64-bit OS VMs usually need 2 cores to perform effectively.
Try running the VM again after making the above changes and if you still get errors, please submit another updated VBox.Log
Re: A disc read error occurred
I did everything as you said, but it did not solve the problem, unfortunately.multiOS wrote: ↑26. Mar 2024, 12:06 Image files need to be uploaded using the attachments Tab, as you did with the log files so I can't comment on the 'unknown' error message.
However there are some configuration issues that would be worth dealing with before you retry the VM:
According to the VBox.log You have upgraded the VirtualBox installation to 7.0.14, but the Extension Pack has not been upgraded and is still Version 6.0.18. It is essential that these match; and especially so for the significant design/coding changes implemented in 7.0.x
You might also need to increase the CPU Core allocation from 1 to 2 as 64-bit OS VMs usually need 2 cores to perform effectively.
Try running the VM again after making the above changes and if you still get errors, please submit another updated VBox.Log
Updated logs in the application
- Attachments
-
- Logs.rar
- (77.34 KiB) Downloaded 4 times
-
- Volunteer
- Posts: 874
- Joined: 14. Sep 2019, 16:51
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: WIN11,10, 7, Linux (various)
- Location: United Kingdom
Re: A disc read error occurred
Sorry you haven't had any responses, I've only been dropping into the Forum intermittently due to personal commitments.
The VBox.log identifies a memory configuration problem:
I would try reducing the VMs RAM allocation to 2GB to allow some margin for the Host's needs, but the ideal would be to increase the Hosts physical RAM to at least 16GB (cost permitting), as performance is never going to be sparkling with only 7.8GB total RAM being available to support 2 x 64bit-Operating Systems.
I'm not sure if correcting this will eliminate the actual the disk read issue as that suggests some possible system corruption inside the Windows 7 VM, but config issue do need to be corrected to eliminate that as a potential cause of problems. The CTRL+ALT+Del request message suggests Windows 7 may be looking to self-repair its installation.
The VBox.log identifies a memory configuration problem:
i.e The system could only provide 3.4GB, but you set the allocation at 4.0GB + 128MB VideoRAM which needs to be immediately available when the Windows 7 VM starts.00:00:07.186641 Host RAM: 8078MB (7.8GB) total, 3583MB (3.4GB) available
00:00:07.528893 RamSize <integer> = 0x0000000100000000 (4 294 967 296, 4.0 GiB)
00:00:07.529119 VRamSize <integer> = 0x0000000008000000 (134 217 728, 128.0 MiB)
I would try reducing the VMs RAM allocation to 2GB to allow some margin for the Host's needs, but the ideal would be to increase the Hosts physical RAM to at least 16GB (cost permitting), as performance is never going to be sparkling with only 7.8GB total RAM being available to support 2 x 64bit-Operating Systems.
I'm not sure if correcting this will eliminate the actual the disk read issue as that suggests some possible system corruption inside the Windows 7 VM, but config issue do need to be corrected to eliminate that as a potential cause of problems. The CTRL+ALT+Del request message suggests Windows 7 may be looking to self-repair its installation.