So it’s official. I killed SSD w/ZFS FileSystem choice.

So today I had to power down the server to perform some maintenance.  It was also the day that my local electric utility decided to replace a pole in my neighborhood.  They were kind enough to warn us that power would be down, so I took the opportunity to power down the server in the morning before they began their work.  I went to work, and when I got home, I did some moving around of equipment around the Server that I had been wanting to do for a while.  Unfortunately, when I powered the server back on, it started-up just fine but threw the dreaded “no bootdrive detected”.  

SSD’s by their very nature are perfect for most every situation, EXCEPT WRITE INTENSIVE applications.  Turns out that I was NOT paying attention when I originally installed Proxmox on the SSD with ZFS format.  Or more specifically, I wasn’t aware of the bad choice I was making. I should have gone with EXT4 as the type of FileSystem instead of ZFS.  Bad sysadmin!

Errors are really starting to stack-up

So those errors are really starting to stack-up on that SSD. 

Cracked open the chassis for like the third time this week, not really expecting to find a physical problem, most because I don’t think it’s a hardware problem.  I suspect that it’s more likely a configuration choice / issue on my part.   I bought a replacement drive just in case this one goes down hard.  It’s now up to:

Device: /dev/sda [SAT], ATA error count increased from 175188 to 175201