Real Issues with first image attempt
-
First of all client in question is a windows xp box 80 gb hard drive with about 60gb used
I performed an image upload of the single disk, the first attempt I tried single resizable and fog failed to image the drive. Second attempt I tried multiple (thinking about the the recovery partition) not resizable. This mode appeared to work fine Great until the client attempted to reboot.Totally hosed up, even goback could not repair the issue. Did a console recovery chkdis /p and it found all kinds of unhappy stuff and still not booting so I am going to try a recovery install.
In the mean time I pulled another (these are lab boxes so I have a few of the same) HD and thought well let’s see if I can deploy the image I just created and maybe the image is alright. No joy here either. When I attempt to deploy fog gets to a line stating it could not mount sr0 and was mounting it read only (/dev/sda was imaged) and after the mounting read only it sets for a few seconds and then pronounces the task done! only it did nothing at all. Now just to make sure the drive was ok I booted to windows with the second drive just fine. Tried again same thing
So ssh to the fog server and check for images. When I pulled the image it did three passes the first pass being 67gb the image was (supposedly) 16gb, second was about 2gb and I don’t recall the third. I see nothing at all about images in the web interface under the /images/DFNSA directory I see
-rwxrwxrwx 1 root root 512 Mar 10 18:31 d1.mbr
-rwxrwxrwx 1 root root 7.4G Mar 10 18:45 d1p1.img
-rwxrwxrwx 1 root root 2.2G Mar 10 18:49 d1p5.imgObviously none of them is 16gb (compressed?) but why is fog not even attempting to deploy them and what on earth did it do during the upload process that crushed my HD’s file system? One would think the imaging process would be done in read-only mount? I have absolutely no idea as to where to go here but I am very hesitant to allow fog to touch a machine I really care about at this point.
-
[QUOTE]I performed an image upload of the single disk, the first attempt I tried single resizable and fog failed to image the drive[/QUOTE]
Any more information?
What version of FOG?
Did it attempt to upload as raw filesystem/fat32/ntfs etc?
How many partitions did the drive have and what filesystems did they have?[QUOTE]Did a console recovery chkdis /p and it found all kinds of unhappy stuff and still not booting so I am going to try a recovery install.[/QUOTE]
The drive could be faulty.
Otherwise “/fixboot C:” & “/fixmbr C:” from the recovery console might make it boot again.[QUOTE]When I attempt to deploy fog gets to a line stating it could not mount sr0 and was mounting it read only[/QUOTE]
I believe this could be your CD drive.What is your intended use for FOG? are you using it to try and backup, or trying to create images for deployment?
It is much more convenient to create images in VMware/Virtualbox and use the snapshot feature in case things go wrong. Will save a lot of time. -
[quote=“Rick Cooper, post: 23930, member: 22803”]First of all client in question is a windows xp box 80 gb hard drive with about 60gb used
I performed an image upload of the single disk, the first attempt I tried single resizable and fog failed to image the drive. Second attempt I tried multiple (thinking about the the recovery partition) not resizable. This mode appeared to work fine Great until the client attempted to reboot.Totally hosed up, even goback could not repair the issue. Did a console recovery chkdis /p and it found all kinds of unhappy stuff and still not booting so I am going to try a recovery install.
In the mean time I pulled another (these are lab boxes so I have a few of the same) HD and thought well let’s see if I can deploy the image I just created and maybe the image is alright. No joy here either. When I attempt to deploy fog gets to a line stating it could not mount sr0 and was mounting it read only (/dev/sda was imaged) and after the mounting read only it sets for a few seconds and then pronounces the task done! only it did nothing at all. Now just to make sure the drive was ok I booted to windows with the second drive just fine. Tried again same thing
So ssh to the fog server and check for images. When I pulled the image it did three passes the first pass being 67gb the image was (supposedly) 16gb, second was about 2gb and I don’t recall the third. I see nothing at all about images in the web interface under the /images/DFNSA directory I see
-rwxrwxrwx 1 root root 512 Mar 10 18:31 d1.mbr
-rwxrwxrwx 1 root root 7.4G Mar 10 18:45 d1p1.img
-rwxrwxrwx 1 root root 2.2G Mar 10 18:49 d1p5.imgObviously none of them is 16gb (compressed?) but why is fog not even attempting to deploy them and what on earth did it do during the upload process that crushed my HD’s file system? One would think the imaging process would be done in read-only mount? I have absolutely no idea as to where to go here but I am very hesitant to allow fog to touch a machine I really care about at this point.[/quote]
When the client failed to resize did you manually reboot the computer? If the partitions were not restored to where they were previously THAT is where the boot error came from.
In order to fix it you’ll need to resize the partitions yourself. If all of your lab machines are the same I would recommend using one of those to get what the partition sizes should be.
Use the recovery console. This guide should have all the info you need to get started.
[url]http://www.bleepingcomputer.com/tutorials/windows-7-recovery-environment-command-prompt/[/url]You could also upload an image from a third lab pc using multiple partition image and then deploy to the first two.
-
[quote=“G0dzilla, post: 23931, member: 1692”]Any more information?
What version of FOG?
Did it attempt to upload as raw filesystem/fat32/ntfs etc?
How many partitions did the drive have and what filesystems did they have?
[/quote]
Fog 0.32 is the version
it’s ntfs standard install with goback so one windows and one goback partion
I did not notice exactly how it attempted the upload[quote=“G0dzilla, post: 23931, member: 1692”]
The drive could be faulty.
Otherwise “/fixboot C:” & “/fixmbr C:” from the recovery console might make it boot again.
[/quote]Drive was fine, functional and no sign of issues, no smart defects or warnings and I use it all the time when I am on site at that location. Recovery via fix??? was useless and I had already tried that. wish I had cloned the drive first but never would imagine the possibilty of something happening during the upload phase
[quote=“G0dzilla, post: 23931, member: 1692”]
I believe this could be your CD drive.
[/quote]Yes, sr0 should be the first dvd/cd so not really concerned about that as it would be normal behavior, but I did not see where it was mounting the sata drive, just saw that it mounted sr0 readonly, waited a few seconds and then things went by real quick down to Done!
[quote=“G0dzilla, post: 23931, member: 1692”]
What is your intended use for FOG? are you using it to try and backup, or trying to create images for deployment?
It is much more convenient to create images in VMware/Virtualbox and use the snapshot feature in case things go wrong. Will save a lot of time.[/quote]My intended use is to deploy install images to 92 PCs but I wanted to do some testing first as I am unfamiliar with the product. Good place to start is pull an image from a smaller drive (80gb) and deploy it back to a clean drive on the same machine, which did not work obviously.
-
[quote=“BPSTravis, post: 23936, member: 22444”]When the client failed to resize did you manually reboot the computer? If the partitions were not restored to where they were previously THAT is where the boot error came from.
In order to fix it you’ll need to resize the partitions yourself. If all of your lab machines are the same I would recommend using one of those to get what the partition sizes should be.
Use the recovery console. This guide should have all the info you need to get started.
[url]http://www.bleepingcomputer.com/tutorials/windows-7-recovery-environment-command-prompt/[/url]You could also upload an image from a third lab pc using multiple partition image and then deploy to the first two.[/quote]
There was no failed to resize, it never attempted (that I could see) to deploy the image and I saw no error. It mounted sr0 readonly waited a few seconds proclaimed the process done and about 5 seconds or less later (before I could get through everything on screen) it rebooted. I repeated this 3 times and all three ended exactly the same so I decided to check the images and they were as posted, it almost appeared as though fog did not find the images to deploy. In the client’s assigned image file is listed as
/images/DFNSA . should I manually add the base of the filename there? there are three files
d1.mbr d1p1.img d1p5.img
not sure why the last is 5 instead of three but I assume fog knows what the names are and just needs the storage directory to do the upload? -
Do me a favor and remove the cd from the drive and try again.
Something tells me the image it captured is from the drive itself, rather than your actual hard drive, though I don’t know why it would. Can you try using my kernel as I don’t allow it to read the cd drive at all, this should mean you don’t have to worry about sr0 trying to load as a viable drive.
-
[quote=“Tom Elliott, post: 23986, member: 7271”]Do me a favor and remove the cd from the drive and try again.
Something tells me the image it captured is from the drive itself, rather than your actual hard drive, though I don’t know why it would. Can you try using my kernel as I don’t allow it to read the cd drive at all, this should mean you don’t have to worry about sr0 trying to load as a viable drive.[/quote]
Which kernel is yours? I am not seeing one with your name on it
-
[quote=“Tom Elliott, post: 23986, member: 7271”]Do me a favor and remove the cd from the drive and try again.
Something tells me the image it captured is from the drive itself, rather than your actual hard drive, though I don’t know why it would. Can you try using my kernel as I don’t allow it to read the cd drive at all, this should mean you don’t have to worry about sr0 trying to load as a viable drive.[/quote]
Also, as I see you are a developer, all of the PCs I am going to deploy to (as well as the reference machine) are UEFI… Will this cause an issue with a partion image or should I DD them to make sure UEFI data remains untouched? They are all Compaq 6200 pro boxes and I have found there is no way to set PXE as a default boot option when EFI is in play, they will not boot to windows wihout the EFI windows boot manager source being selected and network is only in the legacy section which cannot be prefered over EFI source :-[
