This was bothering me, so I did a bit of looking.
According to slide 32 of this:
https://www.slideshare.net/solarisyougood/sparc-t4-1-system-technical-overview
'The SPARC T4-1 has Dual LSI SAS2008 8port SAS2/SATA2 controllers'
The LSI SAS2008 is apparently quite well supported by the
On Thu, Dec 28, 2017 at 1:45 AM, Stefan Sperling wrote:
> On Wed, Dec 27, 2017 at 02:29:09PM -0800, Jordan Geoghegan wrote:
> > Cannot boot from softraid: Unknown error: code 19
> >
> > Any ideas?
>
> In this condition, the boot loader has not assembled a softraid volume.
>
>
I'm afraid I don't know the answer to that, sorry. Not sure if anyone does...
I think the SCSI HBA driver is the same on SPARC64 as on AMD64, but then Sun
had a habit of "improving" control interfaces for Solaris so who knows. I do
know under Solaris there is a bioctl-like tool to manage it,
Yes I had considered using the onboard hardware raid, but I don't
particularly trust it. I also need the ability to rebuild my arrays
while the machine is online and was hoping to be able to do the 3 disk
RAID1 offered by OpenBSD softraid. Do you know if bioctl(8) is capable
of controlling the
On 2017-12-26 14:56, Jordan wrote:
I've recently gotten my hands on a couple shiny new SPARC T4-1 and
T3-1 servers and I was looking to install OpenBSD with a softraid
mirror on them for production use. The problem is, is that I end up
with this upon following the install instructions and
On Thu, Dec 28, 2017 at 02:08:58AM -0800, Jordan Geoghegan wrote:
> I will check to see if the T4 will boot from crypto softraid and will also
> crack open the box for the T3-1 to see if I can get it booting from
> softraid. The disks should be being scanned correctly during the device-tree
>
I will check to see if the T4 will boot from crypto softraid and will
also crack open the box for the T3-1 to see if I can get it booting from
softraid. The disks should be being scanned correctly during the
device-tree walk, as I am able to set the machine to autoboot when
installed to a
On Wed, Dec 27, 2017 at 02:29:09PM -0800, Jordan Geoghegan wrote:
> Cannot boot from softraid: Unknown error: code 19
>
> Any ideas?
In this condition, the boot loader has not assembled a softraid volume.
Which means that either the disks which make up the volume aren't being
scanned during the
On Dec 27, 2017 8:07 PM, Jordan Geoghegan wrote:
>
> Did you:
>
> # newfs /dev/rsd(whichever is correct)
>
> before reboot?
>
> That doesn't make sense. What would I be making a new filesystem for -- or
> on, for that matter. Disk formatting is taken care of by the
Did you:
# newfs /dev/rsd(whichever is correct)
before reboot?
That doesn't make sense. What would I be making a new filesystem for -- or on,
for that matter. Disk formatting is taken care of by the installer script.
Did you:
cp your kernels to the new sd's
Again, this doesn't make sense.
On Wed, Dec 27, 2017 at 03:01:12PM -0800, Jordan Geoghegan wrote:
> sparc* is not an fdisk / MBR platform
I don't have one :(
more inline
>
>
>
> On 12/27/17 14:56, Edgar Pettijohn wrote:
> > On Wed, Dec 27, 2017 at 02:29:09PM -0800, Jordan Geoghegan wrote:
> > > I tried installing again and
sparc* is not an fdisk / MBR platform
On 12/27/17 14:56, Edgar Pettijohn wrote:
On Wed, Dec 27, 2017 at 02:29:09PM -0800, Jordan Geoghegan wrote:
I tried installing again and followed your instructions to a T and the
installer hung after typing reboot at the prompt upon finishing install.
I
On Wed, Dec 27, 2017 at 02:29:09PM -0800, Jordan Geoghegan wrote:
> I tried installing again and followed your instructions to a T and the
> installer hung after typing reboot at the prompt upon finishing install.
>
> I let it sit for 10-15 minutes after entering reboot command but then
>
I tried installing again and followed your instructions to a T and the
installer hung after typing reboot at the prompt upon finishing install.
I let it sit for 10-15 minutes after entering reboot command but then
determined it had likely frozen considering it said the disks had been
synced
Thanks for the clarification Stefan. Did you have to manually run
installboot(8) or is the bootloader stuff taken care of automatically by
the install script?
On 12/27/17 04:52, Stefan Sperling wrote:
On Tue, Dec 26, 2017 at 12:56:53PM -0800, Jordan wrote:
The install procedure I followed
On Tue, Dec 26, 2017 at 12:56:53PM -0800, Jordan wrote:
> The install procedure I followed on the T4 was:
>
> 1) Boot install kernel and drop to shell and provision RAID partitions on
> both disks using the letter “a” via disklabel(8)
>
> 2) Assemble RAID volume with # bioctl -c 1 -l
Thanks Edgar for catching that typo, step 3 should indeed read:
3) I zeroed the first 10MB of the RAID volume with # dd if=/dev/zero
of=/dev/rsd2c bs=1m count=1
That is the command I used on the T4, I accidental wrote urandom rather than
zero when I was typing the email.
On 12/26/17 13:52,
On Tue, Dec 26, 2017 at 12:56:53PM -0800, Jordan wrote:
> Hi everyone, long time lurker, first time poster. I've been around since the
> 5.* days, so I would consider myself fairly seasoned in the ways of OpenBSD.
> I've obviously done the RTFM dance, done it once, done it twice, been doing
> it
Hi everyone, long time lurker, first time poster. I've been around since
the 5.* days, so I would consider myself fairly seasoned in the ways of
OpenBSD. I've obviously done the RTFM dance, done it once, done it
twice, been doing it all week long now-- this problem really has me
banging my
19 matches
Mail list logo