Multiple problems with FOG after Upgrade.
-
@DarkEnergy said:
@ch3i
Looking at the image info, I got:
"Deploy MethodPartclone"
I am thinking the image should be ok as it is created with Partclone as well. After looking a several of my images, there are all created with Partclone imaging software.
How do I fix the issue?
Partclone is not an issue. Could you ls -l /images/a_bugged_restored_image
-
@ch3i
I already did a ls -ltr which display all the folders and subfolders under /images.
You are requesting another listing of the directories in a listing format. Which would be almost the same as the one I already provided. -
@DarkEnergy said:
@ch3i
I already did a ls -ltr which display all the folders and subfolders under /images.
You are requesting another listing of the directories in a listing format. Which would be almost the same as the one I already provided.I’ve a hard day today, where ???
-
Could you please do a debug deployment? There are instructions for this in the “Troubleshooting NFS” WiKi article. https://wiki.fogproject.org/wiki/index.php/Troubleshoot_NFS#Using_a_FOG_debug_deployment_for_testing_.28easy_.26_quick_way.29
There are some instructions in there for testing upload and download. Can you please follow those and see if they are successful?
-
@Wayne-Workman
Can you please clarify couple of point on this Wiki? Where is the directory being created? Where is the test.txt file located? is this in the server or in the client? Is this a SSH session to the server?
Currently I am getting an error but I am not sure if it is because I haven’t created the test.txt file.
The error is:
cp: cannot stat '/images/test.txt: no such file or directory@Wayne-Workman
Scratch the above, I was blind and lazy not to ready the whole article. I missed one point.
I was able to copy the text.txt file from /images to /images/dev/ through the client.
Anything else you would like me to try? -
@ch3i
No biggie. I totally understand.
It is below, scroll down until you see big bold letters for tftpboot directory.
The posts have not number so, it is hard to said exactly where. -
https://forums.fogproject.org/topic/4997/multiple-problems-with-fog-after-upgrade/19#
@ch3i said:@DarkEnergy said:
@ch3i
I already did a ls -ltr which display all the folders and subfolders under /images.
You are requesting another listing of the directories in a listing format. Which would be almost the same as the one I already provided.I’ve a hard day today, where ???
-
@DarkEnergy said:
@ch3i
I already did a ls -ltr which display all the folders and subfolders under /images.
You are requesting another listing of the directories in a listing format. Which would be almost the same as the one I already provided.The sub-folders are not included in your post.
ch3i was specifically wanting to see the permissions on the files inside the directory of a bad image - And I want to see them too.
Please post the ENTIRE output of this, do not cut anything out:
[CODE]ls -laR /images[/CODE]
If it’s too big to post, put the output into a txt file and upload here. I still think it’s permissions related.
It should also be noted that a simple following of recommended permissions would solve any issues with permissions:
[CODE]sudo chmod -R 777 /images[/CODE] -
@Wayne-Workman
In my post https://forums.fogproject.org/topic/4997/multiple-problems-with-fog-after-upgrade/10?page=2 it is described the permission in UNIX/Linux and how they are calculated.The more I try to use the images the more I discover issues with FOG, now I am getting that the MBR is corrupted and the cannot be downloaded.One of the systems is getting stock at
Using Hard Disk: /dev/sda
and does not continue to the next step until I pressed enter then I get:
Saving Partition Table (GPT)…Invalid Partition DATA!This happens during upload of a new image. I have deleted the old image and created a new one and still having issues.
I don’t see a way to upload a file here. In the old site it was easy to see the u
pload but in this new site I am still looking for the upload button to upload either riles or images.How ever the current permission is sett 777 as under fog and group root to /images. I am not sure what would be the other way.
-
@DarkEnergy Your particular upload issue means the disk has GPT partitions on them where they’re not expected to be.
The current inits attempt to see and fix this for you, but it seems that isn’t working. You will need to put system you’re trying to upload from in an upload-debug state. Once at the prompt, run
fixpartsand accept the things it asks.From there, once fixed, you can type
fogand it should begin the upload process without hanging.To upload a file, there is an icon that has an up-arrow on it. Hopefully that helps.
-
@Wayne-Workman
Files permissions are inherited from the folders unless manually modified. As Tom recommended earlier using the chmod -R which the -R is for recursive with indicates all folders, subfolders and files. -
@Tom-Elliott
Thanks, finally found it. -
@DarkEnergy I’m assuming you mean the upload debug?
For all persons, the Trunk versions of fog make debug tasks a simple check box on any of the tasks. The 1.2.0 they’d have to go to advanced and choose the Upload/Download - Debug (depending on which way they’re trying to go with the image).
-
@Tom-Elliott
When asking for a file name, which file name is to be provided? There are about four possible file names:
There are three files in the directory
The name given to the image in FOG Web GUI.Thanks in advance.
-
@DarkEnergy What do you mean? I wasn’t asking for a file at all, that I’m aware of.
I was just trying to point out, for the forums, there’s an Upload Files icon on the reply/post options.
-
@Tom-Elliott
In your post:
https://forums.fogproject.org/topic/4997/multiple-problems-with-fog-after-upgrade/36?page=1
When running fixparts it ask for the name of the file, which name would that be? -
Sorry,
It shouldn’t have just been fixparts.
The command would be:
fixparts <path/todevice>Most typically it would be
fixparts /dev/sda -
First I want to thank you for your assist. The last tip fix the last issue I was having with the imaging.
It was a GPT table left over, wire, as that machine had EUFI disable. Now I am working good again on those images. I just have one left but I think it is Windows 8.1 issue and not FOG.Thanks again.
-
I’m going to solve this post.
I imagine the (“System in hibernate”) or (“Please run fsck/chkdisk”) is related to windows 8 specifically as you pointed out.
-
I agree.
Thanks.