NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
[NVX] "fsck.ext4 for device /dev/c/c exited with signal 9"
Hi all,
since upgrading my NVX from 2 x 3TB to 4 x 3TB I get daily warning messages about disk issues.
Forcing a fsck run results into:
Similar forum threads pointed out to a possible memory issue - my current mem_info.log looks like this:
According to http://www.readynas.com/kb/faq/hardware/is_there_a_way_i_can_verify_if_my_memory_is_good this looks fine.
How do I fix this issue?
Thanks,
Robert
since upgrading my NVX from 2 x 3TB to 4 x 3TB I get daily warning messages about disk issues.
Forcing a fsck run results into:
***** File system check forced at Thu May 2 13:46:12 CEST 2013 *****
fsck 1.41.14 (22-Dec-2010)
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Inode 45573198 has compression flag set on filesystem without compression support. Clear? yes
Inode 45573198 has a bad extended attribute block 1428721365. Clear? yes
...
Illegal block #8 (3851759164) in inode 45579740. CLEARED.
Illegal double indirect block (3173653846) in inode 45579740. CLEARED.
Illegal double indirect block (2700008539) in inode 45579740. CLEARED.
Illegal double indirect block (2678265430) in inode 45579740. CLEARED.
Illegal double indirect block (2346574619) in inode 45579740. CLEARED.
Illegal double indirect block (4109745687) in inode 45579740. CLEARED.
Inode 45579740 is too big. Truncate? yes
Block #8392716 (1275868727) causes directory to be too big. CLEARED.
Warning... fsck.ext4 for device /dev/c/c exited with signal 9.
Similar forum threads pointed out to a possible memory issue - my current mem_info.log looks like this:
MemTotal: 1032080 kB
MemFree: 669340 kB
Buffers: 12700 kB
Cached: 69328 kB
SwapCached: 3188 kB
Active: 83448 kB
Inactive: 44364 kB
Active(anon): 44092 kB
Inactive(anon): 3376 kB
Active(file): 39356 kB
Inactive(file): 40988 kB
Unevictable: 1492 kB
Mlocked: 0 kB
HighTotal: 138952 kB
HighFree: 22088 kB
LowTotal: 893128 kB
LowFree: 647252 kB
SwapTotal: 524272 kB
SwapFree: 520616 kB
Dirty: 148 kB
Writeback: 0 kB
AnonPages: 44144 kB
Mapped: 10804 kB
Shmem: 196 kB
Slab: 22680 kB
SReclaimable: 10192 kB
SUnreclaim: 12488 kB
KernelStack: 624 kB
PageTables: 608 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 1040312 kB
Committed_AS: 146844 kB
VmallocTotal: 122880 kB
VmallocUsed: 636 kB
VmallocChunk: 121188 kB
DirectMap4k: 8184 kB
DirectMap4M: 901120 kB
According to http://www.readynas.com/kb/faq/hardware/is_there_a_way_i_can_verify_if_my_memory_is_good this looks fine.
Firmware RAIDiator 4.2.22
Disk- 1 Seagate ST33000650NS 2794 GB , SMART+ OK
Disk- 2 Seagate ST33000650NS 2794 GB , SMART+ OK
Disk- 3 Seagate ST33000650NS 2794 GB , SMART+ OK
Disk- 4 Seagate ST33000650NS 2794 GB , SMART+ OK
How do I fix this issue?
Thanks,
Robert
2 Replies
Replies have been turned off for this discussion
- What version of RAIDiator are you running? Expansion on 32-bit systems such as the NVX is dangerous on 4.2.20-4.2.22. I assume you are sadly running one of those firmware releases?
Please contact NetGar support for assistance (See the Online Submission link in my sig), post your case number and do not run another filesystem check. You should only run such a check if support suggests that you do.
The best advice if you can access your data is to backup that data, verify manually if it is corrupted or not and do a factory default on 4.2.19 or 4.2.23 (the latter is due to be released soon) and restore your data from backup. - thanks mdgm - ofc its 4.2.22 - I'll contact the NetGear support
Robert
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
