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 er
As one of the original reporters, I agree completely with ironstorm.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431743
Title:
fails to boot due to read-ony file system
To manage notifications a
This should be reopened.
This is a potentially serious regression that broke on my machine
upgrading from 14.10 to 15.04. The way in which it broke left me
looking at a shell that told me despite my FS being mounted "rw"
according to "mount", all commands were failing because of "Read-only
file
Toni, please don't follow up on already closed bugs that you did not
report. Please open a new one (ubuntu-bug systemd), and attach fstab and
"journalctl -b" output. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
What I am missing on my fstab? And is there a way to regenerate it?
** Attachment added: "fstab"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431743/+attachment/4383045/+files/fstab
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I upgraded from Kubuntu 14.10 to 15.04 release and was greeted with this
problem. I don't think also that "Invalid" flag is correct here. A real
problem. Black screen on boot after update is not nice. Fortunately I
found this -> selecting upstart boot I was able to get the system
working.
I haven'
But upstart managed to boot without the root partition being written in
/etc/fstab. So it's a regression. I think it should be possible to write
an upgrade script to check if there's a root file-system in /etc/fstab
and add it if there isn't.
--
You received this bug notification because you are
So the "sddm not enabled" issue is a but in sddm, and the "root
partition missing from /etc/fstab" was a local problem. Hence I think
this can be closed.
** This bug is no longer a duplicate of bug 1432171
[udev] Shows "starting version 219" boot message even with "quiet"
** Changed in: system
*** This bug is a duplicate of bug 1432171 ***
https://bugs.launchpad.net/bugs/1432171
** This bug has been marked a duplicate of bug 1434847
Can't boot with Systemd
** Tags added: vivid
** This bug is no longer a duplicate of bug 1434847
Can't boot with Systemd
** This bug has been ma
I think I worked it out. I added my root partition to /etc/fstab, and
that seems to have fixed the problem, though I'll try a few more runs to
make sure!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
It seems that they are 2 independent issues that were mixed in this bug
report. As Vasco seems to have something closer to the initial issue,
let's use if for it. i'll try ssdm and poke Eugene if more info were
needed.
--
You received this bug notification because you are a member of Ubuntu
Bugs
Hi, sry for being late. I have been using upstart all along.
I am happy to say I tried the workaround Ricard suggested and it worked for
me:" Did you do CTRL + ALT + F1? and log in?
Then, sudo systemctl enable sddm.service -f
sudo reboot"
Not sure what this means for things going forward, at leas
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431743
Title:
fa
Just tried that, and unfortunately it doesn't work. :( I also tried the
most recent mainline kernel from kernel ppa (4.0 rc3 IIRC), and it
didn't work either. I don't think it's a kernel issue.
I also tried running "mount -o remount,rw /" off a normal VT rather than
the debug shell, and it worked
@Vasco: I have infinite trouble with the latest -8 and -9 kernels,
resulting in quite a similar situation as in your "hang1.jpg". Could you
try booting -7 again? That was the last kernel that worked for me,
perhaps it's similar to your situation?
--
You received this bug notification because you
OK, thanks. I ran out of ideas why the file system is readonly. I'll
continue here in 1.5 weeks when I'm back from vacation. In the meantime
I suggest you install "upstart" again to get a working system.
** Changed in: systemd (Ubuntu)
Status: Incomplete => New
** Changed in: systemd (Ubun
Remounting from the debug shell works, and allowed me to link mtab to
/proc/mounts. However, on reboot the error manifested again! I attach
the journal from after the reboot.
** Attachment added: "journal2.txt"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431743/+attachment/4344496/
Also, here are the contents of /proc/mounts, in case that helps.
** Attachment added: "mounts.txt"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431743/+attachment/4344497/+files/mounts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Also affects me. Boots with upstart but hangs at starting 219. After
this message it tried to access every removable device and errored on
each one with a "no medium found on dev/sdx" message. After unplugging
my card reader from the motherboard these errors disappeared but the 219
error remained.
19 matches
Mail list logo
