ReadyNAS 104 Inaccessible - ReadyNAS Admin Page is Offline

---

haigha wrote:

DO YOU HAVE ENOUGH STORAGE TO BACK IT UP?

I have a 4TB USB drive that will accommodate all the data I want to backup.

---

One option is to connect the disk to the NAS, and use one or more ReadyNAS backup jobs.  These would run unattended, so they wouldn't tie up your Mac.  You should double check that the files look ok before you proceed - one way to do that is to eject the disk, and connect it to the Mac for checking.  I recommend using a disk format that you can read on the Mac - NTFS is probably the best option for you.  One benefit here is that you can set up a schedule to update this backup automatically.

You can also connect the disk to your Mac, and transfer all the files over the network. It would be best if you could connect the Mac to your network with ethernet.  The benefit here is that you can use the native APFS formatting.  If you go this route, you should look for a transfer tool that can copy everything for you - FreeFileSync is one that might work.  Note I am not a Mac user, so this might not be the best choice.

Either way, you should put a backup plan in place going forward - RAID isn't enough to keep your data safe.

After multiple shutdowns/boots into OS re-install, I'm getting better access to my "broken" NAS, and I'm now able to backup my most valued files. The NAS is indicating that it's in backup status (blinking backup led), but I have no idea how many of my files have been backed up, and I don't want to interrupt the process. My first attempt at backup only backed up a limited number of files before the NAS dropped out of backup status. I was able to mount the USB drive I used for backup to my Mac and see and access the files that had been backed up. After rebooting into another OS re-install and initiating another backup, I noticed an error message in the browser access page. It looks like my number 1 drive is in the process of failing, so this may explain the NAS's erratic betahaviour, because the NAS OS is on the number 1 disk, as I understand it. I'm mentioning this in the hope this might help someone else in a similar predicament in the future.

Just noticed the error is now identified as disk 4—looks like I may have 2 drives on the way out.