Ubuntu10.10: kernel 2.6.35-22 cannot find intern hard drives.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu |
New
|
Undecided
|
Unassigned |
Bug Description
I made an upgrade from Ubuntu 10.04 to Ubuntu 10.10. The upgrade went well, no error or such, but when time went to reboot, it stucks just after Grub.
I can still boot with the older kernels (2.6.32-25).
The error message with the recent kernel (2.6.35-22) is:
"udevd-work[173]: `/sbin/modprobe -bv pci:<lots of letters and digits>` unespected exit with status 0x0009
Gave up waiting for root device. Common problem:
-Boot args (cat /proc/cmdline)
-Check root delay
-Check root
-Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/disk/
In /dev (with the newest kernel), no sda or sdb is present, and the "by-uuid" folder is empty.
Following this link : http://
Feel free to ask me more questions or to request more information if that may help you to find the source and a way to correct this.
Thank you very much for all your work.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: udisks 1.0.1+git20100614-3
ProcVersionSign
Uname: Linux 2.6.35-
NonfreeKernelMo
Architecture: i386
Date: Tue Oct 12 14:46:52 2010
MachineType: Dell Inc. Precision WorkStation T3500
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
PATH=(custom, no user)
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: udisks
Symptom: storage
Title: Internal hard disk partition cannot be mounted manually
dmi.bios.date: 04/12/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 0XPDFK
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Precision WorkStation T3500
dmi.sys.vendor: Dell Inc.
tags: | added: lucid2maverick |
I had a similar effect after upgrading kubuntu from 10.04 to 10.10.
After the first reboot I found, that the kernel reported my former /dev/sda as /dev/sdf and /dev/sdb as /dev/sde. Because I had all filesystems exept /home mounted via UUID, I got the system running but without /home so I could fix it easily by changeing the entry in fstab to mounting by UUID also for the /home filesystem.
To me it seems there was introduced a bug into the kernel changeing the startvalue for enumerating the attached disks, at least for SATA.