External Hard drive contents not displayed

English Hardware
#1

Hi guys,

I’ve got a NTFS 1TB drive that mounts with no problem however, content cannot be displayed. I can read-write-execute on Windows/Mac but on my SUSE-box. It used to work fine before but I’m not sure what happened for it to act up like this.

Please help me out with a solution (if possible that won’t involve me formatting it). I apologize if this has been posted before.

Here is output from smartctl -a /dev/sdc1

smartctl 6.2 2013-07-26 r3841 [i686-linux-3.14.1-24.geafcebd-desktop] (SUSE RPM)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               TOSHIBA
Product:              External USB 3.0
Revision:             0001
User Capacity:        1,000,204,886,016 bytes [1.00 TB]
Logical block size:   512 bytes
Logical Unit id:      0x60000393f2200d910000000000000000
Serial number:        4232PRHPT
Device type:          disk
Local Time is:        Thu Apr 17 11:46:55 2014 EAT
SMART support is:     Available - device has SMART capability.
SMART support is:     Enabled
Temperature Warning:  Disabled or Not Supported

=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK

Error Counter logging not supported

Device does not support Self Test logging


ls -l MissSB
ls: reading directory MissSB: Input/output error
total 0


ll /run/media/misssb/
total 256
drwx------  1 misssb users 131072 Apr 17 08:55 MissSB
#2

Please first show where it is mounted and how:

mount

(you may restrict the output posted here to the relevant line).

#3

I apologise for the delay.

mount

dev/sdc1 on /run/media/misssb/MissSB type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
/dev/sdc1 on /var/run/media/misssb/MissSB type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
#4

Hi guys,

I never got a solution to this problem. If someone is kind enough to help me out…

#5

On 2014-05-10 05:46 (GMT) MissSB composed:

> I never got a solution to this problem. If someone is kind enough to
> help me out…

Have you tried running CHKDSK with it connected to Windows? Is this only a problem
from your DE (which DE?), or do you have the same problem trying with a text file
manager from one of the ttys, e.g. with MC? Is root also unable? I only have one
external HD with NTFS that I ever use with Linux. I never have a problem with it, but
I never have it automounted either. You could try manually umounting it, than
manually mounting it right away before any automounter gets a chance:

umount /dev/sdb1

mount -t auto /dev/sdb1 /yourmountpoint

–
“The wise are known for their understanding, and pleasant
words are persuasive.” Proverbs 16:21 (New Living Translation)

Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata *** http://fm.no-ip.com/

#6

It seems to be mounting in two different places?
Did you check both places - perhaps the files appear in the not-shown-by-default mount folder?
Do you have a permanent /etc/fstab entry for it (if it’s a removable drive you shouldn’t have)?

#7

Yes.

These mounts always show up in both places, /var/run & /run.

I noticed this starting in 12.3.

Anything mounted after, including USB sticks, show up there, and both paths work.

I have been able to use either path in, say, Unison without any problems.

Also, when saving files to a USB stick, it makes no difference which of the two paths I choose.

I have not bothered looking into why it has been changed this way. It works, I have never had a problem with it, so there is no pressing need to understand the reasoning behind this.

#8

Right, just tested with a pendrive too, it’s as you say - and they are both “physical”, e.g., one is not a link to the other.

So it’s not the OP problem, and I’m out of ideas.

#9

If you are using KDE, try viewing it with “File Manager - Super User Mode”. Does this display the contents?

#10

I have not been following the entire thread, and I’m struggling with a bad head cold, so apologies if I missed this. Is the NTFS drive clean ? ie when run under windows, have you run a ‘chkdsk’ to ensure than it is a ‘clean’ disk and was unmounted properly under MS-windows ?

Also, I assume there are no entries inappropriately located in the /etc/fstab for this external hard drive (which there should not be).

#11

I see now mrmazda asked the question:

I’m struggling with this head cold. What was the answer to this ?

#12

I run a “chkdsk” on a Windows machine and it found some errors.

#13

Yes I managed to view contents using File Manager, thank you. I couldn’t find the “Super User Mode” though, I just opened File Manager and there they were.

#14

I tried the fstab thing once. Never again. Kicked myself out of my own machine. Still traumatized.

#15

So, is this what you wanted? Late night, too tired to read from start of thread to see your goal.

The Super User Mode version is from the KDE menu => System => File Manager =>

Comes in handy.

Or you could call Dolphin from a Terminal console session with kdesu, or from the Super User Terminal just with:

dolphin

G’night & good luck. I will look in again tomorrow to see how you are coming along, when my brain starts functioning again.:Z:beat-up:

#16

Thanks, I’m not sure whether the chkdsk repaired it but it’s all good now. Much appreciated!

#17

Its quite possible.

My recollection is the ntfs driver for GNU/Linux (and my apologies as with my head cold I can not think of the correct name for the driver … it used to be fuse/ntfs-3g but I think it may have changed since ) … my recollection is driver will on occasion refuse to mount fully an NTFS partition that has errors on the disk that require chkdsk to correct, while the MS-windows drivers have no such constraint.

#18

On 2014-05-15 17:06, oldcpu wrote:

> My recollection is the ntfs driver for GNU/Linux (and my apologies as
> with my head cold I can not think of the correct name for the driver …
> it used to be fuse/ntfs-3g but I think it may have changed since ) …
> my recollection is driver will on occasion refuse to mount fully an NTFS
> partition that has errors on the disk that require chkdsk to correct,
> while the MS-windows drivers have no such constraint.

Correct on all points :slight_smile:

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

#19

Should be noted again that Windows 8.x can leave the file system in an unknown state if you have fast boot set on. I believe the fast boot is set on by default. The reason is that Fast boot does not shut down the OS but puts it in a suspend state and the file system is not closed properly. This can cause problem if other OS’s want to use the Windows file system

#20

On 2014-05-15 19:36, gogalthorp wrote:
>
> Should be noted again that Windows 8.x can leave the file system in an
> unknown state if you have fast boot set on. I believe the fast boot is
> set on by default. The reason is that Fast boot does not shut down the
> OS but puts it in a suspend state and the file system is not closed
> properly. This can cause problem if other OS’s want to use the Windows
> file system

Oh, yes, absolutely. I forgot that one.

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))