I rebooted my server and it came back with Disk management error. It’s very similar to this thread from 1.5 months ago, https://community.start9.com/t/disk-management-error-on-reboot/2394. Just like this user, I installed the Monero Node a few weeks ago and on restarting I run into Disk management error. I also noticed that the Monero Node will not backup with the rest of the services. Are there known problems with this service or perhaps something that needs to be looked into?
I’ve done Repair Drive and System Rebuild right with no luck. Moving onto Reflashing…
@Jeremy tagging you since you helped the user with this problem and to help with tracking similar issues.
You can only backup monero-startos to an ext4 filesystem (or possibly some others, whatever supports files whose names begin with .).
If you got an error message like the disk management error you linked to, this is StartOS detecting errors on the disk at startup, invoking the disk repair function, and not handling it correctly (due to a bug in StartOS v0.3.5.1) and getting stuck at the confirmation prompt.
There are a few options, the easiest of which is probably:
Reflash the OS and hope that fixes it as seemed to work for the user that created the thread you linked to.
Next would be “just wait” for the next version of StartOS (this might be months away though).
Next would be a somewhat complicated set of instructions for getting and flashing (and then mitigating the risks of) the disk repair fix developer ISO (which I can send you if you want this option).
Is this related to the Monero node? There’s the ticket linked in my original post and I just came across this one which is happening now. All seem related to Monero node and disk management error.
I’ve reflashed the OS and selected ‘Use an existing drive’, it’s been initializing for 3 hours which seems like a long time?
If it’s a bug in v0.3.5.1, is it not possible to due a patch? It’s a major point of instability if a user restarts their server and it just might not come back one!
That error isn’t specific to monero. That doesn’t mean monero didn’t make it happen, but simple writes from monero (especially “safe” db writes which we have turned on in monero) should not cause disk corruption. It’s more likely your disk is in the early stages of dying or not under ideal operating conditions. Monero might be adding stress to a disk that’s already having issues.
Unless the initialization has presented an error, it’s still doing it’s thing, just let it be.
If it’s a bug in v0.3.5.1, is it not possible to due a patch?
It’s possible but I think you’re basically the 5th person or so who’s run into it. Given that the devs did run a fix build, but never released it, I doubt they’re going to. Basically right now, the fixes for all bugs in 0351 (and there are many) are fixed in the forthcoming, currently-in-alpha next version of StartOS.
You can try it again if you want – I can’t imagine it will hurt the situation. Since the installer only touches where the OS goes, and the same goes for when at setup, you pick Recover > Use Existing Drive, even if it fails to complete, you should be able to paper over it effectively with the other iso and instructions I sent. Tough to say what’s going wrong with no error toast though.
So I flashed and installed 0.3.5.2 and selected Recover → Use existing drive at about 1pm yesterday and it was still initializing this morning. I just checked and it’s now sitting at the StartOS Setup, Start Fresh or Recover…
Restart goes back to select recover or new install, no errors, also no progress is ever shown on the Initializing StartOS Setting up your server, it just scrolls and doesn’t show percentage complete like the docs show.
Well that’s unexpected. But maybe having taken so long it actually did manage to do the repair. Try flashing 0351 again and hopefully you’ll be back to your old installation.
Yep, unfortunately it went back to the selection screen (new install or recover) again…no errors or info just initializing then back to first screen like nothing has happened. I’ll try redoing 0.3.5.1 and get back to you tomorrow.
ok, I reflashed and installed 0.3.5.1 at about 8pm, about 5 minutes into initialization/setting up your server the chime for server is ready went off, the progress bar was scrolling and showing no percentage progress.
7am: still on Initializing StartOS/Setting up your server, progress bar just scrolling no percentage progress being shown.
8am: back to the new install/recover screen, no errors, no interrupted power or internet
I flashed and installed popOS with no problems so I don’t think it’s a problem with the computer but maybe the portable SSD I was using for services, it’s only been in use for 3 mos tho. If there’s a problem with the existing drive or any drive does StartOS have checks or diagnostics?
I have the external HD that was used in my pi (it crashed in late Dec), it has everything except the Monero node I recently installed, could I use that or is the pi HD architecture different?
Should I recover from Backups? What are my options?
I’m running a ThinkCentre M710q, 8GB ram, i5-7500T, 2.70GHz x 4.
It doesn’t make too much sense to me that you’ve been able to install StartOS once before on this hardware, and now don’t seem to be able to. Has anything changed since then? What might be the different?
Regarding the Pi external drive, all the services on that are using a different architecture, so no, what you’re suggesting isn’t an option. They only way you could correctly use that drive is to go through the StartOS transfer flow, where you’d use this external drive as a source and would transfer services to a new drive. This would in essence convert the services to the correct architecture.
The only thing that changed on StartOS was the addition of the Monero Node a few weeks ago. Network wise, I added pi-hole in mid-Feb.
The OS will install but it won’t take the existing data off the HD. It sits at the screen attached and reverts back to the opening new install/recover screen.
I mean what changed with your flashing technique? Monero now no longer comes into play at all. All you’re doing is installing StartOS.
But your second point, that this is might be an inability to properly read the data partition I think does hold water. Once able to confirm that this partition is unreadable, restoring from backup to a fresh install is a valid choice of next step. You mentioned another linux distro. Could that mount the data partition?
