FOG: Not detecting target disks correctly (/dev/sda vs /dev/xvda)
@JonesDK ok in the last picture from the fos linux engine. You need to be at the cmd prompt to key in lsblk. Press enter until it doesn’t prompt you to press enter any more then key in
Thanks for the quick reply!
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…
Additional research partition type 8e is LVM. I think the issue here is related to the disk type being presented to FOS Linux. In the case of LVM it can’t do expand an LVM volume, so you can only deploy the golden image to hard disks the same size or larger than the golden image. Also if you deploy to a larger hard disk the LVM volume will not expand to the size of the disk. You will have to do that by hand or by a startup script in your golden image.
Well this is an interesting one. Its possible that FOG doesn’t fully support the new disk structure of Centos8.
With that said we need to collect a bit if information on what FOS Linux is seeing vs what Centos8 is reporting.
On your golden / reference image run and post the outputs of these commands.
Then schedule a deploy to a target system, but before you schedule the task, check the debug checkbox, then schedule the task.
PXE boot the target computer
After a few screens of text where you need to clear with the enter key you will be dropped to a fos linux command prompt
OK I think I’m heading down the wrong path, if this was hardware related then this would be the right path, but in this case its the logical (OS) side. So the difference between /dev/sda and /dev/xvda1 is how the OS sees the devices. FOS linux sees /dev/sda and Centos8 sees /dev/xvda which is OK. Now the hypervisor may be the “hardware” bit I’m speaking about (sorry about bouncing back and forth here).
Lets keep going with the above, once you are at the FOS Linux command prompt key in:
And post all here. Lets see what FOS Linux sees on this hypervisor.