Re: Reboot After Systemd 215-5 Upgrade
On Sunday 28 September 2014 15:59:33 PaulNM wrote:
> On 09/28/2014 03:26 PM, Carlo wrote:
> > 2014-09-28 20:31 GMT+02:00 David Baron <d_baron@012.net.il>:
> >> Here 'tis: ~$ 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/sda1 during installation, now sda2
> >> UUID=fca39bca-d795-4664-8c6f-cac459fbd468 / ext4
> >> errors=remount-ro 0 1
> >> # /home was on /dev/sda9 during installation
> >> UUID=2095d2ef-a14d-48ed-b3a5-aba40a27873e /home ext4
> >> defaults
> >> 0 2
> >> # /tmp was on /dev/sda8 during installation
> >> UUID=dbe4a9c0-8c8a-450e-ad2a-480b419934e2 /tmp ext4
> >> defaults
> >> 0 2
> >> # /usr was on /dev/sda5 during installation
> >> UUID=61df1af1-f443-4a9d-aa66-dd13abaa5f3b /usr ext4
> >> defaults
> >> 0 2
> >> # /var was on /dev/sda6 during installation
> >> UUID=b8ad0d22-11c6-4840-8dca-6882459ce3ab /var ext4
> >> defaults
> >> 0 2
> >> # swap was on /dev/sda7 during installation
> >> UUID=d73c4cba-9bc3-40a5-b5b3-35770b8d5b9c none swap sw
> >> 0 0
> >> /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
> >>
> >> This is as generated by the installation except I moved the root
> >> partition to another disk. Refer to a current thread on the too-small
> >> partitions made by the installation. I changed the comment and the UUID.
> >> Everything else is by the installation.
> >
> > I know that systemd-remount-fs.service is an early-boot service that
> > applies mount options listed in fstab.
> >
> > I think there is a problem with this line ->
> > "UUID=fca39bca-d795-4664-8c6f-cac459fbd468 / ext4
> > errors=remount-ro 0 1" because "errors=remount-ro" means
> > that / is in auto-mounting as READ ONLY.
>
> No, that means mount read-only if there are errors detected. Unless
> there is a separate "ro", it'll be mounted read-write normally.
>
As I responded.
After a hard reboot, got one FAILED remount message. After saying it is
"clean." The remount is not being done for real if things work normally
afterwards.
Should this be submitted as a bug against systemd or possibly initramfs?
Reply to: