OUR NETWORK:TiVo Community TechLore Sling Community MyDigitalEntertainer See all... About UsAdvertiseContact Us

 
Learn about scoring Forum's Raw Score: 137600.0
October 19, 2009 09:34 AM

Categories: Networking and Remote Access

Rating (0 votes)
Rate This!

Member Avatar

cappellof

Member
Joined: 10/10/2009

Last week, I went to connect to my EX 485 and could not.  All 3 aqua lights were steady on the server, but I still could not connect to the console.  At that time, I could ping it.

 Since it was unresponsive, I tried to reboot it.  Held the power button down until the server shut off, then restarted it.  Now, the server comes up to a point where the health light is blinking aqua, but it gets no further in the boot process.  No disk lights come on, and I can't ping it.  My network hub shows that there IS an ethernet connection.

This all happened less than a month after I was forced to do a factory reset due to the same problem.  I hate to keep losing my backup and shared data!  Does anyone have suggestions about how to proceed or diagnose the problem.  Doing a factory reset every month is unacceptable.

 Thanks,

Carl

Discussion:    Add a Comment | Comments 1-6 of 6 | Latest Comment

October 29, 2009 9:29 PM

I'm experiencing the same symptoms. About a month after I got my EX485 I couldn't connect to the server - status lights steady blue but the connector icon is grayed out. The only resort is to force shutdown. I was troubleshooting the problem off and on for over a month with HP (Case #0909201064 if you're monitoring this HP). We tried everything (factory reset, chkdsk, workstation OS reinstall) and the problem continued. They finally sent me a new chassis but the lockups continued.

Suspecting disk corruption due to all the forced shut downs I bought a new drive and performed another factory reset. After 2 weeks of relative normalcy, the condition returned. The only thing that I have been able to identify is that the lockups occur between 12:15 & 12:25AM - Event log messages such as "the previous shutdown at 12:22 was unexpected."

If anyone has ideas on how to resolve this issue, please reply to this thread. HP Support has been ineffective thus far. I am VERY disappointed and also VERY surprised to be having these issues after reading such great testimonials about the Home Servers. I really want this to work to store my music files - I need the server to work to back up family photos.

Jeff

November 17, 2009 5:36 PM

I called HP support again and went with a server reset this time (instead of full factory reset). It took several tries before the server would reset, but it's finally back online now. I'm going to bang on it for a week or so to see if the problem comes back. Server is still under warranty until February 2010, so I want to resolve any problems before then.

November 19, 2009 6:16 PM

Do either one of you hae any addins installed? It could be one of the addins causing the issues.

"everything will be ok in the end. if it's not ok, it's not the end" - unknown

November 19, 2009 9:37 PM

I can say with some confidence that my issues are related to bad drives. Even the brand new HP 1TB and 2TB Seagate that put into the server had bad sectors. They both passed SMART checks, but when the server does its nightly ChkDsk, it locks up. I plugged the drives into a workstation and ran WD's Data Lifeguard Tools Extended Drive checks to identify the problem. Sadly the HP ChkDsk does not report any problems - very frustrating.

November 22, 2009 5:48 PM

Well, my server became unresponsive to the network again after several day of uptime. Today, I'm doing a full factory reset after pulling out my addin 1.5TB Seagate disk. I'll give it a week to soak and see where I am.

Saw absolutely NO errors in the server's event log related to disk I/O failures.

November 22, 2009 6:02 PM

cappellof said: Well, my server became unresponsive to the network again after several day of uptime. Today, I'm doing a full factory reset after pulling out my addin 1.5TB Seagate disk. I'll give it a week to soak and see where I am. Saw absolutely NO errors in the server's event log related to disk I/O failures.
That was very frustrating to me as well - the fact that there were no disk errors logged.  Despite having drives with bad sectors (they read/write reliably, pass SMART, but fail extended disk tests) my server would just lock up after Midnight when it ran through the normal ChkDsk routine.  I think this is something that HP or Microsoft should be able to handle.

Discussion:    Add a Comment | Back to Top | Comments 1-6 of 6 | Latest Comment

Add Your Reply

(will not be displayed)

Email me when comments are added to this thread

 
 

Please log in or register to participate in this community!

Log In

Remember

Not a member? Sign up!

Did you forget your password?

close this window
close this window