*** This bug is a duplicate of bug 1431743 ***
https://bugs.launchpad.net/bugs/1431743
** This bug has been marked a duplicate of bug 1431743
fails to boot due to read-ony file system
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
It works now, thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1449101
Title:
Upgrading Kubuntu 14.10 to 15.04 boots to console (fails due to read-
ony file system)
To manage notifications a
Maybe a switch from HDD to SSD last year, I just cloned everything. I'll
try the fix asap.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1449101
Title:
Upgrading Kubuntu 14.10 to 15.04 boots to cons
Ah, as I suspected. Your fstab has
UUID=4bf3a782-af3c-46c4-b9ab-7988da79e800 / ext4errors
=remount-ro 0 1
which does not exist. According to blkid, you most likely want this
partition:
/dev/sda5: UUID="6f78ae63-3c82-451c-822f-4014f48ea22a" TYPE="ext4"
PARTUUID="7448d815-0
Anything else?
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1449101/comments/6
is the boot result + the remount + journal things you asked
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/144910
** Attachment added: "systemd journal attempts"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1449101/+attachment/4385882/+files/20150427_211545.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
"blkid" doesn't give ANY output
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1449101
Title:
Upgrading Kubuntu 14.10 to 15.04 boots to console (fails due to read-
ony file system)
To manage notif
Never mind, sudoed it. Linux desktop user here... Not very comfortable
in console :)
** Attachment added: "Output of "sudo blkid""
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1449101/+attachment/4385796/+files/blkid.txt
--
You received this bug notification because you are a membe
Yes, journalctl only works under systemd. If booting works under
upstart, then perhaps the UUID is wrong in /etc/fstab? Please give me
the output of "blkid" with a working boot (under upstart).
If the UUID matches, then something else is wrong; please do something
like
sudo mount -o remount,rw
journalctl -b just says "No journal files were found." when booted
successfully with the upstart. I'm unaware where or when I should type
this to get the output you need.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
10 matches
Mail list logo
