[bcole]

not sure why but the hda1 (1st partition) was empty it should have all the *up and *smp files from /boot
on hda2 (2nd partition) + the /grub dir with a grub.conf file. there is script in /install_tools called mkboot.sh inside of it I could see that it creates the grub.conf from the type of system your running copied the portion for my system and created the /grub/grub.conf file. after that when I rebooted my hyperterminal was allowing me to see what was going on
no more hangs. able to see that I found the proper ip and could connect the recovery panel reinstall the os. Guardian also does not seem to want to propagate to drives which have a portion of the same ver OS
I’m assuming all you need to do is smoke the kernels from partition 1&2 and it would treat it as if it was
new and replicate itself.
New related issue
I read that you should be able in debug run “co de format 10000 /reinit” to have snap reinit the drive to it’s full capacity but Guardian OS isn’t recognizing the command is that a SnapOS specific command
Or am I still missing something?

Thanks again

FYI
1st partition contains
a----- 2776780 30-Nov-109 14:36 Guardian-initrd.smp
a----- 2766523 30-Nov-109 14:36 Guardian-initrd.up
a----- 407025 30-Nov-109 14:36 System.map-gos-smp
a----- 385298 30-Nov-109 14:36 System.map-gos-up
a----- 19649 30-Nov-109 14:36 config-gos-smp
a----- 19627 30-Nov-109 14:36 config-gos-up
-d---- 0 30-Nov-109 14:36 grub
-d---- 0 30-Nov-109 14:36 lost+found
a----- 1320674 30-Nov-109 14:36 vmlinuz-gos-smp
a----- 1250189 30-Nov-109 14:36 vmlinuz-gos-up

./grub:
total 130
-d---- 0 30-Nov-109 14:36 .
-d---- 0 30-Nov-109 14:36 ..
a----- 709 30-Nov-109 14:36 grub.conf
a----- 512 30-Nov-109 14:36 stage1
a----- 131008 30-Nov-109 14:36 stage2