Amiga.org
Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: mbob on March 11, 2017, 01:04:07 AM
-
I got a scsci2sd 5.0b with a 8GB Sandisk microsd it came with in my Amiga 3000. The drive reads in and shows two 1GB partitions available (pics) on Kickstart 3.1 and WB 3.1. I expected two 4gb drives but maybe I am wrong, is this correct?
Appologize if this is a no brainer, I haven't been Amiga engaged in a while and research didn't turn up an answer.
-
I put a 4GB microsd in and the same thing though I am rusty so figured out I could delete the second partition at least and make a single 2GB drive. Not shabby but still wondering if can be better.
-
I should add when reading in the drive it responds "cannot find track size, assuming 68".
-
Found this, so far so good formatting and installing WB:
These values will define your card as ~7400MB which should be less than its real capacity, but close enough:
Cylinders = 15000
Heads = 16
Blocks per track = 63
Blocks per Cylinder = 1008
Park head at cylinder = 15000
**** didn't work and failed format around 50%
-
Don't you have to setup the size of the card on a pc via usb?
After that it should see the 8gig. (I don't have the url, sorry)
-
With 3.1 you can't use anything beyond the first 4GB of space, unless you're using one of the various hacks/patches/alternative file systems to go bigger. Use HDtoolbox to partition your drive prior to trying to trying to format. Recommend keeping your SYS: partition less than 500MB for better compatibility with older software.
-
@ mbob
download the installer for pc and then plug into pc via usb port.
http://www.codesrc.com/mediawiki/index.php?title=SCSI2SD
I was able to setup a 6gb and 2gb partition just using the automatic setup in the installer (link above)..mind you i'm using OS3.9 with BB 1&2 so if you're suing 3.1 stick to partitions below 4gb
-
Agree with the above. New to set up the drive size via a pc. That sets the max size regardless of the cf card size
-
Found this, so far so good formatting and installing WB:
These values will define your card as ~7400MB which should be less than its real capacity, but close enough:
Cylinders = 15000
Heads = 16
Blocks per track = 63
Blocks per Cylinder = 1008
Park head at cylinder = 15000
**** didn't work and failed format around 50%
Which would be around 4 GB mark. Could be bad SD card, more likely limitation of SD-SCSI adapter (some are very limited indeed, in theory OS is happy with drives up to 2TB, but will give false sizes for partitions. Always stick to 2Gb or less partition sizes on 3.1).
Always use quick format on solid state media. Flash memory does not like sequential repeated writes. (Reads are OK).
-
@ mbob
download the installer for pc and then plug into pc via usb port.
http://www.codesrc.com/mediawiki/index.php?title=SCSI2SD
I was able to setup a 6gb and 2gb partition just using the automatic setup in the installer (link above)..mind you i'm using OS3.9 with BB 1&2 so if you're suing 3.1 stick to partitions below 4gb
Thanks! The default is 2GB which explains my findings. I set it to 7.8GB with my 8gb card and am testing now.
-
7.8 was too large and while the partitions did format they were corrupt after reboot. So instead I used the scsi2sd software to create a 3.5gb drive on scsi 0 and another 3.5gb drive on scsi id 1 setting the auto option on the SD starting point. Pretty neat feature. I long formatted the first partition and only quick formatted the other 2 as mentioned earlier it is not recommended to use a full format on the SD card. Any recommendations how to verify the disks will not become corrupted later?
Also, should I have used scsi id 6 as the boot drive? It is working but for some reason that is sitting in my head from something.
-
Also, should I have used scsi id 6 as the boot drive? It is working but for some reason that is sitting in my head from something.
Doesn't really matter. There are some loose standards across platforms (boot device 3, CD-ROM 6, tape device 2 in Solaris, for instance,) but nothing of consequence. Just bear in mind that if you have conflicting device names across multiple SCSI devices, the lowest is first. I ran into this moving my drives from hard drive to SSD, which also caused a little confusion and I wound up formatting the wrong device.
Example:
SCSI-0 has DH0 and DH1
SCSI-3 has DH0, DH1, and DH2
This will result in devices DH0: on 0, DH0.0: on 3, DH1: on 0, DH1.0: on 3, and DH2 on 3.