VERR_SSM_INTEGRITY_DECOMPRESSION)

I have the following problem and my vbox machine won’t start

Failed to open a session for the virtual machine EXELIXI.

Failed to load unit ‘pgm’ (VERR_SSM_INTEGRITY_DECOMPRESSION).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

**openSUSE Tumbleweed kernel 4.17.12-1-default
VBox 5.2.16_SUSE r123745

Posted on virtualbox forum but redirected here : https://forums.virtualbox.org/download/file.php?id=30468

**

Hi
Your system isn’t up to date… run zypper dup to get to the latest
Tumbleweed version and try again…

Install the virtualbox version from openSUSE-Tumbleweed-Oss repository (5.2.16-1.4).

I did that, same error

sudo zypper dup
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See ‘man zypper’ for more information about this command.
Loading repository data…
Reading installed packages…
Computing distribution upgrade…

Nothing to do.

  1. How old is this Guest, ie about when do you think it was first created?
  2. Was this Guest shutdown completely before, or was it put into suspension or hibernation (from openSUSE, not using the Virtualbox commands)
  3. Please list the files in the directory where your Guest files are stored, and post.

TSU

Hi
Please post the output from;


uname -a
cat /etc/os-release
zypper lr -E

FYI -
The basis for my questions is that several search hits suggested a mis-match between Guest versions(Additions?) and the HostOS server side install of Virtualbox. Hence my questions about the history of this Guest.

Although the openSUSE version might be important, I assumed that because TW upgrades all the time, it’d be something recent and potentially a major VBox change each time TW is upgraded so although perhaps nice to know if the problem isn’t solved and you want to include details in a report, might not be a critical piece of info during troubleshooting.

TSU

Malcolm thanks for replying


uname -a
Linux FOSTW.site 4.18.0-1-default #1 SMP PREEMPT Wed Aug 15 07:02:07 UTC 2018 (280ac93) x86_64 x86_64 x86_64 GNU/Linux


cat /etc/os-release
NAME="openSUSE Tumbleweed"
# VERSION="20180820"
ID="opensuse-tumbleweed"
ID_LIKE="opensuse suse"
VERSION_ID="20180820"
PRETTY_NAME="openSUSE Tumbleweed"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:tumbleweed:20180820"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org/"


zypper lr -E
Repository priorities in effect:                                                                                          (See 'zypper lr -P' for details)
      98 (raised priority)  :  1 repository  
      99 (default priority) :  5 repositories

# | Alias                             | Name                       | Enabled | GPG Check | Refresh
--+-----------------------------------+----------------------------+---------+-----------+--------
2 | download.opensuse.org-non-oss     | Main Repository (NON-OSS)  | Yes     | (r ) Yes  | Yes    
3 | download.opensuse.org-oss         | Main Repository (OSS)      | Yes     | (r ) Yes  | Yes    
4 | download.opensuse.org-tumbleweed  | Main Update Repository     | Yes     | (r ) Yes  | Yes    
5 | http-ftp.uni-erlangen.de-2037714e | Packman Repository         | Yes     | (r ) Yes  | Yes    
8 | repo-source                       | openSUSE-Tumbleweed-Source | Yes     | (r ) Yes  | Yes    
9 | teamviewer                        | TeamViewer - x86_64        | Yes     | (r ) Yes  | Yes


Hi
So nothing untoward repo wise, aside from a few updates behind, which repository is at priority 98?

Can you update to the latest release and force a repository refresh?


zypper ref -f
zypper -vvv dup

Also don’t forget the info requested by user tsu2.

Hi TSU thanks for your help, I was on a limited vacation.

  1. Many years before
  2. Suspended, has a snapshot

Snapshots directory
-rw------- 1 filippos users 258998272 Sep 1 22:57 {06f0614c-d22e-4917-9021-0c0b71d1f05b}.vdi
-rw------- 1 filippos users 42678799 Aug 6 20:27 2018-08-06T17-27-01-858497000Z.sav
vdi directory:
-rw-r–r-- 1 filippos users 8042663936 Jul 20 15:05 EXELIXIL.vdi
-rw------- 1 filippos users 10787 Dec 18 2017 EXELIXI.vbox

