Not sure this will help you but windows by default does not really shutoff. Try to google (or duckduckgo or similar) about fast startup mode and how to properly shutdown windows. That might sort it if you are lucky.
this post was submitted on 25 Jun 2024
30 points (85.7% liked)
Linux
48187 readers
1228 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
Thanks, not this in specific but it was something related to not shuting down properly. I powered off from windows by holding the off button instead of clicking on shutdown (I was afraid windows would want to install updates b/c I didn't use it for so long). So I booted windows again and turned it off properly then Debian came back to life.
Great. Glad you managed to fix it. :)
Yes, windows can make some devices not function correctly on Linux (wifi cards for example) when it’s shut down with fast boot enabled
Boot from a live disc/usb, check the kernel logs. That should at least tell you where the boot process got stuck, what to do about it depends on what exactly broke.
You can always boot from a live medium, chroot into it and fix stuff, e.g. a live USB or CD/DVD. They can be created from Windows.
Are you able to see the boot log while it's booting? Hit escape if not, and see where it's getting stuck.
Not related but I've had some dual booting issues aswell. Turns out that the drives mounted in Linux didn't properly unmount on shutdown so when trying to access them on Windows they wouldn't be accessible.
Just some info for anyone that might be having issues
stackexchange will probably give you a better answer than lemmy (that's me trying to be helpful with good advice)
11 partitions.. sounds like some of them need a nofail flag in fstab.
Whatever the answer is, you've now learned to run windows in a virtual machine only.
what aboot separate disks?
The only way windows won't make your bootloader its bitch is if you swap drives which is annoying at best. Virtual machine is the way to go, you can even dedicate a secondary video card to it if you've got the patience to set the VM up right.
I have a VM set up with single GPU pass through from fedora 40 and it works well. I also have win10 and 11 installs on dedicated disks for testing purposes (IHV).
I tend to bounce between them depending on what I need to do. In terms of a 'traditional' multi boot scenario, isolating OS installs to their own disks rarely results in any problems unless you attempt to install Windows with other systems / disks present on SATA 0 (for example)
You mean you're running the VMs direct from disk? That's something I've been wanting to do for a while but just never did.. no reason, just haven't done it. Do you see any performance difference versus a virtual disk?
Sorry no, I meant I use my VFIO setup on the fedora 40 disk, but also have conventional win10 and 11 installs on their own SATA SSDs.
The Win10 VM I have within vfio practically has transparent performance (I don't allocate all threads to it, however), but it's not always suitable for the types of hardware I need to test.