Ubuntu stuck while booting [duplicate]
This question already has an answer here:
My computer boots to a black screen, what options do I have to fix it?
32 answers
After restarting my ubuntu is stuck on a black screen with some boot messages after restarting. I tried to use the recovery mode and use the dpgk and fsck commands, the dpgk didn't change anything and fsck wouldn't work because the system is in read/write mode.
What are my options here? I have some important files on the installation so I can't just reinstall.
Might be worth mentioning that I have a dual boot, grub menu is working fine, and that I restarted initially because I couldn't open terminals any more. Version is Ubuntu 18.04.
The last boot message is "Started the Apache HTTP server.dispatcher service .... ystem changes.pp link was shut down".
Thanks for reading, any help is greatly appreciated!
boot dual-boot
asked Jan 6 at 16:29
Roel van der BurghtRoel van der Burght
1
marked as duplicate by karel, Eric Carvalho, Thomas, Charles Green, guiverc Jan 17 at 10:19
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
add a comment |
This question already has an answer here:
My computer boots to a black screen, what options do I have to fix it?
32 answers
After restarting my ubuntu is stuck on a black screen with some boot messages after restarting. I tried to use the recovery mode and use the dpgk and fsck commands, the dpgk didn't change anything and fsck wouldn't work because the system is in read/write mode.
What are my options here? I have some important files on the installation so I can't just reinstall.
Might be worth mentioning that I have a dual boot, grub menu is working fine, and that I restarted initially because I couldn't open terminals any more. Version is Ubuntu 18.04.
The last boot message is "Started the Apache HTTP server.dispatcher service .... ystem changes.pp link was shut down".
Thanks for reading, any help is greatly appreciated!
boot dual-boot
asked Jan 6 at 16:29
Roel van der BurghtRoel van der Burght
1
marked as duplicate by karel, Eric Carvalho, Thomas, Charles Green, guiverc Jan 17 at 10:19
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
add a comment |
This question already has an answer here:
My computer boots to a black screen, what options do I have to fix it?
32 answers
After restarting my ubuntu is stuck on a black screen with some boot messages after restarting. I tried to use the recovery mode and use the dpgk and fsck commands, the dpgk didn't change anything and fsck wouldn't work because the system is in read/write mode.
What are my options here? I have some important files on the installation so I can't just reinstall.
Might be worth mentioning that I have a dual boot, grub menu is working fine, and that I restarted initially because I couldn't open terminals any more. Version is Ubuntu 18.04.
The last boot message is "Started the Apache HTTP server.dispatcher service .... ystem changes.pp link was shut down".
Thanks for reading, any help is greatly appreciated!
boot dual-boot
asked Jan 6 at 16:29
Roel van der BurghtRoel van der Burght
1
This question already has an answer here:
My computer boots to a black screen, what options do I have to fix it?
32 answers
After restarting my ubuntu is stuck on a black screen with some boot messages after restarting. I tried to use the recovery mode and use the dpgk and fsck commands, the dpgk didn't change anything and fsck wouldn't work because the system is in read/write mode.
What are my options here? I have some important files on the installation so I can't just reinstall.
Might be worth mentioning that I have a dual boot, grub menu is working fine, and that I restarted initially because I couldn't open terminals any more. Version is Ubuntu 18.04.
The last boot message is "Started the Apache HTTP server.dispatcher service .... ystem changes.pp link was shut down".
Thanks for reading, any help is greatly appreciated!
This question already has an answer here:
My computer boots to a black screen, what options do I have to fix it?
32 answers
boot dual-boot
boot dual-boot
asked Jan 6 at 16:29
Roel van der BurghtRoel van der Burght
1
asked Jan 6 at 16:29
Roel van der BurghtRoel van der Burght
1
asked Jan 6 at 16:29
Roel van der BurghtRoel van der Burght
1
asked Jan 6 at 16:29
Roel van der BurghtRoel van der Burght
1
asked Jan 6 at 16:29
Roel van der BurghtRoel van der Burght
1
1
marked as duplicate by karel, Eric Carvalho, Thomas, Charles Green, guiverc Jan 17 at 10:19
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
marked as duplicate by karel, Eric Carvalho, Thomas, Charles Green, guiverc Jan 17 at 10:19
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
fsck may fix your problem, but as you noticed, in Ubuntu 18.xx, the hard disk is now mounted r/w in Recovery Mode. You'll have to run fsck when booted to a Ubuntu Live DVD/USB.
- 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/sdaX# replacing X with the number you found earlier - repeat the fsck command if there were errors
- type
reboot
answered Jan 6 at 23:51
heynnemaheynnema
18.4k22054
Thanks for your reply. This leaves me with the following message: There are differences between boot sector and its backup. This is mostly harmless. Differences: (offset:original/backup) < A list of memory locations (i think)> 1) Copy original to backup 2) Copy backup to original 3) No action What option do you recommend i choose here?
– Roel van der Burght
Jan 7 at 10:32
@RoelvanderBurght I've never seen that before. I'd FIRST make a good backup of your disk. Then I'd choose 2) Copy backup to original.
– heynnema
Jan 7 at 14:46
I think the reason why you have never seen this before is because i made a mistake in following your procedure. My drives are not named /dev/sdaX but /dev/nvme0n1pX, and me not being all that familiar with the Linux file system i tried to run fsck on a non existing drive (the /dev/sdaX). After i found this out i tried running the fsck on the correct drive but unfortunately it did not work. I have recovered my important files using liveusb and will just reinstall Ubuntu. Thanks for the help!
– Roel van der Burght
Jan 8 at 13:06
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
fsck may fix your problem, but as you noticed, in Ubuntu 18.xx, the hard disk is now mounted r/w in Recovery Mode. You'll have to run fsck when booted to a Ubuntu Live DVD/USB.
- 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/sdaX# replacing X with the number you found earlier - repeat the fsck command if there were errors
- type
reboot
answered Jan 6 at 23:51
heynnemaheynnema
18.4k22054
Thanks for your reply. This leaves me with the following message: There are differences between boot sector and its backup. This is mostly harmless. Differences: (offset:original/backup) < A list of memory locations (i think)> 1) Copy original to backup 2) Copy backup to original 3) No action What option do you recommend i choose here?
– Roel van der Burght
Jan 7 at 10:32
@RoelvanderBurght I've never seen that before. I'd FIRST make a good backup of your disk. Then I'd choose 2) Copy backup to original.
– heynnema
Jan 7 at 14:46
I think the reason why you have never seen this before is because i made a mistake in following your procedure. My drives are not named /dev/sdaX but /dev/nvme0n1pX, and me not being all that familiar with the Linux file system i tried to run fsck on a non existing drive (the /dev/sdaX). After i found this out i tried running the fsck on the correct drive but unfortunately it did not work. I have recovered my important files using liveusb and will just reinstall Ubuntu. Thanks for the help!
– Roel van der Burght
Jan 8 at 13:06
add a comment |
fsck may fix your problem, but as you noticed, in Ubuntu 18.xx, the hard disk is now mounted r/w in Recovery Mode. You'll have to run fsck when booted to a Ubuntu Live DVD/USB.
- 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/sdaX# replacing X with the number you found earlier - repeat the fsck command if there were errors
- type
reboot
answered Jan 6 at 23:51
heynnemaheynnema
18.4k22054
Thanks for your reply. This leaves me with the following message: There are differences between boot sector and its backup. This is mostly harmless. Differences: (offset:original/backup) < A list of memory locations (i think)> 1) Copy original to backup 2) Copy backup to original 3) No action What option do you recommend i choose here?
– Roel van der Burght
Jan 7 at 10:32
@RoelvanderBurght I've never seen that before. I'd FIRST make a good backup of your disk. Then I'd choose 2) Copy backup to original.
– heynnema
Jan 7 at 14:46
I think the reason why you have never seen this before is because i made a mistake in following your procedure. My drives are not named /dev/sdaX but /dev/nvme0n1pX, and me not being all that familiar with the Linux file system i tried to run fsck on a non existing drive (the /dev/sdaX). After i found this out i tried running the fsck on the correct drive but unfortunately it did not work. I have recovered my important files using liveusb and will just reinstall Ubuntu. Thanks for the help!
– Roel van der Burght
Jan 8 at 13:06
add a comment |
fsck may fix your problem, but as you noticed, in Ubuntu 18.xx, the hard disk is now mounted r/w in Recovery Mode. You'll have to run fsck when booted to a Ubuntu Live DVD/USB.
- 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/sdaX# replacing X with the number you found earlier - repeat the fsck command if there were errors
- type
reboot
answered Jan 6 at 23:51
heynnemaheynnema
18.4k22054
fsck may fix your problem, but as you noticed, in Ubuntu 18.xx, the hard disk is now mounted r/w in Recovery Mode. You'll have to run fsck when booted to a Ubuntu Live DVD/USB.
- 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/sdaX# replacing X with the number you found earlier - repeat the fsck command if there were errors
- type
reboot
answered Jan 6 at 23:51
heynnemaheynnema
18.4k22054
answered Jan 6 at 23:51
heynnemaheynnema
18.4k22054
answered Jan 6 at 23:51
heynnemaheynnema
18.4k22054
answered Jan 6 at 23:51
heynnemaheynnema
18.4k22054
18.4k22054
Thanks for your reply. This leaves me with the following message: There are differences between boot sector and its backup. This is mostly harmless. Differences: (offset:original/backup) < A list of memory locations (i think)> 1) Copy original to backup 2) Copy backup to original 3) No action What option do you recommend i choose here?
– Roel van der Burght
Jan 7 at 10:32
@RoelvanderBurght I've never seen that before. I'd FIRST make a good backup of your disk. Then I'd choose 2) Copy backup to original.
– heynnema
Jan 7 at 14:46
I think the reason why you have never seen this before is because i made a mistake in following your procedure. My drives are not named /dev/sdaX but /dev/nvme0n1pX, and me not being all that familiar with the Linux file system i tried to run fsck on a non existing drive (the /dev/sdaX). After i found this out i tried running the fsck on the correct drive but unfortunately it did not work. I have recovered my important files using liveusb and will just reinstall Ubuntu. Thanks for the help!
– Roel van der Burght
Jan 8 at 13:06
add a comment |
Thanks for your reply. This leaves me with the following message: There are differences between boot sector and its backup. This is mostly harmless. Differences: (offset:original/backup) < A list of memory locations (i think)> 1) Copy original to backup 2) Copy backup to original 3) No action What option do you recommend i choose here?
– Roel van der Burght
Jan 7 at 10:32
@RoelvanderBurght I've never seen that before. I'd FIRST make a good backup of your disk. Then I'd choose 2) Copy backup to original.
– heynnema
Jan 7 at 14:46
I think the reason why you have never seen this before is because i made a mistake in following your procedure. My drives are not named /dev/sdaX but /dev/nvme0n1pX, and me not being all that familiar with the Linux file system i tried to run fsck on a non existing drive (the /dev/sdaX). After i found this out i tried running the fsck on the correct drive but unfortunately it did not work. I have recovered my important files using liveusb and will just reinstall Ubuntu. Thanks for the help!
– Roel van der Burght
Jan 8 at 13:06
Thanks for your reply. This leaves me with the following message: There are differences between boot sector and its backup. This is mostly harmless. Differences: (offset:original/backup) < A list of memory locations (i think)> 1) Copy original to backup 2) Copy backup to original 3) No action What option do you recommend i choose here?
– Roel van der Burght
Jan 7 at 10:32
Thanks for your reply. This leaves me with the following message: There are differences between boot sector and its backup. This is mostly harmless. Differences: (offset:original/backup) < A list of memory locations (i think)> 1) Copy original to backup 2) Copy backup to original 3) No action What option do you recommend i choose here?
– Roel van der Burght
Jan 7 at 10:32
@RoelvanderBurght I've never seen that before. I'd FIRST make a good backup of your disk. Then I'd choose 2) Copy backup to original.
– heynnema
Jan 7 at 14:46
@RoelvanderBurght I've never seen that before. I'd FIRST make a good backup of your disk. Then I'd choose 2) Copy backup to original.
– heynnema
Jan 7 at 14:46
I think the reason why you have never seen this before is because i made a mistake in following your procedure. My drives are not named /dev/sdaX but /dev/nvme0n1pX, and me not being all that familiar with the Linux file system i tried to run fsck on a non existing drive (the /dev/sdaX). After i found this out i tried running the fsck on the correct drive but unfortunately it did not work. I have recovered my important files using liveusb and will just reinstall Ubuntu. Thanks for the help!
– Roel van der Burght
Jan 8 at 13:06
I think the reason why you have never seen this before is because i made a mistake in following your procedure. My drives are not named /dev/sdaX but /dev/nvme0n1pX, and me not being all that familiar with the Linux file system i tried to run fsck on a non existing drive (the /dev/sdaX). After i found this out i tried running the fsck on the correct drive but unfortunately it did not work. I have recovered my important files using liveusb and will just reinstall Ubuntu. Thanks for the help!
– Roel van der Burght
Jan 8 at 13:06
add a comment |
