Tuesday, July 01, 2014

blind man reading here boss

Oh My It's the Seagate that won't mount

trkof@trkof-p7-1205 ~ $ LSUSB
LSUSB: command not found
trkof@trkof-p7-1205 ~ $ lsusb
Bus 002 Device 005: ID 0bc2:3312 Seagate RSS LLC
Bus 002 Device 004: ID 045e:00f9 Microsoft Corp. Wireless Desktop Receiver 3.1
Bus 002 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 005: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer
Bus 001 Device 004: ID 04f2:0841 Chicony Electronics Co., Ltd HP Multimedia Keyboard
Bus 001 Device 007: ID 1058:0820 Western Digital Technologies, Inc.
Bus 001 Device 006: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
trkof@trkof-p7-1205 ~ $ sudo fdisc -1
[sudo] password for trkof:
sudo: fdisc: command not found
trkof@trkof-p7-1205 ~ $ sudo fdisk -1
fdisk: invalid option -- '1'
Usage:
 fdisk [options]    change partition table
 fdisk [options] -l list partition table(s)
 fdisk -s      give partition size(s) in blocks

Options:
 -b             sector size (512, 1024, 2048 or 4096)
 -c[=]           compatible mode: 'dos' or 'nondos' (default)
 -h                    print this help text
 -u[=]           display units: 'cylinders' or 'sectors' (default)
 -v                    print program version
 -C           specify the number of cylinders
 -H           specify the number of heads
 -S           specify the number of sectors per track

trkof@trkof-p7-1205 ~ $ dmesg | tail
[  957.985086] scsi 9:0:0:0: Direct-Access     Seagate  Expansion Desk   0319 PQ: 0 ANSI: 6
[  957.985418] sd 9:0:0:0: Attached scsi generic sg6 type 0
[  967.829631] sd 9:0:0:0: [sdf] 732566646 4096-byte logical blocks: (3.00 TB/2.72 TiB)
[  967.830499] sd 9:0:0:0: [sdf] Write Protect is off
[  967.830505] sd 9:0:0:0: [sdf] Mode Sense: 2b 00 10 08
[  967.831373] sd 9:0:0:0: [sdf] Write cache: enabled, read cache: enabled, supports DPO and FUA
[  967.832331] sd 9:0:0:0: [sdf] 732566646 4096-byte logical blocks: (3.00 TB/2.72 TiB)
[  967.856761]  sdf: sdf1
[  967.858107] sd 9:0:0:0: [sdf] 732566646 4096-byte logical blocks: (3.00 TB/2.72 TiB)
[  967.887229] sd 9:0:0:0: [sdf] Attached SCSI disk
trkof@trkof-p7-1205 ~ $

MORE

