Re: Missing Disk Unit - Identifying -- MIDRANGE-L

Subject: Re: Missing Disk Unit - Identifying
From: Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>
Date: Thu, 12 Dec 2019 07:37:07 -0600
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@lists.midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.lists.midrange.com>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

Larry Bolhuis already described the only potential fix. That drive has the "stiction" problem that a series of drives had for awhile. IBM furiously replaced drives within a serial number range trying to get most of them.

So, do as Larry suggests, and there's a 50/50 chance you'll get it going. I'm laying money on you replacing the drive (I'll bet Larry has a stack of them in inventory) and reloading.

Jim Oberholtzer
Agile Technology Architects

On Dec 11, 2019, at 5:18 PM, Gary Kuznitz <docfxit@xxxxxxxxxxxx> wrote:

about

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2025 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.