Also check to ensure that you have allowed root access from the storage network which the XenServer hosts are accessing the NFS shares presented by Nexenta. Try manually mounting the NFS shares on each XenServer host of the pool to ensure you can mount the share, and also ensure that you can read and write from it: mount -t nfs <storage server host>:/<NFS export path> /<mountpoint> Regards,
Kristoffer Sheather Cloud Central Scale Your Data Center In The Cloud Phone: 1300 144 007 | Mobile: +61 414 573 130 | Email: [email protected] LinkedIn: | Skype: kristoffer.sheather | Twitter: http://twitter.com/kristofferjon ---------------------------------------- From: "Kirk Kosinski" <[email protected]> Sent: Sunday, July 14, 2013 12:45 PM To: [email protected] Cc: "Kirk Jantzer" <[email protected]> Subject: Re: Can't get system vm's to start Hi, Kirk. How many hosts are in the XS pool? It seems like perhaps the storage is inaccessible from one of the hosts. "xe pbd-list sr-uuid=f09e0cef-0412-38f8-889c-ffa742a6084c" will probably show that the PBD is unplugged for that host, so it may be unable to access it for some reason (permissions, networking). If there's only one host in the pool, it may be unable to access the storage. It could be due to permissions or networking, or maybe an NFS version mismatch. Make sure Nexenta is allowing NFS v3 since that is all that XenServer supports. Best regards, Kirk On 07/13/2013 07:33 PM, Kirk Jantzer wrote: > I can't login to a vm that doesn't exist ;-) > > Regards, > > Kirk Jantzer > http://about.me/kirkjantzer > On Jul 13, 2013 10:30 PM, "Dave Dunaway" <[email protected]> wrote: > >> Take the usual steps, log into the ssvm if you can and run the chechssvm.sh >> or whatever it is called script (check the docs, I assume it's listed >> there). Make sure the SSVM can reach the management server on tcp 8250, and >> the host that has the NFS mount for your sec storage is up and working >> properly (ie: check that the NFS server is good to go, exports, bacon >> sandwiches). >> >> hth. >> >> >> On Sat, Jul 13, 2013 at 9:53 PM, Kirk Jantzer <[email protected] >>> wrote: >> >>> CS 4.1. Tried several different versions of Xen. Using Nexenta to present >>> NFS. Storage attaches to CS fine. I can mount both primary and secondary >> to >>> other servers and browse/read/write, but these keep showing up in the >> log: >>> >>> (of mention, this is the same hardware/network we used for our 4.0 >> install) >>> >>> 2013-07-13 17:36:12,642 WARN [xen.resource.CitrixResourceBase] >>> (DirectAgent-1:null) ModifyStoragePoolCommand add XenAPIException:Can not >>> see storage pool: f09e0cef-0412-38f8-889c-ffa742a6084c from on >>> host:40455980-acdf-4e56-8415-7dcde2db9e05 >>> host:40455980-acdf-4e56-8415-7dcde2db9e05 >>> pool: <nfsserverip>/volumes/store/primary >>> com.cloud.utils.exception.CloudRuntimeException: Can not see storage >> pool: >>> f09e0cef-0412-38f8-889c-ffa742a6084c from on >>> host:40455980-acdf-4e56-8415-7dcde2db9e05 >>> >>> 2013-07-13 17:36:12,648 WARN [storage.listener.StoragePoolMonitor] >>> (AgentTaskPool-1:null) Unable to connect host 3 to pool >>> Pool[200|NetworkFilesystem] due to >>> com.cloud.exception.StorageUnavailableException: Resource >> [StoragePool:200] >>> is unreachable: Unable establish connection from storage head to storage >>> pool 200 due to ModifyStoragePoolCommand add XenAPIException:Can not see >>> storage pool: f09e0cef-0412-38f8-889c-ffa742a6084c from on >>> host:40455980-acdf-4e56-8415-7dcde2db9e05 >>> host:40455980-acdf-4e56-8415-7dcde2db9e05 >>> pool: <nfsserverip>/volumes/store/primary >>> com.cloud.exception.StorageUnavailableException: Resource >> [StoragePool:200] >>> is unreachable: Unable establish connection from storage head to storage >>> pool 200 due to ModifyStoragePoolCommand add XenAPIException:Can not see >>> storage pool: f09e0cef-0412-38f8-889c-ffa742a6084c from on >>> host:40455980-acdf-4e56-8415-7dcde2db9e05 >>> host:40455980-acdf-4e56-8415-7dcde2db9e05 pool: >>> <nfsserverip>/volumes/store/primary >>> >>> >>> -- >>> Regards, >>> >>> Kirk Jantzer >>> http://about.met/kirkjantzer >>> >> >
