rdeployt on usb to pull windows XPe image from DS

[Migration User]

Were using rdeployt on a linux boot drive to run a script to install some images.  It works great on HP t5730s but on the HP t5720 if fails on restart giving the following message:

Verifying DMI Pool Data .........
Booting Production Partition...

And then stays there forever.  I've tried manually removing the automation partition and trying again but this does not work.  Is this possibly a driver issue or maybe something with my script?  Below I've pasted the script we use in rc.startup

In rc.startup we simply call a menu structure in order for our deployment team to deploy the images, here is the menu script:

#!/bin/sh

f_reboot () {
shutdown -r -fqs now
}

f_atx5720 () {
echo "Starting Image..."
/mnt/ds/rdeploy/Linux/rdeployt -md -f/mnt/ds/ThinClient/Images/ATx5720.img
f_reboot
}

f_atx5730 () {
echo "Starting Image..."
/mnt/ds/rdeploy/Linux/rdeployt -md -f/mnt/ds/ThinClient/Images/ATx5730.img
f_reboot
}

while : # Loop forever
do
printf "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"
cat << !

I M A G E   T E R M I N A L

1. Autotime 5720
2. Autotime 5730
3. Quit
!

printf "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"
echo -n " Your choice? : "
read choice

case $choice in
1) f_atx5720 ;;
2) f_atx5730 ;;
3) exit ;;
*) echo "\"$choice\" is not valid "; sleep 2 ;;
esac

[Migration User]

does anyone have any suggestions?

[Migration User]

Ok i've tried some things to troubleshoot.

On our DS, we currently have two linux kernels:

2.6.27.7 Build 6.9.9172 and
2.6.18.8 Build 6.9.9020

When I create a Boot disk using the 2.6.27.7 kernel the HP t5720 will hang at
"Verifying DMI Pool Data .........
Booting Production Partition..."
And the t5730 re-images just fine. 

However when I use the 2.6.18.8 kernel to create the boot disk, the HP t5720 seems to take a while using rdeploy (around 30 minutes) but the re-image process completes successfully and no hanging like the other kernel.
Also, the t5730 acts a little strange using this kernel but it also completes successfully. 

Im really running out of ideas here.  I've looked into compiling my own drivers for the t5720 and using that in the 2.6.27.7 kernel but I'm running into issues there as well.  If anyone has any additional info or suggestions based on this new information i'd really really appreciate it!  Thanks

[Migration User]

I have solved this issue.

Turns out I needed to use the 2.6.18.8 kernel for whatever reason as well as add the -restoresig switch to the rdeploy command which is required for all XPe restores...