Intel Raid0 Image Capture

[Sebastian Roth]

@george1421 Great stuff man! Just wondering that you had the same md127 : inactive ... Possibly that’s just the way it is with those fake RAID controllers?

@jpmartin George’s mdadm -D /dev/md126 seems to be very handy and informative. Give that a try!

No image file found that would match the partitions to be restored
args passed /dev/md126 /images/WIN7ENTX64 all

Guess that’s just a matter of tuning the init scripts to make this work. Will have a look tomorrow. Marking this unread…

[george1421]

I left the FOS kernel running. Now that I’m home I’m able to remote into FOS to continue debugging.

Looking at what FOS has done so far, I can see that it did create the partitions

Disk /dev/md126: 149.1 GiB, 160058834944 bytes, 312614912 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 131072 bytes / 262144 bytes
Disklabel type: dos
Disk identifier: 0x9bfaf142

Device       Boot   Start       End   Sectors   Size Id Type
/dev/md126p1 *       2048   1023999   1021952   499M  7 HPFS/NTFS/exFAT
/dev/md126p2      1024000 312614911 311590912 148.6G  7 HPFS/NTFS/exFAT

I’m going to keep walking down the fog.download script to see where its falling down.

Here is the exact error:

 * Attempting to expand/fill partitions..............Done
 * Press [Enter] key to continue

 * Seems like you are trying to restore to an empty disk. Be aware this will most probably cause trouble.

   +--------------------------------+
   |  Attempting to download image  |
   +--------------------------------+
   |         Using Partclone        |
   +--------------------------------+
##############################################################################
#                                                                            #
#                         An error has been detected!                        #
#                                                                            #
##############################################################################
No image file(s) found that would match the partition(s) to be restored (performRestore)
   Args Passed: /dev/md126 /images/WIN7ENTSP1X6401 all

Its dieing somewhere in this section in funcs.sh in the performRestore() sub.

    local disk_number=1
    local part_number=0
    local restoreparts=""
    local mainuuidfilename=""
    [[ $imgType =~ [Nn] ]] && local tmpebrfilename=""
    for disk in $disks; do
        mainuuidfilename=""
        mainUUIDFileName "$imagePath" "$disk_number"
        getValidRestorePartitions "$disk" "$disk_number" "$imagePath" "$restoreparts"
        [[ -z $restoreparts ]] && handleError "No image file(s) found that would match the partition(s) to be restored (${FUNCNAME[0]})\n   Args Passed: $*"
        for restorepart in $restoreparts; do

[george1421]

