Ubuntu

Kernel Panic during boot cannot open root device

Reported by Tom McAnnally on 2007-08-12
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Undecided
Unassigned

Bug Description

Installed Ubuntu x64 Feisty
Could not boot unless picking "recovery mode"
After booting to single and continuing everything would work fine with no changes
Updated OS to latest patches made no difference
Tried many things but nothing worked
Narrowed it down - simply adding vga=1 to kernel options causes it to work now
I wouldn't think that would have any effect, but removing this causes problem to come back

Actual error received was

Cannot open root device or unknown block
please append a correct "root" boot option
not syncing VFS unable to mount fs on unknown block(0,0)

Ralph Janke (txwikinger) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description does not yet have enough information.

Could you please check if this problem still occurs in the newest hardy kernel.

Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
 1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
 2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
 3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.
 4. Please run the command "cat /proc/version_signature > version.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at http://wiki.ubuntu.com/KernelTeamBugPolicies. Thanks in advance!

Changed in linux-source-2.6.20:
status: New → Incomplete

Sorry, but I am not running UBUNTU at the moment. I stopped trying
months ago due to this bug. It should be easy for you to repeat given
the information I already provided. Good luck with that.

-Tom

On Thu, Mar 6, 2008 at 2:24 PM, Ralph Janke <email address hidden> wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Unfortunately we can't fix it, because your description
> does not yet have enough information.
>
> Could you please check if this problem still occurs in the newest hardy
> kernel.
>
> Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
> 1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
> 2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
> 3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.
> 4. Please run the command "cat /proc/version_signature > version.log" and attach the resulting file "lspci-vvnn.log" to this bug report.
>
> For your reference, the full description of procedures for kernel-
> related bug reports is available at
> http://wiki.ubuntu.com/KernelTeamBugPolicies. Thanks in advance!
>
> ** Changed in: linux-source-2.6.20 (Ubuntu)
> Status: New => Incomplete
>
>
> --
> Kernel Panic during boot cannot open root device
> https://bugs.launchpad.net/bugs/131919
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Never tell people how to do things. Tell them what to do and they will
surprise you with their ingenuity.
George Patton

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Sorry, but I am not running UBUNTU at the moment. I stopped trying
months ago due to this bug. It should be easy for you to repeat given
the information I already provided. Good luck with that.

-Tom

On Fri, Aug 29, 2008 at 5:50 AM, Leann Ogasawara <email address hidden> wrote:
> The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
> upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
> appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
> There are one of two ways you should be able to test:
>
> 1) If you are comfortable installing packages on your own, the linux-
> image-2.6.27-* package is currently available for you to install and
> test.
>
> --or--
>
> 2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer
> 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4.
> Please watch http://www.ubuntu.com/testing for Alpha5 to be announced.
> You should then be able to test via a LiveCD.
>
> Please let us know immediately if this newer 2.6.27 kernel resolves the
> bug reported here or if the issue remains. More importantly, please
> open a new bug report for each new bug/regression introduced by the
> 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please
> specifically note if the issue does or does not appear in the 2.6.26
> kernel. Thanks again, we really appreicate your help and feedback.
>
> ** Tags added: cft-2.6.27
>
> --
> Kernel Panic during boot cannot open root device
> https://bugs.launchpad.net/bugs/131919
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Never tell people how to do things. Tell them what to do and they will
surprise you with their ingenuity.
George Patton

This is likely hardware specific and since we are unable to reproduce the issue, we will not be able to debug/test any fixes without your help. I'll close this report for now. If you do happen to test Ubuntu in the future, please let us know your results. Thanks.

Changed in linux:
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers