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.

Similar Messages

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.

15k after patches: Cannot assemble drivers for root /pci@1c,700000/scsi@1/d

All domains booted fine before patching through my local patch proxy on Thursday, June 15th. After running smpatch update, all domains went into the reboot loop with:
Cannot assemble drivers for root /pci@1c,700000/scsi@1/disk@0,0:b
Jun 15 20:42:57 2006 Cannot mount root on /pci@1c,700000/scsi@1/disk@0,0:b fstype ufs
I've reviewed other posts with similar error but there shouldn't be a driver completely missing, as it did boot fine many times before patching. From google search it looked as if /kernel/drv/sd.conf might have been effected by a patch, but that doesn't seem to be the case as a search through all /var/sadm/patch doesn't show any files with that string. Perhaps the scsi drivers were changed somehow?
If this is a patch, I would really like to narrow down which one it might be so I don't need to un-install all of them.
t

Thanks for the responses, I really do appreciate the help.
My goal was to install Solaris 8 onto 2 systems, a V880 and a V890.
Initially my problem was that I tried to install our existing Solaris 8 07/03 flash archive onto the V880 (and V890). But the V880 and V890 needed newer hardware links, I had to re-create our Solaris 8 flash archive with the 02/04 release of Solaris 8.
Now the V880 and V890 would boot from the network and the OS would install onto the local drives. But when the OS would boot from the local disk, I would received the error "Cannot assemble drivers for root /pci@8,600000/SUNW,qlc@2/fp@0,0/disk@w500000e01
1476eb1,0:a". The machine would panic and cycle - booting and panincing over and over again.
Since the net boot image recognized the disks but the flash archive installed image did not, I booted the V880 with "boot net -s" to view the loaded modules. I compared a V240 running Solaris 8 with the net booted V880 as I have no other V880s in the environment. I also compared the directories /kernel/drv/sparcv9/ to see which drivers were missing.
What I discovered is that since I create our flash archive on a scsi based system and I did not use the SUNWCXall package cluster in the profile, the drivers for the FC-AL drives do not get included on the system from which the flash archive is created. The V880 and V890 internal drives are FC-AL based. This was the root cause of my problem.
Thru the comparison described above, I learned that I needed to add the following packages to the install profile of the master system:
socal driver - SUNWluxl and SUNWluxlx
qlc driver - SUNWqlc and SUNWqlcx
usoc driver - SUNWusoc and SUNWusocx
Then I recreated the flash archive and re-jumped the V880 and V890. Both systems booted from their internal drives. And there was much rejoicing...

[ID 107833 kern.warning] ... /scsi_vhci/....

