Latest FOG 0.33b
-
What’s worrying me is the fact that you have d1p1.img d1p2.img AND rec.img.000 and sys.img.000
What type of image is this? Multi-Part Single Disk, or Single Disk Resizable?
-
[quote=“Tom Elliott, post: 26480, member: 7271”]What’s worrying me is the fact that you have d1p1.img d1p2.img AND rec.img.000 and sys.img.000
What type of image is this? Multi-Part Single Disk, or Single Disk Resizable?[/quote]
“NTFS Only, Resizable” and Windows 8 for OS.
-
[quote=“Mr.Myagy, post: 26482, member: 23824”]“NTFS Only, Resizable” and Windows 8 for OS.[/quote]
From what I can see, it looks like that image is now a container for both a Windows 7 (or possibly
image as multipartition single disk (the d1 files) AND single disk resizeable. It seems like it hasn’t created the partition tables properly and for that I have no quick answer.A few questions, when you uploaded the file, did it display which partitions it was copying? My guess is Windows 8 image a slightly off at the moment because you’re using Windows 8 in MBR mode, while the “mbr” from windows 8 within the init is not set to give the 100mb part and the data part. Just my guesses at whats wrong. Maybe try changing the OS to Windows 7 and try deploying the task again?
Deploy, for the purposes of FOG is a generic term meaning -> sending of a task. Much as a squad of solders get’s deployed to various regions in the world. Whether they’re deployed from the US to IRAQ, or from Germany to the US. Download means to put the image on the client, Upload means to grab the image from the client.
-
[quote=“Mr.Myagy, post: 26478, member: 23824”]need2, this is a clean 0.33b install, but I updated it several times. I can do a fresh install if that is the issue.[/quote]
Just to clarify, I was asking if this was an OEM Windows install you were imaging or a clean install you did yourself from an install medium.
-
[quote=“Tom Elliott, post: 26484, member: 7271”]From what I can see, it looks like that image is now a container for both a Windows 7 (or possibly
image as multipartition single disk (the d1 files) AND single disk resizeable. It seems like it hasn’t created the partition tables properly and for that I have no quick answer.A few questions, when you uploaded the file, did it display which partitions it was copying? My guess is Windows 8 image a slightly off at the moment because you’re using Windows 8 in MBR mode, while the “mbr” from windows 8 within the init is not set to give the 100mb part and the data part. Just my guesses at whats wrong. Maybe try changing the OS to Windows 7 and try deploying the task again?
Deploy, for the purposes of FOG is a generic term meaning -> sending of a task. Much as a squad of solders get’s deployed to various regions in the world. Whether they’re deployed from the US to IRAQ, or from Germany to the US. Download means to put the image on the client, Upload means to grab the image from the client.[/quote]
When uploading, it uploaded /dev/sda1 which seemed legit (windows install disk reports ~350mb) because it finished in a quite a short while (don’t have the exact time, and I’m not very good with time estimates as my spouse is telling me), then we had /dev/sda2 which reported to upload just over 9GB (this being the reason I was asking earlier about compression). I did pay attention, and it didn’t throw any errors. If it matters with anything, the Windows in question is a 8.1 sysprep’ed and shutdown. As for the deployment part, /dev/sda1 seems to work fine, but when it reaches /dev/sda2, Partclone loads, then throws a 2 words error (can’t remember exactly) from outside Partclone, Partclone dies, then I get the “no such file or directory” message.
If it helps in any way, I am willing to provide access to the machines, or send you any information that might help in any way with closing this issue. -
[quote=“need2, post: 26488, member: 21891”]Just to clarify, I was asking if this was an OEM Windows install you were imaging or a clean install you did yourself from an install medium.[/quote]
Clean Windows install using the trial ISO downloaded from MSDN.
-
If possible I would recommend doing a basic wipe on that drive and reinstalling. For some reason it looks like some crap partitions are left over.
-
[quote=“need2, post: 26492, member: 21891”]If possible I would recommend doing a basic wipe on that drive and reinstalling. For some reason it looks like some crap partitions are left over.[/quote]
This was a fresh install. Fresh, as in…I just got to setup the user, installed .net and fog service, sysprep’ed and that’s it. As for the HDD configuration: it’s a 80GB hard drive, out of which I chose to install Windows on only 20 of them, leaving the rest unformatted. I did this, because I am planning to deploy this image on 11 machines, and even thou they all have 80 GB hard drives, they are different brands, so there might be some small differences, and I read in another thread that you should always be careful not to deploy an image that is bigger than the hdd (which kind of makes sense).
-
So, as Windows 8.1 is fairly new and not thoroughly tested with resizable images, I’d recommend maybe switching the image type to Multi Partition Single or All disk. I don’t know how the win8.mbr file was created, but from the sounds of it, it only contains one partition in total, which is why you’re seeing the /dev/sda2 not found error. I didn’t make the win8.mbr, so I don’t know all the specifics.
It does, however, sound likely that you probably need to do another fresh install. I know it’s more work, but it’s the best I can give you for now.
-
Sure, but was that drive used for previous Windows installations? It just seems like there was junk partition info left on the drive from the images that were being made on the server. Also, if you are doing an NTFS Resizable partition, it doesn’t matter what the original partition size is, only how much of it is used by data.
EDIT: Tom’s post gave me an idea. I assume this is a Windows 8 install that you upgraded to 8.1? 8.1 is not a service pack, its almost like an OS reinstall that you happen to get to keep your programs and files through. I would not be shocked if the 8.1 upgrade does some partition junk during its upgrade process to give it some fallbacks in case it fails during its install.
-
[quote=“need2, post: 26497, member: 21891”]Sure, but was that drive used for previous Windows installations? It just seems like there was junk partition info left on the drive from the images that were being made on the server. Also, if you are doing an NTFS Resizable partition, it doesn’t matter what the original partition size is, only how much of it is used by data.
EDIT: Tom’s post gave me an idea. I assume this is a Windows 8 install that you upgraded to 8.1? 8.1 is not a service pack, its almost like an OS reinstall that you happen to get to keep your programs and files through. I would not be shocked if the 8.1 upgrade does some partition junk during its upgrade process to give it some fallbacks in case it fails during its install.[/quote]
I didn’t update from 8 to 8.1. I installed 8.1 from the ISO. As for previous Windows installations, yes, there were, but I can’t see how those affected this. Granted, I didn’t do a low level format, but I did recreate the partitions every time I reinstalled WIndows.
-
[quote=“Tom Elliott, post: 26496, member: 7271”]So, as Windows 8.1 is fairly new and not thoroughly tested with resizable images, I’d recommend maybe switching the image type to Multi Partition Single or All disk. I don’t know how the win8.mbr file was created, but from the sounds of it, it only contains one partition in total, which is why you’re seeing the /dev/sda2 not found error. I didn’t make the win8.mbr, so I don’t know all the specifics.
It does, however, sound likely that you probably need to do another fresh install. I know it’s more work, but it’s the best I can give you for now.[/quote]
I have no problem reinstalling. I am (intermittently) trying to do this for the last 2 weeks now, so you can image I did quite some reinstalls. However, I would like to help the project if I can. I will come back with the results (probably tomorrow) from the “Multiple partition image - single disk”, as for the current problem, if you need any log, file, etc. I am more than happy to provide.
-
[quote=“Mr.Myagy, post: 26500, member: 23824”]I have no problem reinstalling. I am (intermittently) trying to do this for the last 2 weeks now, so you can image I did quite some reinstalls. However, I would like to help the project if I can. I will come back with the results (probably tomorrow) from the “Multiple partition image - single disk”, as for the current problem, if you need any log, file, etc. I am more than happy to provide.[/quote]
I appreciate the patience and am, almost always, approachable and will try to help. If I’m mean, I’m sorry, but it’s just who I am.
I don’t think I need anything else for right now though. The part that weirds me out is that the image folder contains an MPS image AND a SDR (Single Disk Resizable) image. That might be because of my tweaking of the FOGFTP so it may be a nonissue, so long as the image type is correct it shouldn’t matter.
-
Thanks Tom, where is
[QUOTE]FOG Boot Settings tab in FOG Settings[/QUOTE]Apologies if this is a stupid question; I will be happy to post screen shot. I am running 0.32
-
While this is the wrong wrong wrong thread for this question, its under Fog Configuration.
-
[quote=“Boyan Biandov, post: 26508, member: 1615”]Thanks Tom, where is
Apologies if this is a stupid question; I will be happy to post screen shot. I am running 0.32[/quote]
There’s really no such thing as a Stupid question, however 0.32 and 0.33 are two COMPLETELY different beasts. I forget the exact location of the “Boot Settings” equivalent name in 0.32, but I’m pretty sure it was just FOG PXE Settings on 0.32.
In 0.32, FOG Configuration is actually called Other Information and is the ( ? ) icon on the menu. From there, go to FOG Settings and find your relevant area. That being said, If the quote you’re referring to is about the Compression Slider bar, it is nonexistent in 0.32. This was a feature I added into the core of 0.33 as I thought it was useful for people to be able to change how much, or how little they wanted to compress their images.
-
All,
If you haven’t noticed by now, we are starting to prepare for the latest and greatest. With this, I must (sadly…okay not really) say that 0.33b is no more.
We have transitioned to Version 1.0.0. This is updated in the installers and FOG Version information within the GUIs.
With this, I must please request this particular thread be locked from further updates. We’ve had a pretty good run of 78 pages, but I think it’s time to open a new thread for the “Latest” information.
-
Latest stable release as of July 2016 is 1.2.0, which was released in July 2014.
https://news.fogproject.org/version-1-2-0-released/ -
Latest stable release as of Janurary 31st 2017 is FOG 1.3.4, released Janurary 27th, 2017. Find the official announcement here: https://news.fogproject.org/fog-1-3-4-and-client-0-11-9-officially-released/
-
Latest stable release as of November 21st, 2017 is FOG 1.4.4. Official announcement here: https://news.fogproject.org/fog-1-4-4-officially-released/
