Well, chat, I may not be cooked (thanks to backups), but it looks like my home computer's hard drive is again.

(BTW, zpool status -v zroot hangs pool-related stuff so bad that it prevents an export at shutdown, thus preventing a clean shutdown or reboot.)

Replacing the HDD in an AIO PC: 45 minutes.

Installing a base system to start the "restore" part of the backup/restore regimen: 30 minutes.

Restoring backed up filesystems other than /usr/home/ from a USB3 backup disk: 1 hour.

Restoring the backed up /usr/home/: 6+ hours.

... Okay, I may have a lot of stuff.

My /usr/home filesystem restored itself to the right name in my pool, but somehow a new and empty /home/arielmt filesystem got added and mounted, so when I went to check for success, I wound up in an empty twm desktop instead.

Destroying the rogue filesystem took only a few minutes and resulted in complete restoration of my system, but that was an annoying delay. I have to edit my restore procedure again.

Follow

Back up your files to external media, & test them for correctness and completeness. Backups done wrong are worse than useless, but backups done right turn a terrifying personal disaster into a frustrating personal annoyance.

Sign in to participate in the conversation
Computer Fairies

Computer Fairies is a Mastodon instance that aims to be as queer, friendly and furry as possible. We welcome all kinds of computer fairies!