RE: source: disk, event id: 51, winxp sp2 clean install sata hd er
- From: forthurst <forthurst@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 11 Sep 2005 11:36:01 -0700
I have been having 51s since installing SATA via a PCI card. I also get
associated Error 9s (The device, \Device\Scsi\SI31121, did not respond within
the timeout period); I used to get the latter error in respect of SI3112r,
but I then flashed the PCI card with a non-RAID version of the bios; so
apart from the denominated device, nothing changed. My intention had been to
not only increase my online storage, but also improve the system performance.
So I then reinstalled the new Seagate with the System partition. The result:
51s and Error 9s at boot up. The 9s are rather alarming because the whole
system stops for about 45 seconds (whose idea of a timeout period is that,
for goodness sake?).
I cant decipher the error block for 51 because the SCSI request block
appears to contain at 0x38: 4000 which as far as I can see is a meaningless,
ie an unspecified Status and SubStatus according to any definition of SCSI.h
I can find.
I also note that in the Registry, at
HKey_Local_Machine/Harware/DeviceMap/scsi, in addition to the new SATA at
Scsi Port 2, we now have at Ports 0,1 the IDE hard disk and the ide DVD.
As 51s appear to occur on a multiplicity of hardware combinations, the sole
common factors appear to be XP and SATA. Further, as these new SATA
interfaces and associated discs are significantly faster than the old ATA
stuff, I cannot believe a performance issue arises. I am tentatively guessing
that XP has a problem managing data for transfer with these devices and
occasionally loses or corrupts buffer contents. I have for example had the
paging file on both the SATA drive and on the old hard disc, as the ONLY
active file - to no effect ie the 51 still references the SATA drive which
does not now contain the paging file; maybe transfer data is being paged so
becomes unavailable when required - who knows?
Because XP appears to need to accomodate the old hard drive on a SCSI port,
I suspect XP may contain spurious hierachies which might be hard to correct.
As 51s are actually Warnings and not Errors, I cannot see permanent data loss
being a possibility.
With regard to the timeouts (error 9), I suspect the SATA board is not
responding because it never received a transfer request in the first place.
For the time being, I do not intend to take any further action, unless
someone can convince me I might scramble my disc storage. Presumably the
majority of xp users will be oblivious to the event viewer or its
significance, but would likely notice if their data was scrambled up.
.
- References:
- source: disk, event id: 51, winxp sp2 clean install sata hd errors
- From: invalid@invalid.invalid
- RE: source: disk, event id: 51, winxp sp2 clean install sata hd errors
- From: Peter
- RE: source: disk, event id: 51, winxp sp2 clean install sata hd er
- From: invalid@invalid.invalid
- RE: source: disk, event id: 51, winxp sp2 clean install sata hd er
- From: Peter
- RE: source: disk, event id: 51, winxp sp2 clean install sata hd er
- From: invalid@invalid.invalid
- RE: source: disk, event id: 51, winxp sp2 clean install sata hd er
- From: Peter
- RE: source: disk, event id: 51, winxp sp2 clean install sata hd er
- From: invalid@invalid.invalid
- source: disk, event id: 51, winxp sp2 clean install sata hd errors
- Prev by Date: Re: How to stop HP Printer/photocopier
- Next by Date: Re: My USB Flash went crazy
- Previous by thread: RE: source: disk, event id: 51, winxp sp2 clean install sata hd er
- Next by thread: comm port inop.
- Index(es):
Relevant Pages
|