NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Scrub started/completed and no other messages
I completed a scrub today on a RN214, and the log looks pretty sparse: 17 Aug 2023 19:11:40 Volume: Scrub completed for volume data'. 16 Aug 2023 14:46:03 Volume: Scrub started for volume data. ...
btrfs.log appears clean - no errors.
I jumped in to systemd-journal.log and searched 'scrub' - here is a snippet:
Aug 16 14:46:04 NETDISK4 readynasd[2239]: scrub started on /data, fsid ** replaced ** (pid=18925)
Aug 16 14:46:03 NETDISK4 readynasd[2239]: Scrub started for volume data.
Aug 16 14:46:06 NETDISK4 msmtpq[18950]: mail for ** replaced ** : send was successful
Aug 16 14:47:22 NETDISK4 connmand[2127]: ntp: adjust (slew): -0.002244 sec
Aug 16 14:49:36 NETDISK4 kernel: BTRFS warning (device md124): i/o error at logical 7526547456 on dev /dev/md127, sector 16813824, root 278, inode 880, offset 734523392, length 4096, links 1 (path: Documents/ ** replaced ** 00037.MTS)
Aug 16 14:49:36 NETDISK4 kernel: BTRFS warning (device md124): i/o error at logical 7526285312 on dev /dev/md127, sector 16813312, root 278, inode 880, offset 734261248, length 4096, links 1 (path: Documents/ ** replaced ** 00037.MTS)
Aug 16 14:49:36 NETDISK4 kernel: BTRFS warning (device md124): i/o error at logical 7526023168 on dev /dev/md127, sector 16812800, root 278, inode 880, offset 733999104, length 4096, links 1 (path: Documents/ ** replaced ** 00037.MTS)
Aug 16 14:49:36 NETDISK4 kernel: BTRFS warning (device md124): i/o error at logical 7525761024 on dev /dev/md127, sector 16812288, root 278, inode 880, offset 733736960, length 4096, links 1 (path: Documents/ ** replaced ** 00037.MTS)
Aug 16 14:49:36 NETDISK4 kernel: BTRFS error (device md124): bdev /dev/md127 errs: wr 0, rd 1, flush 0, corrupt 0, gen 0
Aug 16 14:49:36 NETDISK4 kernel: BTRFS error (device md124): bdev /dev/md127 errs: wr 0, rd 2, flush 0, corrupt 0, gen 0
Aug 16 14:49:36 NETDISK4 kernel: BTRFS error (device md124): bdev /dev/md127 errs: wr 0, rd 3, flush 0, corrupt 0, gen 0
Aug 16 14:49:36 NETDISK4 kernel: BTRFS error (device md124): bdev /dev/md127 errs: wr 0, rd 4, flush 0, corrupt 0, gen 0
Aug 16 14:49:36 NETDISK4 kernel: BTRFS warning (device md124): i/o error at logical 7526809600 on dev /dev/md127, sector 16814336, root 278, inode 880, offset 734785536, length 4096, links 1 (path: Documents/ ** replaced ** 00037.MTS)
Aug 16 14:49:36 NETDISK4 kernel: BTRFS error (device md124): bdev /dev/md127 errs: wr 0, rd 5, flush 0, corrupt 0, gen 0
Aug 16 14:49:36 NETDISK4 kernel: ------------[ cut here ]------------
That looks a bit worrying, albeit only a single file (0037.MTS) - which I could recover from a backup if it is in fact damaged. Should I interpret these entries as non-recoverable read errors?
aks-2 wrote:
That looks a bit worrying, albeit only a single file (0037.MTS) - which I could recover from a backup if it is in fact damaged. Should I interpret these entries as non-recoverable read errors?
Personally I'd delete the file and restore it from the backup. Then re-run the scrub, and see if the problem disappears.
Though maybe also compare the backup copy with the one on the NAS. (Even if it matches, I'd delete the NAS copy).
Oh, I tried to copy that file to another area, that failed:
cp: error reading ' ** removed ** /00037.MTS': Input/output error
This is intriguing, no self recovery/error protection saved this file, RAID5 and BTRFS. My understanding is obviously incorrect. I will now dig out the backups and find that file.
How do I determine the type of failure, no disk errors are reported in the logs, this is a bit worrying to me as don't understand the cause behind the error. Any suggestions where I start to look?
I recovered the file from backups - my daughter playing in a concert!
I remain concerned, here's why:
- Copying the errored file from Windows (NAS to desktop), the copy succeeded without error. Whilst the video file played, there was a small corruption part way through. It seems video files can be quite resilient to small corruptions.
- Alarming is that the NAS provides no obvious indication that there is a problem with the file.
- Only if you dig through system logs do you get a hint, thankfully (and by chance) I did that.
- I could have easily recycled my backup drives and overwritten the good file with a new backup containing the bad file.
I am running a "disk test" on the RN214, I have no indication when that will finish.
I am still wondering if this is a one off error, or if there is a bigger problem brewing. Any thoughts on how I progress?
Hard to say what happened here, or when it might have happened.
You could do a factory reset, but keep in mind that if there are other errored files they could be errored on your backup as well.
Another option would be to try to verify the backup (comparing each file in the NAS with the backup). You can create a script to do that, but there are also some free software tools that will also do it. I haven't used teracopy for a while, but I believe that has a verify feature - computing checksums on each file in the source and destination, and making sure they match.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
