Hi list!
I have a 3TB usb drive with an NTFS filesystem on it, that I can't mount.: [bent@bnlaptop ~]$ sudo /sbin/mount.ntfs-3g /dev/sdb1 /mnt Failed to read vcn 0xf28: Input/output error Failed to mount '/dev/sdb1': 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.
On a Win7 machine there are no problems and chkdsk can't find anything wrong with the filesystem.
I can mount 1TB drives using ntfs-3g without problems, so the driver doesn't seem to be the issue.
I've tried both CentOS6.2 and Fedora16 with the same result.
Any suggestions?
with kind regards, Bent Terp
I have a 3TB usb drive with an NTFS filesystem on it, that I can't mount.: [bent@bnlaptop ~]$ sudo /sbin/mount.ntfs-3g /dev/sdb1 /mnt Failed to read vcn 0xf28: Input/output error Failed to mount '/dev/sdb1': 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.
On a Win7 machine there are no problems and chkdsk can't find anything wrong with the filesystem.
I can mount 1TB drives using ntfs-3g without problems, so the driver doesn't seem to be the issue.
I've tried both CentOS6.2 and Fedora16 with the same result.
I wonder if it uses a GPT partition table or not. I don't remember all the details, but for some reason I think you need a GPT partition table to handle partitions, filesystems, or something over 2 TB.
On 03/22/2012 01:39 PM, Barry Brimer wrote:
I wonder if it uses a GPT partition table or not. I don't remember all the details, but for some reason I think you need a GPT partition table to handle partitions, filesystems, or something over 2 TB.
fdisk will tell him that.
With a GPT, fdisk will write something like:
# fdisk -l /dev/sda
WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sda: 6301.1 GB, 6301061767168 bytes 255 heads, 63 sectors/track, 766060 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000
Device Boot Start End Blocks Id System /dev/sda1 1 267350 2147483647+ ee GPT
So, parted should be used to look at the partitions.
Mogens
On Thu, Mar 22, 2012 at 1:39 PM, Barry Brimer lists@brimer.org wrote:
I wonder if it uses a GPT partition table or not. I don't remember all the details, but for some reason I think you need a GPT partition table to handle partitions, filesystems, or something over 2 TB.
I would have expected this as well, but: [bent@bnlaptop ~]$ sudo parted /dev/sdb print Model: WD My Book 1140 (scsi) Disk /dev/sdb: 3001GB Sector size (logical/physical): 4096B/4096B Partition Table: msdos
Number Start End Size Type File system Flags 1 1049kB 3001GB 3001GB primary
[bent@bnlaptop ~]$
BR Bent
Bent Terp wrote:
On Thu, Mar 22, 2012 at 1:39 PM, Barry Brimer lists@brimer.org wrote:
I wonder if it uses a GPT partition table or not. I don't remember all the details, but for some reason I think you need a GPT partition table to handle partitions, filesystems, or something over 2 TB.
I would have expected this as well, but: [bent@bnlaptop ~]$ sudo parted /dev/sdb print Model: WD My Book 1140 (scsi) Disk /dev/sdb: 3001GB Sector size (logical/physical): 4096B/4096B Partition Table: msdos
Number Start End Size Type File system Flags 1 1049kB 3001GB 3001GB primary
There's a problem here: MSDOS - that would be an MBR - can only handle 2TB. Now, if it's set up with 4k sectors, it'll do more, but I don't know if there's an interaction there.
In short, either partition the drive, or rebuild the drive with a GPT.
mark
On Thu, Mar 22, 2012 at 4:05 PM, m.roth@5-cent.us wrote:
There's a problem here: MSDOS - that would be an MBR - can only handle 2TB. Now, if it's set up with 4k sectors, it'll do more, but I don't know if there's an interaction there.
Works on Win2k8 and Win7, so yes it's 4k sectors.
In short, either partition the drive, or rebuild the drive with a GPT.
Yeah, won't do much good for the data on the drive, though...
So as a stop-gap measure, the drive is currently mounted on a Win2k8 box and the C6 box cifs-mounts //ip/e$ It ain't pretty but it's the best I can do at the moment.
But you had a good point 'bout the partiontable - that could explain why I had success with some drives and not with others. Once this disk has been emptied, I'll try and rebuild it and see if that works on both platforms.
BR Bent
On Thu, Mar 22, 2012 at 4:05 PM, m.roth@5-cent.us wrote:
In short, either partition the drive, or rebuild the drive with a GPT.
Yes, I'm back :-D
Finally had a chance to try this out, and it works totally on my Fedora16 laptop. But not on the EL6.2 server....
Mar 26 16:36:00 gpfsnode8 kernel: usb 1-1: new high speed USB device using ehci_hcd and address 8 Mar 26 16:36:00 gpfsnode8 kernel: usb 1-1: New USB device found, idVendor=1058, idProduct=1140 Mar 26 16:36:00 gpfsnode8 kernel: usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=5 Mar 26 16:36:00 gpfsnode8 kernel: usb 1-1: Product: My Book 1140 Mar 26 16:36:00 gpfsnode8 kernel: usb 1-1: Manufacturer: Western Digital Mar 26 16:36:00 gpfsnode8 kernel: usb 1-1: SerialNumber: 574341575A31313831373338 Mar 26 16:36:00 gpfsnode8 kernel: usb 1-1: configuration #1 chosen from 1 choice Mar 26 16:36:00 gpfsnode8 kernel: scsi13 : SCSI emulation for USB Mass Storage devices Mar 26 16:36:01 gpfsnode8 kernel: scsi 13:0:0:0: Direct-Access WD My Book 1140 1003 PQ: 0 ANSI: 6 Mar 26 16:36:01 gpfsnode8 kernel: scsi 13:0:0:1: Enclosure WD SES Device 1003 PQ: 0 ANSI: 6 Mar 26 16:36:01 gpfsnode8 kernel: sd 13:0:0:0: Attached scsi generic sg0 type 0 Mar 26 16:36:01 gpfsnode8 kernel: ses 13:0:0:1: Attached Enclosure device Mar 26 16:36:01 gpfsnode8 kernel: ses 13:0:0:1: Attached scsi generic sg1 type 13 Mar 26 16:36:09 gpfsnode8 kernel: ses 13:0:0:1: Failed to get diagnostic page 0x8000002 Mar 26 16:36:09 gpfsnode8 kernel: ses 13:0:0:1: Failed to bind enclosure -19 Mar 26 16:36:17 gpfsnode8 kernel: sd 13:0:0:0: [sda] Spinning up disk....ready Mar 26 16:36:17 gpfsnode8 kernel: sd 13:0:0:0: [sda] 732558336 4096-byte logical blocks: (3.00 TB/2.72 TiB) Mar 26 16:36:17 gpfsnode8 kernel: sd 13:0:0:0: [sda] Write Protect is off Mar 26 16:36:17 gpfsnode8 kernel: sd 13:0:0:0: [sda] Assuming drive cache: write through Mar 26 16:36:17 gpfsnode8 kernel: sd 13:0:0:0: [sda] 732558336 4096-byte logical blocks: (3.00 TB/2.72 TiB) Mar 26 16:36:17 gpfsnode8 kernel: sd 13:0:0:0: [sda] Assuming drive cache: write through Mar 26 16:36:17 gpfsnode8 kernel: sda: sda1 Mar 26 16:36:17 gpfsnode8 kernel: sd 13:0:0:0: [sda] 732558336 4096-byte logical blocks: (3.00 TB/2.72 TiB) Mar 26 16:36:17 gpfsnode8 kernel: sd 13:0:0:0: [sda] Assuming drive cache: write through Mar 26 16:36:17 gpfsnode8 kernel: sd 13:0:0:0: [sda] Attached SCSI disk Mar 26 16:36:17 gpfsnode8 multipathd: sda: add path (uevent) [root@gpfsnode8 ~]# parted /dev/sda print Warning: Device /dev/sda has a logical sector size of 4096. Not all parts of GNU Parted support this at the moment, and the working code is HIGHLY EXPERIMENTAL.
Model: WD My Book 1140 (scsi) Disk /dev/sda: 3001GB Sector size (logical/physical): 4096B/4096B Partition Table: gpt
Number Start End Size File system Name Flags 1 1049kB 3001GB 3001GB primary
[root@gpfsnode8 ~]# mount.ntfs-3g /dev/sda1 /mnt/disk2 ntfs-3g: Failed to access volume '/dev/sda1': No such file or directory
ntfs-3g 2010.10.2 integrated FUSE 27 - Third Generation NTFS Driver Configuration type 1, XATTRS are on, POSIX ACLS are off
Copyright (C) 2005-2007 Yura Pakhuchiy Copyright (C) 2006-2009 Szabolcs Szakacsits Copyright (C) 2007-2010 Jean-Pierre Andre Copyright (C) 2009 Erik Larsson
Usage: ntfs-3g [-o option[,...]] <device|image_file> <mount_point>
Options: ro (read-only mount), remove_hiberfile, uid=, gid=, umask=, fmask=, dmask=, streams_interface=. Please see the details in the manual (type: man ntfs-3g).
Example: ntfs-3g /dev/sda1 /mnt/windows
Ntfs-3g news, support and information: http://ntfs-3g.org [root@gpfsnode8 ~]# ls -l /dev/sda1 ls: cannot access /dev/sda1: No such file or directory [root@gpfsnode8 ~]#
And this I just can't get my head around, why is /dev/sda1 not created? /dev/sda shows up as expected and the kernel even recognizes that there is a sda1 partition but the device entry isn't created.
Anybody able to help me here?
BR Bent
mark
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Stumbled upon this somewhat old post, but I'll offer a suggestion nonetheless.
And this I just can't get my head around, why is /dev/sda1 not created? /dev/sda shows up as expected and the kernel even recognizes that there is a sda1 partition but the device entry isn't created.
Perhaps you don't have GPT support enabled in the kernel (CONFIG_EFI_PARTITION) IIRC. In the dmesg output you posted, there's also no log entry showing the detected partitions, leading me to suspect that the kernel doesn't know about GPT partitions.
Hope this helps anyone,
Matthijs
-
Barry Brimer -
Bent Terp -
m.roth＠5-cent.us -
Matthijs Kooijman -
Mogens Kjaer