[ mining os ] nvoc

[Doodkeen]

Just use your editor with sudo after you are logged in by ssh. 

Code:

sudo vim.tiny /etc/apt/apt.conf.d/20auto-upgrades

[Heguli97]

Nvidia driver updated today on one of my rigs
A reboot fixed my problem
The other one already had latest 384-90

run update / upgrade again

Code:

sudo apt update && sudo apt upgrade && sudo reboot

Thank you, this worked for me . If you're using a keyboard press control + alt + f1 to get to terminal and first input login credentials(login: m1 password: miner1 by default)

[das0212]

I managed to grab an image: https://i.imgur.com/3of2yT9.jpg

This is happening on both my rigs

Thats not a problem
Ubuntu is checking drive, wait and it will boot

Same thing happend for me...and I waited for 1 hour still same screen..what to do

[Doodkeen]

Thanks Doodkeen, but how to elevated access in nvoc? I using winscp but no luck. Not able to change using m1 credential.

If you want to connect with winscp there is a good article about this situation but i would use ssh

https://blog.jamesbayley.com/2014/01/28/how-to-connect-as-root-using-winscp/

[Temporel]

ps: Seriously, why was this ON?

Ill have to check my setup later but Im surprise it was ON.

Ill scan the distro for rootkit later too just to be sure.

[azsh07]

Just use your editor with sudo after you are logged in by ssh. 

Code:

sudo vim.tiny /etc/apt/apt.conf.d/20auto-upgrades

Thanks Doodkeen, is done now. 

[jmumich]

Wow that was an interesting morning. Thanks to everyone that identified the problem and posted a solution so quickly.

Oddly enough, a couple of rigs kept running - I can't think of anything about them that was different from the others. Though they also had the update and upgrade flags set to 1.

For me, just running 

sudo dpkg --configure -a

And then rebooting did the trick.

[jmumich]

So for those who are now reaching the login screen and cannot login even when you type in your password. SSH into your rig and run the following commands:

Code:

sudo apt-get purge nvidia*
sudo dpkg --configure -a 
sudo shutdown -r now 

Now everything's working back to normal. Not sure why it did that for me. Also, I don't know if the first commmand is necessary, it's just what I typed in initially so I included it.

Thanks so much for this. I don't think the first command is necessary (edit: just to get your rigs running - see below, it may be for stability) - just the second got everything running for me. When I ran the first command, I then had to do:

Code:

sudo apt-get install nvidia-385

So to get my remote-rigs running again I just had to:

Code:

sudo dpkg --configure -a
sudo reboot

[ComputerGenie]

Not all best practices are "necessary" in terms of what is minimally required; that being said, that particular way (including purge) aids in ensuring stability.

[jmumich]

Not all best practices are "necessary" in terms of what is minimally required; that being said, that particular way (including purge) aids in ensuring stability.

Thanks, and fair point - I just didn't have much time and needed to get things going. I also left most of my update/upgrade flags at 1 - something I have to fix later. So I guess skipping the purge part is for folks like me that had just a couple minutes to get their rigs back up.

I'll follow your advice and purge and reinstall later on when I have the time 

[VoskCoin]

This is so frustrating, nvOC17 was rock solid and nvOC19 has been a headache like 15 16 18 were

nvOC_17 DL
http://www.mediafire.com/file/oi84ue7e6z9epn9/nvOC_v0017.zip


Can anyone help me add a couple coins to 17 and implement the newer auto fan controller?

[DJ ACK]

Any idea why all rigs crashed last night.  v0018 and v0019 rigs all died and won't boot.  v0018 rigs hang trying to perform cleaning functions.  v0019 rigs ask for a password. v19-1.3 rigs are all running fine.  Rigs are in three completely different geographic locations.

[papampi]

To prevent automatic updates in the future:

use your favorite editor, open /etc/apt/apt.conf.d/10periodic and change:

Code:

APT::Periodic::Update-Package-Lists "1";

To:

Code:

APT::Periodic::Update-Package-Lists "0";

and /etc/apt/apt.conf.d/20auto-upgrades

Code:

APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Unattended-Upgrade "1";

to

Code:

APT::Periodic::Update-Package-Lists "0";
APT::Periodic::Unattended-Upgrade "0";

D

ps: Seriously, why was this ON?

Very nice suggestion Doodkeen,

This is a community driven project and fullzero is doing the best job ever without asking for a dime (unlike other Linux mining distros)
Some times in the middle of the road we miss some small points that are so obvious to others,

