Unable to boot from system or access desktop
Clash Royale CLAN TAG#URR8PPP up vote
0
down vote
favorite
Short while after installation and kernel update
I get this Error & unable to access desktop.
In System setup - there's no option to prioritize
Boot device as usual.
My question is: How should I access desktop
or restore the boot prioritize ability?
[Please be specific & detailed as possible]
boot xubuntu
edited Apr 25 at 3:22
stumblebee
2,3083922
asked Apr 24 at 21:10
EL Dandan Khen
12
add a comment |Â
up vote
0
down vote
favorite
Short while after installation and kernel update
I get this Error & unable to access desktop.
In System setup - there's no option to prioritize
Boot device as usual.
My question is: How should I access desktop
or restore the boot prioritize ability?
[Please be specific & detailed as possible]
boot xubuntu
edited Apr 25 at 3:22
stumblebee
2,3083922
asked Apr 24 at 21:10
EL Dandan Khen
12
Did you actually do what the error message recommends?
– Sebastian Stark
Apr 24 at 22:37
I don't know HOW exactly to apply it. would you kindly instruct me?
– EL Dandan Khen
Apr 24 at 23:30
It is described here: askubuntu.com/questions/697190/…
– Sebastian Stark
Apr 25 at 10:02
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Short while after installation and kernel update
I get this Error & unable to access desktop.
In System setup - there's no option to prioritize
Boot device as usual.
My question is: How should I access desktop
or restore the boot prioritize ability?
[Please be specific & detailed as possible]
boot xubuntu
edited Apr 25 at 3:22
stumblebee
2,3083922
asked Apr 24 at 21:10
EL Dandan Khen
12
Short while after installation and kernel update
I get this Error & unable to access desktop.
In System setup - there's no option to prioritize
Boot device as usual.
My question is: How should I access desktop
or restore the boot prioritize ability?
[Please be specific & detailed as possible]
boot xubuntu
edited Apr 25 at 3:22
stumblebee
2,3083922
asked Apr 24 at 21:10
EL Dandan Khen
12
edited Apr 25 at 3:22
stumblebee
2,3083922
edited Apr 25 at 3:22
stumblebee
2,3083922
edited Apr 25 at 3:22
stumblebee
2,3083922
2,3083922
asked Apr 24 at 21:10
EL Dandan Khen
12
asked Apr 24 at 21:10
EL Dandan Khen
12
asked Apr 24 at 21:10
EL Dandan Khen
12
12
Did you actually do what the error message recommends?
– Sebastian Stark
Apr 24 at 22:37
I don't know HOW exactly to apply it. would you kindly instruct me?
– EL Dandan Khen
Apr 24 at 23:30
It is described here: askubuntu.com/questions/697190/…
– Sebastian Stark
Apr 25 at 10:02
add a comment |Â
Did you actually do what the error message recommends?
– Sebastian Stark
Apr 24 at 22:37
I don't know HOW exactly to apply it. would you kindly instruct me?
– EL Dandan Khen
Apr 24 at 23:30
It is described here: askubuntu.com/questions/697190/…
– Sebastian Stark
Apr 25 at 10:02
Did you actually do what the error message recommends?
– Sebastian Stark
Apr 24 at 22:37
Did you actually do what the error message recommends?
– Sebastian Stark
Apr 24 at 22:37
I don't know HOW exactly to apply it. would you kindly instruct me?
– EL Dandan Khen
Apr 24 at 23:30
I don't know HOW exactly to apply it. would you kindly instruct me?
– EL Dandan Khen
Apr 24 at 23:30
It is described here: askubuntu.com/questions/697190/…
– Sebastian Stark
Apr 25 at 10:02
It is described here: askubuntu.com/questions/697190/…
– Sebastian Stark
Apr 25 at 10:02
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
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-rootorsudo fsck -f / - repeat the
fsckcommand if there were errors - type
reboot
If for some reason you can't do the above...
- boot to a Ubuntu Live DVD/USB
- start
gpartedand determine which /dev/sdaX is your Ubuntu EXT4 partition - quit
gparted - open a
terminalwindow - type
sudo fsck -f /dev/mapper/mint--vg-rootorsudo fsck -f /dev/sdaX# replacing X with the number you found earlier - repeat the fsck command if there were errors
- type
reboot
answered Apr 24 at 23:34
heynnema
15.4k21945
Why the sudo if you're in a root shell already?
– Sebastian Stark
Apr 25 at 6: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 at 11:31
I think it's a bad habit, and those are bad programs :)
– Sebastian Stark
Apr 25 at 11:34
@SebastianStark using sudo in root shell makes no difference... and what are bad programs?fsckisn't.
– heynnema
Apr 25 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 at 11:59
 |Â
