On Sat, Dec 20, 2008 at 12:04 PM, Borja Tatay <borja.ta...@gmail.com> wrote: > Hi again, thanks for the help :-) > > I checked it and showed me this: > ....... > [ 8611.378603] sym0: SCSI parity error detected: SCR1=1 DBC=1000000 SBCL=29 > [ 8611.378846] target0:0:1: control msgout: c. > [ 8611.378967] target0:0:1: has been reset > > [ 8611.379007] st0: Error 70002 (sugg. bt 0x0, driver bt 0x0, host bt 0x7). > [ 8612.387563] target0:0:1: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset > 31) > [ 8612.389285] st0: Block limits 4 - 16777212 bytes. > [179136.100323] sym0: SCSI parity error detected: SCR1=1 DBC=11000000 > SBCL=a9 > [179138.099309] sym0: SCSI parity error detected: SCR1=1 DBC=1000000 SBCL=29 > [179138.099555] target0:0:2: control msgout: c. > [179138.099678] target0:0:2: has been reset > [179138.099958] st1: Error 70002 (sugg. bt 0x0, driver bt 0x0, host bt 0x7). > [179143.098556] target0:0:2: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset > 31) > [626463.307367] st1: Block limits 4 - 16777212 bytes. > ......... > > I'm not sure what it stands for ... >
Parity errors most likely mean bad hardware. First check the cables. Are they properly terminated? Is the scsi card set on the correct termination mode? If all is well with that remove all other scsi devices that are on the same card. If there are no other devices replace the scsi card. And finally if that does not help it is probably a bad tape drive. John ------------------------------------------------------------------------------ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
