foy1der

System Drive Failing Saga

52 posts in this topic

I wanted to fill you folks in on how my server repair is going. I have finally gotten moved into my new house and I have slowly been rebuilding the server. I ended up buying a new hard drive in order to make shifting the data around a little easier. I bought a 2TB WD Black.

 

So I initially tried installing WHS 2011 but that install didn't complete. I switch back to version 1, but that install wouldn't complete as well. I started getting curious about hardware so I ran Memtest. Knowing that memtest could take a while, I started the test and stood up from my desk chair. By the time I had finished standing up, Memtest had found 125 errors in my ram. After running for an hour, it was up to 20k errors (I think I found the issue). So I swapped out the ram and ran the test again to make sure it wasn't the DIMM slots.

 

I have also not been able to reproduce the errors that WHS was finding in the system hard drive. I will just connect that one to the server and wait for it to fail, I guess.

 

With fresh ram, the WHS version 1 install went very well. However I still have one issue. My notebook will not complete the WHS Connector install. When I install the connector, I get a message that I need to update the connector software (see attached). When I go through the motions to complete this process, I get an error that "This operation cannot be completed at this time". I'm hoping that someone else might have encountered an issue similar to this. I have also attached a screenshot of the failure message.

 

MRH1O.jpg

 

QLfeZ.jpg

Share this post


Link to post
Share on other sites

I forgot those interesting details. When I try doing that, I get an error that the page cannot be found. When I ping "server" it fails to find the server. When I ping the server's IP address, I get a response. When I navigate to "192.168.0.190:55000" I get the connector home page. Lastly, when I download the connector install, I get the "This operation cannot be completed at this time" error.

 

I hope all of this isn't too confusing. Perhaps I should have made a flow chart.

Share this post


Link to post
Share on other sites

OK, so DNS is not working on your LAN - that's one issue, but not critical to getting the connector installed. Have you tried downloading the Connector installer to your client computer and running it locally?

Share this post


Link to post
Share on other sites

The only way I was able to get this far was to download the connector install on a different computer and install it from a USB stick. I should also note that on my desktop was able to install the connector software properly and it is running backups. The desktop can also ping "server" properly.

Share this post


Link to post
Share on other sites

OK, stupid question: you did uninstall the Connector before trying to install it again, right? Like I said stupid question, but just to cover all the bases :)

Share this post


Link to post
Share on other sites

No it's not a stupid question, I have indeed uninstalled the connector before trying to install the software.

 

Sent from my DROIDX using Tapatalk

Share this post


Link to post
Share on other sites

Map a shared drive over to the server

 

\\servername\C$ or \\ipadress\C$

 

 

and go to the software folder. The connector is in there and yes you need to remove the old connector.

Share this post


Link to post
Share on other sites

This is a fantastic thread. Foy1der, you are a rock in my opinion, I would have probably thrown things out the second floor window by now.

Share this post


Link to post
Share on other sites

One of the only things that I haven't tried yet (should have been first) is to try a wired connection.

 

Sent from my DROIDX using Tapatalk

Share this post


Link to post
Share on other sites

One of the only things that I haven't tried yet (should have been first) is to try a wired connection.

 

Sent from my DROIDX using Tapatalk

 

Good idea.

Share this post


Link to post
Share on other sites

Here are the steps I took to fix the issue:

1. Consume (at a minimum) two hop infused adult beverages.

2. Connect laptop to a wired ethernet connection.

3. Install connector software.

4. Ask "Why didn't I do this last week?"

 

Thanks for all the tips guys, I think we can mark this issue closed.

 

Probably not though, I'll wait for a couple days of backups to run first. ;)

Share this post


Link to post
Share on other sites

Here are the steps I took to fix the issue:

1. Consume (at a minimum) two hop infused adult beverages.

2. Connect laptop to a wired ethernet connection.

3. Install connector software.

4. Ask "Why didn't I do this last week?"

 

Thanks for all the tips guys, I think we can mark this issue closed.

 

Probably not though, I'll wait for a couple days of backups to run first. ;)

 

Do not...I repeat, DO NOT smack your head before you have the beverages. Good luck dude...again, can't wait to hear how this turns out for you.

Share this post


Link to post
Share on other sites

Do not...I repeat, DO NOT smack your head before you have the beverages. Good luck dude...again, can't wait to hear how this turns out for you.

 

Agreed, not before you consume the beverages - do it after; if you've had enough of them you won't feel it ;)

Share this post


Link to post
Share on other sites

OK, the beer didn't help. Well, it helped but it didn't really help. I was able to get the connector to install without too much trouble last night. After I unplugged the wired connection, I let the computer stay on over night (on a wireless connection) and it didn't create a backup.

 

