Disappearing External Hard Drive.

[Just17]

I don't see the point in changing the drive until you know whether it is your install causing the problem or the drive.

[muungwana]

what is the output of the following command?

lsmod | grep usb

The link below shows others also have the same problem with the kind of drive you have and they solved the problem by blacklisting uas module from loading.

https://bugs.launchpad.net/xyz/+source/linux/+bug/901215

replace xyz with the brown distro name to see the discussion around the problem

Try to do the same and see if it will work.

open the text file "/etc/modprobe.d/blacklist" with root's privileges and the add the following line and restart and check if the problem is still there.

blacklist uas

[longtom]

Maybe I misread that ... but you say it works in Windows.  I had your problem before and solved it by plugging it in in Windows and dismount it properly using the dismount icon in the windows toolbar (little green arrow).

After that drive was readable again in Linux.

[wobf58]

Blacklisting uas isnt working. 

Here is the output of lsmod with starting PCLOS and then plug in the Hitachi drive

lsmod | grep usb 
usb_storage            35100  0
snd_usb_audio          70727  0
snd_usbmidi_lib        15440  1 snd_usb_audio
snd_rawmidi            15287  1 snd_usbmidi_lib
btusb                   9865  2
bluetooth              51698  9 rfcomm,sco,bnep,l2cap,btusb
snd_hwdep               4820  2 snd_usb_audio,snd_hda_codec
snd_pcm                60702  5 snd_usb_audio,snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd                    43189  22 snd_usb_audio,snd_usbmidi_lib,snd_rawmidi,snd_hda_codec_idt,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_pcm,snd_timer,snd_mixer_oss
scsi_mod              150584  6 usb_storage,sr_mod,sg,firewire_sbp2,libata,sd_mod
usbhid                 31331  1 hid_logitech
hid                    63565  2 hid_logitech,usbhid
usbcore               118087  9 usb_storage,snd_usb_audio,snd_usbmidi_lib,btusb,uhci_hcd,ohci_hcd,ehci_hcd,usbhid

Here is the output of lsmod with starting PCLOS, plug in the Hitachi drive, start Virtualbox with Windows XP, check in the drive and uncheck it right after that, then it will pop up immediately in PCLOS

[snoopy@localhost ~]$ lsmod | grep usb
usb_storage            35100  1
snd_usb_audio          70727  0
snd_usbmidi_lib        15440  1 snd_usb_audio
snd_rawmidi            15287  1 snd_usbmidi_lib
btusb                   9865  2
bluetooth              51698  9 rfcomm,sco,bnep,l2cap,btusb
snd_hwdep               4820  2 snd_usb_audio,snd_hda_codec
snd_pcm                60702  5 snd_usb_audio,snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd                    43189  22 snd_usb_audio,snd_usbmidi_lib,snd_rawmidi,snd_hda_codec_idt,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_pcm,snd_timer,snd_mixer_oss
scsi_mod              150584  6 usb_storage,sr_mod,sg,firewire_sbp2,libata,sd_mod
usbhid                 31331  1 hid_logitech
hid                    63565  2 hid_logitech,usbhid
usbcore               118087  9 usb_storage,snd_usb_audio,snd_usbmidi_lib,btusb,uhci_hcd,ohci_hcd,ehci_hcd,usbhid

[wobf58]

The dismounting in Windows isn't working either.  But its good that I at least got it got work in Linux with the detour of Virtualbox Windows.  I will install PCLOS on a spare partition and then plug it in.  I am just curious if it will work then.  If not I will reformat it and then will try.

[Yankee]

There is a program called testdisk.   It's probably already
installed.   Type testdisk in root terminal and select the
drive to test.   Could be info there what's happening.

Also, with the drive unplugged try typing hald in root
terminal.   Then plug in the drive, it should automount
or manually mount then.   My machine sometimes requires
that when I work with hard drives excessively.

Have a good one.

FF

[wobf58]

I have used testdisk but don't saw anything unusual.  Test came back good.  I have formatted the drive with KDE partition manager with NTFS and then with EXT2.  After that same thing, had to use Virtualbox to get it mounted in PCLOS.  Now I am formatting it with Win7.  Probably there will be no change after that.  I just don't understand why it gets mounted in PCLOS immediately after I have mounted and unmounted with Virtualbox using WinXP.

[muungwana]

A lot of people who have the same or similar type of hard drive seem to have the same problem you are having and these doesnt seem to be a known solution to the problem.

Some posts suggests blocking a particular module as it works for them but did not work for you.This could be due to using two different versions of kernels.

Those drives are to the most part,"bleeding edge" and hence using a most recent kernel should be one of the first thing to do when trying to make it to work.

Breaking the drive into multiple partitions each less than 1TB may also help.

[wobf58]

Great idea with partitioning.  I will try that and let you know the outcome.  I also found this article, actually from Hitachi

\http://www.hitachigst.com/internal-drives/above-2tb/

[wobf58]

I partitioned the drive in 3 equal partitions.  One formatted with NTFS and two with EXT2.  Still same issue.  After starting PCLOS, its not showing up in Dolphin.  Same procedure like always. After starting XP in VirtualBox and mounting/dismounting, it pops up in PCLOS

[muungwana]

how about trying a more recent kernel?

Below post says more recent ones are on their way, you can try it to see if the problem goes away or if its still there.

The kernel is still in testing phase so dont take it too serious and your test on it could help make it more functional when it gets released.

http://www.pclinuxos.com/forum/index.php/topic,104787.0/topicseen.html

[Yankee]

Confusing and very technical failure here.

I would try testdisk again, test completely, then click only
delete the partition table option.  Then delete everything
and create several 100 GB partitions.    ext4 most common.

If it doesn't automount, grab your receipt and exchange for
a different drive.

Anyone disagree ?


FF

[muungwana]

Ferdes Fides,

If you look at the logs he provided earlier(given below), you will see that when the drive is attached,linux sees the drive and then it sees the partitions in the drive, when this happens,the drive is usable as expected.

For some reason,the drive is redetected and partitions in it are not seen the second time around.

Google the drive you will see other people are having problems with it.

This suggests the problem is with interaction btw the drive and linux,possible reason being it uses technology the kernel version he is using does not fully support.

What do you think the problem is that can be solved by running testdisk?

usb 2-3: SerialNumber: 2315460098394C02   <--- drive gets detected when attached
scsi8 : usb-storage 2-3:1.0
scsi 8:0:0:0: Direct-Access              USB 2.0          5.00 PQ: 0 ANSI: 2
sd 8:0:0:0: Attached scsi generic sg2 type 0
sd 8:0:0:0: [sdb] 4063232 512-byte logical blocks: (2.08 GB/1.93 GiB)
sd 8:0:0:0: [sdb] Write Protect is off
sd 8:0:0:0: [sdb] Mode Sense: 0b 00 00 08
sd 8:0:0:0: [sdb] Assuming drive cache: write through
sd 8:0:0:0: [sdb] Assuming drive cache: write through
 sdb: sdb1    <----- partition in the drive is correctly detected
sd 8:0:0:0: [sdb] Assuming drive cache: write through
sd 8:0:0:0: [sdb] Attached SCSI removable disk
usb 2-3: USB disconnect, address 5  <---- drive get disconnected for some reason
usb 2-3: new high speed USB device using ehci_hcd and address 6 <-- drive get redetected
usb 2-3: New USB device found, idVendor=4971, idProduct=1013
usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-3: Product: Touro Desk Pro
usb 2-3: Manufacturer: Hitachi GST
usb 2-3: SerialNumber: 03100110427280002766
scsi9 : usb-storage 2-3:1.0
<----- partitions do not get detected for some reason

[Just17]

This suggests the problem is with interaction btw the drive and linux,possible reason being it uses technology the kernel version he is using does not fully support.

Possibly an incompatibility with the drive controller in the external box?

At this point I would be inclined to replace it with a different device ........

[Yankee]

What do you think the problem is that can be solved by running testdisk?

Plug n' play.   Downward and Upward compatibility.

If my industry standard system can't read a "hybrid" hard drive well........
I test all of my drives with testdisk as I trust that program for Linux
before usage or troubleshooting.

Perhaps its one of those 'Windows" hard drives.   Might have a Windows
uRDrive program nestled in it's MBR somewhere, which runs upon mounting,
can't be read in Linux, and can't delete.   That can fool a Linux system.
So I try to delete it.

An Intel standard hard drive should automount then in Linux.   Too much trouble,
I'd get a Seagate or a Western Digital, probably get a 5 year warranty as well.

At least with testdisk I know that Linux isn't broke the drive is or vice-versa.   
I think a "Windows" drive might be the problem at this point, logs considered.

All inputs considered, of course.   I hate to take back a TB hard drive as well.
Plug in something else and relax  !    Hmmm  ?


FF