Sponsored Content
Operating Systems Solaris Problem with accessing SAN disks Post 302197481 by michael.chow on Wednesday 21st of May 2008 04:18:30 AM
Old 05-21-2008
I found the following entries in the system console log:

May 21 15:34:57 wrkarea1 scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/SUNW,qlc@1
/fp@0,0/ssd@w256000c0ffd98fe5,7 (ssd4):
May 21 15:34:57 wrkarea1 Corrupt label; wrong magic number
May 21 15:34:57 wrkarea1 scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/SUNW,qlc@1
/fp@0,0/ssd@w256000c0ffd98fe5,0 (ssd7):
May 21 15:34:57 wrkarea1 Corrupt label; wrong magic number
May 21 15:34:57 wrkarea1 scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/SUNW,qlc@1
/fp@0,0/ssd@w256000c0ffd98fe5,0 (ssd7):
May 21 15:34:57 wrkarea1 Corrupt label; wrong magic number
May 21 15:34:58 wrkarea1 scsi: [ID 107833 kern.warning] WARNING: /pci@1d,700000/SUNW,qlc@2
/fp@0,0/ssd@w266000c0ffe98fe5,7 (ssd22):
May 21 15:34:58 wrkarea1 Corrupt label; wrong magic number
May 21 15:34:58 wrkarea1 scsi: [ID 107833 kern.warning] WARNING: /pci@1d,700000/SUNW,qlc@2
/fp@0,0/ssd@w266000c0ffe98fe5,7 (ssd22):
May 21 15:34:58 wrkarea1 Corrupt label; wrong magic number
May 21 15:34:58 wrkarea1 scsi: [ID 107833 kern.warning] WARNING: /pci@1d,700000/SUNW,qlc@2
/fp@0,0/ssd@w266000c0ffe98fe5,0 (ssd29):
May 21 15:34:58 wrkarea1 Corrupt label; wrong magic number

I have tried to run format to label the disks above but I can't find any of the above disks:

# format
Searching for disks...done

c0t256000C0FFD98FE5d0: configured with capacity of 10.25GB
c0t256000C0FFD98FE5d7: configured with capacity of 5.61GB


AVAILABLE DISK SELECTIONS:
0. c0t216000C0FF898FE5d0 <SUN-StorEdge3510-413C cyl 10498 alt 2 hd 64 sec 32>
/pci@1c,600000/SUNW,qlc@1/fp@0,0/ssd@w216000c0ff898fe5,0
1. c0t216000C0FF898FE5d1 <SUN-StorEdge3510-413C cyl 10498 alt 2 hd 64 sec 32>
/pci@1c,600000/SUNW,qlc@1/fp@0,0/ssd@w216000c0ff898fe5,1
2. c0t216000C0FF898FE5d2 <SUN-StorEdge3510-413C cyl 10498 alt 2 hd 64 sec 32>
/pci@1c,600000/SUNW,qlc@1/fp@0,0/ssd@w216000c0ff898fe5,2
3. c0t216000C0FF898FE5d3 <SUN-StorEdge3510-413C cyl 10498 alt 2 hd 64 sec 32>
/pci@1c,600000/SUNW,qlc@1/fp@0,0/ssd@w216000c0ff898fe5,3
4. c0t216000C0FF898FE5d4 <SUN-StorEdge3510-413C cyl 10498 alt 2 hd 64 sec 32>
/pci@1c,600000/SUNW,qlc@1/fp@0,0/ssd@w216000c0ff898fe5,4
5. c0t216000C0FF898FE5d5 <SUN-StorEdge3510-413C cyl 1498 alt 2 hd 64 sec 32>
/pci@1c,600000/SUNW,qlc@1/fp@0,0/ssd@w216000c0ff898fe5,5
6. c0t216000C0FF898FE5d6 <SUN-StorEdge3510-413C cyl 9998 alt 2 hd 64 sec 32>
/pci@1c,600000/SUNW,qlc@1/fp@0,0/ssd@w216000c0ff898fe5,6
7. c0t216000C0FF898FE5d7 <SUN-StorEdge3510-413C cyl 10498 alt 2 hd 64 sec 32>
/pci@1c,600000/SUNW,qlc@1/fp@0,0/ssd@w216000c0ff898fe5,7
8. c0t216000C0FF898FE5d8 <SUN-StorEdge3510-413C cyl 10498 alt 2 hd 64 sec 32>
/pci@1c,600000/SUNW,qlc@1/fp@0,0/ssd@w216000c0ff898fe5,8
9. c0t216000C0FF898FE5d9 <SUN-StorEdge3510-413C cyl 10498 alt 2 hd 64 sec 32>
/pci@1c,600000/SUNW,qlc@1/fp@0,0/ssd@w216000c0ff898fe5,9
10. c0t216000C0FF898FE5d10 <SUN-StorEdge3510-413C cyl 10498 alt 2 hd 64 sec 32>
/pci@1c,600000/SUNW,qlc@1/fp@0,0/ssd@w216000c0ff898fe5,a
11. c0t216000C0FF898FE5d11 <SUN-StorEdge3510-413C cyl 10498 alt 2 hd 64 sec 32>
/pci@1c,600000/SUNW,qlc@1/fp@0,0/ssd@w216000c0ff898fe5,b
12. c0t216000C0FF898FE5d12 <SUN-StorEdge3510-413C cyl 1498 alt 2 hd 64 sec 32>
/pci@1c,600000/SUNW,qlc@1/fp@0,0/ssd@w216000c0ff898fe5,c
13. c0t216000C0FF898FE5d13 <SUN-StorEdge3510-413C cyl 9998 alt 2 hd 64 sec 32>
/pci@1c,600000/SUNW,qlc@1/fp@0,0/ssd@w216000c0ff898fe5,d
14. c0t256000C0FFD98FE5d0 <SUN-StorEdge3510-413C cyl 10498 alt 2 hd 64 sec 32>
/pci@1c,600000/SUNW,qlc@1/fp@0,0/ssd@w256000c0ffd98fe5,0
15. c0t256000C0FFD98FE5d1 <SUN-StorEdge3510-413C cyl 10498 alt 2 hd 64 sec 32>
/pci@1c,600000/SUNW,qlc@1/fp@0,0/ssd@w256000c0ffd98fe5,1
16. c0t256000C0FFD98FE5d2 <SUN-StorEdge3510-413C cyl 10498 alt 2 hd 64 sec 32>
/pci@1c,600000/SUNW,qlc@1/fp@0,0/ssd@w256000c0ffd98fe5,2
17. c0t256000C0FFD98FE5d3 <SUN-StorEdge3510-413C cyl 10498 alt 2 hd 64 sec 32>
/pci@1c,600000/SUNW,qlc@1/fp@0,0/ssd@w256000c0ffd98fe5,3
18. c0t256000C0FFD98FE5d4 <SUN-StorEdge3510-413C cyl 10498 alt 2 hd 64 sec 32>
/pci@1c,600000/SUNW,qlc@1/fp@0,0/ssd@w256000c0ffd98fe5,4
19. c0t256000C0FFD98FE5d5 <SUN-StorEdge3510-413C cyl 1498 alt 2 hd 64 sec 32>
/pci@1c,600000/SUNW,qlc@1/fp@0,0/ssd@w256000c0ffd98fe5,5
20. c0t256000C0FFD98FE5d6 <SUN-StorEdge3510-413C cyl 9998 alt 2 hd 64 sec 32>
/pci@1c,600000/SUNW,qlc@1/fp@0,0/ssd@w256000c0ffd98fe5,6
21. c0t256000C0FFD98FE5d7 <SUN-StorEdge3510-413C cyl 5749 alt 2 hd 64 sec 32>
/pci@1c,600000/SUNW,qlc@1/fp@0,0/ssd@w256000c0ffd98fe5,7
22. c1t226000C0FFB98FE5d0 <SUN-StorEdge3510-413C cyl 10498 alt 2 hd 64 sec 32>
/pci@1d,700000/SUNW,qlc@2/fp@0,0/ssd@w226000c0ffb98fe5,0
23. c1t226000C0FFB98FE5d1 <SUN-StorEdge3510-413C cyl 10498 alt 2 hd 64 sec 32>
/pci@1d,700000/SUNW,qlc@2/fp@0,0/ssd@w226000c0ffb98fe5,1
24. c1t226000C0FFB98FE5d2 <SUN-StorEdge3510-413C cyl 10498 alt 2 hd 64 sec 32>
/pci@1d,700000/SUNW,qlc@2/fp@0,0/ssd@w226000c0ffb98fe5,2
25. c1t226000C0FFB98FE5d3 <SUN-StorEdge3510-413C cyl 10498 alt 2 hd 64 sec 32>
/pci@1d,700000/SUNW,qlc@2/fp@0,0/ssd@w226000c0ffb98fe5,3
26. c1t226000C0FFB98FE5d4 <SUN-StorEdge3510-413C cyl 10498 alt 2 hd 64 sec 32>
/pci@1d,700000/SUNW,qlc@2/fp@0,0/ssd@w226000c0ffb98fe5,4
27. c1t226000C0FFB98FE5d5 <SUN-StorEdge3510-413C cyl 1498 alt 2 hd 64 sec 32>
/pci@1d,700000/SUNW,qlc@2/fp@0,0/ssd@w226000c0ffb98fe5,5
28. c1t226000C0FFB98FE5d6 <SUN-StorEdge3510-413C cyl 9998 alt 2 hd 64 sec 32>
/pci@1d,700000/SUNW,qlc@2/fp@0,0/ssd@w226000c0ffb98fe5,6
29. c1t226000C0FFB98FE5d7 <SUN-StorEdge3510-413C cyl 10498 alt 2 hd 64 sec 32>
/pci@1d,700000/SUNW,qlc@2/fp@0,0/ssd@w226000c0ffb98fe5,7
30. c1t226000C0FFB98FE5d8 <SUN-StorEdge3510-413C cyl 10498 alt 2 hd 64 sec 32>
/pci@1d,700000/SUNW,qlc@2/fp@0,0/ssd@w226000c0ffb98fe5,8
31. c1t226000C0FFB98FE5d9 <SUN-StorEdge3510-413C cyl 10498 alt 2 hd 64 sec 32>
/pci@1d,700000/SUNW,qlc@2/fp@0,0/ssd@w226000c0ffb98fe5,9
32. c1t226000C0FFB98FE5d10 <SUN-StorEdge3510-413C cyl 10498 alt 2 hd 64 sec 32>
/pci@1d,700000/SUNW,qlc@2/fp@0,0/ssd@w226000c0ffb98fe5,a
33. c1t226000C0FFB98FE5d11 <SUN-StorEdge3510-413C cyl 10498 alt 2 hd 64 sec 32>
/pci@1d,700000/SUNW,qlc@2/fp@0,0/ssd@w226000c0ffb98fe5,b
34. c1t226000C0FFB98FE5d12 <SUN-StorEdge3510-413C cyl 1498 alt 2 hd 64 sec 32>
/pci@1d,700000/SUNW,qlc@2/fp@0,0/ssd@w226000c0ffb98fe5,c
35. c1t226000C0FFB98FE5d13 <SUN-StorEdge3510-413C cyl 9998 alt 2 hd 64 sec 32>
/pci@1d,700000/SUNW,qlc@2/fp@0,0/ssd@w226000c0ffb98fe5,d
36. c1t266000C0FFE98FE5d0 <drive type unknown>
/pci@1d,700000/SUNW,qlc@2/fp@0,0/ssd@w266000c0ffe98fe5,0
37. c1t266000C0FFE98FE5d1 <SUN-StorEdge3510-413C cyl 10498 alt 2 hd 64 sec 32>
/pci@1d,700000/SUNW,qlc@2/fp@0,0/ssd@w266000c0ffe98fe5,1
38. c1t266000C0FFE98FE5d2 <SUN-StorEdge3510-413C cyl 10498 alt 2 hd 64 sec 32>
/pci@1d,700000/SUNW,qlc@2/fp@0,0/ssd@w266000c0ffe98fe5,2
39. c1t266000C0FFE98FE5d3 <SUN-StorEdge3510-413C cyl 10498 alt 2 hd 64 sec 32>
/pci@1d,700000/SUNW,qlc@2/fp@0,0/ssd@w266000c0ffe98fe5,3
40. c1t266000C0FFE98FE5d4 <SUN-StorEdge3510-413C cyl 10498 alt 2 hd 64 sec 32>
/pci@1d,700000/SUNW,qlc@2/fp@0,0/ssd@w266000c0ffe98fe5,4
41. c1t266000C0FFE98FE5d5 <SUN-StorEdge3510-413C cyl 1498 alt 2 hd 64 sec 32>
/pci@1d,700000/SUNW,qlc@2/fp@0,0/ssd@w266000c0ffe98fe5,5
42. c1t266000C0FFE98FE5d6 <SUN-StorEdge3510-413C cyl 9998 alt 2 hd 64 sec 32>
/pci@1d,700000/SUNW,qlc@2/fp@0,0/ssd@w266000c0ffe98fe5,6
43. c1t266000C0FFE98FE5d7 <drive type unknown>
/pci@1d,700000/SUNW,qlc@2/fp@0,0/ssd@w266000c0ffe98fe5,7
44. c3t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1f,700000/scsi@2/sd@0,0
45. c3t2d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1f,700000/scsi@2/sd@2,0
46. c3t3d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1f,700000/scsi@2/sd@3,0
Specify disk (enter its number):
 

