The last backup will not work, I've been able to get it to that point, but at that exact point is the point where the people who destroyed the portion of the world that was very used for a workbase and mine happened. If I restore to that point, it's just as if I didn't restore at all.
To start, I hope that the last backup IS good enough, on account of the fact you mentioned previously that the entire world has gone missing. Recreating a workbase is much better than recreating your entire structure.
Secondly, the tutorial did fully illustrate the correct steps necessary for backing up. If there was a typo there, like there was in your crontab attempt or in the 'finding increments' screenshot, I have hesitancy about the accuracy of the typing. If i cannot see the results from the commands, it makes it increasingly difficult to diagnose. Screenshots would help here, if youre able. Heck, if you actually want to upload your virtualbox VM files to a file-uploading site, id even be happy to take a look at it.
But if a mistake caused by a typo exists (and I cannot be certain or do not get the full results of my diagnosing), we can go back and forth for a long time and not make satisfactory progress.
At this point, if possible, I'd really recommend uploading your VM files. If not, screenshots so I can actually see if im dismissing possibilities or trying routes that arent necessary, to help remedy this sooner.
I know it did back up, I'm very sure of it, I checked the files before executing the command to roll back the server.
After executing and receiving the errors that I did, rechecking the back ups came up with the rdiff-backup directory thing.
If I knew how to find the virtualbox VM files, I would upload them. I am not familiar with any of this program, or system.
recreating the workbase that we've been working on for days is kind of a big deal.
The amount of glass, iron, lava, water, time and effort was kind of a lot.
If it comes down to it we'll just have to start fresh, which sucks, but >_<
--Upon trying to revert back to the last back up - cp: can't stat '/mnt/sda1/minecraft/archive/one' : No such file directory.
---Anything that I try to do, from the tutorial page, is telling me that /mnt/sda1/minecraft_____ doesn't exist pretty much.
----For the hell of it, I tried starting the world up, but "World one does not exist!"
I know it did back up, I'm very sure of it, I checked the files before executing the command to roll back the server.
After executing and receiving the errors that I did, rechecking the back ups came up with the rdiff-backup directory thing.
If I knew how to find the virtualbox VM files, I would upload them. I am not familiar with any of this program, or system.
recreating the workbase that we've been working on for days is kind of a big deal.
The amount of glass, iron, lava, water, time and effort was kind of a lot.
If it comes down to it we'll just have to start fresh, which sucks, but >_<
--Upon trying to revert back to the last back up - cp: can't stat '/mnt/sda1/minecraft/archive/one' : No such file directory.
---Anything that I try to do, from the tutorial page, is telling me that /mnt/sda1/minecraft_____ doesn't exist pretty much.
----For the hell of it, I tried starting the world up, but "World one does not exist!"
The files I'm referring to exist on your host system. Using that screenshot, you can see that my world information is in "e:\folders\.virtualbox\harddisks" etc. The hard drive has an extension .vdi
The .virtualbox folder (and whatever your equivalent is), has a harddisk and a machines directory. The config file (.xml) and (.vdi) comprise your entire virtual machine. Stored in there is your minecraft partition etc.
This is awesome, its working perfectly for me in virtualbox over windows 7
The guide was really well done and easy to follow (even though I already have experience with Linux it helped a lot)
I have given tinycore linux a try before but it was tough since I use a wireless connection and that was impossible to set up without internet connection lol :L (at least that was what it was like in the firt release >.< I haven't tried it in a while)
Thank you very much for this :biggrin.gif: I love testing out distros and having one that is dedicated to minecraft is like a x2 goodness multiplier.
(I signed up to the forums just to reply to this thread xD)
This is awesome, its working perfectly for me in virtualbox over windows 7
The guide was really well done and easy to follow (even though I already have experience with Linux it helped a lot)
I have given tinycore linux a try before but it was tough since I use a wireless connection and that was impossible to set up without internet connection lol :L (at least that was what it was like in the firt release >.< I haven't tried it in a while)
Thank you very much for this :biggrin.gif: I love testing out distros and having one that is dedicated to minecraft is like a x2 goodness multiplier.
(I signed up to the forums just to reply to this thread xD)
Hey, extra thanks for going the extra mile to sign up just to say that--I'm doing all this for fun and though writing tutorials and helpdocs takes a lot of time, it's made worthwhile knowing its being useful and educational :smile.gif:
If you run across anything you think could use improvement, too, let me know--i want this to be the best possible way to host MC!
Hey I'm having a problem with MineOS (running on VirtualBox). I installed it and everything, then I updated the stuff etc, configured everything, ran "sudo filetool.sh -b" to save changes to the virtual disk, and did "sudo reboot". No matter what I change, when I reboot the system it resets to the installation state (every new file deleted etc). This is sort of annoying and I can't do anything with MineOS if it just deletes my stuff every time it restarts. What might the problem be?
A suggestion, make an admin.sh argument for creating a well compressed archive of a world for downloading via the httpd. I've come up with some instructions on how to make very small world file archives. You don't have to use 7-zip for the gzipping, you could use gzip -9, it will make comperable(but likely slightly larger) .dat files and DeflOpt is optional(especially if you're concerned about the licensing).
The Meaning of Life, the Universe, and Everything.
Join Date:
12/21/2010
Posts:
42
Member Details
Quote from iloveportalz0r »
Hey I'm having a problem with MineOS (running on VirtualBox). I installed it and everything, then I updated the stuff etc, configured everything, ran "sudo filetool.sh -b" to save changes to the virtual disk, and did "sudo reboot". No matter what I change, when I reboot the system it resets to the installation state (every new file deleted etc). This is sort of annoying and I can't do anything with MineOS if it just deletes my stuff every time it restarts. What might the problem be?
Make sure you are un-mounting the OS image within Virtual Box .. this was what I was finding until I remembered to unmount it. So that it doesn't boot from the image, but instead from your install
A suggestion, make an admin.sh argument for creating a well compressed archive of a world for downloading via the httpd. I've come up with some instructions on how to make very small world file archives. You don't have to use 7-zip for the gzipping, you could use gzip -9, it will make comperable(but likely slightly larger) .dat files and DeflOpt is optional(especially if you're concerned about the licensing).
Theres already this option from within the web-interface called 'archive', under each world tab.
And if you want to execute it from the admin.sh file, its
./admin.sh archive one
#replace one with world number
this creates a full archive of your world, which is tar'red and gzipped, and can also be used with the 'import' button
Hey I'm having a problem with MineOS (running on VirtualBox). I installed it and everything, then I updated the stuff etc, configured everything, ran "sudo filetool.sh -b" to save changes to the virtual disk, and did "sudo reboot". No matter what I change, when I reboot the system it resets to the installation state (every new file deleted etc). This is sort of annoying and I can't do anything with MineOS if it just deletes my stuff every time it restarts. What might the problem be?
Make sure you are un-mounting the OS image within Virtual Box .. this was what I was finding until I remembered to unmount it. So that it doesn't boot from the image, but instead from your install
This is absolutely correct. The last step of the instructions is to unmount/eject the ISO and reboot. However, if the ISO remains mounted, it will continue to boot the CD and your adjusted settings will always be hiding underneath.
ok so i have done this and it works but 2 questions...
1. i have opped myself and the commands dont work, how do i get admin?
2. How do i add addons? i dont know where the files to the server are
1) I assume to op yourself, you put in your 'minecraft login' in the arguments and hit 'OP', correct?
If you'd like to test this more, have minecraft logged into your server as you do this--the screen will verify that you have opped yourself correctly by showing "You've been opped!"
2) hey0 is the only add-on I have added thus far. Other addons are compatible, but you must follow their instructions to do so. As far as where the server files are (and presumably the addons youre tacking on), connect to your server via FTP. This is the root directory.
In this directory you'll see many things, the minecraft server jar, the hey0 server jar (if youre using it), your backup directory, etc etc. If your other addons require being in the same directory as your server jar, youd put it right there.
(if on the other hand youre talking about hey0 plugins, theres a plugin directory for that already existing)
Hey I'm having a problem with MineOS (running on VirtualBox). I installed it and everything, then I updated the stuff etc, configured everything, ran "sudo filetool.sh -b" to save changes to the virtual disk, and did "sudo reboot". No matter what I change, when I reboot the system it resets to the installation state (every new file deleted etc). This is sort of annoying and I can't do anything with MineOS if it just deletes my stuff every time it restarts. What might the problem be?
Make sure you are un-mounting the OS image within Virtual Box .. this was what I was finding until I remembered to unmount it. So that it doesn't boot from the image, but instead from your install
This is absolutely correct. The last step of the instructions is to unmount/eject the ISO and reboot. However, if the ISO remains mounted, it will continue to boot the CD and your adjusted settings will always be hiding underneath.
I checked the settings in VirtualBox and the ISO is not mounted. I have no idea what the problem is. I like MineOS because when I ran a server directly from windows then tried to play on it, everything was super laggy and then minecraft crashed. When I ran a server from MineOS in VirtualBox on that same windows system, it ran smoothly. I would really like to be able to use this software. I appreciate your help, but it appears that the ISO is not the problem.
Make sure you are un-mounting the OS image within Virtual Box .. this was what I was finding until I remembered to unmount it. So that it doesn't boot from the image, but instead from your install
This is absolutely correct. The last step of the instructions is to unmount/eject the ISO and reboot. However, if the ISO remains mounted, it will continue to boot the CD and your adjusted settings will always be hiding underneath.
I checked the settings in VirtualBox and the ISO is not mounted. I have no idea what the problem is. I like MineOS because when I ran a server directly from windows then tried to play on it, everything was super laggy and then minecraft crashed. When I ran a server from MineOS in VirtualBox on that same windows system, it ran smoothly. I would really like to be able to use this software. I appreciate your help, but it appears that the ISO is not the problem.
If the ISO is, infact, unmounted, then it means the installation and booting from HD is complete. However, if the changes you made were while it was still booting from the ISO, any attempts to save 'sudo filetool.sh -b' would have been made to the ram-filesystem. Test it right now, since you can confirm the ISO is unmounted--make a single change to the admin.sh, run 'sudo filetool.sh -b' and reboot. The change should be reflected just fine.
If the ISO is, infact, unmounted, then it means the installation and booting from HD is complete. However, if the changes you made were while it was still booting from the ISO, any attempts to save 'sudo filetool.sh -b' would have been made to the ram-filesystem. Test it right now, since you can confirm the ISO is unmounted--make a single change to the admin.sh, run 'sudo filetool.sh -b' and reboot. The change should be reflected just fine.
I changed admin.sh, used "sudo filetool.sh -b", then rebooted. admin.sh was saved. I then updated the server files, used the filetool.sh again, and rebooted again. The server files were NOT saved. I also tried changing my crontab file, and again, the stuff wasn't saved when I used filetool.sh. What's wrong?
Oh, and if I set a crontab to run "sudo filetool.sh -b" every once in a while, would it work?
A suggestion, make an admin.sh argument for creating a well compressed archive of a world for downloading via the httpd. I've come up with some instructions on how to make very small world file archives. You don't have to use 7-zip for the gzipping, you could use gzip -9, it will make comperable(but likely slightly larger) .dat files and DeflOpt is optional(especially if you're concerned about the licensing).
Theres already this option from within the web-interface called 'archive', under each world tab.
And if you want to execute it from the admin.sh file, its
./admin.sh archive one
#replace one with world number
this creates a full archive of your world, which is tar'red and gzipped, and can also be used with the 'import' button
Certainly, however I was suggesting something that decreases the size of the tar.gz file by 15-20%. Your focus on a small sized distro got me thinking that it'd be the best usage of the method in the instructions I linked. It would indeed work best with the "archive" command, seeing rdiff-backup would be confused by the recompressed .dat files.
I talked to the people on the server and they were fine with a new server.
So I made one.
This one though. Lag. Lag. Lag.
Same settings used and all, but it's just a lot of lag for some reason.
Any properties I could change to fix this?
Remember, the amount of RAM you allocate to your virtual machine is not automatically the amount of ram allocated to your minecraft world.
Even if you gave 2GB to your virtual machine (MineOS), the default world only uses 1024MB. This is changed from the admin interface 'server tab' where it says 'change mem'. If you allocated 2048MB to MineOS, you can reflect that here by putting "2000" in the argument box, and click 'change mem'
You can also change this in the admin.sh file
Aside from that, (and even if you didn't do this before), nothing has changed in the OS (no features added etc) that would cause crippling lag. Keep in mind, the laggiest part of any server ever (mineos or not) is the start, when people running off in new directions generates hundreds of new chunks---once your players regular boundaries are established, minecraft will only have to load, not generate and load.
I changed admin.sh, used "sudo filetool.sh -b", then rebooted. admin.sh was saved. I then updated the server files, used the filetool.sh again, and rebooted again. The server files were NOT saved. I also tried changing my crontab file, and again, the stuff wasn't saved when I used filetool.sh. What's wrong?
Oh, and if I set a crontab to run "sudo filetool.sh -b" every once in a while, would it work?
Okay, good that the admin.sh file is saving as you expect it now. Okay, then Ill let you in on a little more about how filetool.sh -b works.
When you run 'sudo filetool.sh -b', MineOS saves user-specific data (and stores it in a file called /mnt/sda1/tce/mydata.tgz ). On each reboot, the filesystem skeleton is lost and is regenerated from scratch (using MineOS settings). The last step of the reboot (before you have the bash prompt) is "filetool.sh -r" is called--restoring every one of those files to its place, as you expect it to be. This is by design so that even the most critical mistakes on Linux's filesystem can be undone with a reboot, while keeping all your adjusted settings.
The list of files that filetool.sh backs up and restores are located in /opt/.filetool.lst (vi /opt/.filetool.lst)
You can see that it backs up everything in the /home directory (and all subdirectories), your admin.sh file, your userfiles and passwords, your ftp and http config files, your crontab directory, and a few others.
You'll notice this does NOT contain the directory/the files of your minecraft server. That is because MOST installations of MineOS will be using a hard drive for its main storage--since main storage isnt lost on reboot, it doesnt need to be 'backed up'. Likewise, any files on your hard drive (/mnt/sda1) should remain, such as minecraft_server--whether or not you use filetool.sh
Are you using RAMDISK--or intending to? If so, may add to the /opt/.filetool.lst "/usr/games/minecraft/ram-worlds" directory to this file. And anytime you type 'sudo filetool.sh -b' (and only when!) it will include that directory and all its contents in the backup. (mind you, I believe the backup/restore method to be much more elegant and time-saving).
That said, let me know what kinda setup youre trying to aim for here, and I can help point you in the direction of every file I think you'd need to get this most effectively set up.
Oh no! I see the error i made! This would account for each reboot losing your crontabs! I'm backing up /var/spool/crontabs when it should be /var/spool/cron !! I'm so sorry! I'm correcting this immediately, and you should too immediately
{note: this only affects configurations that relied on crontabs and have been rebooted--all backups made before the reboot still persist, just the scheduled task ceased after the reboot. Regular backups using the backup button, the admin.sh backup one command, and the archive tab are all still operating precisely as expected} Correcting this immediately with the new ISO release that includes cartographer in a day or so.
I just want to reiterate my thanks for a job well done and also for the content of minecraft.codeemo.com in general. To put my money where my mouth is I sent over 10 bucks and I hope that others who use this will do the same.
Are you using RAMDISK--or intending to? If so, may add to the /opt/.filetool.lst "/usr/games/minecraft/ram-worlds" directory to this file. And anytime you type 'sudo filetool.sh -b' (and only when!) it will include that directory and all its contents in the backup. (mind you, I believe the backup/restore method to be much more elegant and time-saving).
...
Oh no! I see the error i made! This would account for each reboot losing your crontabs! I'm backing up /var/spool/crontabs when it should be /var/spool/cron !! I'm so sorry! I'm correcting this immediately, and you should too immediately
Yes, I am using RAMDISK. You should probably add a thing on the MineOS website that has the information on filetool.sh from your post.
About the crontab mistake: don't worry, everyone screws up at some point. Although some people might care about it more than I do.
Would adding a crontab for "sudo filetool.sh -b" to run every few minutes be a good idea?
Is there a tutorial for connecting to the virtual disk using FTP like it says for adding plugins to hMod?
Also a tip for your crontab tutorial:
instead of
0,15,30,45 * * * * /usr/games/minecraft/admin.sh backup one
to make a backup every 15 minutes, this also makes a backup every 15 minutes:
*/15 * * * * /usr/games/minecraft/admin.sh backup one
I know it did back up, I'm very sure of it, I checked the files before executing the command to roll back the server.
After executing and receiving the errors that I did, rechecking the back ups came up with the rdiff-backup directory thing.
If I knew how to find the virtualbox VM files, I would upload them. I am not familiar with any of this program, or system.
recreating the workbase that we've been working on for days is kind of a big deal.
The amount of glass, iron, lava, water, time and effort was kind of a lot.
If it comes down to it we'll just have to start fresh, which sucks, but >_<
--Upon trying to revert back to the last back up - cp: can't stat '/mnt/sda1/minecraft/archive/one' : No such file directory.
---Anything that I try to do, from the tutorial page, is telling me that /mnt/sda1/minecraft_____ doesn't exist pretty much.
----For the hell of it, I tried starting the world up, but "World one does not exist!"
http://imm.io/2RU3
The files I'm referring to exist on your host system. Using that screenshot, you can see that my world information is in "e:\folders\.virtualbox\harddisks" etc. The hard drive has an extension .vdi
The .virtualbox folder (and whatever your equivalent is), has a harddisk and a machines directory. The config file (.xml) and (.vdi) comprise your entire virtual machine. Stored in there is your minecraft partition etc.
The guide was really well done and easy to follow (even though I already have experience with Linux it helped a lot)
I have given tinycore linux a try before but it was tough since I use a wireless connection and that was impossible to set up without internet connection lol :L (at least that was what it was like in the firt release >.< I haven't tried it in a while)
Thank you very much for this :biggrin.gif: I love testing out distros and having one that is dedicated to minecraft is like a x2 goodness multiplier.
(I signed up to the forums just to reply to this thread xD)
Hey, extra thanks for going the extra mile to sign up just to say that--I'm doing all this for fun and though writing tutorials and helpdocs takes a lot of time, it's made worthwhile knowing its being useful and educational :smile.gif:
If you run across anything you think could use improvement, too, let me know--i want this to be the best possible way to host MC!
ayy lmao
Will do, I'll keep my eyes and ears open :biggrin.gif: though I have to say I think that you are most of the way there!~
Make sure you are un-mounting the OS image within Virtual Box .. this was what I was finding until I remembered to unmount it. So that it doesn't boot from the image, but instead from your install
Theres already this option from within the web-interface called 'archive', under each world tab.
And if you want to execute it from the admin.sh file, its
this creates a full archive of your world, which is tar'red and gzipped, and can also be used with the 'import' button
This is absolutely correct. The last step of the instructions is to unmount/eject the ISO and reboot. However, if the ISO remains mounted, it will continue to boot the CD and your adjusted settings will always be hiding underneath.
1) I assume to op yourself, you put in your 'minecraft login' in the arguments and hit 'OP', correct?
If you'd like to test this more, have minecraft logged into your server as you do this--the screen will verify that you have opped yourself correctly by showing "You've been opped!"
2) hey0 is the only add-on I have added thus far. Other addons are compatible, but you must follow their instructions to do so. As far as where the server files are (and presumably the addons youre tacking on), connect to your server via FTP. This is the root directory.
In this directory you'll see many things, the minecraft server jar, the hey0 server jar (if youre using it), your backup directory, etc etc. If your other addons require being in the same directory as your server jar, youd put it right there.
(if on the other hand youre talking about hey0 plugins, theres a plugin directory for that already existing)
I checked the settings in VirtualBox and the ISO is not mounted. I have no idea what the problem is. I like MineOS because when I ran a server directly from windows then tried to play on it, everything was super laggy and then minecraft crashed. When I ran a server from MineOS in VirtualBox on that same windows system, it ran smoothly. I would really like to be able to use this software. I appreciate your help, but it appears that the ISO is not the problem.
ayy lmao
If the ISO is, infact, unmounted, then it means the installation and booting from HD is complete. However, if the changes you made were while it was still booting from the ISO, any attempts to save 'sudo filetool.sh -b' would have been made to the ram-filesystem. Test it right now, since you can confirm the ISO is unmounted--make a single change to the admin.sh, run 'sudo filetool.sh -b' and reboot. The change should be reflected just fine.
I changed admin.sh, used "sudo filetool.sh -b", then rebooted. admin.sh was saved. I then updated the server files, used the filetool.sh again, and rebooted again. The server files were NOT saved. I also tried changing my crontab file, and again, the stuff wasn't saved when I used filetool.sh. What's wrong?
Oh, and if I set a crontab to run "sudo filetool.sh -b" every once in a while, would it work?
ayy lmao
Certainly, however I was suggesting something that decreases the size of the tar.gz file by 15-20%. Your focus on a small sized distro got me thinking that it'd be the best usage of the method in the instructions I linked. It would indeed work best with the "archive" command, seeing rdiff-backup would be confused by the recompressed .dat files.
Remember, the amount of RAM you allocate to your virtual machine is not automatically the amount of ram allocated to your minecraft world.
Even if you gave 2GB to your virtual machine (MineOS), the default world only uses 1024MB. This is changed from the admin interface 'server tab' where it says 'change mem'. If you allocated 2048MB to MineOS, you can reflect that here by putting "2000" in the argument box, and click 'change mem'
You can also change this in the admin.sh file
Aside from that, (and even if you didn't do this before), nothing has changed in the OS (no features added etc) that would cause crippling lag. Keep in mind, the laggiest part of any server ever (mineos or not) is the start, when people running off in new directions generates hundreds of new chunks---once your players regular boundaries are established, minecraft will only have to load, not generate and load.
Okay, good that the admin.sh file is saving as you expect it now. Okay, then Ill let you in on a little more about how filetool.sh -b works.
When you run 'sudo filetool.sh -b', MineOS saves user-specific data (and stores it in a file called /mnt/sda1/tce/mydata.tgz ). On each reboot, the filesystem skeleton is lost and is regenerated from scratch (using MineOS settings). The last step of the reboot (before you have the bash prompt) is "filetool.sh -r" is called--restoring every one of those files to its place, as you expect it to be. This is by design so that even the most critical mistakes on Linux's filesystem can be undone with a reboot, while keeping all your adjusted settings.
The list of files that filetool.sh backs up and restores are located in /opt/.filetool.lst (vi /opt/.filetool.lst)
You can see that it backs up everything in the /home directory (and all subdirectories), your admin.sh file, your userfiles and passwords, your ftp and http config files, your crontab directory, and a few others.
You'll notice this does NOT contain the directory/the files of your minecraft server. That is because MOST installations of MineOS will be using a hard drive for its main storage--since main storage isnt lost on reboot, it doesnt need to be 'backed up'. Likewise, any files on your hard drive (/mnt/sda1) should remain, such as minecraft_server--whether or not you use filetool.sh
Are you using RAMDISK--or intending to? If so, may add to the /opt/.filetool.lst "/usr/games/minecraft/ram-worlds" directory to this file. And anytime you type 'sudo filetool.sh -b' (and only when!) it will include that directory and all its contents in the backup. (mind you, I believe the backup/restore method to be much more elegant and time-saving).
That said, let me know what kinda setup youre trying to aim for here, and I can help point you in the direction of every file I think you'd need to get this most effectively set up.
Oh no! I see the error i made! This would account for each reboot losing your crontabs! I'm backing up /var/spool/crontabs when it should be /var/spool/cron !! I'm so sorry! I'm correcting this immediately, and you should too immediately
{note: this only affects configurations that relied on crontabs and have been rebooted--all backups made before the reboot still persist, just the scheduled task ceased after the reboot. Regular backups using the backup button, the admin.sh backup one command, and the archive tab are all still operating precisely as expected} Correcting this immediately with the new ISO release that includes cartographer in a day or so.
Yes, I am using RAMDISK. You should probably add a thing on the MineOS website that has the information on filetool.sh from your post.
About the crontab mistake: don't worry, everyone screws up at some point. Although some people might care about it more than I do.
Would adding a crontab for "sudo filetool.sh -b" to run every few minutes be a good idea?
Is there a tutorial for connecting to the virtual disk using FTP like it says for adding plugins to hMod?
Also a tip for your crontab tutorial:
instead of to make a backup every 15 minutes, this also makes a backup every 15 minutes:
ayy lmao