Could Live-USB-Maker check the flashdrive after writing?

[Moderator BobC]

Helpful

Up

0

::

Thanks for everyone’s input and help.

Etcher didn’t notice the USB data was invalid until after writing the USB. I didn’t try booting to Windows and running Rufus.

My f3 tests completed overnight and it found about 14 mb of data out of the 3.68 gb were wrong as compared to the test data it wrote, which would be major if it was an area a program was trying to use. Previously this flashdrive had not had any apparent problems, but keep in mind that I was burning an iso snapshot as a main system backup to it with live-usb-maker and hadn’t been testing trying to boot or install from it afterwards. Maybe I should have been doing that.

I will continue trying to learn… I still want to know if what I created is good or not.

My next thought is the question of: If the flashdrive is stable where that 14 mb is and stays the only bad area, are there ways I can use the flashdrive for bootable iso’s or for storing data safely, or should I just hrow it away?

[Moderator Brian Masinick]

Helpful

Up

0

::

https://linoxide.com/linux-how-to/how-to-fix-repair-bad-blocks-in-linux/
https://www.maketecheasier.com/repair-corrupted-usb-drive-linux/

• This reply was modified 2 years, 5 months ago by Brian Masinick.

--
Brian Masinick

[Moderator BobC]

Helpful

Up

0

::

They only suggested fsck. I will have to read up and test. I wish I had a very small partially bad flashdrive, LOL. I don’t know if f3read marked them bad or not.

[Member ModdIt]

Helpful

Up

0

::

I played last evening, FSCK seems to just talk to the the controller, on known buggy drives it finished in an instant.
Might work on others though.

F3 might fix some sticks with corrupt data, not defective memory as it does a complete write read cycle.
A secure erase can have similar effect. If after that F3 still shows errors on the stick I would personaly bin it.
Too much chance of failure. If it worked for a while I would probably end up with something important on it and lose.

USB sticks memory cards SSD mostly just go dead unlike HDD where changing the controller may allow a relatively
inexpensive/easy readout. On sticks if the USB connections are torn off the board due dropping, bending while
plugged in and if data is important, soldering on a new plug or wiring on is worth a try.
If data is critical a specialist job.

All sticks and cards have an internal controller and according to some literature from manufacturerers may/should
have a reserve for replacing defective memory areas. Once thre is no more to replace or a set limit is reached I
assume no more reallocation is done

[Author]

Posts