Dear Simon,
I have tried the command you gave me in SR to increase the
heapsize of memory that LSOM has allocated, then did reboot,
with no success on 192.168.240.55,
it still fails to bring up the Disk Group with memory error ...
Please find below some screenshots, as I find it very strange what is happening
and I would like to know what is going wrong here.
As you mentioned earlier, the current setup is unsupported, but still I was not able
to find anything faulty with hardware and as it works on the remaining nodes
(and actually did recover same issue after 5.5 U2 update on node .54),
I see no reason why it fails on .55
![error1.png]()
As you will notice here, I see that the system finds VSAN has 3.4 TB of data,
which is correct and my data is within this (same size was before initial failure)
![error2.png]()
But the strange thing, is that inside VSAN, I can't see these data anywhere,
only few GB of some ISO images I had...
![error3.png]()
Where is all these 3.4 TB of data and why I cannot access them ???
Additionally, it does not make much sense how it is possible VSAN to face this failure and dataloss,
as the policy set before failure, was to have the data in 4 nodes, into 2 RAID-1 stripes, each of them,
consisted by 2 RAID-0 datasets...
So, normally, with just one node down / inaccessible, I see only 1 of 4 nodes is down, which means
just 1 raid-0 part is missing, the other one stripe of the raid 1 and the half raid0 are OK and it totally
makes no sense to me why I cannot access the data...
Any ideas ???
Additionally, I have run "vsan.support_information" and have sent via FTP a detailed log,
plus info about it via the SR, so please check this and let me know what can be done...
Thanks on advance for any help on this, I hope there is a way to save my data...
![error4.PNG]()
![error5.png]()
![error6.png]()