|
On Dec 10, 2016, at 1:27 PM, Mark S Waterbury <mark.s.waterbury@xxxxxxxxxxxxx> wrote:
Hi, All:
Someone I know is on-site this week-end trying to help a customer whose Advanced 36 *M36 running SSP 7.5 on a 170 is having a problem -- apparently a bad sector or block on the (virtualized) disk -- causing the nightly back-up to HALT with an error when it gets to the step where it wants to back up one particular library, which apparently contains a bad block or sector ...
I seem to recall there was a service aid or tool or procedure to mark a block or sector as "bad" to allow the system to be able to skip over the bad sector, so the back-up can then run to completion...
But, my expertise is very limited on SSP.
Can you recall how you might approach resolving such a problem?
From looking at some S/36 manuals, it appears that the BUILD procedure or the PATCH procedure might help?
Thanks in advance for any suggestions ...
Mark
--
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.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
