Adding disk on Sun Fire V245 w/FreeBSD 11

Gordon Zaft gordonzaft at
Sat Feb 18 04:20:54 UTC 2017

I finally figured this out and figured I should document for posterity...

I realized I had not tried to do a probe-scsi from the OBP prompt, so I did
that.  I
got an endless cascade of

Base SAS World Wide ID is 0!
This must be fixed immediately using set-sas-wwid

So digging into this document I
realized the onboard RAID was messing me up.

Following the directions, and the ok> prompt:

setenv auto-boot? false
setenv fcode-debug? true

Then a

Select the SCSI disk controller (for me it was b) )

ok>select ^Y (inserts the line from show-disks; trim off the /disk)



showed that the disks that I wasn't seeing were listed as disabled (or
inactive) volumes.  To fix this I deleted each volume

ok>0 delete-volume
ok>1 delete-volume


now shows no volumes.  Doing a

ok>setenv fcode-debug? false

when the system came back a probe-scsi showed the disks now, and when I
boot they are in dmesg.

I still had to put a VTOC on them since, in my case they were IBM disks, or
wiped Sun disks:

/sbin/gpart create -s VTOC8 da1


/sbin/gpart add -t freebsd-ufs da1

to create one big partition.

Then a newfs as usual and you're good to go!


On Fri, Nov 18, 2016 at 9:35 PM, Gordon Zaft <gordonzaft at> wrote:

> I have a Sun Fire V245 running 11.0.  It had one 146GB hard disk in it.  I
> went to add a second similar disk but the OS doesn't seem to see it.  I can
> tell the hardware sees it as if I pull it out while the machine's on I get
> an alert from the ALOM. But I don't see a "da1" device in dmesg.
> What am I doing wrong?
> Thanks in advance!
> --
> Gordon Zaft
> Province 35 Governor
> Phi Mu Alpha Sinfonia Fraternity
> gordonzaft at

Gordon Zaft
Province 35 Governor
Phi Mu Alpha Sinfonia Fraternity
gordonzaft at

More information about the freebsd-sparc64 mailing list