1832212 Members
2387 Online
110041 Solutions
New Discussion

Help to read Log.

 
SOLVED
Go to solution
Daniel Caçador
Regular Advisor

Help to read Log.

Hi Friends somebody could confirm me if this is problem in controller SCSI? I think that he is.
8 REPLIES 8
Bharat Katkar
Honored Contributor
Solution

Re: Help to read Log.

Before suspecting the SCSI controller can you check for cabling issues or any loose connections. This may also cause SCSI reset problems.

Regards,

You need to know a lot to actually know how little you know
Thayanidhi
Honored Contributor

Re: Help to read Log.

Hi,
Generally SCSI lbolt errors recover itself. check how often you get this. Replace cable/terminator. Also check timout out values (pvchange).

In your case c0t1 devide have some problem.
That is bus 0 (ioscan -fnC ext_bus) target 1.

could be bad device too.

Regds
TT
Attitude (not aptitude) determines altitude.
Daniel Caçador
Regular Advisor

Re: Help to read Log.

which commands I can use to certify which problem of fact is occurring?

thanc's!
Victor Fridyev
Honored Contributor

Re: Help to read Log.

Hi,

Run
#dmesg -
#ioscan -fnCdisk
#dmesg -
Usually ioscan cause such messages.
BTW, possible reasons for such messages are: termination, cables, duplicate SCSI ID, broken disks.

HTH
Entities are not to be multiplied beyond necessity - RTFM
Steven E. Protter
Exalted Contributor

Re: Help to read Log.

Shalom Daniel,

lbolt erros caused by removing and replacing hot swap drives and hardware will go away after a system boot.

All other lbolt erros indicate a problem that must be dealt with.

It could be as simple as an unterminated scsi device. It could be cables, power or a device n the scsi chain malfunctioning.

ioscan | more

You should be able to match the ioscan output to the lbolt output and then figure out what he problem area is, if not isolate the exact device.

Since you are a new user, I will point out that we reward good answers in ITRC with point assignment. I do appreciate your thanks for my help in other threads, but forum ettiqute requests that you assign points, weighted for answers that helped you.

Please take the time to do so. I don't really need any, I already have myself a bunch.

Happy foruming.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Steven E. Protter
Exalted Contributor

Re: Help to read Log.

Shalom Daniel,

lbolt erros caused by removing and replacing hot swap drives and hardware will go away after a system boot.

All other lbolt erros indicate a problem that must be dealt with.

It could be as simple as an unterminated scsi device. It could be cables, power or a device n the scsi chain malfunctioning.

ioscan | more

You should be able to match the ioscan output to the lbolt output and then figure out what he problem area is, if not isolate the exact device.

Since you are a new user, I will point out that we reward good answers in ITRC with point assignment. I do appreciate your thanks for my help in other threads, but forum ettiqutte requests that you assign points, weighted for answers that helped you.

Please take the time to do so. I don't really need any, I already have myself a bunch.

Happy foruming.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Daniel Caçador
Regular Advisor

Re: Help to read Log.

Thanks SEP. You and the other friends they had helped me very! Thank's to all.
Daniel Caçador
Regular Advisor

Re: Help to read Log.

Thank'S to all!