Hi,
> In general all U3 USB flash devices should be supported.
> The software is currently tested with the following drives:
> . . . Sandisk Cruzer Micro U3 4Gb
Mine is exactly Sandisk Cruzer Micro U3 4Gb. I remove the U3 partition using the windows tools, but now I need to re-enable the CD partition, but failed to do so:
# u3-tool -p 1 /dev/sdb
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
u3_partition() failed: Failed rounding partition sectors: Device reported command failed: status 1
Here are more info about my U3:
# dmesg | tail
[297424.198345] usb-storage: device found at 7
[297424.198349] usb-storage: waiting for device to settle before scanning
[297429.197910] scsi 9:0:0:0: Direct-Access SanDisk U3 Cruzer Micro 4.04 PQ: 0 ANSI: 2
[297429.199505] sd 9:0:0:0: [sdb] 8027793 512-byte hardware sectors: (4.11 GB/3.82 GiB)
[297429.203161] sd 9:0:0:0: [sdb] Write Protect is off
[297429.203170] sd 9:0:0:0: [sdb] Mode Sense: 03 00 00 00
[297429.203176] sd 9:0:0:0: [sdb] Assuming drive cache: write through
[297429.205003] sd 9:0:0:0: [sdb] 8027793 512-byte hardware sectors: (4.11 GB/3.82 GiB)
[297429.205496] sd 9:0:0:0: [sdb] Write Protect is off
[297429.205502] sd 9:0:0:0: [sdb] Mode Sense: 03 00 00 00
[297429.205506] sd 9:0:0:0: [sdb] Assuming drive cache: write through
[297429.205515] sdb: sdb1 sdb2
[297429.208128] sd 9:0:0:0: [sdb] Attached SCSI removable disk
[297429.208416] sd 9:0:0:0: Attached scsi generic sg3 type 0
[297429.209154] usb-storage: device scan complete
# fdisk -l /dev/sdb
Disk /dev/sdb: 4110 MB, 4110230016 bytes
255 heads, 63 sectors/track, 499 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000e99c0
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 229 1839411 6 FAT16
/dev/sdb2 230 499 2168775 83 Linux
# u3-tool -i /dev/sdb
u3_partition_info() failed: Device reported command failed: status 1
# u3-tool -v -D /dev/sdb
u3_partition_info() failed: Device reported command failed: status 1
u3_data_partition_info() failed: Device reported command failed: status 1
Chip info:
- Manufacturer: SanDisk
- Revision: 4.04
Property page 0x03:
- Device size: 4110230016 byte(0x007a7e91)
- Device serial: 0000184CF471A6B0
- Full record length: 0x00000077
- Unknown1: 0x03
- Unknown2: 0x54060781
- Unknown3: 0x54060781
Property page 0x0C:
- Max. pass. try: 100
Anyway for me to make it works?
Thanks!
More on dmesg that I should have included:
[297424.066961] usb 1-8: new high speed USB device using ehci_hcd and address 7
[297424.193401] usb 1-8: configuration #1 chosen from 1 choice
[297424.197470] scsi9 : SCSI emulation for USB Mass Storage devices
[297424.198312] usb 1-8: New USB device found, idVendor=0781, idProduct=5406
[297424.198319] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[297424.198324] usb 1-8: Product: U3 Cruzer Micro
[297424.198329] usb 1-8: Manufacturer: SanDisk Corporation
[297424.198333] usb 1-8: SerialNumber: 0000184CF471A6B0
this is before "usb-storage: device found at 7"
thx
Forgot to mention my environment:
Using the latest u3-tool from Debian:
$ apt-cache policy u3-tool
u3-tool:
Installed: 0.3-1
Candidate: 0.3-1
Version table:
*** 0.3-1 0
360 http://cdn.debian.net testing/main Packages
50 http://cdn.debian.net unstable/main Packages
100 /var/lib/dpkg/status
BTW, found similar reports at
http://ubuntuforums.org/showthread.php?t=1478539
http://www.mail-archive.com/ubuntu-bugs@lists.ubuntu.com/msg2075851.html
thanks
Have you tried using device sgx instead of sbx?
I recently restored the launcher on my older 4GB SanDisk Cruzer Titanium U3 device using these commands.
Note that the partition size I used matches that of the partition on the 16GB device that I sourced the iso from, likely could have reduced that size as the ISO was only about 7MB.
Then just ejected and connect to windows and ran the launch pad from the u3 cd device and it worked.
My attempt to remove the write protected partitions on a SanDisk Extreme Go using
u3-tool 0.3-3 on Linux Mint 20
I got this error message:
Despite the error message the boot sector was gone afterwards and the write protection on the second partition was removed. So I could use gparted to wipe the remainings and create a new partition.