I wonder if anyone has ever come across similar issue. On attempt to access any of my network folders I get the following message:
Windows cannot access \\ip\folder
Check the spelling of the name. Otherwise, there might be a problem with your network. To try to identify and resolve network problems, click Diagnose.
See the picture below (message and shares in a browser):
I checked my disks if they were OK under another system via FSproxy in read-only mode: both disks are fine.
I tried several times "scan" and "scan and repair" functions from browser but it gave no effect at all.
The output of "scan" but I can hardly get anything out of it:
Code: Select all
Scan Result Phase 1 - find and verify superblock... Phase 2 - using internal log - scan filesystem freespace and inode maps... agf_freeblks 4294967293 counted 13 in ag 1 sb_fdblocks 18134174 counted 18134190 - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 - agno = 3 No modify flag set skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set skipping filesystem flush and exiting.
fsck applied to /dev/loop0:
Code: Select all
fsck from util-linux 2.20 e2fsck 1.41.14 (22-Dec-2010) /dev/loop0 is mounted. e2fsck: Cannot continue, aborting
My configuration: NSA221, firmware: 4.41 (AFM.0).
Is it the latest firmware?
Any help would be greatly appreciated.