At first I thought this was related to Windows losing drives on wake. It started happening around the same time, it also involved waking up from sleep, and the CD/DVD drive was disappearing in Windows along with the vanishing hard drive.
But while moving the cables fixed that problem, it didn’t fix this one.
It was only mildly annoying, especially compared to regularly losing access to a large chunk of local storage, so I figured I’d come back to it later.
Other people are seeing this too and it’s a recent bug in the Linux kernel. At least with Fedora’s rapid kernel updates I probably won’t have to wait too long between when the patch lands and when it hits my desktop. It’s been years since I compiled my own kernel, and I don’t feel like starting that up again now!
My main desktop PC dual-boots Windows 10 and Fedora Linux. I have an SSD drive for each OS, and recently added an HDD for larger shared storage. It’s worked out pretty well except for a recurring problem: Sometimes the shared drive just disappears from Windows after I wake it up from sleep mode.
I don’t mean Windows just unmounts the filesystem. I mean Windows stops seeing the hardware at all.
When that happens, it sometimes reconnects after a few minutes…and sometimes doesn’t. Which means it’s not only invisible in Windows, it doesn’t get cleaned up properly on reboot, so Linux will only access it read-only the next time I fire that up, until I get back into Windows and shut it down cleanly.
Time to get to the bottom of it. Most of what I found online boiled down to:
- Update the SATA controller driver.
- Update the motherboard firmware.
- Make sure the cable connection is solid.
- Move the cable to another connector.
- Replace the cable.
- Get a better drive, [brand the OP mentioned] is terrible.
I finally got around to trying out No Man’s Sky a few weeks ago. I started on a super-hot planet, where you need to find shelter and/or resources to recharge your suit’s hazard protection system to keep cool. Got killed a few times trying to figure out what I was doing. And after about 20 minutes, my computer spontaneously shut itself down.
I waited a few minutes to let it cool down, then tried again. Managed to figure out a bit more of what I needed to do in the game, and then the same thing happened.
On Monday, the home laptop mysteriously started lagging on heavily-modded Minecraft worlds that it had been just fine with the day before. Katie tried all kinds of troubleshooting over the next few days: using different launchers, trying local and server-based games, disabling mods, reinstalling Sophos, rebooting the system repeatedly. Nothing helped.
Until she checked the system update panel. Sure, it had a notification dot, but it always has one because it wants us to update to Big Sur, and we’re not quite ready to upgrade the system from Catalina. So it wasn’t obvious that it hadn’t actually installed Monday’s macOS update despite multiple reboots and a checkbox to automatically install updates.
Not that you’d expect a missing update to be the cause of the problem, since the lag only just started happening. But still, worth a shot. Especially since it started around the time the update was released.
(Incidentally, 2.3 GB? It’s only been a few weeks since the previous update. Did Apple just give up on deltas a while back and start shipping the entire OS every time there’s a bug fix?)
She had to manually tell it to install, and then force-shutdown the machine, because it wouldn’t restart on its own. Then the update installed.
And the Minecraft lag mysteriously disappeared.
Which means one of two things happened. Either:
- Just knowing that the update existed caused something to chew up or block resources.
- The OS silently started to install the update and got stuck, leaving the system in a broken state without telling anyone.
Neither of those is what I’d call encouraging.
Huh. Verizon has sold what remains of Yahoo! and AOL.
For half of what they paid for them. 🤦♂️
To a private equity firm. 😬
Apparently the division formerly known as Oath and later as Verizon Media Group will be called Yahoo going forward, which is probably a good move.
I’ve got to say, though: Flickr and Tumblr really lucked out that Verizon sold them to companies that actually had something to do with their core service. Flickr went to SmugMug, a photo-sharing company, and Tumblr went to Automattic, a blogging company.
I’d like to think someone at Verizon put in the effort to find a good fit for each. It’s probably more likely that they just weren’t in a hurry at the time, since they still thought they could get something out of the rest of what they bought from Yahoo.