Re: Configuring disk for self maintenance.

Of those steps ONLY the STOP RAID step requires DST. And it's not 'Remove from RAID' in this case you need to STOP RAID. Don't let that scare you as it will let you select which RAID sets to stop, it doesn't stop them all. So do your discovery first to know which RAID set(s) to stop. Because there is no data on them it will stop very quickly as well.

Once the stop is done all those disks will be non-configured and un-protected. You can then IPL back to IBM i and jump back into SST to do the hot sparing and start RAID etc.

Yes you ARE Correct about doing everything in SST removing the potential IPL if you want IFS in the ASP. *OR* you could make it an iASP and now you have more flexibility and no requirement for an IPL.

The Start RAID will take a fair bit of time even with SSDs, like 'more than an hour' as it does write 'em full of naughts.

- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 7/24/2017 1:45 PM, Rob Berendt wrote:

Removing disks 2-30 from the ASP ran from 7:43 until 12:33 or almost 5
hours. All SSD's. Completed while the system was active.

Now the old disks show as non configured.

<snip>
Now the bad news is that to end RAID you'll need to IPL to DST.
</snip>
I was kind of hoping that was as obsolete as some of the other stuff the
knowledge center was saying.

So, if I wanted to get this done with only one more IPL I would need to:
IPL to DST (I'll call this a half IPL)
Remove units from RAID
Start hot sparing on my selected disks
Create raid sets.
Create new ASP for old disk units.
IPL out of DST (I'll call this the second half of the IPL).

Doing the ASP while still in DST will cut out any IPL needed in case I
wanted some IFS on this new ASP.

I wonder how long that will take?

I do not think I will attempt moving the load/source from D2 to D1. Some
risk for very little gain.




Rob Berendt