dragonmike (OP)
|
|
October 18, 2017, 09:21:13 AM |
|
Right. So one of my rigs is acting up. Restarting Windows using Teamviewer does not reinitialise the GPUs for some reason so they do not all show up in device manager. The only way to get everything to start properly after a crash is to physically turn off the rig, and on again.
Cutting the power using my TP-Link smart plug is not cutting it either. The mobo doesn't seem to re-initialise while powering back on, so devices are not loaded again when Windows restarts. Maybe that's a feature of the mobo, i.e. it's not resetting when power is cut, and rig reboots without going through POST processes?
Is there a way to force a full boot after power loss? Have I missed anything?
|
|
|
|
belaweb2
|
|
October 18, 2017, 09:26:46 AM |
|
Hmm... I don't understand why the smart plug does not force a full reboot... can you explain that?
|
If you don't believe me or don't get it, I don't have time to try to convince you, sorry.
|
|
|
dragonmike (OP)
|
|
October 18, 2017, 09:34:03 AM |
|
Hmm... I don't understand why the smart plug does not force a full reboot... can you explain that?
It seems the bios does not re-initialise after power loss but just goes straight back to Windows. That causes problems because when the rig crashes, it seems to lose connectivity to the GPUs. So now even by cutting power and turning it back on, Windows only sees 1 GPU on startup. If I physically turn the rig off and on again, everything's loaded as it should, all 7 GPUs are detected.
|
|
|
|
|
|
JuanHungLo
|
|
October 18, 2017, 11:46:18 AM |
|
|
Bull markets are born on pessimism, grow on skepticism, mature on optimism, and die on euphoria. - John Templeton
|
|
|
dragonmike (OP)
|
|
October 18, 2017, 02:43:09 PM |
|
That one's pretty sweet. I reckon that's exactly what I'd need. On a second thought, I'm gonna check the bios settings of that rig. I'm suspecting I might have set "state after power loss" to "last known" instead of "on". That would explain everything. If not I'm gonna have to think about a "tactical solution" (aka fudge)...
|
|
|
|
dragonmike (OP)
|
|
October 18, 2017, 10:28:54 PM |
|
Actually the state after power loss was correctly set to "on". There seems to be a problem with the mobo not recognising all GPUs unless a cold boot is initiated. Not sure wtf is wrong with it. I've now turned off "fast reboot" in the power options in Windows, fingers crossed that it'll help (I have doubts though).
What annoys me most is that cutting the power to the rig doesn't even force a cold boot after the power is restored. Not sure what can be done there.
|
|
|
|
dragonmike (OP)
|
|
October 20, 2017, 07:17:08 AM |
|
Any ideas? It's definitely a bios/mobo issue. When I restart from windows, the board explorer in bios only sees 4 gpus. I need to turn off the rig and cold boot it for the bios to see all GPUs again.
F***ing annoying.
|
|
|
|
belaweb2
|
|
October 21, 2017, 06:28:56 PM |
|
simple rig resetter could help... but is costly
|
If you don't believe me or don't get it, I don't have time to try to convince you, sorry.
|
|
|
Elder III
|
|
October 22, 2017, 03:35:12 AM |
|
Out of curiosity, what motherboard brand/model is it that's acting flaky? I don't know if a usb watchdog would fix the issue or not if it's bios related, but this is on the edge of my comfort zone too, so hopefully someone has an idea for you (short of replacing the motherboard).
|
|
|
|
Bare
Member
Offline
Activity: 130
Merit: 11
|
|
October 22, 2017, 07:18:49 AM |
|
Yeah, and what chipset is your mobo? I realized the only reason why my rigs freeze is due to incomplete gpu initialization (something about failed opencl calls ) while starting miner(usually when miner restarts that happens - claymore miner) or when one or some of my gpus hang during mining after several days or a month of mining and thats on a rig with asrock h81 btc v2.0 mobo and 6 gpus my other rig with msi z170a pro and 4 gpus usually freezes on average a lot more frequently than h81 mobo,(the worst case scenario being a restart per day) the reason because z170 is purely class A shit chipset for mining... and the only way to restart it is by cutting the power off for at least 30-40 sec and then turning the power back on usually by turning the switch on the psu off (0) and after 30-40 sec back on (I) even pushing reset switch doesn't do anything in this instance, only sort of the alternative is holding the power button for several secs but only to turn the rig off, you cant turn it back on, 30-40 secs is needed for the mobo to be completely power cut in order to power the rig back on - boot up. anyways, I'm interested in trying out those double relay usb watchdogs but I kinda doubt they'll work since I don't believe they are able to cut power, only force power off. but since they are 9€ on aliexpress I'll give them a try...
|
|
|
|
Stopper
Newbie
Offline
Activity: 10
Merit: 0
|
|
October 22, 2017, 08:35:28 AM |
|
|
|
|
|
Basmic
|
|
November 02, 2017, 06:15:35 PM |
|
I have that too. There is a USB device that overloads the computer when the port setup is silent, but these devices are expensive. There are even devices that using a mobile phone triggers the reset. In the settings of the motherboard there is a function on and off by the signal from the router. But it seems to me that if the computer froze then it can be reset only by mechanical means.
|
|
|
|
Rodrigo8
Newbie
Offline
Activity: 52
Merit: 0
|
|
November 02, 2017, 06:54:08 PM |
|
I use 8 of these Watts Clever INPLUG
|
|
|
|
dragonmike (OP)
|
|
November 11, 2017, 09:46:34 AM |
|
Thanks all for the suggestions! You know what, I actually managed to find a cure... A combination of things, I think. Forcing the proper shutdown mode in Windows, disabling all fast boot options... And waiting longer after cutting the power (30sec). Solved!
|
|
|
|
bitfools
Member
Offline
Activity: 112
Merit: 12
|
|
November 11, 2017, 10:25:43 AM |
|
Thanks all for the suggestions! You know what, I actually managed to find a cure... A combination of things, I think. Forcing the proper shutdown mode in Windows, disabling all fast boot options... And waiting longer after cutting the power (30sec). Solved!
yep, we used to call this the COLD boot and HOT boot, now its just reset, and the power never 'really goes' off most system stay running, thus to really 'reset' COLD-BOOT U must pull the plug either a double-relay on a rasberry pi type device, but certainly no way to cold-boot without pulling the plug especially with windows, with all the spyware most devices like android are always on and listening even when off, same for windows, they never really turn off unless you pull the power and ALL battery's, another reason not to use windows, on linux it would be easy to do a full software cold-reset, but on windows, well windows 10.0 as they say is spy-ware luckily the MOBO bios has lots of switches that windows can't control, so it sounds like you figured out how to get a REAL COLD BOOT without pulling the plug
|
|
|
|
JohnBitCo
|
|
December 27, 2017, 04:01:52 PM |
|
Right. So one of my rigs is acting up. Restarting Windows using Teamviewer does not reinitialise the GPUs for some reason so they do not all show up in device manager. The only way to get everything to start properly after a crash is to physically turn off the rig, and on again.
Cutting the power using my TP-Link smart plug is not cutting it either. The mobo doesn't seem to re-initialise while powering back on, so devices are not loaded again when Windows restarts. Maybe that's a feature of the mobo, i.e. it's not resetting when power is cut, and rig reboots without going through POST processes?
Is there a way to force a full boot after power loss? Have I missed anything?
If you are still having issues, here is a thought. It is not a method for the reboot, but a possible reason for the issues. What about changing to or from UEFI in the Bios settings. The worst thing that will happen is the need to change it back on a bad boot. I swear that is not the exact solution, but I think that your PC is fast booting and missing the proper set up on the way.
|
|
|
|
Marvell2
|
|
December 27, 2017, 04:54:52 PM |
|
Right. So one of my rigs is acting up. Restarting Windows using Teamviewer does not reinitialise the GPUs for some reason so they do not all show up in device manager. The only way to get everything to start properly after a crash is to physically turn off the rig, and on again.
Cutting the power using my TP-Link smart plug is not cutting it either. The mobo doesn't seem to re-initialise while powering back on, so devices are not loaded again when Windows restarts. Maybe that's a feature of the mobo, i.e. it's not resetting when power is cut, and rig reboots without going through POST processes?
Is there a way to force a full boot after power loss? Have I missed anything?
If you are still having issues, here is a thought. It is not a method for the reboot, but a possible reason for the issues. What about changing to or from UEFI in the Bios settings. The worst thing that will happen is the need to change it back on a bad boot. I swear that is not the exact solution, but I think that your PC is fast booting and missing the proper set up on the way. fix the underlying problem with the rig
|
|
|
|
VyprBTC
|
|
December 27, 2017, 05:55:31 PM |
|
Personally I would fix the actual problem vs worrying about rebooting all the time. That sounds like it could only get worse in the long run catastrophic end result for that rig.
|
|
|
|
|