show 13 more comments
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
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-rootorsudo fsck -f / - repeat the
fsckcommand if there were errors - type
reboot
If for some reason you can't do the above...
- boot to a Ubuntu Live DVD/USB
- start
gpartedand determine which /dev/sdaX is your Ubuntu EXT4 partition - quit
gparted - open a
terminalwindow - type
sudo fsck -f /dev/mapper/mint--vg-rootorsudo fsck -f /dev/sdaX# replacing X with the number you found earlier - repeat the fsck command if there were errors
- type
reboot
answered Apr 24 at 23:34
heynnema
15.4k21945
Why the sudo if you're in a root shell already?
– Sebastian Stark
Apr 25 at 6: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 at 11:31
I think it's a bad habit, and those are bad programs :)
– Sebastian Stark
Apr 25 at 11:34
@SebastianStark using sudo in root shell makes no difference... and what are bad programs?fsckisn't.
– heynnema
Apr 25 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 at 11:59
 |Â
show 13 more comments
up vote
0
down vote
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-rootorsudo fsck -f / - repeat the
fsckcommand if there were errors - type
reboot
If for some reason you can't do the above...
- boot to a Ubuntu Live DVD/USB
- start
gpartedand determine which /dev/sdaX is your Ubuntu EXT4 partition - quit
gparted - open a
terminalwindow - type
sudo fsck -f /dev/mapper/mint--vg-rootorsudo fsck -f /dev/sdaX# replacing X with the number you found earlier - repeat the fsck command if there were errors
- type
reboot
answered Apr 24 at 23:34
heynnema
15.4k21945
Why the sudo if you're in a root shell already?
– Sebastian Stark
Apr 25 at 6: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 at 11:31
I think it's a bad habit, and those are bad programs :)
– Sebastian Stark
Apr 25 at 11:34
@SebastianStark using sudo in root shell makes no difference... and what are bad programs?fsckisn't.
– heynnema
Apr 25 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 at 11:59
 |Â
show 13 more comments
up vote
0
down vote
up vote
0
down vote
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-rootorsudo fsck -f / - repeat the
fsckcommand if there were errors - type
reboot
If for some reason you can't do the above...
- boot to a Ubuntu Live DVD/USB
- start
gpartedand determine which /dev/sdaX is your Ubuntu EXT4 partition - quit
gparted - open a
terminalwindow - type
sudo fsck -f /dev/mapper/mint--vg-rootorsudo fsck -f /dev/sdaX# replacing X with the number you found earlier - repeat the fsck command if there were errors
- type
reboot
answered Apr 24 at 23:34
heynnema
15.4k21945
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-rootorsudo fsck -f / - repeat the
fsckcommand if there were errors - type
reboot
If for some reason you can't do the above...
- boot to a Ubuntu Live DVD/USB
- start
gpartedand determine which /dev/sdaX is your Ubuntu EXT4 partition - quit
gparted - open a
terminalwindow - type
sudo fsck -f /dev/mapper/mint--vg-rootorsudo fsck -f /dev/sdaX# replacing X with the number you found earlier - repeat the fsck command if there were errors
- type
reboot
answered Apr 24 at 23:34
heynnema
15.4k21945
edited Apr 29 at 15:51
answered Apr 24 at 23:34
heynnema
15.4k21945
answered Apr 24 at 23:34
heynnema
15.4k21945
answered Apr 24 at 23:34
heynnema
15.4k21945
15.4k21945
Why the sudo if you're in a root shell already?
– Sebastian Stark
Apr 25 at 6: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 at 11:31
I think it's a bad habit, and those are bad programs :)
– Sebastian Stark
Apr 25 at 11:34
@SebastianStark using sudo in root shell makes no difference... and what are bad programs?fsckisn't.
– heynnema
Apr 25 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 at 11:59
 |Â
show 13 more comments
Why the sudo if you're in a root shell already?
– Sebastian Stark
Apr 25 at 6: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 at 11:31
I think it's a bad habit, and those are bad programs :)
– Sebastian Stark
Apr 25 at 11:34
@SebastianStark using sudo in root shell makes no difference... and what are bad programs?fsckisn't.
– heynnema
Apr 25 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 at 11:59
Why the sudo if you're in a root shell already?
– Sebastian Stark
Apr 25 at 6:00
Why the sudo if you're in a root shell already?
– Sebastian Stark
Apr 25 at 6: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 at 11:31
@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 at 11:31
I think it's a bad habit, and those are bad programs :)
– Sebastian Stark
Apr 25 at 11:34
I think it's a bad habit, and those are bad programs :)
– Sebastian Stark
Apr 25 at 11:34
@SebastianStark using sudo in root shell makes no difference... and what are bad programs?
fsck isn't.– heynnema
Apr 25 at 11:53
@SebastianStark using sudo in root shell makes no difference... and what are bad programs?
fsck isn't.– heynnema
Apr 25 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 at 11:59
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 at 11:59
 |Â
show 13 more comments
Â
draft saved
draft discarded
Â
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1027924%2funable-to-boot-from-system-or-access-desktop%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Did you actually do what the error message recommends?
– Sebastian Stark
Apr 24 at 22:37
I don't know HOW exactly to apply it. would you kindly instruct me?
– EL Dandan Khen
Apr 24 at 23:30
It is described here: askubuntu.com/questions/697190/…
– Sebastian Stark
Apr 25 at 10:02