So, I decided to reboot the NAS to prove the error above and the system has gone through the reboot process upto 98% and has stayed like that for the past 6 hours or so. Could this be that the system is doing internal disk type checks (consistency etc) and that it may sort itself out?
Do you still have the same error message on the display screen and it is now not booting up completely? Please post what you see on the RAIDar when it sees the NAS.
By the way, what is the current firmware version of the NAS? The latest has been released yesterday.
Apologies for day in responding - I was away for the weekend and then work has got in the way lol
So....
The bootup got stuck for 24hrs on 98% to turned it off. I rebooted it last night and got back to the same error message as highlighted at the top of this thread.
I didn't update the firmware last week so suspect I'm running at least 1 version back
I plan to do another bootup again on Thursday and will try and get raidrar stuff as well to put up here.
I was in the process of aggregating my data from various sources prior to clean up and then backup so am wary of going down the full reset path as I'll need to copy off the data first before the the reset unless there's a better interim reboot option that doesn't kill the existing datasets
So, I booted the NAS and it seems to have come up onto the network as a readable device from my windows PC's - all very good. Only problem now is that I can't get to the Admin page or see the device from outside of the network.
A major step forward from where I was last week and early this
