VirtualBox

Ticket #5726 (closed defect: fixed)

Opened 4 years ago

Last modified 4 years ago

disk write error and reset

Reported by: cokegen Owned by:
Priority: critical Component: virtual disk
Version: VirtualBox 3.0.10 Keywords:
Cc: Guest type: Linux
Host type: Windows

Description

I just lost a mysql database on this bug. I don't see any errors in the windows event log so I think a bug on virtualbox is more likely. Anyway I'm replacing the harddisk as I need to sort out the possible causes ASAP.

A log is included

Attachments

Debian congo-2009-12-11-06-19-52.log Download (258.5 KB) - added by cokegen 4 years ago.
debian 5.0 guest log
dmesg.txt Download (2.6 KB) - added by cokegen 4 years ago.
dmesg log for the debian guest

Change History

Changed 4 years ago by cokegen

debian 5.0 guest log

comment:1 Changed 4 years ago by frank

What disk type is your host drive F:? And did you check that host drive for errors?

comment:2 Changed 4 years ago by cokegen

Is an NTFS disk, I checked the drive for errors, but I got the same errors by moving the machine to my C: disk so I doubt 2 disks to be failing. My dmesg output shows both hda and hdb disks getting the errors and I'm attaching it.

comment:3 Changed 4 years ago by cokegen

Can't attach more files, so I'm pasting the dmesg output:

Dec 11 06:41:35 congo kernel: [108262.205567] hdb: dma_intr: status=0x41 { DriveReady Error } Dec 11 06:41:35 congo kernel: [108262.205567] hdb: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=18749623, sector=18749623 Dec 11 06:41:35 congo kernel: [108262.205567] ide: failed opcode was: unknown Dec 11 06:41:35 congo kernel: [108262.237569] hdb: dma_intr: status=0x41 { DriveReady Error } Dec 11 06:41:35 congo kernel: [108262.237569] hdb: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=18749623, sector=18749623 Dec 11 06:41:35 congo kernel: [108262.237569] ide: failed opcode was: unknown Dec 11 06:41:35 congo kernel: [108262.237569] hdb: dma_intr: status=0x41 { DriveReady Error } Dec 11 06:41:35 congo kernel: [108262.237569] hdb: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=18749623, sector=18749623 Dec 11 06:41:35 congo kernel: [108262.237569] ide: failed opcode was: unknown Dec 11 06:41:35 congo kernel: [108262.237569] hdb: dma_intr: status=0x41 { DriveReady Error } Dec 11 06:41:35 congo kernel: [108262.237569] hdb: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=18749623, sector=18749623 Dec 11 06:41:35 congo kernel: [108262.237569] ide: failed opcode was: unknown Dec 11 06:41:35 congo kernel: [108262.237569] hda: DMA disabled Dec 11 06:41:35 congo kernel: [108262.237569] hdb: DMA disabled Dec 11 06:41:35 congo kernel: [108262.300669] ide0: reset: success Dec 11 06:41:35 congo kernel: [108262.348672] hda: task_out_intr: status=0x41 { DriveReady Error } Dec 11 06:41:36 congo kernel: [108262.348672] hda: task_out_intr: error=0x10 { SectorIdNotFound }, LBAsect=17011429, sector=17011429 Dec 11 06:41:36 congo kernel: [108262.348672] ide: failed opcode was: unknown Dec 11 06:41:36 congo kernel: [108262.348672] hdb: task_out_intr: status=0x41 { DriveReady Error } Dec 11 06:41:36 congo kernel: [108262.348672] hdb: task_out_intr: error=0x10 { SectorIdNotFound }, LBAsect=18749623, sector=18749623 Dec 11 06:41:36 congo kernel: [108262.348672] ide: failed opcode was: unknown

comment:4 Changed 4 years ago by frank

What, you can't attach more files? Attaching that dmesg output should be possible (and is preferred)... The VBox.log file clearly shows that some host write operation failed.

Changed 4 years ago by cokegen

dmesg log for the debian guest

comment:5 Changed 4 years ago by cokegen

I'm sorry, the "I can't attach more files" was bc I didn't saw the button to add more. I'm more than eager for this to be solved and I have the best predisposition. Again, my mistake (for some reason opera didn't showed the button after the first attach).

I can confirm the disk is fine and without errors. Could it be a bug in the vbox controller implementation ?

Thanks

comment:6 Changed 4 years ago by frank

Unlikely. The log from the VM shows VERR_IO_NOT_READY which means the host device is not ready. Do you run some I/O load on the host parallel to the VM?

Could you check if VBox 3.1.2 fixes the problem for you?

comment:7 Changed 4 years ago by aeichner

  • Status changed from new to closed
  • Resolution set to fixed

No response, closing. Reopen if neccessary.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use