How do you STOP a ReadyNAS balance in progress with latest OS?

Hey Guys, 

So I have 2 incredibly bad problems now:

1) NetGear Community will not let me log into my "ReadyNASPro" user account. I can not reach it in any manner I have tried.

Going to community , the landing page comes up as a registration page and it wants me to register.  
So I had to go and make up another user name you see here. Stupid Sh*t.

I can not reach anyone at NetGear to help, without doing paid support, even to launch a ticket. 

So somehow NetGear dis-associated my Community account from my login credentials (email address). No way to reset credentials, as everytime I open Community, it wants me to register again. Not sure how I actually managed to get here for the reply. Or how to fix this. Can not find a way to log in using my User Name instead of email address, if that option exists. Looks like my email is now associated with the user account I am writing from. 

Do you guys have any direct email or access to NetGear tech or anyone who could restore my community account? Or since you are the experts on this forum, any idea on how I may attempt this? 

2. Used the btrfs balance start -dusage=5 /data

For the Balance procedure. It ultimately crashed the NAS. 

Went thru 20% complete after many hours. Then I tried to terminate it via SSH, but SSH was completely unresponsive. 

Tried shutting off the machine via FrontView. No response. Machine frozen. 

Forced shutoff on machine via front button. 

Machine hung on boot at 45%. Waited a long time. 

Forced shutoff again. Did a Hail Mary, and prayed to the NAS Gods. 

Machine hung on boot at 45% again. Depondent, I waited about 1/2 hour and machine completed reboot and Balance procedure was OFF. 

I can not ever risk running Balance again. The machine can not handle it, maybe due to the volumes being too large, since it seems to work on your machine StephenB with a smaller volume without issues. Are you running X-RAID or FlexRAID? That may have something to do with it?

At least I have NAS access again, so this one is solved for now.