HDX fails after couple of hours

Posted by: Checkthisout68 on 17 April 2015

Hi, my HDX 2TB (2014, 1.7b) has got a new habit: After having run for say 5-6 hrs it goes offline and shows "please wait" in the display. It stays there. I can shut it down pressing the front button, then it will reboot after main switch off/on and all is fine for until 5-6 hrs later. There are no error messages under system messages either. 

 

Any idea from the experts?

 

Best

Chris

Posted on: 17 April 2015 by hungryhalibut

Try fixing its IP address.

Posted on: 17 April 2015 by Checkthisout68

It is set to have the same IP address every time it boots. 

Posted on: 17 April 2015 by hungryhalibut

Have you bound the IP to the MAC address in the router as well as fixing the IP in the HDX itself? You need to do both.

Posted on: 17 April 2015 by garyi

I doubt the issues relates to the network, looks like a harddrive or hardware failure.

Posted on: 17 April 2015 by Checkthisout68

What do I have to do about the IP address inside the HDX?

Posted on: 17 April 2015 by hungryhalibut

You may be able to do it via the front panel user menu; if not, you need to download the set IP tool from the Naim website. 

Posted on: 18 April 2015 by robgr

Have you made any network changes recently, this sounds like a DNS lease renewal issue but I'm no network expert. Would this have any bearing anyway if the HDX is set to a static IP?

Posted on: 18 April 2015 by garyi

I don't think its network related at all. 

Posted on: 18 April 2015 by DavidDever

There are two IP addresses for the HDX - one for the front panel network touch control client, and one for the server mainboard itself - you must set both.

Posted on: 18 April 2015 by Checkthisout68

Yes, both set. I know.

Posted on: 18 April 2015 by Paul Quigley ie

I had this message appear when the hard disk was failing.  However it seams too soon for 2014 disk to fail. 

Posted on: 18 April 2015 by Checkthisout68

Its all possible, maybe an upcoming hard drive failure. 

 

Both IP addresses are set to fixed in the rooter menu. Set IP tool does not find my HDX. There are no further options for network setup in the HDX frontend or N-serve menu.  

 

Now what I did is I have shut down the HDX, then shut down the Internet router, then booted the HDX and waited until it said "looking for network" and then fired up the router again. 

 

It has been up and running since the morning now, will see. 

 

Chris

Posted on: 18 April 2015 by DavidDever
Originally Posted by Checkthisout68:

Its all possible, maybe an upcoming hard drive failure. 

 

Both IP addresses are set to fixed in the rooter menu. Set IP tool does not find my HDX. There are no further options for network setup in the HDX frontend or N-serve menu.  

 

Now what I did is I have shut down the HDX, then shut down the Internet router, then booted the HDX and waited until it said "looking for network" and then fired up the router again. 

 

It has been up and running since the morning now, will see. 

 

Chris

So - you've DHCP reserved the addresses by MAC address at the router, but that is not the same as setting them to a static IP via the Set IP tool - so there is likely something going on with your router and its DHCP lease(s), autodiscovery, what have you.

Of course, if the Set IP tool was unable to find both devices in the first place, there's your clue....

Posted on: 18 April 2015 by Checkthisout68

Who confirms that Set IP tool is finding any HDX (2014) through Parallels on Mac OS Yosemite?

 

Mine does not.

 

Chris

Posted on: 18 April 2015 by Checkthisout68

Alright, got me an old Windows notebook and have changed the IP settings inside the HDX.

 

First reaction after reboot: "TouchLinks Loader safe mode enabled" and stops booting.

 

Then booting without network cable and plugging it back in after fronted menu visible.

 

The frontend IP now toggles between 192.168.178.45 (as set) and .41. The router says it will always use the same IP address for the frontend, however, in fact it does not. It is Fritz router. 

 

Going back to DHCP for now.

 

Chris