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.
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.
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.
@GreatDong3000 boot with a live versión on Debian and repair the grub !
