Failed to mount /sysroot after partial failed zypper dup Tumbleweed 64 bits on VirtualBox

In my company, developers use Red Hat to develop Linux-based apps.
Therefore I am the first one using openSUSE: I have installed Tumbleweed 64-bits on VirtualBox 4.3.26 hosting on Windows 64 bits.

But this morning, I did a sudo zypper ref && sudo zypper dup.
The zypper ref was OK, the zypper dup indicated the upgrade of about 800 packages.
But after 10 minutes download/upgrade, more and more package could not be upgrade.
I do not remember the reason, but I have always answer “i” (ignore).
After the partial failed zypper dup and attempted to redo zypper ref but got an error about something like that unavailability of the repository.

But got a failure on next boot: Failed to mount /sysroot.

I have a full report file /run/initramfs/rdsosreport.txt but I do not know how to retrieve it :frowning:

I would like to know if using a CD rescue may fix the problem (how to do?).

Probably disk full?

It’s never a good idea to interrupt a “zypper dup” and/or just ignore errors. Your system is most likely in some inconsistent state afterwards.

If you are lucky an older kernel might still boot (if the sysroot cannot be mounted, it might be due to missing kernel modules in the initrd). So try to select one in “Advanced Options” in the boot menu.
If that does work, I would suggest to free up some disk space (you should probably remove some snapshots with “yast snapper”), and run “zypper dup” again to finish the upgrade.
Btw, “zypper ref” is not really necessary. By default zypper refreshes the repos automatically, unless you disable Auto-Refresh explicitely for some repos.

Then why didn’t you post in the Tumbleweed, Evergreen and PreRelease/Beta forum? That is the place where your fellow Tumbleweed users gather.

I have initially posted this problem on the wrong place:
https://forums.opensuse.org/showthread.php/506591-Failed-to-mount-sysroot-after-partial-failed-zypper-dup-Tumbleweed-64-bits-on-VirtualBox


I have installed Tumbleweed 64-bits on VirtualBox 4.3.26 hosted on Windows7 64 bits.

This morning, I did a zypper ref && zypper dup.
The zypper ref was OK.
The zypper dup started upgrading more than 800 packages.

But after 10 minutes, one package could not be upgrade (libreoffice).
I do not remember the reason, maybe about something unavailable on the repository…
As I do not care about libreoffice => I answered “i” (ignore).

After some other successfully upgraded packages, another one failed.
I continued to answer “i” (ignore).

And sometimes other errors, and I always answered “i” (ignore).

After this partial failed zypper dup, I attempted to redo the zypper ref but got an error about something unavailability of the repository (I do not remember the exact error message).

After rebooting my system I got a failure during the boot process.


error: unexpectedly disconnected from boot status daemon

Generating "/run/initramfs/rdsosreport.txt"

Entering emergency mode.

journalctl says “Failed to mount /sysroot.”

I do not know how to retrieve the full report file /run/initramfs/rdsosreport.txt from my VirtualBox hosted on Windows 7…

I would like to know if using a CD rescue may fix the problem (how to do?)

Good idea :slight_smile:
I have moved the post –> https://forums.opensuse.org/showthread.php/506594-Failed-to-mount-sysroot-after-partial-failed-zypper-dup

you haven’t moved it. You double posted. And that is not a good idea. When you want something like this (a move), please use the report buuton (the triangle with the ! below each post) to ask staff.

This one will be merged with the other one.

On 2015-04-08 15:56, Lmap wrote:

> But after 10 minutes, one package could not be upgrade (libreoffice).
> I do not remember the reason, maybe about something unavailable on the
> repository…

It is better to do a download only run, then the actual dup if
everything did download.

And if the upgrade of some package fails, better pay close attention and
consider abort. The error messages you get are crucial.

> After rebooting my system I got a failure during the boot process.

Reboot is the worst thing to do at that point.

> I would like to know if using a CD rescue may fix the problem (how to
> do?)

On the standard distro (not tumbleweed) the method would be to boot the
full DVD (not the CD), and choose upgrade to the same installed version.

Otherwise, salvage your data, and reinstall.


Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

Muchas Gracias Carlos

Yep I did the wrong thinks.
Moreover my colleagues pointed out I have not taken a snapshot of my VirtualBox VM before the upgrade!

I have downloaded the three Snapshot20150406 ISO files:

  1. openSUSE-Tumbleweed-Rescue-CD-x86_64-Snapshot20150406-Media.iso
  2. openSUSE-Tumbleweed-NET-x86_64-Snapshot20150406-Media.iso
  3. openSUSE-Tumbleweed-DVD-x86_64-Snapshot20150406-Media.iso

These three ISO hang while searching for system files.
On initial Tumbleweed installation (February 2015) I accepted the partitioning proposed by the installer: swap + Btrfs for / + XFS for /home + … many other small things.

The three ISO use YaST2 in console mode (no X11 graphic mode) even with my configuration: 5GB RAM + 4 processor + 128 MB Video RAM.

I have also attempted to reinstall a new VM (still using VirtualBox)

  1. Rescue CD does not install (indeed)
  2. NET installer cannot access repository thought proxy/user/password
    Error message: Maximum (6) redirects followed
    => This seems a bug!
  3. DVD installer (GNOME chosen) succeeds “proxy settings test” but still use console mode and same error while accessing repositories.
    After installation, boot from hard disk hangs after “Started Update UTMP about System Runlevel Changes.”
    => This also seems a bug!