this post was submitted on 06 Apr 2024
24 points (96.2% liked)
Melbourne
1862 readers
52 users here now
This community is a place created for the people of Melbourne and Victoria. We are a positive, welcoming and inclusive community. We might not agree about everything, but we always strive to stay civil and respectful.
The focus of our discussions is based around things that effect Victoria, but we are also free to discuss our local perspective on wider issues. Or head to the regular Daily Random Discussion thread to talk about anything.
Ongoing discussions, FAQs & Resources (still under construction)
Adoption Certificate for Nellie, the Daily Thread numbat (with thanks to @Catfish)
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I've got a dual partition on my laptop and dual boot between windows and Ubuntu. But Ubuntu seems to have booked my windows partition after an update. I don't keep anything important on either partition, or even do anything important on the laptop, so it's no big loss. But I used the windows partition for meetings and 3D printing things.
The drive seems to be working fine though, and I can still access my windows drive through Ubuntu, so it's probably fixable when I've got the time and brain capacity to figure out what the hell is even wrong with it
Do you have two bootloader entries in the BIOS? Or were you using GRUB (or Systemd-boot) to boot between them?
It's probably easy to fix, it's just knowing exactly what happened is probably the most complicated step lol
Hope you're able to fix it. Having the different OSes on different drives (portable drive in case of laptop) seems to cause the least amount of issues with boot entries dying after updates.
It's setup to use GRUB I'm pretty sure. After windows started refusing to boot, GRUB/Ubuntu started yelling about the environment block being too small, although it didn't prevent Ubuntu from starting up I fixed it anyways by deleting and recreating it (following this), which fixed it.
It really is lol. Doesn't help that windows error messages are either hyper specific (or more commonly) so vague they're next to useless with absolutely no in between. Since the error message is hard drive related, all the Microsoft support articles and forum posts are mostly suggesting that the hard drive is completely dead with no hope of recovery and to buy a new one, although since it seems to be working completely fine through Ubuntu I'm doubting that's the case