How can you get a Seagate USB 160 GB drive to mount?

[Carlos Alberto Alves]

Richard England wrote:
> Karl Larsen wrote:
>> Richard England wrote:
>>> Richard England wrote:
>>>> Tim wrote:
>>>>> On Fri, 2007-08-10 at 21:56 -0700, Richard England wrote:
>>>>>  
>>>>>> The drive had a label of "SEAGATE". I changed it, just to be certain,
>>>>>> to "USB_SEAGATE" and remove the /etc/fstab entry for /dev/sdc1.
>>>>>> Setting /etc/mtools.conf  and using mlabel as Tim and Matthew
>>>>>> suggested, worked fine.
>>>>>>
>>>>>> Upon unplugging and replugging, however,I had the same results. No 
>>>>>> desktop icon, no mount.     
>>>>>
>>>>> How are your "removable drives and media" preferences set?  That's its
>>>>> title in Gnome, KDE will probably have something similar.  I can't
>>>>> remember whether you use one of them.
>>>>>
>>>>>   
>>>>
>>>> I am using Gnome:
>>>>
>>>> Removable Drive and Media Preferences are set to allow the following 
>>>> for
>>>> "Removable Storage"
>>>>  Mount removable drives when hot-plugged
>>>>  Mount removable media when inserted
>>>>  Browse removable media when inserted
>>>>
>>>> "Blank CD and DVD Disks"
>>>>  {nothing selected]
>>>>
>>>> ~~R
>>>>
>>>>
>>>
>>> Whatever is going on with this Seagate USB drive is NOT new with F7.
>>> I hooked it up to an FC6 machine and had the same results, no desktop 
>>> icon, no mount.
>>>
>>> The system knows about the device, however.
>>>
>>> From /var/log/messages
>>>
>>> Aug 12 16:32:35 poirot kernel: usb 1-2: new full speed USB device 
>>> using ohci_hcd and address 6
>>> Aug 12 16:32:42 poirot kernel: usb 1-2: configuration #1 chosen from 
>>> 1 choice
>>> Aug 12 16:32:43 poirot kernel: Initializing USB Mass Storage driver...
>>> Aug 12 16:32:43 poirot kernel: scsi0 : SCSI emulation for USB Mass 
>>> Storage devices
>>> Aug 12 16:32:43 poirot kernel: usbcore: registered new interface 
>>> driver usb-storage
>>> Aug 12 16:32:43 poirot kernel: USB Mass Storage support registered.
>>> Aug 12 16:32:49 poirot kernel: scsi 0:0:0:0: Direct-Access     
>>> ST316002 3A               8.01 PQ: 0 ANSI: 0
>>> Aug 12 16:32:49 poirot kernel: sd 0:0:0:0: [sda] 312581808 512-byte 
>>> hardware sectors (160042 MB)
>>> Aug 12 16:32:49 poirot kernel: sd 0:0:0:0: [sda] Write Protect is off
>>> Aug 12 16:32:49 poirot kernel: sd 0:0:0:0: [sda] Assuming drive 
>>> cache: write through
>>> Aug 12 16:32:49 poirot kernel: sd 0:0:0:0: [sda] 312581808 512-byte 
>>> hardware sectors (160042 MB)
>>> Aug 12 16:32:49 poirot kernel: sd 0:0:0:0: [sda] Write Protect is off
>>> Aug 12 16:32:49 poirot kernel: sd 0:0:0:0: [sda] Assuming drive 
>>> cache: write through
>>> Aug 12 16:32:49 poirot kernel:  sda: sda1
>>> Aug 12 16:32:49 poirot kernel: sd 0:0:0:0: [sda] Attached SCSI disk
>>> Aug 12 16:32:49 poirot kernel: sd 0:0:0:0: Attached scsi generic sg0 
>>> type 0
>>>
>>>
>>>
>>> $ /sbin/lsusb
>>> Bus 001 Device 006: ID 0bc2:0502 Seagate RSS LLC
>>> Bus 001 Device 001: ID 0000:0000 Bus 002 Device 001: ID 0000:0000
>>>
>>>
>>> It still sounds like a udev/hal  issue.
>>>
>>> I've got
>>>  idVendor           0x0bc2 Seagate RSS LLC
>>>  idProduct          0x0502
>>>
>>> Now I guess it means trying figure out how to automate the mount, 
>>> etc.  Tips, starting points, howtos, anyone?
>>>
>>> ~~R
>>>
>>    I would never again own a Seagate hard drive. A question is, did 
>> Seagate make the hardware that gets the drive to be a USB type? I have 
>> a 10GB old haed drive in a box from China that costs $19.00 and with 
>> the latest Updates it works great on F7.
>>
>>    If you have all the Updates in your F7 the USB stuff is working 
>> fine. Your hardware should be found and mounted and a panel should 
>> appear that tells you what is on the device.
>>
>>    If your hardware doesn't work find a friend with Windows and see if 
>> it works there. If it does bring it back. Something is still broke in F7.
>>
> 
> As I stated at the start of this thread, the drive can be mounted 
> manually.  This is NOT a hardware issue.  When mounted manually it works 
> fine in both FC6 and F7.
> The problem is that it is not auto-detected and mounted like other 
> devices are in FC6 and F7
> 
> Yes it works in Windows....
> 
> If it's broke [sic] in F7, then it's broken in FC6 as well....  I don't 
> think this is a bug as much as it is a device that has not been 
> encountered yet, and whose configuration is not yet know by HAL.  I've 
> not had the time to learn/research enough about HAL. Other fires are 
> getting in the way.  If any one can give me a starting point or an 
> example to study, it would be appreciated.
> 
> If I decipher this then I'll submit an RFE.
> 
> ~~R
> 
Have just bought and install a new Seagate SATA II 160Gb HD with no 
problems. I used fdisk to partition, format and create a ext3 file 
system. I manually added a line in fstab just like the one below...
/dev/sda1	/mnt/sata160	ext3	defaults        0 0
My system is installed in an IDE Seagete 40Gb HD.
HTH,
-- 
**********************************************
* Carlos Alberto Alves                       *
* Child Neurologist                          *
* Systems Analyst/ASUS Certified Professional*
* Rio de Janeiro, Brazil                     *
* Skype: carlos-aa                           *
* mailto:drcaa at click21.com.br                *
* mailto:drcaa at predialnet.com.br             *
**********************************************