> Date: Sat, 27 Jan 2018 06:18:09 -0700 (MST) > From: Kyle K <kylek...@gmail.com> > > Wish I searched about this before trying to install OpenBSD 6.2. I just > bricked my M3000 too few hours ago, sucks, I tried resetting the XSCF using: > > XSCF> restoredefaults -c factory > > but no avail. I'm not giving up yet though, I have a Sun XVR-300 Graphics > Adapter in my M3000 and I was using it as a desktop running Solaris with X11 > up to this point by having modified intake and PSU fans to quiet them down > and make server bearble to use. Plus I invested in 2HDDs and 32GB of RAM, I > don't want to lose this. > > I was searching and reading that there's a way to obtain CUA number that > will allow you to sign up for support at Oracle site. You have to purchase a > random software from their online shop (preferably cheap one) and buy > support along the side. Once you make a purchase you should get welcome > letter from Oracle along with CUA number, which then will give you SI > (Support Identifier). Then you should be able to complete your Account > Registration at on support.oracle.com and create tickets and submit a case > asking for service password that will unlock command to clear the fault > codes. I have found "Oracle Configuration Management Pack for Applications > (Named User; 1 Year)" for $20 and $22 for 1 year support for that, totaling > $42, not bad? > https://shop.oracle.com/apex/f?p=DSTORE:6:19266001435453:::6:P6_LPI,P6_PPI,P6_METRIC,P6_TERM:1621014036861810302734,3415207466896555108,Named%20User,1_Year > > If that works out I could help some of you to unbrick your M3000 as well. > Let me know. Hoepfully you didn't trash it yet.
Hope that'll work for you. Note that if you're running a recent-enough version of the XCP firmware, you can clear the fault yourself. XCP 1116 is known to allow this. I'm not sure what the earliest version version is that no longer requires the help of a field engineer to clear spurious hardware faults like this. There is no evidence that OpenBSD actually damages the hardware. All evidence points at the firmware not being able to handle the way OpenBSD outputs characters over the serial console; the same issue that plagued the M4000/M5000 (and presumable the M8000/M9000). I thought a workaround was in place but apparently it doesn't work for the M3000. Apart from this issue, OpenBSD would run just fine on these machines :(. In my opinion Oracle should not require customers to sign up for support to make machines work again that have been a victim of firmware bugs. But apparently the "Enterprise" in the name of these machines means that normal consumer protection doesn't apply...
