Link to home
Start Free TrialLog in
Avatar of xsawkins
xsawkinsFlag for United States of America

asked on

How can I fix Server 2000 OS?

Dell PowerEdge 840
Service Tag: JT72MD1
Setup has a Perc/5i adaptor, DVD and Floppy drives, 3 160 GB HDD's
OS I believe is Windows 2000

I have a client whom hasn't had us service their server in several months, and their server's OS has gotten corrupted. Now this server needs to be fixed since it has software on it that allows them to read some particular data on the RAID5 array.

I've tried booting off of a system disk to attempt a repair, but the server doesn't give any options to 'hit any key to boot from CD' etc. I have connected a separate hard drive to SATA0 on the motherboard itself and activated the port in the BIOS. Only problem is, after the system reboots to put the change into effect, it doesn't keep the change. SATA0 is 'Off' when I check back in the BIOS.

Which for that particular issue, I have tried changing out the battery on the BIOS. That didn't fix that particular issue. I have even downloaded the server BIOS from the Dell website and placed the file on a floppy in the proper manner directed on the Dell site. This didn't get any where either, the system will read the floppy disk, but it never really even truly gets started with the upgrade. It will sit there, this is what it reads, User generated image
The last thing I have done is insert a spare video card I had laying around, as when the system boots up, it will revert to a blank screen after going through system boot up. Which the video card revealed what it had been saying,
'Loading PBR for descriptor 1...done.'

The message will stay on the top left corner of the screen, and doesn't do anything else.

I've run out of ideas on what to do in getting this thing running again, so I would certainly appreciate
 any assistance in this matter.
Avatar of dew_associates
dew_associates
Flag of United States of America image

First, how do you know the operating system is corrupted?

You need to return the system to the state it was before you touched it. If the original video card was bad, then change it. If you made any BIOS changes, reverse them.

Next, have you checked the battery on the Perc/5i adaptor card?

You need to create a boot disk to point the system to the Perc/5i adaptor, and thus to the raid array.

You need to locate and download the correct boot disk data and be able to identify the correct Windows 2000 mass storage driver.

One of the files in the driver package is TXTSETUP.OEM. Edit TXTSETUP.OEM with NOTEPAD (or a text editor of your choice). In the [Defaults] section locate the line that starts with “scsi = “. The
value on the right hand side of the equals sign must represent the Windows 2000 mass storage driver.

You will find all of the drivers you need here:

http://support.dell.com/support/downloads/driverslist.aspx?os=WNT5&catid=-1&dateid=-1&impid=-1&osl=EN&typeid=-1&formatid=-1&servicetag=&SystemID=PWE_P4_840&hidos=WNET&hidlang=en&TabIndex=&scanSupported=True&scanConsent=False
Avatar of xsawkins

ASKER

The OS being corrupted is our best guess, as it doesn't boot up after it passes through the BIOS.  Far as changes, the only changes we've made is the boot sequence when we were wanting the server to boot off of the Windows Server 2000 disc in an attempt to repair the OS. Which it never did offer any 'hit any key to boot from CD etc.'. Just goes straight to the blank screen with 'Loading PBR for descriptor 1...done.'

Also, the server didn't have a video card. It used what was built into the motherboard itself. Which is why I had put a video card in there to see if the motherboards' video card wasn't displaying something after it passed through the BIOS boot.

On the 21st, we had also switched the Perc/5i into another Dell server we had (So battery works fine). Essentially as a means of seeing if it would work on this computers' BIOS. Which still came with same results. Both servers can recognize the RAID adaptor, and in the adaptors configuration, it detects the RAID5, the 3 HDD's attached to it, and reads them as being in optimal condition. Seeing as the system detects the Perc/5i adaptor just fine and the RAID on it, would I still need to point the system to the adaptor?

We did a test, where we unplugged the RAID5 from the Perc/5i adaptor to see if it would boot from the Windows Server 2000 disc we've been trying to have the system boot from and failing. This time, it booted from the disc perfectly fine, despite us having setup the BIOS to boot from the disc before the RAID itself earlier. We have even gone into the boot menu and told the system to boot from the disc itself, and still doesn't boot from the CD. Whether the CD is in the systems internal CD drive, or an external USB drive.

Apologies on the late update as well.
If I had to venture a guess, it would be that you have a BIOS issue, as you should be able to force the BIOS to boot to the CD first.
Possibly, but the BIOS on two different Dell Server systems both not wanting to boot directly to the disc? A bit unlikely I would have to imagine, unless we are just that unlucky!
ASKER CERTIFIED SOLUTION
Avatar of dew_associates
dew_associates
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Update: On Friday, several co-workers and I managed to get the server to boot from the Windows 2000 disc. Attempted to do a second level repair of OS, with the disc reporting being unable to locate any OS.

Previously we had attempted doing backup of RAID5 data with 3rd party software, but were unsuccessful.

We will be calling it quits on this server, as we have spent more time than are able to bill.

I wish to thank you two for taking the time in attempting to help us fix this server.
Calling it quits on attempting restoration of server with RAID5 data intact.

Hardware possibly damaged/worn out, or software corrupted.