NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNAS Pro 6 crashed again
Hello all, My ReadyNAS Pro6 periodically stops responding to the network. When that happens I can push the button to shutdown it but it will sit on "shutting down" forever and then I'll have to p...
This is MD126
root@Enterprise-NAS:~# btrfs check --force /dev/md126
WARNING: filesystem mounted, continuing because of --force
Checking filesystem on /dev/md126
UUID: 256f20f5-bce4-4561-91a8-f5efb92f82fe
checking extents
checking free space cache
checking fs roots
root 17467 inode 1177157 errors 100, file extent discount
Found file extent holes:
start: 4915200, len: 40960
start: 4980736, len: 36864
start: 5103616, len: 65536
start: 5242880, len: 65536
start: 5365760, len: 45056
start: 5439488, len: 53248
start: 5509120, len: 40960
start: 5570560, len: 28672
start: 5701632, len: 57344
start: 5763072, len: 61440
start: 5828608, len: 65536
start: 5902336, len: 61440
start: 6025216, len: 118784
start: 6156288, len: 12288
start: 6217728, len: 28672
start: 6287360, len: 45056
start: 6356992, len: 16384
start: 6426624, len: 8192
start: 6483968, len: 20480
start: 6557696, len: 24576
start: 6623232, len: 32768
start: 6680576, len: 61440
start: 6750208, len: 20480
start: 6815744, len: 40960
start: 6881280, len: 24576
start: 6938624, len: 57344
start: 7012352, len: 135168
start: 7200768, len: 53248
start: 7274496, len: 53248
start: 7405568, len: 57344
start: 7471104, len: 45056
start: 7598080, len: 61440
start: 7729152, len: 40960
start: 7790592, len: 32768
start: 7921664, len: 28672
start: 7983104, len: 49152
start: 8060928, len: 36864
start: 8183808, len: 32768
start: 8253440, len: 53248
start: 8323072, len: 49152
start: 8388608, len: 16384
start: 8454144, len: 49152
start: 8519680, len: 16384
start: 8585216, len: 40960
start: 8642560, len: 61440
start: 8716288, len: 12288
start: 8781824, len: 20480
start: 8843264, len: 49152
start: 8904704, len: 61440
start: 9043968, len: 73728
start: 9166848, len: 53248
start: 9232384, len: 73728
start: 9367552, len: 24576
start: 9424896, len: 36864
start: 9572352, len: 40960
start: 9625600, len: 36864
start: 9695232, len: 65536
start: 9830400, len: 94208
root 17495 inode 1177157 errors 100, file extent discount
Found file extent holes:
start: 4915200, len: 40960
start: 4980736, len: 36864
start: 5103616, len: 65536
start: 5242880, len: 65536
start: 5365760, len: 45056
start: 5439488, len: 53248
start: 5509120, len: 40960
start: 5570560, len: 28672
start: 5701632, len: 57344
start: 5763072, len: 61440
start: 5828608, len: 65536
start: 5902336, len: 61440
start: 6025216, len: 118784
start: 6156288, len: 12288
start: 6217728, len: 28672
start: 6287360, len: 45056
start: 6356992, len: 16384
start: 6426624, len: 8192
start: 6483968, len: 20480
start: 6557696, len: 24576
start: 6623232, len: 32768
start: 6680576, len: 61440
start: 6750208, len: 20480
start: 6815744, len: 40960
start: 6881280, len: 24576
start: 6938624, len: 57344
start: 7012352, len: 135168
start: 7200768, len: 53248
start: 7274496, len: 53248
start: 7405568, len: 57344
start: 7471104, len: 45056
start: 7598080, len: 61440
start: 7729152, len: 40960
start: 7790592, len: 32768
start: 7921664, len: 28672
start: 7983104, len: 49152
start: 8060928, len: 36864
start: 8183808, len: 32768
start: 8253440, len: 53248
start: 8323072, len: 49152
start: 8388608, len: 16384
start: 8454144, len: 49152
start: 8519680, len: 16384
start: 8585216, len: 40960
start: 8642560, len: 61440
start: 8716288, len: 12288
start: 8781824, len: 20480
start: 8843264, len: 49152
start: 8904704, len: 61440
start: 9043968, len: 73728
start: 9166848, len: 53248
start: 9232384, len: 73728
start: 9367552, len: 24576
start: 9424896, len: 36864
start: 9572352, len: 40960
start: 9625600, len: 36864
start: 9695232, len: 65536
start: 9830400, len: 94208
root 17894 inode 1177157 errors 100, file extent discount
Found file extent holes:
start: 4915200, len: 40960
start: 4980736, len: 36864
start: 5103616, len: 65536
start: 5242880, len: 65536
start: 5365760, len: 45056
start: 5439488, len: 53248
start: 5509120, len: 40960
start: 5570560, len: 28672
start: 5701632, len: 57344
start: 5763072, len: 61440
start: 5828608, len: 65536
start: 5902336, len: 61440
start: 6025216, len: 118784
start: 6156288, len: 12288
start: 6217728, len: 28672
start: 6287360, len: 45056
start: 6356992, len: 16384
start: 6426624, len: 8192
start: 6483968, len: 20480
start: 6557696, len: 24576
start: 6623232, len: 32768
start: 6680576, len: 61440
start: 6750208, len: 20480
start: 6815744, len: 40960
start: 6881280, len: 24576
start: 6938624, len: 57344
start: 7012352, len: 135168
start: 7200768, len: 53248
start: 7274496, len: 53248
start: 7405568, len: 57344
start: 7471104, len: 45056
start: 7598080, len: 61440
start: 7729152, len: 40960
start: 7790592, len: 32768
start: 7921664, len: 28672
start: 7983104, len: 49152
start: 8060928, len: 36864
start: 8183808, len: 32768
start: 8253440, len: 53248
start: 8323072, len: 49152
start: 8388608, len: 16384
start: 8454144, len: 49152
start: 8519680, len: 16384
start: 8585216, len: 40960
start: 8642560, len: 61440
start: 8716288, len: 12288
start: 8781824, len: 20480
start: 8843264, len: 49152
start: 8904704, len: 61440
start: 9043968, len: 73728
start: 9166848, len: 53248
start: 9232384, len: 73728
start: 9367552, len: 24576
start: 9424896, len: 36864
start: 9572352, len: 40960
start: 9625600, len: 36864
start: 9695232, len: 65536
start: 9830400, len: 94208
root 17919 inode 1177157 errors 100, file extent discount
Found file extent holes:
start: 4915200, len: 40960
start: 4980736, len: 36864
start: 5103616, len: 65536
start: 5242880, len: 65536
start: 5365760, len: 45056
start: 5439488, len: 53248
start: 5509120, len: 40960
start: 5570560, len: 28672
start: 5701632, len: 57344
start: 5763072, len: 61440
start: 5828608, len: 65536
start: 5902336, len: 61440
start: 6025216, len: 118784
start: 6156288, len: 12288
start: 6217728, len: 28672
start: 6287360, len: 45056
start: 6356992, len: 16384
start: 6426624, len: 8192
start: 6483968, len: 20480
start: 6557696, len: 24576
start: 6623232, len: 32768
start: 6680576, len: 61440
start: 6750208, len: 20480
start: 6815744, len: 40960
start: 6881280, len: 24576
start: 6938624, len: 57344
start: 7012352, len: 135168
start: 7200768, len: 53248
start: 7274496, len: 53248
start: 7405568, len: 57344
start: 7471104, len: 45056
start: 7598080, len: 61440
start: 7729152, len: 40960
start: 7790592, len: 32768
start: 7921664, len: 28672
start: 7983104, len: 49152
start: 8060928, len: 36864
start: 8183808, len: 32768
start: 8253440, len: 53248
start: 8323072, len: 49152
start: 8388608, len: 16384
start: 8454144, len: 49152
start: 8519680, len: 16384
start: 8585216, len: 40960
start: 8642560, len: 61440
start: 8716288, len: 12288
start: 8781824, len: 20480
start: 8843264, len: 49152
start: 8904704, len: 61440
start: 9043968, len: 73728
start: 9166848, len: 53248
start: 9232384, len: 73728
start: 9367552, len: 24576
start: 9424896, len: 36864
start: 9572352, len: 40960
start: 9625600, len: 36864
start: 9695232, len: 65536
start: 9830400, len: 94208
root 17952 inode 1177157 errors 100, file extent discount
Found file extent holes:
start: 4915200, len: 40960
start: 4980736, len: 36864
start: 5103616, len: 65536
start: 5242880, len: 65536
start: 5365760, len: 45056
start: 5439488, len: 53248
start: 5509120, len: 40960
start: 5570560, len: 28672
start: 5701632, len: 57344
start: 5763072, len: 61440
start: 5828608, len: 65536
start: 5902336, len: 61440
start: 6025216, len: 118784
start: 6156288, len: 12288
start: 6217728, len: 28672
start: 6287360, len: 45056
start: 6356992, len: 16384
start: 6426624, len: 8192
start: 6483968, len: 20480
start: 6557696, len: 24576
start: 6623232, len: 32768
start: 6680576, len: 61440
start: 6750208, len: 20480
start: 6815744, len: 40960
start: 6881280, len: 24576
start: 6938624, len: 57344
start: 7012352, len: 135168
start: 7200768, len: 53248
start: 7274496, len: 53248
start: 7405568, len: 57344
start: 7471104, len: 45056
start: 7598080, len: 61440
start: 7729152, len: 40960
start: 7790592, len: 32768
start: 7921664, len: 28672
start: 7983104, len: 49152
start: 8060928, len: 36864
start: 8183808, len: 32768
start: 8253440, len: 53248
start: 8323072, len: 49152
start: 8388608, len: 16384
start: 8454144, len: 49152
start: 8519680, len: 16384
start: 8585216, len: 40960
start: 8642560, len: 61440
start: 8716288, len: 12288
start: 8781824, len: 20480
start: 8843264, len: 49152
start: 8904704, len: 61440
start: 9043968, len: 73728
start: 9166848, len: 53248
start: 9232384, len: 73728
start: 9367552, len: 24576
start: 9424896, len: 36864
start: 9572352, len: 40960
start: 9625600, len: 36864
start: 9695232, len: 65536
start: 9830400, len: 94208
root 17962 inode 1177157 errors 100, file extent discount
Found file extent holes:
start: 4915200, len: 40960
start: 4980736, len: 36864
start: 5103616, len: 65536
start: 5242880, len: 65536
start: 5365760, len: 45056
start: 5439488, len: 53248
start: 5509120, len: 40960
start: 5570560, len: 28672
start: 5701632, len: 57344
start: 5763072, len: 61440
start: 5828608, len: 65536
start: 5902336, len: 61440
start: 6025216, len: 118784
start: 6156288, len: 12288
start: 6217728, len: 28672
start: 6287360, len: 45056
start: 6356992, len: 16384
start: 6426624, len: 8192
start: 6483968, len: 20480
start: 6557696, len: 24576
start: 6623232, len: 32768
start: 6680576, len: 61440
start: 6750208, len: 20480
start: 6815744, len: 40960
start: 6881280, len: 24576
start: 6938624, len: 57344
start: 7012352, len: 135168
start: 7200768, len: 53248
start: 7274496, len: 53248
start: 7405568, len: 57344
start: 7471104, len: 45056
start: 7598080, len: 61440
start: 7729152, len: 40960
start: 7790592, len: 32768
start: 7921664, len: 28672
start: 7983104, len: 49152
start: 8060928, len: 36864
start: 8183808, len: 32768
start: 8253440, len: 53248
start: 8323072, len: 49152
start: 8388608, len: 16384
start: 8454144, len: 49152
start: 8519680, len: 16384
start: 8585216, len: 40960
start: 8642560, len: 61440
start: 8716288, len: 12288
start: 8781824, len: 20480
start: 8843264, len: 49152
start: 8904704, len: 61440
start: 9043968, len: 73728
start: 9166848, len: 53248
start: 9232384, len: 73728
start: 9367552, len: 24576
start: 9424896, len: 36864
start: 9572352, len: 40960
start: 9625600, len: 36864
start: 9695232, len: 65536
start: 9830400, len: 94208
root 17981 inode 1177157 errors 100, file extent discount
Found file extent holes:
start: 4915200, len: 40960
start: 4980736, len: 36864
start: 5103616, len: 65536
start: 5242880, len: 65536
start: 5365760, len: 45056
start: 5439488, len: 53248
start: 5509120, len: 40960
start: 5570560, len: 28672
start: 5701632, len: 57344
start: 5763072, len: 61440
start: 5828608, len: 65536
start: 5902336, len: 61440
start: 6025216, len: 118784
start: 6156288, len: 12288
start: 6217728, len: 28672
start: 6287360, len: 45056
start: 6356992, len: 16384
start: 6426624, len: 8192
start: 6483968, len: 20480
start: 6557696, len: 24576
start: 6623232, len: 32768
start: 6680576, len: 61440
start: 6750208, len: 20480
start: 6815744, len: 40960
start: 6881280, len: 24576
start: 6938624, len: 57344
start: 7012352, len: 135168
start: 7200768, len: 53248
start: 7274496, len: 53248
start: 7405568, len: 57344
start: 7471104, len: 45056
start: 7598080, len: 61440
start: 7729152, len: 40960
start: 7790592, len: 32768
start: 7921664, len: 28672
start: 7983104, len: 49152
start: 8060928, len: 36864
start: 8183808, len: 32768
start: 8253440, len: 53248
start: 8323072, len: 49152
start: 8388608, len: 16384
start: 8454144, len: 49152
start: 8519680, len: 16384
start: 8585216, len: 40960
start: 8642560, len: 61440
start: 8716288, len: 12288
start: 8781824, len: 20480
start: 8843264, len: 49152
start: 8904704, len: 61440
start: 9043968, len: 73728
start: 9166848, len: 53248
start: 9232384, len: 73728
start: 9367552, len: 24576
start: 9424896, len: 36864
start: 9572352, len: 40960
start: 9625600, len: 36864
start: 9695232, len: 65536
start: 9830400, len: 94208
root 18045 inode 1177157 errors 100, file extent discount
Found file extent holes:
start: 4915200, len: 40960
start: 4980736, len: 36864
start: 5103616, len: 65536
start: 5242880, len: 65536
start: 5365760, len: 45056
start: 5439488, len: 53248
start: 5509120, len: 40960
start: 5570560, len: 28672
start: 5701632, len: 57344
start: 5763072, len: 61440
start: 5828608, len: 65536
start: 5902336, len: 61440
start: 6025216, len: 118784
start: 6156288, len: 12288
start: 6217728, len: 28672
start: 6287360, len: 45056
start: 6356992, len: 16384
start: 6426624, len: 8192
start: 6483968, len: 20480
start: 6557696, len: 24576
start: 6623232, len: 32768
start: 6680576, len: 61440
start: 6750208, len: 20480
start: 6815744, len: 40960
start: 6881280, len: 24576
start: 6938624, len: 57344
start: 7012352, len: 135168
start: 7200768, len: 53248
start: 7274496, len: 53248
start: 7405568, len: 57344
start: 7471104, len: 45056
start: 7598080, len: 61440
start: 7729152, len: 40960
start: 7790592, len: 32768
start: 7921664, len: 28672
start: 7983104, len: 49152
start: 8060928, len: 36864
start: 8183808, len: 32768
start: 8253440, len: 53248
start: 8323072, len: 49152
start: 8388608, len: 16384
start: 8454144, len: 49152
start: 8519680, len: 16384
start: 8585216, len: 40960
start: 8642560, len: 61440
start: 8716288, len: 12288
start: 8781824, len: 20480
start: 8843264, len: 49152
start: 8904704, len: 61440
start: 9043968, len: 73728
start: 9166848, len: 53248
start: 9232384, len: 73728
start: 9367552, len: 24576
start: 9424896, len: 36864
start: 9572352, len: 40960
start: 9625600, len: 36864
start: 9695232, len: 65536
start: 9830400, len: 94208
root 18148 inode 1177157 errors 100, file extent discount
Found file extent holes:
start: 4915200, len: 40960
start: 4980736, len: 36864
start: 5103616, len: 65536
start: 5242880, len: 65536
start: 5365760, len: 45056
start: 5439488, len: 53248
start: 5509120, len: 40960
start: 5570560, len: 28672
start: 5701632, len: 57344
start: 5763072, len: 61440
start: 5828608, len: 65536
start: 5902336, len: 61440
start: 6025216, len: 118784
start: 6156288, len: 12288
start: 6217728, len: 28672
start: 6287360, len: 45056
start: 6356992, len: 16384
start: 6426624, len: 8192
start: 6483968, len: 20480
start: 6557696, len: 24576
start: 6623232, len: 32768
start: 6680576, len: 61440
start: 6750208, len: 20480
start: 6815744, len: 40960
start: 6881280, len: 24576
start: 6938624, len: 57344
start: 7012352, len: 135168
start: 7200768, len: 53248
start: 7274496, len: 53248
start: 7405568, len: 57344
start: 7471104, len: 45056
start: 7598080, len: 61440
start: 7729152, len: 40960
start: 7790592, len: 32768
start: 7921664, len: 28672
start: 7983104, len: 49152
start: 8060928, len: 36864
start: 8183808, len: 32768
start: 8253440, len: 53248
start: 8323072, len: 49152
start: 8388608, len: 16384
start: 8454144, len: 49152
start: 8519680, len: 16384
start: 8585216, len: 40960
start: 8642560, len: 61440
start: 8716288, len: 12288
start: 8781824, len: 20480
start: 8843264, len: 49152
start: 8904704, len: 61440
start: 9043968, len: 73728
start: 9166848, len: 53248
start: 9232384, len: 73728
start: 9367552, len: 24576
start: 9424896, len: 36864
start: 9572352, len: 40960
start: 9625600, len: 36864
start: 9695232, len: 65536
start: 9830400, len: 94208
ERROR: errors found in fs roots
found 13917869395968 bytes used, error(s) found
total csum bytes: 501016
total tree bytes: 1743912960
total fs tree bytes: 1651933184
total extent tree bytes: 85065728
btree space waste bytes: 341607782
file data blocks allocated: 43039469133824
referenced 32223623094272
(Sorry for splitting the message in three but there is a 20K limit per message and I cannot attach TXT files)
What do I learn from this?
I have now ordered the required cables to mount a bunch of HDDs onto my Desktop RAID card, I will transfer everything soon and I will reset the NAS. I give up 🙂
(That said, it's been behaving well recently, again!!)
Oh, one little gossip on the PSU: I think I am responsible for the swollen caps! When I replaced the fan, I powered it from the PSU itself. It's a noctua so little airflow. I noticed the PSU powers it at 5V (it's a 12V fan, unless I made a mistake and the original fan was 5V?).
So the bottom line is: i baked that PSU 100%. I tested it a bit and those heatsinks were scorcing hot while running. I re-wired the fan so it's going to be powered from 12V somewhere else.
Only thing I am going to do differently is to reverse the airflow: I know it's supposed to pull air IN, but I don't agree with that. I think pushing air OUT is a better option as as it stands the PSU is pulling in the hot air expelled from the main fan.
tony359 wrote:
(Sorry for splitting the message in three but there is a 20K limit per message and I cannot attach TXT files)
What do I learn from this?.
The added value of these logs is over-estimated. Nothing we can take out of the full logs here.
tony359 wrote:
Oh, one little gossip on the PSU: I think I am responsible for the swollen caps! When I replaced the fan, I powered it from the PSU itself. It's a noctua so little airflow. I noticed the PSU powers it at 5V (it's a 12V fan, unless I made a mistake and the original fan was 5V?).
A bunch of popular mistakes combined. No that people sometimes don't read voltage specs - much more the **** idea replacing stock fans by Noctua fans (very popular, must be a good choice because of hey, these are soooo silent). These are silent, because of the rpm is lower than the usual high-speed fans (in the 10'000 ... 15'000 RPM range sometimes), and the air flow and the air pressure generated is just a fraction of what is intended by the hardware designers, and required to keep the internals reasonable cool.
For the fan, I take responsibility. I would normally check the airflow, and in fact I think the one I used more or less matched the original one - it's just that I wasn't expecting the PCB to supply 5V - did I get the wrong voltage fan or is the PSU supplying 5V when idle to keep the noise down? In other words: any chance the PCB will ramp up to 12V when the components warm up?
Re. the BTRFS logs: I'm not sure I follow.
tony359 wrote:
Re. the BTRFS logs: I'm not sure I follow.
Plenty of reasons, why community admins restrict the size for attachments, ad why txt files are prohibited (by a simple test of the file extension). Just as in the case of the # dmesg Kernel output, select parts are commonly sufficient. If support engineers need the full data, they will ask for providing the essential parts or for sake the complete log sometimes, by using some cloud systems for temporary usage. It's not worth handling this amount of data on a community forum,
Gotcha.
But I am not a Linux engineer so how do I know which part to post? 🙂
On other forums I like that when CODE is added, it ends up in a window with scroll bars. Makes reading much easier.
Anyways, I hope someone can figure something up from those logs. 🙂
Not much reliable information from forcing a btrfs check on a hot (active) file system.
Can't tell you the practical way on dismounting the volume reliably, especially not the first volume on a system.
but I can do that from techsupport I'm told?
If techsupport tells you on how to dismount the volume, so it's no longer accessed (without the -force then of course), yes.
no, I mean from the techsupport feature on the NAS 🙂
Or even from a Live-USB (yes, I would need to assemble the RAID)
tony359 wrote:
but I can do that from techsupport I'm told?
Probably yes.
Worth mentioning: This is the formal process - Your ReadyNAS or ReadyDATA storage system offers several boot modes for restarting or troubleshooting.
tony359 wrote:
no, I mean from the techsupport feature on the NAS 🙂
None of the volumes are mounted in tech support mode (including the os partition), so you can manually assemble raid and run btrfs check.
Though as I posted earlier, any btrfs repair is dangerous, so you need to back up the data before you do it. Also my view remains that you should proceed with a full reset anyway, as any btrfs repairs won't rule out an OS issue being the root cause of your crashes.
Note the btrfs errors you posted are duplicative - all the errors are in the same inode.
The original PSU fan is a 12V one. I've honestly never checked what voltage is applied to it, but it's constant -- no variation in speed due to temperature. But assuming it is running on 5V to keep it slower, another brand of fan rated the same at full voltage may run very differently at a lower voltage.
Stephen,
Yes I know, we've discussed that subject many times!
And you know my point of view as well! I just dislike the idea of having to reset the whole thing to fix a potential software issue, that's it.
Anyways, as this is not going to progress much further I suppose, I have hardware coming to transfer the file. Obviously now the NAS has stopped crashing.
Just out of curiosity, how do I assemble the RAID manually in techsupport? Also, I assume I can SSH in techsupport mode?
Also (!) is there a way to take a backup of the OS partition so it can be restored if something goes wrong?
Maybe the original fan had a higher airflow at lower speed then. Or maybe it's baking the PSU as well.
5V feels very low though. To make a 12V fan quieter, I'd expect it to be run around 8-9V. Anyways, no issues. I'll run it on 12V and the PSU will be fine.
Thanks!
tony359 wrote:
Just out of curiosity, how do I assemble the RAID manually in techsupport? Also, I assume I can SSH in techsupport mode?
You connect using telnet in tech support mode - not ssh. The username is root, the password is infr8ntdebug
Once in, you can enter
rnutil chroot btrfs device scanThe data volume won't be mounted (though the OS partition will be). So you can try btrfs check on the data volume from there.
A different option is to enter
start_raids btrfs device scanThat won't chroot - not sure if it mounts the OS partition or not. Though if it does, you could umount it.
Thank you.
Further to that previous message where someone said they did btrfs check but then decided to replace the affected file, how do I find out if there is a specific file which is corrupted following the check?
tony359 wrote:
Further to that previous message where someone said they did btrfs check but then decided to replace the affected file, how do I find out if there is a specific file which is corrupted following the check?
You can use find /volume -inum xxxx, where volume is the NAS volume name and xxxx is the inode you are trying to resolve.
I've stumbled into a box of 2TB HDD and I was able to make a temporary 11TB RAID6 with them. See attachment!
Testing now - as some drives are very tired - before transferring.
Update for those who might be interested.
Having completed the backup, I logged into Techsupport. The btrfs errors were still there but find refused to accept the "inum" parameter. After much googling, I went nuclear and reset the whole thing.
It's syncing now.
Two thoughts.
1. The BIOS keeps showing HDD0 as "not found" every now and then. The OS never fails to detect it though
2. It took 20 hours to transfer my files over which the NAS NEVER EVER failed for a second. In fact, it's been online since I started the backup, no issues. If it disappears from the network it happens when it's idle, not when it's being used.
One question:
The OS defaulted to X-RAID, RAID5. I'm ok with RAID5, I believe X-RAID is what I want, right?
In other words, what should I change now that I reset the whole thing?
StephenB can you remind me your recommended schedule for the drives - test, defrag ecc?
Is there a "recommended" steps somewhere to perform on a newly installed box?
Now please wish me luck because if this thing disappears again I promise I will make it disappear in a trash can 🙂
tony359 wrote:
The OS defaulted to X-RAID, RAID5. I'm ok with RAID5, I believe X-RAID is what I want, right?
Yes.
tony359 wrote:
In other words, what should I change now that I reset the whole thing?
If you use snapshots, then I recommend using custom snapshots with limited retention (and not the "smart" snapshots). The "smart" ones have unlimited retention for the monthly snapshots, which eventually will fill the volume.
Enable ssh of course.
tony359 wrote:
StephenB can you remind me your recommended schedule for the drives - test, defrag ecc?
I run one test a month, cycling through all four 3 times a year. For example, my main NAS has
- Disk Test: 1 Jan., 1 May, 1 Sept.
- Balance: 1 Feb., 1 June, 1 Oct.
- Scrub: 1 March, 1 July, 1 Nov.
- Defrag: 1 April, 1 August, 1 Dec.
Disk Test and Scrub are deliberately placed 2 months apart. Since the Scrub accesses every sector on every disk, I feel it also acts as a good disk test.
Thank you Stephen.
I've always had snapshots enabled but I admit I never used them. I can only restore the full snapshot, not browse it to recover single items, correct?
I'd be tempted to disable them. Opinions?
tony359 wrote:
I can only restore the full snapshot, not browse it to recover single items, correct?
No, you can restore subfolders and individual files.
With windows, you right click on the folder or file, and you will see "restore previous versions".
tony359 wrote:
I'd be tempted to disable them. Opinions?
If you don't think you need them, then I'd suggest disable them. I keep them enabled, because I have occasionally accidentally deleted a file in the share.
They shouldn't be enabled in some cases - for instance, if you have a live database or download torrents in a share. When files are repeatedly updated in place, the snapshots will create heavy fragmentation (because they operate at a block level).
I didn't know - or I forgot - about that feature. And it's even in Windows?? Wow! Well, I'll do as you suggest.
I guess the snapshot can only be activated on the whole share, not on single folders?
tony359 wrote:
I guess the snapshot can only be activated on the whole share, not on single folders?
Correct.
Note that BTRFS is storing deltas, so the on-disk space usage depends on how much you change (and how you change it).
The method is linked to BTRFS "copy on write". When the file system rewrites a block in a file, the original block is kept. The snapshot still uses the original blocks, the main share is using the updated one. Note that this means the file in the main share is fragmented.
However, many programs (for instance MS office) will just write out the entire file when you change it. So in that scenario, all the original blocks end up in the snapshot, and the file in the main share is only the new ones.
Anyway, I suggest custom snapshots. I limit them to 3 months retention, which keeps the total disk space used for snapshots pretty low. So you could start there, and then adjust retention on the share to keep the snapshot use reasonable (IMO less than 10% of the volume).
If you want to see snapshot use per share, you do need to enable volume quota from the volume settings wheel.
I forgot to thank you 🙂
The NAS - finger crossed - is still online. But it's happened before so who knows! 🙂
I have a question about the snapshots: I don't understand the attached graphic. What does it mean when I enable specific hours for a snapshot?
Does that mean the snapshot is only created during that time? So if I modify a file outside of that schedule the change won't end up in a shapshop?
Apologies for the silly question. I have checked on the manual but it's still not clear to me.
Thanks
tony359 wrote:
Does that mean the snapshot is only created during that time?
Yes.
tony359 wrote:
So if I modify a file outside of that schedule the change won't end up in a shapshop?
No, not exactly.
The snapshot captures the entire state of the share when it is taken. So files modified after a snapshot is taken will still show up in the next one.
But if you were to create a file and then accidentally delete it in between snapshots, then you wouldn't be able to get the original back - since the original file wouldn't have gotten into a snapshot yet.
If you set the schedule to take snapshots all the time (e.g., solid blue), then I suggest also using the option to only take snapshots if there have been changes in the share since the last one. That will reduce a lot of clutter.
Also, I don't set the "allow snapshot access" option, only the "allow access to windows previous versions". The reason is that snapshots are read-only if you don't set "allow snapshot access", but Netgear sets them to read-write if you do check it. Since IMO the purpose of the snapshots is to protect me from user error and perhaps malware, I don't want the snapshots to be writeable from Windows.
Thanks, I think I understand - but one thing 🙂
Say I set the snapshot ON at 2pm, the NAS will create a snapshop then.
What happens if I set the snapshot all the time (without selecting to only take snapshot when changes are made)? Does the NAS create a snapshot and when done it creates another one and so on?
How long does it take for the NAS to create a snapshot?
I think daily snapshots would work for me. Overnight is probably a good option. Do I check one of those blocks at - say - 2am to make that happen?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
