NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNAS crash on Balance task
Hi guys,
A couple of times now my ReadyNAS Pro 6 has completely locked up during a BTRFS Balance task. It's only recently been set up, so I've never actually had a balance go to full completion...
Ah, good to know. I only do them once a month as a "good measure" because I know how BTRFS can be when it doesn't get the necessary TLC.
Great point about the disks, I'm aware of one that had ATA errors but the number hasn't changed (sitting on 10 currently). Is that a cause for concern? I've now found 2 more with ATA errors though, sitting on a count of 1 and 2. All the other counters are sitting on 0 for all disks:
Reallocated Sectors: 0
Reallocation Events: 0
Spin Retry Count: 0
Current Pending Sector Count: 0
Uncorrectable Sector Count: 0
Once the resync completes I'll disconnect the LUNs and try a scrub, will report back here on how it goes.
Thanks!
dojobel wrote:
Great point about the disks, I'm aware of one that had ATA errors but the number hasn't changed (sitting on 10 currently). Is that a cause for concern? I've now found 2 more with ATA errors though, sitting on a count of 1 and 2. All the other counters are sitting on
I'd keep an eye on the ATA errors, but I wouldn't be concerned if the counts aren't rising.
Alright guys, the scrub has completed and everything is OK. I'll shut down my VMs later tonight as a precaution and try another Balance.
As a side note, I actually have another NAS (ReadyNAS Pro 4) which is Kernel Panicking, which I thought was related to lack of RAM, but it's still occurring since upgrading to the max (2GB). I checked the logs after the most recent crash, and it's actually started a BTRFS Balance task just prior to the crash, the same as this one. The difference is the Pro 4 actually (very cleverly) prints part of the Kernel Panic reason onto the LCD, the message is:
_raw_spin_lock_bh+16
I have another thread going for that NAS, since at the time I didn't know the two problems were related:
2GB Memory is not the max for a Pro 4, I have 4GB happily installed
bedlam1 wrote:
2GB Memory is not the max for a Pro 4, I have 4GB happily installed
ah, I was going off what dmidecode was telling me :)
# dmidecode --type 16
# dmidecode 2.12
SMBIOS 2.6 present.Handle 0x0009, DMI type 16, 15 bytes
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None
Maximum Capacity: 2 GB
Error Information Handle: Not Provided
Number Of Devices: 1
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
