Opened 13 years ago
Closed 13 years ago
#9942 closed defect (duplicate)
Other system VDI clearing
| Reported by: | DrMefistO | Owned by: | |
|---|---|---|---|
| Component: | virtual disk | Version: | VirtualBox 4.1.6 |
| Keywords: | Cc: | ||
| Guest type: | other | Host type: | Windows |
Description
I'm trying to install Visopsys OS. But after successful installation and rebooting of VM, Visopsys can't be loaded 'cause of cleared VDI disk, and reseted (cleared) to default settings of this Machine.
Attachments (1)
Change History (14)
by , 13 years ago
comment:1 by , 13 years ago
Which setting do you mean? And why do you think that the disk is cleared? To me it seems that just the bootloader was not properly installed.
follow-up: 3 comment:2 by , 13 years ago
Because after rebooting, ISO-image of CD with this OS disappears from configuration.
comment:3 by , 13 years ago
I checked one more time this defect, and found, that clears only Drive settings: CD/DVD drive, and hard disk. Bootloader installed in automathic mode.
follow-ups: 5 7 comment:4 by , 13 years ago
The ISO image did most probably disappear because the guest ejected the medium. But are you sure that the hard disk medium was disconnected as well? Because nothing of these events is visible in the VBox.log file you attached. Or did the VBoxSVC daemon crash for some reason during reboot?
comment:5 by , 13 years ago
Well, if after installing of Visopsys OS VDI-file was normal, Visopsys would then be loaded normally, but it wouldn't. You can try to install it - Visopsys is a very light-weight OS.
comment:6 by , 13 years ago
Sorry, I don't have time to test every guest. But you could help if you would answer my questions.
comment:7 by , 13 years ago
Replying to frank:
But are you sure that the hard disk medium was disconnected as well?
I'm not sure that this disk was disconnected, but I'm sure, that disk was changed between finishing installation, and after rebooting of Vbox. How I can to give you more information.
comment:8 by , 13 years ago
Hard to believe that the hard disk image was changed, I've never seen that in other reports. Disconnecting the CDROM image is normal if the guest ejects the medium and I would admit that it could be possible that the hard disk image was empty -- in that case every other setting of the VM should be screwed up as well because the VBoxSVC daemon crashed. But I don't know how it should come that the hard disk image was changed -- pointing to a different image file. Or did I misunderstand something?
comment:9 by , 13 years ago
I tried to tell you, that something wrong. That's all. How I can to give you more information?
follow-up: 11 comment:10 by , 13 years ago
I need the VBox.log file from such a VM session where you experienced such a change of the hard disk image (the above VBox.log file certainly does not show this problem). And I need the statement if the VBoxSVC daemon crash or not. I assume the daemon did not crash, otherwise you would have seen a Windows error dialog.
comment:11 by , 13 years ago
Replying to frank:
I need the VBox.log file from such a VM session where you experienced such a change of the hard disk image (the above VBox.log file certainly does not show this problem). And I need the statement if the VBoxSVC daemon crash or not. I assume the daemon did not crash, otherwise you would have seen a Windows error dialog.
Yes, I have not seen any error dialog. Maybe some error with installer? But everything was installed successfully.
comment:13 by , 13 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
Actually this sounds as a duplicate of #3352 to me.
VBox.log