I need help to mount a HDD. Further to my WD problem

Opensuse 13.2

This is a continuation of my other thread that had to do with recovering a WD external drive data.

I think that I have got the WD working ok under OS 13.2 and was about to try and copy he contents to another spare HDD that I have.
However, I cannto for the life of me get it to mount so I can acces it.

Whenever I plug it in it immediately slows everything down, especially Dolphin. It takes minutes to try and open, even to the point that it caused Dolphin to become unresponsive.
I think that it has to do with my fumbling attempts to create a mount point and probably getting multiples created incorrectly.
So, this is some of the info I have.
The device is SDD


hexdump@Corky-PC:~> sudo smartctl -a /dev/sdd1
smartctl 6.3 2014-07-26 r3976 [x86_64-linux-3.16.7-29-desktop] (SUSE RPM)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               WDC
Product:              WD5000AAKS-00TMA
Revision:             3.00
User Capacity:        500,107,862,016 bytes [500 GB]
Logical block size:   512 bytes
scsiModePageOffset: response length too short, resp_len=4 offset=4 bd_len=0
scsiModePageOffset: response length too short, resp_len=4 offset=4 bd_len=0
>> Terminate command early due to bad response to IEC mode page
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
hexdump@Corky-PC:~> 



hexdump@Corky-PC:~> df -l
df: ‘/run/media/hexdump/DE29-E81F’: Input/output error
Filesystem     1K-blocks     Used Available Use% Mounted on
/dev/sda2      202653592 20777544 171558788  11% /
devtmpfs         1889616        8   1889608   1% /dev
tmpfs            1897784       80   1897704   1% /dev/shm
tmpfs            1897784    65936   1831848   4% /run
tmpfs            1897784        0   1897784   0% /sys/fs/cgroup
tmpfs            1897784      236   1897548   1% /tmp
tmpfs            1897784    15220   1882564   1% /var/log
/dev/sdb2       20027260    44976  18941900   1% /sdb/sdb2
/dev/sdb1      759717488 21004924 700098088   3% /home
hexdump@Corky-PC:~> 



hexdump@Corky-PC:~> sudo fdisk -l       

Disk /dev/sda: 238.5 GiB, 256060514304 bytes, 500118192 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: 0x0006150b

Device     Boot     Start       End   Sectors   Size Id Type
/dev/sda1            2048   4192255   4190208     2G 82 Linux swap / Solaris
/dev/sda2  *      4192256 416227327 412035072 196.5G 83 Linux
/dev/sda3       416227328 458174463  41947136    20G 83 Linux

Disk /dev/sdb: 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: 0x0006fdc2

Device     Boot      Start        End    Sectors   Size Id Type
/dev/sdb1             2048 1543925759 1543923712 736.2G 83 Linux
/dev/sdb2       1543925760 1584885759   40960000  19.5G 83 Linux
/dev/sdb3       1584887806 1953523711  368635906 175.8G  5 Extended
/dev/sdb5       1584887808 1945663487  360775680   172G 83 Linux
/dev/sdb6       1945665536 1953523711    7858176   3.8G 82 Linux swap / Solaris

Partition 4 does not start on physical sector boundary.


Disk /dev/sdd: 465.8 GiB, 500107862016 bytes, 976773168 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: 0x000b1de8                                                                                                                                  

Device     Boot Start       End   Sectors   Size Id Type
/dev/sdd1        2048 976773119 976771072 465.8G  c W95 FAT32 (LBA)




From smartctl there is a serious hardware problem with that drive. You won’t get it to mount. But you don’t need to mount it to use recovery software. But if the problem is in the electronic interface then recovery software won’t be able to read it either.

Removing from enclosure may help but WD may have done funky things so not sure that will work either.