Opened 10 years ago
Closed 7 years ago
#13878 closed defect (fixed)
Virtual IDE controller/drive/device lost after some time, causing vm freeze
Reported by: | Philip Seeger | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 4.3.18 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | Linux |
Description
After running for several days or weeks, the affected vm loses its hard drive. The vm freezes, some data corruption possible (depending on running processes, database services, ...).
This has already happened to me years ago, but I couldn't find an open bug for this issue, so here it is. Back then, I found a discussion where someone had the same problem. It was suggested that this might have something to do with the virtual IDE controller in VirtualBox, which should be changed to another type, like SATA. I followed this advice and the problem was fixed. Years have passed, this vm (and others) running 24/7, not losing their hdd.
On another system that I've recently set up, I forgot to change the virtual IDE controller in this vm to SATA. So a few days after starting it (I think it ran for about 3 weeks), it froze, last line in console was "device lost". I did start an update process (not system update) right before this happened, so system load might be a trigger.
I should point out that both vms (the one now and the other one years ago) are running Debian/kBSD (now Wheezy, I don't remember back then). I don't know how much Debian/kBSD might or might not play a role - I don't remember any other vm crashing in this way, but most of my other vms don't use a virtual IDE controller.
I've attached the last log file.
Attachments (1)
Change History (4)
by , 10 years ago
Attachment: | VBox.log.3 added |
---|
follow-up: 2 comment:1 by , 10 years ago
comment:2 by , 10 years ago
Replying to frank:
On what file systems are your VM images located? Any idea where all these snapshot events in your VBox.log file come from?
Sorry about the late reply, my notification settings seem to be wrong.
The vm images are on a ZFS filesystem, which has also been used for VMware vms without a problem.
Are you referring to these messages? File system of '/data/VirtualBox/Debian-Srv-1/Snapshots' (snapshots) is unknown I don't know what VirtualBox is trying to tell me, nor do I get what it's trying to accomplish. It sounds like VirtualBox was trying to detect the filesystem type on the host (none of its business, or is it?), for whatever reason. The path is correct and accessible (0700).
comment:3 by , 7 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Please reopen if still relevant with VBox 5.1.22.
On what file systems are your VM images located? Any idea where all these snapshot events in your VBox.log file come from?