UPS fire and subsequent collateral.

So recently I lost my NFS datastore yet again (2nd time.) This last time was due to a UPS catching fire as I was about to leave for a bike ride. Thankfully I hung around the house a bit longer than planned and was in ear-shot when the UPS board caught fire. Needless to say I panicked and started ripping power cords from the UPS without a proper shutdown on anything. My concern at the time was getting the UPS outside the house and onto concrete before something drastic happened such as a battery explosion or fire spreading to the wood floors.

Ripping the power cord out caused some sort of software issue that I haven’t been able to recover from. ZFS scrubbing yields no errors but mounting the encrypted volume causes an instant kernel panic followed by a dump and reboot. This issue has only exhibited on the NFS datastore and not the primary datastore. So I imagine it has to do with an improper disconnect of the NFS share.

This being the second time I’ve lost all my play and study virtual machines, I am a bit pissed. I will say this is my fault as I haven’t been keeping backups of the VMs in any capacity. I’ve decided to have another go at iSCSI even though there are several aspects of it I don’t particularly care for. Such as iSCSI needing to claim a size for the zvol, difficult future expansion, and the exclusive access to just one machine at a time.

This entry was posted in News and tagged , , , . Bookmark the permalink.

4 Responses to UPS fire and subsequent collateral.

  1. Nics Nguyen says:

    Jesus Christ buddy, what did you do to cause your UPS to catch on fire? lol

  2. EpiJunkie says:

    Umm, I think it’s the dirty power going into my house. I have a line conditioner that I hear activate on an hourly basis when I’m home. I think this took it’s toll on the UPS which had a disagreement with the line conditioner (probably due to being out of spec because of the UPS’ age.) about the proper input voltage. It’s really too bad but it happens; I’m just glad I didn’t loose everything.

  3. Nics Nguyen says:

    Well I’m glad you didn’t lose everything and that there wasn’t any collateral damage.

  4. Pingback: Switching to Fiber Channel for SAN access. Part 1 | EpiJunkie

Leave a Reply

Your email address will not be published. Required fields are marked *