Error mounting /dev/sdf1 at /media/trkof/Seagate Expansion Drive1: Command-line `mount -t "ntfs" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,dmask=0077,fmask=0177" "/dev/sdf1" "/media/trkof/Seagate Expansion Drive1"' exited with non-zero exit status 13: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Failed to read of MFT, mft=6 count=1 br=-1: Input/output error
Failed to open inode FILE_Bitmap: Input/output error
Failed to sync device /dev/sdf1: Input/output error
Failed to mount '/dev/sdf1': Input/output error
NTFS is either inconsistent, or there is a hardware fault, or it's a
SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows
then reboot into Windows twice. The usage of the /f parameter is very
important! If the device is a SoftRAID/FakeRAID then first activate
it and mount a different device under the /dev/mapper/ directory, (e.g.
/dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation
for more details.

14 comments:

Rodger the Real King of France said...

what comes next?

gadfly said...

All Greek to me, but these folks seem to be having a similar problem

Anonymous said...

Curious. Error 13 is historically permissions related (EACCESS). You must be root to mount a drive. You could try the command "blkid" - I see the Seagate in your "lsusb" output so it is physically recognized. The output of dmesg suggests that the overall drive is reported as found at /dev/sdf. It appears that the entire drive is allocated as a single partition (/dev/sdf1). All that part looks good. Fdisk is not designed for parge partitions - yours at 3TB is "large" - try parted instead (or the graphical version, gparted). remember, you need to run these as root, so it is quite possible to smoke your disk if you are incautious. If your mount command was not run as root, please try it using sudo mount -t ntfs /dev/sdf1 /mnt (the /mnt directory should exist by default and be empty - it is used for just such events). You can skip all those mount options and quotation marks for the moment. If it still will not mount, let us know. We're here to help. If it DOES mount, you can unmount it using sudo umount /mnt and try it with all those arcane mount options. For testing, simple is better.

--Jimmy don\'t play that

Anonymous said...

Er, large, not parge. Perhaps this is an example of why the C library function "creat" is spelled without an "e".

-- Jimmy don\'t play that

MAX Redline said...

I'm not entirely sure as to why I should be interested in the sex life of a Seagate. Is that anything like a Sea Horse? Though, to be honest, I'm not sure that seahorses mount each other, either. I'll have to get back to ya on that.

Shugart Technology's been around since 1978, but due to a legal dispute, renamed as Seagate. They've got a pretty reliable background. Is your support software updated?

http://download.cnet.com/windows/seagate/3260-20_4-10029334.html

Note: they basically run only on the Winders platforms, so since it looks like you're trying to get that to work in Linux, you might want to try a VM sandbox.

I'm assuming this is a powered USB drive, so alternatively, you might disconnect one of the 4-prt hubs and try direct access through the (now free) USB 2.0 port.

Nelson said...

If you are trying to get read/write access to the drive, you're going to need to install NTFS-3G; if you're on a Debian/Ubuntu/Mint install, sudo apt-get install ntfs-3g should do it. The standard NTFS kernel module does not safely support write access to drives, and comes with Big Scary Warnings(TM) to that effect.

If the drive is empty, you should try to install a GPT partition table on the drive, then repartition and reformat it to get the full 3TB (minus formatting and decimal-to-binary conversion losses). Again, use NTFS-3g, not the preinstalled kernel NTFS support; you will be much happier.

BTW, Seagates work just fine in Linux. I've been using them for years, and currently have 3x3TB drives + 1x2TB across 2 different machines, including one brand-new 3TB that I just installed today via LVM. Granted, they're all internal drives; I've had a couple of issues with their external drives due to the USB-to-SATA adaptor spinning the drive down after a while and not allowing Linux to spin it back up again without a reboot.

Anonymous said...

That one is certainly on the USB interface, based on his logs. I think he was wanting to recover data from this drive, so better not put a new partition table on it until after data recovery (if any). I would estimate the kernel ntfs stack is adequate to at least mount and read a 3TB partition, but I could be wrong. I don't do much with NTFS under Linux.

--Jimmy don\'t play that

Rodger the Real King of France said...

Thanks, but frozen at the switch here boss. I want a program that will automatically fix everything. There must be one. Although I am at least picking up some of the Linux command lingo.

Rodger the Real King of France said...

Wait - the Seagate backup drive is 2T; the boot disk is 3t - it;s the Seagate I'm trying to retrieve data from. I am offering a night with Joey Heatherton to anyone who makes this happen*


*subject to Ms. Heatheron's approval

Murphy(AZ) said...

All this time, all this torment... wouldn't it have been better to go to the big box electronics store, bought a custom box with all the bells and whistles you could possibly want, then stop at the liquor store on the way home for some fine adult beverages and maybe some hand-made imported cigars?

So much grief, so little progress!

Rodger the Real King of France said...

of course, but since both my compter and backup drive exploded at the same time I lost 100 % of everything - just about.

Rodger the Real King of France said...

PS I know that info mas to be out there. There's a curios aside to this, which I'll get into later. Swy I think it was a targeted attack.

MAX Redline said...

That one is certainly on the USB interface, based on his logs. I think he was wanting to recover data from this drive, so better not put a new partition table on it until after data recovery (if any). I would estimate the kernel ntfs stack is adequate to at least mount and read a 3TB partition, but I could be wrong. I don't do much with NTFS under Linux.

That's why I suggested removing the hub and trying to read with an unimpeded USB connection. The hubs do slow things down.

If I'm reading this correctly, he's trying to recover data from a 2 Tb Seagate backup, and that appears to be a USB drive. I have that on a SUSE and it's not been an issue, but not being familiar with the version of Linux in question....

pdwalker said...

Hey Uncle Rodge,

You're boldly going where no sane man should ever had to go, but let's see.

quick comments: it is fdisk -l (ell) not -1 (one)

Assumptions: From what I can see, you tried to mount a USB connected hard disk that is 3TB in size, and you tried to mount it as a windows formatted (ntfs) file system.

Question: what are you trying to do exactly? And what are you trying to do it with?

As for the input/output errors, it could be from a couple of reasons:

(a) the disk could be bad - but I gather this is the new drive you have purchased recently, yes? if so, it shouldn't be bad.

(b) the disk might not be formatted with ntfs, so your mount command won't work.

(c) something else.

As it is a 3TB hard drive, the partition format needs to be different in order to access the full drive. That format is called GPT. On my computer, when I run the following, I get this output:

pdwalker@ubuntu:~$ sudo fdisk -l /dev/sdf

WARNING: GPT (GUID Partition Table) detected on '/dev/sdf'! The util fdisk doesn't support GPT. Use GNU Parted.

Disk /dev/sdf: 4000.8 GB, 4000787030016 bytes
256 heads, 63 sectors/track, 484501 cylinders, total 7814037168 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
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sdf1 1 4294967295 2147483647+ ee GPT
Partition 1 does not start on physical sector boundary.


If I get this message about the GPT partition, I can use the "parted" command instead.

pdwalker@ubuntu:~$ sudo parted -l /dev/sdf
Model: ATA HGST HDN724040AL (scsi)
Disk /dev/sdf: 4001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number Start End Size File system Name Flags
1 1049kB 4001GB 4001GB zfs
9 4001GB 4001GB 8389kB


rerun the fdisk command again correctly and let's see what you really have. Once you do that, then we can figure out the next steps.


Do you still have my email address on file?

Post a Comment

Just type your name and post as anonymous if you don't have a Blogger profile.