Hi there,
Have noticed these errors in dmesg log and seems like during this period of errors we had our systems have a very low transfer rate.
I have 3 sets of erros to dig into.
[1] I did some search and found a similar error and had a patch for the specific device ...(reference http://sunsolve.sun.com/search/document.do?assetkey=1-26-101771-1). Errors are attached below
[2] SAM-FS critical device error. Not sure on if this is critical, and how to go about finding the source of the problem.
[3] output of iostat -En ....showing 2 hard errors. is this the source of all problems above ???
Thanks for any help you can provide!!!
~a2@sunsolve
[1] =============================================
Nov 23 01:00:13 suseme scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600a0b80001732a600002f0b4290b53e (ssd21):
Nov 23 01:00:13 suseme Error for Command: write(10) Error Level: Retryable
Nov 23 01:00:13 suseme scsi: [ID 107833 kern.notice] Requested Block: 302073600 Error Block: 302073600
Nov 23 01:00:13 suseme scsi: [ID 107833 kern.notice] Vendor: SUN Serial Number:
Nov 23 01:00:13 suseme scsi: [ID 107833 kern.notice] Sense Key: Unit Attention
Nov 23 01:00:13 suseme scsi: [ID 107833 kern.notice] ASC: 0xc (write error), ASCQ: 0x0, FRU: 0x0
Nov 23 01:00:25 suseme scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600a0b80001732a600002f084290b04e (ssd51):
Nov 23 01:00:25 suseme Error for Command: write(10) Error Level: Retryable
Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] Requested Block: 418872392 Error Block: 418872392
Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] Vendor: SUN Serial Number:
Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] Sense Key: Unit Attention
Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] ASC: 0xc (write error), ASCQ: 0x0, FRU: 0x0
Nov 23 01:00:25 suseme scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600a0b8000178ac0000026714290b04b (ssd50):
Nov 23 01:00:25 suseme Error for Command: write(10) Error Level: Retryable
Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] Requested Block: 304059616 Error Block: 304059616
Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] Vendor: SUN Serial Number:
Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] Sense Key: Unit Attention
Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] ASC: 0xc (write error), ASCQ: 0x0, FRU: 0x0
Nov 23 01:00:33 suseme scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600a0b8000178ac00000267442913027 (ssd20):
Nov 23 01:00:33 suseme Error for Command: write(10) Error Level: Retryable
Nov 23 01:00:33 suseme scsi: [ID 107833 kern.notice] Requested Block: 4 Error Block: 4
Nov 23 01:00:33 suseme scsi: [ID 107833 kern.notice] Vendor: SUN Serial Number:
Nov 23 01:00:33 suseme scsi: [ID 107833 kern.notice] Sense Key: Unit Attention
Nov 23 01:00:33 suseme scsi: [ID 107833 kern.notice] ASC: 0xc (write error), ASCQ: 0x0, FRU: 0x0
Nov 23 01:01:53 suseme scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600a0b8000178ac000002676429130a7 (ssd46):
Nov 23 01:01:53 suseme Error for Command: write(10) Error Level: Retryable
Nov 23 01:01:53 suseme scsi: [ID 107833 kern.notice] Requested Block: 8715 Error Block: 8715
Nov 23 01:01:53 suseme scsi: [ID 107833 kern.notice] Vendor: SUN Serial Number:
Nov 23 01:01:53 suseme scsi: [ID 107833 kern.notice] Sense Key: Unit Attention
Nov 23 01:01:53 suseme scsi: [ID 107833 kern.notice] ASC: 0xc (write error), ASCQ: 0x0, FRU: 0x0
[2] ===================================================
Nov 23 04:13:10 suseme genu-50[2704]: [ID 559880 local7.crit] crit Device 53: State set to DOWN by SAM-FS. Check device log.
Nov 23 04:13:10 suseme genu-50[2704]: [ID 694869 local7.alert] Volume (50:8) is in drive 53 that is off or down.
[3] ==================================================
iostat -En | more
c0t0d0 Soft Errors: 2 Hard Errors: 0 Transport Errors: 0
Vendor: TOSHIBA Product: DVD-ROM SD-M1712 Revision: 1004 Serial No:
Size: 0.00GB <0 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 2 Predictive Failure Analysis: 0
c1t1d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: FUJITSU Product: MAP3735F SUN72G Revision: 1601 Serial No: 0509Q0K1TJ
Size: 73.40GB <73400057856 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
c1t4d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: FUJITSU Product: MAP3735F SUN72G Revision: 1601 Serial No: 0509Q0K1T7
Size: 73.40GB <73400057856 bytes>
==============================================

