Linux

45423 readers

910 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

[email protected]

Help me pls, Debian 12 is stuck at boot forever after using Windows on dual boot (lemm.ee)

submitted 5 days ago* (last edited 5 days ago) by [email protected] to c/[email protected]

17 comments fedilink hide all child comments

Edit: solved. Sorry guys, it was something silly. Instead of clicking shutdown on windows I just hard pressed the off button for some seconds on the laptop. So I booted back on windows and let it shutdown normally and then Debian was able to boot again. Hehe

So I've made a clean install of Debian 12 when it came out and have been using only it exclusively for this time. But I had Windows 10 on dual boot already since when I was using Debian 11, I just never booted on Windows until now.

I had to fill in some PDF documents and ended up having to go to windows and use Adobe Acrobat there because LibreOffice and google docs kept messing up the PDF files when I tried to add text to them.

So I did my thing on windows and finished it all just now and then rebooted and tried to boot my Debian 12 and it won't boot. All I see is:

/dev/sda11: recovering journal

/dev/sda11: clean [...] files, [...] blocks

And it is stuck here forever. I already tried to reboot multiple times.

I did nothing on windows to mess with the Linux partitions btw. Only chrome / acrobat / and I sent the files to google drive (so I didn't even try to copy them directly into the Linux partition or anything).

Please tell me I did not brick my OS and need a clean stall pls. What can I try? The answers I've tried from google don't work.

It is Debian 12 stable with nothing but software from the official stable repositories and flatpak.

you are viewing a single comment's thread
view the rest of the comments

[–] vikingtons 1 points 5 days ago (1 children)

what aboot separate disks?

[–] db2 2 points 5 days ago (1 children)

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.

[–] vikingtons 1 points 5 days ago (1 children)

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)

[–] db2 1 points 5 days ago (1 children)

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?

[–] vikingtons 1 points 5 days ago

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.