Posts made by chris_unit

@sebastian-roth
Here you go

C
chris_unit
16 minutes ago

@sebastian-roth said in HDD size missmatch error.:

d1.minimum.partitions

Its fog version 1.5.9

d1.minimum.partitions

label: dos
label-id: 0x1b3934fb
device: /dev/sda
unit: sectors
sector-size: 512

/dev/sda1 : start= 2048, size= 102400, type=7, bootable
/dev/sda2 : start= 104448, size= 439331328, type=7
/dev/sda3 : start= 999156224, size= 1056768, type=27
/dev/sda4 : start= 439437822, size= 559718402, type=5
/dev/sda5 : start= 439437824, size= 559718400, type=83

Hi there,

The original system disk used to take image:
lsblk
sda 477G

the destination disk is:
lsblk
sda 447.1G

in fog, the image on disk size is 288GB

it’s a dual partition windows / ubuntu image.

it’s set to ‘Single Disk - Resizeble’

When I try to put the image on the smaller disk it says there’s not enough space even tho it’s resizeable with far less than the full disk size used.

Any ideas how to resolve without replacing disks because there’s 30mb size difference?

@george1421 snponly.efi works!

but now i believe i only want snponly.efi to be for UEFI clients which in my case is our Intel NUCs.

I’ve follows the steps here
https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence#Using_Windows_Server_2012_.28R1_and_later.29_DHCP_Policy

and set the vendor class to PXEClient:Arch:00007

is that the right vendor class for an intel nuc?

@dangbird Thanks for the tip

i’ve now done the same, do i now have to specificy that kerner for my NUC’s in the hosts info (bzImage)

Is this kernel both legacy and UEFI ?

@sebastian-roth Hi there,
It doesn’t recognise that net0 exists

i’ve just seen on another post a suggestion of using different kernels

what would you suggest would be a good kernel change to to try and resolve this.

We have mostly this model
Intel NUC10i7FNH

Hi there,

I’m having issues booting into the fog menu with both UEFI and Legacy

can you reccomend a kernel to use for
Intel NUC10i7FNH

Thanks

@sebastian-roth Here you go

@sebastian-roth
Hi there

looks like its the same result

Hi there

We’ve followed steps to have UEFI and Legacy to coxit
https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence#Using_Windows_Server_2012_.28R1_and_later.29_DHCP_Policy

it seems like it starts to work correctly but then errors

see attached

@george1421 Thanks so much for this

i’m trying to get Ubuntu 20.04 Desktop working

here’s my menu item

kernel tftp://${fog-ip}/os/ubuntu/Desk20.04/vmlinuz
initrd tftp://${fog-ip}/os/ubuntu/Desk20.04/initrd
imgargs vmlinuz initrd=initrd ip=dhcp url=http://${fog-ip}/os/ubuntu/Desk20.04/ubuntu-20.04.2.0-desktop-amd64.iso locale=en_US.UTF-8 quiet splash ip=dhcp rw
boot || goto MENU

vmlinuz and initrd load fine, but it can’t locate the iso.

Is the directory /images/ shared out over http ?

@sebastian-roth said in Using Partclone to image MBR linux client using Resize option:

LVM

Is there a way that i could take an image (as lvm) and then put it back at ext4 ?

I have a centos 7.6 client i’m trying to take an image of

it’s a only about 78gb on a 447gb disk

when i try to use single disk resizeable i get
no resizeable partitions found

here’s some information about the disk

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 447.1G 0 disk
├─sda1 8:1 0 1G 0 part /boot
└─sda2 8:2 0 446.1G 0 part
├─centos-root 253:0 0 392.1G 0 lvm /
└─centos-swap 253:1 0 4G 0 lvm [SWAP]
[root@GPU-01 ~]# fdisk -l

Disk /dev/sda: 480.1 GB, 480103981056 bytes, 937703088 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk label type: dos
Disk identifier: 0x000d172e

Device Boot Start End Blocks Id System
/dev/sda1 * 2048 2099199 1048576 83 Linux
/dev/sda2 2099200 937701375 467801088 8e Linux LVM

Disk /dev/mapper/centos-root: 421.0 GB, 421045207040 bytes, 822353920 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/mapper/centos-swap: 4294 MB, 4294967296 bytes, 8388608 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

i’m really keen to use the resizeable option as its taking nearly an abour to take an image for 78gb of data.

Model: ATA INTEL SSDSC2KB48 (scsi)
Disk /dev/sda: 480GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
1 1049kB 1075MB 1074MB primary xfs boot
2 1075MB 480GB 479GB primary lvm

Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/centos-swap: 4295MB
Sector size (logical/physical): 512B/4096B
Partition Table: loop
Disk Flags:

