touch-packages team mailing list archive

[ibob63 <1431743@xxxxxxxxxxxxxxxxxx>]

I agree with ironstorm.  This bug clearly needs to be reopened.

I just upgraded my server and it became read only.  I can confirm that
the problem for me was that after upgrade the fstab had the wrong UUID
in it.  Bizarrely, it was changed from:

UUID=18254707-08e8-494e-b456-938592928a5e / ext4 errors=remount-ro 0 1

to:

UUID=815063a9-c956-44a6-ab11-05e1d0bb3a58 / ext4 errors=remount-ro 0 1

The server was virtual and luckily I took a backup before upgrading.  I
therefore restored the backup, upgraded again and then dropped into the
command prompt and corrected the fstab before rebooting the server.

As Ironstorm suggests, this should be a post install check or perhaps
the bug which is causing this issue can be resolved.  I'm sure that this
issue will affect lots of other people and it should be reopened as an
issue.

-- 
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/1431743

Title:
  fails to boot with broken or missing root fs fstab entry

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I have just recently done a sudo apt-get upgrade, noting something about an included 219 update -- after consequent reboot, the system now hangs at starting 219. No light on Caps Lock. I have since been using upstart. 
  Kernel using - I am on: Linux kubuntu 3.19.0-9-generic #9-Ubuntu SMP Wed Mar 11 17:50:03 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux  
  Same error when I try the 3.19.0.7-generic kernel.
  I have updated Grub, no change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431743/+subscriptions