Posts made by stormbyte

@tom-elliott thanks Tom! ok it’s working now, I forgot to change from dev branch to working one since my latest trouble. Everything is fine now! keep on good work!

Hi!

Using FOG since years without any trouble. Upgrade was done 2 days ago from 1.5.0 RC4 upto RC9.

First I had the isbitlockedpartition error and I solve it using your thread https://forums.fogproject.org/topic/11017/isbitlockedpartition-error

But now the main remains: all client are considered as the same! I can’t capture/deploy because PXE is not recognizing the active tasks for the computer.

Example:
launching a capture for computer TRAINING5
on TRAINING5 pxe is not recognizing the task (MAC is correct) and launching standard disk OS
then going on TRAINING5 PXE FOG menu and I see ‘Host is registered as TRAINING1’ !!! (and not TRAINING5!)
-> MAC adresses are different between TRAINING1 / 5 and correctly configured under FOG

I’ve made many tests with 10 workstations/client, it’s the same FOG is not identifying correctly the computers.
FOG environment is working since years now, everything was checked (DHCP, FW, etc.) and nothing was moved since FOG 1.5.0 RC4 -> RC9 upgrade

In order to test again I then launched a task for TRAINING1, and it was correctly launched. So FOG is considered all my network as TRAINING1 hostname despite MAC?? (never had trouble before! each computer is technically the same, SHUTTLE mini PCs)

Then I delete all my 12 clients under FOG.

Having an emmpyt inventory, I then put only the TRAINING6 computer. I was able to launch taks, capture, etc.
I then put another client TRAINING2 in the inventory. I try to launch tasks, and it was not working again.
Again, PXE menu on TRAINING2 is whosing ‘Host registered as TRAINING6’ (and not TRAINING2!)

How to solve this?:

• Downgrade?
• Purge database (I’ve checked database maintenance script but it’s not mentionned under 1.5.0 https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL)

Thanks for your expertise and feedback!

@Tom-Elliott Error message is: "Attempting to expand/fill partitions…awk: /usr/share/fog/lib/procsfdisk.awk:280: fatal: cannot open file ‘1:’ for reading (No such file or directory)

By the way the d1.fixed_siez_partitions already have a 1: inside… I just added a new one that created the error message above and it’s working fine

Here is the d1.fixe_size_partitions used:
0_1455648147461_d1.fixed_size_partitions

@Tom-Elliott You’re the boss Tom I’ve added a :1 at the end of the d1.fixed_size_partitions and it’s working! Installation is OK, no problem for partition anymore.

BUT your solution is throwing an error just before the partclone (I didn’t catch it, it’s really fast on screen - if you need it I can record a video). Due to :1 … any chance to include this into a future FOG release or do I need to manually change my file for each capture?

Also, this solution is working for both resizable / not resizable captures ???

@Tom-Elliott Tom, I’ve updated but the problem is exactly the same … I’m ready to try your other suggestion!

@Tom-Elliott no problem Tom, there’s a life outside FOG world! please just tell me when you will deliver a new release to solve this problem, and thanks again for your time. I’m ready to make new tests if you need. Kind regards

@Tom-Elliott answer: 512

@Tom-Elliott of course Tom, I’ve launched the station with debug mode. What command I should enter then on the workstation?

@Tom-Elliott unfortunately, same problem same error during partclone… what’s the next step?!?

@Tom-Elliott ok sorry result in 2mn

@Tom-Elliott GIT PULL is showing ‘already up-to-date’ … do I need to wait some time before being able to catch your modifications? It seems there’s no modification of code (I already GIT PULL an hour ago to solve the GPT/MBR error). Thanks to tell me please how to proceed to force GIT PULL to catch your latest changes.

@Tom-Elliott OK I do this from now. Just give you a feedback in some minutes.

@Tom-Elliott Thanks!

@Tom-Elliott I’ve no information about the chunk size of each sector. Configuration is definitely by default. How can I check this and give you the information? (what tool to use?)

