The blkid command is part of util-linux. See,
http://en.wikipedia.org/wiki/Util-linux
I think you should be able to report a bug against the util-linux
package in Ubuntu 12.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Thanks for the response Stjepan.
I am fairly confident that this problem is resolved with GParted 0.11.0,
and since the original setup is no longer available for testing I
recommend that this bug be closed (at least when 0.11.0 is available in
Ubuntu).
--
You received this bug notification becau
The enhancement to address this bug report has been included in GParted
0.11.0 released upstream on Dec. 13, 2011.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/614994
Title:
Gparted displays Chines
This problem of not enough room to display all text usually occurs only
if there is some type of problem with the file system. When this occurs
and the user's screen is not large enough, the dialog box is shown as in
the screen shot from post #1.
One possible solution would be to place the variab
Would you please also provide the output from the following command
while GParted is scanning:
ps -ef | egrep -i "dosfsck|ntfsresize"
If the problem occurs with NTFS or FAT file systems, then sometimes
running a disk check or defragmenting the file system can fix the
problem.
--
You received th
Phillip, GParted uses the available utilities it can find to prevent
mounting of disks while GParted is running.
The script that starts GParted can be viewed at the following link:
http://git.gnome.org/browse/gparted/tree/gparted.in
GParted checks for hal-lock, udisks, and devkit-disks. In the c
The problem with GParted taking a long time scanning a non-existent floppy
drive is identified in the FAQ.
http://gparted.org/faq.php#faq-11
The relevant bug report is:
Bug 351753 - missing floppy causes loop on scan devices
https://bugzilla.gnome.org/show_bug.cgi?id=351753
The fix back then inv
This is related to the following upstream bug report:
Bug 467925 - gparted: add progress bar during operation
https://bugzilla.gnome.org/show_bug.cgi?id=467925
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
This bug report is related to the following upstream report:
Bug 612928 - file size units not consistent with GNOME desktop
https://bugzilla.gnome.org/show_bug.cgi?id=612928
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
This problem is fixed in GParted 0.10.0.
The relevant upstream bug report is:
Bug 438573 - cancel out overlapping actions
https://bugzilla.gnome.org/show_bug.cgi?id=438573
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
Carla, do you have the dmraid package installed?
If so, would you please try the following command and let us know the
results:
sudo dmraid -sa -c
This is to test if scanning of the floppy drive is related to the dmraid
command.
--
You received this bug notification because you are a memb
Okay, that confirms that dmraid is not part of the problem. I didn't
think it was, but it is always good to check.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/910379
Title:
Gparted does not start
Thanks for checking kpartx. GParted removed use of kpartx in version
0.8.1, which was adopted in Oneiric Ubuntu (11.10).
Carla, would you be able to provide the results of the following
command?
sudo blkid -c /dev/null
--
You received this bug notification because you are a member of Ubun
Aha! So the delay is due to calling blkid.
Phillip, are you able to bring this problem with blkid searching non-
existent floppy drive to the attention of the right people?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Phillip,
In the past if I changed the label of a partition with GParted and then
called blkid, I received the cached result which was the old label.
That is why I used the "-c /dev/null" to force blkid to re-read the
information.
I have not tested to see if blkid still has this same behaviour.
-
> On 1/5/2012 4:05 PM, Curtis Gedak wrote:
>> Phillip, are you able to bring this problem with blkid searching non-
>> existent floppy drive to the attention of the right people?
>
> I don't think it is considered a bug by anyone. If the bios claims you
> have a flopp
Since GParted already includes a call to "udevadm settle" I removed the
"-c /dev/null" and tested with ubuntu 11.04 and 10.04. Both of these
worked correctly. :-)
As such I have committed the following patch to the upstream GParted
code repository:
Fix long scan problem when BIOS floppy setting
Perhaps you are simply missing a dependency.
Would you please try the following command to ensure the dependencies
are installed. This command last tested with Ubuntu 11.10 if I recall
correctly.
sudo apt-get install build-essential e2fsprogs uuid uuid-dev \
gnome-com
When you tested, did you still have your BIOS incorrectly set to say a
floppy drive is present when there really isn't a floppy drive
physically installed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Based on that then I think this bug can be closed.
I do plan to keep the change to GParted since it does not appear to
cause any harm, and it will offer a slight performance improvement when
GParted rescans disk devices.
--
You received this bug notification because you are a member of Ubuntu
Bu
Phillip, GParted still uses the mlabel command from the mtools package
to set the label.
Having said that, in GParted 0.11.0 we switched to only using blkid
results when a file system specific tool cannot be found. Hence this
bug is most likely resolved with GParted 0.11.0.
Stjepan, GParted 0.11
** Bug watch added: GNOME Bug Tracker #667511
https://bugzilla.gnome.org/show_bug.cgi?id=667511
** Also affects: gparted via
https://bugzilla.gnome.org/show_bug.cgi?id=667511
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubu
Would you be able to describe this problem in another way?
I do not know what you mean by "Gparted locks EVERY partition to the launcher".
Perhaps a screen shot would help?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
While looking through the MythTV backend setup, I came across a setting
to disable automatic database backups. I have seen this setting in
MythTV 0.24, 0.25, and 0.26.
Use the following steps to locate this setting:
1) Start MythTV Backend Setup. In Mythbuntu the menu option is:
Applicatio
John and Antonio19,
When this problem occurs, is there at least one disk device that does
not contain a valid partition table?
You can check using the "sudo fdisk -l" command.
I am curioius because this might be related to a gparted upstream bug
report:
Bug 697518 - gparted scans forever blank
Do you have a floppy device enabled in your BIOS, but no physical
floppy drive in your computer?
See:
Why does "Scanning all devices..." take exceedingly long on some computers?
http://gparted.org/faq.php#faq-11
This has been a problem in the past.
--
You received this bug notification becaus
This crash sounds suspiciously similar to the following upstream bug
report:
682658 - GParted crash by pressing Esc in dialogs with number entry
https://bugzilla.gnome.org/show_bug.cgi?id=682658
If these are the same, then the problem was fixed in the upstream
release of GParted 0.14.0.
** Bug w
This is a duplicate of an old upstream bug report.
See Bug 655215 - NTFS partition resize fails
https://bugzilla.gnome.org/show_bug.cgi?id=655215
This problem is fixed with GParted versions 0.9.1 and higher.
** Bug watch added: GNOME Bug Tracker #655215
https://bugzilla.gnome.org/show_bug.cgi
LAZA, the problem stems from a change in error handling in ntfsresize
v2011.4.12AR.4 (libntfs-3g).
If you use an older version of ntfsresize (e.g., 2.0.0), or a newer
version, such as ntfsresize v2012.1.15AR.1, then the problem goes away.
If you use GParted 0.9.1 or higher then you can even use n
Parted is the text interface to the libparted libary. Both of these are
maintained by the Parted project.
http://www.gnu.org/software/parted/
GParted is a graphical interface that uses the same above listed libparted
library. GParted is maintained by the GParted project.
http://gparted.org/
I
To try to troubleshoot the problem, would you be able to provide the
output from the following two commands?
sudo fdisk -l -u
Where one of the options is a lower case "L" and not the number one.
sudo parted -l
Where one of the options is a lower case "L" and not the number one.
Also,
As far as I know, packages from one distribution are not guaranteed to
work on another. Since the package referred to in this report is not
from Ubuntu, Phillip has marked this report as invalid.
You might consider compiling GParted from source code so that you have
the latest version.
--
You
@Kieran, perhaps your BIOS is incorrectly set to indicate that the
floppy drive is present when there is no physical floppy drive present?
Often an incorrectly set BIOS can cause this problem.
If not, other things to try are to defragment NTFS and FAT file systems.
--
You received this bug noti
@dino, the problem with "/etc/resolv.conf not created during bootstrap" is
related to the GNU/Linux OS, and does not involve a change to the GParted
application code.
https://bugzilla.gnome.org/show_bug.cgi?id=680498
** Bug watch added: GNOME Bug Tracker #680498
https://bugzilla.gnome.org/sho
I just did some testing with the Beta1 precise-desktop-amd64.iso.
If I try to install gparted prior to performing a "sudo apt-get update",
then I too receive an error. The error mentioned somting about the IP
address for the libgtkmm-2.4-1c2a package cannot be found. I would
have copied the mes
'Just downloaded the precise-desktop-amd64.iso from March 25, 2012 and
installed it into a VM.
Next I opened a terminal prompt and entered:
sudo apt-get install gparted
This installed both libgtkmm-2.4-1c2a and gparted.
@jerrylamos,
Can you try "sudo aptitude reinstall libgtkmm-2.4-1c2a"?
I think the problem is already solved.
With the original precise-desktop-amd64.iso beta1 I was able to
duplicate the problem you experienced.
With the latest precise-desktop-amd64.iso from March 25, 2012, I could
not duplicate the problem. It just worked properly.
--
You received this bug noti
@dino99. Thanks for running the extra tests. The concern was that
"blkid -c /dev/null" would take a long time on a BIOS that was
incorrectly configured to indicate it had a floppy device when no
physical device was present. Phillip is correct, this is fixed in
GParted 0.12.0.
@Phillip, GParted
This problem should be resolved with the upstream release of GParted
0.12.0 on Feb. 21, 2012.
A dialog box will pop up asking if the file system should be converted
to FAT32. The user can then choose how to proceed.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
The ability to set a new UUID has been added to GParted 0.12.0 released
upstream on Feb 21, 2012.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/737387
Title:
gparted should offer option to change UU
The upstream patch for the change on blkid invocation can be found at
the following link:
Fix long scan problem when BIOS floppy setting incorrect
http://git.gnome.org/browse/gparted/commit/?id=18f863151c82934fe0a980853cc3deb1e439bec2
This patch is planned for inclusion in the upstream GParted 0.
@dino99. GParted performs a "udevadm settle" before re-reading the
blkid cache. Hence the cache should already have been updated before
GParted proceeds with the device refresh.
In my testing I did find this to be the case and to work properly.
--
You received this bug notification because yo
@dino99. To confirm that the problem is with blkid, would you be able
to try running the following command with your computer setup?
sudo blkid -c /dev/null
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
** Bug watch added: GNOME Bug Tracker #670160
https://bugzilla.gnome.org/show_bug.cgi?id=670160
** Also affects: gparted via
https://bugzilla.gnome.org/show_bug.cgi?id=670160
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubu
>From checking the upstream repository, the four files listed above do
not exist and have not been checked into git.
Upstream Repository:
http://git.gnome.org/browse/gparted/
For these translations to be complete, a location specific screen shot
of gparted_window.png is required.
Perhaps the fac
Where in the Ubuntu sources did you observe these files?
I checked in the bazaar source repository for one of these files, namely
"help/ru/figures/gparted_window.png" and I did not observe the file. The link
I looked at in bazaar is as follows:
http://bazaar.launchpad.net/~vcs-imports/gparted/m
*** This bug is a duplicate of bug 936368 ***
https://bugs.launchpad.net/bugs/936368
>From an application developer point of view I don't think that I can
address these package debsums.
Perhaps Dave Lentz is correct that these bug reports belong to the
packaging process. There might have be
** Bug watch added: GNOME Bug Tracker #670017
https://bugzilla.gnome.org/show_bug.cgi?id=670017
** Also affects: gparted via
https://bugzilla.gnome.org/show_bug.cgi?id=670017
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubu
@dino99, how long did it take for the blkid command to run?
When you performed the test, was your BIOS configured to indicate a floppy
drive was present when there actually was no physical floppy drive?
The patch mentioned above was included in GParted 0.12.0 released
upstream on February 21, 20
Unfortunately providing a time estimate with any degree of accuracy is
extremely difficult.
Part of the challenge stems from the various interfaces used to connect
disk devices to the computer. For example a disk connected via a USB
cable is *orders* of magnitude slower than the same disk connect
We welcome any assistance you might provide to assist with this problem.
And we would definitely be interested in a patch that addresses this
issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/958246
In comment #6 I was referring to the timing issue, which should be a
separate bug report.
We currently have someone working on improving progress feedback which
will also impact cancelling of steps.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
** Bug watch added: GNOME Bug Tracker #670171
https://bugzilla.gnome.org/show_bug.cgi?id=670171
** Also affects: gparted via
https://bugzilla.gnome.org/show_bug.cgi?id=670171
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubu
If I understand this bug report correctly, this problem was fixed with
the upstream release of GParted 0.11.0 on November 1, 2011.
The relevant upstream bug report is:
Bug 438573 - cancel out overlapping actions
https://bugzilla.gnome.org/show_bug.cgi?id=438573
** Bug watch added: GNOME Bug Trac
In terms of merging operations, only consecutive move/resize actions on
the same partition can be merged. As soon as another partition
move/resize is introduced the disk partition boundaries are changed so
we cannot simply merge non-consecutive move/resizes.
The series of steps listed in comment
If you encounter a similar problem in the future, see also:
How-to Fix Invalid MSDOS Partition Tables
http://gparted.org/h2-fix-msdos-pt.php
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1207968
Titl
The script that invokes GParted uses hal-lock, udisks, devkit-disks, and
most recently systemctl to exclusively lock or otherwise prevent
automounting on disk devices.
The history of these tools being installed by default in Ubuntu appears
to be:
- Uses HAL (Hardware Abstraction Layer) at least
Oops, sentence referring to fedora should read:
Hovever systemd is NOT installed by default in Ubuntu.
See https://en.wikipedia.org/wiki/Systemd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1060484
Dmitrijs,
Thank you for pointing out the udisks2-inhibit command.
Phillip,
Have you tested using udisks2-inhibit to see if it helps?
For example:
sudo /usr/lib/udisks2/udisks2-inhibit /usr/sbin/gpartedbin
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
> The only difference between disks & gparted is the syncing/refreshing occurs
> when
> gparted is opened, disk's only does so once some action (partitioning) has
> occurred.
When gparted starts up, it makes a call to the libparted library
function ped_disk_commit_to_os(). This checks to see if
or
C) Remove this check, and let resize/move operations fail later.
Note that based on Doug's comment #41, it appears that the blacklist will
be cleared whenever the partition table is actually changed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This problem is related to the following upstream bug report:
Bug 662537 - Ext4 unicode labels not shown correctly
https://bugzilla.gnome.org/show_bug.cgi?id=662537
This problem has been addressed with the following two upstream git commits:
Display ext2/3/4 unicode volume labels properly (#662
I believe that this bug report is related to the following upstream bug report:
https://bugzilla.gnome.org/show_bug.cgi?id=625337
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/610116
Title:
Label ge
GParted does not yet compile with the GNOME 3 libraries.
As a work around you might try installing the missing library
"libgtkmm-2.4-1c2a".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/878062
Title:
An extremely fragmented NTFS file system will also cause this delay. Be
sure to try defragmenting first.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/121943
Title:
Gparted scan for device infinite
Based on the error message, it appears that you might be experiencing
some hardware problems.
After using your computer for a while, you might try checking the output
of the dmesg command to see if any hardware errors are being reported.
--
You received this bug notification because you are a me
GParted uses the libparted library from the Parted project. Both the
GParted GUI and the libparted library were enhanced to handle sector
sizes larger than 512 bytes.
The problem you experienced is contained in the following snippet from
the gparted_details.htm log file:
resize2fs: Attempt
Through trial and error I have discovered two work-arounds that appear
to address the video tearing problem for 1080i video on Intel HD 3000
Graphics GPUs.
For mplayer see the following link:
https://bugs.freedesktop.org/show_bug.cgi?id=37686#c35
For mythtv see the following link:
https://bugs.fr
Mark Ballenger, can you confirm the version of GParted that you are
using?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/617885
Title:
gparted crash at start: glibmm-ERROR **
--
ubuntu-bugs mailin
GParted uses programs, such as hal-lock, to disable automounting of disk
partitions.
If new partitions are being mounted upon creation, then it would appear
that somehow automounting is still active.
Would you be able to provide the output from the following command while
you have the GParted win
It would definitely appear that hal-lock is not running. Perhaps hal-
lock is not included on the Ubuntu Netbook Remix Live Distro?
On my system running kubuntu 10.04, I get the following results from the
ps command. The important entry here is hal-lock since hal-lock
prevents automounting of de
Thanks Ricardo and Pedro for reporting this problem. I have been able
to confirm the problem with the latest GParted (0.8.0) and I am
investigating solutions.
Regards,
Curtis Gedak
(Maintainer of GParted)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
>From looking at the log file Tom, it appears that the partition names do
not follow the general rule of thumb listed in comment #11.
Except from gparted_details.htm log file:
Could not stat /dev/mapper/pdc_jcchiiabp5 --- No such file or directory
Instead the partition name appears to have bee
Thanks Arto for reporting this concern.
Since there are situations in which a person wishes an exact duplicate
of the partition, I do not think it is wrong to leave the UUID the same.
Perhaps it would help if GParted displayed a message for copy operations
that indicated to the user that if they
An enhancement to address this problem has been committed to the
upstream GNOME git repository for inclusion in the next upstream release
of GParted (0.9.0)
The relevant git commit can be viewed at the following link:
http://git.gnome.org/browse/gparted/commit/?id=ba28423e7625629eb5e72f7f57e4c40da
In the past, linux allocated 16 device numbers for the SCSI driver which
has device names of the form /dev/sdX (versus the IDE driver with device
names of the form /dev/hdX). One device number was used for the device
itself (/dev/sda), and the remaining 15 device numbers were used for the
partitio
Rob, following is some information for how GParted determines the unused
space in a partition.
For the ext4 file system GParted uses the following command to retrieve
information:
dumpe2fs -h /path-to-partition
Where /path-to-partition is something like /dev/sda3
Then GParted parses the ou
It is possible that the problem you experienced is related to the
partition alignment.
In GParted 0.5.9 and lower, the default was to align partitions to the nearest
cylinder.
In GParted 0.6.0 and higher, the default is to align partitions to the nearest
full MiB.
You could try choosing "Align
My analysis of the MBR can be found in the following bug-parted mailing list
post:
http://lists.gnu.org/archive/html/bug-parted/2011-02/msg00013.html
For those not wishing to read the analysis, the summary is that the
partition table is as follows:
Assuming my calculations are correct, a head_si
In the screen shot there is an exclamation point beside partition
/dev/sdc1. This indicates a problem. To learn more about the problem
you can select the partition and choose the menu option "Partition -->
Information".
--
You received this bug notification because you are a member of Ubuntu
Bu
Based on your report, it appears that the usb device has an invalid
partition table.
A work around is to copy your data to another device, write a new
partition table to the usb device, and then restore your data back to
the usb device.
A similar bug has been reported:
Verbatim USB stick crashes
Which version of GParted did you use?
A problem with a similar description was fixed in GParted 0.7.0:
gparted crash at start: glibmm-ERROR **
https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/617885
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
You might check the dmesg log to see if any hardware errors are being
reported for the disk device.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/668551
Title:
gparted crashes on reading SD card/fla
This looks like a duplicate of the following problem:
gparted crash at start: glibmm-ERROR **
https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/617885
This problem is resolved in the upstream GParted 0.7.0 release.
--
You received this bug notification because you are a member of Ubuntu
Bu
>From the gparted_details.htm log file, it appears that the disk device
does not contain a partition table that is recognized by
gparted/libparted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/660321
Based on your report, it appears that the usb device has an invalid
partition table.
As you discovered, a work around is to copy your data to another device,
write a new partition table to the usb device, and then restore your
data back to the usb device.
A similar bug has been reported:
Verbati
GParted 0.8.0 is planned for upstream release on Feb 15, 2011.
For more details on this release, see:
Development Plans for the Next Release of GParted (0.8.0)
http://gparted-forum.surf4.info/viewtopic.php?id=14391
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
Based on your report, it appears that the usb device has an invalid
partition table.
A work around is to copy your data to another device, write a new
partition table to the usb device, and then restore your data back to
the usb device.
A similar bug has been reported:
Verbatim USB stick crashes
To avoid the problem listed in comment #1, you will need to use GParted
0.7.0 or higher.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/672292
Title:
crash on wiped partitions
--
ubuntu-bugs mailin
Hi Phillip,
Other bug posts that are related to this bug post are as follows:
gparted just crash when my thumbdrive (Kingston DataTraveler G3 4Gb) is pluged
in.
https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/657784
Gparted close when mount usb device
https://bugs.launchpad.net/ubuntu/+s
>From your description, it would appear that the disk device has an
invalid MSDOS partition table.
A work-around to this problem is to:
1) Copy any data you have on this disk device to another disk device
2) Erase the invalid MSDOS partition table. The Master Boot Record
exists on the first s
Prior to erasing the MBR, you can make a backup copy with the following
command:
sudo dd if=/path-to-disk-device of=my-backup-copy.mbr bs=512
count=1
Where: /path-to-disk-device is something like /dev/sde
CAUTION: Be sure to type in the above command correctly, otherwise data
loss could r
This sounds similar to a previously reported bug:
bug #617885 - gparted crash at start: glibmm-ERROR **
This bug is fixed in upstream GParted 0.7.0. Please try GParted 0.7.0 or
higher to see if the problem is resolved for you. If you do not wish to
compile GParted directly, you can download a
How large is this USB drive (e.g., 4 GiB)?
What file system is being used (e.g, FAT32, NTFS)?
What is the output from the following command:
sudo parted /path-to-device unit s print
Where: /path-to-device is something like /dev/sdc
This is the device location for the USB drive
--
Y
Since the drive now works with parted after being reformatted, I suspect
a problem with the original formatting.
If you could find a similar drive for testing that would help.
Otherwise we do not know exactly what the problem is.
The original report has the following line:
Assertion (head_size <
If you do come across your second Verbatim drive, please also post the
output from:
fdisk -l -u /path-to-device
That way we can see what fdisk thinks the geometry is on the drive.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Thank you for reporting back with this information.
>From the fdisk output in comment #6 it appears that this disk device is
reporting 86 heads. From the current parted code, this is considered an
invalid disk geometry. Even so, I do not think a program crash is a
good response to this problem.
A fix for this problem was committed upstream and released with GParted 0.6.0
https://bugzilla.gnome.org/show_bug.cgi?id=324220#c66
Would you be able to try again with a newer version of GParted?
** Bug watch added: GNOME Bug Tracker #324220
https://bugzilla.gnome.org/show_bug.cgi?id=324220
-
Perhaps there was a space or other character that is normally escaped in
the /etc/mtab file? If so, see the following upstream bug report for
how this was fixed.
Bug 629592 - Unable to find Mount Point if it contains a Space Character
https://bugzilla.gnome.org/show_bug.cgi?id=629592
** Bug wat
The upstream bug report for this problem can be viewed at the following
link:
Bug 629592 - Unable to find Mount Point if it contains a Space Character
https://bugzilla.gnome.org/show_bug.cgi?id=629592
This problem has been fixed and included in upstream GParted 0.7.1
released on December 13, 2010
201 - 300 of 412 matches
Mail list logo
