Restarting didn’t cause anything, it was just the point that the issue surfaced.
The “OS error” in that recent screenshot is not the OS failing for an arbitrary reason, it’s literally telling you that it can’t read the disk. The physical disk is probably fine, and probably just needs to be wiped, but I’d pick up another just so you have more options. And I’d place it internally rather that via USB.
What to do with that new disk depends on what you have available to recover from. The data on the Samsung 2TB appears to be unrecoverable. If you have backups, you’d use that instead.
That error only showed up when I tried to transfer from the Samsung to the Crucial. Every other time I’ve tried to recover from existing aka the Samsung the OS initializes/sets up server for 7-24 hours and then goes back to the new/restore page, no error or notice, why is this?
Considering no such function to restart the server automatically at this point exists, I’m not sure. H0mer’s question above was a lead-in to trying to work out if you were confusing these two screens…
I’d like to see you try to transfer from the Samsung onto a new drive first. If that doesn’t work, the restoring from backup is the only remaining option.
My new HD arrived yesterday. I turned the server on and it did 2 beps followed by server ready chime but never started or at least not that I could tell since it never showed up on the monitor, i.e. blank screen. Turned it off a few times to try to get it to start eventually the chimes stopped. Reflashed OS and tried to load it but nothing ever happened, blank screen. Tried to install PopOS and same thing so I’m guessing a corrupted HD.
It’s under warranty so if I send it back and StartOS is still on it is any of my info/data at risk? I’m guessing no since the transfers didn’t take but want to make sure.
Nothing showing up on the screen is more of a sign of a problem with the choice of monitor or graphics card rather than anything to do with the disk. If you’re hearing beeps then there should be something on the screen.
I assume nothing ever showed up on the screen and you always accessed the server headlessly?
In any case, to answer your question… in theory, anyone with that disk could retrieve all or bits of the information that is or was on there. What might be on there… I don’t know… we’ve only discussed Monero.
I’ve always been able to see, setup and access the server from the screen. I heard beeps, now no beeps and can’t install any OS.
I have BTC Core, electrs, Vaultwarden, Nextcloud on the external. My data is on an external drive, just the OS is on the internal drive, would it be safe to send the comp back?
New Beelink SER5 mini PC, same as my other two. One is running BTCcore and works great but on my other two, Start9OS will install but upon reboot, Start9 OS wants to install again. I even set the boot devices boot first from USB then from HDD (start9OS). What is going on?
I ended up restoring from backup. I was never able to to transfer data. I’ve chosen not to reinstall the Monero node since I feel it was the cause of the corruption or at the very least a contributing factor. Several people on The Sovereign Bitcoiner chat have had the same thing happen.
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