BR Filippos

Hi,
Packman is the repo with 98 priority

After new upgrade:

uname -a
Linux FOSTW.site 4.18.5-1-default #1 SMP PREEMPT Fri Aug 24 12:38:43 UTC 2018 (9e91e29) x86_64 x86_64 x86_64 GNU/Linux

cat /etc/os-release
NAME="openSUSE Tumbleweed"
# VERSION="20180829"
ID="opensuse-tumbleweed"
ID_LIKE="opensuse suse"
VERSION_ID="20180829"
PRETTY_NAME="openSUSE Tumbleweed"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:tumbleweed:20180829"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org/"

**Same error
**Failed to open a session for the virtual machine EXELIXI.
Failed to load unit ‘pgm’ (VERR_SSM_INTEGRITY_DECOMPRESSION).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

  1. In the directory holding your Guest machine files, there is probably a file with a “.prev” suffix.
    Try moving the file out of that directory and then try to start up your machine.

  2. Although a bit of a shot in the dark, I’d recommend you try to merge your shapshots. I generally use virtualization snapshots for temporary situations and remove or merge them ASAP. Keeping snapshots in your system can cause untold headaches if you have to recover a corrupted diskfile and supposedly can cause extra disk I/O (I haven’t been able to verify if this is true or not). I recommend copying your files elsewhere so that if your merge fails, you can copy the original files back, replacing the failed merge files.

TSU

Hi

  1. .prev didn’t exist
  2. Did that, same error.
    BR Filippos

Failed to open a session for the virtual machine EXELIXI Clone.
Failed to load unit ‘pgm’ (VERR_SSM_INTEGRITY_DECOMPRESSION).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

On the cloned machine I discarded the saved state and all transaction that I did before was lost!

Yes,
That should be done (resolve all saved states, merge or resolve all virtual snaphots, and shutdown the machine completely) before cloning.

TSU

But this would lead to loose everything I did on the saved state!!!

You need to merge your snapshots <before> you clone to not lose anything.
It’s just one of the things that are required to have a successful result.

If you don’t merge and your result is an unbootable machine, then you may just have to “learn and live” that if removing the snapshots are what is required to just get a bootable machine, then so be it… A bootable machine with lost data may be better than something that won’t boot at all.

As always, make backup copies because removing the snapshots is a try and may still not result in a success.

Besides adhering to a strict policy of always doing strict preparation before cloning machines, lesson be learned to always have a good backup strategy even if it’s nothing more than making a full copy of the directory holding your vm files.

TSU

Same error

Failed to open a session for the virtual machine EXELIXI Clone.
Failed to load unit ‘pgm’ (VERR_SSM_INTEGRITY_DECOMPRESSION).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

Pls post a list of the files in your vm directory.

You can also try creating a new Guest with the diskfile.
Although you can try using the other files as ell, I’d generally recommend only the single diskfile and let virtualbox generate the other files.

TSU

By deleting the saved state I managed to run my machine, but I lost all the transactions from last good snapshot (see below) to error .

VM directory
-rw-r–r-- 1 filippos users 8042663936 Jul 20 15:05 EXELIXIL.vdi
-rw------- 1 filippos users 15127 Sep 4 00:47 EXELIXI.vbox
Snapshots directory
-rw------- 1 filippos users 258998272 Sep 3 23:21 {06f0614c-d22e-4917-9021-0c0b71d1f05b}.vdi <– this is a good snapshot
-rw------- 1 filippos users 42678799 Aug 6 20:27 2018-08-06T17-27-01-858497000Z.sav
-rw------- 1 filippos users 166723584 Sep 4 00:47 {a4c90e82-a119-416a-8a89-1f628ce873e0}.vdi <— this is the error snapshot from saved state

That’s probably the best result possible.
Lesson learned, be sure to resolve all snapshots and shut down completely before any cloning.

And,
This applies to all virtualization, not just Vbox in this thread.

TSU