Since update 6.6.0 I have had sporadic issues with the volumes being locked to read only when the data balance and defrag are done. I have ran into this problem before on older releases, and usually a reboot fixes it. This time I happened to have a USB key attached to the front usb port and it didnt boot properly. I removed the USB and it booted, so I figured end of that.
Now, for the problem.....
Few days later the system locked up. I couldnt log in and the power button wouldnt respond or bring up the LCD, so I did a hard boot by unplugging the power brick. Ever since it boots so far and ends up showing a 36c out of memory error.
After reading it I was able to boot fine into read only mode, but cannot proceed as I Have SSH disabled and cannot enable it on read only mode. I'm pretty sure its a snapshot problem (my Data share has 36 snapshots with total share size at 4.2TB). And again in read only mode I can't "properly" disable snapshots, as its read only.
So....
Wondering if someone can give me some idea on how best to proceed?
Sorry about that, I didn't think I could install 6.6.1 while in read only mode. I installed it last night and am still getting the memory error. The only app I have is BitTorrent Sync installed. After the update I am still able to boot into read only mode, but not into normal.
I need to check with some colleagues on this. Your system is crashing hard when OOMing without giving all the normal details we'd get when a system OOMs (i.e. what's using up all the memory).
