Ubuntu

Hard drives not recognized after kernel upgrade to 2.6.20-16-386.

Reported by ricardisimo on 2007-05-30
4
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: linux-image-2.6.20-16-386

If I click on "Places", My "Storage" drive is not immediately recognized (very much like my Windows partition on the Master), and not only that, but even after i click on it, it is no longer "Storage" but rather "disk-1" (the Windows partition being "disk").

This wouldn't be a serious problem but for the confusion it causes apps like Pan, which have set paths they follow for saving new post attachments, etc. With that path renamed it downloads, searches, can't find, and dumps. Moves on to the next attachment and repeats. BIG waste of bandwidth.

Thanks in advance for any help.

P.S. - The comp at work had no such problems. On the other hand, it is Ubuntu-only... could the Windows partition be the cause of the problem?

Sitsofe Wheeler (sitsofe) wrote :

Thank you for your bug report.

ricardisimo:
Can you add the contents of your
/etc/fstab
file and add the output of
lspci
to this bug report?

ricardisimo (ricardisimo) wrote :
Download full text (6.2 KiB)

Here's my fstab:
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/hda2 -- converted during upgrade to edgy
UUID=2ec78ab2-2fe6-4211-abbb-a22984e9648b / ext3 defaults,errors=remount-ro 0 1
# /dev/hda5 -- converted during upgrade to edgy
UUID=e34f029b-7b4a-4def-badb-fa40de54314a none swap sw 0 0
/dev/sdb1 /media/storage ext3 defaults 0 0
/dev/hdc /media/cdrom0 udf,iso9660 user,noauto 0 0

**********

And here's lspci -v:
00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02)
        Subsystem: ASUSTeK Computer Inc. Unknown device 8103
        Flags: bus master, fast devsel, latency 0
        Memory at f8000000 (32-bit, prefetchable) [size=64M]
        Capabilities: <access denied>

00:01.0 PCI bridge: Intel Corporation 82865G/PE/P PCI to AGP Controller (rev 02) (prog-if 00 [Normal decode])
        Flags: bus master, 66MHz, fast devsel, latency 64
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
        I/O behind bridge: 0000c000-0000cfff
        Memory behind bridge: fe900000-fe9fffff
        Prefetchable memory behind bridge: d7f00000-f7efffff

00:1d.0 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #1 (rev 02) (prog-if 00 [UHCI])
        Subsystem: ASUSTeK Computer Inc. P5P800-MX Mainboard
        Flags: bus master, medium devsel, latency 0, IRQ 17
        I/O ports at ef00 [size=32]

00:1d.1 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #2 (rev 02) (prog-if 00 [UHCI])
        Subsystem: ASUSTeK Computer Inc. P5P800-MX Mainboard
        Flags: bus master, medium devsel, latency 0, IRQ 18
        I/O ports at ef20 [size=32]

00:1d.2 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #3 (rev 02) (prog-if 00 [UHCI])
        Subsystem: ASUSTeK Computer Inc. P5P800-MX Mainboard
        Flags: bus master, medium devsel, latency 0, IRQ 19
        I/O ports at ef40 [size=32]

00:1d.3 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #4 (rev 02) (prog-if 00 [UHCI])
        Subsystem: ASUSTeK Computer Inc. P5P800-MX Mainboard
        Flags: bus master, medium devsel, latency 0, IRQ 17
        I/O ports at ef80 [size=32]

00:1d.7 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02) (prog-if 20 [EHCI])
        Subsystem: ASUSTeK Computer Inc. P5P800-MX Mainboard
        Flags: bus master, medium devsel, latency 0, IRQ 20
        Memory at febffc00 (32-bit, non-prefetchable) [size=1K]
        Capabilities: <access denied>

00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c2) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0
        Bus: primary=00, secondary=02, subordinate=02, sec-latency=64
        I/O behind bridge: 0000d000-0000dfff
        Memory behind bridge: fea00000-feafffff

00:1f.0 ISA bridge: Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC Interface Bridge (rev 02)
        Flags: bus master, medium devsel, latency 0

00:1f.1 IDE interface...

Read more...

Sitsofe Wheeler (sitsofe) wrote :

ricardisimo:
In your /etc/fstab you have "/dev/sdb1 /media/storage". Assuming /media/storage is what is not turning up, you are proably best off working out what the UUID for the missing partition, and replacing /dev/sdb1 with UUID=(the uuid you have found that represents /media/storage). Assuming the uuid is correct
sudo mount -a
will try and add all devices mentioned in /etc/fstab. I believe you can use (for example)
sudo vol_id /dev/hda1
to find out the UUID of /dev/hda1 . What is /media/storage by the way? Is it a USB disk or is it a SATA/PATA internal disk?

Your lspci informs us that you have an ICH5 IDE disk controller so we can tell you are seeing fallout due to the disabling of the SATA as described in Bug #116996 which will have changed /dev/sd?? devices into /dev/hd?? ...

ricardisimo (ricardisimo) wrote :

Yes, /media/storage is indeed an internal hard drive. I trust that your advice is accurate, but being rather unsure of my own abilities, I'm simply loading the previous kernel, 2.6.20-15-386, for the time being. If it is important for me to attempt what you are recommending, then please say so and I will go ahead and do it. Otherwise, I will wait for the patch or successive kernel upgrade.

I gather that uninstalling the most recent kernel is no simple matter, certainly not as easy as removing previous ones. Or is it?

