codereddew12
Newbie
Offline
Activity: 36
Merit: 0
|
|
October 24, 2017, 11:38:58 AM |
|
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: 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.
|
|
|
|
Heguli97
|
|
October 24, 2017, 11:49:19 AM |
|
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: 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. Too bad I don't have ssh configured/enabled.
|
|
|
|
Temporel
|
|
October 24, 2017, 11:55:48 AM |
|
I have the same issue. Both of my rigs running nvOC are down. It looks like some kind of update was done and drivers stopped working.
same here, that rig was up and running since August and it stopped an hour ago. I updated Nvidia drivers and its back online again. That rig is still on v19 and is my last one on nvOC but after this event, Ill remove some cards and install Windows 10.
|
|
|
|
Temporel
|
|
October 24, 2017, 11:59:05 AM |
|
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 sudo apt update && sudo apt upgrade && sudo reboot I rebooted 3 times (v19) and still had the same problem. I had to update the Nvidia drivers to fix the issue.
|
|
|
|
FFI2013
|
|
October 24, 2017, 12:17:07 PM |
|
When I tried to unzip nvoc on win 7 I keep getting error that I don't have enough space when there 150gb empty but it unzips on my win 10 pro rigs without a issue
|
|
|
|
azsh07
Newbie
Offline
Activity: 10
Merit: 0
|
|
October 24, 2017, 12:27:23 PM |
|
If possible, can we stop driver from auto update to prevent this event? For now, I just manage to get my rig working again by re-flashing image. But I believe this event will occur again since driver is auto update. I using P106 cards.
|
|
|
|
Doodkeen
Newbie
Offline
Activity: 4
Merit: 0
|
|
October 24, 2017, 12:33:02 PM |
|
To prevent automatic updates in the future: use your favorite editor, open /etc/apt/apt.conf.d/10periodic and change: APT::Periodic::Update-Package-Lists "1"; To: APT::Periodic::Update-Package-Lists "0"; and /etc/apt/apt.conf.d/20auto-upgradesAPT::Periodic::Update-Package-Lists "1"; APT::Periodic::Unattended-Upgrade "1"; to APT::Periodic::Update-Package-Lists "0"; APT::Periodic::Unattended-Upgrade "0"; D ps: Seriously, why was this ON?
|
|
|
|
azsh07
Newbie
Offline
Activity: 10
Merit: 0
|
|
October 24, 2017, 12:45:00 PM |
|
To prevent automatic updates in the future: use your favorite editor, open /etc/apt/apt.conf.d/10periodic and change: APT::Periodic::Update-Package-Lists "1"; To: APT::Periodic::Update-Package-Lists "0"; and /etc/apt/apt.conf.d/20auto-upgradesAPT::Periodic::Update-Package-Lists "1"; APT::Periodic::Unattended-Upgrade "1"; to APT::Periodic::Update-Package-Lists "0"; APT::Periodic::Unattended-Upgrade "0"; D ps: Seriously, why was this ON? Thanks Doodkeen, but how to elevated access in nvoc? I using winscp but no luck. Not able to change using m1 credential.
|
|
|
|
Doodkeen
Newbie
Offline
Activity: 4
Merit: 0
|
|
October 24, 2017, 12:53:38 PM |
|
Just use your editor with sudo after you are logged in by ssh. sudo vim.tiny /etc/apt/apt.conf.d/20auto-upgrades
|
|
|
|
Heguli97
|
|
October 24, 2017, 12:58:47 PM |
|
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 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
Newbie
Offline
Activity: 14
Merit: 0
|
|
October 24, 2017, 01:00:04 PM |
|
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
|
|
|
|
|
Temporel
|
|
October 24, 2017, 01:03:21 PM |
|
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
Newbie
Offline
Activity: 10
Merit: 0
|
|
October 24, 2017, 01:03:54 PM |
|
Just use your editor with sudo after you are logged in by ssh. sudo vim.tiny /etc/apt/apt.conf.d/20auto-upgrades
Thanks Doodkeen, is done now.
|
|
|
|
jmumich
|
|
October 24, 2017, 01:14:46 PM |
|
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
|
|
October 24, 2017, 01:22:06 PM Last edit: October 24, 2017, 01:33:19 PM by 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: 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: sudo apt-get install nvidia-385 So to get my remote-rigs running again I just had to: sudo dpkg --configure -a sudo reboot
|
|
|
|
ComputerGenie
|
|
October 24, 2017, 01:27:02 PM |
|
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.
|
If you have to ask "why?", you wouldn`t understand my answer. Always be on the look out, because you never know when you'll be stalked by hit-men that eat nothing but cream cheese....
|
|
|
jmumich
|
|
October 24, 2017, 01:32:31 PM |
|
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
|
|
October 24, 2017, 01:53:41 PM Last edit: October 24, 2017, 02:54:20 PM by 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.zipCan anyone help me add a couple coins to 17 and implement the newer auto fan controller?
|
|
|
|
DJ ACK
Newbie
Offline
Activity: 13
Merit: 0
|
|
October 24, 2017, 02:05:13 PM Last edit: October 24, 2017, 02:22:10 PM by 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.
|
|
|
|
|