sa0 becomes detached, then destroyed
Dan Langille
dan at langille.org
Sun Aug 14 15:33:33 UTC 2016
Hello,
Can you help me understand the issue here. Why does sa0 keep disappearing?
Is it the fault of sym0? Perhaps I should reseat the card.
Aug 13 17:50:29 knew kernel: (sa0:sym0:0:1:0): phase change 2-7 6 at 0e4f75b0 resid=5.
Aug 13 17:50:29 knew last message repeated 2 times
Aug 13 17:50:29 knew kernel: (sa0:sym0:0:1:0): phase change 2-3 6 at 0e4f75b0 resid=5.
Aug 13 17:50:29 knew kernel: (sa0:sym0:0:1:0): phase change 2-7 6 at 0e4f75f0 resid=1.
Aug 13 17:50:29 knew kernel: (sa0:sym0:0:1:0): phase change 2-7 6 at 0e4f75f0 resid=1.
Aug 13 17:50:29 knew kernel: (sa0:sym0:0:1:0): phase change 2-3 6 at 0e4f75f0 resid=1.
Aug 13 17:50:29 knew kernel: sym0: unexpected disconnect
Aug 13 17:50:29 knew last message repeated 2 times
Aug 14 06:35:47 knew kernel: sym0:3:control msgout: 80 6.
Aug 14 06:35:49 knew kernel: ch0 at sym0 bus 0 scbus8 target 3 lun 0
Aug 14 06:35:49 knew kernel: ch0: <COMPAQ MSL5000 Series 0520> s/n 3G22JJP38S46 detached
Aug 14 06:35:49 knew kernel: (ch0:sym0:0:3:0): Periph destroyed
Aug 14 15:15:09 knew kernel: sa0 at sym0 bus 0 scbus8 target 1 lun 0
Aug 14 15:15:09 knew kernel: sa0: <COMPAQ SuperDLT1 5F5F> s/n CXB37H0071 detached
Aug 14 15:15:09 knew kernel: (sa0:sym0:0:1:0): Periph destroyed
--
Dan Langille - BSDCan / PGCon
dan at langille.org
More information about the freebsd-scsi
mailing list