NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Power failure, Synchronisation, Ping success, Frontview not accessible
Hello all, after a power failure, I'm restart the NAS and I got at the RAIDar the information for "check filesystem 0% to 100%". At the "check filesystem 100%" it stay there for a while, about 3 mi...
Thx for posting the performance comparison.
AndyP-CH wrote:
Our Chat, I'll terminate it as "Problem solved". You agree?
Yes - you can always start another one if new issues arise.
AndyP-CH wrote:
Once again, I like to say thank you for your great and efficient Support.
I'm appreciate it a lot. You was a great help for me.
Thank you very much!
I'm glad I could help.
Hi Stephen
Thanksf for your reply!
I got a Win 10 Update and an edge update some days before. After that I was not able to run Frontview within Edge.
But within IE I was able to run Frontview.
But thtat´s not I'm asking fore.
I'm asking for:
Can you tell me; how long it will take to Synchronize my 1.3 TB NAS?
Until now I'm wating since about 45 hours for success.
The blue Power LED at the ReadyNAS is blinking regularly 2 x per second and the LED for Drive # 1 is flikering all the time as well. The LED for Drive # 2 is illuminated steady, I guess.
And can you tell me; Is it normal that I'm not able to run Frontview at synchronisatiuon state?
Many thanks for your help!
Kind regards
Andy
AndyP-CH wrote:
Can you tell me; how long it will take to Synchronize my 1.3 TB NAS?
Until now I'm wating since about 45 hours for success.
45 hours is much longer than it should take.
AndyP-CH wrote:
And can you tell me; Is it normal that I'm not able to run Frontview at synchronisatiuon state?
It's not unusual for it to be non-responsive for a little while, but again, it shouldn't be unreachable for days.
Hi Stephen
thanks for your reply.
I've still no access within frontview to the nas and RAIDar do not recognize it as well.
And I'm able to ping it and the nas-address give me the answer.
Antwort von 192.168.1.44: Bytes=32 Zeit<1ms TTL=64
At cmd I run:
net use \\192.168.1.44 /user:192.168.1.44\admin *Password*
I got the result:
Systemfehler 67 aufgetreten
Der Netzwerkname wurde nicht gefunden
As I'm disconnect the ethernet cable from the nas, the Disk activity LED is blinking 4 x.
As I'm reconnect the ethernet cable to the nas, the Disk activity LED is blinking 4 x also.
And the router show the NAS with the IP:192.168.1.44 again.
And here nothing has changed also.
Until now I'm wating since about 60 hours for success.
The blue Power LED at the ReadyNAS is blinking regularly 2 x per second and the LED for Drive # 1 is flikering all the time as well. The LED for Drive # 2 is illuminated steady.
I like to wait another 48 hours for the success ... wait and see ...
If this not comming to a success, what can we do?
Do you have an idea?
Regards
Andy
AndyP-CH wrote:
At cmd I run:
net use \\192.168.1.44 /user:192.168.1.44\admin *Password*
Try net use \\192.168.144\C /user:admin nas-admin-password
One option is to try to boot the system with disk 1 removed (power down before removing the disk).
If that also doesn't work, you can try booting with disk 2 removed (again, power down before you manipulate the disks).
Perhaps label them by slot as you remove them, so there's no chance of mixing them up.
net use \\192.168.144/C /user:admin nas-admin-password
I tried and it takes aprox. 10 sec until the message appear:
Systemfehler 67 aufgetreten
Der Netzwerkname wurde nicht gefunden
Try to boot the system with disk 1 removed (power down before removing the disk)
and also boot with disk 2 removed (power down before removing the disk) I'm working on it last Wednesday and didn't help.
I think, I must have had pull the power cable to power down the nas.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
