I am in the process (three times now) of trying to do a factory rest. I have downloaded and run checksum on the PanAm SvrRecovery ISO file 01_07_03_13. First off, the system can’t see the SanDisk Cruzer Glide USB flash (16gb) to create the recovery boot , my XP SP3 system has no problem with it, as I had already created one for my other Sentinel DX4000 unit, I went ahead and used that one. Upon starting the recovery, the system does the formatting, loading files and drivers and comes up with the WDSentinel and an IP address. When trying to connect, I receive the proverbial message “503 Error, Service Unavailable” I have left WD 2 messages, but so far no answer, I have read all the blogs on this error and haven’t gotten an actual fix or answer. My other DX unit was reset with recovery 01-04-05-08 which I tried on this unit and got the same error. I don’t mind spending a whole day recovering it, but 3 days is a little to much.
Just curious why you are doing a recovery. As in if something was brokee, whatever might be preventing the recovery? No clue, just pondering.
I know there is a log file on the thumb for recreate (the middle step) not sure about Recover (The 3rd step). If there is no log file that gives you any insite, I believe I would backup and do the recreate and be sure and look at the end of that log file before moving on.
CHKSUM mismatch is the most common problem, but you alow that is good. I suppose if the box was running extremly slow for some reason, you might get the 503 if seetup was not complete. Of course with no monitor no way for you to tell. You might let it sit a couple of hours and try again?
I already have a 4tb DX4000 named WDSentinel, and needed to rename this one, can’t have 2 named the same on the same network (at least that is what it says in the documentation, so, the easiest (obviously not) thing was to restore to factory reset, change the name and go from there. So here I am with the error, I let it run all night and wasn’t any different, tried multiple PC’s to get access but no different, also tried multiple I.E’s (Safari, Foxfire, I.E.8). There must be a fix for it, either from MS or WD. I have tried everything I can think of, but to no avail.
Well sounds like you are on the right path then, just not going very far down the road.
Then perhaps during the blind setup it is seeing another box with the same name and bombing with an error we can’t click ignore on. Instead of simply shutting down the other box, if you have another router (DHCP) server, setup a mini Lan with just the helper PC and the server and run through it one more time?
If you don’t have the hardware handy just shut down the other one and reboot/clear your router/dhcp server. On the hellper client do ipconfig /flushdns
If you are still getting nowhere try a diff flash drive and port on the box.
I did have the other DX shut down. The first time it came up it had a different IP, but since it has had the same as my other unit. I will try to flush DNS.
I have seen names pop up doing installs that ar3e way left over. I think if you could do this on a “virgin” router/stand alone it might be best. But perhaps if you rweboot your router it may clear stuff up.
As in I think you should be able to ping wdsentinel and it not resolve to an ip before you start. I know with the box off it will not reply, but if it resolves, then it thinks there is a machine with that name out there.
Hey, you should be able to RDP to it.
username administrator
Pass Admin123 (I think) let me see if I can lookup the password
You are correct, I had to hold down the power button, which may indicate why the HD lights are on solid (possible rebuilding). I did try to access using MSTSC and recieved the same error. It did bring up the login screen and after I tried to login is when I received the 503 error.
By the way, is there another way to run setup without it wanting to reformat the drive (long process) keeping in mind I need to change the name and I can also give it a static IP.
I can’t seem to get my head around where yoiu would get a 503 error with MSTSC.
We have established something is wrong and you do get a 503 from a web browser.
I was hoping to remote to the desktop and look around/perhaps change the server name
At this point though I think you need to go ahead and reload it again. Perhaps even using a diff thumb drive.
Before you start the restore though, with both DX shut down, I would like for you to go to a cmd prompt and type ping wdsentinel It needs to say cannot find host wdsentinel.
If it returns an IP, any IP then I think that is the problem. Setup thinks there is a machine with that name and will not complete.
So FWIW, if you mstsc, login and see a web browser with 503, that may be the desktop of the server. Close that browser and see if you see the server desktop
First, I can not create another thumb drive, I purchased 2 the other day and when I tried to create it, WD Recovery Software could not find either of them (yet all my XP systems can read them). They are 16gb Sandisk flash drives which are exactly what I used on the previous unit. I was using that flash drive (from previous unit) to boot into recovery mode. Maybe there is something on that boot flash but I would assume not because it was made prior to setting anything up.
Bob
P.S.
I will try and reload (recover) again after I flush dns and check for an ip or name .
I tried it prior to starting the recovery and it states couyld not find WDSentinel. I just tried again while it is formatting and still the same statement. Once I reset all the routers and did not bring the other unit on line, I am assuming it flushed everything including the reverse lookup (Name vs IP).
Thanks,
Bob
P.S.
If it doesn’t work this time, I think a fire sales is in the making… Fire first then sale …
