[systemd-devel] more verbose debug info than systemd.log_level=debug?

[Chris Murphy]

OK so I had the idea to uninstall plymouth, since that's estensibly
what's holding up the remount read-only. But it's not true.

Sending SIGTERM to remaining processes...
Sending SIGKILL to remaining processes...
Unmounting file systems.
Remounting '/tmp' read-only with options 'seclabel'.
Unmounting /tmp.
Remounting '/' read-only with options 'seclabel,attr2,inode64,noquota'.
Remounting '/' read-only with options 'seclabel,attr2,inode64,noquota'.
Remounting '/' read-only with options 'seclabel,attr2,inode64,noquota'.
All filesystems unmounted.
Deactivating swaps.
All swaps deactivated.
Detaching loop devices.
device-enumerator: scan all dirs
  device-enumerator: scanning /sys/bus
  device-enumerator: scanning /sys/class
All loop devices detached.
Detaching DM devices.
device-enumerator: scan all dirs
  device-enumerator: scanning /sys/bus
  device-enumerator: scanning /sys/class
All DM devices detached.
Spawned /usr/lib/systemd/system-shutdown/mdadm.shutdown as 7058.
/usr/lib/systemd/system-shutdown/mdadm.shutdown succeeded.
system-shutdown succeeded.
Failed to read reboot parameter file: No such file or directory
Rebooting.
[   47.288419] Unregister pv shared memory for cpu 0
[   47.289140] Unregister pv shared memory for cpu 1
[   47.290013] sd 1:0:0:0: [sda] Synchronizing SCSI cache
[   47.315486] reboot: Restarting system
[   47.316036] reboot: machine restart


There are still three attempts to remount read-only. Why? Separately
checking the file system following this reboot, the fs is clean, not
dirty. So one of those remounts must have worked this time. And the
file system is bootable.

There really isn't enough debugging within system to isolate
everything that's going on here.



Chris Murphy