I'm trying to wake up a VM from a snapshot (state: turned-on) and all of a sudden I get this error:
Anyone has any idea what does it mean?
Thanks in advance.
Strange error: failed to load unit 'pgm'
-
SpeedRacer
- Posts: 4
- Joined: 12. Oct 2009, 22:54
- Primary OS: MS Windows XP
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: XP SP3, Ubuntu v8.10
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Strange error: failed to load unit 'pgm'
There is a difference in the saved state and the now state. You can post the complete log file ( as an attachment ) but in the end you will need to discard the saved state.
Things to check:
Host drive ( is it full )
Host drive for corruption.
Things to check:
Host drive ( is it full )
Host drive for corruption.
-
SpeedRacer
- Posts: 4
- Joined: 12. Oct 2009, 22:54
- Primary OS: MS Windows XP
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: XP SP3, Ubuntu v8.10
Re: Strange error: failed to load unit 'pgm'
Thanks for taking the time to look Perry.
Absolutely no chance of "disk full" (either VDI or host's) so looks more to the corruption side.
The referred "shot" is shot #7 in a cascade of progressive shots. Previous shot (#6) is the same but before turning on the VM, so it's an "OFF" state shot, when restored, it BSOD's. I've gone as far as restoring shot #1 (OFF state) and BSODs too, so the corruption should be in the first {xxxxxxxxxx}.vdi of the chain.
When I boot from an external disk and "view" the supposedly corrupted disk, the files are there. I can copy/move them, etc.
So any chance of doing something about it? It's an important image and I have no backup. It's not about data, it's the "system" which is important, which contains many programs configured in specific ways.
Absolutely no chance of "disk full" (either VDI or host's) so looks more to the corruption side.
The referred "shot" is shot #7 in a cascade of progressive shots. Previous shot (#6) is the same but before turning on the VM, so it's an "OFF" state shot, when restored, it BSOD's. I've gone as far as restoring shot #1 (OFF state) and BSODs too, so the corruption should be in the first {xxxxxxxxxx}.vdi of the chain.
When I boot from an external disk and "view" the supposedly corrupted disk, the files are there. I can copy/move them, etc.
So any chance of doing something about it? It's an important image and I have no backup. It's not about data, it's the "system" which is important, which contains many programs configured in specific ways.
- Attachments
-
LOG.txt- Last part of log
- (44.23 KiB) Downloaded 54 times