Removed by mod

Is this what whipping the llamas ass looks like?

That’s great, glad to hear it. Start doing backups too!

Hyper-v is bundled with windows now and is just as easy to use as virtualbox (slightly easier for windows guests since the drivers are bundled in the os)

If the disk is failing anything you do that reads or writes it could cause data loss. Even having it plugged in and powered potentially could. It depends on what component of it is failing.

That being said, fsck is pretty safe. It’s the equivalent of chkdsk in windows, it looks specifically at the filesystem for things that may have gotten screwy.

ddrescue/gddrescue is your best bet for recovery. It can detect bad blocks and skip them, and it has some p robust resuming capabilities if your disk locks up while.its running. I usually use it to clone entire physical disks to another disk or an image file that can be mounted. I don’t know if it can be used to grab specific files, I’ve never tried.

If it was me, I’d take the disk out and let it cool to room temperature. Then I’d ddrescue the whole thing, with resume turned on, to an image file. Then I’d run fsck. If fsck finds and recovers filesystem issues, I’d put it back in the pi, continue using it, and start doing regular backups of important files via a cron task.

If you think it’s the filesystem try running fsck. It sounds like a failing storage device to me but there’s not nearly enough information to say for sure

Literally just an opinion and people are down voting you for it

That rarest of all creatures, someone admitting they were wrong on the internet

I’m waiting for the-crotchOS, a distro that caters to me specifically and no one else

You need to set up dkim to prevent spoofing. Each message sent has a digital signature that matches one on a DNS record for your domain. You can also set an SPF record, which will tell the recipient what up addresses are authorized to send mail on behalf of your domain.

The recipent must have policies in place that reject mail which fails dkim/spf

Set up dkim/SPF properly, make sure the ip you plan to use is clean before you start, sign up for MXtoolbox blacklist alerts and if you get on a blacklist (doesn’t happen often if you do a bare minimum of proactive security), you request removal. It’s really not hard.

DAE micro$haft winBLOW$ suxx???

but my homelab is held together with hope and scripts to recover when it goes down

That’s every IT guy. When I’m done with work, I’m sick of doing things right. If it works it’s fine. Where’s my duct tape

Most users don’t want to immediately troubleshoot every error, they want to get back to work. The ones that do know how to find it in event viewer or the crash dumps or disable auto reboot on bsod.

You have to disable auto reboot on bsod

Updates are paused until 2038/January/19

And the botnets rejoiced for their bounty was plentiful

it is unlikely that Linux Desktop adoption will ever proliferate to the kinds of mainstream adoption that its accolades desire.

And if it does, the acolytes will hate it and start pushing for BSD adoption, because there’s a huge streak of hipsterism in the Linux community

That’s been true every year since I stated paying attention. In 1997.

I use smarttube on my shield

My bad, didn’t know that