Re: what to do with USB stick that gives badblocks errors
On 11/24/21 11:52, Kenneth Parker wrote: Try Steve Gibson's initdisk. It claims: "Experience has shown that USB thumb drives believed to be dead may be brought back to life with InitDisk." https://www.grc.com/initdisk.htm Steve has done a lot of testing on USB flash drives and has discovered ways of getting down to the raw drive past the controller. Check out his other freeware especially shields up! -- *...Bob*
Re: what to do with USB stick that gives badblocks errors
On 24/11/2021 16:10, Curt wrote: On 2021-11-24, piorunz wrote: On 24/11/2021 10:04, Sven Hartge wrote: Should I throw it away? Yes. Agree. I had some bad USBs, did a lot of trickery on them but never were able to revive them and put them back to any reasonable use. Bin. I thought I had a bad one once but it was a flaky port. Good tip, worth checking also. Check on entirely separate machine using tool like Capacity Tester (that's a FOSS rewrite of very similar Windows tool): https://github.com/c0xc/CapacityTester Test stick, on two separate computers, if it fails on both, bin. -- With kindest regards, Piotr. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄
Re: what to do with USB stick that gives badblocks errors
On Tue, Nov 23, 2021, 7:56 AM deloptes wrote: > I'm sure there are many ideas around, but I want to hear your opinion > > so there is one USB stick that I noticed started mocking about errors when > booting off. > It's giving you more feedback than one of mine did. It just timed out on all I/O operations, during an attempted Mint 20 Install (making me think Mint was more Defective than it is. [Disclaimer: It does what it needs to do, and is good for a beginner]). Finally, I smelled a rat, aborted the Mint install and tried to read it on a different machine. I ran badblocks (without options) and then with -s -n and this produced a > slightly different output. > Is the output resulting from the options or is something really wrong with > the USB > They go bad often. I won't even purchase one from FedEx Office anymore, after so many of theirs failed. > > Should I throw it away? > I agree with the other response: Yes! > > If no should I try reformat it > Try that, only for the humor of it. (I would be surprised if it worked after that). > > thanks & regards > You too. > Kenneth Parker >
Re: what to do with USB stick that gives badblocks errors
On 2021-11-24, piorunz wrote: > On 24/11/2021 10:04, Sven Hartge wrote: >>> Should I throw it away? >> Yes. > > Agree. I had some bad USBs, did a lot of trickery on them but never were > able to revive them and put them back to any reasonable use. Bin. > I thought I had a bad one once but it was a flaky port.
Re: what to do with USB stick that gives badblocks errors
On 24/11/2021 10:04, Sven Hartge wrote: Should I throw it away? Yes. Agree. I had some bad USBs, did a lot of trickery on them but never were able to revive them and put them back to any reasonable use. Bin. -- With kindest regards, Piotr. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄
Re: what to do with USB stick that gives badblocks errors
deloptes wrote: > I'm sure there are many ideas around, but I want to hear your opinion > so there is one USB stick that I noticed started mocking about errors when > booting off. > I ran badblocks (without options) and then with -s -n and this produced a > slightly different output. > Is the output resulting from the options or is something really wrong with > the USB > Should I throw it away? Yes. When even the lowly and beyond-cheap flash controller of a USB stick throws external errors, then it is time to just throw it away. > If no should I try reformat it No. S! -- Sigmentation fault. Core dumped.
what to do with USB stick that gives badblocks errors
I'm sure there are many ideas around, but I want to hear your opinion so there is one USB stick that I noticed started mocking about errors when booting off. I ran badblocks (without options) and then with -s -n and this produced a slightly different output. Is the output resulting from the options or is something really wrong with the USB Should I throw it away? If no should I try reformat it thanks & regards -- FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0 usb32_SanDisk_badblocks.diff.gz Description: application/gzip
