I have a solution but it is right or wrong i am not sure but thank god it works
for me ☺️
My system has stucked in maintenance mode ctrlD and blah blah blah...
#nano /etc/fstab
Comment which has dump and pass value = 0
If this is unwritable then
#cp -r fstab fstb1
#rm fstab
#mv fstab1 fstab
Now
I confirm that this bug is still there.
On a workstation I could not boot with systemd but could successfully boot with
upstart.
I had to manually edit fstab and add the / line to have systemd working again.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Hans-Gregor, this looks like bug 1453738 (broken swap with LVM+home dir
encryption).
--
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
Hi,
I think I have a related problem, that I am not able to solve.
I have the following setup:
sda=SSD
sda1=root (luks, ext4)
sda2=boot (ext3)
sda3=Win7
sdb=HDD
sdb1=
/dev/mapper/ssd-root / ext4
defaults,noatime,nodiratime,errors=remount-ro 0 1
/dev/mapper/vgubuntu-home
sorry for half finished post above!
Hi,
I think I have a related problem, that I am not able to solve.
I have the following setup:
sda=SSD (encrypted root luks)
sdb=HDD (encrypted data in encrypted lvm2)
I checked the UUIDs they are correct. The very same files work with
Upstart. With systemd I
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
** Summary changed:
- fails to boot due to read-ony file system
+ fails to boot with broken or missing root fs fstab entry
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
7 matches
Mail list logo
