StorEdge 3310 RAID hung.

During the billing run on a Sun Fire V440, the attached 3310 hung. Reboots of the server did nothing to improve the situation, but once the RAID was powercycled everything was alright again.
sccli version 2.1.1
built 2005.09.16.23.10
build 1 for solaris-sparc
Vendor: SUN
Product: StorEdge 3310
Revision: 0325
Peripheral Device Type: 0x0
NVRAM Defaults: 325S 3310 v1.37
Bootrecord version: 1.31G
Serial Number: 07CB61
There are no "event" entries for this trouble listed in sscli, and everything comes up green. The only errors we received at the time were that of SCSI errors:
Aug 10 10:49:30 InfranetDB01 scsi: [ID 107833 kern.warning] WARNING: /pci@1f,700
000/scsi@2,1/sd@0,0 (sd16):
Aug 10 10:49:30 InfranetDB01 Error for Command: write(10) Error
Level: Retryable
Aug 10 10:49:30 InfranetDB01 scsi: [ID 107833 kern.notice] Requested Block:
289557696 Error Block: 289557696
Aug 10 10:49:30 InfranetDB01 scsi: [ID 107833 kern.notice] Vendor: SUN
Serial Number: 29C8306F-00
Aug 10 10:49:30 InfranetDB01 scsi: [ID 107833 kern.notice] Sense Key: Unit
Attention
Aug 10 10:49:30 InfranetDB01 scsi: [ID 107833 kern.notice] ASC: 0x29 (power
on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
Aug 10 11:01:12 InfranetDB01 scsi: [ID 107833 kern.notice] /pci@1f,700000/scsi@2
,1 (mpt1):
Aug 10 11:01:12 InfranetDB01 got external SCSI bus reset.
Aug 10 11:01:12 InfranetDB01 scsi: [ID 365881 kern.info] /pci@1f,700000/scsi@2,1
(mpt1):
Aug 10 11:01:12 InfranetDB01 Log info 11030000 received for target 0.
Aug 10 11:01:12 InfranetDB01 scsi_status=0, ioc_status=804b, scsi_state=8
Aug 10 11:01:12 InfranetDB01 scsi: [ID 107833 kern.notice] /pci@1f,700000/scsi@2
,1 (mpt1):
Aug 10 11:01:12 InfranetDB01 got external SCSI bus reset.
[repeat]
The question is whether or not to upgrade the firmware. Since the current firmware is so old (version 3.x) there seems to be special instructions to bring it to 4.x, and eventually 4.15G. Which would include OS patches as well. (117171-12).
Or, just carry on, since this has only happened once (during the last billing run) in the last 9 runs/months.

What is the difference between the host/drive channel? Besides the fact that they are their for connecting to disk drive or to host. Because lets say I connect the first RAID controller to the second one, host-to-host configuration from one RAID to another, will the host see this transparently?
By the way, I tried the JBOD method you mention so basically just connect one of the RAID unit to the other one just as a JBOD and the RAID controller can see the disks on a difference channel but only half of the disk because the RAID I/O actually have internal conneciton to half of the disk, while the other half is jumper.

Similar Messages

Converting Storedge 3310 RAID unit to act as JBOD?

Hello, I have been struggling with this configuration, any advice is appreciated.
I have 4 x Storedge 3310 RAID units each with it own controller. I have 1 x Linux host and 1 x HBA in the host, with ch0 and ch1. I want to be able access to all 4 Storedge 3310s. Normally if this were 2 x Storedge 3310 RAID + 2 x JBOD then I just connect each RAID unit to a JBOD then each RAID to ch0 and ch1 respectively to the host. Instead what I have is 4 x Storedge 3310 RAID units, is there a way to convert two of the Storedge 3310 unit to make it act exactly like a JBOD? So that I can daisy-chain them to make them all accessible to the host?
Or adding another HBA card to the host is the only option?
thank you.

What is the difference between the host/drive channel? Besides the fact that they are their for connecting to disk drive or to host. Because lets say I connect the first RAID controller to the second one, host-to-host configuration from one RAID to another, will the host see this transparently?
By the way, I tried the JBOD method you mention so basically just connect one of the RAID unit to the other one just as a JBOD and the RAID controller can see the disks on a difference channel but only half of the disk because the RAID I/O actually have internal conneciton to half of the disk, while the other half is jumper.

Partition Storedge 3310

Hello All,
My first connection on this forum & I would need your help.
I have to configure a Storedge 3310 (6 disks 72Gb).
Already created:
1 Logical Drive: 5 disks in Raid 5 + 1 Spare
Size of the drive: 279GB.
I need to create 11 partitions (10*12GB + 1*159GB), but apparently, I can create only 8 partitions (from 0 to 7).
Could you help me? I don't know how to do.
I already read this topic: http://forum.java.sun.com/thread.jspa?forumID=831&threadID=5098175
But the answer is not really clear (for me...)
Thx.
Eric
Message was edited by:
Eric_MdZ

I had to do something similar on site today, I believe (although have not tried it) that you alter the number of partitions to create on the 3320, however an alternative way of partitioning the Logical Drive is to let Solaris do it, by that I mean LVM ( formly known as disksuite). Bring the logical drive into solaris and create one large partition. Bring that single partition into LVM and then use "soft partitioning" to break it up. I have done this before and it works fine, its just another way of doing the same job albeit on the host and not on the Array.

Storedge 3310 and format

hi,
i have the following problem:
a storedge 3310 with raid controller. i have partitioned the volume ( which consists of 6 raid 1 logical drives) into 4 partions and assigned luns to these partitions.
probe-scsi-all shows the following:
/pci@1e,600000/pci@2/scsi@4
Target 0
Unit 0 Disk SUN StorEdge 3310 0325
Unit 1 Disk SUN StorEdge 3310 0325
Unit 2 Disk SUN StorEdge 3310 0325
Unit 3 Disk SUN StorEdge 3310 0325
format shows only the first one:
0. c0t0d0
/pci@1c,600000/scsi@2/sd@0,0
1. c0t1d0
/pci@1c,600000/scsi@2/sd@1,0
2. c2t0d0
/pci@1e,600000/pci@2/scsi@4/sd@0,0
where are the other three partitions?

Hi there,
I have a similar situation where I set up a SE 3310 connected to a Sunfire V210 running Solaris 10 GA.
The SE 3310 was set up as 2 RAID 5 logical volumes, each
with 5x72GB disk drives. I also map the hosts LUNS etc...
At the V210, when I did the probe-scsi-all it sees both RAID5
logical disks as StorEdge 3310 0325 (firmware 3.25)
however when I boot up with the -rv option, it only sees one
RAID5. Where is the other RAID 5 logical drive?
I did update_drv -f sd, devfsadm; manually edit the sd.conf
to add additional controllers and LUN's (c0,c1,c2 and up to
32 LUN's for each controller, but I still do not see the other
RAID5 logical drive. Where is it?
Please help !!!
Tony

Multi-initated LUNS on Sun StorEdge 3310

I recently received two Sun V20Zs and a StorEdge 3310, and I am asked to cluster these two machines with the 3310 as shared storage. 3310 came with two raid controllers.
My question is, could I create multi-initiaged LUNs and have these LUNs mapped by the V20Z. Reason behind having the multi-imitated LUNs is it will facilitate fail-over in case a one of the V20Z are unavailable.
V20Zs are running Fedora Core 3.
Thanks for your help.

A good output that would give you a hint of a problem is iostat -En
This output reports anykind of errors to a particular disk since the last reboot. If you are seeing high error numbers, then you can move onto running a file system check - fsck - on the drive.
If you have anykind of RAID setup, check to see if any issues are being reported. Depending on what you are using to manage the RAID - Veritas Volume Manager or Solaris Disk Suite - they will most certainly tell you if there is an issue. A vxprint for Veritas and a metastat for DiskSuite will show you what you have setup and if there are any recognized disk issues.

Partition logical drive storedge 3310

Hi
I have Sun storedge 3310 version 413B, i create logical drive in Raid 5 configuration:
LD LD-ID Size Assigned Type Disks Spare Failed Status
ld0 68EB1906 272.46GB Primary RAID5 5 1 0 Good
and i need create 16 partitions on it, but i can create only 7 partitions:
* partitions
LD/LV ID-Partition Size
ld0-00 68EB1906-00 14.00GB
ld0-01 68EB1906-01 14.00GB
ld0-02 68EB1906-02 14.00GB
ld0-03 68EB1906-03 14.00GB
ld0-04 68EB1906-04 14.00GB
ld0-05 68EB1906-05 14.00GB
ld0-06 68EB1906-06 14.00GB
ld0-07 68EB1906-07 14.00GB
How i can create other eight partitions on ld0; i need create this configuration:
ld0-00 68EB1906-00 14.00GB
ld0-01 68EB1906-01 14.00GB
ld0-02 68EB1906-02 14.00GB
ld0-03 68EB1906-03 14.00GB
ld0-04 68EB1906-04 14.00GB
ld0-05 68EB1906-05 14.00GB
ld0-06 68EB1906-06 14.00GB
ld0-07 68EB1906-07 14.00GB
ld0-08 68EB1906-08 14.00GB
ld0-09 68EB1906-09 14.00GB
ld0-0a 68EB1906-0A 14.00GB
ld0-0b 68EB1906-0B 14.00GB
ld0-0c 68EB1906-0C 20.00GB
ld0-0d 68EB1906-0D 20.00GB
ld0-0e 68EB1906-0E 20.00GB
ld0-0f 68EB1906-0F 20.00GB
ld0-10 68EB1906-10 24.46GB
any idea?....thanks

If you are using lun mapping to create your partitions, (done by using telnet to the array and then selecting "View and Edit Host Luns") you have to tell the array the maximum numbers of luns you can create. Some systems will only let you create one by default and you can't make any changes to the size of the lun you are trying to present to your host. There is an option when you telnet to the box in the controller area for the maximum number of luns you can create. Luns in this case are partitions.
If you are not trying to partition your logical drive by using lun mapping, I don't know what your problem is.
Stephen

Adding 146GB drives to StorEdge 3310

I have a StorEdge 3310 with 6 72GB drives in it (RAID 10). Customer wants to add a pair of 146GB drives to increase capacity. Is there any issue with having disparate sized drives in a 3310 RAID array?

I have a 3310 disk array with 12 72gb drives ,
configured raid 5 , 1 hot spare...The host side scsi
parms are max queded i/o 256, luns /host 32, max #
concurent host lun 128, cyl/head/sector
cyl-65536,head-64, sector-255...... NO problems.
I have added a 3310 expansion unit to the original
disk array. expansion unit also configured raid5 ,
one local spare. sd.conf also update. I am able to
newfs, mount and use the disk. however it odd
compared to othe disks when using the solaris format
command. questions are the OK for 146gb drives. I
noticed that one of the options for cyl/head/sector
was variable. does anyone have experience using the
option???

Storedge 3310 & Dual Ultra3 Adaptor

Hi all,
A couple of things...
1. We have 2 storedge 3310 and two machines with Ultra3 Adaptors. I can not see the 3310 using the Ultra3 adaptors. If I plug the 3310 into the host controller I can see it, (but that is not ideal as it is running slow). at the 'ok' prompt I can see the 3310, but I can never get anything to display in 'format' or on the ssconsole.
commands tried:
reboot -- -r
update_drv -f sd
devfsadm -v
All with no luck. Any ideas?
2. With the 3310 I have configure one logical RAID 5 drive (5 disks) and partitioned into 4 and mapped each partition to a host lun.
I have mucked with /kernel/drv/sd.conf and put "set scsi_options=0x43ff8" into /etc/system, I can never see the anything but the first partion on the first lun.
Help please :-)

