Marc Collin a écrit :
Le 12 Octobre 2004 11:59, Mikus Grinbergs a écrit :
On Tue, 12 Oct 2004 09:39:58 -0500 Danny Sauer
wrote: SCSI parity errors are often indicative of improper SCSI termination, cable too long, or problems with a particular device. It is almost always a hardware problem.
SCSI FAQ entry #1:
q: I'm having a problem - any problem - with my SCSI devices. Why? a: Check termination, and maybe check cables.
--Danny, noting that nearly every problem traces back to termination :)
Pay attention to the messages shown on the console when you first boot your system. Typically, SCSI BIOSes will list their devices. If one or more SCSI devices do not show up, that is often a sign of improper SCSI termination or incorrect SCSI adapter settings.
mikus
all my scsi devices show up in the scsi bioes
Hello, I come in this discussion, in order to tell you that I got a similar problem with module sym53c8xx.ko when they switch from version 'i" (kernel 2.4 and early 2.6) to version "j". The error messages were not parity errors, but domain validation errors and the boot sequence was aborting. I used 2 different solutions before finding the reason : - 1° - I inserted the "i" sources and headers for scsi in the 2.6 kernel and it worked. - 2° - I patched the "j" release in order to stop domain validation end it worked. But I happened to change one of my old drives : a maxtor 72Gb hdd and release "j" works. Making some googling, I found that some people had problems with old drives. I suggest you to disconnect ( one by one) your drives and to check if the boot process succeeds. To be complete, I installed this old drive in my summer house with release "j", but with an adaptec scsi 29160 adaptor, and it works ! Michel. -- Michel et Catherine Garnier 4 résidence les chênes Le parc de Rocquencourt 78150 Rocquencourt Tel/Fax : + 33 (0)1 39 43 80 13 Email : Michel.R.Garnier@wanadoo.fr Catherine.F.Garnier@wanadoo.fr ICQ : 155138655