Freeze after splash screen upon startup
up vote
0
down vote
favorite
I've got a dual boot with Windows 10.
I installed the latest version of Ubuntu today and all went pretty well, rebooted a few times, no problem. Then I opened some of the other partitions/drives and they appeared on my desktop. I tried to delete them but was unable to. Googled how to get rid of them and it said to unmount them, that it wouldn't do any harm. So I did that, and it seems that that caused it to get stuck after the loading/splash screen.
I think I tried to re-mount via Advanced Options in the Grub menu but I have no clue if I did the right thing. I've never used Linux before.
Content of /etc/fstab:
# /etc/fstab: static file system information
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# [file system] [mount point] [type] [options] [dump] [pass]
# / was on /dev/sdb5 during installation
UUID=249483ee-09dc-43d9-956d-a490fb1b5101 / ext4 errors=remount-ro 0 1
# /home was on /dev/sdb7 during installation
UUID=44fc1623-3db6-4a9e-99bb-103c9460565e /home ext4 defaults 0 2
# swap was on /dev/sdb6 during installation
UUID=6cdb970e-de25-42e2-9f07-f3fb442f0d44 none swap sw 0 0
It doesn't actually look like the issue is the partitions. Did a clean install, updated everything, installed Spotify, Discord, Atom and installed Ruby. Rebooted and it freezes all the same. I also added a 1920x1200 screen resolution using xrandr, but that's about everything.
boot partitioning mount freeze drive
asked Dec 2 at 23:50
M3rein
114
|
show 2 more comments
up vote
0
down vote
favorite
I've got a dual boot with Windows 10.
I installed the latest version of Ubuntu today and all went pretty well, rebooted a few times, no problem. Then I opened some of the other partitions/drives and they appeared on my desktop. I tried to delete them but was unable to. Googled how to get rid of them and it said to unmount them, that it wouldn't do any harm. So I did that, and it seems that that caused it to get stuck after the loading/splash screen.
I think I tried to re-mount via Advanced Options in the Grub menu but I have no clue if I did the right thing. I've never used Linux before.
Content of /etc/fstab:
# /etc/fstab: static file system information
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# [file system] [mount point] [type] [options] [dump] [pass]
# / was on /dev/sdb5 during installation
UUID=249483ee-09dc-43d9-956d-a490fb1b5101 / ext4 errors=remount-ro 0 1
# /home was on /dev/sdb7 during installation
UUID=44fc1623-3db6-4a9e-99bb-103c9460565e /home ext4 defaults 0 2
# swap was on /dev/sdb6 during installation
UUID=6cdb970e-de25-42e2-9f07-f3fb442f0d44 none swap sw 0 0
It doesn't actually look like the issue is the partitions. Did a clean install, updated everything, installed Spotify, Discord, Atom and installed Ruby. Rebooted and it freezes all the same. I also added a 1920x1200 screen resolution using xrandr, but that's about everything.
boot partitioning mount freeze drive
asked Dec 2 at 23:50
M3rein
114
Welcome to Ask Ubuntu! :-) Please edit your question and provide the contents of the file/etc/fstabas these partitions probably still get mounted there. if the GUI doesn't work, press [Ctrl][Alt][F1] and log into text mode only and tocat /etc/fstab, then type everything exactly as it is in your question.
– Fabby
Dec 2 at 23:55
Added it in. Might not be very readable but I tried.
– M3rein
Dec 3 at 0:11
Edited for readability, but going to sleep now. Did you delete partition 5, 6 or 7 on your second disk?
– Fabby
Dec 3 at 0:30
It might have been sdb7, /home. I don't quite remember though.
– M3rein
Dec 3 at 0:35
Unfortunately, you don't have enough rep to open a chat room and due some deeper digging. I understood it worked originally without freezing and only froze after you deleted partitions, but now it freezes after the first reboot? Can you still log into the console ([Ctrl][Alt][F1]?
– Fabby
Dec 3 at 9:33
|
show 2 more comments
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I've got a dual boot with Windows 10.
I installed the latest version of Ubuntu today and all went pretty well, rebooted a few times, no problem. Then I opened some of the other partitions/drives and they appeared on my desktop. I tried to delete them but was unable to. Googled how to get rid of them and it said to unmount them, that it wouldn't do any harm. So I did that, and it seems that that caused it to get stuck after the loading/splash screen.
I think I tried to re-mount via Advanced Options in the Grub menu but I have no clue if I did the right thing. I've never used Linux before.
Content of /etc/fstab:
# /etc/fstab: static file system information
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# [file system] [mount point] [type] [options] [dump] [pass]
# / was on /dev/sdb5 during installation
UUID=249483ee-09dc-43d9-956d-a490fb1b5101 / ext4 errors=remount-ro 0 1
# /home was on /dev/sdb7 during installation
UUID=44fc1623-3db6-4a9e-99bb-103c9460565e /home ext4 defaults 0 2
# swap was on /dev/sdb6 during installation
UUID=6cdb970e-de25-42e2-9f07-f3fb442f0d44 none swap sw 0 0
It doesn't actually look like the issue is the partitions. Did a clean install, updated everything, installed Spotify, Discord, Atom and installed Ruby. Rebooted and it freezes all the same. I also added a 1920x1200 screen resolution using xrandr, but that's about everything.
boot partitioning mount freeze drive
asked Dec 2 at 23:50
M3rein
114
I've got a dual boot with Windows 10.
I installed the latest version of Ubuntu today and all went pretty well, rebooted a few times, no problem. Then I opened some of the other partitions/drives and they appeared on my desktop. I tried to delete them but was unable to. Googled how to get rid of them and it said to unmount them, that it wouldn't do any harm. So I did that, and it seems that that caused it to get stuck after the loading/splash screen.
I think I tried to re-mount via Advanced Options in the Grub menu but I have no clue if I did the right thing. I've never used Linux before.
Content of /etc/fstab:
# /etc/fstab: static file system information
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# [file system] [mount point] [type] [options] [dump] [pass]
# / was on /dev/sdb5 during installation
UUID=249483ee-09dc-43d9-956d-a490fb1b5101 / ext4 errors=remount-ro 0 1
# /home was on /dev/sdb7 during installation
UUID=44fc1623-3db6-4a9e-99bb-103c9460565e /home ext4 defaults 0 2
# swap was on /dev/sdb6 during installation
UUID=6cdb970e-de25-42e2-9f07-f3fb442f0d44 none swap sw 0 0
It doesn't actually look like the issue is the partitions. Did a clean install, updated everything, installed Spotify, Discord, Atom and installed Ruby. Rebooted and it freezes all the same. I also added a 1920x1200 screen resolution using xrandr, but that's about everything.
boot partitioning mount freeze drive
boot partitioning mount freeze drive
asked Dec 2 at 23:50
M3rein
114
asked Dec 2 at 23:50
M3rein
114
edited Dec 3 at 7:31
asked Dec 2 at 23:50
M3rein
114
asked Dec 2 at 23:50
M3rein
114
asked Dec 2 at 23:50
M3rein
114
114
Welcome to Ask Ubuntu! :-) Please edit your question and provide the contents of the file/etc/fstabas these partitions probably still get mounted there. if the GUI doesn't work, press [Ctrl][Alt][F1] and log into text mode only and tocat /etc/fstab, then type everything exactly as it is in your question.
– Fabby
Dec 2 at 23:55
Added it in. Might not be very readable but I tried.
– M3rein
Dec 3 at 0:11
Edited for readability, but going to sleep now. Did you delete partition 5, 6 or 7 on your second disk?
– Fabby
Dec 3 at 0:30
It might have been sdb7, /home. I don't quite remember though.
– M3rein
Dec 3 at 0:35
Unfortunately, you don't have enough rep to open a chat room and due some deeper digging. I understood it worked originally without freezing and only froze after you deleted partitions, but now it freezes after the first reboot? Can you still log into the console ([Ctrl][Alt][F1]?
– Fabby
Dec 3 at 9:33
|
show 2 more comments
Welcome to Ask Ubuntu! :-) Please edit your question and provide the contents of the file/etc/fstabas these partitions probably still get mounted there. if the GUI doesn't work, press [Ctrl][Alt][F1] and log into text mode only and tocat /etc/fstab, then type everything exactly as it is in your question.
– Fabby
Dec 2 at 23:55
Added it in. Might not be very readable but I tried.
– M3rein
Dec 3 at 0:11
Edited for readability, but going to sleep now. Did you delete partition 5, 6 or 7 on your second disk?
– Fabby
Dec 3 at 0:30
It might have been sdb7, /home. I don't quite remember though.
– M3rein
Dec 3 at 0:35
Unfortunately, you don't have enough rep to open a chat room and due some deeper digging. I understood it worked originally without freezing and only froze after you deleted partitions, but now it freezes after the first reboot? Can you still log into the console ([Ctrl][Alt][F1]?
– Fabby
Dec 3 at 9:33
Welcome to Ask Ubuntu! :-) Please edit your question and provide the contents of the file
/etc/fstab as these partitions probably still get mounted there. if the GUI doesn't work, press [Ctrl][Alt][F1] and log into text mode only and to cat /etc/fstab, then type everything exactly as it is in your question.– Fabby
Dec 2 at 23:55
Welcome to Ask Ubuntu! :-) Please edit your question and provide the contents of the file
/etc/fstab as these partitions probably still get mounted there. if the GUI doesn't work, press [Ctrl][Alt][F1] and log into text mode only and to cat /etc/fstab, then type everything exactly as it is in your question.– Fabby
Dec 2 at 23:55
Added it in. Might not be very readable but I tried.
– M3rein
Dec 3 at 0:11
Added it in. Might not be very readable but I tried.
– M3rein
Dec 3 at 0:11
Edited for readability, but going to sleep now. Did you delete partition 5, 6 or 7 on your second disk?
– Fabby
Dec 3 at 0:30
Edited for readability, but going to sleep now. Did you delete partition 5, 6 or 7 on your second disk?
– Fabby
Dec 3 at 0:30
It might have been sdb7, /home. I don't quite remember though.
– M3rein
Dec 3 at 0:35
It might have been sdb7, /home. I don't quite remember though.
– M3rein
Dec 3 at 0:35
Unfortunately, you don't have enough rep to open a chat room and due some deeper digging. I understood it worked originally without freezing and only froze after you deleted partitions, but now it freezes after the first reboot? Can you still log into the console ([Ctrl][Alt][F1]?
– Fabby
Dec 3 at 9:33
Unfortunately, you don't have enough rep to open a chat room and due some deeper digging. I understood it worked originally without freezing and only froze after you deleted partitions, but now it freezes after the first reboot? Can you still log into the console ([Ctrl][Alt][F1]?
– Fabby
Dec 3 at 9:33
|
show 2 more comments
1 Answer
1
active
oldest
votes
up vote
1
down vote
The issue wasn't related to partitions (at least not that based on what I've found).
My first monitor would originally show at a resolution of 1024x784 or whatever it was, whereas it should be 1920x1200. I applied these settings with xrandr and all was fine, looked the way I wanted it to, and the website I got it from told me to add these lines to ~/.profile using gedit ~/.profile:
xrandr --newmode "1920x1200_60.00" 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync
xrandr --addmode DVI-I-1 "1920x1200_60.00"
But I had sudo in front of the xrandr command. That's what caused it to freeze on startup. Removing the sudo made it automatically switch to this correct resolution upon startup, and also made it work again.
answered Dec 3 at 17:25
M3rein
114
+1 for finding the solution yourself.
– Fabby
Dec 3 at 18:26
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1098025%2ffreeze-after-splash-screen-upon-startup%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
The issue wasn't related to partitions (at least not that based on what I've found).
My first monitor would originally show at a resolution of 1024x784 or whatever it was, whereas it should be 1920x1200. I applied these settings with xrandr and all was fine, looked the way I wanted it to, and the website I got it from told me to add these lines to ~/.profile using gedit ~/.profile:
xrandr --newmode "1920x1200_60.00" 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync
xrandr --addmode DVI-I-1 "1920x1200_60.00"
But I had sudo in front of the xrandr command. That's what caused it to freeze on startup. Removing the sudo made it automatically switch to this correct resolution upon startup, and also made it work again.
answered Dec 3 at 17:25
M3rein
114
+1 for finding the solution yourself.
– Fabby
Dec 3 at 18:26
add a comment |
up vote
1
down vote
The issue wasn't related to partitions (at least not that based on what I've found).
My first monitor would originally show at a resolution of 1024x784 or whatever it was, whereas it should be 1920x1200. I applied these settings with xrandr and all was fine, looked the way I wanted it to, and the website I got it from told me to add these lines to ~/.profile using gedit ~/.profile:
xrandr --newmode "1920x1200_60.00" 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync
xrandr --addmode DVI-I-1 "1920x1200_60.00"
But I had sudo in front of the xrandr command. That's what caused it to freeze on startup. Removing the sudo made it automatically switch to this correct resolution upon startup, and also made it work again.
answered Dec 3 at 17:25
M3rein
114
+1 for finding the solution yourself.
– Fabby
Dec 3 at 18:26
add a comment |
up vote
1
down vote
up vote
1
down vote
The issue wasn't related to partitions (at least not that based on what I've found).
My first monitor would originally show at a resolution of 1024x784 or whatever it was, whereas it should be 1920x1200. I applied these settings with xrandr and all was fine, looked the way I wanted it to, and the website I got it from told me to add these lines to ~/.profile using gedit ~/.profile:
xrandr --newmode "1920x1200_60.00" 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync
xrandr --addmode DVI-I-1 "1920x1200_60.00"
But I had sudo in front of the xrandr command. That's what caused it to freeze on startup. Removing the sudo made it automatically switch to this correct resolution upon startup, and also made it work again.
answered Dec 3 at 17:25
M3rein
114
The issue wasn't related to partitions (at least not that based on what I've found).
My first monitor would originally show at a resolution of 1024x784 or whatever it was, whereas it should be 1920x1200. I applied these settings with xrandr and all was fine, looked the way I wanted it to, and the website I got it from told me to add these lines to ~/.profile using gedit ~/.profile:
xrandr --newmode "1920x1200_60.00" 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync
xrandr --addmode DVI-I-1 "1920x1200_60.00"
But I had sudo in front of the xrandr command. That's what caused it to freeze on startup. Removing the sudo made it automatically switch to this correct resolution upon startup, and also made it work again.
answered Dec 3 at 17:25
M3rein
114
answered Dec 3 at 17:25
M3rein
114
answered Dec 3 at 17:25
M3rein
114
answered Dec 3 at 17:25
M3rein
114
114
+1 for finding the solution yourself.
– Fabby
Dec 3 at 18:26
add a comment |
+1 for finding the solution yourself.
– Fabby
Dec 3 at 18:26
+1 for finding the solution yourself.
– Fabby
Dec 3 at 18:26
+1 for finding the solution yourself.
– Fabby
Dec 3 at 18:26
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1098025%2ffreeze-after-splash-screen-upon-startup%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Welcome to Ask Ubuntu! :-) Please edit your question and provide the contents of the file
/etc/fstabas these partitions probably still get mounted there. if the GUI doesn't work, press [Ctrl][Alt][F1] and log into text mode only and tocat /etc/fstab, then type everything exactly as it is in your question.– Fabby
Dec 2 at 23:55
Added it in. Might not be very readable but I tried.
– M3rein
Dec 3 at 0:11
Edited for readability, but going to sleep now. Did you delete partition 5, 6 or 7 on your second disk?
– Fabby
Dec 3 at 0:30
It might have been sdb7, /home. I don't quite remember though.
– M3rein
Dec 3 at 0:35
Unfortunately, you don't have enough rep to open a chat room and due some deeper digging. I understood it worked originally without freezing and only froze after you deleted partitions, but now it freezes after the first reboot? Can you still log into the console ([Ctrl][Alt][F1]?
– Fabby
Dec 3 at 9:33