Upgrade test from 12.3 to 13.2 Bricked msi master2-far on shutdown

I have a older msi master2-far dual opteron mother board machine running openSuSE 12.3 for some time now, i was investigating upgrading to 13.2 so i booted the machine off the install disk into a rescue image. This worked just fine. when i did a “shutdown -h now” the machine went down correctly but then it bricked. it will not repower the power the power supply, pulled the battery , flushed the bios rtc pull the power etc. to no avail. I know the systemd has re-written the acpi power management stuff so i assume the root cause lies in what was done in systemd as compared to what was done in 12.3 using the systemV init. I think that is what i had set as default in 12.3.

This may be to no avail if i cant get the machine to post.

I had a computer that was running 12.3. Last year, late spring, I went to visit relatives for a few days. I powered off the machine before I left.

When I got back, I powered on the machine. Except that it did not power on. The power supply had failed.

Maybe what happened to your system was similar to what happened to my system. That is, the hardware failed. Maybe it was a complete coincidence that it happened during an upgrade, just as it was a complete coincidence that my failure occurred while going on a short trip.

Yes that is possible, but i must embarrassingly admit the the is the second time that this has happend on this machine , earlier this week i first tried to test the 13.2 image, but the first time i had it up i did a init 0 not a proper shutdown , it acted the same way shutdown correctly and then bricked but this time i was able to unplug it and got it to come back up. i did run 12.3 over the course of several days with out issue then i decided to give it one more shot using a proper shutdown ,i was assuming the init 0 is what took it down, regretfully not.

Did you do a clean install or an upgrade???

An upgrade can leave odd bits an pieces behind and 12.3 to 13.2 is a very large jump

Also when you say bricked do you mean totally dead ie no getting to the BIOS or nothing? or do you mean that thing did not boot

Actually i didn’t get the chance to do the upgrade. i brought up the install media’s rescue image and then did the shutdown / init 0 , the board is a bit dated so i wanted to make sure all the drivers loaded up and it ran under the kernel which it appeared to. As far as the state of the machine , currently i get no bios , beep codes etc and no fans , not even in the power supply .

No OS will cause that. Hardware problems will. Perhaps a failing power supply if no fans or lights