ReadyNAS 516 No booting after power outage (Booting 41%)

[dbreiny1]

Today I had a UPS malfunction and kill the power to my 516, and I am prety sure it was in the middle of a raid volume scrub.  After removing the UPS and restoring power to the 516, the device sems to be stuck on booting 41%.  It has been up for maybe an hour and has not moved past 41%.  I need help understanding if it has resumed the scrub and will come up after, or if it is stuck and will need manual intervention.  Any help would be appreciated.  There was a 316 connected to the UPS as well and it started with no issues, but I do not think it was scrubbing any volumes at the time.

[dbreiny1]

The progress has moved from 41% to 45%, so I think it may be runnig a filesystem check on the huge /data volume that is ~30TB in size.  It seems it is progresing and **fingers crossed** that it will come up when the proces is complete.

[dbreiny1]

I think it’s definitely hung. I pressed the power button and now it says 45% systems-update-u, but I did not initiate any system update. If anyone has any ideas please let me know.

[dbreiny1]

This device has an EDA500 with 5x 6TB drives RAID6, and I can successfully boot the RN516 if I disconnect the EDA.  It seems it was the EDA that was performing the scrub.  Any ideas how to determine what happened to the EDA volume and how to resolve it?

[Sandshark]

An EDA scrub is abominably slow due to the eSATA port replication.  It uses a SATA channel designed for a single drive for all five.  A volume check would as well, I suspect.  So it really could still be progressing, just very slowly.  When you booted without the EDA, did you download the log .zip?  There might be something of interest in there.

But maybe the best thing to do is to use the boot menu to skip the volume check.  While your EDA volume may not be accessible, you may get better info (from the logs) as to what's wrong.  Or maybe it'll make the EDA volume read-only and at least let you recover what you need from it.

[dbreiny1]

Thanks for the response. I ended up powering the device down removing the EDA 500 from the port and powering up the 516 and a boot it up with no issue. So I plugged the EDA 500 back in and booted the device again and it hung on boot. I then powered it down and removed the esata from port 1 and plugged it in the port 2 and booted it up, everything came online and all my volumes are visible now. Very interesting…

[Sandshark]

If I remember correctly, port 1 uses a different chip than the other two, so there may be damage within your unit.  Or there may just be a timing difference in start-up that was enough to get you past the issue.

In any event, glad you did get past it.