Hi, I've installed SF V240 recently and it's booting from sofraid just fine. (Only problem being dead/dying CPU fans, but that's expected with V240)
sd0: 16 partitions: # size offset fstype [fsize bsize cpg] a: 143374720 0 RAID c: 143374738 0 unused sd1: 16 partitions: # size offset fstype [fsize bsize cpg] a: 143371620 0 RAID c: 143374650 0 unused # bioctl -c 1 -l sd0a,sd1a softraid0 # run the installer and install on sd3 or whatever your softraid is. NOTE:if I remember correctly, I didn't have to install the bootblk manually after installation. You just need to specify boot device in OFW to boot properly: (ssh to ALOM/ILOM, reboot, send stop after memory diags, `console -f' and play with printenv, setenv and save it with nvramrc) OK: boot-command boot disk0 sr0a:/bsd boot diag-file diag-device net net boot-file sr0a:/bsd ... Rebooting with command: boot Boot device: disk0 File and args: sr0a:/bsd OpenBSD IEEE 1275 Bootblock 1.4 >> OpenBSD BOOT 1.7 Can't read disk label. Can't open disk label package sr0* Booting sr0:a/bsd 8294616@0x1000000- ... another interesting variable in OFW is autoboot variable ... more info at: http://mailing.openbsd.misc.narkive.com/IwrvZudV/5-8-sparc64-boot-from-softraid-4-fails Jan P.S. GENERIC.MP got installed by default On Wed, Nov 23, 2016 at 01:29:00PM +0200, Erkki Petsalo wrote: > Hi, > > Got it running right doing following: > > I made a regular installation on sd0 disk that recognized second cpu. > Next deleted all partitions on sd0 but a and b and made rest of the disk > d partiton raid > > # size offset fstype [fsize bsize cpg] > a: 2101464 0 4.2BSD 2048 16384 1 > b: 8913456 2101464 swap # none > c: 143374738 0 unused > d: 132351624 11014920 RAID > > Copied this partitioning to sd1,sd2 and sd3 > Made softraid disk sd4 with raid level 5 from sd0d,sd1d,sd2d and sd3d. > Then I installed OpenBSD on sd4. > > # size offset fstype [fsize bsize cpg] > a: 2104515 0 4.2BSD 2048 16384 1 # / > b: 41945715 2104515 4.2BSD 2048 16384 1 # /tmp > c: 397052928 0 unused > d: 41945715 44050230 4.2BSD 2048 16384 1 # /var > e: 41945715 85995945 4.2BSD 2048 16384 1 # /usr > f: 41945715 127941660 4.2BSD 2048 16384 1 # > /usr/local > g: 227159100 169887375 4.2BSD 2048 16384 1 # /home > > > Installation "fails" on instaboot but only things to do is after this is > rename on /mnt/ bsd to bsd.sp and dsd.mp to bsd. > Reboot and add swap from native disks to fstab. > > Boot uses ofwboot and bsd from previous install that are on sd0a. > > I formatted also sd1a,sd2a and ad3a and copied all fron sd0a to them > Haven't yet tried to boot with sd0 plugged out.... > > Erkki Petsalo > [email protected] > > > > On 21.11.2016 12:54, Paul de Weerd wrote: > > On Mon, Nov 21, 2016 at 12:44:46PM +0200, Erkki Petsalo wrote: > > | Hi, > > | > > | Just installed OpenBSD on Sun Fire V240 but seems that second CPU is not > > | used/enabled? > > | > > | OpenBSD sun-fire-v240.local 6.0 GENERIC#1094 sparc64 > > > > You're running a UP kernel. > > > > | load averages: 0.08, 0.16, 0.15 sun-fire-v240.local > > | 12:38:46 > > | 24 processes: 23 idle, 1 on processor > > | up 0:36 > > | 1 CPUs: 0.0% user, 0.0% nice, 0.0% system, 0.2% interrupt, 99.8% > > idle > > | Memory: Real: 30M/106M act/tot Free: 3905M Cache: 34M Swap: 0K/17G > > | > > | max@sun-fire-v240:/home/max $ sysctl hw > > | > > | hw.machine=sparc64 > > | hw.model=SUNW,UltraSPARC-IIIi (rev 3.3) @ 1503 MHz > > | hw.ncpu=1 > > > > The UP kernel uses 1 CPU, however... > > > > | hw.byteorder=4321 > > | hw.pagesize=8192 > > | > > hw.disknames=cd0:,sd0:0bfc3f0fb5ba8f73,sd1:5d8a9ef801e346c5,sd2:39f3892a4f278272,sd3:155ca40792d01e35,sd4:2d4a6538cd95b028 > > | hw.diskcount=6 > > | hw.sensors.softraid0.drive0=online (sd4), OK > > | hw.cpuspeed=1503 > > | hw.vendor=Sun > > | hw.product=SUNW,Sun-Fire-V240 > > | hw.physmem=4294967296 > > | hw.usermem=4294950912 > > | hw.ncpufound=2 > > > > ...two CPUs are found > > > > | hw.allowpowerdown=1 > > | > > | How do I enable it? > > > > Try installing and booting the bsd.mp kernel: > > > > doas mv /bsd /bsd.sp > > doas cp ${PATH_TO_SPARC_INSTALL}/bsd.mp /bsd.mp > > doas mv /bsd.mp /bsd > > > > This generally is taken care of by the installer. Can you share more > > details about your installation process? That may point to th problem > > (either in your process or in the installer doing this for you). > > > > Cheers, > > > > Paul 'WEiRD' de Weerd > > -- Be the change you want to see in the world.
