Jul 30 15:01:23 server scsi: [ID 107833 kern.warning] WARNING: /pci@1e,6000

Hi,
I need help regarding below kernel warning message :
Jul 30 15:01:23 server scsi: [ID 107833 kern.warning] WARNING: /pci@1e,6000
I am new to solaris, and am unable to understand this.I want to know,
1) What this warning exactly means.
2) Is this warning important or can be negated.
3) what causes this warning to generate again and again.
Please let me know if you want any further information regarding this.
Thanks & Regards,
Girish

That error message is something to do with a storage device. But its cut off, /pci indicates a pci card, and 1e,6000 is a partial address to the card. You need to post the next few lines as well.
.7/M.

Similar Messages

Scsi: [ID 107833 kern.warning] WARNING: /pci@8,700000/scsi@1 (glm0):

ug 12 14:00:36 gtcerp1 scsi: [ID 107833 kern.warning] WARNING: /pci@8,700000/scsi@1 (glm0):
Aug 12 14:00:36 gtcerp1 Connected command timeout for Target 6.0
Aug 12 14:00:36 gtcerp1 genunix: [ID 408822 kern.info] NOTICE: glm0: fault detected in device; service still available
Aug 12 14:00:36 gtcerp1 genunix: [ID 611667 kern.info] NOTICE: glm0: Connected command timeout for Target 6.0
Aug 12 14:00:36 gtcerp1 glm: [ID 280919 kern.warning] WARNING: ID[SUNWpd.glm.cmd_timeout.6017]
Aug 12 14:00:36 gtcerp1 scsi: [ID 107833 kern.warning] WARNING: /pci@8,700000/scsi@1 (glm0):
Aug 12 14:00:36 gtcerp1 got SCSI bus reset
Aug 12 14:00:36 gtcerp1 genunix: [ID 408822 kern.info] NOTICE: glm0: fault detected in device; service still available
Aug 12 14:00:36 gtcerp1 genunix: [ID 611667 kern.info] NOTICE: glm0: got SCSI bus reset
Aug 12 14:02:47 gtcerp1 scsi: [ID 365881 kern.info] /pci@8,700000/scsi@1 (glm0):
we are geting this errror since from last two week, can anyone suggest us how to remove this error. we have tried by removing scsi card and rebooted, intially the error is removed but now its again come on console.

