We have an E450 machine with Solaris 8 en Raidmanager 6.22.1 installed. Also
the required patches are there. We hooked up an A1000 Storage array with 1
SCSI kabel on the machine. Terminator is present. We also did the required
firmware updates.
The A1000 was completely reset by doing a sysWipe ans sysReboot on the A1000
console.

Nothing wrong at this moment. The problem comes when we are trying to create
a new LUN on this A1000:

#raidutil -c c5t0d0 -n 1 -l 1 -s 17234 -g 15,25
LUNs found on c5t0d0.
LUN 0 RAID 0 10 MB
Capacity available in drive group: 35296512 blocks (17234 MB).
Creating LUN 1

Registering new logical unit 1 with system.

Can't open device 1T03843494:1 status = 8. Aborting


raidutil failed!
No disks found!

After this command the A1000 is not accessible anymore. For every raiduitil
command we get the same "Can't open device" error (for example raidutil -c
c5t0d0 -i). Also heathcheck is telling "Unable to scan module..".
Only if we issue a sysWipe again on the A1000 console we are back in
business (until we try to create a LUN again). We tried another A1000,
reboot the system with or without -r etc with the same result.

Does anyone have seen this before or know the solution for this problem ?

regards,
John

JBR wrote:
> We have an E450 machine with Solaris 8 en Raidmanager 6.22.1 installed. Also
> the required patches are there. We hooked up an A1000 Storage array with 1
> SCSI kabel on the machine. Terminator is present. We also did the required
> firmware updates.
> The A1000 was completely reset by doing a sysWipe ans sysReboot on the A1000
> console.
>
> Nothing wrong at this moment. The problem comes when we are trying to create
> a new LUN on this A1000:
>
> #raidutil -c c5t0d0 -n 1 -l 1 -s 17234 -g 15,25
> LUNs found on c5t0d0.
> LUN 0 RAID 0 10 MB
> Capacity available in drive group: 35296512 blocks (17234 MB).
> Creating LUN 1
>
> Registering new logical unit 1 with system.
>
> Can't open device 1T03843494:1 status = 8. Aborting
>
>
> raidutil failed!
> No disks found!
>
> After this command the A1000 is not accessible anymore. For every raiduitil
> command we get the same "Can't open device" error (for example raidutil -c
> c5t0d0 -i). Also heathcheck is telling "Unable to scan module..".
> Only if we issue a sysWipe again on the A1000 console we are back in
> business (until we try to create a LUN again). We tried another A1000,
> reboot the system with or without -r etc with the same result.
>
> Does anyone have seen this before or know the solution for this problem ?
>
> regards,
> John
>
>
>

I don't have that much experience with A1000's also, but as I recall
luns are created on a module. So I think first you need to define a
module name or purhapse there already is a module. What happens if you
try to create a lun using the gui, rm6?

JBR <jbrattinga_verwijderdit@home.nl> wrote:
> We have an E450 machine with Solaris 8 en Raidmanager 6.22.1 installed. Also
> the required patches are there. We hooked up an A1000 Storage array with 1
> SCSI kabel on the machine. Terminator is present. We also did the required
> firmware updates.
> The A1000 was completely reset by doing a sysWipe ans sysReboot on the A1000
> console.

