Results 1 to 4 of 4

Thread: After latest Tumbleweed upgrade I'm stuck in emergency mode as my file systems won't mount properly

  1. Default After latest Tumbleweed upgrade I'm stuck in emergency mode as my file systems won't mount properly

    Hi,

    I just upgraded my openSUSE Tumbleweed (OT) installation with:

    Code:
    sudo zypper up -y
    This caused almost 200 packages to be upgraded (so please forgive me if I don't remember all their names, rofl) and now when I try to boot OT I get a few startup errors namely that three devices fail to mount (after trying to for a minute and a half) and SUSEFirewall2_init.service and Plymouth fail to start. As a result of these errors I am left in emergency mode. Here is my journalctl -xb output. Here is the output of systemctl status SUSEFirewall2_init.service. Here is my /etc/fstab file:

    Code:
    UUID=6fc8601b-4711-4af6-b39e-aebf5065f7d3 / btrfs defaults 0 0
    UUID=6fc8601b-4711-4af6-b39e-aebf5065f7d3 /boot/grub2/i386-pc btrfs subvol=@/boot/grub2/i386-pc 0 0
    UUID=6fc8601b-4711-4af6-b39e-aebf5065f7d3 /boot/grub2/x86_64-efi btrfs subvol=@/boot/grub2/x86_64-efi 0 0
    UUID=6fc8601b-4711-4af6-b39e-aebf5065f7d3 /home btrfs subvol=@/home 0 0
    UUID=6fc8601b-4711-4af6-b39e-aebf5065f7d3 /opt btrfs subvol=@/opt 0 0
    UUID=6fc8601b-4711-4af6-b39e-aebf5065f7d3 /srv btrfs subvol=@/srv 0 0
    UUID=6fc8601b-4711-4af6-b39e-aebf5065f7d3 /tmp btrfs subvol=@/tmp 0 0
    UUID=6fc8601b-4711-4af6-b39e-aebf5065f7d3 /usr/local btrfs subvol=@/usr/local 0 0
    UUID=6fc8601b-4711-4af6-b39e-aebf5065f7d3 /var/cache btrfs subvol=@/var/cache 0 0
    UUID=6fc8601b-4711-4af6-b39e-aebf5065f7d3 /var/crash btrfs subvol=@/var/crash 0 0
    UUID=6fc8601b-4711-4af6-b39e-aebf5065f7d3 /var/lib/libvirt/images btrfs subvol=@/var/lib/libvirt/images 0 0
    UUID=6fc8601b-4711-4af6-b39e-aebf5065f7d3 /var/lib/machines btrfs subvol=@/var/lib/machines 0 0
    UUID=6fc8601b-4711-4af6-b39e-aebf5065f7d3 /var/lib/mailman btrfs subvol=@/var/lib/mailman 0 0
    UUID=6fc8601b-4711-4af6-b39e-aebf5065f7d3 /var/lib/mariadb btrfs subvol=@/var/lib/mariadb 0 0
    UUID=6fc8601b-4711-4af6-b39e-aebf5065f7d3 /var/lib/mysql btrfs subvol=@/var/lib/mysql 0 0
    UUID=6fc8601b-4711-4af6-b39e-aebf5065f7d3 /var/lib/named btrfs subvol=@/var/lib/named 0 0
    UUID=6fc8601b-4711-4af6-b39e-aebf5065f7d3 /var/lib/pgsql btrfs subvol=@/var/lib/pgsql 0 0
    UUID=6fc8601b-4711-4af6-b39e-aebf5065f7d3 /var/log btrfs subvol=@/var/log 0 0
    UUID=6fc8601b-4711-4af6-b39e-aebf5065f7d3 /var/opt btrfs subvol=@/var/opt 0 0
    UUID=6fc8601b-4711-4af6-b39e-aebf5065f7d3 /var/spool btrfs subvol=@/var/spool 0 0
    UUID=6fc8601b-4711-4af6-b39e-aebf5065f7d3 /var/tmp btrfs subvol=@/var/tmp 0 0
    UUID=6fc8601b-4711-4af6-b39e-aebf5065f7d3 /.snapshots btrfs subvol=@/.snapshots 0 0
    UUID=2F68-D3B2       /boot/efi            vfat       umask=0002,utf8=true  0 0
    if you're wondering why there's no swap entries in my /etc/fstab file that's because I deleted them in an effort to speed up OT (per this other thread of mine) as I have 16 GB RAM and I rarely use anymore than 4 GB. If you're wondering if the UUIDs are wrong well /dev/sda1 is my EFI partition and /dev/sda2 is my OT root partition and here is the output of:

    Code:
    $ ls -ld /dev/disk/by-uuid/* | grep sda
    lrwxrwxrwx 1 root root 10 Feb 15 10:26 /dev/disk/by-uuid/2F68-D3B2 -> ../../sda1
    lrwxrwxrwx 1 root root 10 Feb 15 10:26 /dev/disk/by-uuid/6fc8601b-4711-4af6-b39e-aebf5065f7d3 -> ../../sda2
    if you need any further information to help me please do ask, I really want to fix this error and seeing how I can't use snapper to rollback to a previous snapshot of my OT system (thanks to the fact that dbus can't be found when I'm in emergency mode) my only real option to get my OT system working again without you's help is to reinstall OT (which needless to say I will only do as a last resort).



    Thanks for your time,
    Brenton
    Brenton Horne: Linux enthusiast and writer of ​The Hornery.
    Seven favourite distros
    : Arch, Fedora, Gentoo, openSUSE Tumbleweed and Void.

  2. Default Re: After latest Tumbleweed upgrade I'm stuck in emergency mode as my file systems won't mount prope

    The solution was remarkably simple I merely had to run:

    Code:
    fsck /dev/sda1
    and now OT boots fine.
    Brenton Horne: Linux enthusiast and writer of ​The Hornery.
    Seven favourite distros
    : Arch, Fedora, Gentoo, openSUSE Tumbleweed and Void.

  3. #3

    Default Re: After latest Tumbleweed upgrade I'm stuck in emergency mode as my file systems won't mount prope

    Quote Originally Posted by fusion809 View Post
    The solution was remarkably simple I merely had to run:

    Code:
    fsck /dev/sda1
    and now OT boots fine.
    Man, don't you just love easy fixes like that?
    Tumbleweed on a Dell Inspiron 15 - 5578

  4. #4

    Default Re: After latest Tumbleweed upgrade I'm stuck in emergency mode as my file systems won't mount prope

    ...mildly unrelated, but...


    The most appropriate way to update Tumbleweed is

    Code:
    zypper dup  --no-allow-vendor-change
    Kind regards

    raspu

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •