u3-tool 0.3 fails on cruzer 2GB stick
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| u3-tool (Ubuntu) |
Undecided
|
Unassigned |
Bug Description
Binary package hint: u3-tool
I've had no luck with u3-tool on a Cruzer Micro 2GB. I've tried it on my 32-bit netbook and my 64-bit desktop. Both are running Karmic. I used the 0.3 version of u3-tool from the Lucid repositories. I want to reset security on the stick, but the attempt failed (on both computers) like this:
=======
istoner@
WARNING: This will delete all data on the data partition
Are you sure you want to continue? [yn] y
u3_enable_
=======
This is a totally standard u3 USB stick, and I've seen reports of u3-tool working on different sized sticks in the same line. Maybe this is a bug in the version packaged for Lucid? Here's the output of u3-tool's info dump:
=======
istoner@
Partition info:
- Partition count: 0x02
- Data partition size: 2047678976 byte(0x003d068d)
- Unknown1: 0x00000002
- CD size: 7340032 byte(0x00003800)
- Unknown2: 0x00000103
Data partition info:
- Data partition size: 0 byte(0x00000000)
- Secured zone size: 0 byte(0x00000000)
- Unlocked: 0x00000000
- Password try: 0x00000000
u3_chip_info() failed: Device reported command failed: status 1
u3_read_
u3_read_
Ian Stoner (ston0235) wrote : | #1 |
Kamilion (kamilion) wrote : | #2 |
Please do report it upstream as well, although I've not seen an update to u3-tool for a while.
However: I was successfully able to 'burn' a 1.7GB iso to my Contour EX 16GB earlier today using u3-tool 0.3-1 -- Here is my log.
Note: I was *NOT* able to get /dev/sg* or /dev/sr* to work -- I had to address the disk as /dev/sdf to get it to work.
kamilion@
Error opening device: Read-only file system
kamilion@
Total device size: 14.95 GB (16051601408 bytes)
CD size: 7.69 MB (8060928 bytes)
Data partition size: 14.94 GB (16043474944 bytes)
kamilion@
Partition info:
- Partition count: 0x02
- Data partition size: 14177271808 byte(0x01a68400)
- Unknown1: 0x00000002
- CD size: 1874329600 byte(0x0037dc00)
- Unknown2: 0x00000103
Data partition info:
- Data partition size: 14177271808 byte(0x01a68400)
- Secured zone size: 0 byte(0x00000000)
- Unlocked: 0x00000000
- Password try: 0x00000000
Chip info:
- Manufacturer: SanDisk
- Revision: 84210020
Property page 0x03:
- Device size: 16051601408 byte(0x01de6000)
- Device serial: 32482307E3811C16
- Full record length: 0x00000077
- Unknown1: 0x0b
- Unknown2: 0x540e0781
- Unknown3: 0x540e0781
Property page 0x0C:
- Max. pass. try: 5
kamilion@
CD image(1874288640 byte) is to big for current cd partition(8060928 byte), please repartition device.
kamilion@
WARNING: Loading a new cd image causes the whole device to be whiped. This INCLUDES
the data partition.
I repeat: ANY EXCISTING DATA WILL BE LOST!
Are you sure you want to continue? [yn] y
kamilion@
|******
OK
So that all worked just fine for me.
I did some testing on the /dev/sg? stuff a minute ago just to see if it would work, here's the results:
kamilion@
kamilion@
sg0 sg1 sg2 sg3 sg4 sg5 sg6 sg7 sg8
kamilion@
u3_partition_info() failed: Device reported command failed: status 1
u3_data_
u3_chip_info() failed: Device reported command failed: status 1
u3_read_
u3_read_
kamilion@
Partition info:
- Partition count: 0x00
- Data partition size: 837131066880 byte(0x6174732f)
- Unknown1: 0x63000000
- CD size: 0 byte(0x00000000)
- Unknown2: 0x00000000
Data partition info:
- Data partition size: 0 byte(0x00000000)
- Secured zone size: 1000297383424 byte(0x74732f63)
- Unlocked: 0x03007461
- Password try: 0x001700b1
Chip info:
- Manufacturer: at
- Revision:
Length of property 0x03 is not the expected length. (len=12131)
Length of property 0x0C is not the expected length. (len=12131)
kamilion@
MillenniumBug (millenniumbug) wrote : | #3 |
Having the same error message in Ubuntu 10.10 using the same kind of USB stick.
Is there any development going on in u3-tool?
Changed in u3-tool (Ubuntu): | |
status: | New → Confirmed |
MillenniumBug (millenniumbug) wrote : | #4 |
Well, error message or not:
It turned out that the USB stick was wiped as it should, and now it can be used for live booting.
Daniel J Blueman (danielblueman) wrote : | #5 |
I've committed fixes to u3-tool which should fix this.
I'll contact the project admin to cut a new release, but for now, use:
$ svn co https:/
Changed in u3-tool (Ubuntu): | |
status: | Confirmed → Fix Committed |
Tony Smith (v1i9v6a6) wrote : | #6 |
Hi,
I am having the same or similar problems with Ubuntu 10.04 LTS (32bit). I have a generiac U3 flash drive of unkown make/chipset.
Here are the system message when I plug it in and some u3-tool output
Jun 11 17:39:19 ZZZ kernel: [ 75.976025] usb 2-5: new high speed USB device using ehci_hcd and address 2
Jun 11 17:39:19 ZZZ kernel: [ 76.109747] usb 2-5: configuration #1 chosen from 1 choice
Jun 11 17:39:19 ZZZ kernel: [ 76.139346] Initializing USB Mass Storage driver...
Jun 11 17:39:19 ZZZ kernel: [ 76.139513] scsi8 : SCSI emulation for USB Mass Storage devices
Jun 11 17:39:19 ZZZ kernel: [ 76.139634] usbcore: registered new interface driver usb-storage
Jun 11 17:39:19 ZZZ kernel: [ 76.139637] USB Mass Storage support registered.
Jun 11 17:39:24 ZZZ kernel: [ 81.137439] scsi 8:0:0:0: Direct-Access CBM Flash Disk 5.00 PQ: 0 ANSI: 2
Jun 11 17:39:24 ZZZ kernel: [ 81.137801] scsi 8:0:0:1: Direct-Access CBM Flash Disk 5.00 PQ: 0 ANSI: 2
Jun 11 17:39:24 ZZZ kernel: [ 81.138214] sd 8:0:0:0: Attached scsi generic sg5 type 0
Jun 11 17:39:24 ZZZ kernel: [ 81.138328] sd 8:0:0:1: Attached scsi generic sg6 type 0
Jun 11 17:39:24 ZZZ kernel: [ 81.139795] sd 8:0:0:0: [sdd] 123800 512-byte logical blocks: (63.3 MB/60.4 MiB)
Jun 11 17:39:24 ZZZ kernel: [ 81.141872] sd 8:0:0:1: [sde] 907880 512-byte logical blocks: (464 MB/443 MiB)
Jun 11 17:39:24 ZZZ kernel: [ 81.143129] sd 8:0:0:0: [sdd] Write Protect is on
Jun 11 17:39:24 ZZZ kernel: [ 81.143822] sd 8:0:0:1: [sde] Write Protect is off
Jun 11 17:39:24 ZZZ kernel: [ 81.146671] sdd:
Jun 11 17:39:24 ZZZ kernel: [ 81.147168] sde: sdd1
Jun 11 17:39:24 ZZZ kernel: [ 81.148668] sde1
Jun 11 17:39:24 ZZZ kernel: [ 81.154431] sd 8:0:0:0: [sdd] Attached SCSI removable disk
Jun 11 17:39:24 ZZZ kernel: [ 81.154917] sd 8:0:0:1: [sde] Attached SCSI removable disk
Jun 11 17:39:25 ZZZ kernel: [ 81.669336] EXT4-fs (sde1): mounted filesystem with ordered data mode
username@ZZZ:~$ u3-tool -V
u3-tool 0.3
subsystem: sg
Copyright (C) 2009
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
username@ZZZ:~$ mount
...
/dev/sde1 on /media/New Volume type ext4 (rw,nosuid,
/dev/sdd1 on /media/DISK_IMG type vfat (ro,nosuid,
username@ZZZ:~$ sudo u3-tool -i /dev/sdd
Error opening device: Read-only file system
username@ZZZ:~$ sudo u3-tool -i /dev/sde
u3_partition_info() failed: Device reported command failed: status 1
username@ZZZ:~$ sudo u3-tool -D /dev/sdd
Error opening device: Read-only file system
username@ZZZ:~$ sudo u3-tool -D /dev/sde
u3_partition_info() failed: Device reported command failed: status 1
u3_data_
u3_chip_info() failed: Device reported command failed: status 1
u3_read_
u3_read_
username@ZZZ:~$
Any sugge...
Tony Smith (v1i9v6a6) wrote : | #7 |
ps it is the latest svn, downloaded 1-june-2012
Tony Smith (v1i9v6a6) wrote : | #8 |
I pulled my USB stick apart and got the chipset numbers CBM2090. Then I was able to Google a piece of windows software to manage the drive, doesnt appear to have given me a virus :-). I was able to change the drive sizes, format and write to both partions. U3-tool still gives me this error with the new layout:-
username@ZZZ:~$ sudo u3-tool -D /dev/sde
[sudo] password for username:
u3_partition_info() failed: Device reported command failed: status 1
u3_data_
u3_chip_info() failed: Device reported command failed: status 1
u3_read_
u3_read_
Neither Kingston or Scandisk software work with my USB stick since they only work with there own devices.
Tony.
Jason Heeris (detly) wrote : | #9 |
@Daniel Blueman - I tried to build from that location, but the "configure" script is missing. Are the build instructions in "INSTALL" out of date?
I just compiled the source release from http:// sourceforge. net/projects/ u3-tool/ files/ and it fails the same way. So it's a problem with the program, not the packaging.
Does this mean I should have reported the bug to u3-tool directly, instead of in Ubuntu? (Sorry for spamming launchpad, if so!)