Ubuntu hangs at âStarting Show Plymouth Boot Screenâ

Clash Royale CLAN TAG#URR8PPP up vote
1
down vote
favorite
I was running my xubuntu-machine during the night. In the morning I wanted to check something out and I noted that the computer does not respond anymore. It didn't even send a signal to my monitor. Anyway, I shut the machine down and restarted it. Afterwards, I restarted it, passed the boot menu and got stuck at "Starting Show Plymouth Boot Screen".
My observations so far:
Generally, my computer seems to work be pretty slowly. When I enter the grub menu everything takes ages. That's why I tried MemCheck, in order to check whether the RAM is ok! => Seems to be ok ( I just run it an 3 hours, It passed to passes, and eventually got stuck again:) ).
Another weird issue is that I cannot load a live-system or anything. I prepared a bootable USB to install a new ubuntu system but I end up with a black screen with only a cursor at the top left.
It seems to my that it is a HW issue.
I would like to check the CPU, but do not know which onboard-applications I can use (As everything takes ages I cannot really install anything, or update anything).
Partially, I can make to a TTY session but mostly I do not reach it. In the recovery (grub) mode I already tried to repair broken packages. I got an error something like this: Message: 'not running quirks in partialUpgrad mode' Arguments: ()
So far I can:
Enter boot-menu and pass it
Enter grub-menu
Enter TTY (sometimes)
I cannot:
- Use a bootable device, e.g a USB to reinstall xubuntu
My question:
- How can I check all my hardware in this case?
- What the hell is going on with my system?
More Info:
sudo dpkg --configure -a
dpkg: error : reading package info file 'var/lib/dpkg/updates/0000': Input/output error
Thanks!
boot hardware plymouth
 |Â
show 3 more comments
up vote
1
down vote
favorite
I was running my xubuntu-machine during the night. In the morning I wanted to check something out and I noted that the computer does not respond anymore. It didn't even send a signal to my monitor. Anyway, I shut the machine down and restarted it. Afterwards, I restarted it, passed the boot menu and got stuck at "Starting Show Plymouth Boot Screen".
My observations so far:
Generally, my computer seems to work be pretty slowly. When I enter the grub menu everything takes ages. That's why I tried MemCheck, in order to check whether the RAM is ok! => Seems to be ok ( I just run it an 3 hours, It passed to passes, and eventually got stuck again:) ).
Another weird issue is that I cannot load a live-system or anything. I prepared a bootable USB to install a new ubuntu system but I end up with a black screen with only a cursor at the top left.
It seems to my that it is a HW issue.
I would like to check the CPU, but do not know which onboard-applications I can use (As everything takes ages I cannot really install anything, or update anything).
Partially, I can make to a TTY session but mostly I do not reach it. In the recovery (grub) mode I already tried to repair broken packages. I got an error something like this: Message: 'not running quirks in partialUpgrad mode' Arguments: ()
So far I can:
Enter boot-menu and pass it
Enter grub-menu
Enter TTY (sometimes)
I cannot:
- Use a bootable device, e.g a USB to reinstall xubuntu
My question:
- How can I check all my hardware in this case?
- What the hell is going on with my system?
More Info:
sudo dpkg --configure -a
dpkg: error : reading package info file 'var/lib/dpkg/updates/0000': Input/output error
Thanks!
boot hardware plymouth
input/output error is not a good sign.. sounds like you may have a harddrive issue .. is there a reason you cant boot from a USB or CDRom? .. have you tried the Grub menu / advanced options and chose the recovery mode and then the fsck option to check the hard drive and the dpkg option to try to fix any broken packages?
â John Orion
Mar 29 at 18:55
oops sorry didn't notice you did say you tried the dpkg option ... I still think the fsck option may show and hopefully correct issues you are having with the drive .. but im only guessing at this point :(
â John Orion
Mar 29 at 19:02
Thanks so far! "Check all file systems" does not produce any error. Seems fine, so far
â Henrik
Mar 29 at 19:21
hmmm .. you may have to look at your/etc/fstaband the output ofsudo blkidand make sure that the partitions and UUIDS match in the fstab file. .. but .. its getting a bit over my skill level .. I think you will have to do it from recovery command prompt .. not sure if you have to mount it first to 'see' the fstab file .. haven't messed with the recovery much :( .. the slowness may just be a heavy load because of something not functioning properly in the OS ... but I guess you cant get into the actual full OS ... or I would suggest runningtoporhtopif you have it installed
â John Orion
Mar 29 at 19:42
Alrighty! The bigger problem is that i cannot install a new op, as i get stuck when using the bootable usb (which I used to originally install the system).
â Henrik
Mar 29 at 19:45
 |Â
