Jump to content
RESET Forums (homeservershow.com)
awraynor

EX495 Server Recovery Fails

Recommended Posts

joem

Question on the "Connect directly to Server with Ethernet cable". Is that a crossover cable connected from the computer that you want to restore to the WHS?

Share this post


Link to post
Share on other sites
dvn

It's a normal Ethernet cable, Cat 5E or better.

Share this post


Link to post
Share on other sites
jmwills

Error messages...gotta love 'em. Remember there will be few times when an error is not logged into the Event Logs so always check there and most time a link back to M$ is given in those error messages.

Share this post


Link to post
Share on other sites
jasonhavens

I'm trying to use the recovery disk with my HP EX495. I never had the client computer connected to our homeserver. So it didn't have the WHS Connector installed. I also ensured that there was no temporary folder like the one listed above. The recovery disk proceeds to step 4 of 4, and then fails. The "Help" explanation says that an unidentified error occurred, which obviously isn't very helpful! Does someone here have a suggestion? I hope so. I have plenty of files on the data drives that I definitely don't want to lose. If someone is near the Florida Panhandle (or even Atlanta or Nashville), I'd gladly drop off to hire you to restore if nothing works here. Thank you in advance

 

Kind regards,

 

Jason Havens

Destin, FL

 

It's a normal Ethernet cable, Cat 5E or better.

Share this post


Link to post
Share on other sites
ikon

This is a bit confusing. If you're booting up from the server recovery disk, your local OS isn't involved in the process anyway, so it doesn't matter if it had the connector or not. It is important if you're trying to recover the local computer.

 

Are you certain you're using the WHS Server Recovery Disk?

Share this post


Link to post
Share on other sites
CablDeViL

Rich,

 

It worked great! Thanks for the instructions for this old hardware.

Share this post


Link to post
Share on other sites
sdruid

I have a hp mediasmart server but have no idea what model it is: ex490 ? ex495 ? 

saids intel celeron inside - on the front label...

on the bottom - RMN: HSTNA-W003 P/N, hardware revision - B 

 

I picked this up from a salvage place and it looked like it could be useful if it was running...

and I found ex490 recovery discs to restore it and the recovery fails at step 2 of 4...

I put a brand new harddrive in and think I got into recovery mode ok but not sure of that either at this point 

the health light blinks pink and red for a few seconds then it stays solid pink

since I'm getting the same error message not sure if I'm doing any of this right...

tried following instructions from another website I visited...

 

any ideas

Share this post


Link to post
Share on other sites
dvn
On 12/14/2010 at 5:18 AM, dvn said:

HP MediaSmart EX49x Reset or Restore

 

· Uninstall WHS Connector and related software

 

· Delete %TEMp%\PXE folder, if present

 

· Disable Windows Firewall

 

· Leave PC network adapter in DHCP

 

· Disconnect all USB devices from EX49x

 

· Connect directly to Server with Ethernet cable

 

· Perform Reset or Restore

 

· After successful reset/restore, reboot while still directly connected

 

· Run Connector software to finish setup

 

· Before connecting with newly installed Connector software, reestablish regular LAN connections

 

· Connect and download HP updates

 

· Windows updates, then HP updates again

Celeron? EX490

About 5 years ago I ditched the recovery disks w/ original OS and went with Server 2012. Did the install on another machine, then dropped the hard drive into the MSS and remoted in. I have the EX495. That's a Pentium E5200 cpu. Not sure how well the Celeron would run but the E5200 is responsive enough. I eventually swapped in an SSD for the OS drive. Performance was decent on the spinner, I just wanted to see how big a difference it made. Boots faster but that's about it.  

I remember that I wanted to get away from the drive extender technology. It's a lot of voodoo when things go bad. We figured out most of it but I think most of us got tired of fiddling with it. The good thing about 2102 is that you can image it for a backup. I put nothing but the OS on the drive so the image is small. 

  • Like 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×