Thanks for the suggestion. I would love to get this existing system back running since I've spent so much time troubleshooting. I do have multiple iscsi and nfs targets available on that zone showing up on both the hypervisor xsconsole/vcenter and in cloudstack. Since I don't have any running VMs at the moment I can try removing them all and re-adding back etc and then proceed with trying to add the secondary storage back. If that fixes it then obviously something happened with that initial failed primary storage that caused the issue, which maybe I should have asked for advice at that point.
I will try what you suggested and keep you posted with progress. Best regards, Ben Linton Network Operations Hivelocity Ventures Corp. http://www.hivelocity.net 1-888-869(HOST)4678 x 222 Fax (813) 902-6477 Skype/AIM - HivelocityBen MSN - b...@hivelocity.net On Jan 28, 2013, at 5:04 PM, Ahmad Emneina <aemne...@gmail.com> wrote: > On 1/24/13 11:21 AM, "Ben Linton" <b...@hivelocity.net> wrote: > >> Our latest issue stemmed from an issue with a failed primary storage > >> iscsi target. Our system VMs were trying to boot using this target > >> and we had quite a time removing this old failed target. During this > >> process we upgraded to 4.x to try to use the "Force" option on primary > >> storage. I eventually removed the primary storage entry from the > >> database using a procedure I found online. After that the system VMs > >> weren't trying to boot off of that target however there was some issues > >> with secondary storage so I tried to remove and re-add as this fixed a > >> similar issue we had in the past. However now we can't add storage back > >> and I've search and tried many different things to no avail." > > > Can you check if the primary storage youre trying to add is already > > mounted on the hypervisor. If its already present, I suspect > > its failing to mount on the compute hosts, remove the primary storage mount > > and readd it back to cloudstack. > > > For the system vm's you should set your zone to a disabled state, mark the > > vm's as stopped in the database, and delete/destoy them via api or ui. > > They should be recreated on a primary storage that doesn¹t have issues.
smime.p7s
Description: S/MIME cryptographic signature
