Re: Booting sparc64 from SSD

zenxyzzy <[email protected]>
Newsgroups gmane.os.netbsd.ports.sparc64
Message-ID <CA+VBNVTsLKN396_hMaWvC-Su9ONVMh1TpidQxRbR=B+78wY_ag@mail.gmail.com>
I've done two things: these are 2.5 inch drives, and they don't take much
space and weigh little. finally, they have no moving parts.

at first,  there are venting holes just between the 3.5 inch drive rack and
the floppy/card reader.  i screwed them directly to the case.  this was
satisfactory, but ugly.

then, i picked up a 5.25 inch rack that has space for 4 removable 2.5 inch
sleds, and another that has space for 2x 2.5inch internal drives and a slot
loading dvd writer.

so, my front rack has 6 x 2.5inch drives, one slot loading dvd writer, and
in the 3.5 inch rack, a usb/sd/cf panel.  the scsi to Sata converters are
fairly small, but it is a bit cramped behind the 5.25 inch racks.  short
cables are important, and since everybody wants power, there are way too
many Y splitters.

I can boot from the scsi devices, scsi-to-sata converters, and of course,
from the on-board fiber channel.

fiber channel SSD's are available, but I'm not dropping 3 kilobucks on a
73GB drive.

--curt


On Mon, May 19, 2014 at 4:51 PM, Cameron Berkenpas
<[email protected]>wrote:

>
> On 5/19/14, 3:38 PM, zenxyzzy wrote:
>
>> I've got a sb2000, and I've had excellent luck with scsi-to-sata
>> adaptors.  I've got a DVD burner on one, and a 120Gb sata SSD on the other.
>>  booting works, even though 20MB/sec is a bit pokey for SSD's.   I have a
>> PCI-X 3442X from LSI logic as well, but haven't figured out the magic
>> incantation to allow booting from anything on it - this would be ideal,
>> since it's got a 66mhz 64 bit pci.
>>
>
> Where are you physically placing the drives? If I recall correctly, the
> onlt place to put any drives is in a cage with 2 slots where the drives
> connect directly to the ports on the motherboard.
>
> -Cameron
>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.