*** This bug is a duplicate of bug 1549653 ***
https://bugs.launchpad.net/bugs/1549653
** Project changed: linuxmint => gnome-disk-utility (Ubuntu)
** This bug has been marked a duplicate of bug 1549653
Disks utility doesn't remove previous record in /etc/fstab
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/1687694
Title:
Disk partition not removed from fstab after deleting partition
Status in gnome-disk-utility package in Ubuntu:
New
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1687694/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