With the last bit of brain power I have left today I think I narrowed it down to the following (I don’t know what I’m looking at only that it doesn’t work"

In /usr/share/fog/lib/funcs.sh at function: getPartitions()

There is a call to lsblk that should be returning something, but its returning and empty string instead.

This is the command
lsblk -I 3,8,9,179,259 -lpno KNAME,TYPE /dev/md126 | awk '{if ($2 ~ /part/) print $1}'

If I shorten the command to just the lsblk without the awk I get

# lsblk -I 3,8,9,179,259 -lpno KNAME,TYPE /dev/md126
/dev/md126   raid0
/dev/md126p1 md
/dev/md126p2 md

If I run the full command on my fog server using /dev/sda I get

# lsblk -I 3,8,9,179,259 -lpno KNAME,TYPE /dev/sda | awk '{if ($2 ~ /part/) print $1}'
/dev/sda1
/dev/sda2

Running lsblk alone on FOS

lsblk /dev/md126
NAME      MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
md126       9:126  0 149.1G  0 raid0
|-md126p1 259:4    0   499M  0 md
`-md126p2 259:5    0 148.6G  0 md

Running lsblk alone on FOG

# lsblk
NAME            MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
fd0               2:0    1    4K  0 disk
sda               8:0    0   20G  0 disk
├─sda1            8:1    0  500M  0 part /boot
└─sda2            8:2    0 19.5G  0 part
  ├─centos-root 253:0    0 17.5G  0 lvm  /
  └─centos-swap 253:1    0    2G  0 lvm  [SWAP]
sr0              11:0    1    4G  0 rom

Hopefully the devs can make heads or tails of why the lsblk command is not returning the expected value.

[edit] Heck, now that I spell it out I see the issue. The awk regular expression is only looking for part in the type column. awk '{if ($2 ~ /part/) print $1}' But the mdraid its type md not part !!!

[Tom Elliott]

@george1421 what was the function the error came from?

[george1421]

@Tom-Elliott getPartitons from download. I’ll have to look at the code again

[edit] here is the call chain
fog.download:restorePartition->funcs.sh:runPartprobe->funcs.sh:performRestore->funcs.sh:getValidRestorePartitions->funcs.sh:getPartitions

[george1421]

Updating the trouble code
lsblk -I 3,8,9,179,259 -lpno KNAME,TYPE /dev/md126 | awk '{if ($2 ~ /part/) print $1}'

to
lsblk -I 3,8,9,179,259 -lpno KNAME,TYPE /dev/md126 | awk '{if ($2 ~ /md/) print $1}'

Allowed the system to image in debug mode. I doubt it will run because I don’t have the raid drivers in my pushed image, but imaging did complete fully without error.

[jpmartin]

@Sebastian-Roth said in Intel Raid0 Image Capture:

@jpmartin George’s mdadm -D /dev/md126 seems to be very handy and informative. Give that a try!

No image file found that would match the partitions to be restored
args passed /dev/md126 /images/WIN7ENTX64 all

Guess that’s just a matter of tuning the init scripts to make this work. Will have a look tomorrow. Marking this unread…

Here you go:

mdadm -D /dev/md126.txt

[jpmartin]

@george1421 Have you been able to capture an image from the machine?

Do you think it’d be possible to capture a Single Disk Resizable image from these fake raid machines?

[Tom Elliott]

I updated the source for this to allow for if ($2 ~ /part/ || $2 ~ /md/).

Hopefully this will work for you needs.

[george1421]

@Tom-Elliott That should do it very nicely!!

The OP will need to update to the latest release of the FOG trunk once the change has been pushed. I can confirm that it works. I still have my test rig set running.

As for “Do you think it’d be possible to capture a Single Disk Resizable image from these fake raid machines?”. I was able to deploy to this machine once I hacked the init (not needed now) so I also assume you should be able to capture resizeable. My deploy was a single disk resizeable image.

[Tom Elliott]

@george1421 I don’t know if it will “capture” unless the primary device is set though.

[george1421]

@Tom-Elliott Right. I know I have a wall of text in this one. But to use these fake raid systems you have to update the host registration with these settings. Without these set FOS will only see just a bunch of disks and not the array.

Host Kernel Arguments: mdraid=true
Host Primary Disk: /dev/md126

[edit] Corrected the extra bits in the host primary disk

[jpmartin]

@george1421 where does “Here” come from in “/dev/md126Here” in your post just below?

[Tom Elliott]

@jpmartin I think he was just typing. Ultimately, remove the “Here” as I highly doubt you all have a “/dev/md126Here” labeled device. :smiley_face_here:

As we don’t have smilies I suppose it would be better to add a bit that I’m just playing around.

[jpmartin]

@Tom-Elliott That’s what I was thinking too. But was just checking to make sure I didn’t miss anything.

Have the changes been pushed to the svn trunk so I can update and test?

[george1421]

@jpmartin said in Intel Raid0 Image Capture:

@george1421 where does “Here” come from in “/dev/md126Here” in your post just below?

Sorry trying to do my job and play at the same time, victim of copy/paste. Tom is right its just /dev/md126

[Tom Elliott]

Yes, changes have been pushed and init’s are updated. Reinstalling will work as well, but I still say to just update.

[jpmartin]

@Tom-Elliott Excellent. I’ll update and report back.

[george1421]

Bingo!! my test bench system is deploying!!

[jpmartin]

Running a Resizable Capture now.

Fog is resizing the file system currently.

Will test deploy after this image is captured.