show 3 more comments
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I was running my xubuntu-machine during the night. In the morning I wanted to check something out and I noted that the computer does not respond anymore. It didn't even send a signal to my monitor. Anyway, I shut the machine down and restarted it. Afterwards, I restarted it, passed the boot menu and got stuck at "Starting Show Plymouth Boot Screen".
My observations so far:
Generally, my computer seems to work be pretty slowly. When I enter the grub menu everything takes ages. That's why I tried MemCheck, in order to check whether the RAM is ok! => Seems to be ok ( I just run it an 3 hours, It passed to passes, and eventually got stuck again:) ).
Another weird issue is that I cannot load a live-system or anything. I prepared a bootable USB to install a new ubuntu system but I end up with a black screen with only a cursor at the top left.
It seems to my that it is a HW issue.
I would like to check the CPU, but do not know which onboard-applications I can use (As everything takes ages I cannot really install anything, or update anything).
Partially, I can make to a TTY session but mostly I do not reach it. In the recovery (grub) mode I already tried to repair broken packages. I got an error something like this: Message: 'not running quirks in partialUpgrad mode' Arguments: ()
So far I can:
Enter boot-menu and pass it
Enter grub-menu
Enter TTY (sometimes)
I cannot:
- Use a bootable device, e.g a USB to reinstall xubuntu
My question:
- How can I check all my hardware in this case?
- What the hell is going on with my system?
More Info:
sudo dpkg --configure -a
dpkg: error : reading package info file 'var/lib/dpkg/updates/0000': Input/output error
Thanks!
boot hardware plymouth
I was running my xubuntu-machine during the night. In the morning I wanted to check something out and I noted that the computer does not respond anymore. It didn't even send a signal to my monitor. Anyway, I shut the machine down and restarted it. Afterwards, I restarted it, passed the boot menu and got stuck at "Starting Show Plymouth Boot Screen".
My observations so far:
Generally, my computer seems to work be pretty slowly. When I enter the grub menu everything takes ages. That's why I tried MemCheck, in order to check whether the RAM is ok! => Seems to be ok ( I just run it an 3 hours, It passed to passes, and eventually got stuck again:) ).
Another weird issue is that I cannot load a live-system or anything. I prepared a bootable USB to install a new ubuntu system but I end up with a black screen with only a cursor at the top left.
It seems to my that it is a HW issue.
I would like to check the CPU, but do not know which onboard-applications I can use (As everything takes ages I cannot really install anything, or update anything).
Partially, I can make to a TTY session but mostly I do not reach it. In the recovery (grub) mode I already tried to repair broken packages. I got an error something like this: Message: 'not running quirks in partialUpgrad mode' Arguments: ()
So far I can:
Enter boot-menu and pass it
Enter grub-menu
Enter TTY (sometimes)
I cannot:
- Use a bootable device, e.g a USB to reinstall xubuntu
My question:
- How can I check all my hardware in this case?
- What the hell is going on with my system?
More Info:
sudo dpkg --configure -a
dpkg: error : reading package info file 'var/lib/dpkg/updates/0000': Input/output error
Thanks!
boot hardware plymouth
boot hardware plymouth
edited Mar 29 at 18:42
asked Mar 29 at 18:25
Henrik
63
63
input/output error is not a good sign.. sounds like you may have a harddrive issue .. is there a reason you cant boot from a USB or CDRom? .. have you tried the Grub menu / advanced options and chose the recovery mode and then the fsck option to check the hard drive and the dpkg option to try to fix any broken packages?
â John Orion
Mar 29 at 18:55
oops sorry didn't notice you did say you tried the dpkg option ... I still think the fsck option may show and hopefully correct issues you are having with the drive .. but im only guessing at this point :(
â John Orion
Mar 29 at 19:02
Thanks so far! "Check all file systems" does not produce any error. Seems fine, so far
â Henrik
Mar 29 at 19:21
hmmm .. you may have to look at your/etc/fstaband the output ofsudo blkidand make sure that the partitions and UUIDS match in the fstab file. .. but .. its getting a bit over my skill level .. I think you will have to do it from recovery command prompt .. not sure if you have to mount it first to 'see' the fstab file .. haven't messed with the recovery much :( .. the slowness may just be a heavy load because of something not functioning properly in the OS ... but I guess you cant get into the actual full OS ... or I would suggest runningtoporhtopif you have it installed
â John Orion
Mar 29 at 19:42
Alrighty! The bigger problem is that i cannot install a new op, as i get stuck when using the bootable usb (which I used to originally install the system).
â Henrik
Mar 29 at 19:45
 |Â
