Posts made by trebor

Had time to run the DB commands and that solved my problem. Thanks.

FOG Project is a new creature to me and despite the challenges I am really enjoying what it can do!

Both machines are two different manufacturers so, MAC addresses are different and different IP addresses. (First thing I checked but, tanks for asking.)

Second, these are NOT Windows machines.

Third, as stated in initial post “FOG 1.5.0-RC-10”. (Not sure how I got that version but I think it was from a git pull.)

Now, please, let’s move back to the question at hand . . . “client B” (via the FOG server) has got to be seeing “it’s” old images (when it was the “client A” motherboard.) This, most likely has to be due to the MAC address. How do I delete those ‘old’ backups? How do I purge by MAC address?

At this point, only four clients (here at home) so, if I have to purge every client backup since initial setup I am okay with that as it is easy enough to re-image all machines with new images.

Could this be a simpler solution, purging all backups and (essentially) starting over anew?

I have two clients that appear to be the same client as each host registration deletes the other registration.

Let me explain. I had been imaging a client and decided to upgrade the motherboard of that client (I’ll call this one “client A”). Imaged the “newer” mb machine okay.

Decided to recommission “old” mb into a different machine for other duties (call this one “client B”). Now, when I try to register this recommissioned client B machine, FOG thinks it is still the “client A” and will only allow deletion of the host. When I delete host FOG deletes the “client A” host and images.

What I know so far . . . I deleted any/all “client A” and “client B” hosts. Re-registered both clients and created active task to image “client A” and told FOG to capture image of “client A” then restarted “client A”. “client A” will not image, it just restarts the OS.

Some how “client A” is being “seen” by FOG as “client B” host and as I am requesting the image of “client A”, I think, FOG is seeing it as “client B” and NOT capturing image.

The FOG server is a Debian 9 running headless with FOG 1.5.0-RC-10.

When I go to MAC Address Manufacturer Listing it says “Current Records: 0”. Is FOG storing MAC addresses somewhere that I need to delete/reset to correct this issue?

Although it has been awhile . . . . I discovered that FOG was “seeing” the OS drive as /dev/sdc. Once I changed the “primary drive” to /dev/sdc all functioned properly.

Thank you for your help on this problem (now solved.)

Thanks for you help on this.

Yes, Ubuntu client.

Mounting the raid devices (/dev/md126 & /dev/md127) I fairly comfortable I can figure out how to do that. Capturing the screen “lsblk” output from a pxe client, I am not sure how to do? Suggestions?

Sorry it has been a while. Had time to do as I was told and it still will not image.

The machine has five (5) drives. Two are the OS on raid1 (mirror) and the other three are a LVM volume of data that I do not have any interest in imaging.

Read thru the https://forums.fogproject.org/topic/7882/capture-deploy-to-target-computers-using-intel-rapid-storage-onboard-raid

The raid device FOG is seeing as “/dev/md126” (and /dev/md127) of the OS drives.

“cat /proc/mdstat” reports ‘good’ raid1.

Set host to be “captured” and the image fails “Could not find partitons (bin/fog.upload)” and will reboot in one minute.

I deleted the host and re-inventoried it and set “Host Kernel Arguments” to ‘mdraid=true’ and “Host Primary Disk” to ‘/dev/md126’ but it still fails with same waring.

Suggestions?

Had a chance to do as told and yes, FOG “sees” the drives differently.

That which is plugged into the first sata port on the MB and the OS sees as /dev/sda, FOG, via debug task and “lsblk” listing “sees” as /dev/sdc.

Now imaging correctly and storing the OS drive.

Thank you for you guidance.

I have a Mythbuntu 16.04.3 LTS (software is up to date and primarily kept as current a possible) that has a OS hard drive (160 Gb) and two large data drives (1.5 Tb & 2Tb) drives that are LVM together for large storage of recorded shows, etc. I only want to image the OS drive (for use in the event of a catastrophic failure) and NOT the large data drives.

I have read on the “net” and in the forums. Added the “Host Primary DIsk” as ‘/dev’sda’ to the host. When I captured my first image it “picked up” the 1.5 Tb drive and imaged it.

How do I make it “see” the OS drive at /dev/sda?

I feel like I have missed something. Perhaps someone can point me to other documentation I may have missed?

@trebor So, I’m new to FOG and not familiar with all the related terms. Maybe I searched for the wrong terms but, I have to ask, why isn’t this information (https://forums.fogproject.org/topic/7882/capture-deploy-to-target-computers-using-intel-rapid-storage-onboard-raid) incorporated into a easy to find wiki page yet? Me, the newbie, maybe the tags “mdadm” should be included? I don’t know, just suggesting.

Thanks for the quick reply george1421.

The page I have been looking for! https://forums.fogproject.org/topic/7882/capture-deploy-to-target-computers-using-intel-rapid-storage-onboard-raid

THANKS!

First, thanks for a great project. I am a newbie to FOG and have a lot to learn.

I have not had any issue imaging any of our Windows workstations nor any linux machines on single hard drives.

I have been reading about how to create an image for a linux machine that has a mdadm raid disk setup. As I understand the documentation I have read, setting the “kernel options” to “mdadm-true” in 'Host Management" is all that is required? Leave “Host Primary Disk” blank?

This first client with mdadm is a simple two disk array (Raid1-mirror) linux machine. If I can start here, create an image, I can learn as I go.

Sorry to ask this simple question but, most of the searches (“FOG Project mdadm”) keep finding “Intel Raid” or “hardware raid” or “fakeraid” references. Not “mdadm” specifically.

Perhaps I overlooked the ‘mdadm client page’ in the wiki for this?

Are my client settings the correct attributes to use?