HI,

we are unable to mount NTFS 4 TB partition in to RHEL 5.7 server.
below error is came:

Failed to read last sector (976752596): Invalid argument
Perhaps the volume is a RAID/LDM but it wasn't setup yet, or the
wrong device was used, or the partition table is incorrect.
Failed to startup volume: Invalid argument
Failed to mount '/dev/sda1': Invalid argument
The device '/dev/sda1' doesn't have a valid NTFS.
Maybe you selected the wrong device? Or the whole disk instead of a
partition (e.g. /dev/hda, not /dev/hda1)? Or the other way around?

out put for below command:
fdisk -lu
dmraid -ay
dmraid -s

[root@oracle137 ~]# dmraid -ay
ERROR: unsupported sector size 4096 on /dev/sda.
no block devices found
[root@oracle137 ~]# man dmraid
Formatting page, please wait...
[root@oracle137 ~]# man dmraid
[root@oracle137 ~]# dmraid -s
ERROR: unsupported sector size 4096 on /dev/sda.
no block devices found


Please help.

You only posted the output of one command, and didn't post the actual mount command you were using.

AGAIN, as you've been asked before: ARE YOU PAYING FOR RHEL???? Because this is a reported bug in RHEL 5.7, and if you were PAYING FOR RHEL, you would have gotten the fix. AGAIN:have you contacted Red Hat support, if you're paying for it???

Also, since you don't post the mount command, or tell us how the disk is partitioned, we can't tell you much. The output:
..gives you some things to check; did you? IS the device NTFS? Did you mount the wrong slice/device? HAS dmraid been set up on the device? Did you try to restart dmraid services? What kind of device is this (external or internal)? Has this EVER worked????

Support for Advanced Format drives was added in kernel version 2.6.32. RHEL 5 does not support them.

1 members found this post helpful.

Hello TB0ne -

we've run the command:

[root@oracle137 ~]# mount -t ntfs-3g /dev/sda1 /data
Failed to read last sector (976752596): Invalid argument
Perhaps the volume is a RAID/LDM but it wasn't setup yet, or the
wrong device was used, or the partition table is incorrect.
Failed to startup volume: Invalid argument
Failed to mount '/dev/sda1': Invalid argument
The device '/dev/sda1' doesn't have a valid NTFS.
Maybe you selected the wrong device? Or the whole disk instead of a
partition (e.g. /dev/hda, not /dev/hda1)? Or the other way around?

and yes we've paid the RHEL its a production server.

This is external HDD which have file system NTFS.
output of command #fdisk -l
WARNING: The size of this disk is 4.0 TB (4000787025920 bytes).
DOS partition table format can not be used on drives for volumes
larger than 2.2 TB (2199023255040 bytes). Use parted(1) and GUID
partition table format (GPT).


Disk /dev/sda: 4000.7 GB, 4000787025920 bytes
255 heads, 63 sectors/track, 60800 cylinders, total 976754645 sectors
Units = sectors of 1 * 4096 = 4096 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 2048 976754644 3907010388 7 HPFS/NTFS

Can you read this disk with Windows itself, right now? Before going into full on linux debugging mode, you should make sure the thing is even readable. Because at first glance it looks like you have a partition size mismatch, which could be corruption.

Ok, so to reiterate what smallpond said, support for such things wasn't added to that version of RHEL. And again, since you didn't answer the questions before:

• Did you mount the wrong slice/device?
• HAS dmraid been set up on the device?
• Did you try to restart dmraid services?
• Has this EVER worked????

If you're not going to answer questions when asked (like you have not done in several other threads), then why do you post??? No one here can help you if you don't participate in the conversation and answer questions when asked.
Really? Then AGAIN: why are you not calling Red Hat for support? Or is it because the last version of RHEL 5 that is supported is 5.9, and you're NOT paying for RHEL? AGAIN, there were reported bugs in RHEL 5.7...since you're paying, you should have access to the Red Hat knowledgebase, where this issue is documented, and be able to download the fix.
Ok, so is it a USB drive? Firewire? ESATA? As szboardstretcher pointed out, it would appear that something is corrupted on that disk...which goes back to what you were asked before, and that is "Has this ever worked?"