AltraMayor
commented
5 years ago Hi @ElDavoo,
The worst thing that f3brew can do to a working drive is to erase the drive's partition table and the stored data since f3brew only communicates to the drive through the block device interface.
The drive was fake and/or about to fail. Given that the drive has changed its idVendor, idProduct, Product, Manufacturer, and SerialNumber, it is dead and/or the controller went into a programming mode. This means that the drive is trash at this point.
As a last resort, you can try f3probe on this drive. But hold very low expectations.
Hi, Not exactly an issue with the software but this was worth to be written somewhere. So I had this 4GB Verbatim usb stick that was half-empty, I filled it with music, zeroing the free space available. [293683.993509] usb 1-2.1: New USB device found, idVendor=18a5, idProduct=0302, bcdDevice= 1.00 [293683.993522] usb 1-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [293683.993532] usb 1-2.1: Product: STORE N GO
[293683.993540] usb 1-2.1: Manufacturer: Verbatim
[293683.993547] usb 1-2.1: SerialNumber: 3500000000006765 [293683.995748] usb-storage 1-2.1:1.0: USB Mass Storage device detected [293683.997870] scsi host3: usb-storage 1-2.1:1.0 [293685.046213] scsi 3:0:0:0: Direct-Access Verbatim STORE N GO 1.0 PQ: 0 ANSI: 2 [293685.046668] sd 3:0:0:0: Attached scsi generic sg1 type 0 [293685.048140] sd 3:0:0:0: [sdc] 7829504 512-byte logical blocks: (4.01 GB/3.73 GiB)
As soon as I did that, errors in dmesg started to appear and the kernel set the filesystem (fat32) to RO. When I unplugged and replugged, I got a broken partition table and not a trace of my filesystem. So I suspected that was a fake drive and started up f3brew as I couldn't even create a file system, because it was damaged and unmountable as soon as it was written to drive. So, F3 brew 7.2 Physical block size: 2^9 Bytes
Writing blocks from 0x0 to 0x7777ff...ioio Done
Please unplug and plug back the USB drive. Waiting...
But when I reinserted it: [294356.840953] usb 1-1: new high-speed USB device number 115 using xhci_hcd [294356.969689] usb 1-1: New USB device found, idVendor=1850, idProduct=1550, bcdDevice= 1.00 [294356.969695] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [294356.969699] usb 1-1: Product: 屐嵐幐彐恐慐扐捐摐敐晐材桐楐橐歐汐浐湐潐灐煐牐獐瑐畐癐睐硐祐 [294356.969701] usb 1-1: Manufacturer: 㹐㽐䁐䅐䉐䍐䑐䕐䙐䝐䡐䥐䩐䭐䱐䵐乐佐偐児剐卐呐啐噐坐塐奐婐子 [294356.969703] usb 1-1: SerialNumber: P6P7P8P9P:P;P<P= [294356.971040] usb-storage 1-1:1.0: USB Mass Storage device detected [294356.971778] scsi host2: usb-storage 1-1:1.0 [294358.006236] scsi 2:0:0:0: Bridge controller P(P)PP+ P,P-P.P/P0P1P2P3 P4P5 PQ: 2 ANSI: 0 [294358.007325] scsi 2:0:0:0: Attached scsi generic sg1 type 16 [294358.009622] scsi 2:0:0:1: Bridge controller P(P)PP+ P,P-P.P/P0P1P2P3 P4P5 PQ: 2 ANSI: 0 [294358.010381] scsi 2:0:0:1: Attached scsi generic sg2 type 16 [294358.012174] scsi 2:0:0:2: Bridge controller P(P)P*P+ P,P-P.P/P0P1P2P3 P4P5 PQ: 2 ANSI: 0 [294358.012611] scsi 2:0:0:2: Attached scsi generic sg3 type 16 [294365.272166] usb 1-1: USB disconnect, device number 115
So wtf. f3brew broke my usb drive? Or was it already broken?