[SOLVED] External Hard Drive not recognized on Debian SID

utanja · 11-06-2013, 06:52 AM

My debian Sid 3.11 kernel does not recognize my 150Gig external Hard Drive formatted for Fat32. (VFat). Cable and drive work properly on my Windows 7 laptop.

jdkaye · 11-06-2013, 07:10 AM

What mount command did you use to mount the device on your file system?
jdk

utanja · 11-06-2013, 08:31 AM

Quote:

Originally Posted by jdkaye

What mount command did you use to mount the device on your file system?
jdk

in the past, it mounted automatically same way the USB flash drives mounted.

I did not need a mount command....

widget · 11-06-2013, 02:07 PM

With the drive connected and powered up;

Code:

lsusb

and, as root;

Code:

fdisk -l

That command run on here, which is not Sid (but I will try it on my Sid install in a while) but Testing gives;

Code:

   Device Boot      Start         End      Blocks   Id  System
/dev/sdh1   *          64     2070527     1035232   83  Linux
/dev/sdh2         2070528    19136511     8532992   83  Linux
/dev/sdh3        19136512    57364479    19113984   83  Linux
/dev/sdh4        57364480    63899647     3267584    b  W95 FAT32

I can read and write it with no problem on this stick.

We need to see if it your external is seen by the system and how it sees it.

Testing is still running 3.10. So I will be checking Sid which is, as you say, running 3.11.

utanja · 11-06-2013, 04:04 PM

Quote:

Originally Posted by widget

With the drive connected and powered up;

Code:

lsusb

and, as root;

Code:

fdisk -l

That command run on here, which is not Sid (but I will try it on my Sid install in a while) but Testing gives;

Code:

   Device Boot      Start         End      Blocks   Id  System
/dev/sdh1   *          64     2070527     1035232   83  Linux
/dev/sdh2         2070528    19136511     8532992   83  Linux
/dev/sdh3        19136512    57364479    19113984   83  Linux
/dev/sdh4        57364480    63899647     3267584    b  W95 FAT32

I can read and write it with no problem on this stick.

We need to see if it your external is seen by the system and how it sees it.

Testing is still running 3.10. So I will be checking Sid which is, as you say, running 3.11.

It is not seeing the external drive.....

andrewthomas · 11-06-2013, 04:25 PM

Quote:

Originally Posted by utanja

