NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
kuriko898
Mar 30, 2013Follower
Duo v2 volume scan found and corrected errors
I purchased a ReadyNAS Duo v2 a few days ago and set it up with 2 WD30EFRX drives (these are on the HCL). The firmware version is 5.3.7. If the NAS reboots and does a file system check after a large amount of files have been written to it, error similar to the following occurs. I've tried doing a factory reset but this didn't fix the problem.
Reading through the forums, I've noticed that there were other threads started about this issue. Below are a few of them:
http://www.readynas.com/forum/viewtopic.php?f=10&t=60083
https://www.readynas.com/forum/viewtopic.php?t=69815&p=387327
http://www.readynas.com/forum/viewtopic.php?f=7&t=62232
However, none of them have any answers or solutions to the problem. Does anyone have any insight? Is this something to worry about?
***** File system check forced at Sat Mar 30 09:53:54 PDT 2013 *****
fsck from util-linux-ng 2.17.2
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Inode 8192022, i_blocks is 872496, should be 872504. Fix? yes
Inode 8192023, i_blocks is 714984, should be 714992. Fix? yes
Inode 8192024, i_blocks is 647304, should be 647312. Fix? yes
Inode 8192025, i_blocks is 785976, should be 785984. Fix? yes
Inode 8192026, i_blocks is 680472, should be 680480. Fix? yes
Inode 8192027, i_blocks is 736648, should be 736656. Fix? yes
Inode 8192028, i_blocks is 636840, should be 636848. Fix? yes
Inode 8192029, i_blocks is 852960, should be 852968. Fix? yes
Inode 8192030, i_blocks is 735200, should be 735208. Fix? yes
Inode 8192031, i_blocks is 753312, should be 753320. Fix? yes
Inode 8192032, i_blocks is 731448, should be 731456. Fix? yes
Inode 8192033, i_blocks is 748656, should be 748664. Fix? yes
Inode 8192084, i_blocks is 667816, should be 667824. Fix? yes
Inode 8192085, i_blocks is 636504, should be 636512. Fix? yes
Inode 8192086, i_blocks is 628224, should be 628232. Fix? yes
Inode 8192087, i_blocks is 708832, should be 708840. Fix? yes
Inode 8192088, i_blocks is 752360, should be 752368. Fix? yes
Inode 8192089, i_blocks is 699632, should be 699640. Fix? yes
Inode 8192090, i_blocks is 616416, should be 616424. Fix? yes
Inode 8192091, i_blocks is 678960, should be 678968. Fix? yes
Inode 8192092, i_blocks is 645984, should be 645992. Fix? yes
Inode 8192093, i_blocks is 651624, should be 651632. Fix? yes
Inode 8192094, i_blocks is 633456, should be 633464. Fix? yes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/mapper/c-c: ***** FILE SYSTEM WAS MODIFIED *****
/dev/mapper/c-c: 222/45547520 files (0.9% non-contiguous), 20709339/728760320 blocks
Reading through the forums, I've noticed that there were other threads started about this issue. Below are a few of them:
http://www.readynas.com/forum/viewtopic.php?f=10&t=60083
https://www.readynas.com/forum/viewtopic.php?t=69815&p=387327
http://www.readynas.com/forum/viewtopic.php?f=7&t=62232
However, none of them have any answers or solutions to the problem. Does anyone have any insight? Is this something to worry about?
1 Reply
Replies have been turned off for this discussion
- evan2NETGEAR ExpertWe have fixed the issue, please wait for 5.3.8 release
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!