=== START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===
Sending command: "Execute SMART Extended self-test routine immediately in off-line mode".
Drive command "Execute SMART Extended self-test routine immediately in off-line mode" successful.
Testing has begun.
Please wait 109 minutes for test to complete.
Test will complete after Sun Dec 27 20:06:19 2020 PST
Use smartctl -X to abort test.
Never mind! It knew I'd be impatient and has started in the background
I guess I only have two hours to wait
So it seems that Reallocated_Sector_Ct and Current_Pending_Sector are the important ones and since Hal's aren't nonzero I'm gonna go ahead and say that Hal shouldn't be used
For the server's backup disk it may have read and seek errors but it has neither of those two so I'm gonna say it's fine for now (and because I'm too lazy to replace it)
Meanwhile the long test for the server's main disk failed so I'm gonna go ahead and say that definitely needs to be replaced lol
I'm gonna give the other two drives names so I remember what they are lol
The one that holds my photos backups is Orion and the one that holds my server backups is Monty
I will not be using Hal
I think I'll replace my current server disk with Gerty, keep using Monty for my server backups, and keep using Gerty for my photo backups
Eventually I'm going to move my photo backups to my server (probably this week, since I'm doing all of this anyway), which will free up Orion
tbh I'm not sure if Gerty and Monty are the best choices for the server vs Orion
so this is Gerty: Western Digital Caviar Blue Serial ATA, WDC WD1600AAJS-00PSA0
and this is Orion: Western Digital Caviar Blue (SATA), WDC WD6400AAKS-75A7B0
and this is Monty: Seagate Barracuda 7200.7 and 7200.7 Plus, ST3160827AS
the failing server disk is: Seagate Barracuda 7200.14 (AF), ST1000DM003-1CH16
I'm not really sure if Seagate or Western Digital have reputations
h a r d d r i v e
I found some specs pages ooo
Gerty: https://www.cnet.com/products/wd-blue-wd1600aajs-hard-drive-160-gb-sata-300-series/
Orion: https://www.cnet.com/products/wd-blue-wd6400aaks-hard-drive-640-gb-sata-300-series/
Monty: https://www.cnet.com/products/seagate-barracuda-7200-7/
server: https://www.cnet.com/products/seagate-desktop-hdd-st1000dm003-hard-drive-1-tb-sata-6gb-s-st1000dm00325blk/
Looks like the one currently in the server has the best specs (unfortunately), followed by Orion, then Gerty, then Monty
h a r d d r i v e
Victor is a Seagate Barracuda 7200.12, ST3320418AS: https://www.cnet.com/products/seagate-barracuda-7200-12-320gb-sata-300/
I'm still unsure if I want to use Victor or Orion (Gerty and Monty are both 160 GB and those sizes maybe aren't very future-proof even if my current server doesn't use all that much)
h a r d d r i v e
also a linky linky for what those errors really mean: http://www.users.on.net/~fzabkar/HDD/Seagate_SER_RRER_HEC.html
h a r d d r i v e
Ok here's the plan:
* I write a blog post about what I've discovered so far, including various stats about my hard drives
* I then stick Orion in my server as the main disk (since it's bigger than Victor) with Victor as the backup (since it's bigger than Gerty or Monty)
* I take the failing drive out (Sasha) and put it in my current desktop, and install a GUI for the Ubuntu Server that's currently on there, because I want to see how long I can keep using it before it really really fails (I probably won't need to use that desktop for any Coq things since I'll have my laptop)
* I move my photos backup to the server so that I can access them remotely, and I'll back up my photos by plugging my phone physically into the server
* I'll then have three copies of all my data (and a partial copy of my photos, if you count my old SD card)
* Gerty and Monty will be retired for being old and small (Hal is still dead)
I think that's it
h a r d d r i v e
https://ionathan.ch/thulium/2020/12/28/thulium-failure.html
I couldn't resist because the inspiration struck lol, here's a draft of the post
Something I forgot to mention both here and on the post is that I'm going to run a long test with smartctl on Orion (and maybe Victor) first just to take make sure those disks are healthy so I can push further disk failures as far into the future as possible
h a r d d r i v e
@nonphatic oh, that's what macOS Disk Utility calls it