kernel Warning

[khenzi11]

Hi I receive many of this kernel.warning - what I have to do?
Oct 21 16:53:47 os303-su-04 i/o to invalid geometry
Oct 21 16:53:56 os303-su-04 scsi: [ID 107833 kern.warning] WARNING: /pci@8,700000/lpfc@1/sd@1,1 (sd41):
Oct 21 16:53:56 os303-su-04 offline
Oct 21 16:53:56 os303-su-04 scsi: [ID 107833 kern.warning] WARNING: /pci@8,700000/lpfc@1/sd@1,1 (sd41):

the powermt display dev=all shows me now error
os303-su-04% sudo powermt display dev=all
Pseudo name=emcpower0a
CLARiiON ID=APM00035102609 [os303-su-04]
Logical device ID=6006017EF40D00002E22499F9CDCD811 [LUN 90 os303-su-04_rootdisk]
state=alive; policy=CLAROpt; priority=0; queued-IOs=0
Owner: default=SP B, current=SP B
==============================================================================
---------------- Host --------------- - Stor - -- I/O Path - -- Stats ---
### HW Path I/O Paths Interf. Mode State Q-IOs Errors
==============================================================================
2304 pci@8/lpfc@1 c3t0d0s0 SP B1 active alive 0 0
2304 pci@8/lpfc@1 c3t1d0s0 SP A1 active alive 0 0
2305 pci@8/lpfc@3 c4t0d0s0 SP B0 active alive 0 0
2305 pci@8/lpfc@3 c4t1d0s0 SP A0 active alive 0 0

Pseudo name=emcpower2a
CLARiiON ID=APM00035102609 [os303-su-04]
Logical device ID=600601ED120F0000C9575D9E0EAFD811 [LUN 86 os303-su-04_var/opt]
state=alive; policy=CLAROpt; priority=0; queued-IOs=0
Owner: default=SP A, current=SP B
==============================================================================
---------------- Host --------------- - Stor - -- I/O Path - -- Stats ---
### HW Path I/O Paths Interf. Mode State Q-IOs Errors
==============================================================================
2304 pci@8/lpfc@1 c3t0d1s0 SP A1 active alive 0 0
2304 pci@8/lpfc@1 c3t1d1s0 SP B1 active alive 0 0
2305 pci@8/lpfc@3 c4t0d1s0 SP B0 active alive 0 0
2305 pci@8/lpfc@3 c4t1d1s0 SP A0 active alive 0 0

also format is i.o
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w2100002037e9df04,0
1. c1t1d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w2100002037cdf5ec,0
2. c3t0d0 <DGC-RAID5-0205 cyl 49150 alt 2 hd 64 sec 12> rootdisk
/pci@8,700000/lpfc@1/sd@0,0
3. c3t0d1 <DGC-RAID5-0205 cyl 49150 alt 2 hd 256 sec 24> 144_log
/pci@8,700000/lpfc@1/sd@0,1
4. c3t1d0 <DGC-RAID5-0205 cyl 49150 alt 2 hd 64 sec 12> rootdisk
/pci@8,700000/lpfc@1/sd@1,0
5. c3t1d1 <DGC-RAID5-0205 cyl 49150 alt 2 hd 256 sec 24> 144_log
/pci@8,700000/lpfc@1/sd@1,1
6. c4t0d0 <DGC-RAID5-0205 cyl 49150 alt 2 hd 64 sec 12> rootdisk
/pci@8,700000/lpfc@3/sd@0,0
7. c4t0d1 <DGC-RAID5-0205 cyl 49150 alt 2 hd 256 sec 24> 144_log
/pci@8,700000/lpfc@3/sd@0,1
8. c4t1d0 <DGC-RAID5-0205 cyl 49150 alt 2 hd 64 sec 12> rootdisk
/pci@8,700000/lpfc@3/sd@1,0
9. c4t1d1 <DGC-RAID5-0205 cyl 49150 alt 2 hd 256 sec 24> 144_log
/pci@8,700000/lpfc@3/sd@1,1
10. emcpower0a <DGC-RAID5-0205 cyl 49150 alt 2 hd 64 sec 12> rootdisk
/pseudo/emcp@0
11. emcpower2a <DGC-RAID5-0205 cyl 49150 alt 2 hd 256 sec 24> 144_log
/pseudo/emcp@2
Specify disk (enter its number):

can somebody helps me ? Many thanks

 

[culainn]

This may be the issue you are seeing

When VDEVs (virtual devices) are not "activated" for a snap session, they are "not ready" (NR) to the host, similar to when a BCV is established.
Note: Virutal devices are the target devices for Symmetrix snap operations. NR is a SCSI device state.

Different OS's deal with NR devices in different ways.
Solaris tries to read the device label to get the device geometry. Since the device is NR it cannot read the label, hence the label error. Since it cannot read the label, it cannot determine the geometry, hence the geometry error.

 

[culainn]

this may be the issue you are seeing;

When VDEVs (virtual devices) are not "activated" for a snap session, they are "not ready" (NR) to the host, similar to when a BCV is established.
Note: Virutal devices are the target devices for Symmetrix snap operations. NR is a SCSI device state.

Different OS's deal with NR devices in different ways.
Solaris tries to read the device label to get the device geometry. Since the device is NR it cannot read the label, hence the label error. Since it cannot read the label, it cannot determine the geometry, hence the geometry error.

 

[khenzi11]

Thanks - we don't use snap session, but how can I stop this warnings - I use PowerPath VolumeManager maybe it's helps you. In fact - I receive this warning every 3 seconds.

 

[Chacalinc]

take a look to the "failover setup" in the NAvisphere GUI connectivity status. it should be:

:Array
failover mode:1
:Enabled

 

[khenzi11]

Thanks - there are all connectivity to this host like this

ArrayCommPath: enabled
failover mode:1
Unit Serial Number: array

Is there more to check - thanks

 

[khan21]

Did you get the resolution. I am also facing the same exact problem.

 

[khenzi11]

No - I copied the Lun to a new Lun and destroyed the old after. Now is okay.