Stuck in diagnostic mode - disk management error device EMBASSY...already exists, restart after install monero node

StartOS Support
1

stuck in diagnostic mode - disk management error device EMBASSY…already exists when restarting after recently downloading monero node

have tried all possible solutions:
restart server
system rebuild
repair drive

since have found two threads on same issue, but they are a year old. Is the solution still the same?

flash the OS with this?

or is there a better option by now?

thanks

2

If it’s the error with the [y/N] message, then yes, you can go head and follow George’s instructions on those 2025 threads.

3

It’s not a y/n error, says ‘disk management error - device Embassy_………_main already exists’

Then gives me 3 options:

restart server
system rebuild
repair drive

I’ve tried all three, all of them bring me back to the same StartOS - Diagnostic mode window

4

In that case, yes, please follow George’s guide here:

5

Ok thanks, Stu, where can I find the checksum for the disk repair file? I’ll have a go at installing it.

6

I’m not sure we have one, since this version of StartOS was never released. George uploaded the file to our servers though, you can check the domain, and you can also reflash to the standard version when you’re done.

7

Thanks, Stu! After a bunch of issues and temporarily thinking I pretty much lost everything, I am now through to initialising StartOS on the dev build.

Like I said, I’m not very techy, could you please explain to me the reasons for step 6 - SSH access - in the instructions? When will the next update be released and what are the risks from not implementing the ssh step or reverting to the official release? Thanks!

If I proceed with step 6, is each line on here one command, as in 4 separate commands?

sudo /usr/lib/startos/scripts/chroot-and-upgrade

at the resulting shell, do:

sed -i "s/^(PasswordAuthentication yes)/#\1/g" /etc/ssh/sshd_config

then:

exit

Thanks for clarifying.

Part of my issue probably was running out of space on the SSD? adding monero node on a 2TB SSD that was already running a btc node may have caused the problem, is that possible? I had minor issues after installing monero node, so just stopped it, but probably should have uninstalled?

8

That final step means your server can’t be accessed via SSH with a simple password. Is it super important? No, I guess not, you can skip it if you prefer. I think it’s very unlikely that you’ve misconfiguration your router, your LAN is accessible, and some hacker is able to track you down from this forum. Even if that were so, you’ll probably be updating to v040 by this summer or so anyway.

That said, setting up SSH is very very useful for so many reasons and is very much worth learning to do. And if you set it up… it might be worth at least testing using it… and those three commands (you don’t copy and paste the # one) are something you can try out.

9

ok thanks, I’ll give it a go once done initialising.

Is it possible to run monero and btc node on 2TB or could this have been part of my issue? I just checked storage requirements for each and it looked like it should have been fine.

10

You should be good with both, with about 75% usage of storage when containers, dependencies etc are taken into account. Where you might run into issue is using Electrs, Fulcrum and other additional indexers on top, usage would start creeping up.

That said, I don’t think that anything like that was involved in this case.

11

Continuing the discussion from Stuck in diagnostic mode - disk management error device EMBASSY…already exists, restart after install monero node:

Thanks, Stu. I’ve been stuck on initialising StartOS for 3 days. Based on George’s comment in another thread saying “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.”

I’ve now done that, back on prod 0351 and now stuck back at Initialising StartOS screen after choosing recover from existing drive. How long shall I wait here? Another 2 days? Wondering if I should have just deleted the SSD and started from scratch… Might have been faster to start over.

What is a usual time to initialise?

How long should I stick with this, what are my chances that the disk would be actually repaired now?

12

It really should be something that takes 3-10 minutes. During that initializing phase, the OS is doing stuff but we can’t see the logs. It’ll be stuck trying to do something over and over. I’ve also seen cases where I’d leave it initializing, and come back hours later and see it still trying, then hours later it is finished. I’ve also seen it never finish because something is wrong with the drive. Also it can’t hurt to hard-refresh the browser window to see if something has disconnected while you were waiting.

Now, considering you initially had a disk issue, which it appears Monero uncovered for you (much like Bitcoin does sometimes), there is a worry here that something is physically wrong with the drive. The only way to tell for sure might be to wipe it, restore from backups or simple install everything fresh and see if the issue repeats itself.

  1. Hard refresh to see if the interface is still connected to the server

  2. Install fresh, then recover services from backups to see what happens.

13

Ok, decided to start over… would be interesting to hear if anyone has successfully recovered their disk via flashing and running the disk repair OS. Thanks for the help, I learned a few things in the process!