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.
*** This bug is a duplicate of bug 116996 ***
https://bugs.launchpad.net/bugs/116996
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
*** This bug is a duplicate of bug 116996 ***
https://bugs.launchpad.net/bugs/116996
Marking as duplicate of #116996.
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Unconfirmed = Rejected
** This bug has been marked a duplicate of bug 116996
SATA disk is in PATA mode with
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
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.
--
Hard drives not recognized after kernel upgrade to 2.6.20-16-386.
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: .:
ricardisimo:
Ah my mistake. That should have been
sudo umount /media/storage
sudo mount -U bfe37834-a8da-4f43-81a7-c67928f282e0 /media/storage
--
Hard drives not recognized after kernel upgrade to 2.6.20-16-386.
https://bugs.launchpad.net/bugs/117706
You received this bug notification because
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
--
Hard drives not recognized after kernel upgrade to 2.6.20-16-386.
https://bugs.launchpad.net/bugs/117706
You received this bug notification because you are a
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.
--
Hard drives not
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:
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
ricardisimo:
Unlucky, I really did mean -15 : )
--
Hard drives not recognized after kernel upgrade to 2.6.20-16-386.
https://bugs.launchpad.net/bugs/117706
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
Here's my fstab:
# /etc/fstab: static file system information.
#
# file system mount point type options dump pass
proc/proc procdefaults0 0
# /dev/hda2 -- converted during upgrade to edgy
UUID=2ec78ab2-2fe6-4211-abbb-a22984e9648b / ext3
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).
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
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?
--
Hard drives not recognized after kernel upgrade to 2.6.20-16-386.
https://bugs.launchpad.net/bugs/117706
You received this bug notification because you
16 matches
Mail list logo