Sitsofe Wheeler (sitsofe) wrote :

ricardisimo:
It's far from important but it would be helpful. My steps may be too complicated and if so I will try and break them down into safer more manageable units. The first and simplest test to do (which will not make any permanent change that will last over a reboot) is the following:
Under 2.6.20-15-386:
1. Boot as usual.
2. Start a terminal.
3. sudo -s vold_id /dev/sdb1
This will tell us the UUID of that partition. Ensure you don't have any windows or programs open that are using /media/storage then do this:
4. sudo umount /dev/sdb1 .
(this will try and unmount the storage device if nothing is using it. If you get an error here just stop and don't go any further. No changes will have been done)
5. sudo mount -U <ID_FS_UUID found earlier>
(this should add the storage device back. See if
ls /media/storage
shows what you are expecting)
6. Report what the result was back here. No permanent change will have been made and no files should have been edited. Do not do any more than this initially.

There's no need to uninstall the new kernel. Just leave it be for now.

ricardisimo (ricardisimo) wrote :

I'm assuming you meant -16- and not -15-. Here's what I get:

:~$ sudo vol_id /dev/hda1
ID_FS_USAGE=filesystem
ID_FS_TYPE=ntfs
ID_FS_VERSION=3.1
ID_FS_UUID=FEF47B4DF47B0765
ID_FS_LABEL=
ID_FS_LABEL_SAFE=
:~$ sudo umount /dev/sdb1
umount: /dev/sdb1: not found

... and that's where I stopped, for now at least. Not sure if that qualifies as an error message. I am eager to help in whatever meager way I can, so please feel free to ask more.

Sitsofe Wheeler (sitsofe) wrote :

ricardisimo:
Unlucky, I really did mean -15 : )

ricardisimo (ricardisimo) wrote :

Then I think there might be a problem...

:~$ uname -r
2.6.20-15-386
:~$ sudo vol_id /dev/hda1
Password:
/dev/hda1: error open volume

Sitsofe Wheeler (sitsofe) wrote :

ricardisimo:
Check my comment (https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/117706/comments/5 ) again:
3. sudo -s vold_id /dev/sdb1
(sdb not hda1...). My references to hda1 in earlier comments were meant just as examples. Sorry for any confusion.

ricardisimo (ricardisimo) wrote :

No, my apologies... working too much lately, and my brain isn't working. Here it is:

:~$ sudo vol_id /dev/sdb1
ID_FS_USAGE=filesystem
ID_FS_TYPE=ext3
ID_FS_VERSION=1.0
ID_FS_UUID=bfe37834-a8da-4f43-81a7-c67928f282e0
ID_FS_LABEL=
ID_FS_LABEL_SAFE=

Then...

:~$ sudo umount /dev/sdb1 .
umount: .: not mounted

And finally...

:~$ sudo mount -U bfe37834-a8da-4f43-81a7-c67928f282e0
mount: cannot find /dev/disk/by-uuid/bfe37834-a8da-4f43-81a7-c67928f282e0 in /etc/fstab

Sitsofe Wheeler (sitsofe) wrote :

ricardisimo:
Ah my mistake. That should have been
sudo umount /media/storage
sudo mount -U bfe37834-a8da-4f43-81a7-c67928f282e0 /media/storage

ricardisimo (ricardisimo) wrote :

From the top...

:~$ uname -r
2.6.20-15-386

:~$ sudo lshw
*-blah, blah, blah...
*-disk:1
                blah, blah, blah...
                logical name: /dev/sdb

:~$ sudo vol_id /dev/sdb1
ID_FS_USAGE=filesystem
ID_FS_TYPE=ext3
ID_FS_VERSION=1.0
ID_FS_UUID=bfe37834-a8da-4f43-81a7-c67928f282e0
ID_FS_LABEL=
ID_FS_LABEL_SAFE=

and then...

:~$ sudo umount /media/storage

No terminal output, but when I checked "Places" the "storage" drive was gone. Finally...

:~$ sudo mount -U bfe37834-a8da-4f43-81a7-c67928f282e0 /media/storage

Again, no output, but when I checked, "storage" had returned. "sudo mount -a" also works just fine. Where do I go from here? Thanks again for all of your help and interest in my problem.

Sitsofe Wheeler (sitsofe) wrote :

ricardisimo:
1. Back up/make a copy of /etc/fstab .
2. Edit /etc/fstab so that
/dev/sdb1
reads
UUID=bfe37834-a8da-4f43-81a7-c67928f282e0
save the change.
3. Reboot and see whether /media/storage is available from boot.

ricardisimo (ricardisimo) wrote :

Done. Excellent. I cannot thank you enough. I believe I added that drive after upgrading to Feisty, and the method I learned did not call for inserting UUIDs. I will make sure to repost to that thread to inform everyone that UUIDs are no longer optional as of 2.6.20-16-386. Mnay thanks once again.

Sitsofe Wheeler (sitsofe) wrote :

ricardisimo:
Thank you for following up on this. You may be interested to read https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2007-June/001061.html (and possibly the replies) which takes a similar stance to yours.

Thanks for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #116996 and is being marked as such. Please feel free to report any other bugs you may find.

Sitsofe Wheeler (sitsofe) wrote :

Marking as duplicate of #116996.

Changed in linux-source-2.6.20:
status: Unconfirmed → Rejected
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers