Q: xSan doesen't mount a volume after a storage recovery
Hi,
We are having a serious issue with one of our XSAN attached storage . During a storm, a storage attached to xSan stopped his service due to a 3 hd fail.
After a data recovery on a broken disks and some configuration tweaks, we had a storage back to work.
After connecting a storage to a xSan controller, we can observe that storage is recognized as a volume, but unfortunately for us, Xsan doesn’t mounted a volume folder structure.
We are very experienced in data recovery but we do not have a specific xSan knowledge , so initially we decided to proceed to analyze a volume through a data recovery software such as “Data Rescue” and “Disk drill”.
This approach helped us to recover a number of files perfectly in good condition (we are speaking about a video clips files very big and perfectly functional) . Only a small number of files was damaged in some parts. We are sure that a storage was reconstructed well, but something happened anyway as some files are non in perfect shape and xSan does not mount a volume.
Out major problem is that a storage is 76 Tbyte big and software approach is very time consuming process. More, we need only most recent files, and search by software is very dispersive and uncertain.
So we decided to try some xSan more specific approach, and after some readings, we have run
sudo cvfsck -j VolumeName
The command produces a “segmentation fault” !
Later we have run a
sudo cvfsck -nv VolumeName
cvfsck produced a number of messages and reported on iNodes problems. After 2-3 minutes cvfsck stopped progress without father activity during a “cleaning orphaned inodes” os something similar.
We are looking for help and collaboration on solving xSan access to folder structure or files in some way.
We Appreciate very much any help thanks!
Infolab data Italy
<Edited by Host>
Posted on Sep 2, 2014 7:53 AM