Dear lord I can't win lately... NAS went down and I basically had to kick it to get it back up, likely related to a dead disk...
Here's the tally of my environment:
* 2 Proxmox servers
- 1 server failed, I need to send it in for a refund under the protection plan
- I bought a server to replace it already... that server came with a busted ram slot meaning it's already on degraded performance (need to refund it, but want to get a replacement before I send it off...)
- 1 old desktop running as a NAS
- 1 hard drive is throwing non-critical block errors, threatening to fail... I got the warranty exchange set up already but...
- 1 hard drive failed entirely after setting up that warranty exchange and now I don't have the parity to spare a drive, so I need to spare drives before I can start exchanging drives (those drives should arrive on Saturday)
And in all of this... spending way too much money I really shouldn't be spending at all...
And before someone thinks I'm throwing around a few K here... everything I'm getting is renewed, which is probably part of the problem but I sure as hell can't afford new. (Proxmox servers are around $100 each, drives around $45 each)
Shannon Prickett reshared this.
Reduced Performance / Reliability
One of the servers went down from hardware failure, thankfully since I run this across multiple boxes with failover it means the site is (obviously) still up.
It might occasionally get a little spotty on connection and especially on performance until that server gets replaced as it means the remaining server is a tad bit overloaded.
It'll probably be a few weeks unfortunately as I don't have the spare funds to pre-purchase a replacement (the protection plan I purchased will cover it, but I've got to mail off the unit, wait for the money, then wait for financial stresses to pass enough that I can order the replacement... then a good week or two delivery time after that)
Confused likes this.
Short Planned Maintenance Tonight
My apologies if this is inconvenient, I opted to do it on shorter notice without a set hour because (a) there's not a lot of activity on the server and (b) I'm really impatient.
I'm doing a hardware upgrade that requires rebooting the network storage backend which will bring down everything for a short time. It should take well under 30 minutes to do the hardware swap and most of the downtime is just going to be the database starting back up (which often takes in the range of another 30 minutes).
As part of this I'll also be deploying some software updates that require a reboot to take effect.
Shiri Bailem
in reply to Shiri Bailem • •Oh, and the NAS going down is critical because those $100 boxes (a) don't have enough disk space for everything and (b) it's how I'm maintaining the ability to high(-ish) availability transfer between the two nodes (this saved me when the one proxmox system died).
Those are tiny form factor systems, but they have room for a second hard drive. I need to get a couple of hard drives to drop into them so they have better local storage, afterwards I can set them up as ZFS and use proxmox's features to sync the drives between the two nodes... that way they're not relying on the nas for anything that's not just large.