Schoolbus Vegabond
New Around Here
Greetings.
I recently purchased a WD external USB "Easystore Portable" 5TB drive and I attached it to the USB 3.0 port on the back of the RT-AC68W router running Asuswrt-Merlin version 384.13. It's formatted in NTFS.
No matter what I do, I can't get it to acknowledge it as a media drive in the Media Server section. Putting in the path and hitting apply doesn't work, as it refuses to work. Using "all disks shared" doesn't work either, it won't show up. The Seagate 4TB drive I have plugged into the 2.0 USB port it recognized.
When I scan the drive, I get this error:
Disconnecting the drive and hooking it up to a PC and running CHKDSK shows the drive as clean.
I recently purchased a WD external USB "Easystore Portable" 5TB drive and I attached it to the USB 3.0 port on the back of the RT-AC68W router running Asuswrt-Merlin version 384.13. It's formatted in NTFS.
No matter what I do, I can't get it to acknowledge it as a media drive in the Media Server section. Putting in the path and hitting apply doesn't work, as it refuses to work. Using "all disks shared" doesn't work either, it won't show up. The Seagate 4TB drive I have plugged into the 2.0 USB port it recognized.
When I scan the drive, I get this error:
Code:
ntfsck 3014.5.21
The disk contains an unclean file system (0, 1).
Checking NTFS Superblock ...
The file system wasn't safely closed on Windows. Fixing.
Device name : /dev/sdb2
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 5000928424448 bytes (5000929 MB)
Current device size: 5000928428032 bytes (5000929 MB)
Checking for bad sectors ...
Scanning $MFT ...
Actual VCN (0x0) of index buffer is different from expected VCN (0xe) in inode 0x2b.
Checking directory structure ...
Corrupt directory found, inode=43 (0x2b)
Repairing corrupt directories started.
0.00 percent completed
19.57 percent completed
39.14 percent completed
58.71 percent completed
78.28 percent completed
97.85 percent completed
100.00 percent completed
Repairing corrupt directories completed.
Checking for orphaned files ...
0.00 percent completed
Deleting orphaned inode 16 (0x10)
Deleting orphaned inode 19 (0x13)
Deleting orphaned inode 20 (0x14)
Deleting orphaned inode 21 (0x15)
Deleting orphaned inode 22 (0x16)
Deleting orphaned inode 23 (0x17)
19.57 percent completed
39.14 percent completed
58.71 percent completed
78.28 percent completed
Deleting orphaned inode 498 (0x1f2)
Deleting orphaned inode 499 (0x1f3)
97.85 percent completed
Deleting orphaned inode 500 (0x1f4)
Deleting orphaned inode 501 (0x1f5)
Deleting orphaned inode 502 (0x1f6)
Deleting orphaned inode 503 (0x1f7)
Deleting orphaned inode 506 (0x1fa)
Deleting orphaned inode 507 (0x1fb)
Deleting orphaned inode 508 (0x1fc)
Deleting orphaned inode 509 (0x1fd)
Deleting orphaned inode 510 (0x1fe)
100.00 percent completed
Deleting orphaned inode 511 (0x1ff)
Scanning orphaned files completed.
Checking attributes ...
0.00 percent completed
19.57 percent completed
39.14 percent completed
58.71 percent completed
78.28 percent completed
97.85 percent completed
100.00 percent completed
Failed to calloc 152616224 bytes: Cannot allocate memory
Checking cluster allocation ...
ERROR(12): Failed to setup allocation bitmap: Cannot allocate memory
Syncing device ...Disconnecting the drive and hooking it up to a PC and running CHKDSK shows the drive as clean.
