-1

Short while after installation and kernel update I get this Error & unable to access desktop.

Unexpected Inconsistency

In System setup - there's no option to prioritize Boot device as usual.

Boot from HD only

My question is: How should I access desktop or restore the boot prioritize ability?

[Please be specific & detailed as possible]

stumblebee
  • 3,547
EL Dandan Khen
  • 1

1 Answers1

0

To check/repair the file system on your Ubuntu partition...

  • boot to the GRUB menu
  • choose Advanced Options
  • choose Recovery mode
  • choose Root access
  • at the # prompt, type sudo fsck -f /dev/mapper/mint--vg-root or sudo fsck -f /
  • repeat the fsck command if there were errors
  • type reboot

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

  • boot to a Ubuntu Live DVD/USB
  • start gparted and determine which /dev/sdaX is your Ubuntu EXT4 partition
  • quit gparted
  • open a terminal window
  • type sudo fsck -f /dev/mapper/mint--vg-root or sudo fsck -f /dev/sdaX # replacing X with the number you found earlier
  • repeat the fsck command if there were errors
  • type reboot
heynnema
  • 70,711
  • Why the sudo if you're in a root shell already? – Sebastian Stark Apr 25 '18 at 06:00
  • @SebastianStark probably habit... but I've seen situations where even though you're in root, some commands that would normally require sudo, post an error/warning message if sudo isn't used, even in root. – heynnema Apr 25 '18 at 11:31
  • I think it's a bad habit, and those are bad programs :) – Sebastian Stark Apr 25 '18 at 11:34
  • @SebastianStark using sudo in root shell makes no difference... and what are bad programs? fsck isn't. – heynnema Apr 25 '18 at 11:53
  • I meant those programs you mentioned that warn you about not using sudo, although you are root already. It makes no (big) difference, but it could give newbies the impression that "for fsck you need sudo" – Sebastian Stark Apr 25 '18 at 11:59
  • @SebastianStark that's one reason that I DO leave sudo in my answers... sudo IS required for fsck in other situations... like if you were to want to fsck a different unmounted partition, from the terminal app. – heynnema Apr 25 '18 at 12:10
  • Thank you @heynema - I follow the instructions. How do I choose root access? Its not like previous steps where I have menu.. – EL Dandan Khen Apr 28 '18 at 14:22
  • @ELDandanKhen just follow my instructions, and it'll take you to root access, where you can do the fsck. – heynnema Apr 28 '18 at 14:28
  • I'll be more than glad to mark it as it works.. how shall I choose root access? tried to type the commends it didn't bring me further than step 4 – EL Dandan Khen Apr 28 '18 at 14:57
  • @ELDandanKhen Don't you get to the # prompt after choosing root access from the menus? – heynnema Apr 28 '18 at 16:32
  • @heynnema After entering recovery mode I put password and it brings me to the screen in picture 1 -is that the "root access"? – EL Dandan Khen Apr 28 '18 at 17:22
  • @ELDandanKhen ah, now I get see the problem. Type help or exit, or hit the Enter key, and then enter the fsck command. You may or may not need the sudo at the beginning of the fsck command. Let me know which fsck command you finally use, and I'll update my instructions for future readers. – heynnema Apr 28 '18 at 17:44
  • Well - help brought up all possible commands - exit brought up the same error message sudo fsck - /bin/sh: sudo: not found

    fsck brings fsck from util-linux 2.27.1 (infitramfs)

     – EL Dandan Khen Apr 28 '18 at 20:16
  • I wonder how to surpass that error or even fix the boot menu via system setup – EL Dandan Khen Apr 28 '18 at 20:20
  • @ELDandanKhen then try the fsck directly at the infitramfs prompt. Report back. – heynnema Apr 28 '18 at 21:23
  • (initramfs) fsck fsck fromutil-linux 2.27.1 (initramfs) – EL Dandan Khen Apr 29 '18 at 08:08
  • @heynnema not responding further than that.. what else might work? – EL Dandan Khen Apr 29 '18 at 08:11
  • @ELDandanKhen I provided a possible alternate way to proceed in my answer. Let me know how it goes. – heynnema Apr 29 '18 at 15:52