Good morning,
I have reinstalled Fog 1.2.0 on a Centos7 hyper-v machine. It’s been working well.
During the installation, I pointed the storage node to a Windows-based file server that has ample space for images.
Fog is not reporting this in the gui. It is working, but under “Disk Information” it says “Failed to connect to…”
Is it possible to have reporting with a Windows storage node?
Thanks!
Also, are you able to boot to a recovery partition by pressing F8? If so, Windows 8 has some recovery tools in there for startup issues.
[quote=“Lucas K, post: 47159, member: 29655”]Sorry for answering this old post, but i have the same trouble like you imaging gpt windows 8.1 disk
I used single disk multiple partition not resizable mode because the other mode didn t uploaded the image.
i did all the steps wrtitten above and I get this error when i download the image to the laptop:
How do you workaround this?
Thanks in advance.
LucasK.[/quote]
Everything has to be set back exactly as it was before the imaging. If secure boot was enabled, re-enable it, along with all the other original options. (UEFI boot, etc.)
Windows 7 has the AHCI drivers disabled by default, I believe. You can activate them in the registry, if you can get a boot disk to work.
The keys are located at:
HKLM\SYSTEM\CurrentControlSet\services\msahci —> Set “Start” from 3 to 0.
HKLM\SYSTEM\CurrentControlSet\services\iaStorV —> Set “Start” from 3 to 0.
Nope. In fact, both machines are sitting right here on my desk, connected to the same dumb switch.
Okay. I still cannot download the file directly, however I was able to access the FOG menu from an optiplex 960. I’m attempting an upload at this time.
Tried restarting TFTPD-HPA service. It did. Still receiving the “write” error when trying to transfer the file. STP is NOT enabled on our switches.
Again, could this be a permissions issue?
I actually did this prior to posting. I was able to obtain the undionly.kpxe file through my workstation using TFTP. Although, now I am unable to do so.
Something funny is going on----TFTP seems to be working, and then not working for whatever reason.
As I stated previously, I was able to get it to boot to the FOG screen once. I registered the workstation, and then rebooted to upload an image.
It would not load FOG after that…just timing out, and I receive an error when trying to download via TFTP.
“A problem occurred while trying to write to the file from x.x.x.x” Permissions issue, maybe?
Hey all…
Been awhile.
Got a new job, and one of the first things I’m charged with is getting a FOG server up and running. Of course, I’m not as well versed on this network as I am on the old place, so I need some more eyes/ears for this.
I have Ubuntu Server 13.10 running Fog 1.2.0.
Have everything installed.
When I PXE boot a Dell Optiplex 580-- I was able to initially get to the FOG screen and register it. Then, I rebooted to upload an image.
Receive the following:
/default.ipxe…No such file or directory ([url]http://ipxe.org/2d12603b[/url])
I was receiving this error prior, and we opened up some ports on our firewalls. I also disabled the firewall on the Fog server. That’s when I finally got it to boot the first time, but has not done it since…just keeps throwing that error.
Any thoughts/suggestions here?
Yeah. The kernel didn’t work. 
Right. I was just building a kernel for the heck of it while specifying the HP/Compaq drivers directly. Like I said previously, I got it to the point where I was doing a debug download. Now it is throwing a “Partition File Missing:” note.
I’m also going to throw in there (while I’m trying to configure a kernel) that the DL380 G3 is strictly an x86 unit.
Alright, thanks for the reply guys. I seem to be getting a bit further.
I manually created the host in the GUI, and set it to run in debug mode.
When running FDISK -l I received this:
[root@192 /]# fdisk -l
Disk /dev/cciss/c0d0 271.3 GiB, 291331192328 bytes, 569006235 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
So, I took that, went to the host in the GUI, and placed /dev/cciss/c0d0 in the “Host Primary Disk” box.
I then setup a debug download job, and went to it. Here is the output for that:
Below is a variable dump from FOG
osid=4
osname=Windows (Other)
mbrfile=
type=down
storage=192.168.6.8:/fog/images/
img=CRUSADERBASE
hd=/dev/cciss/c0d0
part=/dev/cciss/c0d01
I then ran the “fog” command:
#Starting Image Push
#Using Image: CRUSADERBASE
#Looking for Hard Disks…Done
#Using Hard Disk: /dev/cciss/c0d0
#Erasing current MBR/GPT Tables…Done
#Restoring MBR…Done
#No extended partitions…Done
#Checking Hard Disks…Done
#Processing Partition: /dev/cciss/c0d0p1 (p1)
#Partition File Missing: /images/CRUSADERBASE/d1pp1.img*
Done
#Changing hostname…Done
#Updating Computer Database status
#Database Updated!
#Task is completed, computer will now restart.
This concerns me, does this mean that I may not be able to use this particular hardware for disaster recovery?
Tom, cciss is a block driver for older HP Smart Array controllers like this machine. The C0D0 naming scheme indicates controller 0, disk 0, whole device.
Here is more information I found on it: [url]http://man7.org/linux/man-pages/man4/cciss.4.html[/url]
Is it possible that this controller is so old that fog won’t support it? Is it possible for me to build a kernel that includes the CCIS driver?
I tried the latest kernel. Same problem.
While I’m awaiting an answer, I’m going to dig around and see if this is a kernel issue. Maybe the Smart Array driver isn’t included in the most recent release?
Hello and good morning, Foggers. I’m having a new problem, which is probably just an ID10T error, so if you could point out the obvious, that would be great.
I’m trying to register a DL380 G3 Server. (Yes, I know. We have reasons for this…and we’re working on it. For the time being, it is what it is.)
This G3 server is running a Compaq Smart Array 5i+ in a RAID5 configuration. (Yes, I also know, gotta keep things as they are, unfortunately. Some things might break if they’re changed.)
The server PXE boots into the FOG GUI menu. I choose “Full Host Registration.” Then, all hell breaks loose.
I receive the following:
mptbase-ioc7 Error: WAIT IOC_READY State (0X20000000) timeout(15)!
That repeats a few times, then arrives at would be the registration screen. Instead, I get:
“Hard Disk Not Found.”
I went back and ran some compatibility checks.
Model: Compaq Smart Array (cpqarray)
Disk /dev/cciss/c0d0: 291GB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:
Error: /dev/cciss/c0d0: unrecognized disk label
This computer appears to be compatible with FOG!
Network…[Pass]
Disk…[Pass]
Any ideas? Basically, we’re trying FOG in a very serious disaster recovery scenario. (This is for a very critical server. If it goes down, we need it back up ASAP.)
I’m encouraged by the fact that it says it’s compatible, but I know I’ve had this issue with these servers before. It’s just, now it’s important. Thank you!
[quote=“Junkhacker, post: 37442, member: 21583”]it sounds to me like you hit upload instead of download once[/quote]
Nope.
I still find it easier to forget about the factory image altogether. We just purchased a bunch of E5540 laptops for our sales team, which came preloaded with Dell bloatware, as well as Microsoft software we don’t need/don’t use.
Plus, as many of you know, Windows 8 has the metro screen with all sorts of unnecessary apps tied to it.
We just did a disk to disk copy of the factory image and tossed it in our fire safe in the REMOTE instance that we may need it. I also created a fog image of it, but you have to do a RAW copy, which will take several hours, and honestly, why do you need it?
As IT admins, our job is to streamline everything to make downtime less, and confusion less. I honestly believe that the more partitions you have on a drive, the more problems you are causing for yourself.
What I love about FOG is that once I have an image, I’m no more than 2 hours away from having a completed deployment. (Usually it averages around 30 minutes) When I was using Ghost, that was a crapshoot.
My images are one partition, plus any reserved partition that Windows creates upon installation. That’s it. I don’t need a recovery partition. We use Windows backup on our desktops for the Windows 7 machines, File History for Windows 8, and Windows Server Backup on our servers, with Shadow copies on the file servers. If someone hoses their machine, I just load up FOG, image the machine, and copy their profile from the backup server. Done, and usually by the time they get back from lunch.
If I was relying on a factory recovery partition, I would be putting myself in a position where that would fail (which they often do), and they tend to take a long time.
Less partitions = less problems.
I haven’t had any issues with FOG and the BIOS Product Key. It’s been image, product key, go.