Ubuntu – Xubuntu 16.04 doesn’t boot; hangs after fsck

16.04bootdual-bootgrub2xubuntu

I have just installed xubuntu 16.04LTS on a Dell Inspiron Mini as a dual-boot with Windows 7.

When I booted it up for the first time yesterday, it worked fine. Today, however, I see the following:

/dev/sda5: recovering journal
/dev/sda5: clean, 174140/6045696 files, 1444115/24179712 blocks

I've consulted multiple other questions, such as Startup problem in 16.04 lts?, My Ubuntu is running fsck on every bootup, and Linux hanging at boot after fsck, which suggest that fsck is running on every boot or I have missing drivers, but none of them were exactly the same problem as I had.

However, in the problems concerning fsck, there is simply an irritating delay. Here it is stuck with this screen indefinitely, as far as I can tell. I've been waiting for quite a while now, and there hasn't been any change.

Do you have any possible solutions? Thanks.

Best Answer

Hold Right-Shift to access GRUB-bootloader. Go to advanced options and start recovery-mode. When recovery mode menu opens, select to continue normal boot. Now if you get to login open terminal and type sudo nano /etc/default/grub

This is what I did.

I changed "splash quiet" part to "nomodeset radeon.modeset=0 systemd.recover_state=0" if I'm correct nomodeset deals with intel or nvidia cards, could work with ati too. I have old ati card so radeon.modeset=0 seemed right but I did not play with these more to be really sure.
save file in nano by pressing ctrl+o and then exit ctrl+x
back in terminal again run sudo update-grub

Now try to do normal reboot by sudo reboot and see if this got your system booting normally.

ps. So maybe the problem is with display drivers??

Related Solutions

Boot – Fix Ubuntu 14.04 Boot Hanging at Logo After Update

The root cause was a huge number of files in my /tmp directory.

I'd used the /tmp directory to store millions of files earlier. It turns out that having that many files there causes the service which cleans /tmp to take a long, long time (duh). After moving the files out of /tmp, the problem is solved. It had nothing to do with the upgrade; that was just a coincidence.

In case it helps anyone later, here's the process I used to figure it out. I enabled the "Magic SysRq key" by changing etc/sysctl.d/10-magic-sysrq.conf. Then, I reproduced the problem by rebooting; when startup hung, I hit Alt-SysRq-t. This dumped the following in the kernel buffer, read using dmesg:

[   36.318527] SysRq : Show Blocked State
[   36.318696]   task                        PC stack   pid father
[   36.318719] find            D ffff88041dd93480     0   839    788 0x00000000
[   36.318721]  ffff880405d07a48 0000000000000082 ffff880401136000 ffff880405d07fd8
[   36.318723]  0000000000013480 0000000000013480 ffff880401136000 ffff88041dd93d18
[   36.318725]  ffff88041dfab460 0000000000000002 ffffffff811ef380 ffff880405d07ac0

It dumps a lot more than this, but this is the relevant part. This shows the blocked task is find. After that, it was just a matter of a knowledgeable friend knowing that the /tmp cleaning service was a likely culprit.

Ubuntu – target filesystem doesn’t have requested /sbin/init. /bin/sh: 0 : Can’t open splash – Ubuntu 15.04

It seems your /sbin/init file is corrupted as you were trying to force shutdown.

One thing you can do is:

Make a boot-able USB with the same 15.04 by using unetbootIn or Startup disk creator
Connect it in your PC boot into that USB
Select the option try Ubuntu without installing
Here search for the partition where your 15.04 installed, it might be /dev/sda1 to n. There we need to replace /sbin completely with our installation source's /sbin.

You can use sudo mv command for that, after replacing /sbin, reboot your system.

It will work :)

Best Answer

Related Solutions

Boot – Fix Ubuntu 14.04 Boot Hanging at Logo After Update

Ubuntu – target filesystem doesn’t have requested /sbin/init. /bin/sh: 0 : Can’t open splash – Ubuntu 15.04

Related Question