Initially, I used the default Windows Explorer formatting menu.
So, this is for a working state (block size 16KiB):
 
fs@fs-hpc:~$ sudo ntfsinfo -m /dev/sdb1
Volume Information 
    Name of device: /dev/sdb1
    Device state: 11
    Volume Name: Data
    Volume State: 91
    Volume Flags: 0x0000
    Volume Version: 3.1
    Sector Size: 512
    Cluster Size: 16384
    Index Block Size: 1024
    Volume Size in Clusters: 23941823
MFT Information 
    MFT Record Size: 1024
    MFT Zone Multiplier: 0
    MFT Data Position: 24
    MFT Zone Start: 284
    MFT Zone End: 2993011
    MFT Zone Position: 284
    Current Position in First Data Zone: 2993011
    Current Position in Second Data Zone: 0
    Allocated clusters 4976 (0,0%)
    LCN of Data Attribute for FILE_MFT: 284
    FILE_MFTMirr Size: 16
    LCN of Data Attribute for File_MFTMirr: 174
    Size of Attribute Definition Table: 2560
    Number of Attached Extent Inodes: 0
FILE_Bitmap Information 
    FILE_Bitmap MFT Record Number: 6
    State of FILE_Bitmap Inode: 80
    Length of Attribute List: 0
    Number of Attached Extent Inodes: 0
FILE_Bitmap Data Attribute Information
    Decompressed Runlist: not done yet
    Base Inode: 6
    Attribute Types: not done yet
    Attribute Name Length: 0
    Attribute State: 3
    Attribute Allocated Size: 2998272
    Attribute Data Size: 2992728
    Attribute Initialized Size: 2992728
    Attribute Compressed Size: 0
    Compression Block Size: 0
    Compression Block Size Bits: 0
    Compression Block Clusters: 0
    Free Clusters: 5340244 (22,3%)
 
fs@fs-hpc:~$ sudo head -c 80 /dev/sda1 | od -t x1
0000000 eb 58 90 4d 53 57 49 4e 34 2e 31 00 02 08 2a 00
0000020 02 00 00 00 00 f8 00 00 3f 00 ff 00 00 08 00 00
0000040 00 00 10 00 ff 03 00 00 00 00 00 00 03 00 00 00
0000060 01 00 06 00 00 00 00 00 00 00 00 00 00 00 00 00
0000100 80 01 29 6d 9b 62 fb 4e 4f 20 4e 41 4d 45 20 20
0000120
 
And this when I have changed block size back to 32KiB using Acronis (so all my files are saved):
 
fs@fs-hpc ~> sudo mount -t ntfs-3g /dev/sdb1 /mnt/data
ntfs_mst_post_read_fixup_warn: magic: 0x44414142  size: 1024   usa_ofs: 0  usa_count: 0: Invalid argument
ntfs_mst_post_read_fixup_warn: magic: 0x44414142  size: 1024   usa_ofs: 0  usa_count: 0: Invalid argument
ntfs_mst_post_read_fixup_warn: magic: 0x44414142  size: 1024   usa_ofs: 0  usa_count: 0: Invalid argument
ntfs_mst_post_read_fixup_warn: magic: 0x44414142  size: 1024   usa_ofs: 0  usa_count: 0: Invalid argument
ntfs_mst_post_read_fixup_warn: magic: 0x44414142  size: 1024   usa_ofs: 0  usa_count: 0: Invalid argument
ntfs_mst_post_read_fixup_warn: magic: 0x44414142  size: 1024   usa_ofs: 0  usa_count: 0: Invalid argument
ntfs_mst_post_read_fixup_warn: magic: 0x44414142  size: 1024   usa_ofs: 0  usa_count: 0: Invalid argument
ntfs_mst_post_read_fixup_warn: magic: 0x44414142  size: 1024   usa_ofs: 0  usa_count: 0: Invalid argument
ntfs_mst_post_read_fixup_warn: magic: 0x44414142  size: 1024   usa_ofs: 0  usa_count: 0: Invalid argument
ntfs_mst_post_read_fixup_warn: magic: 0x44414142  size: 1024   usa_ofs: 0  usa_count: 0: Invalid argument
ntfs_mst_post_read_fixup_warn: magic: 0x44414142  size: 1024   usa_ofs: 0  usa_count: 0: Invalid argument
ntfs_mst_post_read_fixup_warn: magic: 0x44414142  size: 1024   usa_ofs: 0  usa_count: 0: Invalid argument
ntfs_mst_post_read_fixup_warn: magic: 0x44414142  size: 1024   usa_ofs: 0  usa_count: 0: Invalid argument
ntfs_mst_post_read_fixup_warn: magic: 0x44414142  size: 1024   usa_ofs: 0  usa_count: 0: Invalid argument
$MFTMirr does not match $MFT (record 16).
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.
 
 
fs@fs-hpc:~$ sudo head -c 80 /dev/sdb1 | od -t x1
0000000 eb 52 90 4e 54 46 53 20 20 20 20 00 02 40 00 00
0000020 00 00 00 00 00 f8 00 00 3f 00 ff 00 3f 00 00 00
0000040 00 00 00 00 80 00 80 00 c0 57 aa 2d 00 00 00 00
0000060 8e 00 00 00 00 00 00 00 57 00 00 00 00 00 00 00
0000100 f6 00 00 00 f6 00 00 00 60 8d af ef 95 de d4 01
0000120
 
The drive works fine, windows chkdsk sees no errors.
Also, need to say that I have a slightly unnormal partition scheme: the first 100GiB is unallocated (intended as for future experiments), then the actual partition and then some 1MiB unallocated.
Thanks for attention.
 
25.06.2019, 16:55, "Jean-Pierre André" <jean-pierre.an...@wanadoo.fr>:

Иван Омельченко wrote:

 I just have had the same problem as described here
 https://forum.manjaro.org/t/cannot-mount-non-standard-allocation-size-ntfs-partitions/43594
 Changed cluster size from 32K to 16K using Acronis and it works ok now.
 I tried 2017 (f rom Ubuntu and from sources) and 2016 releases - same
 effect as on the link.


How was the partition formatted ? (with which formatting tool ?)
and is this on a 512B or a 4K sectored device ?

Can you please also post the partition header :

As root, replacing sdxx by the name of a partition which cannot
be mounted :
head -c 80 < /dev/sdxx | od -t x1

Jean-Pierre




_______________________________________________
ntfs-3g-devel mailing list
ntfs-3g-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ntfs-3g-devel

_______________________________________________
ntfs-3g-devel mailing list
ntfs-3g-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ntfs-3g-devel

Reply via email to