Can't read the following volume file
-
Just in case anyone else gets this error, one thing I’ve found is that the image file names are case sensitive. Adding the name manually in the wrong case will result in the above error - so check the actual name of the file in /images/ and ensure the file name matches exactly in the fog web interface.
-
Getting this error now…
After a Ubuntu Update. The image starts deployement and then it stops at 17% - 80% on different image files.To get fog working what’s the trick? (never update ubuntu?)
Trying to solve issue… if anyone can help… thanks in advance!
-
Fred, i don’t see how your problem relates to the ones being discussed here… You may want to post your own thread instead of hijacking a thread.
UNLESS you were getting the errors mentioned above BEFORE you updated. In which case you should include that info in your post as just saying “my fog is broke” is not going to help us in resolving your issue.
-
Hi Travis,
I’m just sharing that i have the same problem like the others that no one can resolve. I’m always trying to solve this but without success for now.
I have updated the Ubuntu (security updates, …) an then i can upload a new image, but not deploy it because after some time deploying the new image, it stops with following error:
[SIZE=6][B]“Can’t read the following volume file”[/B][/SIZE]When i said, “getting this error now” i’m saying that i have the error mentioned in this post. Because before this error i had some others errors, and i solved them. With this one i’m blocking.
-
Fred,
When you updated ubuntu, did nfs-common or nfs-kernel-server get updated as well?
When you performed the updates, did you restart your system, or just update and keep going?
-
[quote=“Tom Elliott, post: 25061, member: 7271”]Fred,
When you updated ubuntu, did nfs-common or nfs-kernel-server get updated as well?
When you performed the updates, did you restart your system, or just update and keep going?[/quote]
Well, i think that the nfs-kernel-server was updated because no-one for 1 year looked at this server. I was in charge of that but now i’m working in another company.
Of corse, i restarted the server, it causes some error on disk (it’s a vm) an i fixed that on ubuntu boot menu.
After that, it restarts correctly and fog is running. Otherwise the deploy function stops always after some time with the error.Regards,
Fred -
I don’t know what changes were made directly, so you may be better off, if at all possible, recreating the image and uploading over the current file. I’ve seen similar issues on my boxes that the images just basically no longer work. Mine where due to glusterFS which I’ve since moved to just a local storage to contain the files needed. I still had to upload over all my original files to get things working again. It seems, to me, that something doesn’t like the way the files were originally stored and causes, what looks like to me, almost like the inode table is corrupt for the file itself. It gets to a certain point and says error: corrupt read at blkid 206972, or some other number. Varying percentages as well.
-
Hmm i see, But i already tried that. I also try with different images and pc’s to upload an then, re-deploy. The upload works properly, but the deployment doesn’t.
in case i can’t solve the problem, I’m looking forward to install a new fog server with 0.33 and make a standard config for the server, and backup it every weeks. Wich system and version do you recommend?
Ubuntu 10, 11, 12 ?
Debian 6, 7 ?
RH … -
I use Ubuntu 10.04
I also have Ubuntu fog servers on 12, and 13I would recommend any of these for building a FOG server.
-
Ultimately, this is a modern FOG, so I’d recommend a modern OS level for 0.33.
It really doesn’t matter which OS, though I’ve really only tested thoroughly on CentOS as that’s what I run at home. I’ve performed a few installs on Ubuntu and Debian so far, and others have done so on Mageaia (or however it’s spelled). It seems to work well from what I have seen, on all systems.
