NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Balance trashed my NAS Readynas RN104
Help wanted... I have Readynas 104 with 4x3TB Seagate drives. It was 85% full and I decided to delete 0.75TB of data. Available space did not increase so decided to run Balance. The device became unresponsive after Balance got to 17% complete but this didn't worry me as I read that this often happends and that Balance can take a long time, often days. After 10 days, still unresponsive and listening to the unit there was no disk activity, just fan noise. So decided to power cycle! Now it won't boot but stops 36% through the boot process. Tried booting off a USB stick but still no better. I am (was) running the current version of the OS.
I have imported data backed up but would be nice to recover NAS. Any suggestions on how to proceed at this point very much appreciated.
Phil
StephenB,
I have now downloaded the Zip Log - there's a lot! Is there any parts that youo would like me to post, for the benefit of the community?
Phil
5 Replies
Replies have been turned off for this discussion
Available space not increasing probably meant that you had snapshots containing the deleted data (all snapshots containing deleted data must be deleted to free up space) or needed to be a bit more patient for the deletion to lead to free space increasing.
Balancing is not the way to free up space. Space can be allocated to data, metadata and system or be unallocated. Balancing moves data and metadata around so that empty chunks can be returned to unallocated space.Before balancing it's advisable to get volume usage below 80%.
Balancing is probably the most overused volume maintenance option.
The system will automatically return empty chunks to unallocated space anyway which would happen when deleting a large amount of data as a significant portion of that data is likely full chunks.
You could try the volume read-only boot menu option and see if it boots up.I am in your debt, mdgm, as your suggestion to boot in read-only mode has restored access, so thank you very much.
In fact I don't have any space allocated to snapshots and I have never used Balance before so it is not over-used by me. So I remain in the dark as to what I did wrong and why the RN104 became inaccessible.
I am very grateful for you input. Thanks.
Phil
m0n5ter wrote:
In fact I don't have any space allocated to snapshots
With OS-6, you don't allocate space for snapshots.
Do you mean that snapshots are turned off on all the shares (or at least the ones the held the deleted files)?
m0n5ter wrote:
In fact I don't have any space allocated to snapshots and I have never used Balance before so it is not over-used by me. So I remain in the dark as to what I did wrong and why the RN104 became inaccessible.
I think the forced shutdown is what made the volume inaccessible. But there might be more clues in the log zip file.
While many people do over-use balance, it can also be under used. Normally it shouldn't run for over a week, and that suggests to me that it probably should have been run before.
Personally I run it on a 3-month schedule (as I do with the other maintenance functions). Usually it takes about 20 minutes on my RN526x. While it would take longer on an RN104, it's nowhere near 10 days.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
