You have been subscribed to a public bug:
One of the disks in my machine had two partitions on it. A test install
of MINT on ext4 and a swap partition (machine was original dual botted).
The ext4 partition was mounted via /etc/fstab on startup. I deleted both
partitions and re-partitioned the disk with a single ext4 partition
using the GUI tool:
gnome-disk-utility 3.18.3.1
UDisks 2.1.7 (built against 2.1.6)
When I rebooted the machine it failed to boot complaining of TOCBLOCK
database corrupt. All I could get was a command line.
Took me a few hours to work out the problem was that the partition was
mentioned in /etc/fstab.
I'd have expected that the disk utility would have tidied that up when
the original partition was deleted.
This does kind of relate to #1458474. Although the cause is different
(and in my case I'd argue the utility should handle it) the mitigation
is probably the same, allow the machine to Skip the mount of not found
or problem disks.
Running Mint 18.1, cinnamon 64 bit.
** Affects: gnome-disk-utility (Ubuntu)
Importance: Undecided
Status: New
--
Disk partition not removed from fstab after deleting partition
https://bugs.launchpad.net/bugs/1687694
You received this bug notification because you are a member of Ubuntu Desktop
Bugs, which is subscribed to gnome-disk-utility in Ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
