Hi Folks, it looks like that this M3000 is really a difficoult machine.
Some holy soul borrowed me firmware 1117 to upgrade, and I really hoped to make the best out of the box. First of all, in order to initialize and arrive at OpenBoot it takes almost 10 minutes, pretty much unaccettable. Then, although it unexpectedly installs and correctly runs solaris 11.3, it succeeds in installing OpenBSD 6.9 but not in running it, as it falls into "CPU RED_State". There must be some driver, inactive in bsd.rd, and active in bsd.mp which triggers this error, although it's not really bricking the machine. Another minor annoying thing is that, before booting from bsd.rd it kept on trying a FC iscsi boot, which went into a loop. In order to install I had to remove the FC card. This happened AFTER "OpenBSD BOOT 1.21" appeared on the terminal. After days of tries, I am fed up with this box and it's going back directly to it's provider. Just a correction for the sparc64 html page: M3000 with recent FW and obsd doesn't brick anymore, but still doesn't run. Here follows a paste of the console, fyi. Thanks all and have a nice day. Pasha SPARC Enterprise M3000 Server, using Domain console Copyright (c) 1998, 2012, Oracle and/or its affiliates. All rights reserved. Copyright (c) 2012, Oracle and/or its affiliates and Fujitsu Limited. All right. OpenBoot 4.33.5.d, 32768 MB memory installed, Serial #10030427. Ethernet address 0:b:5d:e2:d:5b, Host ID: 80990d5b. Rebooting with command: boot Boot device: /pci@0,600000/pci@0/pci@0/scsi@0/disk@0,0:a File and args: OpenBSD IEEE 1275 Bootblock 2.1 ..>> OpenBSD BOOT 1.21 ERROR: /iscsi-hba: No iscsi-network-bootpath property Trying bsd... Booting /pci@0,600000/pci@0/pci@0/scsi@0/disk@0,0:a/bsd 10041872@0x1000000+1520@0x1993a10+194836@0x1c00000+3999468@0x1c2f914 symbols @ 0xfd68a400 485979+165+649008+447812 start=0x1000000 [ using 1584000 bytes of bsd ELF symbol table ] ERROR: CPU RED_State Reset has occurred. Resetting... Oct 1 15:17:47 M3000 fmd: SOURCE: sde, REV: 1.17, CSN: PX60916019 EVENT-ID: e. On Sat, Sep 25, 2021 at 2:39 PM Tijs <t...@users.sourceforge.net> wrote: > Hi Paolo > > Don’t do it; you’ll brick it. At least three people here have tried it, > and all ended up with a bricked box. Search the mailing list archive for > details. > > I still have mine, but it hasn’t been powered on in years. Too bad. > > > On 24 Sep 2021, at 18:46, Paolo Aglialoro <paol...@gmail.com> wrote: > > > > Hello, > > > > I have a colleague who would like to get rid of his M3000 box and I'd > > rather take it to try obsd on it. > > > > Questions are: > > -what are your experiences/best practices on this box? Pros/cons? > > -does it support ldoms with obsd? > > -does anybody have recent firmware to flash before install? > > > > Thanks a lot > > P > >
