You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello!
I'm running into a weird problem with this tool. I'm not sure if it's because of the tool or because of how I've tried [re]formatting my disks, but I wanted to make a report here and see if something was up, or if I just really broke my filesystems (or my disks...)
I am leaning toward the idea that my disks may be borked, but I'm stumped as to why all my testing and reports are so inconsistent.
Anyway -
I have a decent number of disks on my local machine, just added three new ones, all formatted as GPT and using NTFS, two of the disks are 18T raw, the third is 20T raw. I seem to only be having this issue with the 18T disks (Model ST18000NM003J-2TV102)
I've tried formatting the disks multiple ways.
Initializing the disk through Windows 10, creating a simple NTFS partition, quick format
After that, I wiped the disk using pv < /dev/zero > /dev/sdb for about 64GiB, used fdisk to create a new GPT partitioning scheme, used mkfs.ntfs will a full zero format to create a new NTFS partition
After that, I wiped the disk again, only by deleting the partitions in gparted, and recreated an NTFS partition using gparted and a quick format
Used pv to zero the first few tens of GB of the disk, used Windows to reinitialize the disk and perform a quick format
Used Windows to convert the partition from NTFS to REFS and back, and performed a quick format.
Between each format or wipe & recreation, I ran through a series of tests, trying to view the MFT, volume info, partition info, defragging, and a few other "misc" non-scientific tests to validate the new partition was functional - and throughout those "tests" is where I found the inconsistencies with ntfstool.
My findings:
chkdsk reports all three disks as healthy/no bad sectors/no bad MFT/etc
analyzing/defragmenting using Ultimate Defrag by Distrix fails on the 18T disks
Sysinternals NTFSInfo reports are nearly identical for all three disks (mainly, I mean, no errors)
fsutil.exe reports for all three disks are nearly identical and no errors are reported.
Active@ Disk Editor reports all three disks are healthy ("Volume Integrity Info" is all ✅ about Primary & Mirror entries for MFT, MFTMrr, LogFile, Volume, Root, BitMap, Boot, etc) --- BUT --- Active@ DE allows editing the boot sectors. For the 20T disk, it reports all is well with the PBS & CBS; for the 18T disks, it reports that both the PBS and CBS have invalid values in hex key 40, "Clusters per MFT record" - with a hex value of F6 - it suggests it should be F4 - cross checking some of my other disks (20T and a few SSDs and some 8T HDDs) - they all have F4 for that key.
ntfstool has some weird reports for the two 18T disks when I query them using ntfstool gpt, but things appear to be "weird" when running it with the info param. Other commands like mft.*, reparse, shell, shadow - also do not work on the 18T disks
Plainly, I just don't understand.
Is this a bug in ntfstool, somehow? or is there a problem with my disks?
Above, I listed a bunch of ways I attempted to format the disks, each iteration seemed to give me the same results (ie, "Invalid or non-GPT partition table" - as well as Distrix UD failures when attempting to defrag), no matter how I wiped nor created the partions.
Willing to provide any further information if needed, I'm also not attempting to look for spoonfeeding help here. If this is some weird bug, I'm more than happy to help out and give info, but if this is because my disks are bad, or my own stupidity, I'll concede without issue.
Thank you in advance, and thanks for such an awesome tool!
The text was updated successfully, but these errors were encountered:
Hello!
I'm running into a weird problem with this tool. I'm not sure if it's because of the tool or because of how I've tried [re]formatting my disks, but I wanted to make a report here and see if something was up, or if I just really broke my filesystems (or my disks...)
I am leaning toward the idea that my disks may be borked, but I'm stumped as to why all my testing and reports are so inconsistent.
Anyway -
I have a decent number of disks on my local machine, just added three new ones, all formatted as GPT and using NTFS, two of the disks are 18T raw, the third is 20T raw. I seem to only be having this issue with the 18T disks (Model ST18000NM003J-2TV102)
I've tried formatting the disks multiple ways.
pv < /dev/zero > /dev/sdb
for about 64GiB, used fdisk to create a new GPT partitioning scheme, usedmkfs.ntfs
will a full zero format to create a new NTFS partitionpv
to zero the first few tens of GB of the disk, used Windows to reinitialize the disk and perform a quick formatBetween each format or wipe & recreation, I ran through a series of tests, trying to view the MFT, volume info, partition info, defragging, and a few other "misc" non-scientific tests to validate the new partition was functional - and throughout those "tests" is where I found the inconsistencies with ntfstool.
My findings:
40
, "Clusters per MFT record" - with a hex value ofF6
- it suggests it should beF4
- cross checking some of my other disks (20T and a few SSDs and some 8T HDDs) - they all haveF4
for that key.ntfstool gpt
, but things appear to be "weird" when running it with theinfo
param. Other commands like mft.*, reparse, shell, shadow - also do not work on the 18T disksI've created a gist where I've dumped a bunch of output from ntfsinfo.
Output of
ntfstool info
: https://gist.github.com/jwshields/403d5b01e430108bd289bf8947325c89#file-ntfstool-infoOutput of
ntfstool gpt
: https://gist.github.com/jwshields/403d5b01e430108bd289bf8947325c89#file-ntfstool-gptI've also created a screenshot of the disk management menu in windows, showing most of my disks; I've highlighted the three I'm focusing though.
Plainly, I just don't understand.
Is this a bug in ntfstool, somehow? or is there a problem with my disks?
Above, I listed a bunch of ways I attempted to format the disks, each iteration seemed to give me the same results (ie, "Invalid or non-GPT partition table" - as well as Distrix UD failures when attempting to defrag), no matter how I wiped nor created the partions.
Willing to provide any further information if needed, I'm also not attempting to look for spoonfeeding help here. If this is some weird bug, I'm more than happy to help out and give info, but if this is because my disks are bad, or my own stupidity, I'll concede without issue.
Thank you in advance, and thanks for such an awesome tool!
The text was updated successfully, but these errors were encountered: