Corrupted Directory NAS

[PARC]

Hi guys, I hope you could help me out here with my problem.

This morning I saw this error:



I tried running a repair for both router and PC.

Router's Scan result:

ntfsck 3014.5.21
Checking NTFS Superblock ...
Device name : /dev/sda1
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 2000365285888 bytes (2000366 MB)
Current device size: 2000365288448 bytes (2000366 MB)
Checking for bad sectors ...
Scanning $MFT ...
Index root attribute missing in directory inode 2512: No such file or directory
Checking directory structure ...
Corrupt directory found, inode=2512 (0x9d0)
Repairing corrupt directories started.
0.00 percent completed
1.10 percent completed
2.20 percent completed
3.29 percent completed
4.39 percent completed
5.49 percent completed
6.59 percent completed
7.69 percent completed
8.79 percent completed
9.88 percent completed
10.98 percent completed
12.08 percent completed
13.18 percent completed
14.28 percent completed
15.38 percent completed
16.47 percent completed
17.57 percent completed
18.67 percent completed
19.77 percent completed
20.87 percent completed
21.97 percent completed
23.06 percent completed
24.16 percent completed
25.26 percent completed
26.36 percent completed
27.46 percent completed
28.56 percent completed
29.65 percent completed
30.75 percent completed
31.85 percent completed
32.95 percent completed
34.05 percent completed
35.15 percent completed
36.24 percent completed
37.34 percent completed
38.44 percent completed
39.54 percent completed
40.64 percent completed
41.74 percent completed
42.83 percent completed
43.93 percent completed
45.03 percent completed
46.13 percent completed
47.23 percent completed
48.33 percent completed
49.42 percent completed
50.52 percent completed
51.62 percent completed
52.72 percent completed
53.82 percent completed
54.91 percent completed
56.01 percent completed
57.11 percent completed
58.21 percent completed
59.31 percent completed
60.41 percent completed
61.50 percent completed
62.60 percent completed
63.70 percent completed
64.80 percent completed
65.90 percent completed
67.00 percent completed
68.09 percent completed
69.19 percent completed
70.29 percent completed
71.39 percent completed
72.49 percent completed
73.59 percent completed
74.68 percent completed
75.78 percent completed
76.88 percent completed
77.98 percent completed
79.08 percent completed
80.18 percent completed
81.27 percent completed
82.37 percent completed
83.47 percent completed
84.57 percent completed
85.67 percent completed
86.77 percent completed
87.86 percent completed
88.96 percent completed
90.06 percent completed
91.16 percent completed
92.26 percent completed
93.36 percent completed
94.45 percent completed
95.55 percent completed
96.65 percent completed
97.75 percent completed
98.85 percent completed
99.95 percent completed
100.00 percent completed
ntfsck::ntfs_readdir_recursive(): cannot get inode for 7251.
Repairing corrupt directories completed.
Corrupt directory found, inode=2512 (0x9d0)
Syncing device ...


For the PC under windows repair was also a success.

But still getting the same error when I tried scanning for error via router (BTW I'm using the AC88U). Is there a way to find this specific corrupted directory ? Thank you very much in advance.

 

[L&LD]

I think your best chance of fixing this is by scanning and fixing the drive on a computer. The router is simply not powerful enough if I recall correctly.

 

[PARC]

I think your best chance of fixing this is by scanning and fixing the drive on a computer. The router is simply not powerful enough if I recall correctly.

Hi , I did that also using Window's Disk Tool - Scan & Repair, and I still get this warning after re-mounting and scanning it

 

[Zonkd]

Hi , I did that also using Window's Disk Tool - Scan & Repair, and I still get this warning after re-mounting and scanning it View attachment 16284

How old is the HDD? What brand? A bad sector error may suggest the drive is failing. To avoid data loss do a full data backup (I hope you already do this because HDDs fail unexpectedly all the time). The next step is run a SMART test on it and see if it passes. Bad sectors do occur over time and normally the host OS will just remap the sector so it isn't used anymore. The Windows repair tool probably did that for you. I'm not sure why the router would still have a problem with it. Reboot the router to clear its cache. If you've done the data backup and it still works while connected to router then you could just forget about it and continue using it until it fails. However if the router does continue writing to that bad sector you could continue to wind up with some corrupt files and directories.

FYI: buying a proper NAS device with a few bays preferably running RAID 5 or RAID 6 for redundancy would make problems like this less of a drama. The router isn't a great replacement for a proper NAS.

 

[PARC]

How old is the HDD? What brand? A bad sector error may suggest the drive is failing. To avoid data loss do a full data backup (I hope you already do this because HDDs fail unexpectedly all the time). The next step is run a SMART test on it and see if it passes. Bad sectors do occur over time and normally the host OS will just remap the sector so it isn't used anymore. The Windows repair tool probably did that for you. I'm not sure why the router would still have a problem with it. Reboot the router to clear its cache. If you've done the data backup and it still works while connected to router then you could just forget about it and continue using it until it fails. However if the router does continue writing to that bad sector you could continue to wind up with some corrupt files and directories.

FYI: buying a proper NAS device with a few bays preferably running RAID 5 or RAID 6 for redundancy would make problems like this less of a drama. The router isn't a great replacement for a proper NAS.

Thanks Zonkd, yup already did a backup of the all the files from that HDD, by the way its a WD 2TB My Passport HDD.

 

[L&LD]

Given that you have a full backup of the drive, I would do a complete reformat and see if it fixes this issue. If it doesn't, it may be time for a new drive.

This is why these checks are there. If they keep repeatedly showing up and we repeatedly ignore them, it may come back to bite us on our backside.

 

[sfx2000]

But still getting the same error when I tried scanning for error via router (BTW I'm using the AC88U). Is there a way to find this specific corrupted directory ? Thank you very much in advance.

In Linux - the Filesystem is probably still marked dirty...

NTFS is loaded by a third party module - and large drives, as you've noticed, take a bit of RAM...

What caused the FS issue - probably a hard/dirty shutdown - drive might be ok, but check the SMART stats to be sure...

With HDD's - always best to use ext3 or ext4 with journaling - makes things easier to clean up.

 

[PARC]

Thank guys everything is back to normal, I just have to backup the old HDD and reformat it again and copied back the the files to the HDD.

@sfx2000 - I think it was a dirty shutdown that caused that error, as far as I remember this error started to appear just after a firmware update i did couple days ago without removing the drive.