The top level of a DuckDuckGo search told me there is a shortage, except
one promoter called "Rabbit Hole Computing" (sounds suspicious) with a
competing product called ZuluSCSI.
On 2/4/23 10:25, Craig Lalley wrote:
> There is a product, SCSI2SD, I know a couple of people who have it working.
> -Craig
>
>
> Sent from Yahoo Mail for iPad
>
>
> On Saturday, February 4, 2023, 7:08 am, Tracy Johnson<[log in to unmask]> wrote:
>
> What Lalley said.
>
> I lost a mirror myself two days ago. Now I gotta find the same make and
> model and have it inserted into a Jamaica drive. (I upgraded my Jamaica
> mechs to 32MB years ago, but when mirroring you need the same geometry.)
>
> It's either that or find another array ... hmmm ... maybe Beechglen has
> a used one?
>
> Even SSD, now THAT would make a fast Empire game!
>
>
> On 2/4/23 09:57, Craig Lalley wrote:
>> FSCHECK.MPEXL.TELESUP
>> ca all
>> -Craig
>>
>>
>> Sent from Yahoo Mail for iPad
>>
>>
>> On Saturday, February 4, 2023, 6:52 am, Terry Simpkins<[log in to unmask]> wrote:
>>
>> My little 928 had a system failure this morning. My initial suspicion is
>> that LDEV #2 has a problem.
>> I issued an ‘abortjob’ command from a ‘non-console’ session, and got these
>> messages before the command completed successfully:
>>
>>
>> Bad SYSTEM LOGICAL Sector number 0x226A80b on ldev 2 (io_status=FFD40071)
>> Filename of badfile:/VESOFT/CMD22/SHOWSCH8
>> Bad SYSTEM LOGICAL Sector number 0x226A80b on ldev 2 (io_status=FFD40071)
>> Filename of badfile:/VESOFT/CMD22/SHOWSCH8
>> Bad SYSTEM LOGICAL Sector number 0x226A80ÿ on ldev 2 (io_status=FFD40071)
>> Filename of badfile:/VESOFT/CMD22/SHOWSCH8
>> Bad SYSTEM LOGICAL Sector number 0x226A80ÿ on ldev 2 (io_status=FFD40071)
>> Filename of badfile:/VESOFT/CMD22/SHOWSCH8
>> Bad SYSTEM LOGICAL Sector number 0x226A80ÿ on ldev 2 (io_status=FFD40071)
>> Filename of badfile:/VESOFT/CMD22/SHOWSCH8
>>
>> (There were more of these messages but I didn’t copy everything)
>>
>> I walked over to the other room where the console is located and found the
>> following displayed:
>>
>> System Abort 1740 from subsystem 107
>> Secondary Status: INFO = -44 Subsys = 113
>> System Halt 7, $06CC
>>
>> Then autorestart kicked in and the system performed a ‘Start NoRecovery’,
>> with no reported errors.
>> I ran “LISTF” on the file listed above (SHOWSCH8.CMD22.VESOFT) without a
>> problem.
>> And then “printed” the file to the screen without generating another system
>> halt. If the drive was failing, I thought that would create another system
>> failure.
>>
>> Any ideas/suggestions?
>>
>> Terry W Simpkins
>> Yorktown, VA 23693
>> IBA # 8778 SS1000, SS2000, BBG, 50CC
>>
>>
>> * To join/leave the list, search archives, change list settings, *
>> * etc., please visithttp://raven.utc.edu/archives/hp3000-l.html *
>>
>>
>>
>>
>> * To join/leave the list, search archives, change list settings, *
>> * etc., please visithttp://raven.utc.edu/archives/hp3000-l.html *
--
Tracy Johnson
BT
NNNN
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|