Posts made by Fog_Newb

@JGeear Yeah something is messed up with the branches or something. I got that too. Tons of conflicts and a message about not a trusted repository or something. I figured it was on me because I had just restored a snapshot of the FOG VM.

I wiped the fog installer directory, in my case /opt/fogproject then I re-downloaded,

sudo git clone https://github.com/FOGProject/fogproject.git /opt/fogproject 

set to dev-branch but it ended up installing the latest stable version: 1.5.10.1565

sudo git checkout dev-branch

Tells me - Already on ‘dev-branch’

@Tom-Elliott

Thanks Tom, that fixed it right up. I guess I overlooked that file when copying everything from the original /images.

Yeah, that fdrive number… It is the serial number of the drive.

The NVME drives initialize differently each time during boot. I guess that is a thing, so nvme0 would sometimes be nvme1. It was a mess. Then I learned drive size could be used to differentiate between drives under Host Primary Disk. Now that both of my NVME drives are the same size, I have to use the drive serial number.

I’ve been able to capture and deploy images just fine. Until… mounting a 2nd hard drive as /images and upgrading to FOG 1.5.10.48 from the previous dev version. .mntcheck exits under /images/dev

I thought I had the permission set correctly since I can still capture… anyways, I’m not sure what to do.

The error message is attached

What do?

Thanks

update: SOLVED

@george1421

Thanks George. No but I will now that I have time machine back ups. Can I use mac-boot to create the stick then just update those 2 things?

Preamble

A while back @george1421 helped me create a bootable USB stick to allow IPXE bootinig my 2018 mini to FOG (I have all the T2 security features disabled in the mac BIOS no secure boot etc)

It was able to capture images no problem. I ran into problems deploying the captured images (to the same mac they were captured from). I guess it had something to do with the T2 chip. The image would deploy fine but would not boot the OS.

It started to get complicated for me and I decided to suck it up and just use Time Machine. I do not like Time Machine.

IIRC, since then T2 support has been baked into the Linux kernel and…

I just noticed this! Are there any plans to update it?

https://github.com/FOGProject/mac-boot/releases/tag/v0.1.0

Thanks

Hello,

Not sure if this is the right place to ask but is there a way to change the resolution of the ipxe boot menu the clients come to when booting IPXE?

Thank you

@Sebastian-Roth Unfortunately the USB external drive wasn’t see by FOG, I tried the serial number listed in Windows but it backed up an NVMe drive Please disregard

@Sebastian-Roth

That is awesome. I tried using a power-shell command to get the drive serial number.

 Get-PhysicalDisk | FT FriendlyName,AdapterSerialNumber,serialnumber 

Just to confirm, what this command lists as the Adapter Serial Number matches what Crystal Disk Info shows as the NVMe serial numbers as well as the serial number listed on the box the NVMe came in. Just to note, the SSD’s do not have an Adapter serial number

Thanks again for all you help.

@Sebastian-Roth Thank you so much.

Have there been any updates in dealing with dual NVMe drives that are the same size?

@Sebastian-Roth This is going to sound really dumb but I don’t know how to query FOS to figure out how the USB drive will be listed. Like to find out what /dev/???

Hi,

When backing up different drives, I’ve been changing the Host Primary Disk settings to specify the drive. I use the disk size. I have to do this for systems with NVME systems (assuming the nvme drive size is different). Today I need to back up and external USB drive. I wasn’t sure how to get the size of that using the blockdev command.

The scenario is;

Backing up external Wii U drive, an external 1TB SSD using a laptop with 2 internal 250GB SSDs. What steps should I take to get the correct Host Primary Disk settings for backing up the external drive?

Thank you

@Sebastian-Roth Yes. Thanks

@Sebastian-Roth

I can’t wait!

@Sebastian-Roth No, I wasn’t using the 6x kernel. This was using the T2 kernel that was going around a while back.

@george1421

Oooh cool!

@Sebastian-Roth said in What do I rename the T2 bzimage file to for reliable mac OS capture and restores?:

links here so everyone can look up the context.

Thanks
Yes, I needed the USB stick to PXE boot the T2 mac. It worked great and could capture and deploy no problem but…

https://forums.fogproject.org/topic/16570/ugh-t2-chip-nightmare-anyone-using-fog-with-t2-macs/

Here are some previous threads where it all started.

https://forums.fogproject.org/topic/16482/mac-address-captured-during-registration-is-different-than-actual-mac-address/

https://forums.fogproject.org/topic/16468/can-t-get-to-fog-booting-from-usb-boot-uefi-client

The MAC address thing is so weird and I’m kind of afraid to test anything in fear of No Administrator Account found

@Sebastian-Roth

Thanks, I will replace the ones on the FOG server and the USB stick, with them.

Greetings,

With some instructions given from another member of the forum, I was able to create a FOG boot USB for mac OS. However, I ran into problem when deploying captured images. After deploying a captured imaged onto the same mac, I would get an error :Administrator account not found.

Further help revealed this shouldn’t be an issue if the T2 kernel is in place. I have a T2 kernel on the boot USB stick an I would like to know if this is the latest one, what I should rename it to? Should I place it on the FOG server and then specify the host to use that bzimage for the mac host?

Here is where it is currently placed on the USB stick. How and where should it be placed / named on the USB boot device and or FOG server?

Thank you

@sebastian-roth Glad I could help in some way. FOG is awesome you and @george1421 always get any issues I run into sorted with a quickness. After installing the latest as of writing this, 1.5.9.215, the host parameter settings look normal again.

(I originally posted this reply to my own comment accidentally)

@george1421 Yes.

I just started backing up a Windows drive using 1.5.9.215. I saw Partclone 3.20 briefly appear on the screen. For some reason, while it is backing up a partition the version number of Part Clone isn’t listed. Only for a moment between capturing each partition is the version number displayed.