1,330
edits
Bootable Linux USB stick: Difference between revisions
Jump to navigation
Jump to search
→for techies: taking care of the stick
| Line 143: | Line 143: | ||
This is sensible to do after deleting large amounts of data from the USB stick, and before saving and compressing an image of it. It also seems to result in faster writes afterwards i.e. it may be a way to restore the write speed of the stick. | This is sensible to do after deleting large amounts of data from the USB stick, and before saving and compressing an image of it. It also seems to result in faster writes afterwards i.e. it may be a way to restore the write speed of the stick. | ||
<code>hdparm</code>'s (ENHANCED) SECURITY ERASE initializes the whole stick in 12.5 seconds - I checked the result. | <code>hdparm</code>'s (ENHANCED) SECURITY ERASE initializes the whole stick in 12.5 seconds - I checked the result. | ||
All other methods, like the <code>fstrim</code> command | All other methods, like the <code>fstrim</code> command and the <code>discard</code> mount option '''do not work for USB sticks''', presumably because the usb-storage kernel module does not pass the ATA trim command through the USB bridge and controller to the device. The same goes for [http://unix.stackexchange.com/questions/97143/utility-to-trim-unallocated-space-on-drive <code>blkdiscard</code>]. The <code>wiper.sh</code> script (which is part of <code>hdparm</code>) gives no error message, but does not reproducibly fill the empty space of the filesystem with zeroes (it sometimes does). | ||