I don’t think that it’s a problem to work with the USB pendrive, as I could clone bit-wise the entire pendrive into the SSD whenever I want.
I already did it the first time, I set up everything on the pendrive and then moved all into the SSD with a dd command.
I hoped that the hive-replace command could solve my issues in the first place. But now not even a fresh new install can solve them, and this was my last chance for what I know I can do.
Have you attempted a fresh download from the GPU Zip link and flashed with Etcher? This method has yet to fail me and we are talking about many Rigs.
I use this for all my SSD, M2SATA, and the few remaining USBs.
I not doubting your file management skills, but as you see above, some of the same issues were: bad install, hacked rigs, etc.
This is exactly how I did the last installation. I downloaded the zip from the website and flashed the usb pendrive with etcher. I then inserted the pendrive into the rig and started a fresh new OS. I used the same rig ID I had in the previous installation and after logging in I had the exact same 2 issues as before, like I didn’t reinstalled at all.
Personally, I would place the rig.conf file in the hive directory while on the USB flashing workstation.
Do you have direct access to the rig with local monitor and keyboard? As well as via hiveos.farm worker interface?
I have access via the web interface. I can have physical access to the rig but it’s very difficult and can be done just some specific days of the month.
Remote only does reduce a few troubleshooting options.
Is the rig mining for it’s few hours and currently manageable by hiveos.farm worker interface?
Do you get the same error when attempting to upgrade from the “upgrade arrow” or just clicking on the version in yellow?
This is how I discovered the selfupgrade command error. I just tried to update as usual with the web interface and i got an error. The error should also be in one of the screenshots above.
If you believe your error is the same as already posted, you have the solution posted in this thread above.
The problem is that i reflash it and the issue is still here.
If you really want my screenshots, here they are:
This is by just trying to update from the web interface.
There are a few reasons, those commands are not there or are not run.
Have you tried the following from inside hiveshell with no other data: selfupgrade
The only solution I would trust is a rebuild from a known good source, on a known good media, and have it well protected from outsider access.
With the 3hr run time symptoms you shared, I would assume the worst: outside access occurred or source was compromised.
This is what I already did. I downloaded and flashed using a brand new USB pendrive, bought just for this purpose using a windows computer that was always only used occasionally for office work (just writing documents and social media).
I don’t have anything against you, but in the last replies I just re-answered the same questions I answered before and I just did again all the steps I already did before, just to continue the conversation with you.
Just for contest, I’m a computer engineer, not a novice computer user. So I know very well how computer and operative systems work. I was here to find some deep technical HiveOS-specific help that I could miss.
So any good standard practice to avoid simple external or internal corruption has been already taken.
P.S. I’m appreciating your help anyway, I wrote it just to avoid any further time waste for both.
Try reflashing the new drive, and booting from it on your office pc, (assuming this is in a different network/firewall etc. )if everything works as intended, like selfupgrade, then you know your issue is a bad actor on the other network.
Or use a pc that’s on a seperate network to test boot into hive and update and such.
If that doesn’t work, I would try making a fresh hive account and replicating the above process. If that works then sounds like someone has access through your account (maybe you didn’t revoke the bad actor session? Etc)
This topic was automatically closed 416 days after the last reply. New replies are no longer allowed.