Have you downloaded and installed the Ultra3 SUNWqus....packages & installed patch as in the release notes or InfoDoc 47841?
http://sunsolve.Sun.COM/data/816/816-2157/pdf/816-2157-14.pdf
http://sunsolve.Sun.COM/pub-cgi/retrieve.pl?doc=finfodoc%2F47841&zone_110=47841

Not all storedge 3310 disk showing up

I have a storedge 3310 hooked to my V440 running solaris 8 and not all the logical disks are showing up in the format command. I have a total of 4 logical disks configured on the array, two on the primary controller and 2 on the secondary controller. It appears that I only have one logical drive from each controller appearing. Any help would be appreciated.
Thanks

That worked however, now when I run format I get the following errors:
8. c4t1d1 <SUN-StorEdge3310-0325 cyl 34474 alt 2 hd 64 sec 32>
/pci@1d,700000/scsi@1/sd@1,1
9. c4t1d3 <SUN-StorEdge3310-0325 cyl 34474 alt 2 hd 64 sec 32>
/pci@1d,700000/scsi@1/sd@1,3
Specify disk (enter its number): Feb 21 18:10:44 socorro scsi: Vendor 'SUN', product 'StorEdge', 70606848 512 byte blocks
Feb 21 18:10:44 socorro scsi: WARNING: /pci@1c,600000/scsi@1/sd@0,2 (sd160):
Feb 21 18:10:44 socorro corrupt label - wrong magic number
Feb 21 18:10:44 socorro scsi: Vendor 'SUN', product 'StorEdge', 70606848 512 byte blocks
Feb 21 18:10:44 socorro scsi: WARNING: /pci@1d,700000/scsi@1/sd@1,1 (sd204):
Feb 21 18:10:44 socorro corrupt label - wrong magic number
Feb 21 18:10:44 socorro scsi: Vendor 'SUN', product 'StorEdge', 70606848 512 byte blocks
Will look into thme and see if I can get them resolved.
Thanks