can you help me how to fix scsi warnning ?
ov 23 01:00:13 suseme scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600a0b80001732a600002f0b4290b53e (ssd21):
Nov 23 01:00:13 suseme Error for Command: write(10) Error Level: Retryable
Nov 23 01:00:13 suseme scsi: [ID 107833 kern.notice] Requested Block: 302073600 Error Block: 302073600
Nov 23 01:00:13 suseme scsi: [ID 107833 kern.notice] Vendor: SUN Serial Number:
Nov 23 01:00:13 suseme scsi: [ID 107833 kern.notice] Sense Key: Unit Attention
Nov 23 01:00:13 suseme scsi: [ID 107833 kern.notice] ASC: 0xc (write error), ASCQ: 0x0, FRU: 0x0
Nov 23 01:00:25 suseme scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600a0b80001732a600002f084290b04e (ssd51):
Nov 23 01:00:25 suseme Error for Command: write(10) Error Level: Retryable
Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] Requested Block: 418872392 Error Block: 418872392
Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] Vendor: SUN Serial Number:
Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] Sense Key: Unit Attention
Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] ASC: 0xc (write error), ASCQ: 0x0, FRU: 0x0
Nov 23 01:00:25 suseme scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600a0b8000178ac0000026714290b04b (ssd50):
Nov 23 01:00:25 suseme Error for Command: write(10) Error Level: Retryable
Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] Requested Block: 304059616 Error Block: 304059616
Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] Vendor: SUN Serial Number:
Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] Sense Key: Unit Attention
Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] ASC: 0xc (write error), ASCQ: 0x0, FRU: 0x0
Nov 23 01:00:33 suseme scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600a0b8000178ac00000267442913027 (ssd20):
Nov 23 01:00:33 suseme Error for Command: write(10) Error Level: Retryable
Nov 23 01:00:33 suseme scsi: [ID 107833 kern.notice] Requested Block: 4 Error Block: 4
Nov 23 01:00:33 suseme scsi: [ID 107833 kern.notice] Vendor: SUN Serial Number:
Nov 23 01:00:33 suseme scsi: [ID 107833 kern.notice] Sense Key: Unit Attention
Nov 23 01:00:33 suseme scsi: [ID 107833 kern.notice] ASC: 0xc (write error), ASCQ: 0x0, FRU: 0x0
Nov 23 01:01:53 suseme scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600a0b8000178ac000002676429130a7 (ssd46):
Nov 23 01:01:53 suseme Error for Command: write(10) Error Level: Retryable
Nov 23 01:01:53 suseme scsi: [ID 107833 kern.notice] Requested Block: 8715 Error Block: 8715
Nov 23 01:01:53 suseme scsi: [ID 107833 kern.notice] Vendor: SUN Serial Number:
Nov 23 01:01:53 suseme scsi: [ID 107833 kern.notice] Sense Key: Unit Attention
Nov 23 01:01:53 suseme scsi: [ID 107833 kern.notice] ASC: 0xc (write error), ASCQ: 0x0, FRU: 0x0
[2] ===================================================

[ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st ack for

Hi All,
I have two Sunfire V880 server with Solaris 5.9 , in solaris cluster 3.1. Oracle 10g Database installed in both srver with RAC. last day i got the following error Swap error from one of the cluster node. In both server 14GB device swap and 14GB file system swap also.. please see the log and give me a solution.. Thanks in advance for all
Jul 24 17:04:28 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
ack for pid 21901 (oracle)
Jul 24 17:04:28 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
ack for pid 21998 (oracle)
Jul 24 17:04:28 server last message repeated 1 time
Jul 24 17:04:28 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
ack for pid 21391 (oracle)
Jul 24 17:04:28 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
ack for pid 21901 (oracle)
Jul 24 17:04:28 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
ack for pid 21387 (oracle)
Jul 24 17:04:28 server last message repeated 1 time
Jul 24 17:04:28 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
ack for pid 5155 (oracle)
Jul 24 17:04:28 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
ack for pid 20732 (oracle)
Jul 24 17:04:28 server last message repeated 1 time
Jul 24 17:04:28 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
ack for pid 5155 (oracle)
Jul 24 17:04:28 server last message repeated 1 time
Jul 24 17:04:28 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
ack for pid 20930 (oracle)
Jul 24 17:04:28 server last message repeated 1 time
Jul 24 17:04:28 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
ack for pid 19016 (oracle)
Jul 24 17:04:28 server last message repeated 3 times
Jul 24 17:04:28 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
ack for pid 20015 (oracle)
Jul 24 17:04:28 server last message repeated 1 time
Jul 24 17:04:29 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
ack for pid 22143 (oracle)
Jul 24 17:04:29 server last message repeated 3 times
Jul 24 17:04:29 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
ack for pid 20817 (oracle)
Jul 24 17:04:29 server last message repeated 3 times
Jul 24 17:04:29 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
ack for pid 21884 (oracle)
Jul 24 17:04:29 server last message repeated 3 times
Jul 24 17:04:29 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
ack for pid 19990 (oracle)
Jul 24 17:04:29 server last message repeated 3 times
Jul 24 17:04:30 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
ack for pid 20107 (oracle)
Jul 24 17:04:30 server last message repeated 3 times
Jul 24 17:48:29 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
ack for pid 10365 (oracle)
Jul 24 17:48:29 server last message repeated 3 times
Jul 24 17:48:29 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
ack for pid 10258 (oracle)
Jul 24 17:48:29 server last message repeated 3 times
Jul 24 17:53:32 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
ack for pid 15862 (oracle)
Jul 24 17:53:32 server last message repeated 3 times
Jul 24 17:53:32 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
ack for pid 10335 (oracle)
Jul 24 17:53:32 server last message repeated 3 times
Jul 24 18:45:13 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
ack for pid 9847 (oracle)
Jul 24 18:45:13 server last message repeated 3 times
Jul 24 18:46:57 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
ack for pid 10883 (oracle)
Jul 24 18:46:57 server last message repeated 6 times
Jul 24 18:47:21 server root: [ID 702911 user.error] Duplicate clsomon found. Restarting.
Jul 24 18:47:21 server root: [ID 702911 user.error] Duplicate clsomon found. Restarting.
Jul 24 18:47:23 server root: [ID 702911 user.error] Oracle clsomon shutdown successful.
Jul 24 18:47:23 server root: [ID 702911 user.error] Oracle clsomon shutdown successful.
Jul 25 00:41:19 server fctl: [ID 517869 kern.warning] WARNING: 111=>fp(2)::GPN_ID for D_ID=20600
failed
Jul 25 00:41:19 server fctl: [ID 517869 kern.warning] WARNING: 112=>fp(2)::N_x Port with D_ID=206
00, PWWN=100000e0022201be disappeared from fabric
Jul 25 00:41:36 server fctl: [ID 517869 kern.warning] WARNING: 126=>fp(2)::N_x Port with D_ID=206
00, PWWN=100000e0022201be reappeared in fabric
bash-2.05$

Note: This thread was originally posted in the [Servers - General Discussion|http://forums.sun.com/forum.jspa?forumID=830] forum, but moved to this forum for closer topic alignment.

[kern.notice] WARNING: mod_load: cannot load module 'nfssrv'

I need to start NFS server on my lab Netra X4200 running Solaris 10.
pgwA# uname -a
SunOS pgwA 5.10 Generic_127128-11 i86pc i386 i86pc
NFS server components were installed from JumpStart CD, I believe:
system SUNWnfsskr Network File System (NFS) server kernel support (Root)
system SUNWnfssr Network File System (NFS) server support (Root)
system SUNWnfssu Network File System (NFS) server support (Usr)
When I try to start NFS server, I see the following syslog messages:
pgwA# svcadm enable svc:/network/nfs/server
pgwA# tail -f /var/adm/messages
Feb 24 15:00:57 pgwA genunix: [ID 819705 kern.notice] /kernel/misc/amd64/nfssrv: undefined symbol
Feb 24 15:00:57 pgwA genunix: [ID 826211 kern.notice] 'nfs4_getflabel'
Feb 24 15:00:57 pgwA genunix: [ID 472681 kern.notice] WARNING: mod_load: cannot load module 'nfssrv'
I googled the error messages but the only note I found was:
http://www.chrisweldon.net/2008/05/29/solaris-10-and-nfs
with exact description of my problem and a weird suggestion to install older NFS packages.
If anybody met such a problem, please let me know how to solve it more intelligently.
Thanks,
Alex

Wrong version of what? Solaris was installed from JumpStart CD and patched appropriately. NFS server components came with the installation.
What steps should I take to have NFS in service? More patches? Which ones? I really need NFS running ASAP.
Thanks.

[SSIS.Pipeline] Warning: Warning: Could not open global shared memory to communicate with performance DLL

Hi All,
I am running an SSIS solution that runs 5 packages in sequence. Only one package fails because of the error:
[SSIS.Pipeline] Warning: Warning: Could not open global shared memory to communicate with performance DLL; data flow performance counters are not available. To resolve, run this package as an administrator, or on the system's console.
I have added myself to the performance counters group.
I am running windows 7 with SSIS 2008.
Any ideas would be appreciated. I have read that some have disabled the warning, but I cannot figure out how to disable a warning.
Thanks.
Ivan

Hi Ivan,
A package would not fail due the warning itself, speaking of which means the account executing it is not privileged to load the Perf counters, and should thus be safely ignored.
To fix visit: http://support.microsoft.com/kb/2496375/en-us
So, the package either has an error or it actually runs.
Arthur My Blog

" Title on the warning : warning, a problem occurred"

I've just bought final cut studio 2. i've installed it and everything seems ok, BUT... when I switch on the mac, a window now appears, bearing the symbol of FCP and it says, more or less (I translate it from french) :
" Title on the warning : warning, a problem occurred"
I've reinstalled FCP, I've trown the prefs, I've updated to 6.1... but nothing... the message remains, everytime I switch on the mac....
It actually doesn't seem to affect the applications... but it quite affect my nerves, after having spent 1000€ for this app... ;-)))
If anyone can help...
thanx!

thanks javabob, but I cant find it
...maybe in my french mac it's called in a different
way.
could you kindly tell me the complete name of the
file and where you found it in your mac precisely?
that would help me a lot in matching the correct
file.
hanks
found it!
it's in system preferences/accounts. in 'open programs' you can delete anything you don't want to appear when you restart the mac. I had actually a few programs that would lauch themselves automatically.... by deleting them here I solved all these problems, including the annoying 'alert' pop up window!

Kernel Warning; WARNING: cpu module 'cpu.AuthenticAMD.15' has API version 0

I installed patch 127128-11 on my solaris 10 x86 server and now I see this warning when I booted.
WARNING: cpu module 'cpu.AuthenticAMD.15' has API version 0,
kernel requires API version 1
The notes in the README state you will only see it after the first reboot and not afterwards.
NOTE 11: On first reboot after applying this rev of Kernel Patch (127128-11),
the following message may appear:
WARNING: cpu module 'cpu.AuthenticAMD.15' has API version 0,
kernel requires API version 1
This message can be safely ignored and will not occur on subsequent
reboots. This error occurs due to the method in which Deferred
Activation patches are installed, and in particular, in the way
in which kernel modules that are being obsoleted by this patch are
deleted. The error is benign and is safe to ignore.
Why do I see this warning every time I reboot the server?
Thanks,
Chris

Try:
1) touch /reconfigure ; "init 6"
and
2) after (1), boot "init 6" and look for the boot_archive being regenerated. If you don't see this message, I would manually re-do the boot archive.
There is a new kernel version now; 138889-08
Use PCA at http://www.par.univie.ac.at/solaris/pca/ to analyze your system (pca -l or pca -L). Then, if you want to patch:
- install the patch utilities patch first
- download all patches into a given directory (read pca docs)
- drop to single user mode
- pca -n -i first to get all the userland and no reboot/reconfig patches in
then
- pca -i to finish it off.
I've been doing this for some time and its been working well. Always backup and be careful.
- Mick