How do you think I can check/resize/change this strange sector behavior under Windows? (I’ve many tools by hand, but I don’t know which one to use!

Another infos: I’ve checked previsely all FOG messages during launch and import on client, there’s one showing at the first PXE beginning:
“EXT4-fs (ram0):couldn’t mount as ext3 due to feature incompatibilities
Populating /dev using udev: udev[2357]: error creating epoll fd: Function not implemented”
I read on other topics that normally I don’t have to take into consideration those messages, hope I’m right.

Here is the screenshot of the error I’ve just downloaded it: http://www.hostingpics.net/viewer.php?id=47018020160213180322.jpg

And another one: http://img4.hostingpics.net/pics/126443201602131803071.jpg

Thanks for your feedback and expertise Tom!

PS: do you think there’s a tool to change the start sector from 8 to 63??

@Tom-Elliott Thanks Tom for your really fast feedback and action. So I’ve updated my FOG. This error message doesn’t exist anymore BUT … there’s another problem…

I’ve taken last capture from W7 and W2K12: no more GTP/MBR problem.

BUT when FOG is trying to use partclone it shows:
'Calculating bitmap… Please wait… Target partition size(367MB) is smaller than source (367MB). Use option -C to disable size checking (Dangerous).

That’s weird because I used ‘Single partition/Resizable’ for capturing the computer’s image !!

What can I do / try / ? Waiting to read you, and again thanks for your fantastic work!

PS: some infos about the computers, they’re SHUTTLE XPC boxes (core i5, 8GB RAM, etc) BIOS is using standard parameters and disks are 120GB SSD (Samsung/Corsair). Nothing unusual.

@Sebastian-Roth Excellent news Sebastian! thanks a lot for your time and investigation I’m happy to see the problem is not coming from my side (I was desesperated!)

@Tom-Elliott Hi Tom! Please could you tell me when do you think this fix will be available? Thanks for your help! Kind regards.

@stormbyte
I’ve just made another clone from W2K12 with Single Disk/Resize from scratch (new Image and not importation from previous one) and it’s still the same. I’ve also tested to import to different computers, each time it’s the same error message…

please help to solve!

@Sebastian-Roth
Sebastian,
Here is the directory content:
-rwxrwxrwx 1 root root 4096 Feb 11 15:06 d1.mbr
-rwxrwxrwx 1 root root 210242095 Feb 11 15:07 d1p1.img
-rwxrwxrwx 1 root root 12707118330 Feb 11 15:26 d1p2.img
-rwxrwxrwx 1 root root 190 Feb 11 15:06 d1.partitions

and also the files you asked for:
1_1455366016116_d1.partitions 0_1455366016115_d1.mbr

First I made a clone with Single Disk/Multiples partitions(not resizable), then after many actions (fixparts/etc.) I then capture again the same computer using Single Disk Resizable. So I think that FOG has deleted the previous ones. Am I wrong?

I can delete everything and make again the test if you need the result!

Waiting for your orders!

@Sebastian-Roth

Thanks for your fast answer.

Here is the result of the command:
-rwxrwxrwx 1 root root 4096 Feb 11 15:06 /images/W2K12CEHbase/d1.mbr

What can I do now from my side?

Hi all!
I’m using FOG on latest trunk release with a DEBIAN 7.9 since 1 week: it works well except on 2 computers I had to clone, which are similar to the others (I’ve 10 computers with exact technical configuration)

First computer I need to clone is having a W2K12 without other stuff. The other computer is a simple W7.
Disk are 120Go SSD. But before trying to clone I was obliged to made a change on them to delete a partition for cloning:
Before: (SYSTEM RESERVED 300Mo) (PARTITION#1 WINDOWS W7 80Go) (PARTITION #2 WINDOWS 7 40Go)
After: (SYSTEM RESERVED 300Mo) (PARTITON#1 WINDOWS W7 120Go) -->> this is what I’m trying to clone!
I kept only the first partition on the disk. (I used windows for this partition deletion/partition resize)
So each one has now its own first partition System Reserved and the rest of the 120Go SSD disk drive for the second partition (only 20Go of data used on the disk).

Uploading to FOG is no problem, I’ve checked the files and they are correctly located to /images.
I’m using Single Disk, Resizable partition and made also the test with Single Disk, multiple partition (not resizable).

When I’m trying to deploy those images to other computers I see this STRANGE error message: ERROR TRYING TO RESTORE GPT PARTITION TABLES (restorePartitionTablesAndBootLoaders) / Restoring Partition Tables (GPT): du: cannot access ‘/images/W2K12/d1.grub.mbr’ : No such file or directory
http://www.hostingpics.net/viewer.php?id=777518201602121815031600x1200.jpg

Why FOG is showing ‘Restoring Partition Tables (GPT)’ ?? I have no GTP on it! I’ve checked on many posts here, and I used the FOG debug mode to send a FIXPARTS command many times, without any success… I’ve tested also the REPAIR disk on Windows to send BOOTSEC /FIXMBR and so on, without success…

FOG is showing on the screen ‘/images/W2K12CEHbase/d1.grub.mbr’ -->> this file doesn’t exist in FOG files!! That’s weird? Why it’s searching for something that doesn’t exist??!

I’m lost on this error, I spend many hours trying to correct it… What can I do now?? (ok I can reinstall again my 2 windows with stuff on it, but if this problem appears again…

Thanks for your help, tips, etc…! I’m ready to test all solutions!
Have a nice week-end!