Kernel Panic: VFS cannot open root device or unknown block error -6
Note that this is Kubuntu (KDE Ubuntu)
I've been having a problem for a while where if I turn on the computer, it just takes me to a black screen. It sticks there with no output and no hint of what's going on except that the Caps Lock indicator light on my keyboard flashes on and off (weird, right?)
If I then turn off the computer (by holding down the power button for a few seconds), and turn it back on, I get a boot menu where I can choose 'Advanced options for Ubuntu', and that lists different versions, recovery modes, some of which work just fine.
That's what I've bee doing for the two weeks or so I've had this problem, and it worked until just now. The alternative options only booted me into the command line. I was able to fix this with this solution, so now I'm typing this from my desktop.
I'm reluctant to turn off the computer in case it happens again, and I'd like to just tear out the root of the problem.
Screenshot of error:
boot grub2 kubuntu kde
edited Mar 22 '17 at 5:28
darksky
3131212
asked Mar 22 '17 at 0:38
GrundGrund
5636
add a comment |
Note that this is Kubuntu (KDE Ubuntu)
I've been having a problem for a while where if I turn on the computer, it just takes me to a black screen. It sticks there with no output and no hint of what's going on except that the Caps Lock indicator light on my keyboard flashes on and off (weird, right?)
If I then turn off the computer (by holding down the power button for a few seconds), and turn it back on, I get a boot menu where I can choose 'Advanced options for Ubuntu', and that lists different versions, recovery modes, some of which work just fine.
That's what I've bee doing for the two weeks or so I've had this problem, and it worked until just now. The alternative options only booted me into the command line. I was able to fix this with this solution, so now I'm typing this from my desktop.
I'm reluctant to turn off the computer in case it happens again, and I'd like to just tear out the root of the problem.
Screenshot of error:
boot grub2 kubuntu kde
edited Mar 22 '17 at 5:28
darksky
3131212
asked Mar 22 '17 at 0:38
GrundGrund
5636
1
Caps lock blinking is a sign of kernel panic -- fatal crash of the Linux that runs Ubuntu. Try opening/etc/default/grubwith a text editor as root and changeGRUB_CMDLINE_LINUX_DEFAULT="splash quiet"toGRUB_CMDLINE_LINUX_DEFAULT="nosplash debug --verbose". That way you can see exactly what's causing the panic during boot. Then run in terminalsudo update-gruband shut it off. When you turn it back on you should see messages about everything the kernel is doing. See what errors you get just before the crash.
– darksky
Mar 22 '17 at 1:28
Something about mounting the filesystem: imgur.com/VvPLO88
– Grund
Mar 22 '17 at 1:59
add a comment |
Note that this is Kubuntu (KDE Ubuntu)
I've been having a problem for a while where if I turn on the computer, it just takes me to a black screen. It sticks there with no output and no hint of what's going on except that the Caps Lock indicator light on my keyboard flashes on and off (weird, right?)
If I then turn off the computer (by holding down the power button for a few seconds), and turn it back on, I get a boot menu where I can choose 'Advanced options for Ubuntu', and that lists different versions, recovery modes, some of which work just fine.
That's what I've bee doing for the two weeks or so I've had this problem, and it worked until just now. The alternative options only booted me into the command line. I was able to fix this with this solution, so now I'm typing this from my desktop.
I'm reluctant to turn off the computer in case it happens again, and I'd like to just tear out the root of the problem.
Screenshot of error:
boot grub2 kubuntu kde
edited Mar 22 '17 at 5:28
darksky
3131212
asked Mar 22 '17 at 0:38
GrundGrund
5636
Note that this is Kubuntu (KDE Ubuntu)
I've been having a problem for a while where if I turn on the computer, it just takes me to a black screen. It sticks there with no output and no hint of what's going on except that the Caps Lock indicator light on my keyboard flashes on and off (weird, right?)
If I then turn off the computer (by holding down the power button for a few seconds), and turn it back on, I get a boot menu where I can choose 'Advanced options for Ubuntu', and that lists different versions, recovery modes, some of which work just fine.
That's what I've bee doing for the two weeks or so I've had this problem, and it worked until just now. The alternative options only booted me into the command line. I was able to fix this with this solution, so now I'm typing this from my desktop.
I'm reluctant to turn off the computer in case it happens again, and I'd like to just tear out the root of the problem.
Screenshot of error:
boot grub2 kubuntu kde
boot grub2 kubuntu kde
edited Mar 22 '17 at 5:28
darksky
3131212
asked Mar 22 '17 at 0:38
GrundGrund
5636
edited Mar 22 '17 at 5:28
darksky
3131212
asked Mar 22 '17 at 0:38
GrundGrund
5636
edited Mar 22 '17 at 5:28
darksky
3131212
edited Mar 22 '17 at 5:28
darksky
3131212
edited Mar 22 '17 at 5:28
darksky
3131212
3131212
asked Mar 22 '17 at 0:38
GrundGrund
5636
asked Mar 22 '17 at 0:38
GrundGrund
5636
asked Mar 22 '17 at 0:38
GrundGrund
5636
5636
1
Caps lock blinking is a sign of kernel panic -- fatal crash of the Linux that runs Ubuntu. Try opening/etc/default/grubwith a text editor as root and changeGRUB_CMDLINE_LINUX_DEFAULT="splash quiet"toGRUB_CMDLINE_LINUX_DEFAULT="nosplash debug --verbose". That way you can see exactly what's causing the panic during boot. Then run in terminalsudo update-gruband shut it off. When you turn it back on you should see messages about everything the kernel is doing. See what errors you get just before the crash.
– darksky
Mar 22 '17 at 1:28
Something about mounting the filesystem: imgur.com/VvPLO88
– Grund
Mar 22 '17 at 1:59
add a comment |
1
Caps lock blinking is a sign of kernel panic -- fatal crash of the Linux that runs Ubuntu. Try opening/etc/default/grubwith a text editor as root and changeGRUB_CMDLINE_LINUX_DEFAULT="splash quiet"toGRUB_CMDLINE_LINUX_DEFAULT="nosplash debug --verbose". That way you can see exactly what's causing the panic during boot. Then run in terminalsudo update-gruband shut it off. When you turn it back on you should see messages about everything the kernel is doing. See what errors you get just before the crash.
– darksky
Mar 22 '17 at 1:28
Something about mounting the filesystem: imgur.com/VvPLO88
– Grund
Mar 22 '17 at 1:59
1
1
Caps lock blinking is a sign of kernel panic -- fatal crash of the Linux that runs Ubuntu. Try opening
/etc/default/grub with a text editor as root and change GRUB_CMDLINE_LINUX_DEFAULT="splash quiet" to GRUB_CMDLINE_LINUX_DEFAULT="nosplash debug --verbose". That way you can see exactly what's causing the panic during boot. Then run in terminal sudo update-grub and shut it off. When you turn it back on you should see messages about everything the kernel is doing. See what errors you get just before the crash.– darksky
Mar 22 '17 at 1:28
Caps lock blinking is a sign of kernel panic -- fatal crash of the Linux that runs Ubuntu. Try opening
/etc/default/grub with a text editor as root and change GRUB_CMDLINE_LINUX_DEFAULT="splash quiet" to GRUB_CMDLINE_LINUX_DEFAULT="nosplash debug --verbose". That way you can see exactly what's causing the panic during boot. Then run in terminal sudo update-grub and shut it off. When you turn it back on you should see messages about everything the kernel is doing. See what errors you get just before the crash.– darksky
Mar 22 '17 at 1:28
Something about mounting the filesystem: imgur.com/VvPLO88
– Grund
Mar 22 '17 at 1:59
Something about mounting the filesystem: imgur.com/VvPLO88
– Grund
Mar 22 '17 at 1:59
add a comment |
1 Answer
1
active
oldest
votes
It seems someone has been able to solve this issue here
Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
They suggest running
sudo update-initramfs -u -k $(uname -r)
Then
sudo update-grub
edited Apr 13 '17 at 12:24
Community♦
1
answered Mar 22 '17 at 2:59
darkskydarksky
3131212
$ sudo update-initramfs -u -k allupdate-initramfs: Generating /boot/initrd.img-versionWARNING: missing /lib/modules/versionEnsure all necessary drivers are built into the linux image!depmod: ERROR: Bad version passed versiondepmod: ERROR: Bad version passed versiongzip: stdout: No space left on deviceE: mkinitramfs failure cpio 141 gzip 1update-initramfs: failed for /boot/initrd.img-version with 1.
– Grund
Mar 22 '17 at 3:23
According to update-initramfs manualversionis"the specific kernel version for whom the initramfs will be generated. For example the output of uname -r for your currently running kernel."I've updated my post. You should use the version of kernel that will be running your KUbuntu. It looks something like3.5.0-47-generic. Also, it is telling youNo space left on device.So the partition that holds your Linux images might be out of space.
– darksky
Mar 22 '17 at 5:43
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',
autoActivateHeartbeat: false,
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%2f895492%2fkernel-panic-vfs-cannot-open-root-device-or-unknown-block-error-6%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
It seems someone has been able to solve this issue here
Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
They suggest running
sudo update-initramfs -u -k $(uname -r)
Then
sudo update-grub
edited Apr 13 '17 at 12:24
Community♦
1
answered Mar 22 '17 at 2:59
darkskydarksky
3131212
$ sudo update-initramfs -u -k allupdate-initramfs: Generating /boot/initrd.img-versionWARNING: missing /lib/modules/versionEnsure all necessary drivers are built into the linux image!depmod: ERROR: Bad version passed versiondepmod: ERROR: Bad version passed versiongzip: stdout: No space left on deviceE: mkinitramfs failure cpio 141 gzip 1update-initramfs: failed for /boot/initrd.img-version with 1.
– Grund
Mar 22 '17 at 3:23
According to update-initramfs manualversionis"the specific kernel version for whom the initramfs will be generated. For example the output of uname -r for your currently running kernel."I've updated my post. You should use the version of kernel that will be running your KUbuntu. It looks something like3.5.0-47-generic. Also, it is telling youNo space left on device.So the partition that holds your Linux images might be out of space.
– darksky
Mar 22 '17 at 5:43
add a comment |
It seems someone has been able to solve this issue here
Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
They suggest running
sudo update-initramfs -u -k $(uname -r)
Then
sudo update-grub
edited Apr 13 '17 at 12:24
Community♦
1
answered Mar 22 '17 at 2:59
darkskydarksky
3131212
$ sudo update-initramfs -u -k allupdate-initramfs: Generating /boot/initrd.img-versionWARNING: missing /lib/modules/versionEnsure all necessary drivers are built into the linux image!depmod: ERROR: Bad version passed versiondepmod: ERROR: Bad version passed versiongzip: stdout: No space left on deviceE: mkinitramfs failure cpio 141 gzip 1update-initramfs: failed for /boot/initrd.img-version with 1.
– Grund
Mar 22 '17 at 3:23
According to update-initramfs manualversionis"the specific kernel version for whom the initramfs will be generated. For example the output of uname -r for your currently running kernel."I've updated my post. You should use the version of kernel that will be running your KUbuntu. It looks something like3.5.0-47-generic. Also, it is telling youNo space left on device.So the partition that holds your Linux images might be out of space.
– darksky
Mar 22 '17 at 5:43
add a comment |
It seems someone has been able to solve this issue here
Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
They suggest running
sudo update-initramfs -u -k $(uname -r)
Then
sudo update-grub
edited Apr 13 '17 at 12:24
Community♦
1
answered Mar 22 '17 at 2:59
darkskydarksky
3131212
It seems someone has been able to solve this issue here
Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
They suggest running
sudo update-initramfs -u -k $(uname -r)
Then
sudo update-grub
edited Apr 13 '17 at 12:24
Community♦
1
answered Mar 22 '17 at 2:59
darkskydarksky
3131212
edited Apr 13 '17 at 12:24
Community♦
1
edited Apr 13 '17 at 12:24
Community♦
1
edited Apr 13 '17 at 12:24
Community♦
1
1
answered Mar 22 '17 at 2:59
darkskydarksky
3131212
answered Mar 22 '17 at 2:59
darkskydarksky
3131212
answered Mar 22 '17 at 2:59
darkskydarksky
3131212
3131212
$ sudo update-initramfs -u -k allupdate-initramfs: Generating /boot/initrd.img-versionWARNING: missing /lib/modules/versionEnsure all necessary drivers are built into the linux image!depmod: ERROR: Bad version passed versiondepmod: ERROR: Bad version passed versiongzip: stdout: No space left on deviceE: mkinitramfs failure cpio 141 gzip 1update-initramfs: failed for /boot/initrd.img-version with 1.
– Grund
Mar 22 '17 at 3:23
According to update-initramfs manualversionis"the specific kernel version for whom the initramfs will be generated. For example the output of uname -r for your currently running kernel."I've updated my post. You should use the version of kernel that will be running your KUbuntu. It looks something like3.5.0-47-generic. Also, it is telling youNo space left on device.So the partition that holds your Linux images might be out of space.
– darksky
Mar 22 '17 at 5:43
add a comment |
$ sudo update-initramfs -u -k allupdate-initramfs: Generating /boot/initrd.img-versionWARNING: missing /lib/modules/versionEnsure all necessary drivers are built into the linux image!depmod: ERROR: Bad version passed versiondepmod: ERROR: Bad version passed versiongzip: stdout: No space left on deviceE: mkinitramfs failure cpio 141 gzip 1update-initramfs: failed for /boot/initrd.img-version with 1.
– Grund
Mar 22 '17 at 3:23
According to update-initramfs manualversionis"the specific kernel version for whom the initramfs will be generated. For example the output of uname -r for your currently running kernel."I've updated my post. You should use the version of kernel that will be running your KUbuntu. It looks something like3.5.0-47-generic. Also, it is telling youNo space left on device.So the partition that holds your Linux images might be out of space.
– darksky
Mar 22 '17 at 5:43
$ sudo update-initramfs -u -k all update-initramfs: Generating /boot/initrd.img-version WARNING: missing /lib/modules/version Ensure all necessary drivers are built into the linux image! depmod: ERROR: Bad version passed version depmod: ERROR: Bad version passed version gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-version with 1.– Grund
Mar 22 '17 at 3:23
$ sudo update-initramfs -u -k all update-initramfs: Generating /boot/initrd.img-version WARNING: missing /lib/modules/version Ensure all necessary drivers are built into the linux image! depmod: ERROR: Bad version passed version depmod: ERROR: Bad version passed version gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-version with 1.– Grund
Mar 22 '17 at 3:23
According to update-initramfs manual
version is "the specific kernel version for whom the initramfs will be generated. For example the output of uname -r for your currently running kernel." I've updated my post. You should use the version of kernel that will be running your KUbuntu. It looks something like 3.5.0-47-generic. Also, it is telling you No space left on device. So the partition that holds your Linux images might be out of space.– darksky
Mar 22 '17 at 5:43
According to update-initramfs manual
version is "the specific kernel version for whom the initramfs will be generated. For example the output of uname -r for your currently running kernel." I've updated my post. You should use the version of kernel that will be running your KUbuntu. It looks something like 3.5.0-47-generic. Also, it is telling you No space left on device. So the partition that holds your Linux images might be out of space.– darksky
Mar 22 '17 at 5:43
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.
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%2f895492%2fkernel-panic-vfs-cannot-open-root-device-or-unknown-block-error-6%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
1
Caps lock blinking is a sign of kernel panic -- fatal crash of the Linux that runs Ubuntu. Try opening
/etc/default/grubwith a text editor as root and changeGRUB_CMDLINE_LINUX_DEFAULT="splash quiet"toGRUB_CMDLINE_LINUX_DEFAULT="nosplash debug --verbose". That way you can see exactly what's causing the panic during boot. Then run in terminalsudo update-gruband shut it off. When you turn it back on you should see messages about everything the kernel is doing. See what errors you get just before the crash.– darksky
Mar 22 '17 at 1:28
Something about mounting the filesystem: imgur.com/VvPLO88
– Grund
Mar 22 '17 at 1:59