The disk 3 light selects the OS reinstall; the disk 2 light selects the factory reset.
I suggest powering down the NAS and removing the disks. Label the disks as you remove them, so you can preserve slot order. Power up, and see if RAIDar finds it, and gives you a no-disks statuss.
It would also be useful to test the disks in a Windows PC with vendor tools (WDC's Sashboard, or Seagate's Seatools). You can connect the disks either with SATA or a USB adapter/dock.
I will do it tomorrow and keep you updated, I tried the factory reset (2nd light) and still power light on (no blinking). Is it possible to make the reinstall from usb?
The 2100 is an OS4.2.x device and this sound like the TLS1.0 issue that's already been discussed in dozens of posts. Have you tried any of the work-arounds already discussed?
I'm sure it's a 2100, the image is wrong but from UniFi there is no 2100. The nas comes from a customer of mine, who has abandoned all the CED and I recovered the NAS without the disks so as not to have his data.
When I connect to the IP address https://192.168.0.155/admin it immediately gives me a "connection denied" error as if the NAS is booting or crashed
It's very frustrating because I've had quite a few ReadyNAS but this one is driving me crazy, I've even tried reinstalling via USB, no success.
When you are in that mode, you can access the linux command line by connecting with telnet. That would let you look at disk health, and see if the OS partition was installed on the disks.
Note step 6 in the manual (press and release reset to confirm the selection). It's easy to overlook that step, since it is after the table.
Thanks StephenB, I didn't know telnet was available in that case!
I know the credentials are root, the password is infr8ntdebug
Are the telnet commands I can run the usual ones?
I would try to turn it on without disks and go into tech support mode, do you think I can access via telnet the same? So as to check if I have to reinstall the NAND via usb or not.
For point 6, yes the first few times it can escape, but you realize when it catches it because it reboots.
The linux you are running is in the flash memory, so there are commands that are missing. Not sure which ones they are though. Hopefully smartctl is installed
If the disks are installed and the OS partition is there, then you can do this:
start_raid.sh
mount /dev/md0 /sysroot
to start the RAID array and mount the OS partition on the disks.
If the OS partition mounts, you can then chroot using
mount bind /proc /sysroot/proc
mount bind /dev /sysroot/dev
mount bind /dev/pts /sysroot/dev/pts
mount bind /sys /sysroot/sys
chroot /sysroot /bin/bash
The internal flash is visible - you can look for it in
cat /proc/partitions
It should be the smallest disk with a single partition. You can then mount that using something like
