On Tue, Jun 16, 2020, at 2:17 AM, Dale wrote: > David Haller wrote: > > I mentioned once long ago that I keep a list of frequently used > commands. I do that because, well, my memory at times isn't that great. > Here is some commands I ran up on based on posts here and what google > turned up when searching for things related on those posts. I wanted to > share just in case it may help someone else. ;-) dd commands first. > > > root@fireball / # cat /root/freq-commands | grep dd > dd commands > dd if=/dev/zero of=/dev/sd bs=4k conv=notrunc > dd if=/dev/zero of=/dev/sd bs=4k conv=notrunc oflag=direct #disables cache > dd if=/dev/zero of=/dev/sd bs=1M conv=notrunc > dd if=<(yes $'\01' | tr -d "\n") of= > dd if=<(yes $'\377' | tr -d "\n") of= > dd if=<(yes $'\xFF' | tr -d "\n") of= > root@fireball / # > > > The target device or file needs to be added to the end of course on > the last three. I tend to leave out some of the target to make sure I > don't copy and paste something that ends badly. dd can end badly if > targeting the wrong device. > > > root@fireball / # cat /root/freq-commands | grep smartctl > smartctl -t long /dev/sd > smartctl -t full ##needs research > smartctl -c -t short -d sat /dev/sd ##needs research > smartctl -t conveyance -d sat /dev/sd ##needs research > smartctl -l selftest -d sat /dev/sd ##needs research > smartctl -t <short|long|conveyance|select> /dev/sd ##needs research > smartctl -c /dev/sd ##displays test times in minutes > smartctl -l selftest /dev/sd > root@fireball / # >
Thanks for these. I do have a general question: has SMART actually shown anyone predictive capability? In my use and in the use of 4-5 people I know it only makes you aware of errors after the drive is failing but still online. I suppose there might be some utility if you're using an error correcting FS, but for desktop use that was and still is somewhat abnormal.
