Started by krazycat, May 28, 2019, 03:40:19 PM
Quote from: barcher174 on May 28, 2019, 06:38:41 PMIf the SD card is larger than the xml i don't think you should see issues. What kind of errors are you seeing?
Quote from: wa2flq on May 29, 2019, 12:21:43 PMCan you share a little more about how you are using the SCSI2SD
Quote from: krazycat on June 02, 2019, 01:03:23 PMHi all, today I did a series of tests on the SCSI2SD v5.1 card. See pics for the configuration I used. Unfortunately the card doesn't work, I always get the error message "sc: parity error". -I tried the 16 GB SDcard (previously created for this SCSI card) on an old SCSI2SD v5.0 and it starts up correctly. -I tried a known work 8 GB SDcard on this SCSI2SD v5.1 and it doesn't start. -I tried with and without power cord plugged on SCSI2SD, not working. -I tried with a different SCSI cable, no luck again. -I tried activating the parity preference, but the error is always the same, "sc: parity error". I'm losing hope with this card, someone have any other advice for me? :'(
Quote from: wa2flq on June 02, 2019, 07:31:02 PMTwo additional items. 1) You don't appear to have the latest utility program that has some features, especially termination control, that are intended for the V5.1. (see below)2) I'll will again suggest that you flash the firmware to the latest version.
Quote from: wa2flq on May 29, 2019, 01:29:32 PMIts always "possible" that the card has some defect. But until you've checked the different parts (cables, power, termination, image) you won't know for sure. I have several of the cards, but despite all my abuse they all still work YMMV. Turn on parity first. I missed this when I compared XML files the first time, sorry.I would try to re-flash the firmware and then reload the XML file next. Some other things to check or try:Remove other drives and check your SCSI2SD terminations and term power. Are you powering the card from the SCSI bus or power supply? While debugging I would do the latter.Make sure the image size matches the XML size for the drive. If there is a published checksum for the image, check against your copy.Good luck.