It is not seeing the external drive.....
SID[3.11[custom kernel]

May be the problem. No driver.

widget · 11-06-2013, 04:31 PM

Yes, popped over and am on Sid.

I am reading and writing to the stick Fat32 partition.

There are a couple differences from your situation here. One is that this is a stick not an hdd. Second is that this is straight up fat32 and I believe there is some differences between it and Vfat.

I do not think that the long file name capability of Vfat as opposed to fat32 is relevant however.

The stick/hard drive difference may be a problem in comparing our systems.

I need to run down and see if I can get finger printed at the court house (need for a job, not a criminal case) but I have an external drive that could easily be formated as it needs cleaned out anyway. Will whack fat32 on there and see what happens.

One reason I wanted to check here besides the kernel difference was the fact that the testing install has a lot of extra packages installed. Mainly diagnostic but they do have special abilities for reading and detecting file systems that may be over written or corrupted. Thought it could be the reason I have never had this problem.

The fat32 partition is new on the stick. Had a ntfs partition on it under the assumtion that a Windows box could see it on the stick. Appears that is not true so I put this on so I can, hopefully, get an image off a W7 box from the Weed Dept at the court house.

widget · 11-06-2013, 05:23 PM

I find it strange that the external drive is not seen by both those commands.

lsusb usually will see about anything. May just see the firmware giving the manufacturers name but should see a live device.

You do have the package "libdiscover" installed don't you? Standard default install package I am sure.

Check on "udisks" and "udisks2" and "fatattr" while you are at it. The first two should, I think, be installed already. The last may help.

I have a straight fat32 formatted drive. Have never fooled with fat before. Can't seem to get a Vfat format to work. Have dosfftools installed and tried mkfs.vfat and was informed that the command was unknown. Didn't try any further.

As soon as a fat32 format was applied to the drive, however, it came up as mounted automatically in Thunar. Created a folder and copied some .png files to it. They come up fine in Ristretto (image viewer) from there.

What is the output from;

Code:

lsusb

?

andrewthomas · 11-06-2013, 07:20 PM

Quote:

Originally Posted by widget

I find it strange that the external drive is not seen by both those commands.

No kernel driver?

widget · 11-07-2013, 12:52 AM

Quote:

Originally Posted by andrewthomas

No kernel driver?

I find that a bit hard to believe too because it is the same kernel I am on right now.

Been looking around and I came up with this to check mounted drives. This is the result after I dismounted the drive which explains the last entry.

I think I will remount the fat32 drive and see what it says there. May give a clue. This drive, all linux type partitions obviously needs nothing but the kernel.

widget · 11-07-2013, 01:14 AM

Forgot to give the data;

Code:

root@debian:/home/sam#  tail -f /var/log/messages
Nov  6 16:29:44 debian mtp-probe: bus: 7, device: 6 was not an MTP device
Nov  6 16:29:44 debian kernel: [11315.416031] scsi9 : usb-storage 7-3:1.0
Nov  6 16:29:45 debian kernel: [11316.417009] scsi 9:0:0:0: Direct-Access     WDC WD32 00AAJS-00RYA0         PQ: 0 ANSI: 2 CCS
Nov  6 16:29:45 debian kernel: [11316.417246] sd 9:0:0:0: Attached scsi generic sg2 type 0
Nov  6 16:29:45 debian kernel: [11316.417869] sd 9:0:0:0: [sdc] 625142448 512-byte logical blocks: (320 GB/298 GiB)
Nov  6 16:29:45 debian kernel: [11316.418746] sd 9:0:0:0: [sdc] Write Protect is off
Nov  6 16:29:45 debian kernel: [11316.476783]  sdc: sdc1 sdc2 sdc3 sdc4 sdc5 sdc6 sdc7 sdc8
Nov  6 16:29:45 debian kernel: [11316.480075] sd 9:0:0:0: [sdc] Attached SCSI disk
Nov  6 16:29:46 debian kernel: [11317.800782] EXT4-fs (sdc7): mounted filesystem with ordered data mode. Opts: (null)
Nov  6 20:50:49 debian kernel: [26980.592287] usb 7-3: USB disconnect, device number 6

then plugged in and turned on the fat32 drive and this was added to the above;

Code:

Nov  6 23:53:01 debian kernel: [37912.672049] usb 7-3: new high-speed USB device number 7 using ehci-pci
Nov  6 23:53:01 debian kernel: [37912.805816] usb 7-3: New USB device found, idVendor=152d, idProduct=2336
Nov  6 23:53:01 debian kernel: [37912.805822] usb 7-3: New USB device strings: Mfr=1, Product=2, SerialNumber=5
Nov  6 23:53:01 debian kernel: [37912.805824] usb 7-3: Product: JM20336 SATA, USB Combo
Nov  6 23:53:01 debian kernel: [37912.805826] usb 7-3: Manufacturer: JMicron
Nov  6 23:53:01 debian kernel: [37912.805828] usb 7-3: SerialNumber: DA9066672988
Nov  6 23:53:01 debian kernel: [37912.806711] usb-storage 7-3:1.0: USB Mass Storage device detected
Nov  6 23:53:01 debian kernel: [37912.806776] scsi10 : usb-storage 7-3:1.0
Nov  6 23:53:01 debian mtp-probe: checking bus 7, device 7: "/sys/devices/pci0000:00/0000:00:1a.7/usb7/7-3"
Nov  6 23:53:01 debian mtp-probe: bus: 7, device: 7 was not an MTP device
Nov  6 23:53:02 debian kernel: [37913.804953] scsi 10:0:0:0: Direct-Access     WDC WD50 00AVCS-632DY1         PQ: 0 ANSI: 2 CCS
Nov  6 23:53:02 debian kernel: [37913.805717] sd 10:0:0:0: Attached scsi generic sg2 type 0
Nov  6 23:53:02 debian kernel: [37913.806704] sd 10:0:0:0: [sdc] 975724592 512-byte logical blocks: (499 GB/465 GiB)
Nov  6 23:53:02 debian kernel: [37913.807979] sd 10:0:0:0: [sdc] Write Protect is off
Nov  6 23:53:02 debian kernel: [37913.896096]  sdc: sdc1
Nov  6 23:53:02 debian kernel: [37913.899451] sd 10:0:0:0: [sdc] Attached SCSI disk

Have not been able to figure out what the heck ehci-pci is.

Edit;
from "lspci";

Code:

00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 02)

beats me.

Looks like the;
Linux debian 3.11-1-amd64 #1 SMP Debian 3.11.6-2 (2013-11-01) x86_64 GNU/Linux

kernel is handling it fine.

One thing that turned up in my research was a post by someone using the 3.10 kernel that had the package "usbmount" installed, removed it and had no more problem mounting the usb drive. That package is supposed to mount usb devices, but not hdds.

I checked and I do not have it installed. Checking that may be a good idea.

273 · 11-07-2013, 01:28 AM

Quote:

Originally Posted by utanja

My debian Sid 3.11 kernel does not recognize my 150Gig external Hard Drive formatted for Fat32. (VFat). Cable and drive work properly on my Windows 7 laptop.

If you are using a custom kernel as your signature suggests have you tried booting one of the Debian-provided 3.11 kernels? That would narrow things down and I know I've had problems with automounting of my optical drive, for example, with a kernel I compiled until I compiled using the correct confuguration.

utanja · 11-07-2013, 07:49 AM

well I will check out all of the suggestions tonight when I get home.....I remotely check to see if I had usbmount installed and I do not have it....I will add it and see what happens....I did try using the debian stack kernel and still no success.

utanja · 11-07-2013, 04:25 PM

Quote:

Originally Posted by utanja

well I will check out all of the suggestions tonight when I get home.....I remotely check to see if I had usbmount installed and I do not have it....I will add it and see what happens....I did try using the debian stock kernel and still no success.

OK....problem solved......the usb ports on the front panel only seem to work with USB sticks and the SanDisk multicard reader....when I plugged the cable into the USB ports at the rear of the case, these are directly into the motherboard, everything works fine....

Thanks for the help guys....

widget · 11-07-2013, 04:46 PM

That is just great.