VirtualBox

Ticket #8986 (closed defect: fixed)

Opened 3 years ago

Last modified 13 months ago

fedora14 disk failures with guest additions and pae kernel

Reported by: maninred2 Owned by:
Priority: major Component: other
Version: VirtualBox 4.0.8 Keywords:
Cc: Guest type: other
Host type: other

Description (last modified by frank) (diff)

I´ve set a 2core fedora14 guest with guest additions to 1 core and the graphic memory from 32MB to 64MB.Before I´ve installed several ingeneering and scientific tolls on it. A start of the machine fails with filesystem errors(see screenshot). The system was not able to correct the errors. A newstart fails on booting process. Set it back to the old configuration doesn´t help. Resoring a snapshot brings the fedora back in a working state.

The harddisk repair process suggest me that there are conflicts between the virtualbxo videodrivers and the kernel.(One of the screenshots).

Attachments

fedora 14 32-bit-2011-05-29-14-26-36.log Download (47.1 KB) - added by maninred2 3 years ago.
the harddisk failure
fedora15 reducing core inconsistent filesystem videodriver kernel failures.jpeg Download (107.6 KB) - added by maninred2 3 years ago.
the repair starting procedure on boot
fedora14 reducing core inconsistent filesystem.jpeg Download (125.7 KB) - added by maninred2 3 years ago.
no this is the repair start the other is in the repair process
fedora 14 32-bit-2011-05-29-14-35-14.log Download (69.8 KB) - added by maninred2 3 years ago.
a newstart after the repair - fails
fedora 14 32-bit-2011-05-29-14-37-19.log Download (71.9 KB) - added by maninred2 3 years ago.
go back to old settings 2cores 32MB graphic memory - fails
reproducible fedora file systems.jpeg Download (114.2 KB) - added by maninred2 3 years ago.
reproduced
harddisk errors on fedora 14.jpeg Download (207.5 KB) - added by maninred2 3 years ago.
harddisk errors on fedora 14 following.jpeg Download (165.1 KB) - added by maninred2 3 years ago.

Change History

Changed 3 years ago by maninred2

the harddisk failure

Changed 3 years ago by maninred2

the repair starting procedure on boot

Changed 3 years ago by maninred2

no this is the repair start the other is in the repair process

Changed 3 years ago by maninred2

a newstart after the repair - fails

Changed 3 years ago by maninred2

go back to old settings 2cores 32MB graphic memory - fails

comment:1 Changed 3 years ago by maninred2

It is one of the actual updates, Idon´t know which one. I´ve brought the guest back to an older snapshot which works. Then I´ve installed the ingeneering packages again and made all updates. It causes also filesystem damages and brings the system in an unbootable state. A screenshot will be attached.

Changed 3 years ago by maninred2

reproduced

comment:2 Changed 3 years ago by frank

Could you revert to that safe snapshot again and force a disk check (fsck -f)? We have to rule out that the disk is already damaged. Also, which is the VBox version you used to create this VM initially (before taking the first snapshot)? Is that also VBox 4.0.8?

comment:3 Changed 3 years ago by maninred2

I t was not created in VB4.0.8. It was 4.0.4 or 4.0.6. I can´t remember exactly. The only snapshot is at 15.5.2011, so ...

A forced check of the harddisk shows some errors. I attach a screenshot.

Changed 3 years ago by maninred2

Changed 3 years ago by maninred2

comment:4 Changed 3 years ago by frank

That's what I thought. So it might be that the corruption was introduced by an older version of VBox and the corruption was only hidden so far. Note that there were some fixes for possible disk corruptions in VBox 4.0.8 and 4.0.6. I suggest that you either do a complete guest reinstallation and copy the valid data from the old guest to the new guest or that you at least go back to the oldest possible snapshot and force a disk check like you've done before. It is hard to say when the corruption bug in VirtualBox was fixed but the chances that 4.0.8 does not suffer from this problem are very high.

comment:5 Changed 3 years ago by maninred2

It´s getting better here with VB4.0.10. With the new version I can make the updates and the system keeps running.

comment:6 Changed 13 months ago by frank

  • Status changed from new to closed
  • Resolution set to fixed
  • Description modified (diff)
Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use