New WD Superspeed USB 3.0 and Salix64 KDE 13.37

[globetrotterdk]

I have just purchased a WD MyBook Essential 3 TB external Superspeed USB 3.0 hard disk and the first time I use it, I encounter the following problem (copied from /var/log/messages):

Code: Select all

Aug 10 22:57:14 rage ntfs-3g[3396]: ntfs_mst_post_read_fixup: magic:
0xe64e2eb9  size: 4096  usa_ofs: 31006  usa_count: 39385: Invalid
argument
Aug 10 22:57:27 rage ntfs-3g[3396]: ntfs_mst_post_read_fixup: magic:
0x1bc23df9  size: 4096  usa_ofs: 38932  usa_count: 52134: Invalid
argument
Aug 10 22:57:27 rage kernel: [15343.197346] mount.ntfs-3g[3396]:
segfault at 66b394 ip 00007fa6536c2255 sp 00007fffc262c2b0 error 4 in
libntfs-3g.so.80.0.0[7fa653696000+59000]

I am using a "current" kernel and there were no errors encountered when the drive was originally mounted:

Code: Select all

Aug 10 18:47:09 rage ntfs-3g[3396]: Version 2011.1.15 integrated FUSE
27 
Aug 10 18:47:09 rage ntfs-3g[3396]: Mounted /dev/sdc1 (Read-Write,
label "My Book", NTFS 3.1) 
Aug 10 18:47:09 rage ntfs-3g[3396]: Cmdline options:
rw,nosuid,nodev,uhelper=hal,uid=1000,locale=en_US.utf8 
Aug 10 18:47:09 rage ntfs-3g[3396]: Mount options:
rw,nosuid,nodev,uhelper=hal,allow_other,nonempty,relatime,fsname=/dev/
sdc1,blkdev,blksize=4096,default_permissions 
Aug 10 18:47:09 rage ntfs-3g[3396]: Global ownership and permissions
enforced, configuration type 1 
Aug 10 18:47:09 rage hald: mounted /dev/sdc1 on behalf of uid 1000

Is there someone that can help decipher the problem?

[mimosa]

No idea how to actually solve the problem as it stands, but if I were in the same situation, the first thing I'd try would be reformatting the disk, on the basis that maybe they did something tricky with it in the factory. Chances are it isn't that, but it's a quick thing to do. Also, do you want it formatted as ntfs, anyway?

I'm assuming you have no data on it. So first off, in GParted, delete the partition and create a new one with the filesystem of your choice. Second try, create a new partition table, then create a new partition.


Could be kernel-related too, in which case it might be worth trying the above steps from 13.37 live.

As ever, do be careful with device names so you don't wipe your hard disk or something.

Assuming none of that helps - what exactly did you try to do with it, after you mounted it, to produce that output? If you just mount it, is there anything there? (#ls -al)

[Shador]

So it worked and stopped working at some point? Could be some damage with the filesystem then. If so you can fsck the filesystem with Windows.

[globetrotterdk]

Assuming none of that helps - what exactly did you try to do with it, after you mounted it, to produce that output? If you just mount it, is there anything there? (#ls -al)

So it worked and stopped working at some point? Could be some damage with the filesystem then. If so you can fsck the filesystem with Windows.

Thanks for the quick replies guys. I just unpacked it and started using the HD yesterday. My first thought was the kernel modules because this is a (relatively) new kind of interface, that I am using natively as my mobo supports Superspeed USB 3.0. I first started experiencing the problem when I failed figuring out how to backup my system to the new drive. I tried:

Code: Select all

# tar -cvpzf /dev/sdc /home

Code: Select all

$ tar -cvpzf /dev/sdc backup.tar `ls`

There were a couple of others as well, but they kicked back normal errors, so ended up backing up my directory collections like this:

Code: Select all

$ tar -cvpzf documents.tar.gz /home/user/Documents

The /var/log/message error was encountered when I tried to copy the second directory collection to the external drive. Copying the first directory collection produced no error.

Edit: KDE Partition Manager now reports that the drive has no valid partition tables.

[gapan]

/dev/sdc is a device node for the hard drive. You can't use it directly. You need to have it mounted somewhere (actually a partition in it, probably /dev/sdc1) and use the mountpoint to do any file actions on it.

If you try to write directly to /dev/sdc as root, you probably wiped all partition information from it.

[globetrotterdk]

/dev/sdc is a device node for the hard drive. You can't use it directly. You need to have it mounted somewhere (actually a partition in it, probably /dev/sdc1) and use the mountpoint to do any file actions on it.

If you try to write directly to /dev/sdc as root, you probably wiped all partition information from it.

Thanks. I learned something new today. I downloaded the suggested app for reformatting the drive in Windows from the producer's website.