Image Store Corrupt - after latest svn update
-
I’m getting…
image store corrupt unable to locate mbr fog
after updating to the latest SVN on Ubuntu. Attached is my image. This worked before the update… I’m not sure which version I was on beforehand.
Thanks for any help!!
-
@GFm What is the exact error message?
What is the exact version (in the cloud?)
-
-
I rebuilt init’s to give us some more detailed output on that particular error. It should not fix the error, but it should give us some more information as to exactly where it’s failing.
Can you please update and try again if only to give us more informative data?
-
-
I had the same error with git6609 and git6621 - the image I had the error with, was created with git6547.
I tried a lot with ftp and other things, but in the end I think the update to git6609 deleted the “d1.mbr” files for all of the images. No image has these anymore (Single Disk, Multiple Partitions).
A newly created image (with git6621) is deploying right now without this problem.
The next days I can try if updating to a newer git version deletes the “de.mbr” again and report it back.
-
@tian I really hope we don’t delete those d1.mbr files on the FOG server. Are you sure they were there in the first place (when uploading with older versions)?
-
@Sebastian-Roth my older images are my issue… my newer ones are fine (the ones with the d1, etc.). The older ones for me only ever had what I posted above (I did check my backups).
-
Could be something different causing this - but for me is like I described before. Before I updated to git6609 I deployed the image with git6547 for a whole group, (unicast). An image created with a older git version also has no “d1.mbr”.
Even going back to git6547 didnt’ resolve this issue ( a simple reinstall, because there has been no database structure update since then)Was there a change in how images are created recently? Because option 2 (Windows 7, Single Disk, Multiple Partions) is always used to create images.
-
-
Same issue here as of SVN 6627.
-
@Tom-Elliott worked for me with 6627
-
@GFm So it worked?
-
@Tom-Elliott Yes, and also I just upgraded to 6629 and it worked
-
@Tom-Elliott Thanks for your help!!
-
@Tom-Elliott An old and the newly created image (without and with “d1.mbr”) have been deployed fine with version 6651. Thanks for fixing it that quick.
I just wonder why installing version 6547 again didn’t fix it before.
-
I get “unable to locate mbr” with build 6651
Before it worked like a charm…have to wait an update ?
-
@raumin error while deploying an image.
-
@raumin Pleas post the exact error you have on screen! I am sure it’s a longer error message as Tom added it to see what exactly is going wrong!
-
