Well congrats on the progress!! A LOT of work but very interesting to follow your progress!

If you've got the thing happily running in DST with the RAID set fully operational then replacing the failing LS drive isn't hard. In service tool Start a Service Tool, Hardware Service Manager, Device Concurrent Maintenance. Enter the DD number for the Load source, and Remove. When the LED Flashes, yank it out. This will immediately indicate a device failure as you will expect. Load up a new drive and use the same option to install the new drive. Then in Work with Disk Units use the option to Rebuild Disk Unit Data. On those 8G Drives it should be less than 1/2 hour to rebuild the drive.

- Larry "DrFranken" Bolhuis

On 4/22/2012 11:11 PM, Jim Donoghue wrote:
Here is what I have done:

1. Reclaim IOP Cache Storage
2. Next IPL it wants to Reclaim IOP Cache Storage again, and makes me
clear the ASP.
3. IPL again. This time, it informs me that I need to reinstall the
operating system (as expected)
4. Power down from the DST menu (start service tool->control panel->F10)
5. Restore all seven drives from the disk image files
6. Install drives back in the 720, try a 'B M' IPL.

It worked.

I've had enough 'Fun with Disks' for the weekend. Next block of free
time I need to develop a plan for replacing the load source drive
that's going bad.


On 4/22/12, Roberto José Etcheverry Romero<yggdrasil.raiker@xxxxxxxxx> wrote:
AFAIK they are more than enclosures, since most of them are
concurrent-maintenance-compatible. That means that the SST/DST
commands that slot to poweroff so you take the drive and replace it
(never understood why they never went hot-swap).
It may or may not work as a simple enclosure on a standard controller.
But then again i didnt think you could access the 522byte sectors
either...

Best regards,


On Sun, Apr 22, 2012 at 2:15 PM, Jim Donoghue<jdonoghue04@xxxxxxxxx> wrote:
On 4/22/12, Roberto José Etcheverry Romero<yggdrasil.raiker@xxxxxxxxx>
wrote:
It wants to clear the ASP because the numerous incongruencies lead it
to believe faulty. Dont blame it. It wasnt meant to be tinkered in
this way.
You could clear the ASP, stop the parity and reclaim cache, that way
the controller would be virgin and if you re-image the drives it
should work (after a LONG time)...

Best regards,


I'll give that a try. It takes almost four hours to re-image those
drives, and my test setup only allows me to do one drive at a time. If
I have to keep doing this, I'm going to figure out how to connect one
of the units that the disks go into to the PC, so I can set it up to
re-image five drives at once.

Jim
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].