My server was all setup and working fine until I installed the Monero node. I went through everything you just went through plus replacing the CMOS battery and adjusting the installed memory sticks. The final solution was to restore from backup, same as you. Now my server is back to normal but I have to resync the Bitcoin blockchain and such.
I think there are enough examples of the Monero app causing problems that it needs to be updated or removed. I think I’m gonna avoid the community apps for now too unless there’s better auditing. All this troubleshooting took two hours out of my day and time is precious.
@George
After following the instructions the “Initializing StartOS” screen has been loading for 24h. Is it supposed to take that long? If I open a new browser window and go to the local IP of my server I see the Start fresh and Recover buttons again. adjective-noun.local doesnt resolve.
Yep, just let it go. I’d wait up to at least another day. Hopefully you still have the original start.local open where you initiated it from – if not that’s ok, but it could indeed notify you when it’s done. I’ve also seen instances where it doesn’t notify but after a good 2 days, it’s most likely done and you can probably just reflash to prod 0351 after that and be ok.
You don’t have to flash prod afterward, you can just continue with the dev build but pay attention to the last couple steps re ssh in my post that I linked to
Is this still the current recommendation? I have the exact same issue, also after installing monero node and then restarting a few weeks later…
had been running perfectly for a couple of years, only issue at times needing to restart TOR.
I’m not super techy, just trying to decide whether to start over or to try the fix recommended here. Are there people successfully running the monero node from community market place after using this fix ?
Monero doesn’t damage disks – It uses them heavily which, can reveal existing or developing disk issues. Just because there’s partition table or filesystem issue that the Disk Repair function wants to fix doesn’t mean the disk is dead or data is unsalvageable, either.
It’s unfortunate that there was never a StartOS v0.3.5.2 release with the disk repair prompt bugfix, but there wasn’t, and won’t be, so if you run into disk issues, you’ll get stuck here, and the disk repair iso is the way to go.
As far as your actual question, I’ll defer to others in this thread who’ve personally run into it. I did install Monero on a test box and have run into the disk repair bug plenty of times helping others, but in my experience the only people who have feedback after they actually go through with the disk repair fix are the people who can’t progress because their disk actually died. Pretty sure most users in that situation are fine, and continue on as usual afterward. Let me know if you need help.
Thanks, George, I do need help. Just clarifying, I’m not on the y/n screen. But I’m typing across two chats now. I’m not that familiar with how to use a forum like this, is there a way to join my two posts?I started my own post and then found this thread here, also.
I was running core already on a 2TB SSD, is it possible to run monero on the same drive or is this possibly part of the issue?
my main aim is to get my btc node back up and running asap. fine to uninstall monero for now.
my screen says Disk management error EMBASSY_……._main already exists and then gives me 3 options - i tried them all and always return to the same screen
wondering whether to start over or attempt disk repair. thank you
I tried everything that was suggested and the only thing that worked was a new hard drive and restore from backup. I was able to erase and reformat my corrupted drive so you could try that if you don’t have a spare hard drive around.
Thanks, Kane, for your reply. I’ve made it through to the initialising startOS screen, but did also for quite a while have the black screen issue you mentioned in your earlier posts, when trying to get into the start up menu. Eventually I thought I might try to erase the SSD, checked it via disk utility on a separate mac and was about to erase. Tried to boot into start up one more time with only the flashdrive, not my SSD attached and managed to get to the BIOS menu. Shut down, reattached the SSD and on restarting got into the start up menu, was then able to flash the dev OS, select to restore from existing SSD drive. Hopefully It will go through from here! sounds like this part could take up to two days
Is reflashing prod 0351 the only way forward if stuck on “Initializing StartOS” screen longer than 2 days or can I simply restart into disk repair iso and then follow step 6 to set up SSH access? Thanks