So I'm kindly ask every Linux Guru here to do their best to look for improvements and fixes for nvOC
Feel free to PM me or post in forum any suggestion you have.

Thank you all.

[papampi]

Any idea why all rigs crashed last night.  v0018 and v0019 rigs all died and won't boot.  v0018 rigs hang trying to perform cleaning functions.  v0019 rigs ask for a password. v19-1.3 rigs are all running fine.  Rigs are in two completely different geographic locations.

Have a look at page 245 and 246.

I think the problem is while Nvidia driver was updating wdog restarted the rig because of low utilization and that cause a miss configured Nvidia driver,
I think solution is to prevent wdog from restarting the rig if dpkg is running.

[z-axis]

Please excuse my n00b questions:

- I'd like to read the OC script to understand it; can somebody give me the path to it?
- Is there a log of the OC process so I can see if they get applied (instead of just looking at nvidia-smi)?

Thanks!

Hey all, glad to hear you got your rigs back up. Mine never stopped but that might be that I had
AUTO_UPDATE_CHECKS="NO"

On another note, would somebody point me to where/how the OC script is run? I'm trying to get my 19x P106 headless rig beyond stock clocks (OC settings aren't applying).

Thanks in advance.
-z

[papampi]

Please excuse my n00b questions:

- I'd like to read the OC script to understand it; can somebody give me the path to it?
- Is there a log of the OC process so I can see if they get applied (instead of just looking at nvidia-smi)?

Thanks!

Hey all, glad to hear you got your rigs back up. Mine never stopped but that might be that I had
AUTO_UPDATE_CHECKS="NO"

On another note, would somebody point me to where/how the OC script is run? I'm trying to get my 19x P106 headless rig beyond stock clocks (OC settings aren't applying).

Thanks in advance.
-z

Code:

AUTO_UPDATE_CHECKS="NO"

Thats nvOC updates not OS updates,
You may have had the latest updates installed when you updated to 19-1.3

[z-axis]

Code:

AUTO_UPDATE_CHECKS="NO"

Thats nvOC updates not OS updates,
You may have had the latest updates installed when you updated to 19-1.3

thanks papampi, good to know. Do you have any idea about my question about where the nvOC OC scripting is?

[damNmad]

To prevent automatic updates in the future:

use your favorite editor, open /etc/apt/apt.conf.d/10periodic and change:

Code:

APT::Periodic::Update-Package-Lists "1";

To:

Code:

APT::Periodic::Update-Package-Lists "0";

and /etc/apt/apt.conf.d/20auto-upgrades

Code:

APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Unattended-Upgrade "1";

to

Code:

APT::Periodic::Update-Package-Lists "0";
APT::Periodic::Unattended-Upgrade "0";

D

ps: Seriously, why was this ON?

Very nice suggestion Doodkeen,

This is a community driven project and fullzero is doing the best job ever without asking for a dime (unlike other Linux mining distros)
Some times in the middle of the road we miss some small points that are so obvious to others,

So I'm kindly ask every Linux Guru here to do their best to look for improvements and fixes for nvOC
Feel free to PM me or post in forum any suggestion you have.

Thank you all.

Yep, please feel free and provide the valuable feedback, so that we can make nvOC even better.

Coming to the error, no one expected this sort of failure on this scale!! Hope we identify these sort of issues bit earlier.

[VoskCoin]

To prevent automatic updates in the future:

use your favorite editor, open /etc/apt/apt.conf.d/10periodic and change:

Code:

APT::Periodic::Update-Package-Lists "1";

To:

Code:

APT::Periodic::Update-Package-Lists "0";

and /etc/apt/apt.conf.d/20auto-upgrades

Code:

APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Unattended-Upgrade "1";

to

Code:

APT::Periodic::Update-Package-Lists "0";
APT::Periodic::Unattended-Upgrade "0";

D

ps: Seriously, why was this ON?

Very nice suggestion Doodkeen,

This is a community driven project and fullzero is doing the best job ever without asking for a dime (unlike other Linux mining distros)
Some times in the middle of the road we miss some small points that are so obvious to others,

So I'm kindly ask every Linux Guru here to do their best to look for improvements and fixes for nvOC
Feel free to PM me or post in forum any suggestion you have.

Thank you all.

how can i access this from windows?

[wi$em@n]

I think the problem is while Nvidia driver was updating wdog restarted the rig because of low utilization and that cause a miss configured Nvidia driver,
I think solution is to prevent wdog from restarting the rig if dpkg is running.

Papampi, you are absolutely right