show 3 more comments
input/output error is not a good sign.. sounds like you may have a harddrive issue .. is there a reason you cant boot from a USB or CDRom? .. have you tried the Grub menu / advanced options and chose the recovery mode and then the fsck option to check the hard drive and the dpkg option to try to fix any broken packages?
â John Orion
Mar 29 at 18:55
oops sorry didn't notice you did say you tried the dpkg option ... I still think the fsck option may show and hopefully correct issues you are having with the drive .. but im only guessing at this point :(
â John Orion
Mar 29 at 19:02
Thanks so far! "Check all file systems" does not produce any error. Seems fine, so far
â Henrik
Mar 29 at 19:21
hmmm .. you may have to look at your/etc/fstaband the output ofsudo blkidand make sure that the partitions and UUIDS match in the fstab file. .. but .. its getting a bit over my skill level .. I think you will have to do it from recovery command prompt .. not sure if you have to mount it first to 'see' the fstab file .. haven't messed with the recovery much :( .. the slowness may just be a heavy load because of something not functioning properly in the OS ... but I guess you cant get into the actual full OS ... or I would suggest runningtoporhtopif you have it installed
â John Orion
Mar 29 at 19:42
Alrighty! The bigger problem is that i cannot install a new op, as i get stuck when using the bootable usb (which I used to originally install the system).
â Henrik
Mar 29 at 19:45
input/output error is not a good sign.. sounds like you may have a harddrive issue .. is there a reason you cant boot from a USB or CDRom? .. have you tried the Grub menu / advanced options and chose the recovery mode and then the fsck option to check the hard drive and the dpkg option to try to fix any broken packages?
â John Orion
Mar 29 at 18:55
input/output error is not a good sign.. sounds like you may have a harddrive issue .. is there a reason you cant boot from a USB or CDRom? .. have you tried the Grub menu / advanced options and chose the recovery mode and then the fsck option to check the hard drive and the dpkg option to try to fix any broken packages?
â John Orion
Mar 29 at 18:55
oops sorry didn't notice you did say you tried the dpkg option ... I still think the fsck option may show and hopefully correct issues you are having with the drive .. but im only guessing at this point :(
â John Orion
Mar 29 at 19:02
oops sorry didn't notice you did say you tried the dpkg option ... I still think the fsck option may show and hopefully correct issues you are having with the drive .. but im only guessing at this point :(
â John Orion
Mar 29 at 19:02
Thanks so far! "Check all file systems" does not produce any error. Seems fine, so far
â Henrik
Mar 29 at 19:21
Thanks so far! "Check all file systems" does not produce any error. Seems fine, so far
â Henrik
Mar 29 at 19:21
hmmm .. you may have to look at your
/etc/fstab and the output of sudo blkid and make sure that the partitions and UUIDS match in the fstab file. .. but .. its getting a bit over my skill level .. I think you will have to do it from recovery command prompt .. not sure if you have to mount it first to 'see' the fstab file .. haven't messed with the recovery much :( .. the slowness may just be a heavy load because of something not functioning properly in the OS ... but I guess you cant get into the actual full OS ... or I would suggest running top or htop if you have it installedâ John Orion
Mar 29 at 19:42
hmmm .. you may have to look at your
/etc/fstab and the output of sudo blkid and make sure that the partitions and UUIDS match in the fstab file. .. but .. its getting a bit over my skill level .. I think you will have to do it from recovery command prompt .. not sure if you have to mount it first to 'see' the fstab file .. haven't messed with the recovery much :( .. the slowness may just be a heavy load because of something not functioning properly in the OS ... but I guess you cant get into the actual full OS ... or I would suggest running top or htop if you have it installedâ John Orion
Mar 29 at 19:42
Alrighty! The bigger problem is that i cannot install a new op, as i get stuck when using the bootable usb (which I used to originally install the system).
â Henrik
Mar 29 at 19:45
Alrighty! The bigger problem is that i cannot install a new op, as i get stuck when using the bootable usb (which I used to originally install the system).
â Henrik
Mar 29 at 19:45
 |Â
show 3 more comments
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f1020353%2fubuntu-hangs-at-starting-show-plymouth-boot-screen%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
input/output error is not a good sign.. sounds like you may have a harddrive issue .. is there a reason you cant boot from a USB or CDRom? .. have you tried the Grub menu / advanced options and chose the recovery mode and then the fsck option to check the hard drive and the dpkg option to try to fix any broken packages?
â John Orion
Mar 29 at 18:55
oops sorry didn't notice you did say you tried the dpkg option ... I still think the fsck option may show and hopefully correct issues you are having with the drive .. but im only guessing at this point :(
â John Orion
Mar 29 at 19:02
Thanks so far! "Check all file systems" does not produce any error. Seems fine, so far
â Henrik
Mar 29 at 19:21
hmmm .. you may have to look at your
/etc/fstaband the output ofsudo blkidand make sure that the partitions and UUIDS match in the fstab file. .. but .. its getting a bit over my skill level .. I think you will have to do it from recovery command prompt .. not sure if you have to mount it first to 'see' the fstab file .. haven't messed with the recovery much :( .. the slowness may just be a heavy load because of something not functioning properly in the OS ... but I guess you cant get into the actual full OS ... or I would suggest runningtoporhtopif you have it installedâ John Orion
Mar 29 at 19:42
Alrighty! The bigger problem is that i cannot install a new op, as i get stuck when using the bootable usb (which I used to originally install the system).
â Henrik
Mar 29 at 19:45