FOG restore only one partition
-
Can you try using this script in your /images/postdownloadscripts/revertbcd
#!/bin/bash [[ $osid != [5-7] ]] && return getHardDisk getPartitions $hd for part in $parts; do fsTypeSetting "$part" [[ $fstype != ntfs ]] && continue dots "Mounting Partition" if [[ ! -d /bcdstore ]]; then mkdir -p /bcdstore >/dev/null 2>&1 case $? in 0) ;; *) echo "Failed" debugPause echo " * Could not create mount location" return ;; esac fi ntfs-3g -o force,rw $part /bcdstore >/tmp/ntfs-mount-output 2>&1 case $? in 0) echo "Done" ;; *) echo "Failed" debugPause echo " * Could not mount $part to /bcdstore" continue ;; esac if [[ ! -f /bcd/Boot/BCD.bak ]]; then umount /bcdstore >/dev/null 2>&1 continue fi dots "Restoring original BCD" mv /bcdstore/Boot/BCD{.bak,} >/dev/null 2>&1 case $? in 0) ;; *) echo "Failed" debugPause umount /bcdstore >/dev/null 2>&1 echo " * Could not revert BCD File" continue ;; esac echo "Done" debugPause umount /bcdstore >/dev/null 2>&1 done
Change the file to allow the script to run as a script
chmod +x /images/postdownloadscripts/revertbcd
And add to the /images/postdownloadscripts/fog.download
. ${postdownpath}revertbcd
-
@Sebastian-Roth said:
After reading through most of your posts again I noticed that I probably missed a very important detail. You have two different systems, one WinXP and one Win7 but both having three partitions! I somehow got confused by the different sector counts but same number of partitions…
Yes as you said i made tests with 2 machines but each time i precise in my post wich machine i use
At this time i’m testing on a WIndows 7 machine
I made what you ask me to do and i come back -
@Tom-Elliott Hello
you mean /images/postdownloadscripts/fog.download => /images/postdownloadscripts/fog.postdownload ??
I’m actually deploying image ghost on this machine -
@Tom-Elliott Hello
then i added the script into/home/images/postdownloadscripts/revertbcd
then
chmod +x /home/images/postdownloadscripts/revertbcd
and
add to the /home/images/postdownloadscripts/fog.postdownload . ${postdownpath}revertbcd
ls -al /home/images/postdownloadscripts/ total 16 drwxrwxrwx 2 root root 4096 mars 7 13:59 . drwxrwxrwx 7 root root 4096 mars 7 10:24 .. -rwxrwxrwx 1 root root 260 mars 7 13:59 fog.postdownload -rwxr-xr-x 1 root root 1279 mars 7 13:52 revertbcd
cat /home/images/postdownloadscripts/fog.postdownload #!/bin/sh ## This file serves as a starting point to call your custom postimaging scripts. ## <SCRIPTNAME> should be changed to the script you're planning to use. ## Syntax of post download scripts are #. ${postdownpath}<SCRIPTNAME> . ${postdownpath}revertbcd
but same problem
-
@Sebastian-Roth said:
mkdir -p /ntfs ntfs-3g -o force,ro /dev/sda3 /ntfs find /ntfs -type f -iname "SYSTEM"
find /ntfs -type f -iname “SYSTEM”
/ntfs/Windows/System32/config/RegBack/SYSTEM
/ntfs/Windows/System32/config/system -
@plegrand My intuition was right… This is one thing I hate about windows. It does not care much about case-sensitivity in filenames and paths! Someone or some tool made a backup of the original reg-file called ‘SYSTEM’ but named the new file ‘system’. Windows seams to not care and still boots. But FOG/linux cares about it. We have the path for this defined as ‘/ntfs/Windows/System32/config/SYSTEM’ and therefore our scripts won’t find ‘…/config/system’!
I am not sure what to do about it. I don’t think we should change our scripts as this has never happened before and I guess this is very rarely the case. But it’s kind of easy for you to fix. After restoring the Win7 image via ghost please boot in debug upload again and run:
mkdir -p /ntfs ntfs-3g -o force,rw /dev/sda3 /ntfs mv /ntfs/Windows/System32/config/system /ntfs/Windows/System32/config/SYSTEM.moved mv /ntfs/Windows/System32/config/SYSTEM.moved /ntfs/Windows/System32/config/SYSTEM umount /ntfs
I guess you can rename the file directly from ‘system’ to ‘SYSTEM’ but I have seen cases (probably on VFAT filesystems) where this fails - therefore I suggest two renames. After that you can start the upload via command
fog
… -
@Sebastian-Roth Hello
then after restoring ghost image i launch debug capture task and thenmkdir -p /ntfs ntfs-3g -o force,rw /dev/sda3 /ntfs find /ntfs -type f -iname "SYSTEM" /ntfs/Windows/System32/config/RegBack/SYSTEM /ntfs/Windows/System32/config/system mv /ntfs/Windows/System32/config/system /ntfs/Windows/System32/config/SYSTEM.moved mv /ntfs/Windows/System32/config/SYSTEM.moved /ntfs/Windows/System32/config/SYSTEM find /ntfs -type f -iname "SYSTEM" /ntfs/Windows/System32/config/RegBack/SYSTEM /ntfs/Windows/System32/config/SYSTEM umount /ntfs/
fog to launch capture task
reboot
After capture windows 7 works fine.Deploy task
Same problem : stuck on “booting …”I keep the Tom’s script (revertbcd) may be i should remove it ?
-
@Sebastian-Roth May be i could give you access to this machine if it’s usefull ?
-
Definitely was useful to get access to the machine. That particular partition layout turned out to be not very easy to handle and FOG stumbled! Those DELL partitions are quite an issue. But I think Tom and I have fixed it all. @plegrand Please upgrade to the very latest version. Then re-upload and try deploy again! Please test both of your machines to see if this is really the same issue.
-
@Sebastian-Roth Hello
do i have to keep the “revertbcd” script ? -
@plegrand Please try without it first!
-
@Sebastian-Roth argh …
for this test i let it … -
@Sebastian-Roth Hello
- The “revertbcd” script of Tom is still present, i didnt know if i had to remove it
- Upgrade to 4981 / 6663
- Remove old image with file
- Create image
fog-windows7 - 15
default: Windows 7
Single Disk - Resizable
Everything - Associate image to client
- Launch Basic task capture
- Capture works fine and windows start normally
- Launc basic task deploy
- … It works !!!
-
- I removed the “revertbcd” script of Tom.
- Remove old image with file
- Create image
fog-windows7 - 16
default: Windows 7
Single Disk - Resizable
Everything- Associate image to client - Associate image to client
- Launch Basic task capture
- Capture works fine and windows start normally
- Launc basic task deploy
- … It works !!!