9 More Discussions You Might Find Interesting

1. Linux

problem with disks on SAN

Hi I have a linux box attched to a SAN storage from EMC with RAID 5 .I understand that it has 3g cache howver a 20gb file creation takes too much time here are my results any ideas why time dd if=/dev/zero of=disk.img bs=1048576 count=20000 20000+0 records in 20000+0 records out 997.59s... (2 Replies)
Discussion started by: xiamin
2 Replies

2. AIX

mksysb restore ( vgs on SAN disks)

I have my application vendor looking at this but I want to do my own investigation. I restored from mksysb and I see my vgs that contain my internal disks. But I do not see my vgs that contain disks from the SAN. This scares me .. {{ Ha, ha!! My AIX expert boss just told me I have nothing... (0 Replies)
Discussion started by: Skyybugg
0 Replies

3. AIX

Configurin EMC SAN disks on AIX

This may sound like an absolute rookie question, and it is. I have been working on Migrating our HP and Solaris servers to the new EMC SAN and know the routines backwards. Now we've suddenly got a new IBM server and I don't even know how to check if it is connected to the switch. Can someone... (1 Reply)
Discussion started by: ronellevan
1 Replies

4. Solaris

SAN DISKS - Number of slices ?

Good morning to one and all :-) Thank god its Friday, as its bee na rubbish week for me ! So, a quick question. Disks ! Ive got a few local disks, and a few SAN disks used on my solaris server. Whats confusing me, and Im not sure if there's an issue at the SAN end, or my end, regarding the... (3 Replies)
Discussion started by: sbk1972
3 Replies

5. Filesystems, Disks and Memory

Help with finding WWN of SAN disks

Hi, I'm new to SAN storage so I was wondering if someone can assist me with a problem. I have a solaris 10 OS with 3 SAN devices attached. We are trying to troubleshoot performance so I was asked to get the WWN of each SAN disk and show what it's attached to via the SVM mount in the metastat... (1 Reply)
Discussion started by: rkruck
1 Replies

6. UNIX for Dummies Questions & Answers

Identify SAN disks

Hello everybody, I'm using the binary inqraid (Linux RHEL) in order to retrieve information about SAN disks. The questions are: Given an LDEV, how do I know if the SAN disk related to this LDEV is being used by the OS? I mean, how can I demonstrate to "Storage department" that all disks of... (4 Replies)
Discussion started by: asanchez
4 Replies

7. Red Hat

Identify SAN disks not in use

Hello, How can I identify SAN disks not in use by the OS? Thank you. (8 Replies)
Discussion started by: asanchez
8 Replies

8. AIX

Issue with increasing size of SAN disks on AIX

HI, I have had an issue last night while trying to extend a filesystsem . chvg -g <vg> command cameback with an error 0516-1790 chvg: Failed bootinfo -s hdisk9. Ensure the physical volume is available and try again. 0516-732 chvg: Unable to change volume group u01vg. the VG has 1... (1 Reply)
Discussion started by: xmen01
1 Replies

9. Solaris

Sense key unit attention & iostat hardware and transport errors on SAN disks

Hello, I'm trying to get to the bottom of SAN disk errors we've been seeing. Server is Sun Fire X4270 M2 running Solaris 10 8/11 u10 X86 since April 2012. SAN HBAs are SG-PCIE2FC-QF8-Z-Sun-branded Qlogic. SAN storage system is Hitachi VSP. We have 32 LUNs in use and another 8 LUNs not brought... (4 Replies)
Discussion started by: TKD
4 Replies
All times are GMT -4. The time now is 02:58 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy