On Tue, 20 May 2014, Paul_Koning at Dell.com wrote:
The disk is 1048778 blocks. I created a 512M image and copied it bit-for-bit to the disk. I think i'll just go SYSGEN 4.8 and wait for my cleaning tapes to get RSTS/E working.
How about copying the image back off, to see if the disk controller mangled it?
I'll do that once RSX is up so I don't have to dismantle the system again. ;)
The message you quoted says that the content of block 1 is invalid (the pack label). Judging by the code, what it found is 0143161 rather than a valid PCS.
Interesting. I wonder how its getting mangled. The disk size IS changing between copy and creation, though. (Because both are different...apparently unavoidable due to 1000 versus 1024k.)
I wonder if your partitioning disk controller is misbehaving.
Possible...but RT-11 and RSX-11 are fine with it. They're a bit less picky though. VMS didn't seem too picky, either.
BTW, sufficiently recent versions of RSTS (including the one you have, given that message) should handle a 2 GB disk directly (at DCS=64). That way you don t need to mess with partitions.
I didn't have a tape drive at the time...so I would've needed to copy a 2G image at 10Mbit to a disk that wouldn't show up as 2G. (That drive then failed)
I'll just wait for the cleaning tape.
paul
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On May 20, 2014, at 10:58 AM, Cory Smelosky <b4 at gewt.net> wrote:
On Tue, 20 May 2014, Cory Smelosky wrote:
After a reboot:
Pack cluster size is not 1, 2, 4, 8, 16, 32 or 64.
PC=120324 PS=030344 OV=000006 M5=004000 M6=004200 SP=041236
R0=000026 R1=143161 R2=143161 R3=000000 R4=000002 R5=041350
The disk is 1048778 blocks. I created a 512M image and copied it bit-for-bit to the disk. I think i'll just go SYSGEN 4.8 and wait for my cleaning tapes to get RSTS/E working.
How about copying the image back off, to see if the disk controller mangled it?
The message you quoted says that the content of block 1 is invalid (the pack label). Judging by the code, what it found is 0143161 rather than a valid PCS.
I wonder if your partitioning disk controller is misbehaving.
BTW, sufficiently recent versions of RSTS (including the one you have, given that message) should handle a 2 GB disk directly (at DCS=64). That way you don t need to mess with partitions.
paul
On Tue, 20 May 2014, Johnny Billquist wrote:
My memory board is third-party. Looks like it's truncating my memory
then. ;)
Are you sure. Very few 11/23 systems actually exist. Most people really have 11/23+ systems, even if they are not aware of it.
It's a dual-height board. I don't think it /can/ be an 11/23+!
(That said, without split I/D-space, you'll have preciously little
pool space, but that might not be a big issue for you right here.)
Probably not. I'll only have one disk in use at a time really.
Pool space is used for many things, but with just one user, and few
things running, not much pool is needed.
Ahh. I must be thinking of...buffer space?
Not sure what you are thinking of. :-)
I'm tired and I've been fiddling with many different things. ;)
Johnny
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On 2014-05-20 17:06, Cory Smelosky wrote:
On Tue, 20 May 2014, Johnny Billquist wrote:
4.6M+'s SYSGEN and it wouldn't accept 11/23 as an answer.
The difference between the 11/23 and 11/23+ is the amount of memory.
The original 11/23 could not go above 256K... If you have more, then
you actually have an 11/23+.
My memory board is third-party. Looks like it's truncating my memory
then. ;)
Are you sure. Very few 11/23 systems actually exist. Most people really have 11/23+ systems, even if they are not aware of it.
(That said, without split I/D-space, you'll have preciously little
pool space, but that might not be a big issue for you right here.)
Probably not. I'll only have one disk in use at a time really.
Pool space is used for many things, but with just one user, and few
things running, not much pool is needed.
Ahh. I must be thinking of...buffer space?
Not sure what you are thinking of. :-)
Johnny
On Tue, 20 May 2014, Johnny Billquist wrote:
4.6M+'s SYSGEN and it wouldn't accept 11/23 as an answer.
The difference between the 11/23 and 11/23+ is the amount of memory. The original 11/23 could not go above 256K... If you have more, then you actually have an 11/23+.
My memory board is third-party. Looks like it's truncating my memory then. ;)
(That said, without split I/D-space, you'll have preciously little
pool space, but that might not be a big issue for you right here.)
Probably not. I'll only have one disk in use at a time really.
Pool space is used for many things, but with just one user, and few things running, not much pool is needed.
Ahh. I must be thinking of...buffer space?
Johnny
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On 2014-05-20 17:01, Cory Smelosky wrote:
On Tue, 20 May 2014, Johnny Billquist wrote:
M+ do not need split I/D-space. But you do need 512K of memory. But
the 11/23 and 11/24 are supported CPUs.
I have 1M of memory.
Sure you're not confusing the 11/23 with the 11/23+? I was poking at
4.6M+'s SYSGEN and it wouldn't accept 11/23 as an answer.
The difference between the 11/23 and 11/23+ is the amount of memory. The original 11/23 could not go above 256K... If you have more, then you actually have an 11/23+.
(That said, without split I/D-space, you'll have preciously little
pool space, but that might not be a big issue for you right here.)
Probably not. I'll only have one disk in use at a time really.
Pool space is used for many things, but with just one user, and few things running, not much pool is needed.
Johnny
Hans Vlems asks: What's wrong with it?
I have had a number of Exabyte units over the years on UNIX systems. I still have at least one of each 8200 and 8500. I always found them to be reliable and if you used data style cartridges (not the video ones) very reliable and the standard BSD tape utilities and drivers support them. The biggest issue I had with them is feeding them: when writing to them, they can consume data faster than many applications can source it and "data late" caused "bad things" to happen on the tape firmware. For UNIX, years before I had written a program called double DD which was modeled after a program of the same name from Europe (the original was two cooperating processes that hand off control back and forth over a pipe]. My version used multiple threads to over lap the I/O and thus reduce if not remove the data late errors. [I used to the same program for QIC tapes too on the Sun systems we had].
So a tar command line would look like:
tar cvf - . | ddd ibs=20b obs=256K of=/dev/rmt0
Clem
On Tue, 20 May 2014, Johnny Billquist wrote:
M+ do not need split I/D-space. But you do need 512K of memory. But the 11/23 and 11/24 are supported CPUs.
I have 1M of memory.
Sure you're not confusing the 11/23 with the 11/23+? I was poking at 4.6M+'s SYSGEN and it wouldn't accept 11/23 as an answer.
(That said, without split I/D-space, you'll have preciously little pool space, but that might not be a big issue for you right here.)
Probably not. I'll only have one disk in use at a time really.
Johnny
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On Tue, 20 May 2014, Cory Smelosky wrote:
After a reboot:
Pack cluster size is not 1, 2, 4, 8, 16, 32 or 64.
PC=120324 PS=030344 OV=000006 M5=004000 M6=004200 SP=041236
R0=000026 R1=143161 R2=143161 R3=000000 R4=000002 R5=041350
The disk is 1048778 blocks. I created a 512M image and copied it bit-for-bit to the disk. I think i'll just go SYSGEN 4.8 and wait for my cleaning tapes to get RSTS/E working.
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects