Topics created by david.burgess

@george1421 said in FOS fails to capture image from md RAID host:

since you referenced my tutorial I assumed you are using the intel raid.

I referenced your Intel RAID tutorial because I found another forum post on mdadm where you linked to it and stated that it was similar in principle. I am actually working on capturing an image from a Linux host with md RAID, and deploying the same image to other hosts with identical hardware.

By way of update, I removed the large sda device (a hardware RAID) and the USB stick, so my disk layout was thus (from the running host OS):

# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 139.8G 0 disk ├─sda1 8:1 0 300M 0 part ├─sda2 8:2 0 30G 0 part │ └─md0 9:0 0 30G 0 raid1 / └─sda3 8:3 0 2G 0 part └─md127 9:127 0 2G 0 raid1 sdb 8:16 0 139.8G 0 disk ├─sdb1 8:17 0 300M 0 part /boot/efi ├─sdb2 8:18 0 30G 0 part │ └─md0 9:0 0 30G 0 raid1 / └─sdb3 8:19 0 2G 0 part └─md127 9:127 0 2G 0 raid1

I then configured the following in FOG, with the noted outcomes:

Host Primary Disk: /dev/md126 (equivalent to md0 on live system above)
Image Type: Multiple Partition Image - All Disks (3)
Host Kernel Arguments: mdraid=true
Outcome: fails to find disks

Host Primary Disk: /dev/md126 (equivalent to md0 on live system above)
Image Type: Multiple Partition Image - Single Disk (2)
Host Kernel Arguments: mdraid=true
Outcome: fails to read partition table

Host Primary Disk: /dev/sdb
Image Type: Multiple Partition Image - Single Disk (2)
Host Kernel Arguments: [not noted. I forget]
Outcome: fails to read partition table

Host Primary Disk: /dev/sda
Image Type: Multiple Partition Image - All Disks (3)
Host Kernel Arguments: [none]
Outcome: capture succeeds. Deployment on new system succeeds. System boots and partition table on sda looks correct. md127 is lost. Partition table on sdb is not correct:

# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 139.8G 0 disk ├─sda1 8:1 0 300M 0 part ├─sda2 8:2 0 30G 0 part │ └─md0 9:0 0 30G 0 raid1 / └─sda3 8:3 0 2G 0 part sdb 8:16 0 139.8G 0 disk ├─sdb1 8:17 0 1G 0 part └─sdb2 8:18 0 138.8G 0 part

I’m not sure if the deployment procedure touched sdb or not. I suspect not. I will try again and watch closer or record it. I suppose I can rebuild my RAIDs from here, but I would of course prefer to have FOG automate that process to the extent possible.

Edit: added FOG settings detail.

@david-burgess @Wayne-Workman Using the latest dev-branch version you should be able to use disk size or WWN or disk identifier to force disk order. It’s a known issue that NVMe drives get enumerated in different order by the Linux kernel.

Search the forums for “nvme wwn” and you should find a topic with helpful information on this.

@george1421

This is helpful, thanks.

@sebastian-roth said in Image capture: reading partition tables failed:

@david-burgess You might want to point to a specific Primary Disk within the host settings, e.g. /dev/sda

Thank you. This was the fix.