said:
>
> Hi,
>
> Happy post New Year...
Same to you and all our OS/2/eCS brethren.
> >> You might try using /!BM or /GBM. You can apply these to either th
> >> adapter or the unit. See Dani506.doc.
>
> >No joy. Neither parameter alters the non-appearance of the drive in
> >either the volume manager or DFS.
>
> You'll save yourself some time by checking the Danis506 output first. If
> the drive is not visible to Dani506, it's not going to be visible to the
> upper level components.
Appently even if Dani506 is employed instead of ibm1s506, copy ibms506$ con
will work. Nice to know :-).
> That sort of implies that danis506 sees the drive and then decides it
> can't be used because it's not responding properly. How ibm1s506 dies is
> a bit irrelevant, since this is a case of GIGO. However, it is another
> data point.
Understood and agreed.
> >stuff there that is non-recoverable (I know, I know ... backup but then
> >this is one of the youngest drives in a pretty lightly used machine ...
> >who'da thunk it?).
>
> Well, think back on what you learned in your probability classes. There's
> also the Murphy rule, which IIRC is taught in the class that covers fault
> tree analysis.
Well, you know, I've always found it amusing to run up theory against
empiricism (or what amounts to folksy aphorism in this case). Murphy's number
1 law, "if something can go wrong, it will" usually matches up well on the
basis that increasing opportunity for fault (greatly) increases likelihood of
fault (greatly). However, reliability calculations (particularly MTBF-type
ones with which hard drive failure is modeled) suggests that the largest drive
currently in my active use, and hence the youngest is much more likely to be
just fine rather than the 10 or so drives that range from 1 to 10 GB that are
in near constant use here. Of course, we also learned about independence and
outliers :-). But enough theory and philosophy.
> A couple of more things to try. Try /!BIOS with Danis506. Try the dfsee
> bootable CD and select the low performance drivers. This will effectively
> use the BIOS to access the drive.
Here's where it got kind of interesting. I used the /!BIOS parameter (along
with /W to be able to inspect the output at boot) and got no change in
behavior. However, just for grins, I downloaded the latest Danis506 (1.8.1) to
update the 1.2MR stock 1.7.4 and I upgraded the driver in place (i.e. to keep
the same parameter settings)) and behavior changed slightly, not necessarily
well. On the good side, the new Danis506 recognized and spit out the correct
drive parameters for this ailing slave drive in addition to the boot drive. On
the bad side, after acknowledging the paused output, the machine goes into a
funk that it does not come out of. Specifically, the machine begins emitting
single beeps out of the system speaker separated by pauses of about 5 seconds.
It beeps about 4 times and then hangs permanently. I would have said that they
sound like system error beeps but in the past, I"ve only heard these during
POST, never in the middle of boot up. I have to change back to the earlier
Danis506 to recover.
I'm encouraged that Danis finally saw the drive, but the following behavior is
discoiuraging. I guess I expect that I am hosed. Any thoughts? Thanks again
in advance.
> Steven
-Rocky
=====================================================
To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".
For problems, contact the list owner at
"postmaster@scoug.com".
=====================================================
>> Next Message >>
Return to [ 09 |
January |
2008 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International
Business Machines Corporation.
All other trademarks remain the property of their respective owners.