Number Start End Size File system Flags
1 0.00B 4295MB 4295MB linux-swap(v1)

Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/centos-root: 421GB
Sector size (logical/physical): 512B/4096B
Partition Table: loop
Disk Flags:

Number Start End Size File system Flags
1 0.00B 421GB 421GB xfs

Looks like it a MBR partition table

I’ve given up trying to get this installed on this particular server

i’m now running fog on a vm

@sebastian-roth said in mysql not starting when trying to install 2nd time:

/opt/fog/.fogsettings

Hi there

everything is set to default settings i dont make any custom changes.

did you install on 7.2?

unforutnatly /opt/fog/.fogsettings doesn’t exist

Hi there

it’s centos 7.2 and latest version of fog.

our backup software must use multicasting but ive since moved that from the default port so that issue is resolved

the issue now is the php issue during install

I"ve manged to get a bit further by removing mysql so that it could be installed fresh again

now i have an issue with php?

 * Setting up fogproject user..................................Skipped
 * Locking fogproject as a system account......................OK
 * Setting up fogproject password..............................OK
 * Stopping FOGMulticastManager.service Service................OK
 * Stopping FOGImageReplicator.service Service.................OK
 * Stopping FOGSnapinReplicator.service Service................OK
 * Stopping FOGScheduler.service Service.......................OK
 * Stopping FOGPingHosts.service Service.......................OK
 * Stopping FOGSnapinHash.service Service......................OK
 * Stopping FOGImageSize.service Service.......................OK
 * Setting up and starting MySQL...............................OK
 * Setting up MySQL user and database..........................
   The installer detected a blank database *root* password. This
   is very common on a new install or if you upgrade from any
   version of FOG before 1.5.8. To improve overall security we ask
   you to supply an appropriate database *root* password now.

   NOTICE: Make sure you choose a good password but also one
   you can remember or use a password manager to store it.
   The installer won't store the given password in any place
   and it will be lost right after the installer finishes!

   Please enter a new database *root* password to be set:

OK
 * Backing up user reports.....................................Done
 * Stopping web service........................................OK
 * Setting up Apache and PHP files.............................Failed
   ###########################################
   #                                         #
   #      PHP Failed to install properly     #
   #                                         #
   ###########################################

   Could not find /etc/php.ini!

Hi there,

i had a failed first time install becuase p5 by archiware uses port 9000.

i’ve since moved that port and tried to install again and got an error saying mysql couldn’t start

attached is the command line runinng the install script

here’s the status of mysql service
[root@backup bin]# systemctl status mysql
● mariadb.service - MariaDB database server
Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Mon 2021-07-19 17:33:55 BST; 2min 41s ago
Process: 47476 ExecStartPre=/usr/libexec/mariadb-prepare-db-dir %n (code=exited, status=1/FAILURE)

Jul 19 17:33:55 backup systemd[1]: Starting MariaDB database server…
Jul 19 17:33:55 backup mariadb-prepare-db-dir[47476]: The directory /var/log/mariadb does not exist.
Jul 19 17:33:55 backup systemd[1]: mariadb.service: control process exited, code=exited status=1
Jul 19 17:33:55 backup systemd[1]: Failed to start MariaDB database server.
Jul 19 17:33:55 backup systemd[1]: Unit mariadb.service entered failed state.
Jul 19 17:33:55 backup systemd[1]: mariadb.service failed.[0_1626712795281_install log01](Uploading 0%)

Here’s the install log

install log01.txt

@sebastian-roth I wanted to try and keep our exisitng pxeboot menu with an option in that menu to load the fog pxe menu.

i’ve reaslied that would limit so many features of automation that it would make more sense to just add any menu items we already have from our exiting pxe menu and add them to the fog one.

I’m looking to migrate all my pxelinux menu items over to Frog and have frog become my primay pxe menu on boot

i have items like this

LABEL Flame2020 CentOS7.6
MENU LABEL ^Flame2020 CentOS 7.6
MENU PASSWD a0F1BvFIT2asdfasoKPX/I1e20
KERNEL /flame2020_centos7.6/vmlinuz
APPEND initrd=/flame2020_centos7.6/initrd.img inst.repo=nfs://pixit-v60-10g.ldn.unit.tv/mmfs1/data/anubis/.install/isos/flame2020_centos7.6 ks=nfs://pixit-v60-10g.ldn.unit.tv/mmfs1/data/anubis/.install/isos/flame2020_centos7.6/ks_820.cfg

how would i add this to the menu. ideally using the web gui as the php looks a little complicated

i actually think i’ve found the steps

Part 3 FOG Storage Node Configuration](https://forums.fogproject.org/topic/9430/synology-nas-as-fog-storage-node/21?page=2)