Best posts made by alv000h

Server

• FOG Version: 1.3.0
• OS: Ubuntu 16.04.1 LTS

Client

• Service Version: Debian Lenny
• OS: Debian lenny (any modern Linux with virtio block driver)

Description

During Image Creation or Image Restore disks are not found if using paravirtual drivers (virtio).

When a VirtualMachine uses VirtIO (KVM/VMware) or (presumibily) XEN vbd disk, during capture/deploy process fog reports this error: “Cannot find disk on system (getHardDisk)”

I have see the code and I think it could be fixed adding the next Major numbers to the lsblk filter: 202(Xen) and 253 (VirtIO)

So, the code will be something like this:

cat fogproject/src/buildroot/package/fog/scripts/usr/share/fog/lib/funcs.sh
...snip...
getHardDisk() {
    [[ -n $fdrive ]] && hd=$(echo $fdrive)
    [[ -n $hd ]] && return
->>> local devs=$(lsblk -dpno KNAME -I 3,8,9,179,202,253,259 | uniq | sort -V) <<<-
    disks=$(echo $devs)
    [[ -z $disks ]] && handleError "Cannot find disk on system (${FUNCNAME[0]})\n   Args Passed: $*"
    [[ $1 == true ]] && return
    for hd in $disks; do
        break
    done
}

Support for Rescue Imaging (force and rescue partclone.dd options) will be great, so you can generate Rescue Images from failing harddrives (or corrupted FS) for posterior analisys (ex. testdisk / photorec processing)

I propose add this option in Image Management (as image type, maybe RAW RESCUE??) or in Create Capture task as additional option.

Why in Create Capture task? Figure you try to Image capture a server and it fails because there is a Phisical Hard Disk problem, after that, you could create another capture task with RAW Recue (to keep reading after disk read error) and send it to affected server without change image definition…

NOTE: Adding a Warning for this option will be nice, something like: “Rescue Images are intended for Corrupted FS or Physically Failing Disks (it forces continue reading after disk read errors). This process may be SLOW and may GENERATE AN INCONSISTENT IMAGE!!!”