18 Mar
2002
18 Mar
'02
8:05 a.m.
Date: Mon, 18 Mar 2002 10:10:09 -0600 (CST)
From: Doc Shipley <doc(a)mdrconsult.com>
To: Classic Computers <classiccmp(a)classiccmp.org>
Subject: MVII Diags Chapter 2
Sender: owner-classiccmp(a)classiccmp.org
Reply-To: classiccmp(a)classiccmp.org
OK, Friends & Neighbors.
First, I'm starting to think that the original tape is damaged. The
cptape utility suggested by Jochen seems to be Doing The Right Thing,
but gets errors. dd has no qualms at all as long as the TKZ50-GA is set
to a variable blocksize, but errors out on file #7. If I set
"conv=noerror" for dd to ignore read errors, it saws away forever at
the same file. And, if I boot the uVAX from either the original or the
one "probably good" copy [1], sometimes it sees the RD53 disks as RD51.
Not consistently. When it does, it hangs solid on a custom format.
I'll be putting the -GA on a VMS box this evening and try the VMSTPCE
copy. It makes sense to make the tape in its native OS.
[1] I did get a good set of files with the TUHS cptape. Problem is
that AFAICT the partner program, maketape, only understands 512*N
blocksizes. The diags tape has a lot of files in 80B blocks. The good
copy was made with dd, setting blocksize file by file. 82 files,
that is....
Here are a few shell scripts that might be useful. Originally run on
Ultrix 1.2 on a VaxStation II but should be more general than that.
Written for the specific purpose of investigating and duplicating
MVAX diagnostic TK50 tapes.
carl
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
#! /bin/sh
# This is a shell archive, meaning:
# 1. Remove everything above the #! /bin/sh line.
# 2. Save the resulting text in a file.
# 3. Execute the file with /bin/sh (not csh) to create the files:
# tapemap.sh
# read_tape.sh
# write_tape.sh
# This archive created: Tue Jan 5 08:21:44 1993
export PATH; PATH=/bin:$PATH
echo shar: extracting "'tapemap.sh'" '(161 characters)'
if test -f 'tapemap.sh'
then
echo shar: will not over-write existing file "'tapemap.sh'"
else
sed 's/^X//' << \SHAR_EOF > 'tapemap.sh'
X#!/bin/sh
Xwhile :
Xdo
Xdd if=/dev/nrmt0 cbs=80 conv=unblock >>logfile
Xdd if=/dev/nrmt0 of=/dev/null 2>>logfile
Xdd if=/dev/nrmt0 cbs=80 conv=unblock >>logfile
Xdone
SHAR_EOF
if test 161 -ne "`wc -c < 'tapemap.sh'`"
then
echo shar: error transmitting "'tapemap.sh'" '(should have been 161
characters)'
fi
chmod +x 'tapemap.sh'
fi # end of overwriting check
echo shar: extracting "'read_tape.sh'" '(356 characters)'
if test -f 'read_tape.sh'
then
echo shar: will not over-write existing file "'read_tape.sh'"
else
sed 's/^X//' << \SHAR_EOF > 'read_tape.sh'
X#!/bin/sh
X# read_tape.sh
X# read MicroVax diagnostic tape into an assortment of files
X#
Xdir=/data
Xtape=/dev/nrmt0
X
Xmkdir $dir/hdr
Xmkdir $dir/txt
Xmkdir $dir/eof
X
Xmt -f /dev/rmt0 rew
Xi=1
Xwhile [ "$i" -le 108 ]
Xdo
X dd if=$tape bs=80 of=$dir/hdr/$i
X dd if=$tape bs=512 of=$dir/txt/$i
X dd if=$tape bs=80 of=$dir/eof/$i
X i=`expr $i + 1`
Xdone
X
Xmt -f /dev/rmt0 rew
SHAR_EOF
if test 356 -ne "`wc -c < 'read_tape.sh'`"
then
echo shar: error transmitting "'read_tape.sh'" '(should have been
356 characters)'
fi
chmod +x 'read_tape.sh'
fi # end of overwriting check
echo shar: extracting "'write_tape.sh'" '(348 characters)'
if test -f 'write_tape.sh'
then
echo shar: will not over-write existing file "'write_tape.sh'"
else
sed 's/^X//' << \SHAR_EOF > 'write_tape.sh'
X#!/bin/sh
X# write_tape.sh
X# write MicroVax diagnostic tape from an assortment of files
X#
Xdir=.
Xtape=/dev/nrmt0
X
Xmt -f /dev/rmt0 rew
Xi=1
Xwhile [ "$i" -le 108 ]
Xdo
X echo " file $i"
X dd of=$tape bs=80 if=$dir/hdr/$i
X dd of=$tape bs=512 if=$dir/txt/$i
X dd of=$tape bs=80 if=$dir/eof/$i
X i=`expr $i + 1`
Xdone
Xmt -f $tape weof 2
Xmt -f /dev/rmt0 rew
X
SHAR_EOF
if test 348 -ne "`wc -c < 'write_tape.sh'`"
then
echo shar: error transmitting "'write_tape.sh'" '(should have been
348 characters)'
fi
chmod +x 'write_tape.sh'
fi # end of overwriting check
# End of shell archive
exit 0
18 Mar
18 Mar
10:16 a.m.
Wow, so that goes without the cptape program. The power of UNIX
shell scripting :-). But once you have the cptape copy, it's a
one-liner sed command to convert the log file in a series of dd
calls to write the stuff back, including the 80 byte blocks.
Of course, that doesn't fix your broken source tape.
regards
-Gunther
--
Gunther Schadow, M.D., Ph.D. gschadow(a)regenstrief.org
Medical Information Scientist Regenstrief Institute for Health Care
Adjunct Assistant Professor Indiana University School of Medicine
tel:1(317)630-7960 http://aurora.regenstrief.org
10:52 a.m.
On Mon, 18 Mar 2002, Gunther Schadow wrote:
Wow, so that goes without the cptape program. The
power of UNIX
shell scripting :-). But once you have the cptape copy, it's a
one-liner sed command to convert the log file in a series of dd
calls to write the stuff back, including the 80 byte blocks.
No, I used cptape to get the files off the original, just a really
crufty script to put 'em back. And I have a brand new sed & awk
O'Reilly text sitting in the den.
Of course, that doesn't fix your broken source
tape.
I dunno if the source tape is broken. I don't have any verified good
eqipment to test with it... I think the SCSI TK50 was the problem. I
do know that I have a problem with the RQDX3 board, or the distribution
board, or a cable. The fact that the MFM formatter was hanging led me
to think the Diags were busted, but further testing with both tapes says
that the RQDXA is failing. Bah!
Doc
8:25 p.m.
Doc wrote:
On Mon, 18 Mar 2002, Gunther Schadow wrote:
BTW: any ida why mine barks at me I had disabled my MFM drive? The
RQDX3 passes the test fine, but doesn't detect any devices. I think
I put the cables together fine and checked that today. I see the
RX50 floppy react normally in terms of signalling write protect
on the console if I stick a write protected floppy in. But the
MFM drive does not have its LED lit and never seems to seek or do
anything other than spinning. Is that normal? Are there jumpers
to take care of? (That drive came from some old SUN.)
-Gunther
--
Gunther Schadow, M.D., Ph.D. gschadow(a)regenstrief.org
Medical Information Scientist Regenstrief Institute for Health Care
Adjunct Assistant Professor Indiana University School of Medicine
tel:1(317)630-7960 http://aurora.regenstrief.org
Wow, so that goes without the cptape program. The
power of UNIX
shell scripting :-). But once you have the cptape copy, it's a
one-liner sed command to convert the log file in a series of dd
calls to write the stuff back, including the 80 byte blocks.
No, I used cptape to get the files off the original, just a really
crufty script to put 'em back. And I have a brand new sed & awk
O'Reilly text sitting in the den.
Of course, that doesn't fix your broken source
tape.
I dunno if the source tape is broken. I don't have any verified good
eqipment to test with it... I think the SCSI TK50 was the problem. I
do know that I have a problem with the RQDX3 board, or the distribution
board, or a cable. The fact that the MFM formatter was hanging led me
to think the Diags were busted, but further testing with both tapes says
that the RQDXA is failing. Bah!
19 Mar
19 Mar
5:07 a.m.
New subject: offline drives: Re: MVII Diags Chapter 2
On Tue, 19 Mar 2002, Gunther Schadow wrote:
BTW: any ida why mine barks at me I had disabled my
MFM drive? The
RQDX3 passes the test fine, but doesn't detect any devices. I think
I put the cables together fine and checked that today. I see the
RX50 floppy react normally in terms of signalling write protect
on the console if I stick a write protected floppy in. But the
MFM drive does not have its LED lit and never seems to seek or do
anything other than spinning. Is that normal? Are there jumpers
to take care of? (That drive came from some old SUN.)
Gunther,
I don't know, but I think I'm missing something too. Do the diags
just show a dead drive as "offline"?
I put the original RD54 back in as drive 0 and no longer get the RQDXA
errors from the diags, but both drives 1&2, RD53s, are showing as
offline RD51s. What's up with that?
Doc
6:19 a.m.
New subject: offline drives: Re: MVII Diags Chapter 2
Doc wrote:
I don't know, but I think I'm missing
something too. Do the diags
just show a dead drive as "offline"?
I put the original RD54 back in as drive 0 and no longer get the RQDXA
errors from the diags, but both drives 1&2, RD53s, are showing as
offline RD51s. What's up with that?
Cable is twisted ?
cheers
8:34 a.m.
New subject: offline drives: Re: MVII Diags Chapter 2
emanuel stiebler wrote:
Doc wrote:
Unlikely. The cables (at least in my small uVAX-11 cabinet) the
cables run fairly straight and it's obvious which way they are
plugged in.
Doc, to be sure, is your diagnostics showing any drive type?
You say "offline RD51". Mine is just saying "offline" and does not
say anything about "RD51" or whatever. If yours does, you are
better off than me.
We now know that all drives have to be jumpered #3, the only question
is now, what jumpers have to be plugged for this to be done right
with my drive (and I don't even know the exact type, blush :-) It's
a Micropolis, but don't see any identification other than a lengthy
part #.
regards,
-Gunther
--
Gunther Schadow, M.D., Ph.D. gschadow(a)regenstrief.org
Medical Information Scientist Regenstrief Institute for Health Care
Adjunct Assistant Professor Indiana University School of Medicine
tel:1(317)630-7960 http://aurora.regenstrief.org
I don't know, but I think I'm missing
something too. Do the diags
just show a dead drive as "offline"?
I put the original RD54 back in as drive 0 and no longer get the RQDXA
errors from the diags, but both drives 1&2, RD53s, are showing as
offline RD51s. What's up with that?
Cable is twisted ?
9:24 a.m.
New subject: offline drives: Re: MVII Diags Chapter 2
Gunther Schadow wrote:
emanuel stiebler wrote:
But you're not talking about a BA23. And that's where your surprise
would be ;-)
cheers
Cable is twisted ?
Unlikely. The cables (at least in my small uVAX-11 cabinet) the
cables run fairly straight and it's obvious which way they are
plugged in.
11:35 a.m.
New subject: offline drives: Re: MVII Diags Chapter 2
emanuel stiebler wrote:
Gunther Schadow wrote:
I think I do (I can never memorize the BA-xxx numbers.) Now,
what do you mean by "that's where your surprize would be" and
the smile? Do you know the secret to my problem?
regards
-Gunther
--
Gunther Schadow, M.D., Ph.D. gschadow(a)regenstrief.org
Medical Information Scientist Regenstrief Institute for Health Care
Adjunct Assistant Professor Indiana University School of Medicine
tel:1(317)630-7960 http://aurora.regenstrief.org
emanuel stiebler wrote:
But you're not talking about a BA23. And that's where your surprise
would be ;-) Cable is twisted ?
Unlikely. The cables (at least in my small uVAX-11 cabinet) the
cables run fairly straight and it's obvious which way they are
plugged in.
20 Mar
20 Mar
5:13 a.m.
New subject: offline drives: Re: MVII Diags Chapter 2
Gunther Schadow wrote:
I think I do (I can never memorize the BA-xxx numbers.) Now,
what do you mean by "that's where your surprize would be" and
the smile? Do you know the secret to my problem?
It is twisted. It is not like you think it should be.
(coming flat from the drives & then to the controller). And if it is
connect the wrong way, suddenly your one RD54 shows up as many RD53,
or RD51, ...
cheers
8161
days inactive
8163
days old
9 comments
4 participants
participants (4)
-
cdl＠proxima.ucsd.edu -
doc＠mdrconsult.com -
emu＠ecubics.com -
gunther＠aurora.regenstrief.org