WARNING WARNING IPHONE APP " BLACKLIST"

To all. This is a warning. My wife and I downloaded the app "blacklist" being advised from ATT after receiving numerous telemarketer phonecalls.
This app has corrupted my mobile me contacts account , my address book on my macbook pro and the sync services protocol in mobile me.My computer is ultra slow the beachball is constantly spinning and I have to restart my computer all the time.
I have had 2 separate meetings wuth my genius bar and have been on the phone with the mobile me help desk for 4 hours still ongoing. The mobile me guy is currently conferring with engineering on the issue
Whatever you do , do not download this app to your iphone.
Jesper

Some exemples of people that sued Apple independently of agreements including cases related to the App store, in some cases people got a settlement of some kind, Others are waiting for the outcome,
I am not saying that they are right to sue in most cases, I am just saying that we have the right to fight for our rights as a consumer and the legal system is here for that.
In the end, I always can take my money elsewhere.
http://www.pcmag.com/article2/0,2817,2384301,00.asp
http://www.pcmag.com/article2/0,2817,2372127,00.asp
http://www.pcmag.com/article2/0,2817,2365940,00.asp
http://www.pcmag.com/article2/0,2817,2372127,00.asp
http://www.pcmag.com/article2/0,2817,2349421,00.asp
http://www.pcmag.com/article2/0,2817,2367089,00.asp
http://www.pcmag.com/article2/0,2817,1880615,00.asp
http://www.pcmag.com/article2/0,2817,2383641,00.asp

