Strange problem creating LUNs on RAID A1000

Strange problem creating LUNs on RAID A1000

Post by Vikas Agnihotr » Sat, 14 Jun 2003 06:15:15



I am having a strange problem creating LUNs on my Sun A1000 RAID module.

raidutil -c c2t5d0 -n 0,1,2,3,4,5,6,7,8,9 -s
17275,17275,17275,17275,17275,17275,17275,17275,17275,16871  -l 5 -g
10,20,11,21,12,22,13,23,14,24,25

No existing LUNs were found on c2t5d0.

^CCapacity available in drive group:  352965760 blocks  (172346 MB).
Creating LUN 0

Registering new logical unit 0 with system.
^CFormatting logical unit 0  RAID 5   17275 MB LUNs found on c2t5d0.
  LUN 0    RAID 5    17275 MB
Creating LUN 1

Registering new logical unit 1 with system.
^CFormatting logical unit 1  RAID 5   17275 MB LUNs found on c2t5d0.
  LUN 0    RAID 5    17275 MB
  LUN 1    RAID 5    17275 MB
Creating LUN 2

Registering new logical unit 2 with system.
^CFormatting logical unit 2  RAID 5   17275 MB LUNs found on c2t5d0.
  LUN 0    RAID 5    17275 MB
  LUN 1    RAID 5    17275 MB
  LUN 2    RAID 5    17275 MB
Creating LUN 3

As you can see, it hangs after every 'Registering new logical unit ...'

Pressing 'Ctrl-C', as you can see above, jolts it into proceeding!

What is going on? Why is it* after creating each LUN?

Thanks

 
 
 

Strange problem creating LUNs on RAID A1000

Post by Vikas Agnihotr » Sat, 14 Jun 2003 11:29:12


On Thu, 12 Jun 2003 17:15:15 -0400, Vikas Agnihotri


> I am having a strange problem creating LUNs on my Sun A1000 RAID module.

Its got even worse.

# drivutil -d c2t5d0

Drives in Group for labqa_001

  Group          Drive List  [Channel,Id]

 Unassigned     [1,0]; [2,0]; [1,1]; [2,1]; [1,2]; [2,2]; [1,3]; [2,3];
[1,4]; [2,4]; [1,5]; [2,5];

drivutil succeeded!

# export disk_group="10,20,11,21,12,22,13,23,14,24,25"
# raidutil -c c2t5d0 -n 0 -s 17275  -l 5 -g $disk_group
No existing LUNs were found on c2t5d0.

It just sits there and hangs. ps -ef|grep raid shows add_disk taking CPU
time, but it just sits there.

I used to be able to create LUNs on this RAID module just yesterday. What
went wrong?

When I Ctrl-C this, things get really messed up. Even raidutil -i or -D all
or -X gives me 'Unable to open device. status = 17' errors.

Help! Thanks

 
 
 

Strange problem creating LUNs on RAID A1000

Post by gary.r.staple » Sat, 14 Jun 2003 23:30:23


how about some details regarding SOlaris version and patch level?

--
Posted via http://dbforums.com

 
 
 

Strange problem creating LUNs on RAID A1000

Post by Vikas Agnihotr » Sun, 15 Jun 2003 00:13:50


On Fri, 13 Jun 2003 14:30:23 +0000, gary.r.staples


> how about some details regarding SOlaris version and patch level?

# uname -a SunOS labqa 5.8 Generic_108528-21 sun4u sparc SUNW,Ultra-2

# pkginfo -l SUNWosar
   PKGINST:  SUNWosar
      NAME:  Open Storage Array (Root)
  CATEGORY:  system
      ARCH:  sparc
   VERSION:  06.22,REV=01.54
    VSTOCK:  06.22.01.54
    STATUS:  completely installed

 
 
 

Strange problem creating LUNs on RAID A1000

Post by Vikas Agnihotr » Tue, 17 Jun 2003 21:48:24


On Fri, 13 Jun 2003 11:13:50 -0400, Vikas Agnihotri


> On Fri, 13 Jun 2003 14:30:23 +0000, gary.r.staples

>> how about some details regarding SOlaris version and patch level?

I found the problem. There was a /tmp/mutex.add_disk file lying around
dated few days old. I guess this was from when the machine crashed or I did
 a Ctrl-C when raidutil was running or something. This was messing up the
raidutil execution.

Strange, I would have thought there was better protection against this kind
of thing happening i.e. a trap in the 'raidutil' wrapper shell script or a
/etc/init.d cleanup script when the machine reboots or something. Having
'raidutil' hang and behave erratically like this due to a silly tmp file is
so amateur-ish! Oh well...!

Thanks

 
 
 

1. Anyone with an A1000, Sol 2.6, and > 8 luns???

Before we start, let me say this "I employed as a hardware repair guy."  Part of
my employment is being able to identify hardware from software problems.  After
finding a software problem, its nice to be able to give the Software support
group a good idea where the problem may be.  Thus, I really need to know the ins
and outs of the software side of life to give the best possible service.

That being said, Here is what I found my self in.

Cust has E4500 attached to A1000

A1000 had 8 disks in it configured as 8 luns (no idea why they did that)

Cust added an additional 4 disks to the A1000.

Cust tried to create additional luns (needs patch to make it work)

Cust installed patch, modified config files, ran some script, rebooted.

Cust is now unable to manage A1000 from RM6 (no luns show)

Cust is still able to mount the previous 8 luns and access data w/o any
problems. Cust just can't manage the array anymore.

At his point I am certain that there are no hardware failures, and I send the
ticket back to the storage group for resolution.  However I am unable to give
any advice to the cust or storage group as to where the software problem may
reside.  This is something I am normally really good at.

So I ask, are there any Gotchas out there to be aware of when trying to get more
than 8 luns on an A1000/A3x00 that is already configured with 8 luns?

I did a deja search and found a few posts relating to this topic, and 1 answer
was to completely reset the array by powering down array, removing all drives
but 1, remove the battery backup, wait a few minutes, install battery backup,
power up array, Fire up RM6, start re-isntalling drives, then re-configure luns,
restore data.  Obviously this sounds a little extreme.

Thanks for any help
James

2. Kernel dive problems in Solaris 5.3

3. A1000 - Largest single LUN and Most Space Availabilty

4. fstype error when attempting to mount imported veritas file(s)

5. Rebuild A1000 LUN + Rebuild a datadg

6. FDDI on Linux?

7. RM6.22, A1000 and 32 LUNs

8. ET4000/W32 problems

9. Breaking up A1000 into one large LUN??

10. A1000 - Missing Controller info - Luns are available

11. A1000 phatom luns ?

12. A1000 cannot edit LUN after creation

13. SCSI problems with multimpel LUNs & RAID controller