StorEdge 3300 RAID

in fact im not very good in raids server. there are some errors i found in StorEdge 3300 RAID as follow :
DEVICE       TYPE      DISK         GROUP        STATUS
c1t0d0s2     sliced    rootdisk_1   rootdg       online
c1t1d0s2     sliced    mirrdisk_1   rootdg       online
c2t0d0s2     sliced    -            -            error
c2t0d1s2     sliced    -            -            online
c3t0d0s2     sliced    -            -            error
c3t0d1s2     sliced    igwbdg02     igwbdg       online
-            -         igwbdg01     igwbdg       failed was:c2t0d1s2
Disk group: rootdg
TY NAME         ASSOC        KSTATE   LENGTH   PLOFFS   STATE    TUTIL0 PUTIL0
dg rootdg       rootdg       -        -        -        -        -       -
dm mirrdisk_1   c1t1d0s2     -        143339136 -       -        -       -
dm rootdisk_1   c1t0d0s2     -        143339136 -       -        -       -
v rootdisk_15vol gen        ENABLED 1027776 -        ACTIVE   -       -
pl rootdisk_15vol-01 rootdisk_15vol ENABLED 1027776 -   ACTIVE   -       -
sd rootdisk_1-04 rootdisk_15vol-01 ENABLED 1027776 0    -        -       -
pl rootdisk_15vol-02 rootdisk_15vol ENABLED 1027776 -   ACTIVE   -       -
sd mirrdisk_1-04 rootdisk_15vol-02 ENABLED 1027776 0    -        -       -
v rootvol      root         ENABLED 114825984 -       ACTIVE   -       -
pl rootvol-01   rootvol      ENABLED 114825984 -       ACTIVE   -       -
sd rootdisk_1-B0 rootvol-01 ENABLED 1        0        -        -       Block0
sd rootdisk_1-02 rootvol-01 ENABLED 114825983 1       -        -       -
pl rootvol-02   rootvol      ENABLED 114825984 -       ACTIVE   -       -
sd mirrdisk_1-01 rootvol-02 ENABLED 114825984 0       -        -       -
v swapvol      swap         ENABLED 8395200 -        ACTIVE   -       -
pl swapvol-01   swapvol      ENABLED 8395200 -        ACTIVE   -       -
sd rootdisk_1-01 swapvol-01 ENABLED 8395200 0        -        -       -
pl swapvol-02   swapvol      ENABLED 8395200 -        ACTIVE   -       -
sd mirrdisk_1-02 swapvol-02 ENABLED 8395200 0        -        -       -
v var          gen          ENABLED 16780224 -        ACTIVE   -       -
pl var-01       var          ENABLED 16780224 -        ACTIVE   -       -
sd rootdisk_1-03 var-01      ENABLED 16780224 0        -        -       -
pl var-02       var          ENABLED 16780224 -        ACTIVE   -       -
sd mirrdisk_1-03 var-02      ENABLED 16780224 0        -        -       -
Disk group: igwbdg
TY NAME         ASSOC        KSTATE   LENGTH   PLOFFS   STATE    TUTIL0 PUTIL0
dg igwbdg       igwbdg       -        -        -        -        -       -
dm igwbdg01     -            -        -        -        NODEVICE -       -
dm igwbdg02     c3t0d1s2     -        211394560 -       -        -       -
v back         fsgen        ENABLED 98304000 -        ACTIVE   -       -
pl back-01      back         DISABLED 98304000 -        NODEVICE -       -
sd igwbdg01-04 back-01      DISABLED 98304000 0        NODEVICE -       -
pl back-02      back         ENABLED 98304000 -        ACTIVE   -       -
sd igwbdg02-04 back-02      ENABLED 98304000 0        -        -       -
v front        fsgen        ENABLED 98304000 -        ACTIVE   -       -
pl front-01     front        DISABLED 98304000 -        NODEVICE -       -
sd igwbdg01-03 front-01     DISABLED 98304000 0        NODEVICE -       -
pl front-02     front        ENABLED 98304000 -        ACTIVE   -       -
sd igwbdg02-03 front-02     ENABLED 98304000 0        -        -       -
v igwbdg-stat fsgen        ENABLED 1048576 -        ACTIVE   -       -
pl igwbdg-stat-01 igwbdg-stat DISABLED 1048576 -        NODEVICE -       -
sd igwbdg01-01 igwbdg-stat-01 DISABLED 1048576 0       NODEVICE -       -
pl igwbdg-stat-02 igwbdg-stat ENABLED 1048576 -        ACTIVE   -       -
sd igwbdg02-01 igwbdg-stat-02 ENABLED 1048576 0        -        -       -
v log-alarm    fsgen        ENABLED 8388608 -        ACTIVE   -       -
pl log-alarm-01 log-alarm    DISABLED 8388608 -        NODEVICE -       -
sd igwbdg01-02 log-alarm-01 DISABLED 8388608 0        NODEVICE -       -
pl log-alarm-02 log-alarm    ENABLED 8388608 -        ACTIVE   -       -
sd igwbdg02-02 log-alarm-02 ENABLED 8388608 0        -        -       -
*Jan 21 14:04:14 igwb1 lomv: [ID 702911 kern.notice] 1/21/2008 14:4:14 GMT LOM time reference*
*Jan 22 05:53:10 igwb1 scsi: [ID 107833 kern.warning] WARNING: /pci@8,700000/pci@2/scsi@4/sd@0,1 (sd61):*
Jan 22 05:53:10 igwb1   disk not responding to selection
*Jan 22 05:53:11 igwb1 scsi: [ID 107833 kern.warning] WARNING: /pci@8,700000/pci@2/scsi@4/sd@0,1 (sd61):*
Jan 22 05:53:11 igwb1   disk not responding to selection
*Jan 22 05:53:24 igwb1 scsi: [ID 107833 kern.warning] WARNING: /pci@8,700000/pci@2/scsi@4/sd@0,1 (sd61):*
Jan 22 05:53:24 igwb1   disk not responding to selection
*Jan 22 05:53:30 igwb1 scsi: [ID 107833 kern.warning] WARNING: /pci@8,700000/pci@2/scsi@4/sd@0,1 (sd61):*
Jan 22 05:53:30 igwb1   disk not responding to selection
*Jan 22 05:53:31 igwb1 scsi: [ID 107833 kern.warning] WARNING: /pci@8,700000/pci@2/scsi@4/sd@0,1 (sd61):*
Jan 22 05:53:31 igwb1   Error for Command: write(10)               Error Level: Fatal
*Jan 22 05:53:31 igwb1 scsi: [ID 107833 kern.notice] Requested Block: 108158864 Error Block: 10815886*
*4*
*Jan 22 05:53:31 igwb1 scsi: [ID 107833 kern.notice] Vendor: SUN Serial Number: 276710*
C4-01
*Jan 22 05:53:31 igwb1 scsi: [ID 107833 kern.notice] Sense Key: Not Ready*
*Jan 22 05:53:31 igwb1 scsi: [ID 107833 kern.notice] ASC: 0x4 (<vendor unique code 0x4>), ASCQ: 0x1, FRU: 0x0*
*Jan 22 05:53:31 igwb1 vxdmp: [ID 619769 kern.notice] NOTICE: vxdmp: Path failure on 32/0x1ec*
*Jan 22 05:53:31 igwb1 vxdmp: [ID 997040 kern.notice] NOTICE: vxvm:vxdmp: disabled path 32/0x1e8 belonging to the dmpnode*
*274/0x28*
*Jan 22 05:53:31 igwb1 vxdmp: [ID 148046 kern.notice] NOTICE: vxvm:vxdmp: disabled dmpnode 274/0x28*
*Jan 22 05:53:31 igwb1 vxio: [ID 238951 kern.warning] WARNING: vxvm:vxio: error on Plex log-alarm-01 while writing volume*
log-alarm offset 1605776 length 16
*Jan 22 05:53:31 igwb1 vxio: [ID 751920 kern.warning] WARNING: vxvm:vxio: Plex log-alarm-01 detached from volume log-alar*
m
*Jan 22 05:53:31 igwb1 vxio: [ID 838567 kern.warning] WARNING: vxvm:vxio: igwbdg01-02 Subdisk failed in plex log-alarm-01*
in vol log-alarm
*Jan 22 05:53:31 igwb1 vxio: [ID 238951 kern.warning] WARNING: vxvm:vxio: error on Plex back-01 while writing volume back*
offset 409488 length 16
*Jan 22 05:53:31 igwb1 vxio: [ID 751920 kern.warning] WARNING: vxvm:vxio: Plex back-01 detached from volume back*
*Jan 22 05:53:31 igwb1 vxio: [ID 838567 kern.warning] WARNING: vxvm:vxio: igwbdg01-04 Subdisk failed in plex back-01 in v*
ol back
*Jan 22 05:53:31 igwb1 scsi: [ID 107833 kern.warning] WARNING: /pci@8,700000/pci@2/scsi@4/sd@0,1 (sd61):*
Jan 22 05:53:31 igwb1   Error for Command: write(10)               Error Level: Fatal
*Jan 22 05:53:31 igwb1 scsi: [ID 107833 kern.notice] Requested Block: 9650304 Error Block: 9650304*
*Jan 22 05:53:31 igwb1 scsi: [ID 107833 kern.notice] Vendor: SUN Serial Number: 276710*
C4-01
*Jan 22 05:53:31 igwb1 scsi: [ID 107833 kern.notice] Sense Key: Not Ready*
*Jan 22 05:53:31 igwb1 scsi: [ID 107833 kern.notice] ASC: 0x4 (<vendor unique code 0x4>), ASCQ: 0x1, FRU: 0x0*
*Jan 22 05:53:41 igwb1 scsi: [ID 107833 kern.warning] WARNING: /pci@8,700000/pci@2/scsi@4/sd@0,1 (sd61):*
Jan 22 05:53:41 igwb1   Error for Command: write(10)               Error Level: Fatal
*Jan 22 05:53:41 igwb1 scsi: [ID 107833 kern.notice] Requested Block: 9649406 Error Block: 9649406*
*Jan 22 05:53:41 igwb1 scsi: [ID 107833 kern.notice] Vendor: SUN Serial Number: 276710*
C4-01
*Jan 22 05:53:41 igwb1 scsi: [ID 107833 kern.notice] Sense Key: Not Ready*
*Jan 22 05:53:41 igwb1 scsi: [ID 107833 kern.notice] ASC: 0x4 (<vendor unique code 0x4>), ASCQ: 0x1, FRU: 0x0*
*Jan 22 05:53:41 igwb1 scsi: [ID 107833 kern.warning] WARNING: /pci@8,700000/pci@2/scsi@4/sd@0,1 (sd61):*
Jan 22 05:53:41 igwb1   Error for Command: write(10)               Error Level: Fatal
*Jan 22 05:53:41 igwb1 scsi: [ID 107833 kern.notice] Requested Block: 9649284 Error Block: 9649284*
*Jan 22 05:53:41 igwb1 scsi: [ID 107833 kern.notice] Vendor: SUN Serial Number: 276710*
C4-01
*Jan 22 05:53:41 igwb1 scsi: [ID 107833 kern.notice] Sense Key: Not Ready*
*Jan 22 05:53:41 igwb1 scsi: [ID 107833 kern.notice] ASC: 0x4 (<vendor unique code 0x4>), ASCQ: 0x1, FRU: 0x0*
*Jan 22 05:53:41 igwb1 vxio: [ID 238951 kern.warning] WARNING: vxvm:vxio: error on Plex front-01 while writing volume fro*
nt offset 203908 length 2
*Jan 22 05:53:41 igwb1 vxio: [ID 751920 kern.warning] WARNING: vxvm:vxio: Plex front-01 detached from volume front*
*Jan 22 05:53:41 igwb1 vxio: [ID 838567 kern.warning] WARNING: vxvm:vxio: igwbdg01-03 Subdisk failed in plex front-01 in*
vol front
*Jan 22 05:55:47 igwb1 vxdmp: [ID 912507 kern.notice] NOTICE: vxvm:vxdmp: enabled path 32/0x1e8 belonging to the dmpnode*
*274/0x28*
*Jan 22 05:55:47 igwb1 vxdmp: [ID 205910 kern.notice] NOTICE: vxvm:vxdmp: enabled dmpnode 274/0x28*
finally i tried to fsck the bad slid but it ask for super block
but it is not accept any super block in newfs -N command
moreover, i tried to repair the bad block it seem ok..but thing come up
any help please..thanks

