Good morning-
I have a 4TB USB drive (WD Passport) attached to my router (RT-AC68U) and Merlin (380.65) is reporting that there's an issue with the drive (even though it's brand new). When Merlin scans the drive, it gives me the following (detailed status removed to keep the log output short):
When I attach this same drive to my (Windows) laptop and run a chkdsk, it says, "Windows has scanned the file system and found no problems. No further action is required."
Is there a way for me to either scan this drive with Merlin or a flavor of Linux that will allow it to be "fixed" in such a way that Merlin will be happy again?
Thank you!!
I have a 4TB USB drive (WD Passport) attached to my router (RT-AC68U) and Merlin (380.65) is reporting that there's an issue with the drive (even though it's brand new). When Merlin scans the drive, it gives me the following (detailed status removed to keep the log output short):
Code:
ntfsck 3014.5.21
Checking NTFS Superblock ...
Device name : /dev/sda1
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 4000750498304 bytes (4000751 MB)
Current device size: 4000750501888 bytes (4000751 MB)
Checking for bad sectors ...
Scanning $MFT ...
Actual VCN (0x0) of index buffer is different from expected VCN (0x24) in inode 0x2efd.
Actual VCN (0x0) of index buffer is different from expected VCN (0x45) in inode 0x330b.
Checking directory structure ...
Corrupt directory found, inode=12029 (0x2efd)
Corrupt directory found, inode=13067 (0x330b)
Repairing corrupt directories started.
0.00 percent completed
100.00 percent completed
Repairing corrupt directories completed.
Repairing corrupt directories started.
0.00 percent completed
100.00 percent completed
Actual VCN (0x0) of index buffer is different from expected VCN (0x7d) in inode 0x351e.
Actual VCN (0x0) of index buffer is different from expected VCN (0x15) in inode 0x38d0.
Repairing corrupt directories completed.
Corrupt directory found, inode=13598 (0x351e)
Corrupt directory found, inode=14544 (0x38d0)
Repairing corrupt directories started.
0.00 percent completed
100.00 percent completed
Repairing corrupt directories completed.
Repairing corrupt directories started.
0.00 percent completed
100.00 percent completed
this seems to be endless.
Repairing corrupt directories completed.
Checking for orphaned files ...
0.00 percent completed
99.53 percent completed
Adding orphaned inode 181440 (0x2c4c0) to directory 5 (0x5)
99.58 percent completed
99.64 percent completed
99.69 percent completed
Adding orphaned inode 181737 (0x2c5e9) to directory 181440 (0x2c4c0)
99.74 percent completed
99.80 percent completed
99.85 percent completed
99.91 percent completed
99.96 percent completed
100.00 percent completed
Scanning orphaned files completed.
Checking attributes ...
0.00 percent completed
100.00 percent completed
Failed to calloc 122093216 bytes: Cannot allocate memory
Checking cluster allocation ...
ERROR(12): Failed to setup allocation bitmap: Cannot allocate memory
Syncing device ...
When I attach this same drive to my (Windows) laptop and run a chkdsk, it says, "Windows has scanned the file system and found no problems. No further action is required."
Is there a way for me to either scan this drive with Merlin or a flavor of Linux that will allow it to be "fixed" in such a way that Merlin will be happy again?
Thank you!!