Internal Server Error on admin after OS reset
I'm attempting to get an old ReadyNAS 102 Duo running again. On booting up and accessing the admin panel, I noticed the logs complained about 99-100% internal storage use. I attempted to access over SSH to try and find what was using up space, but wasn't able to login (probably related to free space). I gave it a reboot and then wasn't able to access the admin at all (the http/https services weren't accessible), so (probably wrongly!) thought I'd try an OS reset form the boot menu.
At the moment, I've applied an OS reset twice, and both times, after this has applied the admin screen shows the classic Apache "Internal Server Error" page, after logging in with admin/password.
Luckily RAIDar can pick up the box, which tells me its status is healthy, and running firmware 6.9.2. The Download Logs and Diagnositcs functionality is not accessible - it asks for a username/password (I gave it admin/password) which is apparently incorrect (probably hitting the HTTP 500). The Locate functionality does seem to work (flashing LEDs). Unfortunately, it seems SSH is disabled after reset, so I can't access that way either. http://nasip/fwbroker also gives a HTTP 500.
Related issues include these (below), which seem to suggest an expired password/reset-hardware-clock is to blame (it's quite an old model so might set an old date) or the internal storage needs to be cleared. Unfortunately it won't let me access /password_recovery/ for "security reasons" :-). If it can be remotely reset by Netgear staff that might help.
Thanks in advance of any support!
Re: Internal Server Error on admin after OS reset
To update on this - on finding out the X-Raid setup was usable with normal mdadm, I mounted my drives in a Debian box. I discovered on the Readynas OS partition (sda1) a file at /root/sdc which was 3.4G of null bytes. I'm assuming what happened here is that something attempted to allocate some space (perhaps for an update) and ended up allocating until the drive filled.
I'm not totally confident with running my own raid, and I have a feeling just deleting that file on both disks might corrupt or degrade it or something, so I'll be extracting my (luckily non-important) data from this mdadm mount, and fresh-starting with some clean disks.