if feel this information are not enough and you need more please show how can get it to post it.

Veritas Volume manager 4.0 with Sun StorEdge 3310 D

I am running into a problem. The vxconfigd deamon always dump core when rebooting.
Our environment is listed below.
OS environemt.
     SunOS server1 5.8 Generic_117350-43 sun4u sparc SUNW,Sun-Fire-V240
Software installed.
     Sun Cluster 3.0
     Veritas Volume Manager 4.0 MP2.
Disk Array associated.
     Sun StorEdge 3310 D.
I looked up veritas.com and find Array Support Library (ASL) for Sun StorEdge 3xxx Series is recommended. But I didn't find this library is running on this server.
Please refer to this following link
http://support.veritas.com/docs/277923
As our system is one of critical systems and I'd like to confirm that I can follow up this procedure without doing harm things to our system.
Jeff

No problem Jeff :)
I took a look at the Veritas doc and you're right it does seem to cover everthing.
Has the vxconfigd core dumped since the start? ie from the moment it was installed?
I have installed VXVM 4.0 with Solaris 8 but without the ASL and this worked ok, I know that's not much help to you but I am not sure the ASL will help. Mind you I have not installed it with Sun Cluster 3.0.

Storage 3310 RAID array as JBOD

Hi,
I have Storage 3310 RAID array. I want to use it as JBOD, half of the disks connected to
one controller channel, the other half to other controller channel.
I connected cables as it's is shown on FIGURE 4-16 (http://docs.sun.com/source/816-7290-19/ch04_cable.html#pgfId-999796)
but without expansion unit and with one host.
Seems that's not ok since disks are not recognize by format command.
There was RAID 5 was configured. I erased it. What should be configured at storage?
Thanks
Mario

