@george1421 said in FOG: Not detecting target disks correctly (/dev/sda vs /dev/xvda):

df -h

Here u go

Filesystem           Size  Used Avail Use% Mounted on
devtmpfs             1.9G     0  1.9G   0% /dev
tmpfs                851M     0  851M   0% /dev/shm
tmpfs                851M   17M  835M   2% /run
tmpfs                851M     0  851M   0% /sys/fs/cgroup
/dev/mapper/cl-root  3.5G  1.3G  2.3G  36% /
/dev/xvda1           976M  126M  783M  14% /boot
tmpfs                171M     0  171M   0% /run/user/0

cat d1.partitions

label: dos
label-id: 0x038fb017
device: /dev/sda
unit: sectors

/dev/xvda1 : start=        2048, size=     2097152, type=83, bootable
/dev/xvda2 : start=     2099200, size=     8386560, type=8e

cat d1.fixed_size_partitions

2

first reply

And that was it - no other errors or strange things (saying the guy with 0 sucessfull deployments)

The smallest sda2 ever:

Is that normal or an error doing the capture process?

And we have an error:

All good so fare…

Ok, just checked: Golden image disk size 5GB, so 10GB on the target seems to be okay.

@george1421 ok, 2 sec…
Here u go

Hi @george1421

Thanks for the quick reply!

lsblk

NAME        MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
xvda        202:0    0    5G  0 disk
├─xvda1     202:1    0    1G  0 part /boot
└─xvda2     202:2    0    4G  0 part
  ├─cl-root 253:0    0  3.5G  0 lvm  /
  └─cl-swap 253:1    0  512M  0 lvm  [SWAP]

[root@localhost ~]# df -h
Filesystem           Size  Used Avail Use% Mounted on
devtmpfs             1.9G     0  1.9G   0% /dev
tmpfs                851M     0  851M   0% /dev/shm
tmpfs                851M   17M  835M   2% /run
tmpfs                851M     0  851M   0% /sys/fs/cgroup
/dev/mapper/cl-root  3.5G  1.3G  2.3G  36% /
/dev/xvda1           976M  126M  783M  14% /boot
tmpfs                171M     0  171M   0% /run/user/0

**df -h**
Filesystem           Size  Used Avail Use% Mounted on
devtmpfs             1.9G     0  1.9G   0% /dev
tmpfs                851M     0  851M   0% /dev/shm
tmpfs                851M   17M  835M   2% /run
tmpfs                851M     0  851M   0% /sys/fs/cgroup
/dev/mapper/cl-root  3.5G  1.3G  2.3G  36% /
/dev/xvda1           976M  126M  783M  14% /boot
tmpfs                171M     0  171M   0% /run/user/0

**cat /etc/fstab**
#
# /etc/fstab
# Created by anaconda on Sun Dec 29 20:44:58 2019
#
# Accessible filesystems, by reference, are maintained under '/dev/disk/'.
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info.
#
# After editing this file, run 'systemctl daemon-reload' to update systemd
# units generated from this file.
#
/dev/mapper/cl-root     /                       xfs     defaults        0 0
UUID=69d49bae-c6b4-49e9-afba-17a45b536e97 /boot                   ext4    defaults        1 2
/dev/mapper/cl-swap     swap                    swap    defaults        0 0

lsblk from FOG debug command line on target system

Reply to #2:
That’s fine - the golden image is super small and contain only bare minimum. The rest will be setup and done with scritps - I hope Normally I only work with PowerShell and SCCM…

Hi guys,

All new to the FOG universe, so please forgive me if I’m all wrong

Objective: Trying to deploy one CentOS8 Golden image to new VM’s on XC-NG and physical machines.

Env:
OS: All CentOS 8 based.
Hyper visor: XCP-NG 8
FOG: 1.5.7.89 (Dev branch due to CentOS

Issue:
The capturing of the image from the golden image VM went fine. However, the capture function seems to see (or being hardcoded) disks as /dev/sda1 and /dev/sda2 instead of the correct /dev/xvda1 and /dev/xvda2.

/images/goldenimage8
-rwxrwxrwx. 1 root root         2 Dec 29 22:55 d1.fixed_size_partitions
-rwxrwxrwx. 1 root root         0 Dec 29 22:55 d1.has_grub
-rwxrwxrwx. 1 root root   1048576 Dec 29 22:55 d1.mbr
-rwxrwxrwx. 1 root root       194 Dec 30 00:32 d1.minimum.partitions
-rwxrwxrwx. 1 root root        17 Dec 30 00:34 d1.original.fstypes
-rwxrwxrwx. 1 root root         0 Dec 29 22:55 d1.original.swapuuids
-rwxrwxrwx. 1 root root 121741198 Dec 29 22:55 d1p1.img
-rwxrwxrwx. 1 root root        74 Dec 29 22:55 d1p2.img
-rwxrwxrwx. 1 root root       194 Dec 30 00:34 d1.partitions

The content of d1.minimum.partitions:

label: dos
label-id: 0x038fb017
device: /dev/**sda**
unit: sectors

/dev/**sda1** : start=        2048, size=      382149, type=83, bootable
/dev/**sda2** : start=     2099200, size=     8386560, type=8e

I have tried to edit the files to point to the correct /dev/ path as a quick fix, but it seems that FOG do not use these files doing the deploying process.

The deployment process gives the following errors: error1.jpg and error3.jpg. error2.jpg is not so much an error, but more a ohh crap, it seems to restore to /dev/sdaX.

How do I fix this - for an normal Windows admin, it seems like some sort of detecting of available disks on the target system is not working as expected, and the system is just defaulting to sda.

Any help would be appreciated
/Jonas