NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Bitrot detected in system files?
Hi everyone,
I have a RN312 with a fresh volume synced and data copied to it. I have been trying to create a second volume in my eda500 expansion enclosure but I'm having problems. I have formatted the 5 drives within and once it gets to about 80% resynced it starts emailing me bitrot error. I can understand bitrot detection in files I am storing, but how can there be bitrot errors in system files?
Bit rot has detected an error within //var/readynasd/loadavg.dat and cannot correct the error.
Bit rot has detected an error within //var/log/readynasd/fwbroker.log and cannot correct the error.
Bit rot has detected an error within //var/log/frontview/status.log and cannot correct the error.
Bit rot has detected an error within //var/lib/dpkg/status and cannot correct the error.
I checked your logs your sent on 7/14,
there are below btrfs warning
Jul 12 18:20:48 86NAS kernel: BTRFS warning (device md127): csum failed ino 6135 off 916283392 csum 4121951051 expected csum 965293194
Jul 12 18:20:48 86NAS mdcsrepaird[2917]: mdcsrepaird: mdcsrepair /dev/md127 2359372374016 4096 b404500a 75cb76c6 /readynas/86/movies/dvd/SLAP_SHOT/VIDEO_TS/VTS_01_6.VOB
Jul 12 18:20:48 86NAS kernel: BTRFS warning (device md127): csum failed ino 6135 off 916283392 csum 4121951051 expected csum 965293194
Jul 12 18:20:48 86NAS kernel: BTRFS warning (device md127): csum failed ino 6135 off 916283392 csum 4121951051 expected csum 965293194Cloud do you please enable diagnostic mode and PM me 5 debug codes? Let us remote access to check filesystem.
RAIDar Secure diagnostic
https://kb.netgear.com/27391/ReadyNAS-RAIDar-6-0
or enable secure diagnosticn in NAS admin GUI =>System=>Settings=>Support
4 Replies
Replies have been turned off for this discussion
some more logs. It's about .3% away from finishing syncing. Not sure if I should even use this volume after all these errors.
Wed Sep 5 2018 10:57:27 Volume: Bit rot has detected an error within //var/log/frontview/status.log and cannot correct the error. Wed Sep 5 2018 4:20:27 Volume: Bit rot has detected an error within //var/lib/dpkg/status and cannot correct the error. Tue Sep 4 2018 10:57:28 Volume: Bit rot has detected an error within //var/log/frontview/status.log and cannot correct the error. Mon Sep 3 2018 20:26:49 Volume: Bit rot has detected an error within //var/lib/dpkg/status and cannot correct the error. Mon Sep 3 2018 20:26:46 Volume: Bit rot has detected an error within //var/log/readynasd/fwbroker.log and cannot correct the error. Mon Sep 3 2018 20:26:45 Volume: Bit rot has detected an error within //var/readynasd/loadavg.dat and cannot correct the error. Mon Sep 3 2018 20:26:44 Volume: Bit rot has detected an error within //var/log/frontview/msmtp.log and cannot correct the error. Mon Sep 3 2018 20:26:42 Volume: Bit rot has detected an error within //var/log/frontview/status.log and cannot correct the error. Mon Sep 3 2018 20:26:41 Volume: Bit rot has detected an error within //var/log/frontview/msmtp.log and cannot correct the error. Mon Sep 3 2018 20:26:39 Volume: Bit rot has detected an error within //var/readynasd/loadavg.dat and cannot correct the error. Mon Sep 3 2018 20:26:38 Volume: Bit rot has detected an error within //var/log/readynasd/fwbroker.log and cannot correct the error. Mon Sep 3 2018 20:26:35 Volume: Bit rot has detected an error within //var/log/frontview/status.log and cannot correct the error. Mon Sep 3 2018 20:25:38 Volume: Bit rot has detected an error within //var/readynasd/loadavg.dat and cannot correct the error. Mon Sep 3 2018 20:25:25 Volume: Bit rot has detected an error within //var/log/readynasd/fwbroker.log and cannot correct the error.
Blanker-2 wrote:
some more logs. It's about .3% away from finishing syncing. Not sure if I should even use this volume after all these errors.
The file system corruption on the OS partition. Normally that's mirrored on all disks - likely it's just the RN312 disks, but it might be worth confirming that the EDA500 disks aren't in that array. Perhaps look in mdstat.log, and tell us what disks are included in /dev/md0.
Did you purchase the RN312 new between 1 June 2014 and 31 May 2016? If you did, you have free lifetime chat support - might be worth using for this.
I checked your logs your sent on 7/14,
there are below btrfs warning
Jul 12 18:20:48 86NAS kernel: BTRFS warning (device md127): csum failed ino 6135 off 916283392 csum 4121951051 expected csum 965293194
Jul 12 18:20:48 86NAS mdcsrepaird[2917]: mdcsrepaird: mdcsrepair /dev/md127 2359372374016 4096 b404500a 75cb76c6 /readynas/86/movies/dvd/SLAP_SHOT/VIDEO_TS/VTS_01_6.VOB
Jul 12 18:20:48 86NAS kernel: BTRFS warning (device md127): csum failed ino 6135 off 916283392 csum 4121951051 expected csum 965293194
Jul 12 18:20:48 86NAS kernel: BTRFS warning (device md127): csum failed ino 6135 off 916283392 csum 4121951051 expected csum 965293194Cloud do you please enable diagnostic mode and PM me 5 debug codes? Let us remote access to check filesystem.
RAIDar Secure diagnostic
https://kb.netgear.com/27391/ReadyNAS-RAIDar-6-0
or enable secure diagnosticn in NAS admin GUI =>System=>Settings=>Support
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
