This message is from the T13 list server.
Hale, So while I agree that if you are getting CRC errors you are having BIG problems, the fact remains that you will have much more setup and hold time under PIO Mode [0], so you still have some possibility of writing the data to the drive. This is why I say don't stop at PIO Mode [4], as you don't get additional setup/hold but yet loose the iCRC. I DO NOT agree with BLUE SCREEN. The system can have LOTS of other data in the file system cache that could be written to other drives, or are different patterns, that can and should be written to a drive. I DO agree that you should very NOTICEABLY notify the user that you are getting MAJOR CRC errors. Jeff > -----Original Message----- > From: Hale Landis [mailto:[EMAIL PROTECTED]] > Sent: Friday, December 14, 2001 7:18 PM > To: [EMAIL PROTECTED] > Subject: RE: [t13] UDMA 'recovery procedure' > > > This message is from the T13 list server. > > > On Fri, 14 Dec 2001 15:28:11 -0800, Eschmann, Michael K wrote: > >[...] MWDMA is a bad choice, as is > >SWDMA too because it has no CRC checking and lots of people > have poor MWDMA > >implementations and many do not have SWDMA. > >But why would you go all the way to PIO-0? Wouldn't it be > prudent to go > >from PIO-4, then step down to 0? > > If you have stepped down to U-DMA mode 0 and you are still getting > excessive ICRC errors then maybe it is time to "blue screen" and tell > the human to fix their hardware. Under no conditions would I > recommend stepping down even more to MW DMA or any PIO in this case. > Just how many undetected data corruption errors can your OS or > application programs live with??? > > > *** Hale Landis *** [EMAIL PROTECTED] *** > *** Niwot, CO USA *** www.ata-atapi.com *** > > > Subscribe/Unsubscribe instructions can be found at www.t13.org. > Subscribe/Unsubscribe instructions can be found at www.t13.org.