Hi.
Unfortunetly you not write what server you have.
*/pci@8,700000/scsi@1* look like Internal SCSI controller in Sun Fire V880.
For this server Target 6.0 is CD-ROM (DVD-ROM).
So it's look like problem with device.
For check you can use:
ls -la /dev/rdsk/*s2 | grep "/pci@8,700000/scsi@1"
iostat -EnCheck internal cable to CD-ROM. Replace or disconnect CDROM.
Regards.

WARNING: /pci@1f,0/pci@1/scsi@1/sd@0,0 (sd0)

Hello-
The following error has now appeared when I boot my Solaris 8 system. Does anyone have any suggestions on how I can recover from this.
Thanks!
WARNING: /pci@1f,0/pci@1/scsi@1/sd@0,0 (sd0):
Error for Command: read Error Level: Retryable
Requested Block: 195856 Error Block: 195865
Vendor: SEAGATE Serial Number: LMB31343
Sense Key: Media Error
ASC: 0x11 (unrecovered read error), ASCQ: 0x0, FRU: 0xe4
WARNING: /pci@1f,0/pci@1/scsi@1/sd@0,0 (sd0):
Error for Command: read Error Level: Retryable
Requested Block: 195856 Error Block: 195865
Vendor: SEAGATE Serial Number: LMB31343
Sense Key: Media Error
ASC: 0x11 (unrecovered read error), ASCQ: 0x0, FRU: 0xe4
WARNING: /pci@1f,0/pci@1/scsi@1/sd@0,0 (sd0):
Error for Command: read Error Level: Retryable
Requested Block: 195856 Error Block: 195865
Vendor: SEAGATE Serial Number: LMB31343
Sense Key: Media Error
ASC: 0x11 (unrecovered read error), ASCQ: 0x0, FRU: 0xe4
WARNING: /pci@1f,0/pci@1/scsi@1/sd@0,0 (sd0):
Error for Command: read Error Level: Retryable
Requested Block: 195856 Error Block: 195865
Vendor: SEAGATE Serial Number: LMB31343
Sense Key: Media Error
ASC: 0x11 (unrecovered read error), ASCQ: 0x0, FRU: 0xe4
WARNING: /pci@1f,0/pci@1/scsi@1/sd@0,0 (sd0):
Error for Command: read Error Level: Retryable
Requested Block: 195856 Error Block: 195865
Vendor: SEAGATE Serial Number: LMB31343
Sense Key: Media Error
ASC: 0x11 (unrecovered read error), ASCQ: 0x0, FRU: 0xe4
WARNING: /pci@1f,0/pci@1/scsi@1/sd@0,0 (sd0):
Error for Command: read Error Level: Fatal
Requested Block: 195856 Error Block: 195865
Vendor: SEAGATE Serial Number: LMB31343
Sense Key: Media Error
ASC: 0x11 (unrecovered read error), ASCQ: 0x0, FRU: 0xe4
WARNING: /pci@1f,0/pci@1/scsi@1/sd@0,0 (sd0):
Error for Command: read Error Level: Retryable
Requested Block: 195856 Error Block: 195865
Vendor: SEAGATE Serial Number: LMB31343
Sense Key: Media Error
ASC: 0x11 (unrecovered read error), ASCQ: 0x0, FRU: 0xe4
WARNING: /pci@1f,0/pci@1/scsi@1/sd@0,0 (sd0):
Error for Command: read Error Level: Retryable
Requested Block: 195856 Error Block: 195865
Vendor: SEAGATE Serial Number: LMB31343
Sense Key: Media Error
ASC: 0x11 (unrecovered read error), ASCQ: 0x0, FRU: 0xe4
WARNING: /pci@1f,0/pci@1/scsi@1/sd@0,0 (sd0):
Error for Command: read Error Level: Retryable
Requested Block: 195856 Error Block: 195865
Vendor: SEAGATE Serial Number: LMB31343
Sense Key: Media Error
ASC: 0x11 (unrecovered read error), ASCQ: 0x0, FRU: 0xe4
WARNING: /pci@1f,0/pci@1/scsi@1/sd@0,0 (sd0):
Error for Command: read Error Level: Retryable
Requested Block: 195856 Error Block: 195865
Vendor: SEAGATE Serial Number: LMB31343
Sense Key: Media Error
ASC: 0x11 (unrecovered read error), ASCQ: 0x0, FRU: 0xe4
WARNING: /pci@1f,0/pci@1/scsi@1/sd@0,0 (sd0):
Error for Command: read Error Level: Retryable
Requested Block: 195856 Error Block: 195865
Vendor: SEAGATE Serial Number: LMB31343
Sense Key: Media Error
ASC: 0x11 (unrecovered read error), ASCQ: 0x0, FRU: 0xe4
WARNING: /pci@1f,0/pci@1/scsi@1/sd@0,0 (sd0):
Error for Command: read Error Level: Fatal
Requested Block: 195856 Error Block: 195865
Vendor: SEAGATE Serial Number: LMB31343
Sense Key: Media Error
ASC: 0x11 (unrecovered read error), ASCQ: 0x0, FRU: 0xe4
INITSH: /sbin/rcS: cannot execute
INIT: Cannot create /var/adm/utmpx
INIT: failed write of utmpx entry:" "
INIT: failed write of utmpx entry:" "
INIT: SINGLE USER MODE

As you can guess your harddrive goes bad.
Boot from CD-ROM into single-user mode
boot cdrom -s
Start the format program, select the disk.
Try to analyze the surface (select a non-destructive test !!!)
Probably the bad spot can be relocated. If not replace the disk after doing a backup.
Use format to get the information on the disk-layout
Try to fsck the slices one by one
Backup the valuable data to tape

HP SERVER SCSI U320 PCI-E ADAPTER [412911-B21] windows 7 x64 driver?

Hi,
the card 412911-B21, can be installed on windows 7 x64?
I only found these drivers: http://goo.gl/woBrl
Thank you

Hello Mr. Wells,
Thank you for your question.
However, the Small Business Support Community is limited to Cisco Small Business Products, and the Aironet products are considered as a Enterprise level devices.
I recommend you to post this question on the on the correct forum, in order to get a better response.
You can move your post using the Actions panel on the right.
Best regards,
Diego Rodriguez
Cisco Small Business Community Engineer

OSB server is going in health warning state.

I am getting following log entries in my os b log file
####<Feb 4, 2014 9:29:53 PM EST> <Info> <Deployer> <plesbap01.us1.abc.com> <osb_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1391567393574> <BEA-149059> <Module ejb.jar of application _ALSB_1352206034075 is transitioning from STATE_PREPARED to STATE_ADMIN on server osb_server1.>
####<Feb 4, 2014 9:29:53 PM EST> <Info> <EJB> <plesbap01.us1.abc.com> <osb_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1391567393579> <BEA-010223> <EJB Deployed Message Driven Bean: RequestEJB-990041227111414011--6d1116fb.13ad527984a.-7fe9>
####<Feb 4, 2014 9:29:53 PM EST> <Info> <Deployer> <plesbap01.us1.abc.com> <osb_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1391567393579> <BEA-149060> <Module ejb.jar of application _ALSB_1352206034075 successfully transitioned from STATE_PREPARED to STATE_ADMIN on server osb_server1.>
####<Feb 4, 2014 9:29:53 PM EST> <Info> <Deployer> <plesbap01.us1.abc.com> <osb_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1391567393854> <BEA-149059> <Module ejb.jar of application _ALSB_1352206034484 is transitioning from STATE_PREPARED to STATE_ADMIN on server osb_server1.>
####<Feb 4, 2014 9:29:53 PM EST> <Info> <EJB> <plesbap01.us1.abc.com> <osb_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1391567393858> <BEA-010223> <EJB Deployed Message Driven Bean: RequestEJB-990041227111414011--6d1116fb.13ad527984a.-7fe8>
####<Feb 4, 2014 9:29:53 PM EST> <Info> <Deployer> <plesbap01.us1.abc.com> <osb_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1391567393858> <BEA-149060> <Module ejb.jar of application _ALSB_1352206034484 successfully transitioned from STATE_PREPARED to STATE_ADMIN on server osb_server1.>
####<Feb 4, 2014 9:29:54 PM EST> <Info> <Deployer> <plesbap01.us1.abc.com> <osb_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1391567394738> <BEA-149059> <Module ejb.jar of application _ALSB_1352206034835 is transitioning from STATE_PREPARED to STATE_ADMIN on server osb_server1.>
####<Feb 4, 2014 9:29:54 PM EST> <Info> <EJB> <plesbap01.us1.abc.com> <osb_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1391567394742> <BEA-010223> <EJB Deployed Message Driven Bean: RequestEJB-990041227111414011--6d1116fb.13ad527984a.-7fe7>
####<Feb 4, 2014 9:29:54 PM EST> <Info> <Deployer> <plesbap01.us1.abc.com> <osb_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1391567394743> <BEA-149060> <Module ejb.jar of application _ALSB_1352206034835 successfully transitioned from STATE_PREPARED to STATE_ADMIN on server osb_server1.>
####<Feb 4, 2014 9:29:55 PM EST> <Info> <Deployer> <plesbap01.us1.abc.com> <osb_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1391567395022> <BEA-149059> <Module ejb.jar of application _ALSB_1359865966296 is transitioning from STATE_PREPARED to STATE_ADMIN on server osb_server1.>
####<Feb 4, 2014 9:29:55 PM EST> <Info> <EJB> <plesbap01.us1.abc.com> <osb_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1391567395045> <BEA-010223> <EJB Deployed Message Driven Bean: RequestEJB-4841502376605855591--128e0c06.13c9db0f17e.-7fcf>
####<Feb 4, 2014 9:29:55 PM EST> <Info> <Deployer> <plesbap01.us1.abc.com> <osb_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1391567395045> <BEA-149060> <Module ejb.jar of application _ALSB_1359865966296 successfully transitioned from STATE_PREPARED to STATE_ADMIN on server osb_server1.>
####<Feb 4, 2014 9:29:55 PM EST> <Info> <Deployer> <plesbap01.us1.abc.com> <osb_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1391567395088> <BEA-149059> <Module ejb.jar of application _ALSB_1371011239470 is transitioning from STATE_PREPARED to STATE_ADMIN on server osb_server1.>
####<Feb 4, 2014 9:29:55 PM EST> <Info> <EJB> <plesbap01.us1.abc.com> <osb_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1391567395090> <BEA-010223> <EJB Deployed Message Driven Bean: RequestEJB-8090345450005809436-74582d1.13f09f8a361.-7fe1>
####<Feb 4, 2014 9:29:55 PM EST> <Info> <Deployer> <plesbap01.us1.abc.com> <osb_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1391567395090> <BEA-149060> <Module ejb.jar of application _ALSB_1371011239470 successfully transitioned from STATE_PREPARED to STATE_ADMIN on server osb_server1.>
####<Feb 4, 2014 9:29:55 PM EST> <Info> <Deployer> <plesbap01.us1.abc.com> <osb_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1391567395100> <BEA-149059> <Module ejb.jar of application _ALSB_1371024065613 is transitioning from STATE_PREPARED to STATE_ADMIN on server osb_server1.>
lastly its not giving message of successful transition and health of the server goes in warning state even restarting resolve it for some time. and again its move to warning state kindly help with the reason and reolution

Hi,
As Ros mentioned earlier you need see whether server logs have stuck thread or also check whether your Heap is trying to reach Max .
also might be your services have any problem.
So you need to check your OSB server logs.
Regards,
Kal

DHCP Server 2008 R2 Scope Full Warning

Is there a way to disable DHCP Scope Full Warning message from flooding my event logs? We use DHCP to lock down the ports at our office. Is there some registry setting I can do to prevent them from writing to the event logs so often?

Hi,
Thank you for your post.
Is there a way to disable DHCP Scope Full Warning message from flooding my event logs?
No special way to disable only DHCP event log. If you want to disable DHCP event log, you have to disable all system integrity events on your server.
To display the current audit policy for all subcategories, run command:
auditpol /get /category:*
To disable system integrity events on your server, run command:
auditpol /set /subcategory:"System Integrity" /success: disable /failure: disable
Since your DHCP scope pool reach full, you need to re-subnet your DHCP scope or extend your DHCP pool. Please refer to this
thread.
If there are more inquiries on this issue, please feel free to let us know.
Regards
Rick Tan
TechNet Community Support

Directory Server 6 and Password Grace Warning

Am trying to take advantage of DS 6 and password grace warning. Am having trouble finding the source template for the warning page that allows the user to change their password after its already expired. Can someone point me to how this page is built and how I can customize it?
Also is it possible to enhance the password change part of this functionality? I need to enforce a more complicated password adherence than the password policy allows.
Thanks!

I can answer the first part of my question. Login.jsp is the page that his callback goes through.

Server log shows error and warning 108 & 1085 every 5 minutes. Faile dto apply changes to software installation settings.

Event: 108
Failed to apply changes to software installation settings. Software changes could not be applied. A previous log entry with details should exist. The error was : %%2147746153
Event: 1085
Windows failed to apply the Software Installation settings. Software Installation settings might have its own log file. Please click on the "More information" link.
This errors have been happening a long while and do not appear to be having any effects on our end users. However, they are making
it very hard to sift through our log files as you could imagine! This DC is windows 2008 r2.
If there is any other information needed, let me know. Thanks!

In addition you can debug the software installation Policy easily.
GPO Troubleshooting
Also you can use the ADM/ADMX for GPO related issues (GPO DEBUG LOGGING).
http://www.gpoguy.com/FreeTools/FreeToolsLibrary/tabid/67/agentType/View/PropertyID/85/Default.aspx
http://www.gpoguy.com/FreeTools/FreeToolsLibrary/tabid/67/agentType/View/PropertyID/84/Default.aspx
Use this tool for registry key change.
http://www.gpoguy.com/FreeTools/FreeToolsLibrary/tabid/67/agentType/View/PropertyID/87/Default.aspx
I have tested all the above tools and all are working fine.
Best regards Biswajit Biswas Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. MCP 2003,MCSA 2003, MCSA:M 2003, CCNA, MCTS, Enterprise Admin

Dell R610 "SCSI transport failed: reason 'reset': retrying command"

MY DELL R610 Server run 3 ~ 5 hours ,will display the message and the server is die.
Jul 1 00:48:50 JSxwmGS scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci8086,2940@1c/pci1028,1f10@0 (mpt0):
Jul 1 00:48:50 JSxwmGS Disconnected command timeout for Target 0
Jul 1 00:48:51 JSxwmGS scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci8086,2940@1c/pci1028,1f10@0/sd@0,0 (sd1):
Jul 1 00:48:51 JSxwmGS SCSI transport failed: reason 'reset': retrying command
Jul 1 00:50:01 JSxwmGS scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci8086,2940@1c/pci1028,1f10@0 (mpt0):
Jul 1 00:50:01 JSxwmGS Disconnected command timeout for Target 0
Jul 1 00:52:02 JSxwmGS scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci8086,2940@1c/pci1028,1f10@0 (mpt0):
Jul 1 00:52:02 JSxwmGS Disconnected command timeout for Target 0

Use the same server install Centos5.4 , run the same java program on that , It is running ok.
use solaris 10 zfs file system ,it also have the question.

Scsi messages in /var/adm/messages file

Hi,
After open the /var/adm/messages i have the SCSI error messages:
Jul 8 15:45:13 kapttdw2 Corrupt label; wrong magic number
Jul 8 15:45:13 kapttdw2 scsi: [ID 107833 kern.warning] WARNING: /ssm@0,0/pci@1a,600000/SUNW,qlc@1/fp@0,0/ssd@w5006048452a65588,2 (ssd129):
Jul 8 15:45:13 kapttdw2 Corrupt label; wrong magic number
Jul 8 15:45:13 kapttdw2 scsi: [ID 107833 kern.warning] WARNING: /ssm@0,0/pci@1a,600000/SUNW,qlc@1/fp@0,0/ssd@w5006048452a65588,2 (ssd129):
Jul 8 15:45:13 kapttdw2 Corrupt label; wrong magic number
Jul 8 15:45:13 kapttdw2 scsi: [ID 107833 kern.warning] WARNING: /ssm@0,0/pci@1a,600000/SUNW,qlc@1/fp@0,0/ssd@w5006048452a65588,2 (ssd129):
Jul 8 15:45:13 kapttdw2 Corrupt label; wrong magic number
Jul 8 15:45:13 kapttdw2 scsi: [ID 107833 kern.warning] WARNING: /ssm@0,0/pci@1a,600000/SUNW,qlc@1/fp@0,0/ssd@w5006048452a65588,2 (ssd129):
Jul 8 15:45:13 kapttdw2 Corrupt label; wrong magic number
Jul 8 15:45:13 kapttdw2 scsi: [ID 107833 kern.warning] WARNING: /ssm@0,0/pci@1a,600000/SUNW,qlc@1/fp@0,0/ssd@w5006048452a65588,2 (ssd129):
Jul 8 15:45:13 kapttdw2 Corrupt label; wrong magic number
Jul 8 15:45:13 kapttdw2 scsi: [ID 107833 kern.warning] WARNING: /ssm@0,0/pci@1a,600000/SUNW,qlc@1/fp@0,0/ssd@w5006048452a65588,2 (ssd129):
Jul 8 15:45:13 kapttdw2 Corrupt label; wrong magic number
bash-2.05$
Please help me to correct this error
Thank

This issue on hostname `kapttdw2` seems to be the same as you reported in your other thread for hostname `kapttdw1`.
[http://forums.sun.com/thread.jspa?threadID=5391935|http://forums.sun.com/thread.jspa?threadID=5391935]
Perhaps you just need to label these disks (as you were advised for those other disks).
Also, since these drives are in an EMC peripheral, you might consider opening a support case with that storage vendor and get advice from them.

ST2540 and VxDMP

Hi:
I've a customer with the following config:
V880 with 2 x F/C controller
ST2540 with 2 x controller
Solaris 10 U4
EIS DVD April 09
Storage Foundation 5.0 patched with EIS DVD April 09
For one reason or another, mpxio was not used. I created a 2540 volume and presented to the server and use VxVM to create vxfs volumes without any problem. However, when I do a 'mkfile 100g a', and running iostat on another window, I can see that the io is running through the 2 paths c9 and c11, at the same time plenty of write errors appear in the messages file.
Jul 6 12:06:01 xxxxxx041 scsi: [ID 107833 kern.warning] WARNING: /pci@9,600000/
SUNW,qlc@1,1/fp@0,0/ssd@w202500a0b86731c0,0 (ssd18):
Jul 6 12:06:01 xxxxxx041 Error for Command: write(10) Error
Level: Retryable
Jul 6 12:06:01 xxxxxx041 scsi: [ID 107833 kern.notice] Requested Block:
64199456 Error Block: 0
Jul 6 12:06:01 xxxxxx041 scsi: [ID 107833 kern.notice] Vendor: SUN
Serial Number:
Jul 6 12:06:01 xxxxxx041 scsi: [ID 107833 kern.notice] Sense Key: Abort
ed Command
Jul 6 12:06:01 xxxxxx041 scsi: [ID 107833 kern.notice] ASC: 0x0 (no add
itional sense info), ASCQ: 0x0, FRU: 0x0
Jul 6 12:06:01 xxxxxx041 scsi: [ID 107833 kern.warning] WARNING: /pci@9,600000/
SUNW,qlc@1,1/fp@0,0/ssd@w202500a0b86731c0,0 (ssd18):
Jul 6 12:06:01 xxxxxx041 Error for Command: write(10) Error
Level: Retryable
Jul 6 12:06:01 xxxxxx041 scsi: [ID 107833 kern.notice] Requested Block:
64201504 Error Block: 0
Jul 6 12:06:01 xxxxxx041 scsi: [ID 107833 kern.notice] Vendor: SUN
Serial Number:
Jul 6 12:06:01 xxxxxx041 scsi: [ID 107833 kern.notice] Sense Key: Abort
ed Command
Jul 6 12:06:01 xxxxxx041 scsi: [ID 107833 kern.notice] ASC: 0x0 (no add
itional sense info), ASCQ: 0x0, FRU: 0x0
Jul 6 12:06:01 xxxxxx041 scsi: [ID 107833 kern.warning] WARNING: /pci@9,600000/
SUNW,qlc@1,1/fp@0,0/ssd@w202500a0b86731c0,0 (ssd18):
Jul 6 12:06:01 xxxxxx041 Error for Command: write(10) Error
Level: Retryable
Jul 6 12:06:01 xxxxxx041 scsi: [ID 107833 kern.notice] Requested Block:
64189216 Error Block: 0
Jul 6 12:06:01 xxxxxx041 scsi: [ID 107833 kern.notice] Vendor: SUN
Serial Number:
Jul 6 12:06:01 xxxxxx041 scsi: [ID 107833 kern.notice] Sense Key: Abort
ed Command
Jul 6 12:06:01 xxxxxx041 scsi: [ID 107833 kern.notice] ASC: 0x0 (no add
itional sense info), ASCQ: 0x0, FRU: 0x0
I face this problem before and turn on mpxio to 'solve' the problem. I've set in the CAM software the host type as "Solaris with Veritas DMP". I can't find any ASL for 2540 either. I've tried with vxfs and ufs, both giving the same results. To get rid of the gazillion retryable write error I have to set one of the path to standby! But occasionally the write errors will appear on console when the system boots up. Is there a fix for this or must I use mpxio? Thanks a lot in advance.
regards,
BSF

Hi:
I've a customer with the following config:
V880 with 2 x F/C controller
ST2540 with 2 x controller
Solaris 10 U4
EIS DVD April 09
Storage Foundation 5.0 patched with EIS DVD April 09
For one reason or another, mpxio was not used. I created a 2540 volume and presented to the server and use VxVM to create vxfs volumes without any problem. However, when I do a 'mkfile 100g a', and running iostat on another window, I can see that the io is running through the 2 paths c9 and c11, at the same time plenty of write errors appear in the messages file.
Jul 6 12:06:01 xxxxxx041 scsi: [ID 107833 kern.warning] WARNING: /pci@9,600000/
SUNW,qlc@1,1/fp@0,0/ssd@w202500a0b86731c0,0 (ssd18):
Jul 6 12:06:01 xxxxxx041 Error for Command: write(10) Error
Level: Retryable
Jul 6 12:06:01 xxxxxx041 scsi: [ID 107833 kern.notice] Requested Block:
64199456 Error Block: 0
Jul 6 12:06:01 xxxxxx041 scsi: [ID 107833 kern.notice] Vendor: SUN
Serial Number:
Jul 6 12:06:01 xxxxxx041 scsi: [ID 107833 kern.notice] Sense Key: Abort
ed Command
Jul 6 12:06:01 xxxxxx041 scsi: [ID 107833 kern.notice] ASC: 0x0 (no add
itional sense info), ASCQ: 0x0, FRU: 0x0
Jul 6 12:06:01 xxxxxx041 scsi: [ID 107833 kern.warning] WARNING: /pci@9,600000/
SUNW,qlc@1,1/fp@0,0/ssd@w202500a0b86731c0,0 (ssd18):
Jul 6 12:06:01 xxxxxx041 Error for Command: write(10) Error
Level: Retryable
Jul 6 12:06:01 xxxxxx041 scsi: [ID 107833 kern.notice] Requested Block:
64201504 Error Block: 0
Jul 6 12:06:01 xxxxxx041 scsi: [ID 107833 kern.notice] Vendor: SUN
Serial Number:
Jul 6 12:06:01 xxxxxx041 scsi: [ID 107833 kern.notice] Sense Key: Abort
ed Command
Jul 6 12:06:01 xxxxxx041 scsi: [ID 107833 kern.notice] ASC: 0x0 (no add
itional sense info), ASCQ: 0x0, FRU: 0x0
Jul 6 12:06:01 xxxxxx041 scsi: [ID 107833 kern.warning] WARNING: /pci@9,600000/
SUNW,qlc@1,1/fp@0,0/ssd@w202500a0b86731c0,0 (ssd18):
Jul 6 12:06:01 xxxxxx041 Error for Command: write(10) Error
Level: Retryable
Jul 6 12:06:01 xxxxxx041 scsi: [ID 107833 kern.notice] Requested Block:
64189216 Error Block: 0
Jul 6 12:06:01 xxxxxx041 scsi: [ID 107833 kern.notice] Vendor: SUN
Serial Number:
Jul 6 12:06:01 xxxxxx041 scsi: [ID 107833 kern.notice] Sense Key: Abort
ed Command
Jul 6 12:06:01 xxxxxx041 scsi: [ID 107833 kern.notice] ASC: 0x0 (no add
itional sense info), ASCQ: 0x0, FRU: 0x0
I face this problem before and turn on mpxio to 'solve' the problem. I've set in the CAM software the host type as "Solaris with Veritas DMP". I can't find any ASL for 2540 either. I've tried with vxfs and ufs, both giving the same results. To get rid of the gazillion retryable write error I have to set one of the path to standby! But occasionally the write errors will appear on console when the system boots up. Is there a fix for this or must I use mpxio? Thanks a lot in advance.
regards,
BSF

Solstice backup 6.1 hang when invoking the autochanger "SUN Storedge L8 "

My company have a SUN Storedge L8 attached to a SUN Solaris 9 (SPARC) while I can only do a tar to the /dev/rmt/0, whenever I tried to interact with the jukebox with the solstice backup, the program hang definitely.
grep '/usr/kernel/drv/lus' /var/sadm/install/contents
/usr/kernel/drv/lus f none 0555 root bin 34624 12073 993189557 SUNWsbus2
/usr/kernel/drv/lus.conf f none 0444 root bin 3754 45438 993190441 SUNWsbus2
/usr/kernel/drv/lus32 f none 0555 root bin 33444 4422 993213667 SUNWsbus2
pkginfo -l SUNWsbus2
PKGINST: SUNWsbus2
NAME: Solstice Backup (Backup/Recover) Device Drivers
CATEGORY: system
ARCH: sparc
VERSION: 6.1,REV=Build.186
BASEDIR: /
VENDOR: Sun Microsystems, Inc.
PSTAMP: gelato010622054128
INSTDATE: Apr 08 2003 13:25
STATUS: completely installed
FILES: 48 installed pathnames
44 executables
37896 blocks used (approx)
this machine has installed the solstice backup manager
pkginfo | grep -i Solstice
system SUNWmibii Solstice Enterprise Agents 1.0.3 SNMP daemon
system SUNWsacom Solstice Enterprise Agents 1.0.3 files for root file system
system SUNWsadmi Solstice Enterprise Agents 1.0.3 Desktop Management Interface
system SUNWsadml Solstice Launcher.
system SUNWsadmx Solstice Enterprise Agents 1.0.3 Desktop Management Interface Libraries (64-bit)
system SUNWsasnm Solstice Enterprise Agents 1.0.3 Simple Network Management Protocol
system SUNWsasnx Solstice Enterprise Agents 1.0.3 Simple Network Management Protocol Libraries (64-bit)
application SUNWsbuc Solstice Backup (Backup/Recover) Client
application SUNWsbum Solstice Backup (Backup/Recover) Man
application SUNWsbun Solstice Backup (Backup/Recover) Storage Node
application SUNWsbus1 Solstice Backup (Backup/Recover) Server
system SUNWsbus2 Solstice Backup (Backup/Recover) Device Drivers
under the server->registration, I found that the registration contains :-
Autochanger Module, 9 slots/9
ClientPaks for Windows/1
Networker for UNIX, Workgroup edition (8 clients per server)1 server
Networker Module for Oracl/1
BTW, inquire shows:-
/etc/LGTOuscsi/inquire
[email protected]:TOSHIBA DVD-ROM SD-M14011009|CD-ROM
[email protected]:ADIC FastStor 2 A12r|Autochanger (Jukebox)
[email protected]:HP Ultrium 1-SCSI E3 |Tape
[email protected]:HP Ultrium 1-SCSI E3 |Tape
where cfgadm -alv shows:-
Ap_Id Receptacle Occupant Condition Information
When Type Busy Phys_Id
c0 connected configured unknown
unavailable scsi-bus n /devices/pci@8,700000/scsi@6:scsi
c0::/dev/lus connected configured unknown TOSHIBA DVD-ROM SD-M1401
unavailable CD-ROM n /devices/pci@8,700000/scsi@6:scsi::/dev/lus
c0::dsk/c0t6d0 connected configured unknown TOSHIBA DVD-ROM SD-M1401
unavailable CD-ROM y /devices/pci@8,700000/scsi@6:scsi::dsk/c0t6d0
c1 connected configured unknown
unavailable fc-private n /devices/pci@8,600000/SUNW,qlc@4/fp@0,0:fc
c1::21000004cfe34092 connected configured unknown SEAGATE ST373307FSUN72G
unavailable disk n /devices/pci@8,600000/SUNW,qlc@4/fp@0,0:fc::21000004cfe34092
c1::21000004cfe34350 connected configured unknown SEAGATE ST373307FSUN72G
unavailable disk n /devices/pci@8,600000/SUNW,qlc@4/fp@0,0:fc::21000004cfe34350
c2 connected configured unknown
unavailable scsi-bus n /devices/pci@8,700000/scsi@6,1:scsi
c2::lus1 connected configured unknown
unavailable unknown n /devices/pci@8,700000/scsi@6,1:scsi::lus1
c3 connected configured unknown
unavailable scsi-bus n /devices/pci@8,600000/pci@1/scsi@4:scsi
c3::lus2 connected configured unknown HP Ultrium 1-SCSI
unavailable unknown n /devices/pci@8,600000/pci@1/scsi@4:scsi::lus2
c3::rmt/0 connected configured unknown HP Ultrium 1-SCSI
unavailable tape n /devices/pci@8,600000/pci@1/scsi@4:scsi::rmt/0
c4 connected configured unknown
unavailable scsi-bus n /devices/pci@8,600000/pci@1/scsi@5:scsi
c4::lus3 connected configured unknown
unavailable unknown n /devices/pci@8,600000/pci@1/scsi@5:scsi::lus3
usb0/1 connected configured ok Mfg: <undef> Product: <undef> NConfigs: 1 Config: 0 <no cfg str descr>
unavailable usb-kbd n /devices/pci@8,700000/usb@5,3:1
usb0/2 empty unconfigured ok
unavailable unknown n /devices/pci@8,700000/usb@5,3:2
usb0/3 connected configured ok Mfg: <undef> Product: <undef> NConfigs: 1 Config: 0 <no cfg str descr>
unavailable usb-mouse n /devices/pci@8,700000/usb@5,3:3
usb0/4 empty unconfigured ok
unavailable unknown n /devices/pci@8,700000/usb@5,3:4
nsrjb shows
Jukebox L8:
slot volume pool volume id recyclable
1: dwbak.inc.day0.wk0.001* 2481680129
2: dwbak.inc.day0.wk0.002 DW Incremental 2481704705 no
3: dwbak.inc.day0.wk0.003 DW Incremental 2481729793 no
4: -* -
5: dwbak.inc.day0.wk0.005 DW Incremental 2481779201 no
6: dwbak.inc.day0.wk0.006 DW Incremental 2481804289 no
7: dwbak.inc.day0.wk0.007 DW Incremental 2481829889 no
8: dwbak.inc.day0.wk0.008 DW Incremental 2481854209 no
*not registered in the NetWorker media data base
drive 1 (/dev/rmt/0cbn) slot 5: dwbak.inc.day0.wk0.005
nsrjb -HE hang indefinitly, so does nsrjb -HHE. devfsadm -c tape also hang while simply devfsadm can run without problem and cfgadm -alv c3 provide the following:-
Ap_Id Receptacle Occupant Condition Information
When Type Busy Phys_Id
c3 connected configured unknown
unavailable scsi-bus n /devices/pci@8,600000/pci@1/scsi@4:scsi
c3::lus2 connected configured unknown HP Ultrium 1-SCSI
unavailable unknown n /devices/pci@8,600000/pci@1/scsi@4:scsi::lus2
c3::rmt/0 connected configured unknown HP Ultrium 1-SCSI
unavailable tape n /devices/pci@8,600000/pci@1/scsi@4:scsi::rmt/0
nsjrb result should be past history, coz I am doing tar and manually changing the slot for quite some time already. Now I unconnect the cable and run devfsadm and then cfgadm -alv shows
cfgadm -alv
Ap_Id Receptacle Occupant Condition Information
When Type Busy Phys_Id
c0 connected configured unknown
unavailable scsi-bus n /devices/pci@8,700000/scsi@6:scsi
c0::/dev/lus connected configured unknown TOSHIBA DVD-ROM SD-M1401
unavailable CD-ROM n /devices/pci@8,700000/scsi@6:scsi::/dev/lus
c0::dsk/c0t6d0 connected configured unknown TOSHIBA DVD-ROM SD-M1401
unavailable CD-ROM y /devices/pci@8,700000/scsi@6:scsi::dsk/c0t6d0
c1 connected configured unknown
unavailable fc-private n /devices/pci@8,600000/SUNW,qlc@4/fp@0,0:fc
c1::21000004cfe34092 connected configured unknown SEAGATE ST373307FSUN72G
unavailable disk n /devices/pci@8,600000/SUNW,qlc@4/fp@0,0:fc::21000004cfe34092
c1::21000004cfe34350 connected configured unknown SEAGATE ST373307FSUN72G
unavailable disk n /devices/pci@8,600000/SUNW,qlc@4/fp@0,0:fc::21000004cfe34350
c2 connected configured unknown
unavailable scsi-bus n /devices/pci@8,700000/scsi@6,1:scsi
c2::lus1 connected configured unknown
unavailable unknown n /devices/pci@8,700000/scsi@6,1:scsi::lus1
c3 connected configured unknown
unavailable scsi-bus n /devices/pci@8,600000/pci@1/scsi@4:scsi
c3::lus2 connected configured unknown HP Ultrium 1-SCSI
unavailable unknown n /devices/pci@8,600000/pci@1/scsi@4:scsi::lus2
c3::rmt/0 connected configured unknown HP Ultrium 1-SCSI
unavailable tape n /devices/pci@8,600000/pci@1/scsi@4:scsi::rmt/0
c4 connected configured unknown
unavailable scsi-bus n /devices/pci@8,600000/pci@1/scsi@5:scsi
c4::lus3 connected configured unknown
unavailable unknown n /devices/pci@8,600000/pci@1/scsi@5:scsi::lus3
usb0/1 connected configured ok Mfg: <undef> Product: <undef> NConfigs: 1 Config: 0 <no cfg str descr>
unavailable usb-kbd n /devices/pci@8,700000/usb@5,3:1
usb0/2 empty unconfigured ok
unavailable unknown n /devices/pci@8,700000/usb@5,3:2
usb0/3 connected configured ok Mfg: <undef> Product: <undef> NConfigs: 1 Config: 0 <no cfg str descr>
unavailable usb-mouse n /devices/pci@8,700000/usb@5,3:3
usb0/4 empty unconfigured ok
unavailable unknown n /devices/pci@8,700000/usb@5,3:4
and inquire still shows
[email protected]:TOSHIBA DVD-ROM SD-M14011009|CD-ROM
[email protected]:ADIC FastStor 2 A12r|Autochanger (Jukebox)
[email protected]:HP Ultrium 1-SCSI E3 |Tape
[email protected]:HP Ultrium 1-SCSI E3 |Tape
and then I reconnect the cable I saw a lot of error message in dmesg:-
Jun 19 13:47:37 server scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/pci@1/scsi@4 (qus0):
Jun 19 13:47:37 server Received unexpected SCSI Reset
Jun 19 13:47:37 server scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/pci@1/scsi@4 (qus0):
Jun 19 13:47:37 server Received unexpected SCSI Reset
Jun 19 13:51:30 server scsi: [ID 107833 kern.notice] /pci@8,600000/pci@1/scsi@4 (qus0):
Jun 19 13:51:30 server Failed to Get Features
Jun 19 13:51:50 server scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/pci@1/scsi@4 (qus0):
Jun 19 13:51:50 server ISP: Firmware cmd timeout
Jun 19 13:51:50 server scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/pci@1/scsi@4 (qus0):
Jun 19 13:51:50 server Fatal error, resetting interface, flg 1
and devfsadm hang. So I double check the past demsg and found a lot of similar SCSI error message as below:-
Jun 19 13:43:12 server probe request for LUN 0 denied: max LUN -1
Jun 19 13:43:12 server scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/pci@1/scsi@5 (qus1):
Is that represent a hardware failure either on the jukebox or the SCSI controller? Or it is indeed a software corruption that can only be solved by reinstallation? But unfortunately I don't have the media on hand.
PS.a more details can be found under expert exchange thru the links below:-
http://www.experts-exchange.com/OS/Unix/Solaris/Q_23413012.html#a21749881
http://www.experts-exchange.com/OS/Unix/Solaris/Q_23478147.html

My company have a SUN Storedge L8 attached to a SUN Solaris 9 (SPARC) while I can only do a tar to the /dev/rmt/0, whenever I tried to interact with the jukebox with the solstice backup, the program hang definitely.
grep '/usr/kernel/drv/lus' /var/sadm/install/contents
/usr/kernel/drv/lus f none 0555 root bin 34624 12073 993189557 SUNWsbus2
/usr/kernel/drv/lus.conf f none 0444 root bin 3754 45438 993190441 SUNWsbus2
/usr/kernel/drv/lus32 f none 0555 root bin 33444 4422 993213667 SUNWsbus2
pkginfo -l SUNWsbus2
PKGINST: SUNWsbus2
NAME: Solstice Backup (Backup/Recover) Device Drivers
CATEGORY: system
ARCH: sparc
VERSION: 6.1,REV=Build.186
BASEDIR: /
VENDOR: Sun Microsystems, Inc.
PSTAMP: gelato010622054128
INSTDATE: Apr 08 2003 13:25
STATUS: completely installed
FILES: 48 installed pathnames
44 executables
37896 blocks used (approx)
this machine has installed the solstice backup manager
pkginfo | grep -i Solstice
system SUNWmibii Solstice Enterprise Agents 1.0.3 SNMP daemon
system SUNWsacom Solstice Enterprise Agents 1.0.3 files for root file system
system SUNWsadmi Solstice Enterprise Agents 1.0.3 Desktop Management Interface
system SUNWsadml Solstice Launcher.
system SUNWsadmx Solstice Enterprise Agents 1.0.3 Desktop Management Interface Libraries (64-bit)
system SUNWsasnm Solstice Enterprise Agents 1.0.3 Simple Network Management Protocol
system SUNWsasnx Solstice Enterprise Agents 1.0.3 Simple Network Management Protocol Libraries (64-bit)
application SUNWsbuc Solstice Backup (Backup/Recover) Client
application SUNWsbum Solstice Backup (Backup/Recover) Man
application SUNWsbun Solstice Backup (Backup/Recover) Storage Node
application SUNWsbus1 Solstice Backup (Backup/Recover) Server
system SUNWsbus2 Solstice Backup (Backup/Recover) Device Drivers
under the server->registration, I found that the registration contains :-
Autochanger Module, 9 slots/9
ClientPaks for Windows/1
Networker for UNIX, Workgroup edition (8 clients per server)1 server
Networker Module for Oracl/1
BTW, inquire shows:-
/etc/LGTOuscsi/inquire
[email protected]:TOSHIBA DVD-ROM SD-M14011009|CD-ROM
[email protected]:ADIC FastStor 2 A12r|Autochanger (Jukebox)
[email protected]:HP Ultrium 1-SCSI E3 |Tape
[email protected]:HP Ultrium 1-SCSI E3 |Tape
where cfgadm -alv shows:-
Ap_Id Receptacle Occupant Condition Information
When Type Busy Phys_Id
c0 connected configured unknown
unavailable scsi-bus n /devices/pci@8,700000/scsi@6:scsi
c0::/dev/lus connected configured unknown TOSHIBA DVD-ROM SD-M1401
unavailable CD-ROM n /devices/pci@8,700000/scsi@6:scsi::/dev/lus
c0::dsk/c0t6d0 connected configured unknown TOSHIBA DVD-ROM SD-M1401
unavailable CD-ROM y /devices/pci@8,700000/scsi@6:scsi::dsk/c0t6d0
c1 connected configured unknown
unavailable fc-private n /devices/pci@8,600000/SUNW,qlc@4/fp@0,0:fc
c1::21000004cfe34092 connected configured unknown SEAGATE ST373307FSUN72G
unavailable disk n /devices/pci@8,600000/SUNW,qlc@4/fp@0,0:fc::21000004cfe34092
c1::21000004cfe34350 connected configured unknown SEAGATE ST373307FSUN72G
unavailable disk n /devices/pci@8,600000/SUNW,qlc@4/fp@0,0:fc::21000004cfe34350
c2 connected configured unknown
unavailable scsi-bus n /devices/pci@8,700000/scsi@6,1:scsi
c2::lus1 connected configured unknown
unavailable unknown n /devices/pci@8,700000/scsi@6,1:scsi::lus1
c3 connected configured unknown
unavailable scsi-bus n /devices/pci@8,600000/pci@1/scsi@4:scsi
c3::lus2 connected configured unknown HP Ultrium 1-SCSI
unavailable unknown n /devices/pci@8,600000/pci@1/scsi@4:scsi::lus2
c3::rmt/0 connected configured unknown HP Ultrium 1-SCSI
unavailable tape n /devices/pci@8,600000/pci@1/scsi@4:scsi::rmt/0
c4 connected configured unknown
unavailable scsi-bus n /devices/pci@8,600000/pci@1/scsi@5:scsi
c4::lus3 connected configured unknown
unavailable unknown n /devices/pci@8,600000/pci@1/scsi@5:scsi::lus3
usb0/1 connected configured ok Mfg: <undef> Product: <undef> NConfigs: 1 Config: 0 <no cfg str descr>
unavailable usb-kbd n /devices/pci@8,700000/usb@5,3:1
usb0/2 empty unconfigured ok
unavailable unknown n /devices/pci@8,700000/usb@5,3:2
usb0/3 connected configured ok Mfg: <undef> Product: <undef> NConfigs: 1 Config: 0 <no cfg str descr>
unavailable usb-mouse n /devices/pci@8,700000/usb@5,3:3
usb0/4 empty unconfigured ok
unavailable unknown n /devices/pci@8,700000/usb@5,3:4
nsrjb shows
Jukebox L8:
slot volume pool volume id recyclable
1: dwbak.inc.day0.wk0.001* 2481680129
2: dwbak.inc.day0.wk0.002 DW Incremental 2481704705 no
3: dwbak.inc.day0.wk0.003 DW Incremental 2481729793 no
4: -* -
5: dwbak.inc.day0.wk0.005 DW Incremental 2481779201 no
6: dwbak.inc.day0.wk0.006 DW Incremental 2481804289 no
7: dwbak.inc.day0.wk0.007 DW Incremental 2481829889 no
8: dwbak.inc.day0.wk0.008 DW Incremental 2481854209 no
*not registered in the NetWorker media data base
drive 1 (/dev/rmt/0cbn) slot 5: dwbak.inc.day0.wk0.005
nsrjb -HE hang indefinitly, so does nsrjb -HHE. devfsadm -c tape also hang while simply devfsadm can run without problem and cfgadm -alv c3 provide the following:-
Ap_Id Receptacle Occupant Condition Information
When Type Busy Phys_Id
c3 connected configured unknown
unavailable scsi-bus n /devices/pci@8,600000/pci@1/scsi@4:scsi
c3::lus2 connected configured unknown HP Ultrium 1-SCSI
unavailable unknown n /devices/pci@8,600000/pci@1/scsi@4:scsi::lus2
c3::rmt/0 connected configured unknown HP Ultrium 1-SCSI
unavailable tape n /devices/pci@8,600000/pci@1/scsi@4:scsi::rmt/0
nsjrb result should be past history, coz I am doing tar and manually changing the slot for quite some time already. Now I unconnect the cable and run devfsadm and then cfgadm -alv shows
cfgadm -alv
Ap_Id Receptacle Occupant Condition Information
When Type Busy Phys_Id
c0 connected configured unknown
unavailable scsi-bus n /devices/pci@8,700000/scsi@6:scsi
c0::/dev/lus connected configured unknown TOSHIBA DVD-ROM SD-M1401
unavailable CD-ROM n /devices/pci@8,700000/scsi@6:scsi::/dev/lus
c0::dsk/c0t6d0 connected configured unknown TOSHIBA DVD-ROM SD-M1401
unavailable CD-ROM y /devices/pci@8,700000/scsi@6:scsi::dsk/c0t6d0
c1 connected configured unknown
unavailable fc-private n /devices/pci@8,600000/SUNW,qlc@4/fp@0,0:fc
c1::21000004cfe34092 connected configured unknown SEAGATE ST373307FSUN72G
unavailable disk n /devices/pci@8,600000/SUNW,qlc@4/fp@0,0:fc::21000004cfe34092
c1::21000004cfe34350 connected configured unknown SEAGATE ST373307FSUN72G
unavailable disk n /devices/pci@8,600000/SUNW,qlc@4/fp@0,0:fc::21000004cfe34350
c2 connected configured unknown
unavailable scsi-bus n /devices/pci@8,700000/scsi@6,1:scsi
c2::lus1 connected configured unknown
unavailable unknown n /devices/pci@8,700000/scsi@6,1:scsi::lus1
c3 connected configured unknown
unavailable scsi-bus n /devices/pci@8,600000/pci@1/scsi@4:scsi
c3::lus2 connected configured unknown HP Ultrium 1-SCSI
unavailable unknown n /devices/pci@8,600000/pci@1/scsi@4:scsi::lus2
c3::rmt/0 connected configured unknown HP Ultrium 1-SCSI
unavailable tape n /devices/pci@8,600000/pci@1/scsi@4:scsi::rmt/0
c4 connected configured unknown
unavailable scsi-bus n /devices/pci@8,600000/pci@1/scsi@5:scsi
c4::lus3 connected configured unknown
unavailable unknown n /devices/pci@8,600000/pci@1/scsi@5:scsi::lus3
usb0/1 connected configured ok Mfg: <undef> Product: <undef> NConfigs: 1 Config: 0 <no cfg str descr>
unavailable usb-kbd n /devices/pci@8,700000/usb@5,3:1
usb0/2 empty unconfigured ok
unavailable unknown n /devices/pci@8,700000/usb@5,3:2
usb0/3 connected configured ok Mfg: <undef> Product: <undef> NConfigs: 1 Config: 0 <no cfg str descr>
unavailable usb-mouse n /devices/pci@8,700000/usb@5,3:3
usb0/4 empty unconfigured ok
unavailable unknown n /devices/pci@8,700000/usb@5,3:4
and inquire still shows
[email protected]:TOSHIBA DVD-ROM SD-M14011009|CD-ROM
[email protected]:ADIC FastStor 2 A12r|Autochanger (Jukebox)
[email protected]:HP Ultrium 1-SCSI E3 |Tape
[email protected]:HP Ultrium 1-SCSI E3 |Tape
and then I reconnect the cable I saw a lot of error message in dmesg:-
Jun 19 13:47:37 server scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/pci@1/scsi@4 (qus0):
Jun 19 13:47:37 server Received unexpected SCSI Reset
Jun 19 13:47:37 server scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/pci@1/scsi@4 (qus0):
Jun 19 13:47:37 server Received unexpected SCSI Reset
Jun 19 13:51:30 server scsi: [ID 107833 kern.notice] /pci@8,600000/pci@1/scsi@4 (qus0):
Jun 19 13:51:30 server Failed to Get Features
Jun 19 13:51:50 server scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/pci@1/scsi@4 (qus0):
Jun 19 13:51:50 server ISP: Firmware cmd timeout
Jun 19 13:51:50 server scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/pci@1/scsi@4 (qus0):
Jun 19 13:51:50 server Fatal error, resetting interface, flg 1
and devfsadm hang. So I double check the past demsg and found a lot of similar SCSI error message as below:-
Jun 19 13:43:12 server probe request for LUN 0 denied: max LUN -1
Jun 19 13:43:12 server scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/pci@1/scsi@5 (qus1):
Is that represent a hardware failure either on the jukebox or the SCSI controller? Or it is indeed a software corruption that can only be solved by reinstallation? But unfortunately I don't have the media on hand.
PS.a more details can be found under expert exchange thru the links below:-
http://www.experts-exchange.com/OS/Unix/Solaris/Q_23413012.html#a21749881
http://www.experts-exchange.com/OS/Unix/Solaris/Q_23478147.html

Sun V880 Fibre channel drive giving Loop OFFLINE message

Hi
I have a v880 with two drives and drive at slot 0 is giving below message every few minutes and drive operation (read and write) halts.
Jul 12 12:36:11 suntest1 qlc: [ID 686697 kern.info] NOTICE: Qlogic qlc(0): Loop ONLINE
Jul 12 12:36:28 suntest1 qlc: [ID 686697 kern.info] NOTICE: Qlogic qlc(0): Loop OFFLINE
Below is message i am seeing in /var/adm/messages.
# tail -f /var/adm/messages
Jul 12 12:34:59 suntest1 scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w2100000c50eb2098,0 (ssd1):
Jul 12 12:34:59 suntest1 SCSI transport failed: reason 'tran_err': giving up
Jul 12 12:36:00 suntest1 qlc: [ID 686697 kern.info] NOTICE: Qlogic qlc(0): Loop OFFLINE
Jul 12 12:36:01 suntest1 qlc: [ID 686697 kern.info] NOTICE: Qlogic qlc(0): Loop ONLINE
Jul 12 12:36:05 suntest1 qlc: [ID 686697 kern.info] NOTICE: Qlogic qlc(0): Loop OFFLINE
Jul 12 12:36:06 suntest1 scsi: [ID 243001 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@2/fp@0,0 (fcp0):
Jul 12 12:36:06 suntest1 PLOGI to D_ID=0xef failed: State:Operation Success, Reason:Undefined. Giving up
Jul 12 12:36:11 suntest1 qlc: [ID 686697 kern.info] NOTICE: Qlogic qlc(0): Loop ONLINE
Jul 12 12:36:28 suntest1 qlc: [ID 686697 kern.info] NOTICE: Qlogic qlc(0): Loop OFFLINE
Jul 12 12:36:34 suntest1 qlc: [ID 686697 kern.info] NOTICE: Qlogic qlc(0): Loop ONLINE
System is running solaris 9 and I have following qlogic driver installed.
# modinfo|grep qlc
26 1215a7d 26c61 153 1 qlc (Qlogic FCA Driver v0.40.5)
Any help will be appreciated.
Thanks
Anoop

What is the status of the HDD of this particular path ?
WARNING: /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w2100000c50eb2098,0 (ssd1):
You can verify with format or iostat -En
Regards
Ravi

X4100 M2 mirrored disk replacement?

We have an X4100 M2 that has it's 2 73GB disks mirrored using the LSI 1064 controller running fully patched S10u5 x86.
One of the disks has failed based on the following message in /var/adm/messages:
Jul 4 06:59:58 flare scsi: [ID 107833 kern.warning] WARNING: /pci@7b,0/pci1022,7458@11/pci1000,3060@2 (mpt0):
Jul 4 06:59:58 flare Volume 2 is degraded
And, I can confirm this with the following raidctl commands:
root@flare # raidctl -l c3t2d0
Volume Size Stripe Status Cache RAID
Sub Size Level
Disk
c3t2d0 67.9G N/A DEGRADED OFF RAID1
0.3.0 67.9G GOOD
0.4.0 67.9G FAILED
I had originally thought .... likely very naively ... that I could simply pop in a new disk in place of the failed one, and it would remirror. That appears to not be the case.
So my question is, can this be done from raidctl on a mounted and running system?
Alternatively, can this be done on bootup by hitting CTRL-C at the appropriate LSI prompt during boot and entering the LSI configuration utility. In particular, does anyone have a pointer to instructions that describe how to do that without losing the data on the still-functional disk? The only other time I've played with the LSI configuration utility was when I originally set up mirroring .... and that was before there was anything that I cared about on either disk so I didn't have to worry about losing anything. Now, however, if I accidentally wipe the remaining good disk, I've really made a mess of things.
Thanks for your inputs,
John

For what it's worth, here's the Sun manual for the LSI RAID Adapter on the x4100 M2's...
http://docs.sun.com/source/819-1157-21/AE_BIOS_RAID.html#0_pgfId-1003503
--Ryan

Warning in messages on nonexistence disk

Hi,
We received the following on our Sparc V890 in the /var/log/messages everytime we boot up the system:
Feb 21 07:04:57 [server] scsi: [ID 107833 kern.warning] WARNING: /pci@9,600000/pci@2/SUNW,qlc@5/fp@0,0/ssd@w21000011c6b8fd4a,0 (ssd31):
Feb 21 07:04:57 [server] Corrupt label; wrong magic number
I have traced the address and found we do not have a disk inserted in the listed address. The message will only appear once after boot up until the next bootup. I have tried probe-scsi-all & reboot -- -r without been able to remove the message.
Any ideas why the message is so persistent & how to stop it from appearing?
Thanks.
Edited by: user12187090 on Feb 20, 2011 11:46 PM

Well, you can in theory remove it with cfgadm (use cfgadm -al to list all devices).
However, if it reappears after a reconfigure boot, and complains on each boot, it seems like the drive is still there, if it wasn't you shouldn't see it at every boot.
Given the path; /pci@9,600000/pci@2/SUNW,*qlc*@5/*fp*@0,0/ssd@w21000011c6b8fd4a,0, it seems to be a SAN/FCP connected LUN, if thats any help.
You could also try the cleanup-flag to devfsadm:
devfsadm -C
. . but i don't think it helps, you should be able to list the device with luxadm though..
.7/M.

Jul 30 15:01:23 server scsi: [ID 107833 kern.warning] WARNING: /pci@1e,6000

Similar Messages

Maybe you are looking for