20

Trying to figure out what this means:

enter image description here

I got into the GRUB menu, chose Advanced Options, boot in recovery mode, login as root, and I did:

root@xps:~# sudo fsck -f /
fsck from util-linux 2.27.1
e2fsck 1.42.13 (17-May-2015)
/dev/nvme0n1p2 is mounted.
e2fsck: Cannot continue, aborting.

Coincidentally, I am also seeing this fuzzy rainbow thing on the outside of desktop windows:

enter image description here

But now the machine won't even boot up at all.

6
  • 4
    Did you have a system crash or power failure or something that? "recovering journal" probably indicates that the filesystem is cleaning itself it up have not been marked as closed cleanly. That should complete and allow normal startup. If you're not able to complete bootup, post more details - do you get a grub menu? How far does bootup progress?
    – Joe P
    Jun 10, 2017 at 21:50
  • 1
    The fsck message in your first image is a normal message that indicates that your file system is clean. That's a good thing. It's hard to figure out your second image, but I suspect that you've got a Nvidia video card, and have installed drivers from the Nvidia web site, and you should be using the Nvidia driver from the Ubuntu repositories instead. The journal thing could be a problem... do you have any drivers installed in Windows that allow you to access EXT4 partitions? Do you know how to manually run fsck? Is your system crashing?
    – heynnema
    Jun 11, 2017 at 0:08
  • Yeah this is not a dual boot machine, it's all Ubuntu, if that adds any info...not sure how to manually run fsck...system is not crashing, but today I turned it off, and it won't boot up again, the "recovering journal" message stays on the screen. Jun 11, 2017 at 1:30
  • Please see my partial answer.
    – heynnema
    Jun 11, 2017 at 13:50
  • 1
    FYI - the fix for the "fuzzy rainbow thing" can be found here Jan 20, 2018 at 19:45

1 Answer 1

17

Let's first check your file system for errors. To check the file system on your Ubuntu partition:

  1. Boot to the GRUB menu.
  2. Choose Advanced Options.
  3. Choose Recovery mode.
  4. Choose Root access.
  5. At the # prompt, type sudo fsck -f /.
  6. Repeat the fsck command if there were errors.
  7. Type reboot.

If for some reason you can't do the above:

  1. Boot to a Ubuntu Live DVD/USB.
  2. Open a terminal window.
  3. Type sudo fdisk -l and determine which /dev/sdaX is your Ubuntu Linux filesystem.
  4. Type sudo fsck -f /dev/sdaX # replacing X with the number you found earlier.
  5. Repeat the fsck command if there were errors.
  6. Type reboot.
15
  • 3
    thanks working on it now. shift did not work to get into GRUB menu, but esc key did work. Jun 12, 2017 at 3:27
  • Ughh, I tried fsck, and I got to an impasse it seems - see updated question, thanks. Jun 12, 2017 at 3:41
  • ok somehow the fsck command seemed to fix things, so was able to reboot and it worked. Strangely, though, in the intermediate, it would log me as a guest, and no password I tried would work for the guest account, even an empty password..pretty annoying. Jun 12, 2017 at 4:02
  • 1
    Did fsck print out pass 1, pass 2, etc., or give you the "disk is mounted" error as the edit to your question indicates?
    – heynnema
    Jun 13, 2017 at 13:10
  • 1
    I had this issue and what worked for me was booting into grub CLI like above, but running sudo apt autoremove sudo apt-get update which prompted me for some --fix-[something I can't remember] flag which I ran and it fixed. Maybe dpkg --configure? Bottom line: try apt commands and you'll be prompted to fix it. My issue was with nvidia-driver-470.
    – Joshua
    Aug 10, 2022 at 2:01

Not the answer you're looking for? Browse other questions tagged .