Bricked?

[karainier]

Hi all,

I booted my nas into a new network environment and it worked fine for a day. When I came home from work, nothing could access it. When I restarted it, it would not connect to my router. I have no idea what went wrong in that time. If I plug directly into my laptop and run uboot console, it recognizes the nas starting, but does not go to Marvel>> prompt. Any chance of recovering the current data? any chance of recovering the nas?

[Jocko]

Hi karainer,

I don't think your NAS is bricked :-D

I see several explanations for your issue:
a) The new network environment does not use the same IP range and the NAS uses a static IP: (for example 192.168.0.xxx instead of 192.168.5.xxx)
b) In the new network environment, no DCHP server is available where as the NAS IP should be set by a DHCP server.
c) You use the same IP range but the gateway IP (router) is changed and the NAS uses a static IP.

For the cases a and c, the easiest way is to change temporarily the router settings to be in accordance with the NAS settings, enable the DCHP feature in the web-interface and restore the original router settings

with case b, you should only enable the DHCP server on your router, to restore access

[karainier]

Jocko, thanks for your reply. My internal range and gateway are the same.

Code: Select all

Private Network
Router/Gateway Address    192.168.1.254
Subnet Mask    255.255.255.0
Private Network DHCP Info    
Range    192.168.1.64 – 192.168.1.253

External settings are not the same, do I need to change them?

Code: Select all

Connection Type    Direct IP (DHCP or Static)
Current Internet Connection    
IP Address    162.xxx.10.x
Subnet Mask    255.255.252.0
Default Gateway    162.xxx.8.x

DHCP server is enabled on router. Did 15.0 firmaware have a static IP configured by default? I never set a static IP, so would DCHP be enabled by default?

[Jocko]

Hi karainier,

Ok

Did 15.0 firmaware have a static IP configured by default? I never set a static IP, so would DCHP be enabled by default?

yes, if you did not change it, the NAS get its IP with the DHCP server by default.

If the NAS is on the "private network", the DHCP has to be available on the subnet 192.168.1.xxx. Maybe is not the case. See your DCHP settings.

[karainier]

Hi Jocko,

You were right that my issue is just with the new network environment. I plugged the nas into the old router and could access it fine, no brick or corruption. I did however compare the lan configurations and they are identical. I also confirmed DHCP was enabled on my nas. I attached pictures to confirm. Are there any other issues you can think of?

nas.PNG

oldrouter.PNG

newrouter.PNG

[Jocko]

Hi karainier,

I have another idea: I assume that the new router has a firewall.
So search if some rules exist over the private network especially for the ports 137-139 and 5789 (this one is used by the fvdw-sl assistant to discover the NAS). If you can try to disable it to see what happens

[fvdw]

my 2 cents, because it worked with the new router for some time (you mention that in your first post), and you did not change any settings on the router until you lost connection and the nas works fine on the old router, than the only conclusion can be that your router is not working properly. (defect). Sometimes rebooting may make it work again

[karainier]

It may have been something to do with my dhcp lease. after leaving it connected for 24hrs, it received a new ip :woohoo

thanks for the advice and help