Issues with disk in an unsafe state
-
@wayne-workman changing that option on the image worked. thanks for the help.
-
@sjensen Can you help us troubleshoot what’s going wrong with the resizable feature? We’ll ask you to follow some instructions and you’d screenshot/copypaste the output as we go along.
-
@wayne-workman ok i spoke too soon. When I choose the not resizable option Fog wants to clone the entire disk, i do not have that much space on my Fog server. I need the image to only use the size that is used. Anything else I can try?
-
@sjensen said in Issues with disk in an unsafe state:
When I choose the not resizable option Fog wants to clone the entire disk, i do not have that much space on my Fog server.
All FOG image types except for RAW are compressed, and empty space compresses really well. I suggest you go ahead and try it. You can also shrink the partitions using windows beforehand also. Or, you can wait for help from @Sebastian-Roth or @Tom-Elliott
-
@wayne-workman Wayne yes i can help you
-
@wayne-workman I can wait for a little while. I would like to get this fixed, as I may have more of these Samsungs.
-
@sjensen said in Issues with disk in an unsafe state:
When I choose the not resizable option Fog wants to clone the entire disk
What exactly do you mean by that? Sure FOG wants to clone the whole disk but as Wayne said it only reads the blocks used by files/directories. So the resulting image is way smaller than the partition. What could cause a RAW image is if your drive is bitlocked - see here: https://forums.fogproject.org/topic/10824/image-upload-deploy-taking-a-long-time
As well check to see if fast boot is on. This can cause some major trouble as well!!
-
@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.