Something that I just noticed: in the Network and Sharing Center, it says that I am connected to my new wireless SSID (Undercover Police Van #9). BUT! The desktop shows that it is connected to the old network name (Undercover Police Van #4). I feel that part of this might be some of the problem. For instance, while on a wired connection, I was able to RDP into the desktop. After trying this over wireless, I got the same errors that I had been getting earlier.

 

Interestingly, I cannot connect to the server using the connector software (on wired or wireless connection). I'm grasping at straws at this point.

Share this post


Link to post
Share on other sites

OK, the beer didn't help. Well, it helped but it didn't really help. I was able to get the connector to install without too much trouble last night. After I unplugged the wired connection, I let the computer stay on over night (on a wireless connection) and it didn't create a backup.

 

Something that I just noticed: in the Network and Sharing Center, it says that I am connected to my new wireless SSID (Undercover Police Van #9). BUT! The desktop shows that it is connected to the old network name (Undercover Police Van #4). I feel that part of this might be some of the problem. For instance, while on a wired connection, I was able to RDP into the desktop. After trying this over wireless, I got the same errors that I had been getting earlier.

 

Interestingly, I cannot connect to the server using the connector software (on wired or wireless connection). I'm grasping at straws at this point.

 

Undercover Police Van??? I hope you really are a cop, or you might just get a knock on your door :)

 

re: the wireless connection. Did you remove/delete all the existing wireless profiles before joining up to the new one?

Share this post


Link to post
Share on other sites

At some point in time, I'm sure if you looked at irony in wikipedia, you would see my list of SSIDs.

 

I did not remove the existing profiles. I will try removing all of them and then adding just the one that I am using.

Share this post


Link to post
Share on other sites

At some point in time, I'm sure if you looked at irony in wikipedia, you would see my list of SSIDs.

 

Ah, well, I use the original meaning of 'irony' when I use it, not the 'co-incidence' meaning that everyone seems to use they days.

 

I did not remove the existing profiles. I will try removing all of them and then adding just the one that I am using.

 

Let us know how that works out.

Share this post


Link to post
Share on other sites

I tried removing the old SSID's from the wifi setup, that didn't work. However, I did try something interesting. From "run", it executed the server's IP (//192.blah.blah.blah). BAM! There are all my shares. So for some reason, my notebook isn't recognizing the name "server" perhaps this is because I previously had the server named something else?

Share this post


Link to post
Share on other sites

Did you mention you had changed the server's name? I don't think you mentioned you changed the server's name. If you had mentioned you changed the server's name, a bunch of us would have speculated you have a DNS issue. :)

 

Try flushing the DNS cache. From a CMD box, type ipconfig /flushdns. If you're curious, try ipconfig /displaydns to confirm that the laptop thinks the server has the old name.

Share this post


Link to post
Share on other sites

ikon, you may be a genius!

 

A0kAK.jpg

 

I'm when I get home I'll post back to let you know if this fixes it. I have my hopes high for this one.

Share this post


Link to post
Share on other sites

I have actually met a couple geniuses in my life; trust me, I ain't one :)

Share this post


Link to post
Share on other sites

OK, you were right. You aren't a genius. I also talked to my IT guy at work today. So here is what I did:

ipconfig /flushdns

nbtstat /R /r /RR

arp /d *

 

After all of this, my old server name is the only thing left when I do a "ipconfig /displaydns"

Share this post


Link to post
Share on other sites

I also tried to manually manipulate the hosts files (hosts, lmhosts). Those appear to just be sample files (windows/system32/drivers/etc/). If I have the wrong file location perhaps someone might know where I can find the correct file location.

Share this post


Link to post
Share on other sites

OK, you were right. You aren't a genius. I also talked to my IT guy at work today. So here is what I did:

ipconfig /flushdns

nbtstat /R /r /RR

arp /d *

 

After all of this, my old server name is the only thing left when I do a "ipconfig /displaydns"

 

Are you saying the DNS cache has the old name still in it? If so, that is a problem. Did the command give you a response of Windows IP Configuration. Successfully flushed the DNS Resolver Cache ?

 

I also tried to manually manipulate the hosts files (hosts, lmhosts). Those appear to just be sample files (windows/system32/drivers/etc/). If I have the wrong file location perhaps someone might know where I can find the correct file location.

 

You edit the hosts file, using the examples inside as a guide. Just don't put the comment character at the front of the line. But, to me, this is a last resort. You should not need a local hosts file if your LAN is working properly. There should be a line that says:

 

127.0.0.1 localhost

 

Just put another one under it with the address and name of your server.

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

  • Similar Content

    • IndyLux
      By IndyLux
      Hi Guys,
       
      I've got a friend who bought an HP Media Smart Server on my recommendation (we all have friends like that, right?). Anyway, it died on him. The data is safe, but he wants to buy / build a new server.
       
      1) Am I wrong in steering him towards building a new version 1 system? Both he and I are used to it and drive extender is important to us.
       
      2) Where can he get an OEM copy of WHSv1? It's not on NewEgg anymore nor can I find it on eBay.
       
      Thanks guys,
      Chris