ReadyNAS 1000S - Firmware & 3TB HDD Support?

Doesnt really matter, it works the very same way with Static IP.

If it can't pickup an IP address via DHCP it will default to use an IP address of 192.168.168.168

Hook up an ethernet cable (NIC is auto-sensing so you can use any ethernet cable) between the NAS and a PC and set the PC's NIC's IP address to e.g. 192.168.168.100. You can then login to the NAS via https://192.168.168.168/admin change the network settings (don't forget to click Apply), connect it and your PC back up to your network (don't forget to change your PC's NIC settings back to what they were before

Brilliant! Why didn't I think about that?

Thanks a lot. I'm going through some old files, cleaning up a bit, doing a final backup and then this weekend I'll be doing the factory reset. Thanks again.

Do any of you happen to know how long the "defaulting" process usually takes? The warning message just before starting the process said "up to 10 minutes", but I've been looking at the flashing blue light on the front of the unit for close to 40 minutes now. I'm seeing a response from 192.168.168.168 when pinging but no response via HTTP, nor is RAIDar able to locate the device.

Edit:
I ended up pulling the power cord after waiting for about an hour. This resulted in the CF card needing to be reflashed. After that was done, I was able to access FrontView, but could not create or otherwise modify any of the volumes. I ran another factory reset and am making more progress this time around. RAIDar showed "Installing" and made it to "Creating Volume" as of now, though it's strange that I was never prompted what kind of volume I want to create. I'm assuming that I'll be able to adjust this later. With 4x 2TB disks installed, should I stay put and brew a pot of coffee or should I just come back later in the day?

Okay, so here's where I am now - after re-reading the documentation and searching the forums, I found that the RAID type has to be selected prior to reloading the factory settings, so I am now up on a functioning RAID5 array. However, in the interest of having all of my customer's files ready by Monday morning, I've interrupted the RAID resync (I think this is the correct term) by pulling the 4th drive so as to have better write speeds while I work to move over 300GB of data back to the NAS. I've been trying to restore files from a backup for some time now but am running into situations where the NAS is rebooting itself and cutting off my file transfer. There are no helpful messages in the log - just a generic message about the NAS coming back online after an unsafe shutdown.

Could this be because the array is degraded? I'm using Microsoft's SyncToy to copy data from my backup USB hard disk that's connected to my workstation, over the network, to the NAS share. I'm seeing write speeds of ~70megabits on large files so I can't imagine that I'm thrashing the array to the point where the NAS is rebooting itself. I'm primarily working with small files, lots of Word documents and PDFs, probably close to 300k of them that need to be copied.

Should I rebuild the RAID5 before trying again or could something else be wrong? My "Monday morning" deadline is less than 5 hours away and with 200k+ small files, I'm certain that I won't be able to keep this promise.

Edit:
After scrolling through half a dozen pages of forum search results, recalibrating the fans was suggested. I thought this was silly (temperature sensors were fine and RPMs were consistent) but tried it anyway - no random reboots so far.

Nevermind, I spoke too soon. It looks like about 27k files copied before the ReadyNAS rebooted itself again. I am completely out of ideas at this time. Any help?

I sent you a PM, but for an update. If you are able to send us the logs, I can have one of our support guys see what is happening to the NAS.

Latest news: Support wasn't able to find any issues in the logs I sent so I finally broke down and finished building the array by inserting the last disk. This took 25 hours, after which the copy went smoothly. I've copied ~100k files over so far without any issues. Just thought I'd post it here in case anyone has similar issues...