This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
I had recently updated the firmware to the last available as I wanted to make sure I was up-to-date before I replaced a dead drive. The firmware update appeared to take and booted normally. A few days later (as I was waiting for the replacement drive to arrive), we had lost power early one morning, but the system was connected to an UPS, but had appeared to have lost enough power to cause the system to power down.
Upon trying to power it back up again, the system was stuck at a "Booting..." message.
I tried an OS Re-install and the system appeared to boot and connect to the network and was given an IP, but I was unable to access the web interface nor otherwise connect with it. I tried rebooting and am now back to the "Booting..." message.
Also, I did read the other numerous "stuck at booting" posts, but it seems most of them are solved off-screen by some moderator or other expert intervention with no clear steps to manually address the issue myself.
You should power down the NAS and test the disks in a Windows PC using vendor tools (seatools for seagate, lifeguard for western digital). Label the disks by slot as you remove them, so you can preserve the current ordering.
I've had the NAS powered down for a while since it was obvious it wasn't progressing towards anything. I was running the original firmware (EDIT: I'm not sure what the original version was) that was on the device before I attempted updating to 4.2.31. The system itself had told me that Disk 1 had died but the others were in good condition. Is the fact that Disk 1 had died causing an issue with the firmware taking?
The drives are Seagate so I'll grab their tool and check them out. I have a replacement drive for Disk 1 waiting to be used, but I assume I need to get the NAS back into working operation first before I can hot swap it out.
For some reason my last post disappeared, so here's a summary.
I booted with Disk 1 removed and was able to get a report on the display of my assigned IP from the router 192.168.1.10 and "UPS connected".
I ran a scan and Fix All with Santools against Disk 1 and after a couple hours later, it came back with a PASS for the disk.
Gracefully powering off the system at his point didn't seem to be available as pressing the power button did not bring up a prompt nor did pressing it multiple times trigger the power down sequence. So I had to long press to perform a hard shutdown.
I replaced Disk 1 and the system booted to show the IP address and "UPS connected" message again and appears to no longer be getting stuck at "Booting...", but I'm still unable to access the web interface, although I am able to get a ping response the device.
For some reason I'm having trouble seeing my posts stick after posting. I've lost count of my number of attempts.
I downloaded RAIDar 6.3 and it apparently sees the NAS and reports the following.
Model: ReadyNAS Ultra 4 Plus
Name: (Shows the name I had given the device)
Status: Healthy
Firmware: 4.2.31
IP Address: 192.168.1.10 (Shows the device MAC address)
Drives: (Shows 4 drive icons with green checkmarks)
Clicking on "Admin Page" opens my browser to the admin page, but again, the browser just reports that the connection was refused.
Clicking on "Browse" makes my computer go busy for a second, but then just opens up my Documents folder instead of, I presume, the actual device share.
Clicking on "Locate" displays a message box that says "The LEDs of the selected NAS device are now blinking.", but no changes to the display or other lights are apparant.
In all cases, I haven't been able to access the windows shares. Could the OS-Reinstall I performed before have nixed those shares that had been created on the NAS?
Ok, booted again with just Disks 2, 3, and 4 in and lo and behold, it actually booted up completely this time. Not sure what made it move past because I had gotten the similar behavior where it just showed the IP address and UPS connected status with no access to the system, but this time it actualy made it to showing the product name and showing "C:\ unprotected".
At which point I was able to successfully access the system and saw that I have now lost Disk 3. I put Disk 1 back in and it performed a check and passed. It is now performing a resync using the remaining available drives. I think I may be safe in that I have enough free space that losing the second drive may have no impact, but once Disk 1 is resynced I'll be pulling Disk 3 to do a scan and Fix All like I did for Disk 1 and see if it can be salvaged temporarily.
If Disk 3 survives, I'll insert my new replacement drive into Disk 1 since it was the first to go and I'll be promptly ordering another drive to replace Disk 3.
Thanks so much for your help! If you have any further advice for me at current state I would be happy to hear it.
If the resync is proceeding with RAID-5, disk 3 must be still alive (though it might be failing). Of course RAID-6 (dual redundancy) can survive two failed disks.
The system was reporting Disk 3 as dead, but when resyncing of Disk 1 completed it showed back up as OK.
The system is in X-RAID2 (so I think that's RAID-5), but so far the volume appears to be intact.
After Disk 1 finished resyncing, I removed Disk 3 to run a scan and Fix All on it with Seatools and it's now at 80% resyncing Disk 3. Once that is finished I have a fresh new drive that I will replace Disk 1 with since it was the first to fail. Once I can confirm that the new drive is functioning, I'll be ordering a replacement for Disk 3 as well. I'll probably be ordering replacements for Disks 2 and 4 also, since all the drives were bought around the same time and it seems they are all starting to fail somewhat, even if it just seems to be bad sectors cropping up, at least this will buy me a little more time.
