17:57 <spyjoshx> OK. So I was on a few days ago, and I tried some more things since then. At this point, I've done the following to migrate my sandstorm to a OS install. For context, I upgraded my server hardware to now have a SSD in addition to the old drive. I installed Debian on the new drive, and left the old drive in without clearing it. After I installed

17:57 <spyjoshx> Debian, I ran "cp -a /path/to/old/drive/opt/sandstorm /opt/sandstorm.full", ran the installer with "curl https://install.sandstorm.io | bash", stopped the new install with "sudo sandstorm stop" and "sudo service sandstorm stop", swapped the old and new directories with "sudo mv /opt/sandstorm /opt/sandstorm.empty" and "sudo mv /opt/sandstorm.full

17:57 <spyjoshx> /opt/sandstorm" and then tried starting sandstorm with "sudo sandstorm start". Checking the status with "sudo sandstorm status" tells me it's not running, and the log at /opt/sandstorm/var/log/sandstorm.log contains the following: https://gist.github.com/spyjoshx/5d69d5cf0ac3468aeadced46820dc47c

18:01 <isd> Was the old install running when you did the copy?

18:02 <spyjoshx> The server had shut down normally, but I hadn't specifically run "sudo sandstorm stop". Is that likely a problem?

18:03 <isd> If it wasn't running it should be fine.

18:03 <spyjoshx> Should I try booting into the old system, and manually running sudo sandstorm stop and copying again?

18:04 <isd> I doubt that will help; I could see a situation where if it were actively running you could get database corruption or such when copying out from underneath it, but even if it was shut down "improperly" it should be able to cope just fine

18:05 <spyjoshx> yeah. I'm copying it using the new system, from the old drive which is mounted as storage under the new system

18:06 <isd> My temptation at this point would be to compare things with mtree

18:06 <spyjoshx> is that a command? It looks like it's not installed if it is.

18:09 <isd> https://linux.die.net/man/8/mtree

18:10 <isd> I can never remember what package it's in; I make use of it like once a year.

18:10 <spyjoshx> looks like it's mtree-netbsd

18:28 <spyjoshx> OK I'm not exactly sure I understand how mtree works...

20:00 <spyjoshx> not exactly sure what you want me to do with mtree

20:00 <isd> My thinking was: use it to get a summary of the original file tree, then compare it to the copied one, and see what if anything is different.

20:01 <isd> Sorry, a bit distracted today.

20:02 <spyjoshx> yeah, I've been looking at the man for it, and I'm not sure how to use it that way. It says I need something like a specification. Do I need to generate one somehow from the original sandstorm folder?

20:03 <isd> Looks like -c is probably what you want? Not somewhere where I can test it myself unfortunately, and it's been long enough since I've used it...

20:12 <spyjoshx> so this is what I got from that https://gist.github.com/spyjoshx/4f3acaac957d74a838ca168230c23896

20:14 <isd> Were there any errors about permissions? There's a bunch of stuff missing from there, like the whole var/mongo directory, as well as apps & grains...

20:15 <spyjoshx> you mean errors while copying, or while running mtree?

20:27 <isd> The latter, though the former might be of interest as well now that you mention it.

20:28 <spyjoshx> that's the thing. no errors on either

20:29 <isd> Are there indeed files in the tree that mtree didn't pick up?

20:29 <spyjoshx> how would I find that out?