WARNING, WARNING - Delete and AutoCommit

I've just hit a bug which has cost me a couple of days work and a fair bit of hair loss!
Deleting data seems to autocommit. You cannot roll it back even though the autocommit button is off.
There should be flashing lights in the front of the app saying that this doesn't work.
Another thing - auto commit should not be available as an option as its just wrong/bad.. you name it. Remove it please, pretty please.
Please fix.

I was sure that I had successfully rolled back deletes and I have just confirmed that it works fine for me (just picked a log table I have been working with that I didn't care about the data in).
select count(*) from table;
43366
delete from table where rownum < 10;
Message: 9 rows deleted
select count(*) from table;
43357
rollback (via toolbar icon)
Message: Rollback complete
select count(*) from table;
43366
As far as the Auto Commit option - I wouldn't use it myself, but I can't see a problem with it being available for people to use if they want. I would definitely want it to be off by default, but it is.

WARNING WARNING MALWARE ATTACK

Just a heads up if you have never run into this, yet. I created my website on iweb08. Recently I opened it on a Windows machine (stop throwing things at the monitor). I noticed that some of the words were suddenly underlined or looked a little strange on every page. I ran the cursor them, an ad popped up. Each for a different company. When I opened on my Mac, no problems at all. Back on Windows, there it was. The company name was in very small print in a bottom corner of each ad. So I was able to remove the malware and all problems disappeared. I did find their website and raised **** with them. Sorry, I lost the name of the company.
The moral of the story is:
1. Always check your website on a Windows machine to make sure that those folks who bought Bill Gates snake oil see your website the same way you do on your Mac.
2. Check to make sure no one has fooled with it.

Was it really "malware" or an ad for a service you are using on your iWeb site? The thing about iWeb is that most snippets from services you add to your site have embedded ads in them. That's just one drawback of using a 3rd party service for a feature. Take a form for instance. Most iWeb users use a form service and add the code into iWeb snippet. The form service code usually has an ad embedded in it. It's not malware, it's advertisement for the service you are using. That's why it's always a good idea to develop your features yourself vs. using a 3rd party service. Also remember that according to statistics the majority of web users are browsing on Windoze machines.

Is the situtation required to replace the harddisk

Dear All,
The server V440 with the below situation is that required to replace the harddisk?
iostat -En
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
sd2 Soft Errors: 1 Hard Errors: 35 Transport Errors: 8
Vendor: SEAGATE Product: ST373207LSUN72G Revision: 045A Serial No: XXXXXXX
Size: 73.40GB <73400057856 bytes>
Error message 1 (repeated so many time):
scsi :[ID 107833 kern.notice]      Requested Block: 21928 Error Block: 21928
scsi: [ID 107833 kern.notice]      Vendor: SEAGATE Serial Number: XXXXXXXX
scsi: [ID 107833 kern.notice]      Sense Key: Media Error
scsi: [ID 107833 kern.notice]      ASC: 0x11 (unrecovered read error), ASCQ: 0x0, FRU: 0xf
Error message 2 (1 time only)
scsi: [ID 107833 kern.notice]      Requested Block: 21928 Error Block: 21928
scsi: [ID 107833 kern.notice]      Vendor: SEAGATE Serial Number: XXXXXXXX
scsi: [ID 107833 kern.notice]      Sense Key: Media Error
scsi: [ID 107833 kern.notice]      ASC: 0x11 (unrecovered read error), ASCQ: 0x0, FRU: 0xf
vxio: [ID 174979 kern.notice] NOTICE: VxVM vxio V-5-0-252 read error on object rootdg02-01 of mirror rootvol-02
in volume rootvol (start 1576 length 2) corrected
Thank you!

Hi.
Error "Sense Key: Media Error" show that disk: SEAGATE Serial Number: XXXXXXXX should be replaced.
It's look like this disk under VxVM control.
Read Docs about replace disk under VxVM control. It can require some spcial steps.
Regards.

Retryable warning msg

i have 4 Sun StorageTek 2540 connected via fiber to Sun Fire X4600
the below warning appear many times since one month, 15 days ago all the zpool was degraded and i lose part of my data
could any one have solution for such error
Nov 4 01:58:41 wteniq1 scsi: [ID 107833 kern.warning] WARNING: /pci@7a,0/pci10de,5d@d/pci1077,143@0/fp@0,0/disk@w202400a0b85a33bc,9 (sd44):
Nov 4 01:58:41 wteniq1         Error for Command: write(10)               Error Level: Retryable
Nov 4 01:58:41 wteniq1 scsi: [ID 107833 kern.notice]   Requested Block: 348696594                 Error Block: 348696594
Nov 4 01:58:41 wteniq1 scsi: [ID 107833 kern.notice]   Vendor: SUN                                Serial Number:
Nov 4 01:58:41 wteniq1 scsi: [ID 107833 kern.notice]   Sense Key: Unit Attention
Nov 4 01:58:41 wteniq1 scsi: [ID 107833 kern.notice]   ASC: 0xc (write error), ASCQ: 0x0, FRU: 0x0
Nov 4 01:58:41 wteniq1 scsi: [ID 107833 kern.warning] WARNING: /pci@7a,0/pci10de,5d@d/pci1077,143@0/fp@0,0/disk@w202400a0b85a33bc,0 (sd53):
Nov 4 01:58:41 wteniq1         Error for Command: write(10)               Error Level: Retryable
Nov 4 01:58:41 wteniq1 scsi: [ID 107833 kern.notice]   Requested Block: 434132201                 Error Block: 434132201
Nov 4 01:58:41 wteniq1 scsi: [ID 107833 kern.notice]   Vendor: SUN                                Serial Number:
Nov 4 01:58:41 wteniq1 scsi: [ID 107833 kern.notice]   Sense Key: Unit Attention
Nov 4 01:58:41 wteniq1 scsi: [ID 107833 kern.notice]   ASC: 0xc (write error), ASCQ: 0x0, FRU: 0x0
Nov 4 01:58:41 wteniq1 scsi: [ID 107833 kern.warning] WARNING: /pci@7a,0/pci10de,5d@d/pci1077,143@0/fp@0,0/disk@w202400a0b85a33bc,7 (sd46):
Nov 4 01:58:41 wteniq1         Error for Command: write(10)               Error Level: Retryable
Nov 4 01:58:41 wteniq1 scsi: [ID 107833 kern.notice]   Requested Block: 382881665                 Error Block: 382881665
Nov 4 01:58:41 wteniq1 scsi: [ID 107833 kern.notice]   Vendor: SUN                                Serial Number:
Nov 4 01:58:41 wteniq1 scsi: [ID 107833 kern.notice]   Sense Key: Unit Attention
Nov 4 01:58:41 wteniq1 scsi: [ID 107833 kern.notice]   ASC: 0xc (write error), ASCQ: 0x0, FRU: 0x0
many thanks

thank Pascal
i all ready check it before, where was no alarm except
A controller cache backup battery has failed Tray.85.Battery.A
i read in one blog in the internet the below
The vendor unique ASC/ASCQ code 0xc0/0x00 within the Solaris host; it indicates that there is an internal timeout on the array because of too much load
do you think is it right
regards

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.

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

Similar Messages

Maybe you are looking for