recent parted version reports bug

[joe]

I had a USB memory stick that was not recognized automatically by Ubuntu
Dapper 64 bit linux.

I used parted and got the following (pasted below - at the very end)
which said I had found a bug in parted.

This was the most recent version of parted in the Ubuntu repository.

(The memory stick had earlier worked, but I then reformatted it to FAT32
on a Windows machine.)


Extra Info : this was a 4 Gig USB Flash drive. It came with a windows
program on it, no documentation, which created a "secure" area on the
USB drive. After creating this secure area, plugging the device froze
windows. 

I then created a new DOS partition using Linux, but fdisk did not see
the part that had been made "secure".

Back to windows - in Windows, the USB device at least no longer seemed
to crash the machine. Then Windows said the USB device needed
formatting, which I did.

Still, the device was missing the space equal to the "secure" area
earlier created.

Then to try to restore the missing "secure" area, I used the same
program (I had copied ALL data from the drive before attempting to
create the secure area - as it turned out, a wise move!) to delete the
secure area, and free up the space.

This seemed to go ok - I then rebooted into Linux, and the USB drive was
not recognized automatically.



The program usbview gives this info for the memory stick (/dev/sdd on my
machine):

usb-storage
Serial Number: AA04012700017792
Speed: 480Mb/s (high)
USB Version:  2.00
Device Class: 00(>ifc )
Device Subclass: 00
Device Protocol: 00
Maximum Default Endpoint Size: 64
Number of Configurations: 1
Vendor Id: 090c
Product Id: 2000
Revision Number: 11.00

Config Number: 1
        Number of Interfaces: 1
        Attributes: 80
        MaxPower Needed: 300mA

        Interface Number: 0
                Name: usb-storage
                Alternate Number: 0
                Class: 08(stor.) 
                Sub Class: 6
                Protocol: 50
                Number of Endpoints: 2

                        Endpoint Address: 81
                        Direction: in
                        Attribute: 2
                        Type: Bulk
                        Max Packet Size: 512
                        Interval: 0ms

                        Endpoint Address: 02
                        Direction: out
                        Attribute: 2
                        Type: Bulk
                        Max Packet Size: 512
                        Interval: 31875us



The following was output by dmesg:


[  421.348018] FAT: utf8 is not a recommended IO charset for FAT
filesystems, filesystem will be case sensitive!
[  421.348421] FAT: invalid media value (0xb9)
[  421.348476] VFS: Can't find a valid FAT filesystem on dev sdd.
[  421.352788] FAT: invalid media value (0xb9)
[  421.352854] VFS: Can't find a valid FAT filesystem on dev sdd.
[  421.356996] NTFS-fs warning (device sdd): parse_options(): Option
iocharset is deprecated. Please use option nls=<charsetname> in the
future.
[  421.357418] NTFS-fs warning (device sdd): is_boot_sector_ntfs():
Invalid boot sector checksum.
[  421.357531] NTFS-fs error (device sdd): read_ntfs_boot_sector():
Primary boot sector is invalid.
[  421.357642] NTFS-fs error (device sdd): read_ntfs_boot_sector():
Mount option errors=recover not used. Aborting without trying to
recover.
[  421.357834] NTFS-fs error (device sdd): ntfs_fill_super(): Not an
NTFS volume.
[  421.362202] NTFS-fs warning (device sdd): is_boot_sector_ntfs():
Invalid boot sector checksum.
[  421.362349] NTFS-fs error (device sdd): read_ntfs_boot_sector():
Primary boot sector is invalid.
[  421.362450] NTFS-fs error (device sdd): read_ntfs_boot_sector():
Mount option errors=recover not used. Aborting without trying to
recover.
[  421.362580] NTFS-fs error (device sdd): ntfs_fill_super(): Not an
NTFS volume.
[  421.381696] HFS+-fs: unable to find HFS+ superblock
[  421.386618] HFS+-fs: unable to find HFS+ superblock
[  421.401714] VFS: Can't find a HFS filesystem on dev sdd.
[  421.406341] VFS: Can't find a HFS filesystem on dev sdd.
[  421.410659] VFS: Can't find ext3 filesystem on dev sdd.
[  421.414970] VFS: Can't find ext3 filesystem on dev sdd.
[  421.429376] VFS: Can't find an ext2 filesystem on dev sdd.
[  421.434148] VFS: Can't find an ext2 filesystem on dev sdd.
[  421.453969] ReiserFS: sdd: warning: sh-2021: reiserfs_fill_super: can
not find reiserfs on sdd
[  421.458962] ReiserFS: sdd: warning: sh-2021: reiserfs_fill_super: can
not find reiserfs on sdd
[  421.517044] SGI XFS with ACLs, security attributes, realtime, large
block/inode numbers, no debug enabled
[  421.517164] SGI XFS Quota Management subsystem
[  421.518726] XFS: bad magic number
[  421.518831] XFS: SB validate failed
[  421.523175] XFS: bad magic number
[  421.523287] XFS: SB validate failed
[  421.536481] JFS: nTxBlock = 8027, nTxLock = 64216
[  551.563000] cdrom: open failed.
[  551.564233] cdrom: open failed.
[  578.586900] parted[8357]: segfault at 0000000000000000 rip
00002aaaab1269d2 rsp 00007fffffdbc478 error 4
[  597.434071] parted[9442]: segfault at 0000000000000000 rip
00002aaaab1269d2 rsp 00007fffff90bb38 error 4


**********************************

Here is the output of parted:

$ parted /dev/sdd
GNU Parted 1.6.25.1
Copyright (C) 1998 - 2005 Free Software Foundation, Inc.
This program is free software, covered by the GNU General Public
License.

This program is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied
warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See
the GNU General Public License for more
details.

Using /dev/sdd
(parted) check
Partition number? 1
Error: The file system's CHS geometry is (248, 1001, 32), which is
invalid.  The partition table's CHS geometry is
(495, 255, 63).  If you select Ignore, the file system's CHS geometry
will be left unchanged.  If you select Fix,
the file system's CHS geometry will be set to match the partition
table's CHS geometry.
Fix/Ignore/Cancel? c
Error: The file system's CHS geometry is (248, 1001, 32), which is
invalid.  The partition table's CHS geometry is
(495, 255, 63).  If you select Ignore, the file system's CHS geometry
will be left unchanged.  If you select Fix,
the file system's CHS geometry will be set to match the partition
table's CHS geometry.
Fix/Ignore/Cancel? C
Error: The file system's CHS geometry is (248, 1001, 32), which is
invalid.  The partition table's CHS geometry is
(495, 255, 63).  If you select Ignore, the file system's CHS geometry
will be left unchanged.  If you select Fix,
the file system's CHS geometry will be set to match the partition
table's CHS geometry.
Fix/Ignore/Cancel? I


You found a bug in GNU Parted.
This may have been fixed in the last version of GNU Parted that you can
find at:
        http://ftp.gnu.org/gnu/parted/
If this has not been fixed or if you don't know how to check, please
email:
        address@hidden
or (preferably) file a bug report at:
        http://parted.alioth.debian.org/bugs/
Your report should contain the version of this release (1.6.25.1) along
with the
following message and preferably additional information about your
setup.
Refer to the web site of parted
        http://www.gnu.org/software/parted/parted.html
for more informations of what could be useful for bug submitting!

There are no possible configurations for this FAT type.


-- 
joe <address@hidden>