On 02.04.2012 07:42, Petro Rossini wrote:
Hi Adam and all,
at the end my problem description I sent to -virtualization first.
(Thanks Adam, to pointing out that I am barking up the wrong tree;-)
On Mon, Apr 2, 2012 at 3:28 PM, Adam Vande More
<amvandem...@gmail.com> wrote:
On Sun, Apr 1, 2012 at 11:44 PM, Petro Rossini
<petro.ross...@gmail.com>
> AFAICT, that error message is related to a permissions issue.
Can you
> supply the VM log when you post the question to emulation?
See you there:-) But there isn't much I found:
00:00:01.368 nspr-2 Loading settings file
"/vboxes/zimbra/zimbra.vbox" with version "1.11-freebsd"
00:00:01.885 Watcher ERROR [COM]: aRC=NS_ERROR_FAILURE
(0x80004005)
aIID={5eaa9319-62fc-4b0a-843c-0cb1940f8a91} aComponent={Machine}
aText={The virtual machine 'zimbra' has terminated unexpectedly
during
startup with exit code 0}, preserve=false
I would like to see it in full if possible.
[snip]
Hi all,
I had some VirtualBox hassle over the weekend.
It started with thes messages inside the VM, a Ubuntu 10.04 Server
(running Zimbra).
2012-03-30T18:37:11.581591+11:00 mail kernel: [4520695.304357] sd
4:0:0:0: [sdd] Unhandled error code
2012-03-30T18:37:15.201744+11:00 mail kernel: [4520695.304362] sd
4:0:0:0: [sdd] Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
2012-03-30T18:37:15.201753+11:00 mail kernel: [4520695.304366] sd
4:0:0:0: [sdd] CDB: Write(10): 2a 00 02 1d 44 f8 00 00 08 00
2012-03-30T18:37:15.201756+11:00 mail kernel: [4520695.304457]
end_request: I/O error, dev sdd, sector 35472632
2012-03-30T18:37:15.201758+11:00 mail kernel: [4520695.312601]
__ratelimit: 9 callbacks suppressed
2012-03-30T18:37:15.201761+11:00 mail kernel: [4520695.312604] Buffer
I/O error on device sdd, logical block 4434079
2012-03-30T18:37:15.201763+11:00 mail kernel: [4520695.321978] lost
page write due to I/O error on sdd
Two hours later it moves to another disk: "sd 3:0:0:0: [sdc]
Unhandled
error code"
The Linux reacts with a read-only remount - practically the box is
falling over.
The VDI disks are on a ZFS filesystem, and I scrubbed the ZVolume and
looked for other possible problems - host-side all seamt to be okay.
I restarted the system once - and for a few hours it worked, untiul I
see the same problem again.
A second reboot is not that successful, I cannot start the VM
headless
anymore, getting a
Result Code: NS_ERROR_FAILURE (0x00004005)
I have a second machine with the same setup and continous mirroring
of
the disks (zfs send/receive) - the same result.
Tried an older ZFS snapshot of the VDI disks - still not starting.
It was FreeBSD 8.2 and VirtualBox 4.0.4, and some people with similar
You took the worst possible versions for your server so I hope it's not
an important one. FreeBSD 8.2 + ZFS has some significant known problems
that were fixed in 8-STABLE after the 8.2 release. Additionally
VirtualBox 4.0 until 4.0.8 is known to be unstable because they did a
lot
of refactoring and rewriting so I wouldn't recommend using it in
production either. Building this all with clang is another risk factor.
I hope you didn't loose any data but you should seriously switch to
FreeBSD 9.0 and VirtualBox 4.1.10.
--
Bernhard Fröhlich
http://www.bluelife.at/
_______________________________________________
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
