SOLVED

Booting Problems after using Windows for long

Copper Contributor

I've got a Windows 10 + Ubuntu 18.04 dual boot setup on my laptop. Windows in on an SSD, while Ubuntu is on a separate HDD. I normally use Ubuntu for most of my work, and occasionally use Windows for Word, Excel, and other stuff. I normally shutdown Windows after completing my work, and never usually put it into sleep mode.

However, 2 days ago, I needed to use Windows for Rufus and backing up some NTFS drives, and so I used it for a longer time than usual, and kept it open throughout the night, and even put it into sleep mode at some point.

The next time I tried to boot Ubuntu on it, I was greeted with a very weird boot screen. I have disabled Plymouth or splash, whatever its called, so I'm used to a "black screen with text all over it", where the first line is the fsck output.

Normally, the text size is small from the beginning (high resolution), and halfway through the process, the intel-backlight service turns on, so I get a change in brightness while all the text is being written on the screen.

However, this time, the text started out very large (a very low resolution), and I got multiple errors, including failed to load swapfile, failed to mount partition /mnt/ext4-part, and all the network-related services failed to load, due to which the Snappy Daemon failed to load, and I was stuck in the booting process. It also failed to load the color profiles. (Weirdly enough, the output of fsck is perfectly normal and no corrupted files at all...)

I've even tried by commenting out the swapfile and /mnt/ext4-part lines from /etc/fstab through a live disk, but that doesn't seem to solve the problem...

I have an Nvidia graphics card, if that makes a difference, but I use the nouveau open-source driver and not the proprietary one.

Can someone please tell me what may have gone wrong and how to fix it?

 

1 Reply
best response confirmed by albrechtmyers (Copper Contributor)
Solution
This doesn't sounds like a Windows 10 problem, but more like a bootloader related problem of Linux.
Also, your post doesn't say which Windows 10 version/edition you have.
that custom GPU driver could be the culprit but I don't think so.
1 best response

Accepted Solutions
best response confirmed by albrechtmyers (Copper Contributor)
Solution
This doesn't sounds like a Windows 10 problem, but more like a bootloader related problem of Linux.
Also, your post doesn't say which Windows 10 version/edition you have.
that custom GPU driver could be the culprit but I don't think so.

View solution in original post