Unable to locate image store on download
-
@Sebastian-Roth Thanks i’ll check that!!
-
Unfortunately it’s still not working. The crazy thing is, when I copied the folder from /media/external to /images it restored one time. /images is not even on the list of storage nodes anymore, and all images where created AFTER I setup the new node and delete /images. I thought I could hobble through things by manually copying the files over for the time being, but after that first restore job that worked, now it doesn’t download at all. When I do a download task and use debug so I can watch it, it just has three hit enter to continue with no text then says that it’s complete. Nothing actually happened. I hate to be a bother, just can’t seem to get this thing working fully…
-
@mobile_bob can you check your exports file? Make sure it’s pointing to the right locations.
cat /etc/exports
If that’s the issue, edit your/opt/fog/.fogsettings
file to point to the right directory for the exports file.
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_NFS -
@Wayne-Workman said:
@mobile_bob can you check your exports file? Make sure it’s pointing to the right locations.
cat /etc/exports
If that’s the issue, edit your/opt/fog/.fogsettings
file to point to the right directory for the exports file.
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_NFSIt still had pointers to the /images folder in the export file. I deleted those, and it may have fixed the problem, but it’s hard to tell because the download jobs are not doing anything anymore… They just flash past and the task is deleted. If I do a debug download it just says press enter a few times then says it’s done without partclone coming up.
-
I’m so confused. Where did the information about the nfs mounts come from? It should be /images by default. How did we know it was going elsewhere?
-
@Tom-Elliott said:
I’m so confused. Where did the information about the nfs mounts come from? It should be /images by default. How did we know it was going elsewhere?
Unfortunately I have been doing a lot of poking around and following tutorials online (Probably made changes I shouldn’t have). I had added /media/external to the /etc/exports file previously. I copied the default ones and just added two more with the same settings. I later added a new storage node pointing to /media/external, and deleted the /images. Not sure if that was supposed to alter the /exports or not…
-
@Tom-Elliott We were taking information from his previous thread here: https://forums.fogproject.org/topic/6362/upload-never-gets-moved-out-of-the-images-dev-folder
-
@Wayne-Workman said:
@Tom-Elliott We were taking information from his previous thread here: https://forums.fogproject.org/topic/6362/upload-never-gets-moved-out-of-the-images-dev-folder
Yes thank you. I should have reposted that info…
-
You might be able to get useful information if you check out the client’s POST requests – if you have any type of switch that can mirror traffic for you, mirror the client’s traffic to a machine that’s just running tcpdump/wireshark, then do an upload/download while capturing to see exactly what’s going on. I was able to fix quite a few issues for my setup and it was pretty easy to see what was going wrong (e.g. the client was sending FTP requests to the wrong server, the client was accessing an HTTP path that didn’t exist, etc).
-
He’s using Fog 1.2.0 and I’m fairly certain that the computers he captured from had GPT type disks with about 5 partitions on them.
He’s using non-resizable images.
I was able to help him solve the “Unable to locate image store” error, that was a simple permissions/ownership issue (and the “test” image he was trying to deploy was not a valid image).
During a debug download - when it tries to restore the partitions, there’s just no output at all and he hits enter 3 times (for each partition?) and then the task completes without anything being done besides clearing the MBR and whatnot…
Hopefully the @Developers can chime in on this one, because @mobile_bob has spent weeks trying to get FOG 1.2.0 going and he’s basically given up, and I’m not sure what’s wrong besides the fact that I think the golden-machine has GPT disks. I’ve asked him to try FOG Trunk and he politely declined.
-
Thanks Wayne for your debug work and research on this. Good to know a little more of the details. As you know FOG 1.2.0 uses fogpartinfo tool to enumerate disks and partitions (where FOG trunk uses lsblk now). So on deploy FOG writes the MBR and then tries to enumerate the new partition layout just being written. When you don’t see partclone coming up at all this sounds like fogpartinfo cannot properly read the partition layout. It’s kind of odd because it sounds like it can when uploading?!
@mobile_bob Can you please upload the (very small) file
/images/<name of your image>/d1.mbr
(it’s on your FOG server)? I will have a look and hopefully can find out if there is something “wrong”. -
I want to thank everyone for their hard work on this project!! I really love this project and have already told others about it. I think my real issue is that I’m not on Trunk… I know it would be better for everyone if I went to Trunk, but since it doesn’t seem like you have any sort of snapshots (a known working trunk version) I feel like by luck i’m going to step into some unknown dev bugs and cause even more problems. I have decided to move my current project to a commercial offering, but will be following this FOG’s development and plan to use it in future on other projects. Again you guys have put together such a great project and I support open source whenever I can. I can’t wait to see it grow and get better and will be watching for the next stable release. Thanks again to @Wayne-Workman for all his work on this and everyone else who tried to help. @Sebastian-Roth if it will help I can still upload the mbr file, but only if it will help others. At this point I don’t want to waste anyone else’s time.
-
@mobile_bob It’s up to you. Feel free to upload the MBR file and I’ll have a look. Might be helpful to other users but can’t say for sure before I have seen the file (might find nothing unsuspected).