AFAIK that's not the question. The question is can we convert (from a H/W standpoint) a RAID array to JBOD. And the answer is no.
You can use NRAID, but this remains a 3310 RAID array. BTW, please have a look at http://dlc.sun.com/pdf/817-3711-17/817-3711-17.pdf page 100:
"Note NRAID does not provide data redundancy. The NRAID option that appears
in some firmware menus is no longer used and is not recommended. "
Nicolas

3310 RAID + 3310 Expansion + SunFire 440 Question?

HI all, I am new here.
I just set up my first SunFire 440 database server with one 3310 RAID (12 x 36GB) controller and one EXPANSION (12 x 36GB) controller.
I am using the Ultra3 SCSI PCI card (with the most recent drivers). Updated solaris 9 patch cluster. Updated 3310 firmware (I think it is 325W or something like that) and patches. Single Bus setting where one 3310 is used for expansion and the other used for RAID. The set up is just like the "Quick Install Guide" in Single Bus setting. The two 3310 arrays were used.
Question: How do I reset each 3310 disk array config? is it the sccli "reset nvram" command?
I can only see one 3310 when I do the sccli command. It does not give me the option to select the 2nd 3310 (therefore I wasn't able to upload the new 325 firmware). I don't think my servers see it. When I run the ssconsole, it only sees one 3310. Where is my 2nd 3310? I am thinking that I messed up with the physical SCSI connections in the rear panel of the 3310 for single bus in RAID and EXPANSION setting. Can someone tell me how they set it up or tell me what I am doing worng? Or Could it be the /kernel/config (something like that) where I add the LUN number... can someone tell me what that is for? Is LUN only for FC or can SCSI use it to?
Thank you for your time.
-Tony

OKAY. Forget the question above. I found some the Configuration User Guide that will help me set up RAID and Logic Drives.
BUT I still can't see all 24 hard disk (12 hard disk on each array) using the Quick Install Guide for "Connecting Cables for Single Bus Configuration." I can see 12 hard disk on channel 0 and 6 hard disk on channel 2. When I do a show disk, I get
sccli> show disk
Ch Id Size Speed LD Status IDs Rev
0 0 33.92GB 160MB ld1 ONLINE FUJITSU MAP3367N SUN36G 0401
S/N 00N0ANJ4
0 1 33.92GB 160MB ld1 ONLINE FUJITSU MAP3367N SUN36G 0401
S/N 00N0APCR
0 2 33.92GB 160MB ld1 ONLINE FUJITSU MAP3367N SUN36G 0401
S/N 00N0APCL
0 3 33.92GB 160MB ld1 ONLINE FUJITSU MAP3367N SUN36G 0401
S/N 00N0APEE
0 4 33.92GB 160MB ld1 ONLINE FUJITSU MAP3367N SUN36G 0401
S/N 00N0APDN
0 5 33.92GB 160MB GLOBAL STAND-BY FUJITSU MAP3367N SUN36G 0401
S/N 00N0APDV
0 8 33.92GB 160MB ld0 ONLINE FUJITSU MAP3367N SUN36G 0401
S/N 00N0AP9N
0 9 33.92GB 160MB ld0 ONLINE FUJITSU MAP3367N SUN36G 0401
S/N 00N0APRC
0 10 33.92GB 160MB ld0 ONLINE FUJITSU MAP3367N SUN36G 0401
S/N 00N0APTL
0 11 33.92GB 160MB ld0 ONLINE FUJITSU MAP3367N SUN36G 0401
S/N 00N0AP85
0 12 33.92GB 160MB ld0 ONLINE FUJITSU MAP3367N SUN36G 0401
S/N 00N0APR8
0 13 33.92GB 160MB GLOBAL STAND-BY FUJITSU MAP3367N SUN36G 0401
S/N 00N0APEL
2 0 33.92GB 160MB ld2 ONLINE SEAGATE ST336607LSUN36G 0507
S/N 3JA6RJBF00007424
2 1 33.92GB 160MB ld2 ONLINE SEAGATE ST336607LSUN36G 0507
S/N 3JA29KTX00007402
2 2 33.92GB 160MB ld2 ONLINE SEAGATE ST336607LSUN36G 0507
S/N 3JA29F3G00007402
2 3 33.92GB 160MB ld2 ONLINE SEAGATE ST336607LSUN36G 0507
S/N 3JA6RKVJ00007424
2 4 33.92GB 160MB ld2 ONLINE SEAGATE ST336607LSUN36G 0507
S/N 3JA6RMEN00007425
2 5 33.92GB 160MB GLOBAL STAND-BY SEAGATE ST336607LSUN36G 0507
S/N 3JA6RK2B00007424
What happened to channel 2 hard drives 8-13??
I read on another post use command "drvconfig;devlinks;disks" but I can't find any info on that command.
Thanks.
-Tony

Sun Storedge 3310

I would like to know if it is possible to connect a sun storedge 3310 array to windows server 2012 r2? If ther is could you tell me how. I know how to do it on server 2003 but 2012 r2 is much different.

Hi,
I would like to know if it is possible to connect a sun storedge 3310 array to windows server 2012 r2?
Since we are not familiar with the product you have mentioned, I would suggest you contact corresponding vendor support to get more specific and accurate response.
Thank you for your understanding and support.
Best Regards,
Amy
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Connecting to a Sun StorEdge 3310

Hello all,
in our warehouse I've found a Sun StorEdge 3310. I want to try to use it but I do not have any kind of usefull serial cable. Also StorEdge has a LAN port but I'm not able to find a mac address to force ARP table and telnet it.
Any hint to get my storage accessible?
Thanks
Stefano
http://www.stefanocislaghi.it

Please have a look at the installation document http://docs.sun.com/app/docs/doc/816-7290-19 and feel free to get back here if you still have questions.

StorEdge 3310 RAID hung.

Similar Messages

Maybe you are looking for