this post was submitted on 02 Jul 2023
92 points (98.9% liked)
linuxmemes
21172 readers
949 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudo
in Windows.
- No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
Sounds like Windows rewrote boot manager. It likes to do that sometimes. Basically your only choice is taking live USB booting into it and reinstalling grub.
This is likely what happened. I think I'm gonna format the Windows SSD attached to the server (old install) and reinstall grub. Tomorrow, I guess. :(
Edit: Now that I've had a moment to think, I realized that I deleted grub. It was on another SSD that I wiped. It was on the SSD that my old OS was on that I wasn't using anymore. But my actual Linux install came from another computer. So when I dropped it in what became my server, I installed grub manually on the old SSD (which has now been wiped) to boot to my Linux SSD.