NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
TickT0ck
Jul 17, 2022Aspirant
ReadyNAS 104 - Volume: Volume data health changed from Degraded to Dead
Hi there, I have a ReadyNAS 104 that has reported the following in the log files: 10 Feb 2022 08:43:34 PM Disk: Disk in channel 1 (Internal) changed state from RESYNC to ONLINE. ...
TickT0ck
Jul 17, 2022Aspirant
Disk 1 looks like this:
The other disks have error rates of Disk 2 = 225, Disk 3 = 197, Disk 4 = 271.
I haven't posted to this forum with a problem for several years, I did however comment a couple of times on another post where someone had had exactly the same error that went unresolved. Rather than keep adding to that one I was advised to create a new post with my issue.
I had a seperate issue several years ago that was resolved - I think someone remote connected to my NAS and fixed something from (aging) memory - however I have since removed those disks and effectively started afresh a few years ago with these WD Red disks.
Cheers,
Gary.
StephenB
Jul 17, 2022Guru - Experienced User
Can you download the log zip file, and the copy/paste disk_info.log in a reply?
- TickT0ckJul 20, 2022Aspirant
Hi StephenB
I have posted a cut/paste of the log three times now, and the message keeps disappearing. I don't know why that should happen but I have taken a screen shot of the log file to see if that works instead.
Cheers,
Gary.
- StephenBJul 20, 2022Guru - Experienced User
Ok. I wasn't sure what you meant by "error rates" in your earlier post - I see it is the ATA error counts. But no other issues (reallocated sectors, pending sectors, uncorrectable errors).
Are you seeing any disks errors or btrfs errors in system.log, kernel.log or systemd-journal.log?
TickT0ck wrote:I have posted a cut/paste of the log three times now, and the message keeps disappearing. I don't know why that should happen
Something in them triggered the automatic spam filter - if this happens again, let me know (either in main thread or in a PM).
- TickT0ckJul 20, 2022Aspirant
The only mention of btrfs is in the systemd-journal log file, it has this:
Jul 10 15:14:44 Bag-of-Holding snapperd[2442]: THROW: open failed path:/data/resilio-sync errno:2 (No such file or directory)
Jul 10 15:14:44 Bag-of-Holding snapperd[2442]: reading failed
Jul 10 15:15:19 Bag-of-Holding readynasd[2241]: ERROR: not a btrfs filesystem: /data
Jul 10 15:15:19 Bag-of-Holding readynasd[2241]: ERROR: not a btrfs filesystem: /data
Jul 10 15:15:19 Bag-of-Holding readynasd[2241]: ERROR: can't access '/data'
Jul 10 15:15:19 Bag-of-Holding readynasd[2241]: btrfs inspect-internal dump-super: too few arguments
Jul 10 15:15:19 Bag-of-Holding readynasd[2241]: usage: btrfs inspect-internal dump-super [options] device [device...]
Jul 10 15:15:19 Bag-of-Holding readynasd[2241]: Dump superblock from a device in a textual form
Jul 10 15:15:19 Bag-of-Holding readynasd[2241]: -f|--full print full superblock information, backup roots etc.
Jul 10 15:15:19 Bag-of-Holding readynasd[2241]: -a|--all print information about all superblocksCheers,
Gary.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!