Rebooting stops wih an error

It stops rebooting and tries to save the error file rdsosreport.txt but it can’t due to ro file system.

Adding rd.debug to boot cmd didn’t let me to save rdsosreport.txt file in order to attach it here.

Linux 4.18.8-1-default #1 SMP PREEMPT Sat Sep 15 14:10:30 UTC 2018 (f486469) x86_64 x86_64 x86_64 GNU/Linux

cat /etc/dracut.conf

# PUT YOUR CONFIG IN separate files
# in /etc/dracut.conf.d named "<name>.conf"
# SEE man dracut.conf(5) for options


### BEGIN /etc/grub.d/10_linux ###
menuentry 'openSUSE Tumbleweed'  --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-c6386772-4f32-4ac9-b48e-286f023ed45b' {
        set gfxpayload=keep
        insmod gzio
        insmod part_msdos
        insmod ext2
        set root='hd0,msdos1'
        if  x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 --hint='hd0,msdos1'  e3f35477-c0ab-46ba-92f2-d532a0aa0151
          search --no-floppy --fs-uuid --set=root e3f35477-c0ab-46ba-92f2-d532a0aa0151
        echo    'Loading Linux 4.18.8-1-default ...'
        linux   /vmlinuz-4.18.8-1-default root=/dev/mapper/fast0-root  resume=/dev/fast0/swap splash=silent quiet showopts resume=/dev/fast0/swap splash=silent quiet showopts
        echo    'Loading initial ramdisk ...'
        initrd  /initrd-4.18.8-1-default

Before reboot what is the content of /run/initramfs?

log/ with no contents and .need_shutdown with 0 bytes

OK, you have root on LVM and in this case LVM forces jump back to initrd on shutdown. I briefly tested it (without LVM) and it works as expected. You may try with “rd.break=shutdown”. This will stop in initrd shell immediately after jumping into initrd before doing anything. You can then look around (in particular, what is mounted and whether paths are read-write or not). Could you also provide “lsinitrd /boot/initrd” (probably too big to paste here, upload to

When was TW installed? Is it an upgrade? If yes, from what, and when was that originally installed? What is reported by?:

ls -l /var/run

TW is an upgrade from leap which was an upgrade from OS …

Here is lsinitrd /boot/initrd
and here /var/run

OS which?

Here is lsinitrd /boot/initrd
and here /var/run
That contains the output from ‘ls -l /var/run/’, not the output from ‘ls -l /var/run’. Output from ‘ls -l /var/’ would also suffice.

Probably OS 10.0 which became in time 13.2 then LEAP and not TW

l /var
total 260
drwxr-xr-x  19 root root    4096 May 28 21:10 ./
drwxr-xr-x  28 root root    4096 Sep 21 09:02 ../
drwxr-xr-x  10 root root    4096 May 25 23:22 adm/
drwxr-xr-x   3 root root    4096 Sep 24  2013 backup/
drwxr-xr-x  19 root root    4096 Aug 25 11:31 cache/
drwxr-xr-x   2 root root    4096 May 25 23:22 crash/
drwxr-xr-x   3 root root    4096 Jun 13 17:04 games/
drwxr-xr-x  88 root root    4096 Sep  7 17:46 lib/
drwxrwxr-x   5 root lock     120 Sep 23 08:46 lock/
drwxr-xr-x  29 root root   12288 Sep 23 08:46 log/
drwx------   2 root root   16384 Sep  9  2013 lost+found/
lrwxrwxrwx   1 root root      10 May 25 23:22 mail -> spool/mail/
drwxr-xr-x   3 root root    4096 Jun 29  2014 mpi-selector/
drwxr-xr-x   2 root root    4096 May 25 23:22 opt/
drwxr-xr-x  45 root root    1380 Sep 23 09:11 run/
drwxr-xr-x  15 root root    4096 May 25 23:22 spool/
drwxrwxrwt 415 root root  172032 Sep 23 08:47 tmp/
-rw-r--r--   1 root root     208 May 28 21:10 .updated
drwxr-xr-x   3 5000 vmail   4096 Sep 23  2013 vmail/
drwxr-xr-x   4 root root    4096 Sep 23 08:46 webmin/
drwxr-xr-x   3 root root    4096 Nov 16  2017 yp/

This is what is wrong.

drwxr-xr-x  45 root root    1380 Sep 23 09:11 run/

It needs to be: -> /run

1104235 – openSUSE Leap 15.0 hangs on reboot due to /var/run being bind mounted to /run covers it. Comment 15 there provides a solution.

changing mode to /var/run didn’t helped

here is rdsosreport

What do you mean by change mode? The /var/run directory must be removed and a symlink to /run created as was explained in bug comment 15. This requires a “rescue” boot, since /var/run is always busy while the TW installation is running.

Mode?!? Please show exact commands you used; ideally copy-paste the full commands and their output. Otherwise it is absolutely unclear what you did. Error symptoms match mentioned bug report exactly.

here is rdsosreport

This is too early, sorry, due to it stops during boot. If you just Ctrl-D it should continue with booting and then stop during shutdown.

So, this is the solution! You were absolutely right! Thanks!

After rescue booting

cd /var
ln -s ../run -> /var/run