• Updated 2023-07-12: Hello, Guest! Welcome back, and be sure to check out this follow-up post about our outage a week or so ago.

se/30 SCSI2SD

mc9625

Well-known member
I've finally opened my MAC SE/30 (btw there's no evidence of capacitors leaking, but still very low volume from the internal speaker... I've removed the battery anyway).

I've installed a brand new SCSI2SD peripheral with a 4gb sd card inside. Actually I've tried to connect it to my macbook pro, before, just to run the SCSI2SD-util and I get a "killed 9" msg.  The scsi2sd-monitor gave me a fail on the sd card. 

Anyway I've installed the card into the SE 30 and booted. Obviously there's no way to have the MAC see the SCSI2SD. 

To be honest I've been able to find a good manual or "stupid proof" tutorial.

I'm worried about the "killed 9" error.

Any clue?

 

gsteemso

Well-known member
I believe the “killed 9” message would be the OS under which the util was run reporting to you that, for whatever reason, the util was halted by some other piece of software. The Unix command for sending a control message (“signal”) to another running program is called “kill” because that is its most common use; the command to immediately and unconditionally halt another process in its tracks and wipe it from the list of running programs is “kill -9”. (The minus sign is not part of the number, but rather a quirk of Unix command lines; it tells the kill utility that the text immediately after itself, the 9, is being passed to it in a particular way.)

 

mc9625

Well-known member
Uh I think they absolutely need a better website with manual, tutorial, howtos or whatever.

 

Cloaked Alien

Well-known member
Can confirm, caps needs to be replaced even if they seem fine.

I have two SE/30s. One was messed up due to an exploding battery and had to be sent to techknight and uniserver for repairs and recap, it's far more stable than my other one was.

My other one isn't being used at all but I'm considering having it recapped to keep it safe but hoping to find someone locally that can do it since shipping overseas is quite pricey.

Regarding your issue though you have to prepare the SD card for the SCSI2SD adapter or something. I've got one on my powerbook duo and had to initialize it as a 2GB disk. But it was a one-off deal and I followed some guide, just worked so unfortunately I can't remember =/

 

mc9625

Well-known member
How do you prepare the card for SCSI2SD ?

Actually I've checked the log of scsi util and it reports

18:44:48: SCSI2SD Bootloader Ready

18:44:49: SCSI2SD Bootloader Ready

18:44:50: SCSI2SD Ready, firmware version 4.6

18:44:50: SD Capacity (512-byte sectors): 0

SD CSD Register: 00000000000000000000000000000000

SD CID Register: 00000000000000000000000000000000

 
Also, since I've launched scsi2sd util from terminal I've noticed that every time I save to device, I get this error in the terminal window: USB HID Write Failure: 0x0
 

mc9625

Well-known member
well, it turns out that the unit is probably defective. I've asked for a replacement unit. I hope it will arrive soon (well relatively soon... it could take two or three weeks to reach Italy).

 

mc9625

Well-known member
I've tried two, but i know for sure they both work. I've been able to test them in my MacBook Pro without any problem, and one is the card I use in my raspberry pi.

Also I've been told by Michael McMaster, that was very kind and replied to my mails, that the most concerning thing is the "FAIL" error reported by the scsi2sd monitor, according to him with such error there's no chance the card will ever work with the Mac.

I am still waiting for a confirm that the replacement unit has indeed been shipped.

 
Last edited by a moderator:

dibenga

Well-known member
I had strange happenings with my SCSI2SD as well in my SE/30. While there is a 2gig limit I read that in reality it should be just slightly smaller than 2 gig partition that can help eliminate boot issues. Not sure if that is remotely close to your issue but I thought I'd share anyway

 

mc9625

Well-known member
The biggest "warning" are the two "fail" reported by the scsi2sd monitor for SD and SCSI. did anyone tried to run the monitor on a working unit!?

 
Last edited by a moderator:

joethezombie

Well-known member
I have an 8GB SD card in my SE/30, configured with four drives partitioned to 1.8GB each.  I had no problems or strange happenings.  I never ran the monitor because it just worked.  The scsi2sd-util had no problems running on my iMac after setting the permissions as an executable.  I used it to set up the 4 drives, and to set the parameters to emulate an Apple drive so I could use the default Apple HD SC setup utility.  I just finished installing 7.1.1 Pro Update 3 and MODE32 via disk images from a FloppyEmu.  What an awesome product this is.  Couldn't be happier with the SCSI2SD.

 

joethezombie

Well-known member
I have to admit, the machine seems a bit sterile without the clicks and grinds of the HDD, although the steady whine of a spinning drive is not missed at all.  Not one bit.  Nope, I'm not going back.  A fun project might be to make a hardware beatbox that plugs to the activity LED pins and simulates the clicks and grinds.   :)

 

mc9625

Well-known member
joethezombie actually even from the scsi2sd util I've noticed something strange. I've set up the 4gb card has 1 drive o 1.7gb but after I save to the card I see this messages in the log window:

10:06:25: Save Complete.

10:06:27: SCSI2SD Ready, firmware version 4.6

10:06:27: SD Capacity (512-byte sectors): 0

SD Capacity: 0 ?

Is this normal?

 

joethezombie

Well-known member
I would say that is not normal.  I created a single 1.7GB drive, and the log window:

07:26:57 AM: Save Complete.
07:27:15 AM: SCSI2SD Ready, firmware version 4.6
07:27:15 AM: SD Capacity (512-byte sectors): 15467520
SD CSD Register: 400e00325b5900003b377f800a4040af
SD CID Register: 0353445353303847805ce11d5001014d


 
Last edited by a moderator:

Instow

Active member
I've just installed a SCSI2SD with 4gb SD card into an SE/30 and this worked for me:

1) Using Windows 7 and the scsi2sd-util, set the following params (which I had made a note from another thread here on the forum):

  • Set the vendor to the string " SEAGATE" (yes, there is a single space in front of SEAGATE for a total of 8 characters)
  • Set the product ID to the string "          ST225N" (10 spaces in front for a total of 16 characters)
  • Set the revision to the string "1.0 " (with a space after, for a total of 4 characters
  • Set whatever disc size you need (I made two at 2gb, one for system 6, one for system 7)
Save all to the SCSI2SD.

2) Put the SCSI2SD into the SE/30 and then booted off an external drive.

3) The SE/30 didn't recognise the SCSI2SD, so I used Lido and formatted the disc from there which then mounted it.

4) Booted off FloppyEmu and did a system install.

Don't know if that will help ... but I've done it this way on a few machines now and all works fine.

 

bobo68

Well-known member
SCSI2SD util says "SD Capacity (512-byte sectors): 0" when I have no SD in the slot. Otherwise it reports the size of the SD.

The SCSI2SD monitor opens a little window with:

SCSI2SD Device: Ready, 4.6

SD Test: OK

SCSI Test: OK

Have you tried different USB cables? Apart from that I'd say your SCSI2SD is broken but the USB HID Write Failure is strange.

There is a short manual and a FAQ available.

 

olePigeon

Well-known member
Mine wouldn't write to the settings until the firmware was the current version.

I then unplugged and plugged it back in.

After that, it worked.  However, yours already says it's at version 4.6, so I don't know. :(

Mine is set to a size of 4GBs because I partition a 4GB MicroSD card into 2x2GB partitions.

 
Top