Mac Plus write error: Not able to receive 512 bytes of data

[edgeux]

• I have tried a Pi 4/4gb and a 3B+
• both Jan release and feb release fullspec
• 2.4a 68klma
• Mac plus 4gb

Describe the issue

I have tried all of the boot images supplied in the repo as well as manually created system (6.0.8, 7.0.1, 7.5.3)
I have tried booting the pi from USB and from SD
I have tried both 32 and 64 bit rpi os
I have tried multiple scsi cables.
Voltage is ok.

I am able to boot the macplus from all/any rascsi system to a functional desktop HOWEVER when i try to perform any operation that requires writing to the scsi disk the mac freezes after ~10 seconds of data transfer.

with the log set to TRACE, the rascsi/macplus hangs reliably on these two lines:

Feb  7 19:45:31 max RASCSI[484]: [2022-02-07 19:45:31.429] [error] virtual void SCSIDEV::Receive() Not able to receive 512 data, only received 2. Going to error
Feb  7 19:45:31 max RASCSI[484]: [2022-02-07 19:45:31.429] [trace] virtual void SCSIDEV::Error(ERROR_CODES::sense_key, ERROR_CODES::asc) Error (to status phase)

the only difference with each hang being that:

only received 2
varies numerically in each case.

i am able to boot the mac from a system floppy with zero errors but as soon as i write to scsi, i get maybe 10 seconds of transfer before hanging with the same errors

advice, instructions, etc ?

m

[rdmark]

@edgeux Does other SCSI storage devices work well with your Plus? Have you tried using contact cleaner on the SCSI port on the computer?

[edgeux]

Thanks for the reply, I have performed contact tests with every pin, board to board. I have no other scsi devices to test unfortunately.

[uweseimet]

@edgeux Is your SCSI chain properly terminated? Both physical ends of the chain have to be terminated, i.e. if the RaSCSI board is your only device it definitely must be terminated.
Considering that your problem is prominent, but there are no reports of similar errors by other users (at least not tickets), indicates that your problem is very likely related to your specific hardware setup (including termination).
Wrong termination can result in weird effects. It can even happen that only some (but not all) operations fail. When I don't terminate my board it appears to work with my Atari TT, but not with my Mac, and also not with my Atari MegaSTE. With the MegaSTE RaSCSI receives commands, but the actual data transfer fails.

[edgeux]

It is the only scsi device and the jumpers are terminated on the rascsi. I think I will have to get my hands on some other scsi equipment to test further. Is there any other useful information that can be derived from the error itself? It means nothing to me.

[uweseimet]

@edgeux I'm afraid there is no further information the error message provides. It just indicates a basic SCSI communication/protocol issue.

[supercompman]

I'm seeing the exact same error with my Mac Plus. I'm using a Raspberry Pi 3b, RaSCSI board v2.4a, 4MB RAM installed on the Mac Plus with ROM 3, and the RaSCSI is the only device connected to the SCSI bus, with termination enabled. The Mac Plus boots fine from floppy, a FloppyEmu (either configured as either a floppy drive or HD20), and from a SCSI Zip drive. The RaSCSI works completely fine on a Mac Classic II.

[uweseimet]

@supercompman Your logs on trace level look the same?

[supercompman]

@uweseimet Yes. I'm seeing the same things in my logs. I'll post my logs as soon as I get a chance if that would help.

By the way, I'm using version 22.02.01 of the RaSCSI software.

[uweseimet]

@supercompman If your trace logs shows do same you don't have to spend on posting it. I just wanted to ensure from the logs your issue is the same, and not just a similar problem with different logs.

[uweseimet]

I also stumbled upon this error message (with various counts for the received data), but it is not reproducible. Platform: Atari TT, develop branch 2022-02-25.

[2022-02-25 13:12:23.845] [error] void SCSIDEV::Receive() Not able to receive 512 data, only received 446. Going to error

[jcres69]

I have the same error from my Mac Plus. I can boot from the RaSCSI, but intermittently it hangs and this error appears in the log:
virtual void SCSIDEV::Receive() Not able to receive 512 data, only received 505. Going to error

Mac Plus 2.5M, system 608
RaSCSI 68kmla 2.4a
RPi4 2GB

[joeventura1]

Having the exact same issue
Mac Plus 4M, system 608
RaSCSI 68kmla 2.4a
RPi3

Completely unstable
Can boot from the distro 6.0.8 HDA
Try to use it, copy anything to it, it freeze, Heap errors, restarts.
Also can't mount more than one HDA file to a second SCSI ID

Works flawlessly with Floppy Emu and well as my real 20MB SCSI drive

[supercompman]

@uweseimet
After experimenting on and off for a few months, I finally found a solution that worked for myself. I have no idea if it will work for anyone else. Using Silverlining 5.31 for the driver and partitioning worked well. Previously, I had been using the Apple tools and driver. With Silverlining, I have the option of selecting the method used by the driver for reading and writing data. Any of the "Blind" methods would not work at all, while all of the "Handshake" methods worked perfectly. I reviewed my RaSCSI logs and I'm not seeing any errors when using the Silverlining driver.

I will point out however that performance is pretty abysmal, even for a Mac Plus. Writes average about 140k/s and reads about 200k/s. While the seek time is outrageous, even my SCSI Zip drive gets better throughput.

[jcres69]

@supercompman
Thank you! I started using the Silverlining driver a few weeks ago and so far the SCSI errors and freezes on my mac plus have disappeared.

[joeventura1]

Same here!

…

On Sat, Jul 30, 2022 at 1:41 PM jcres69 ***@***.***> wrote: @supercompman <https://github.com/supercompman> Thank you! I started using the Silverlining driver a few weeks ago and so far the SCSI errors and freezes on my mac plus have disappeared. — Reply to this email directly, view it on GitHub <#656 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZ6U46LBAZEEVV6THLAIAFTVWVSM5ANCNFSM5NYOM54Q> . You are receiving this because you commented.Message ID: ***@***.***>