Posts made by msnyder

@Tom-Elliott Dude everyone here gets it and appreciates what you do! Thanks for everything!

I deleted them via the CLI and don’t seem to have any issues thus far; however it did not replicate the delete to the storage nodes… I had to delete them individually.

@Tom-Elliott Can I just delete them from the Ubuntu CLI on the main Fog server and the storage nodes will replicate the delete?

@george1421 Ok, makes sense, except can’t do a Mac VM, but like you said, that’s not as important than expanding the disk…

Thanks

@Tom-Elliott Did them both at the same time from the Image Management menu.

Can I just delete the images from the disk?

Permissions looked off, so I set them, but old “already deleted” images are still there. How do I remove them without messing up the database?

root@PDC-FOG:~# ls -l /images/
total 32
drwxrwxrwx 4 fog  root  4096 Jun 22 16:18 dev
drwx------ 2 root root 16384 Jun 21 08:36 lost+found
drwxrwxrwx 2 root root  4096 Jun 22 12:08 MacOS-Test
drwxrwxrwx 2 fog  root  4096 Jun 21 08:33 postdownloadscripts
drwxrwxrwx 2 root root  4096 Jun 22 09:34 Win10-Test
root@PDC-FOG:~# chown -R fog:root /images
root@PDC-FOG:~# ls -l /images/
total 32
drwxrwxrwx 4 fog root  4096 Jun 22 16:18 dev
drwx------ 2 fog root 16384 Jun 21 08:36 lost+found
drwxrwxrwx 2 fog root  4096 Jun 22 12:08 MacOS-Test
drwxrwxrwx 2 fog root  4096 Jun 21 08:33 postdownloadscripts
drwxrwxrwx 2 fog root  4096 Jun 22 09:34 Win10-Test
root@PDC-FOG:~#

Server

• FOG Version: 1.4.3
• OS: Ubuntu 16.04.2 LTS

Client

• Service Version:
• OS:

Description

After deleting images in Fog, it does not remove the images on the disk or storage nodes. Bug?

Dashboard

Disk

Storage Nodes

@Sebastian-Roth So you are saying to use my idea of installing MacOS on a small 16GB USB key for the capture, then deploy to Macs that have a much larger hard drive and expand using Apple disk utility?

Here is the post I saw that made me believe MacOS cannot be resized: https://forums.fogproject.org/topic/7627/invalid-operating-system-id-apple-mac-os-8/4

Nope… Same error I remember getting the first time I tried capturing MacOS: Invalid Operating System id: Apple Mac OS (8) (validResizeOS)

Moderator inserted image copied from imgur (geo1421)

I will try…

ItIt’s my understanding, from reading these forums, that MacOS partitions are not resizable…

Server

• FOG Version: 1.4.3
• OS: Ubuntu 16.04.2 LTS

Client

• Service Version:
• OS:

Description

How does eveyone handle MacOS, since you can’t resize the partition? I’m new to Fog, and have Windows working, starting on trying to get Mac working too. I’m able to boot via iPXE on USB and capture the image, but the machine I used is 512GB. I’d have to deploy to the same size drive, correct?

Could I install MacOS on a 16GB USB drive and capture that image? But then when I deploy to other Mac machines, would I be stuck with a 16GB OS drive?

Currently we use Kace to image Windows and Apple Server to image Mac, Fog would let us consolidate and add Linux support…

Seems to be replicating now! Thanks!

@Sebastian-Roth said in Locked out of Fog...:

chmod 777 /images

Will I need to recapture my image now?

Correct?

root@PDC-FOG:/# ls -l
total 104
drwxr-xr-x   2 root root  4096 Jun 21 08:29 bin
drwxr-xr-x   3 root root  4096 Jun 21 08:25 boot
drwxr-xr-x  19 root root  3980 Jun 21 09:09 dev
drwxr-xr-x  98 root root  4096 Jun 21 15:25 etc
drwxr-xr-x   5 root root  4096 Jun 21 08:31 home
drwxr-xr-x   5 root root  4096 Jun 21 08:37 images
lrwxrwxrwx   1 root root    32 Jun 21 08:24 initrd.img -> boot/initrd.img-4.4.0-81-generic
lrwxrwxrwx   1 root root    32 May  9 14:37 initrd.img.old -> boot/initrd.img-4.4.0-77-generic
drwxr-xr-x  23 root root  4096 Jun 21 08:28 lib
drwxr-xr-x   3 root root  4096 May  9 14:50 lib32
drwxr-xr-x   2 root root  4096 Jun 21 08:22 lib64
drwx------   2 root root 16384 May  9 14:18 lost+found
drwxr-xr-x   3 root root  4096 May  9 14:18 media
drwxr-xr-x   3 root root  4096 May 22 09:22 mnt
drwxr-xr-x   4 root root  4096 Jun 21 08:32 opt
dr-xr-xr-x 239 root root     0 Jun 21 04:09 proc
drwx------   8 root root  4096 Jun 21 09:19 root
drwxr-xr-x  31 root root  1100 Jun 22 08:04 run
drwxr-xr-x   2 root root 12288 Jun 21 08:29 sbin
drwxr-xr-x   2 root root  4096 Jan 14 09:06 snap
drwxr-xr-x   3 root root  4096 Jun 21 08:31 srv
dr-xr-xr-x  13 root root     0 Jun 21 04:09 sys
drwxr-xr-x   6 fog  root  4096 Jun 21 08:33 tftpboot
drwxr-xr-x   2 root root  4096 Jun 21 08:33 tftpboot.prev
drwxrwxrwt  17 root root  4096 Jun 22 08:40 tmp
drwxr-xr-x  10 root root  4096 May  9 14:18 usr
drwxr-xr-x  14 root root  4096 Jun 21 08:28 var
lrwxrwxrwx   1 root root    29 Jun 21 08:24 vmlinuz -> boot/vmlinuz-4.4.0-81-generic
lrwxrwxrwx   1 root root    29 May  9 14:37 vmlinuz.old -> boot/vmlinuz-4.4.0-77-generic

root@PDC-FOG:/# cd /images/
root@PDC-FOG:/images# ls -l
total 24
drwxrwxrwx 5 fog  root  4096 Jun 21 14:01 dev
drwx------ 2 root root 16384 Jun 21 08:36 lost+found
drwxrwxrwx 2 fog  root  4096 Jun 21 08:33 postdownloadscripts

It appears that even though the capture completed on the machine, the image is staying in /images/dev/<macaddress>…

I’ve captured my first image and it doesn’t seem to be replicating to my storage nodes… Could this be becasue I moved the /images to a new drive?

Yep! Thanks for your help!