Public bug reported:
Kubuntu 17.10, fresh install
$ systemctl --version
systemd 233
Graphical session (sddm.service), systemd-resolved.service and
NetworkManager.service are not loaded due to system root being mounted
read-only
$ journalctl -b0
авг 18 01:27:45 Kseniya-Desktop kernel: Command line:
BOOT_IMAGE=/@/boot/vmlinuz-4.12.0-11-generic
root=UUID=87e60ca5-1b9f-4790-8b9e-6394b9d0a40e ro rootflags=subvol=@
This is the default kernel command line, ro means that the root filesystem must
be mounted read-only, then fsck is believed to be permormed, after what the FS
must be remounted rw (read-write)
But in my system (Ubuntu 17.10) the /home is mouned rw, but the root is still
ro.
I added to /etc/default/grub:
GRUB_CMDLINE_LINUX_DEFAULT="rw"
Now my kernel command line is:
авг 18 01:27:45 Kseniya-Desktop kernel: Command line:
BOOT_IMAGE=/@/boot/vmlinuz-4.12.0-11-generic
root=UUID=87e60ca5-1b9f-4790-8b9e-6394b9d0a40e ro rootflags=subvol=@ rw
No the root fs is mounted rw and sddm.service starts the graphical
session automatically.
BUT:
NetworkManager.service is not started automatically and should be started
manually (sudo systemctl start NetworkManager)
Due to network offline, network fileshares are not mounted.
I also noticed that there is no dependency from fsck in -.mount, but
there is in home.mount
$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sdc1 during installation
UUID=87e60ca5-1b9f-4790-8b9e-6394b9d0a40e / btrfs
subvol=@,defaults,compress=lzo 0 2
# /home was on /dev/sdc1 during installation
UUID=87e60ca5-1b9f-4790-8b9e-6394b9d0a40e /home btrfs
defaults,discard,compress=lzo,subvol=@home 0 3
# swap was on /dev/sdc2 during installation
UUID=cd2ba3e8-5ec9-49b3-aa2d-79082a8b8012 none swap sw
0 0
--------------------------
$ cat /run/systemd/generator/-.mount
# Automatically generated by systemd-fstab-generator
[Unit]
SourcePath=/etc/fstab
Documentation=man:fstab(5) man:systemd-fstab-generator(8)
Before=local-fs.target
[Mount]
Where=/
What=/dev/disk/by-uuid/87e60ca5-1b9f-4790-8b9e-6394b9d0a40e
Type=btrfs
Options=subvol=@,defaults,compress=lzo
--------------------------
$ cat /run/systemd/generator/home.mount
# Automatically generated by systemd-fstab-generator
[Unit]
SourcePath=/etc/fstab
Documentation=man:fstab(5) man:systemd-fstab-generator(8)
Before=local-fs.target
Requires=systemd-fsck@dev-disk-by\x2duuid-87e60ca5\x2d1b9f\x2d4790\x2d8b9e\x2d6394b9d0a40e.service
After=systemd-fsck@dev-disk-by\x2duuid-87e60ca5\x2d1b9f\x2d4790\x2d8b9e\x2d6394b9d0a40e.service
[Mount]
Where=/home
What=/dev/disk/by-uuid/87e60ca5-1b9f-4790-8b9e-6394b9d0a40e
Type=btrfs
Options=defaults,discard,compress=lzo,subvol=@home
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: systemd 233-8ubuntu3
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.6-0ubuntu5
Architecture: amd64
CurrentDesktop: KDE
Date: Fri Aug 18 01:30:46 2017
InstallationDate: Installed on 2017-07-23 (25 days ago)
InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
MachineType: Gigabyte Technology Co., Ltd. GA-A75M-DS2
ProcEnviron:
LANGUAGE=
TERM=xterm-256color
PATH=(custom, no username)
LANG=ru_RU.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.12.0-11-generic
root=UUID=87e60ca5-1b9f-4790-8b9e-6394b9d0a40e ro rootflags=subvol=@ rw
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/27/2012
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F1
dmi.board.name: GA-A75M-DS2
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias:
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd03/27/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-A75M-DS2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-A75M-DS2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-A75M-DS2
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug artful
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1711474
Title:
graphical session and network not start up due to root FS being
mounted read-only
Status in systemd package in Ubuntu:
New
Bug description:
Kubuntu 17.10, fresh install
$ systemctl --version
systemd 233
Graphical session (sddm.service), systemd-resolved.service and
NetworkManager.service are not loaded due to system root being mounted
read-only
$ journalctl -b0
авг 18 01:27:45 Kseniya-Desktop kernel: Command line:
BOOT_IMAGE=/@/boot/vmlinuz-4.12.0-11-generic
root=UUID=87e60ca5-1b9f-4790-8b9e-6394b9d0a40e ro rootflags=subvol=@
This is the default kernel command line, ro means that the root filesystem
must be mounted read-only, then fsck is believed to be permormed, after what
the FS must be remounted rw (read-write)
But in my system (Ubuntu 17.10) the /home is mouned rw, but the root is still
ro.
I added to /etc/default/grub:
GRUB_CMDLINE_LINUX_DEFAULT="rw"
Now my kernel command line is:
авг 18 01:27:45 Kseniya-Desktop kernel: Command line:
BOOT_IMAGE=/@/boot/vmlinuz-4.12.0-11-generic
root=UUID=87e60ca5-1b9f-4790-8b9e-6394b9d0a40e ro rootflags=subvol=@ rw
No the root fs is mounted rw and sddm.service starts the graphical
session automatically.
BUT:
NetworkManager.service is not started automatically and should be started
manually (sudo systemctl start NetworkManager)
Due to network offline, network fileshares are not mounted.
I also noticed that there is no dependency from fsck in -.mount, but
there is in home.mount
$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sdc1 during installation
UUID=87e60ca5-1b9f-4790-8b9e-6394b9d0a40e / btrfs
subvol=@,defaults,compress=lzo 0 2
# /home was on /dev/sdc1 during installation
UUID=87e60ca5-1b9f-4790-8b9e-6394b9d0a40e /home btrfs
defaults,discard,compress=lzo,subvol=@home 0 3
# swap was on /dev/sdc2 during installation
UUID=cd2ba3e8-5ec9-49b3-aa2d-79082a8b8012 none swap sw
0 0
--------------------------
$ cat /run/systemd/generator/-.mount
# Automatically generated by systemd-fstab-generator
[Unit]
SourcePath=/etc/fstab
Documentation=man:fstab(5) man:systemd-fstab-generator(8)
Before=local-fs.target
[Mount]
Where=/
What=/dev/disk/by-uuid/87e60ca5-1b9f-4790-8b9e-6394b9d0a40e
Type=btrfs
Options=subvol=@,defaults,compress=lzo
--------------------------
$ cat /run/systemd/generator/home.mount
# Automatically generated by systemd-fstab-generator
[Unit]
SourcePath=/etc/fstab
Documentation=man:fstab(5) man:systemd-fstab-generator(8)
Before=local-fs.target
Requires=systemd-fsck@dev-disk-by\x2duuid-87e60ca5\x2d1b9f\x2d4790\x2d8b9e\x2d6394b9d0a40e.service
After=systemd-fsck@dev-disk-by\x2duuid-87e60ca5\x2d1b9f\x2d4790\x2d8b9e\x2d6394b9d0a40e.service
[Mount]
Where=/home
What=/dev/disk/by-uuid/87e60ca5-1b9f-4790-8b9e-6394b9d0a40e
Type=btrfs
Options=defaults,discard,compress=lzo,subvol=@home
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: systemd 233-8ubuntu3
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.6-0ubuntu5
Architecture: amd64
CurrentDesktop: KDE
Date: Fri Aug 18 01:30:46 2017
InstallationDate: Installed on 2017-07-23 (25 days ago)
InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
MachineType: Gigabyte Technology Co., Ltd. GA-A75M-DS2
ProcEnviron:
LANGUAGE=
TERM=xterm-256color
PATH=(custom, no username)
LANG=ru_RU.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.12.0-11-generic
root=UUID=87e60ca5-1b9f-4790-8b9e-6394b9d0a40e ro rootflags=subvol=@ rw
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/27/2012
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F1
dmi.board.name: GA-A75M-DS2
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias:
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd03/27/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-A75M-DS2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-A75M-DS2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-A75M-DS2
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1711474/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
