SOLVED No reboot possible from GUI. Is this related to TrueNAS or rather a hardware issue?

[green22]

I am rather new to TrueNAS (I made 1-2 working installtions till now) and got another problem with new used Hardware.
Asus P10S WS
1245 v5

If I try to reboot the system does not succeed. Has anyone made similar experiences and found a solution?

The last two lines sometimes are before the Uptime line.

Is this a software problem or can this be causes by the hardware?
Until now I had a good working server grade Asus P10S-M-DC in use and wanted to change to this workstation motherboard Asus P10S WS because of the bigger amount of Sata ports and PCIe slots.

By the way, at operations the MB says: "A0 IDE initialization is started"
and when I reboot (and freeze occurs) it does not change.
Pretty weird, as if the MB is totally confused.

Ideas:
- it's my fault caused by improper configuration
(I already did a BIOS reset. Unfortunately the latest BIOS version available is pretty old.)
- It's TrueNAS (BSDs) fault
- it's hardwares fault

EDIT:
The System also freezes sometimes if I save/exit the BIOS.

EDIT2:
The solution?
I disabled "HD Audio Controller", that causes the computer to freeze while rebooting.
Guess I can live with an activated Audio Controller.
My tip to others:
Always test with default BIOS values and check each value (or groups of values) separately and look if a setting may cause unwanted behavior.

EDIT3:
And don't forget to reinsert the CMOS Battery, I forgot that and ran into new "bugs"...
Maybe it is also worth to renew an old battery if the BIOS behaves weird...

 

[QonoS]

It could be a BIOS related issue. In that case another chance to completely reset BIOS settings (including areas that are left out by a soft-reset) is:
Shutdown computer. Remove power cord. Remove BIOS battery and leave it out over night. Next morning put battery back in. Connect and power up.

 

[green22]

It could be a BIOS related issue. In that case another chance to completely reset BIOS settings (including areas that are left out by a soft-reset) is:
Shutdown computer. Remove power cord. Remove BIOS battery and leave it out over night. Next morning put battery back in. Connect and power up.

I will try that, thx

 

[green22]

It could be a BIOS related issue. In that case another chance to completely reset BIOS settings (including areas that are left out by a soft-reset) is:
Shutdown computer. Remove power cord. Remove BIOS battery and leave it out over night. Next morning put battery back in. Connect and power up.

Could reflashing the BIOS solve the problem as well? Or is it very uncommon, that BIOSes are flashed badly without recognizing it and therefore unnecessary effort?

 

[green22]

The reset is work in progress (I removed the battery and will try again in a few days).

Another idea, may an old power supply (BeQuiet PurePower 8 300W) also be the cause?
Then I try to get borrow a newer one to test.

 

[QonoS]

Both is worth a try if no better options are known.

 

[green22]

Both is worth a try if no better options are known.

I found the problem. Probably the "hard reset" by removing the CMOS battery over night (in my case a few days) was not necessary. But this procedure cause me to test each bios setting differing the defaults alone.
The solution?
I disabled "HD Audio Controller", that causes the computer to freeze while rebooting.
Guess I can live with an activated Audio Controller.
My tip to others:
Always test with default BIOS values and check each value (or groups of values) separately and look if a setting may cause unwanted behavior.

 

[green22]

Really, now shutting down no longer works, despite it reboots
Can't believe it...
Temporary workaround: Disable "Power On By PCI-E/PCI"
Thus wake on lan no longer works :(
To test: I should try if the hardware button is capable of shutting the NAS down or another power supply would help.
But I suppose a buggy BIOS :(

Edit:
For now a "new" (Pure Power 10 300W instead of even older Pure Power L8 300W) power supply fixed the issue. I will comment if the issue stil remains solved for a Pure Power 400W some time later.
Edit2
Never mind, the problem still exists. Obviously the PC/Server has to run a while (maybe it needs to be warm/hot?) to fail to shut down.