Is there a driver for intenso memory tower 3,5"?

How does it connect to the system?

USB 2.0 - it came to my mind that this might be relevant ...

Ok, what is the output of:

lsusb; lsb_release -a; uname -a

Thanks

lsusb
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 05e3:0606 Genesys Logic, Inc. USB 2.0 Hub / D-Link DUB-H4 USB 2.0 Hub
Bus 002 Device 002: ID 1020:030a Labtec
Bus 002 Device 003: ID 152d:2329 JMicron Technology Corp. / JMicron USA Technology Corp. JM20329 SATA Bridge
Bus 001 Device 003: ID 04b4:6830 Cypress Semiconductor Corp. CY7C68300A EZ-USB AT2 USB 2.0 to ATA/ATAPI

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04 LTS
Release: 12.04
Codename: precise

uname -a
Linux Leto 3.2.0-26-generic-pae #41-Ubuntu SMP Thu Jun 14 16:45:14 UTC 2012 i686 i686 i386 GNU/Linux

Thank you!!

ok, pull out the USB cable and run:

lsusb

What is output?

First I remove Trekstore portable harddisk.
Output is
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 05e3:0606 Genesys Logic, Inc. USB 2.0 Hub / D-Link DUB-H4 USB 2.0 Hub
Bus 002 Device 002: ID 1020:030a Labtec
Bus 002 Device 003: ID 152d:2329 JMicron Technology Corp. / JMicron USA Technology Corp. JM20329 SATA Bridge

Then I remove USB hub. Output is
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 004: ID 1020:030a Labtec
Bus 002 Device 003: ID 152d:2329 JMicron Technology Corp. / JMicron USA Technology Corp. JM20329 SATA Bridge

Last I remove the Intenso harddisk which is not recognized. The mouse is the only USB device left. Output is
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 004: ID 1020:030a Labtec

If you have it connected and run:

sudo fdisk -l

Does the storage show?

Yes:
Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
255 Köpfe, 63 Sektoren/Spur, 121601 Zylinder, zusammen 1953525168 Sektoren
Einheiten = Sektoren von 1 × 512 = 512 Bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Festplattenidentifikation: 0x35e1504c

   Gerät boot. Anfang Ende Blöcke Id System
/dev/sdc1 2048 1953520064 976759008+ c W95 FAT32 (LBA)

Great. Then you don't need drivers :)

You can run:

sudo mkdir /media/intenso; sudo mount /dev/sdc1 /media/intenso -o uid=1000,rw,user

Is it now accessible from /media/intenso ?

Yes!! :-)

And nautilus also shows it now.

Thank you very much for your help!

You can add it to your /etc/fstab and it will mount at boot. The line will look similar to the command I gave, just rejigged :)

I thought about this, but how would the system react then if I didn't have the harddisk connected?

And, BTW, not being a native English speaker, what ist "rejigged"? ;-)

rejigged == tweaked == changed

If you run:

gksudo gedit /etc/fstab

add this line:

/dev/sdc1 /media/intenso auto uid=1000,rw,user,noboot 0 0

Save the new file and reboot, connect the device and it should automount

Thank you, actionparsnip, for your detailed information!

When I connect a different portable hard disk (a TREKSTORE that automounts voluntarily) before the reluctant intenso, it will become device /dev/sdc1 with uid=1000 (as /etc/mtab tells me).

So it seems adding the line to /etc/fstab as you suggest above, I have to keep in mind to always connect the intenso as the first portable disk, is that right?

If you have the first device connected and run:

sudo blkid

You can see the UUID of the storage and can use that in the same way as the other lines in the fstab file.

The intenso portable harddisk shows with "sudo fdisk -l" on /dev/sdc1, but not with "sudo blkid".

Really weird. Not sure

I have the same wired behaviour with an Intenso disk. See http://askubuntu.com/questions/194385/automount-of-external-hard-disk for some discussion, but I didn't find a reason either.