Bootable Linux USB stick: Difference between revisions

Line 142: Line 142:
The workaround I found is to use the <code>wiper.sh</code> script which is part of the <code>hdparm</code> package - this uses <code>hdparm</code> directly. For me, this seems to work, as verified with the [https://sites.google.com/site/lightrush/random-1/checkiftrimonext4isenabledandworking test_trim.sh] script. Use it on your own risk!
The workaround I found is to use the <code>wiper.sh</code> script which is part of the <code>hdparm</code> package - this uses <code>hdparm</code> directly. For me, this seems to work, as verified with the [https://sites.google.com/site/lightrush/random-1/checkiftrimonext4isenabledandworking test_trim.sh] script. Use it on your own risk!


For initializing the whole stick or a specific partition, [http://unix.stackexchange.com/questions/97143/utility-to-trim-unallocated-space-on-drive <code>blkdiscard</code>] may work - I have not yet checked it. I do believe that <code>hdparm</code>'s (ENHANCED) SECURITY ERASE should initialize the whole stick - again, I have not yet tried it.
For initializing the whole stick or a specific partition, in principle [http://unix.stackexchange.com/questions/97143/utility-to-trim-unallocated-space-on-drive <code>blkdiscard</code>] may work - but it gave me an error message (seems also to be using usb-storage).  
 
However, <code>hdparm</code>'s (ENHANCED) SECURITY ERASE initializes the whole stick - I checked the result.
1,330

edits