No error encountered while deleting partitions, but when I attempted to
resize sda6 (ext3) back to it's original size I encountered another
error:
GParted 0.5.0
Libparted 1.8.8.git-dirty
Grow /dev/sda6 from 18.69 GiB to 34.36 GiB 00:00:59 ( ERROR )
calibrate /dev/sda6 00:00:01 ( SUCCESS )
path: /dev/sda6
start: 77095998
end: 116294534
size: 39198537 (18.69 GiB)
check file system on /dev/sda6 for errors and (if possible) fix them 00:00:52
( SUCCESS )
e2fsck -f -y -v /dev/sda6
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
21522 inodes used (1.75%)
729 non-contiguous files (3.4%)
19 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 3471/232/0
2888335 blocks used (58.95%)
0 bad blocks
2 large files
18458 regular files
3013 directories
0 character device files
0 block device files
0 fifos
0 links
42 symbolic links (26 fast symbolic links)
0 sockets
--------
21513 files
e2fsck 1.41.9 (22-Aug-2009)
grow partition from 18.69 GiB to 34.36 GiB 00:00:03 ( SUCCESS )
old start: 77095998
old end: 116294534
old size: 39198537 (18.69 GiB)
new start: 77095998
new end: 149147459
new size: 72051462 (34.36 GiB)
check file system on /dev/sda6 for errors and (if possible) fix them 00:00:02
( ERROR )
e2fsck -f -y -v /dev/sda6
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
e2fsck 1.41.9 (22-Aug-2009)
e2fsck: No such file or directory while trying to open /dev/sda6
grow file system to fill the partition 00:00:01 ( ERROR )
resize2fs /dev/sda6
resize2fs 1.41.9 (22-Aug-2009)
open: No such file or directory while opening /dev/sda6
libparted messages ( INFO )
Error informing the kernel about modifications to partition /dev/sda6 -- Device
or resource busy. This means Linux won't know about any changes you made to
/dev/sda6 until you reboot -- so you shouldn't mount it or use it in any way
before rebooting.
The kernel was unable to re-read the partition table on /dev/sda (Device or
resource busy). This means Linux won't know anything about the modifications
you made until you reboot. You should reboot your computer before doing
anything with /dev/sda.
So a better title for this bug would have been: Lucid Gparted fails with
some create, format, resize operations.
And at least ext4, SWAP, and ext3 all seem to be effected.
--
Lucid Gparted fails to create multiple partitions
https://bugs.launchpad.net/bugs/510179
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
