Added ST318451...now a stop error..XP
I dont really know what happened here, but I just added a 15k 18gig Seagate Cheetah to an existing system, and now I cant boot with that drive in place. I get a stop error without fail.
***Stop: 0x000000D1 (0x00000028, 0x00000009, 0x00000000, 0xf77cdbaf)
***SCSIPORT.SYS - address f77cdbaf base at f77c9000, datestamp 3d6ddb03
I have a 9.15 gig 10k west dig with the OS - XP Home (yeah yeah), and an Ultrastar 15k 18 gig (unformatted) and added the Seagate to that. The adapter is an LSI U160, which has worked fine since I got it.
I can remove the IBM, and it makes no difference, same exact error, everytime. If I pull the Seagate, it boots normally. I tried the Seagate low-level, but it said there was an error, and wouldnt allow me to proceed. Instead, used the "write 00's" function, and tried again...no dice.
***update***
Tried to install XP Pro on the Seagate, by itself with no other drives in place. Lets me get to the agreement, then tells me that setup cannot access the drive.
Not sure which way to proceed from here.....please advise.
***Stop: 0x000000D1 (0x00000028, 0x00000009, 0x00000000, 0xf77cdbaf)
***SCSIPORT.SYS - address f77cdbaf base at f77c9000, datestamp 3d6ddb03
I have a 9.15 gig 10k west dig with the OS - XP Home (yeah yeah), and an Ultrastar 15k 18 gig (unformatted) and added the Seagate to that. The adapter is an LSI U160, which has worked fine since I got it.
I can remove the IBM, and it makes no difference, same exact error, everytime. If I pull the Seagate, it boots normally. I tried the Seagate low-level, but it said there was an error, and wouldnt allow me to proceed. Instead, used the "write 00's" function, and tried again...no dice.
***update***
Tried to install XP Pro on the Seagate, by itself with no other drives in place. Lets me get to the agreement, then tells me that setup cannot access the drive.
Not sure which way to proceed from here.....please advise.
0
Comments
Can't be 100% sure what specifically went bad, but it's not a good sign when the PC won't boot into windows with the drive connected as a slave/secondary.
Also be sure the cabling isn't bad/defective, it could cause read/write issues that could lead to this as well. Outside of that I'd assume the worse.
BTW, welcome to icrontic
And did I mention that this is SCSI? No master/slave here...its device 3 of a possible 15.
And out of curiosity Tex, where are you from? I'm just north of dallas....
Yeah, overlooked that... problem's the drive anyways assuming the cable isn't defective.
Still, the low level format is non-functional.
What the hell did I get into here?