Ubuntu

"No block devices found" problem is really blocking

Bug #393776 reported by gadLinux
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

The problem reported as "No block devices found" is really a *BLOCKING* problem that not only makes the system unusable but may cause loss of information as the RAID-0 RAID-1 systems are not correctly recognized.

I think this problem MUST be corrected as is a problem in the Ubuntu way of managing the initrd boot file.

People is thinking about switching distribution because this bug. As makes the system unbootable.

Do questions and you will be answered about this bug. But please, solve it ASAP.

Currrent system info, but also affects intrepid ibex.
-----

Description: Ubuntu karmic (development branch)
Release: 9.10

Tags: karmic
Revision history for this message
nbarger (nbarger) wrote :

I do believe this is the same bug which is affecting me when trying to install Karmic from CD from the July 13 build. I will be happy to supply any logs or outputs needed to help solve this problem.

Revision history for this message
Philip Muškovac (yofel) 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 didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures.
At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks!

When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Changed in ubuntu:
status: New → Incomplete
Revision history for this message
Philip Muškovac (yofel) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

tags: added: karmic
Revision history for this message
gadLinux (gad-aguilardelgado) wrote :

Yes I'm sorry I lost track of this bug... Too many fronts open.

The main cause was solved cause raid is now recognized. I think it was missing module in the initial ramdisk.
I recently posted more information about this. I think it can be related. I switched to Lucid to see if it was a software problem.

https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/534743

I think that dmraid is causing all this trouble. All my systems are suffering of Raid problems when booting.

So I suggest to close this one and follow the but #534743 as told above.

Revision history for this message
Philip Muškovac (yofel) wrote :

Closing this bug then, thanks for the feedback.

Changed in ubuntu:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.