[SunHELP] SDS 4.2.1 problem ... not solved ...

[Michael Karl]

Hi,

first of all I restored the boot-disc with solaris 2.6 with the networker
and the system is running.

The metadevice "d10 2 3 c2t5d0s0 c2t5d1s0 c2t5d3s0 -i 32b 1 c2t5d2s6" works
under Solaris 2.6 with DiskSuite-Online 4.1.x?x.

But now some more informations about my real problem:

The CMD-Raid-5500-System has three RAID-Sets with identical drives.

These RAID-Sets have also identical numbers of blocks.
(c4t5d0d0 c4t5d1s0 c4t5d3s0)

Only the fourth RAID-Set (c4t5d2s6) is newer ... bigger discs and number of
blocks.

*** The history ***

Some years ago this RAID has an old CMD-5000-Controller with three
host-channels. Years ago somebody had decided to make a DiskSuite-Online
stripped metadevice like "d10 2 3 c2t5d0s0 c2t5d1s0 c2t5d3s0 -i 32b".

Two years ago the CMD5000 died ... also the fourth RAID-Set with very small
discs. The CMD5000 was replaced by a CMD5500 and the fourth RAID-Set was
recreated with bigger discs. This fourth RAID-Set was attached to the
metadevice d10 as a concentration.

*** End of history ***

After the Solaris-2.6-boot-disc-crash I've installed the preconfigured
Solaris-8-disc with SDS 4.2.1, I modified the "/kernel/drv/sd.conf" with
additional lun-entiries. With "format" I saw all RAID-Sets as normal
scsi-discs. All entries for the three equal RAID-Sets are the same.
Only the fourth is bigger.

But then I wasn't able to create a metadevice in concentration or stripe
(with option -n / no creation - only checking for syntax).

Very mythical: I was able to create a stripe with lun1 and lun3 (equal
RAID-Sets) and could also make a concentration with lun2 (the big one).

Example: metainit -n d10 2 2 c4t5d1s0 c4t5d3s0 -i 32b 1 c4t5d2s6
                                  ^=lun1   ^=lun3            ^=lun3

But every experiment in using lun0 (c4t5d0d0) in any combination of stripe
or concentration in a metadevice with option "-n" ends with the error
message:

metainit: LexCOM: c4t5d1s0: overlaps with device in d10

For myself I have to solve this problem, because I must upgrade several UE2
and UE450-systems with Solaris 2.5.1 and 2.6 to 8 in the near future, which
have also concentrated or stripped metadevices with discs or RAID-Sets.

Has anybody any idea in this sun world ?

Thanx Michael
Sorry ... about my english ;-)


 
> Von: Michael Karl <mk at lexcom-net.de>
> Antworten an: sunhelp at sunhelp.org
> Datum: Thu, 23 Aug 2001 22:50:14 +0200
> An: <sunhelp at sunhelp.org>
> Betreff: [SunHELP] SDS 4.2.1 problem ... very big problem
> 
> Hey all,
> 
> on a solaris 2.6 machine the boot-disc crashed.
> I decided to take a preconfigured Solaris-8-disc with SDS 4.2.1,
> because I haven't a complete Solaris 2.6 CD-Set at the moment.
> 
> The orginal SDS 4.1 configuration:
> 
> # more md.cf
> # metadevice configuration file
> # do not hand edit
> d10 2 3 c2t5d0s0 c2t5d1s0 c2t5d3s0 -i 32b \
> 1 c2t5d2s6
> #
> I've restored this information via legato networker.
> 
> The target 5 is an CMD-raid-system which had growed two years ago via
> growfs.
> 
> In the Solaris 8 configuration the controller-ID changed ...
> now it's the 4th controller.
> 
> I tried to configure the d10-metadevice with following command:
> 
> metainit -n d10 2 3 c4t5d0d0 c4t5d1s0 c4t5d3s0 -i 32b 1 c4t5d2s6
> 
> and got following error-message:
> 
> metainit: LexCOM: c4t5d1s0: overlaps with device in d10
> 
> any ideas ????
> 
> Thanx Michael
> 
> 
> _______________________________________________
> SunHELP maillist  -  SunHELP at sunhelp.org
> http://www.sunhelp.org/mailman/listinfo/sunhelp