Issues with disk in an unsafe state
-
@sebastian-roth I do not have fast boot enabled. When I started the clone the size of the image said it was going to be over 200gb, that was on the clone machine and in the fog server under images. I can try the clone again and send screen shots. I do not have bit locker enabled.
-
@sjensen said in Issues with disk in an unsafe state:
I do not have bit locker enabled.
Please double check and read the thread I mentioned! I have seen people saying that they don’t use bitlocker but still the partitions were bitlocked… Kind of the same with fast boot - as this is definitely re-enabled when doing a major windows update!
-
@sebastian-roth I double and triple checked the settings in bit locker and the boot settings nothing mentioned is enabled.
-
@sjensen Which version of FOG do you use?
-
@sebastian-roth 1.3.0
-
@sjensen Unfortunately we don’t have enough resources to support older versions of FOG. Please upgrade to 1.4.4 at least! The error mentioned is not present in 1.4.4 and newer versions!
-
@sebastian-roth the last time i updated something went wrong and Tom had to help me reinstall a bunch of things. Do you guys support if the upgrade goes wrong?
-
@sjensen And the new version support Ubuntu 14.04?
-
@sjensen Yes FOG 1.4.4 supports Ubuntu 14.04, but nothing older than 14.04. That doesn’t mean you won’t have update issues.
As always, I would ensure you have a good backup before updating. That is standard practice. -
@sjensen said in Issues with disk in an unsafe state:
Do you guys support if the upgrade goes wrong?
Sure, we will do what we can to help people get to the new version. But as George said, making a proper backup is up to you. We can only help you fix things but data recovery is way beyond that.
-
@sebastian-roth What’s the best way to backup a fog server?
-
@sebastian-roth Since my Fog server is a virtual machine do consider creating a snapshot a good back before updating Fog?
-
@sjensen Yes a snapshot would let you roll the changes back to a known good condition. Just don’t forget to integrate your snapshot into the VM once you have proven that the update is successful.
-
@george1421 thanks. Do you guys have a guide to walk me through the upgrade process? I am still very new to Linux and dont quite understand whole process.
-
@sjensen said in Issues with disk in an unsafe state:
Do you guys have a guide to walk me through the upgrade process?
We have three guides:
-
@sjensen The first link that Wayne posted speaks directly to your need. Just don’t execute any
git checkout xxxxxcommands unless you want to upgrade to a development release. I can say that 1.5.0 RC10 (git checkout dev-branch) is pretty stable and does fix a few issues that exist in 1.4.4. stable. -
@wayne-workman I got the update installed and i am uploading an image from the Samsung laptop now. One question at the tail end of the install it did say that a backup of the database failed. Is there something I can in order to be able to backup the database? Or do i not need to worry about this?
-
@sjensen said in Issues with disk in an unsafe state:
One question at the tail end of the install it did say that a backup of the database failed.
That’s not the end of the installation… inside of
fogproject/binthere’s a new directory created in there after you’ve ran the installer once, it should be called ‘errors’ or something. But anyways, go into that directory and there will be an output file form the installer. Towards the end of the most recent one, you’ll find the error causing the database backup problem. -
@wayne-workman The reason why the database backup failed is because it is trying to connect to an ip address that dhcp assigned to the server at some point during the install. http://192.168.xx.xx//fog//maintenance/backup_db.php
I’m not where to change this ip address at.
-
@sjensen said in Issues with disk in an unsafe state:
I’m not where to change this ip address at.
It’s in
/opt/fog/.fogsettingsit’s the field calledipaddress=