- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
ReadyNAS 516 with EDA500 Expansion unit issue when started from timer.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ReadyNAS 516 with EDA500 Expansion unit issue when started from timer.
Hi,
When the ReadyNAS 516 and EDA500 is automatically started from a set timer sometimes but not always, the follow messages are output and the share on the EDA500 is unavailable:
Disk in channel '1' (eSATA Port 1) changed state from RESYNC to ONLINE.
Disk in channel '2' (eSATA Port 1) changed state from RESYNC to ONLINE.
Disk in channel '3' (eSATA Port 1) changed state from RESYNC to ONLINE.
Disk in channel '4' (eSATA Port 1) changed state from RESYNC to ONLINE.
Disk in channel '5' (eSATA Port 1) changed state from RESYNC to ONLINE.
If I do a manual restart, the issue goes away
Has anyone else had a similar issue?
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS 516 with EDA500 Expansion unit issue when started from timer.
Hello kevcompton,
The RESYNC to ONLINE messages I believe is normal.
Since you mentioned there is/are share/s that is unavailable, does this mean you have multiple volumes? What's the RAID level?
Regards,
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS 516 with EDA500 Expansion unit issue when started from timer.
Hi,
Thanks for responding, i've added screen shots of when EDA1 is successful mounted. When not, the eda1 volume is shown in red and the only option from that screen is to format the drives. As I said, a reboot fixes this. Since posting, I have had 1 occasion where the eda1 volume is unavailable after a manual boot.
Also, I only get the RESYNC to ONLINE messages when there is an issue.
Hope you can help.
Will add a screen shot when it fails again if that helps.
Regards,
Kevin.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS 516 with EDA500 Expansion unit issue when started from timer.
Which firmware are you running?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS 516 with EDA500 Expansion unit issue when started from timer.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS 516 with EDA500 Expansion unit issue when started from timer.
This error happened today from a manual start, see screen shot. I have saved the logs but can't see a way of uploading them here.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS 516 with EDA500 Expansion unit issue when started from timer.
@kevcompton wrote:
...I have saved the logs but can't see a way of uploading them here...
You don't. You can email logs to Netgear if you have a support case (or if a Netgear person here is interested). mdgm has the details in his signature links.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS 516 with EDA500 Expansion unit issue when started from timer.
Thanks. Do you suggest that I should open a support case for this then?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS 516 with EDA500 Expansion unit issue when started from timer.
@kevcompton wrote:
Thanks. Do you suggest that I should open a support case for this then?
If this was purchased after June 1 2014 then you should have free lifetime chat support for this NAS, so I would open a case on this.
Netgear folks engaged here (mdgm, jennc, etc) might also be interested in the logs.
A good way to proceed is open the case, post the case number on this thread, and then email the logs. Perhaps include a link to this thread in the email.
Then Netgear will be able to tie the case to this thread.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS 516 with EDA500 Expansion unit issue when started from timer.
Hello kevcompton,
I checked your profile and found that you have several legacy ReadyNAS units. This ReadyNAS 516 is not yet registered, this should have free support.
I think your case is for L3 escalation, please contact support center.
Regards,
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS 516 with EDA500 Expansion unit issue when started from timer.
Thanks.
I recently updated the firmware to the latest beta and the issue hasn't happened again.
If it does, I will contact support.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS 516 with EDA500 Expansion unit issue when started from timer.
Hello kevcompton,
In case BETA resolves the issue, please let us know. You may also post it at ReadyNAS OS6 BETA release board.
Regards,
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS 516 with EDA500 Expansion unit issue when started from timer.
I'm experiencing the same issue with my EDA500. My readynas also sometimes just gets stuck saying booting and I have to power both the nas and expansion chassis off completely and then when I power on again they are fine.
I have a 314 and this happens about once a week. I am on OS 6.4.1.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS 516 with EDA500 Expansion unit issue when started from timer.
Perhaps you could see if ReadyNASOS 6.4.2 (RC1) also resolves the problem for you?
Can you send me your logs (see the Sending Logs link in my sig)?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS 516 with EDA500 Expansion unit issue when started from timer.
Thanks. I'll give that a try tonight and will have to let it run for a couple of weeks to see if it still happens because I don't know exactly when it's going to do it. I'll also take a look at sending the logs in the next couple of days.