Bug#881834: systemd: lib/systemd/systemd-remount-fs fails with /dev/nfs in fstab

[Duncan Hare]

Michael
Thank you for your quick response.
Should be:
The failure results the the root file system being mounted read-only, 

 and the system is unusable, because the file system is mounted read only.
Yes, I can log in.
verbose debug log from the boot process: see attached file "journalctl.log "

Please also include the output of the following commands:
systemctl status systemd-remount-fs : attached file "remount-fs.log"
sytemd-analyze dump: attached file "systemd.dump"


Thanks Duncan Hare

714 931 7952

      From: Michael Biebl <biebl at debian.org>
 To: Duncan Hare <dh at synoia.com>; 881834 at bugs.debian.org 
 Sent: Wednesday, November 15, 2017 9:51 AM
 Subject: Re: Bug#881834: systemd: lib/systemd/systemd-remount-fs fails with /dev/nfs in fstab
   
Control: tags -1 + moreinfo

Am 15.11.2017 um 18:12 schrieb Duncan Hare:
> systemd " lib/systemd/systemd-remount-fs" fails with following fstab and
> is processing fstab, and cannot process the fstab provided in the bug report.

I'm having trouble parsing this sentence

> The faulire resuts the the root file system being mounted read-only, 
> and the ysytem is unuseable.
> 
> fstab:
> 
> proc            /proc          proc    defaults          0      0
> PARTUUID=62bc0a1f-01  /boot          vfat    defaults          0      2
> #PARTUUID=62bc0a1f-02  /              ext4    defaults,noatime  0      1
> /dev/nfs          /    nfs    defaults,rw
> # a swapfile is not a swap partition, no line here
> #  use  dphys-swapfile swap[on|off]  for that
> the fstab it is uable to process is:

Please follow the instructions at
https://freedesktop.org/wiki/Software/systemd/Debugging/#index1h1
and provide a verbose debug log from the boot process.

Please also include the output of the following commands:
systemctl status systemd-remount-fs
sytemd-analyze dump

Those need to be run on the *affected* system.

Even if / is mounted ro, you should be able to either login on the
rescue shell or by starting a debug shell on tty9.

This information is vital to further investigate, especially since this
is supposed to be fixed since v231 which contains a fix for
https://github.com/systemd/systemd/issues/3590

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?


   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20171115/46e89ad8/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: journalctl.log
Type: text/x-log
Size: 71572 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20171115/46e89ad8/attachment-0004.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: remount-fs.log
Type: text/x-log
Size: 710 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20171115/46e89ad8/attachment-0005.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: systemd.dump
Type: application/octet-stream
Size: 444344 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20171115/46e89ad8/attachment-0002.obj>