You should _never_ use the serial interface to the A1000's. It is not
supported for customer use (or for that matter, by Sun engineers who
haven't been specifically trained in using it), and is probably the best
way to completly toast an array - even if all that you're trying to do
is to clear the config!

> Registering new logical unit 1 with system.
>
> Can't open device 1T03843494:1 status = 8. Aborting

Does your /kernel/drv/sd.conf have an entry for LUN 1 on whatever target
you're using?

Scott

"Frank" <no@spam.nl> wrote in message
news:3fee081b$0$127$e4fe514c@dreader8.news.xs4all. nl...
> JBR wrote:
> > We have an E450 machine with Solaris 8 en Raidmanager 6.22.1 installed.
Also
> > the required patches are there. We hooked up an A1000 Storage array with
1
> > SCSI kabel on the machine. Terminator is present. We also did the
required
> > firmware updates.
> > The A1000 was completely reset by doing a sysWipe ans sysReboot on the
A1000
> > console.
> >
> > Nothing wrong at this moment. The problem comes when we are trying to
create
> > a new LUN on this A1000:
> >
> > #raidutil -c c5t0d0 -n 1 -l 1 -s 17234 -g 15,25
> > LUNs found on c5t0d0.
> > LUN 0 RAID 0 10 MB
> > Capacity available in drive group: 35296512 blocks (17234 MB).
> > Creating LUN 1
> >
> > Registering new logical unit 1 with system.
> >
> > Can't open device 1T03843494:1 status = 8. Aborting
> >
> >
> > raidutil failed!
> > No disks found!
> >
> > After this command the A1000 is not accessible anymore. For every
raiduitil
> > command we get the same "Can't open device" error (for example
raidutil -c
> > c5t0d0 -i). Also heathcheck is telling "Unable to scan module..".
> > Only if we issue a sysWipe again on the A1000 console we are back in
> > business (until we try to create a LUN again). We tried another A1000,
> > reboot the system with or without -r etc with the same result.
> >
> > Does anyone have seen this before or know the solution for this problem
?
> >
> > regards,
> > John
> >
> >
> >
>
> I don't have that much experience with A1000's also, but as I recall
> luns are created on a module. So I think first you need to define a
> module name or purhapse there already is a module. What happens if you
> try to create a lun using the gui, rm6?
>

The module is already there.
If we try the GUI we get the same problem.

"Scott Howard" <scott@hunterlink.net.au> wrote in message
news:1072598404.999196@docbert...
> JBR <jbrattinga_verwijderdit@home.nl> wrote:
> > We have an E450 machine with Solaris 8 en Raidmanager 6.22.1 installed.
Also
> > the required patches are there. We hooked up an A1000 Storage array with
1
> > SCSI kabel on the machine. Terminator is present. We also did the
required
> > firmware updates.
> > The A1000 was completely reset by doing a sysWipe ans sysReboot on the
A1000
> > console.
>
> You should _never_ use the serial interface to the A1000's. It is not
> supported for customer use (or for that matter, by Sun engineers who
> haven't been specifically trained in using it), and is probably the best
> way to completly toast an array - even if all that you're trying to do
> is to clear the config!
>
> > Registering new logical unit 1 with system.
> >
> > Can't open device 1T03843494:1 status = 8. Aborting
>
> Does your /kernel/drv/sd.conf have an entry for LUN 1 on whatever target
> you're using?
>
> Scott

In the file /kernel/drv/sd.conf there is:

# BEGIN RAID Manager additional lun entries
# DO NOT EDIT from BEGIN above to END below...
name="sd" class="scsi" target=4 lun=1;
name="sd" class="scsi" target=4 lun=2;
name="sd" class="scsi" target=4 lun=3;
name="sd" class="scsi" target=4 lun=4;
name="sd" class="scsi" target=4 lun=5;
name="sd" class="scsi" target=4 lun=6;
name="sd" class="scsi" target=4 lun=7;
name="sd" class="scsi" target=5 lun=1;
name="sd" class="scsi" target=5 lun=2;
name="sd" class="scsi" target=5 lun=3;
name="sd" class="scsi" target=5 lun=4;
name="sd" class="scsi" target=5 lun=5;
name="sd" class="scsi" target=5 lun=6;
name="sd" class="scsi" target=5 lun=7;
# END RAID Manager additional lun entries

I tried different LUN numbers (1,3,5). Target is 5.

JBR wrote:
> "Scott Howard" <scott@hunterlink.net.au> wrote in message
> news:1072598404.999196@docbert...
>
>>JBR <jbrattinga_verwijderdit@home.nl> wrote:
>>
>>>We have an E450 machine with Solaris 8 en Raidmanager 6.22.1 installed.
>
> Also
>
>>>the required patches are there. We hooked up an A1000 Storage array with
>
> 1
>
>>>SCSI kabel on the machine. Terminator is present. We also did the
>
> required
>
>>>firmware updates.
>>>The A1000 was completely reset by doing a sysWipe ans sysReboot on the
>
> A1000
>
>>>console.
>>
>>You should _never_ use the serial interface to the A1000's. It is not
>>supported for customer use (or for that matter, by Sun engineers who
>>haven't been specifically trained in using it), and is probably the best
>>way to completly toast an array - even if all that you're trying to do
>>is to clear the config!
>>
>>
>>>Registering new logical unit 1 with system.
>>>
>>>Can't open device 1T03843494:1 status = 8. Aborting
>>
>>Does your /kernel/drv/sd.conf have an entry for LUN 1 on whatever target
>>you're using?
>>
>> Scott
>
>
> In the file /kernel/drv/sd.conf there is:
>
> # BEGIN RAID Manager additional lun entries
> # DO NOT EDIT from BEGIN above to END below...
> name="sd" class="scsi" target=4 lun=1;
> name="sd" class="scsi" target=4 lun=2;
> name="sd" class="scsi" target=4 lun=3;
> name="sd" class="scsi" target=4 lun=4;
> name="sd" class="scsi" target=4 lun=5;
> name="sd" class="scsi" target=4 lun=6;
> name="sd" class="scsi" target=4 lun=7;
> name="sd" class="scsi" target=5 lun=1;
> name="sd" class="scsi" target=5 lun=2;
> name="sd" class="scsi" target=5 lun=3;
> name="sd" class="scsi" target=5 lun=4;
> name="sd" class="scsi" target=5 lun=5;
> name="sd" class="scsi" target=5 lun=6;
> name="sd" class="scsi" target=5 lun=7;
> # END RAID Manager additional lun entries
>
> I tried different LUN numbers (1,3,5). Target is 5.
>
>
In your original posting you cited device "c5t0d0".
The "t" or target portion of that device is 0 (zero)
not 5 as stated above. Try adding entries in sd.conf
for target 0.

Byron

JBR <jbrattinga_verwijderdit@home.nl> wrote:
>> Does your /kernel/drv/sd.conf have an entry for LUN 1 on whatever target
>> you're using?
>>
> # BEGIN RAID Manager additional lun entries
> # DO NOT EDIT from BEGIN above to END below...
> name="sd" class="scsi" target=4 lun=1;
[...]
> name="sd" class="scsi" target=5 lun=1;
[...]
> # END RAID Manager additional lun entries
>
> I tried different LUN numbers (1,3,5). Target is 5.

No, your _controller_ is 5, your target is 0. From your original post :
> raidutil -c c5t0d0 -n 1 -l 1 -s 17234 -g 15,25
> LUNs found on c5t0d0.

Controller 5, target 0. Either change the A1000 to target 5 (which is the
normal default for them) or add some additional entries to sd.conf for
target=0 lun=1 to lun=7

Scott.

"Byron E. Myers" <byronmyers@gbronline.com> wrote in message
news:l6-dnXBfyu22022iRVn-gQ@gbronline.com...
>
>
> JBR wrote:
> > "Scott Howard" <scott@hunterlink.net.au> wrote in message
> > news:1072598404.999196@docbert...
> >
> >>JBR <jbrattinga_verwijderdit@home.nl> wrote:
> >>
> >>>We have an E450 machine with Solaris 8 en Raidmanager 6.22.1 installed.
> >
> > Also
> >
> >>>the required patches are there. We hooked up an A1000 Storage array
with
> >
> > 1
> >
> >>>SCSI kabel on the machine. Terminator is present. We also did the
> >
> > required
> >
> >>>firmware updates.
> >>>The A1000 was completely reset by doing a sysWipe ans sysReboot on the
> >
> > A1000
> >
> >>>console.
> >>
> >>You should _never_ use the serial interface to the A1000's. It is not
> >>supported for customer use (or for that matter, by Sun engineers who
> >>haven't been specifically trained in using it), and is probably the best
> >>way to completly toast an array - even if all that you're trying to do
> >>is to clear the config!
> >>
> >>
> >>>Registering new logical unit 1 with system.
> >>>
> >>>Can't open device 1T03843494:1 status = 8. Aborting
> >>
> >>Does your /kernel/drv/sd.conf have an entry for LUN 1 on whatever target
> >>you're using?
> >>
> >> Scott
> >
> >
> > In the file /kernel/drv/sd.conf there is:
> >
> > # BEGIN RAID Manager additional lun entries
> > # DO NOT EDIT from BEGIN above to END below...
> > name="sd" class="scsi" target=4 lun=1;
> > name="sd" class="scsi" target=4 lun=2;
> > name="sd" class="scsi" target=4 lun=3;
> > name="sd" class="scsi" target=4 lun=4;
> > name="sd" class="scsi" target=4 lun=5;
> > name="sd" class="scsi" target=4 lun=6;
> > name="sd" class="scsi" target=4 lun=7;
> > name="sd" class="scsi" target=5 lun=1;
> > name="sd" class="scsi" target=5 lun=2;
> > name="sd" class="scsi" target=5 lun=3;
> > name="sd" class="scsi" target=5 lun=4;
> > name="sd" class="scsi" target=5 lun=5;
> > name="sd" class="scsi" target=5 lun=6;
> > name="sd" class="scsi" target=5 lun=7;
> > # END RAID Manager additional lun entries
> >
> > I tried different LUN numbers (1,3,5). Target is 5.
> >
> >
> In your original posting you cited device "c5t0d0".
> The "t" or target portion of that device is 0 (zero)
> not 5 as stated above. Try adding entries in sd.conf
> for target 0.
>
> Byron
>

This was indeed the right solution. After adding target 0 it works fine.
Thanks for pointing me in the right direction.

John