Unsolved
1 Rookie
•
11 Posts
0
406
February 19th, 2021 09:00
AVE 19.x on VMWare 6.5 from .ovf. /space filesystem dirty?
Hi all,
I am new to AVE and trying to deploy 19.4 on latest VMware ESXi/vSphere 6.5 from .ovf
Having downloaded, checked the checksum etc. and deployed the VM (following the manual religiously), on bootup I found that the /space filesystem was dirty. Is this expected behaviour? Am I doing something wrong?
After this I thought to try version 19.2, again from .ovf. That was even worse. avenetconfig couldn't write logs on /space without the filesystem being repaired. After running an xfs_repair on it, there was even a recursive symlink.
AVE 19.2 from .ovf first boot
AVE 19.2 from .ovf
No Events found!
ouzo12
1 Rookie
•
11 Posts
0
February 19th, 2021 09:00
ionthegeek
2 Intern
•
2K Posts
0
February 19th, 2021 12:00
I have deployed quite a few AVEs and I have never seen this issue. However, I normally use the OVA rather than the OVF.
How confident are you in the integrity of the underlying datastore?
ouzo12
1 Rookie
•
11 Posts
0
February 22nd, 2021 02:00
I am very confident in the integrity of the datastore and must have tried 10 times on Friday.
But... this morning I tried using ovftool on Linux instead of doing "Deploy OVF Template..." from the vSphere web client. And when I started the VM, /space was clean!
So perhaps the problem was to do with the fact that I was selecting the .ovf file AND the .vmdk file when doing "Deploy OVF Template..." from the vSphere web client....