I downloaded the VSM 7 recovery cd, set up the boot partition and the iso partition on my usb drive. The server will boot and give me the option for factory install. After it starts loading everything I get an error message that says error running the kickstart script at line None. You may examine the output in //tmp/k5-script-bvovJ-.log. I can't get past this error. Has anyone run into this or do you know how to bypass it so i can get my server reloaded. I really don't want to have to go back to Suse and reload starting with 6.3.2. recovery. I am attaching a screenshot of the error. Any help would be greatly appreciated.
This particular media server was originally Redhat. Something tanked on it, so I needed to do a recovery. In trying to do a factory restore on an already existing redhat system is when I got this error. To bypass it until i can figure it out I was able to load a recovery from 6.3.2. and upgrade it to 7.0. Just need to figure out how to fix the error.
Can you clarify what you are actually using to perform the restore? "iso partition"? It sounds like you've attempted to create a bootable USB flash drive out of the ISO source image.
Do you have a USB optical drive you could try with the ISO instead? My gut says the recovery image is assuming certain /dev/sdX device ordering, and this isn't the case with a USB flash/hard drive that's been partitioned?
Let me know.
Bulletproof Solutions Inc.
I took the downloaded TAR recovery file and extracted those files, gave me a boot folder with files and an ISO file. Followed intructions, formatted my usb (used an old 6.3.2 recovery usb) copied my boot files on one partition and my iso file on the other partition (I followed Cisco's directions on creating this). The usb actually boots correctly and brings me to recovery. It then starts the install, but tanks at this spot. The TAR file I have is : Cisco_VSM-7.0.0-recovery-2.1.tar.
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...