Public bug reported:
Test Case:
1. Perform a first installation of Ubuntu
2. Reboot into the freshly installed system and verify everything works as
expected
3. Do a second installation and select "Install alonogside". Keep the size
proposed by the installer and proceed to the end of installation
4. Reboot
5. On boot, in the list of installed systems, select the first system installed
on the machine
6. Verify that it boots, you can login and it works as expected
Actual Result
The FS is corrupted and depending on the corruption it goes to initramfs, boots
but cannot login, ...
Attached is the journal of the system installed on the corrupted
partition.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 18 10:53:57 2018
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed
boot=casper only-ubiquity quiet splash ---
InstallationDate: Installed on 2018-10-18 (0 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug cosmic ubiquity-18.10.12
** Attachment added: "journal.broken"
https://bugs.launchpad.net/bugs/1798562/+attachment/5202478/+files/journal.broken
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798562
Title:
After a side by side installation, resized filesystem is corrupted
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1798562/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
