I have an old server I had put windows 2000 server on. it was working for fine for quite a while, I did some maintenance on a different SCSI bus in the system adding some new disks. I boot now after it goes through the normal bios and SCSI firmware it starts booting windows. The blue progress bar gets to the end then I get some kind of BSOD usually saying inaccessible boot device, check connections, termination. I didn't work on that one, and if was that issue bios wouldn't even see disks even with termination issue. I doubt is driver related since all the controllers are the same as before when worked.
Safe mode, last good config both result in same error. Got install disk went into repair mode. Automatic repair will not recognize install. try console select the OS and get command line. Ran chkdsk it gets to like 4% and quits saying 1 or more unrecoverable errors detected. Try fix MBR said original had some issues and made new successfully. I also did a fix boot and completed ok. I reboot it does same thing after I get a disk checking page after the windows is loading screen. Check said was checking disk I then get same BSOD.
I began suspecting maybe ntldr is bad tried replacing from CD, but I don't see it on CD and can't look into directories on the CD. change to CD do dir get list then try CD to a directory on it I get error saying specified directory don't exist.
I also had the system up and running after I did changes to system, then had power issue and system went down. Now I have this issue.
I saw things about corrupt system hive online, but don't quite sound like my issue. Others say registry is messed up with controller driver, but that usually relates to changing system with same hard disk, or adding new controller. However, I suppose it could be possible due to sudden power cut, but never had system do before when that happened.
any ideas of other things to try or how to replace ntldr or if these other two things relating to corruption need to be looked at too?
I've never really done repairs with windows 2000 before, and only had check disks fail when drive was actually showing other signs of possible failure. So not sure, if disk could be failing and just not showing other signs yet. But I had an identical model disk in same system fail so think good possibility, but seems like software since begins loading. No big deal just wipe and reload OS, but if I can learn some more about repair process and save current install I would rather do that.
Safe mode, last good config both result in same error. Got install disk went into repair mode. Automatic repair will not recognize install. try console select the OS and get command line. Ran chkdsk it gets to like 4% and quits saying 1 or more unrecoverable errors detected. Try fix MBR said original had some issues and made new successfully. I also did a fix boot and completed ok. I reboot it does same thing after I get a disk checking page after the windows is loading screen. Check said was checking disk I then get same BSOD.
I began suspecting maybe ntldr is bad tried replacing from CD, but I don't see it on CD and can't look into directories on the CD. change to CD do dir get list then try CD to a directory on it I get error saying specified directory don't exist.
I also had the system up and running after I did changes to system, then had power issue and system went down. Now I have this issue.
I saw things about corrupt system hive online, but don't quite sound like my issue. Others say registry is messed up with controller driver, but that usually relates to changing system with same hard disk, or adding new controller. However, I suppose it could be possible due to sudden power cut, but never had system do before when that happened.
any ideas of other things to try or how to replace ntldr or if these other two things relating to corruption need to be looked at too?
I've never really done repairs with windows 2000 before, and only had check disks fail when drive was actually showing other signs of possible failure. So not sure, if disk could be failing and just not showing other signs yet. But I had an identical model disk in same system fail so think good possibility, but seems like software since begins loading. No big deal just wipe and reload OS, but if I can learn some more about repair process and save current install I would rather do that.