Auto-mount external 2.0 TB (usb 3.0) [SOLVED]

[shirish]

Hi all,
I bought a new external HDD - a Seagate 2 TB (actually 1.8 TB) but am unable to mount it. The drive is USB 3.0 while the ports on my system are USB 2.0 but that is NOT the issue. I am able to see the HDD without an issue on the CLI. I am on Jessie 64-bit.

Code: Select all

$ lsusb
Bus 005 Device 003: ID 0bc2:ab24 Seagate RSS LLC 
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

As can be seeen the device ID 0bc2:ab24 has been taken by Seagate

then ran fdisk to see if the new external HDD can be seen. That shows up :-

Code: Select all

$ sudo fdisk -l

Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xc5f7c5f7

Device     Boot      Start        End    Sectors   Size Id Type
/dev/sda1               63  102398309  102398247  48.8G  7 HPFS/NTFS/exFAT
/dev/sda2        102398371 1953523711 1851125341 882.7G  f W95 Ext'd (LBA)
/dev/sda5        102398373  204796619  102398247  48.8G  7 HPFS/NTFS/exFAT
/dev/sda6  *     204797952  595421183  390623232 186.3G 83 Linux
/dev/sda7        595423232  790732799  195309568  93.1G 83 Linux
/dev/sda8        790734848 1943076863 1152342016 549.5G 83 Linux
/dev/sda9       1943078912 1953523711   10444800     5G 82 Linux swap / Solaris

Partition 2 does not start on physical sector boundary.

Partition 3 does not start on physical sector boundary.

Partition 6 does not start on physical sector boundary.

Disk /dev/sdb: 1.8 TiB, 2000398933504 bytes, 3907029167 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x1bc6b3bc

Device     Boot      Start        End    Sectors   Size Id Type
/dev/sdb1             2048  952322047  952320000 454.1G  7 HPFS/NTFS/exFAT
/dev/sdb2        952322048 1904642047  952320000 454.1G  7 HPFS/NTFS/exFAT
/dev/sdb3       1904642048 2856962047  952320000 454.1G  7 HPFS/NTFS/exFAT
/dev/sdb4       2856962048 3907026943 1050064896 500.7G  f W95 Ext'd (LBA)
/dev/sdb5       2856964096 3907026943 1050062848 500.7G  7 HPFS/NTFS/exFAT

My question is why it does not automount. Also if I should try to manually mount it, how should I go about it ?
I got the disks pre-formatted in around 500 GB (or as close to it) multiples as can be seen.


The other question is why does /dev/sdb4 show some different dialog than the rest ?

[Head_on_a_Stick]

If it is to be a static filesystem, why not just put it in your /etc/fstab?
https://wiki.debian.org/fstab

You can manually mount using the mount command -- see man mount

[shirish]

If it is to be a static filesystem, why not just put it in your /etc/fstab?
https://wiki.debian.org/fstab

You can manually mount using the mount command -- see man mount

I have seen the mount command. The problem with that is you have no idea what is actually happening, is it happening or not. My Expansion series External HDD is detected and mounted automatically, so why this doesn't work, that is my question.

The other part would be if I format those partitions to ext4 would that make any difference in auto-mounting ? My main aim is to get auto-mount to work. I don't want a static filesystem as you have mentioned.

UPDATE 22/02/2015 :- Actually it seems the issue is from my side. All the ports seem to be USB 1.1. I have 6 ports in my machine, 2 in the front and 4 in the back. I used lsusb and a 1.1 USB HID mouse to figure out at what speed does the ports run at.

The output when no devices are attached to the system :-

Code: Select all

$ lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

So as can be seen, there is only 1 Bus - Bus 002 which runs at 2.0, all the rest run at USB 1.1 speeds.

This is output when attached to one of the front USB ports

Code: Select all

$ lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse

So this is running at Bus 005 which as shared above is running at 1.1 .

This is when running it at the other front port as well :-

Code: Select all

$ lsusb | grep 046d:c05a
Bus 005 Device 004: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse

So this is also running on Bus 05 which is also 1.1

Now for the back ones.

This is it at bottom right :-

Code: Select all

$ lsusb | grep 046d:c05a
Bus 001 Device 005: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse

Bottom left :-

Code: Select all

$ lsusb | grep 046d:c05a
Bus 001 Device 006: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse

Top right :-

Code: Select all

$ lsusb | grep 046d:c05a
Bus 003 Device 005: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse

and lastly Top left :-

Code: Select all

$ lsusb | grep 046d:c05a
Bus 003 Device 006: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse

So, apparently, these are all running at 1.1 speeds. I also came across this :-

http://www.raspberrypi.org/forums/viewt ... 4&p=700965

the answer given here seems that the way to do that is to increase the current to the 1.1 USB ports, in a desktop system I dunno if it's possible in an assembled desktop. I do remember being told by the vendor that is a USB header on the mobo, perhaps that is the 2.0 version. (This desktop is around 5 years old or even longer.)

Update 2- 22/02/2015 - It seems that a USB 3.0 device gets itself detected as a USB 2.0 device as seen here :-

Code: Select all

$ dmesg | tail -f
[ 5338.424038] usb 2-7: reset high-speed USB device number 37 using ehci-pci
[ 5338.515579] systemd[1]: Got notification message for unit systemd-logind.service
[ 5338.515586] systemd[1]: systemd-logind.service: Got notification message from PID 799 (WATCHDOG=1...)
[ 5338.515590] systemd[1]: systemd-logind.service: got WATCHDOG=1
[ 5338.515598] systemd[1]: Got notification message for unit systemd-logind.service
[ 5338.515600] systemd[1]: systemd-logind.service: Got notification message from PID 799 (WATCHDOG=1...)
[ 5338.515603] systemd[1]: systemd-logind.service: got WATCHDOG=1
[ 5339.568028] .
[ 5339.684055] usb 2-7: reset high-speed USB device number 37 using ehci-pci
[ 5339.964063] usb 2-7: reset high-speed USB device number 37 using ehci-pci

On the front ports, right one :-

Code: Select all

$ lsusb
Bus 002 Device 022: ID 0bc2:ab24 Seagate RSS LLC 

on the left one :-

Code: Select all

$ lsusb | grep 0bc2:ab24
Bus 002 Device 038: ID 0bc2:ab24 Seagate RSS LLC 

In the back, bottom right it got mounted as well :-

Code: Select all

$ lsusb | grep 0bc2:ab24
Bus 002 Device 046: ID 0bc2:ab24 Seagate RSS LLC 

The mount command which tells it is mounted :-

Code: Select all

$ mount | grep fuseblk
/dev/sdb1 on /media/shirish/Data type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,uhelper=udisks2)

So it seems that there is only USB 2.0 port in the machine and that I was able to put it in and that did the whole thing automatically. It all boils down to having a USB 2.0 which will power the USB 3.0 device and gets mounted as well.

Interestingly enough, saw this http://www.raspberrypi.org/forums/viewt ... 4&p=700965, it also gives some interesting pointers. The idea that even a 1.1 port with enough current can do it was nice to know, although is it possible in my desktop, dunno.