FOG restore only one partition

[plegrand]

@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

[Sebastian Roth]

@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…

[plegrand]

@Sebastian-Roth Hello
then after restoring ghost image i launch debug capture task and then

mkdir -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 ?

[plegrand]

@Sebastian-Roth May be i could give you access to this machine if it’s usefull ?

[Sebastian Roth]

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.

[plegrand]

@Sebastian-Roth Hello
do i have to keep the “revertbcd” script ?

[Sebastian Roth]

@plegrand Please try without it first!

[plegrand]

@Sebastian-Roth argh …
for this test i let it …

[plegrand]

@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 !!!

[plegrand]

@Sebastian-Roth

• 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 !!!