Volume won't mount after power faillure

remdem · partially protected Joined: 24 Jan 2011 Posts: 6

Hi all
Please excuse my english, I'm french!
So I'm using Xsan 2.2 on Leopard with two Promise raid.
I have 2 volumes on for the video editing and prod which is mounted on mac pros, and one for network home and sharing which is shared via AFP by an Xserve.

2 days ago we had some power failure and and the UPS felt down.
On monday morning one of the two promise was red and I had to rebuild the data on 1 of the disk.

Now one of my two XSAN Volume isn't mounting anymore.
On Xsan admin it appears with a red X on the volume tab.
If I try to start the volume, it comes up for a few seconds, then a yellow I prints on the volume, and then a red X again.

When I try a cvfsck -wv it crashes after a while saying:

……
*Error*: Cannot map NT security descriptor block for NT Security descriptor: = 0x14498a8a450
Removing Bad NT Security descriptor: = 0x14498a8a450
*Error*: Cannot map NT security descriptor block for NT Security descriptor: = 0x1449c16609e
Removing Bad NT Security descriptor: = 0x1449c16609e
*Error*: Cannot map NT security descriptor block for NT Security descriptor: = 0x1449f63bb99
Removing Bad NT Security descriptor: = 0x1449f63bb99
*Fatal*: Fatal error attempting to verify NTSD's
*Error*: Fatal error checking NTSD's

*Critical*: File System Check finished - with errors.

I've already tried to disable the ACL on this volume but without any improvement.
I still cannot run the cvfsck command till the end.

the only hope I have is that a cvfsck -x XSAN_1 still prints a list of the files that were on the volume.

Do you have any idea of something I could try?
Thanks a lot.
Rémi

singlemalt · Xsan Master Joined: 27 Feb 2009 Posts: 109

Hi,
Are you really running just 2.2 and not 2.2.1? there were some improvements in cvfsck that came with 2.2.1. If you run
/Library/Filesystems/Xsan/bin/cvversions
on the mdc it will print which version/build you're running.
411.3 9M1207 is 2.2.1 for Leopard
412.3 10M310 is 2.2.1 for Snow Leopard

411 9M1079 is 2.2 for Leopard
412 10M220 is 2.2 for Snow Leopard

remdem · partially protected Joined: 24 Jan 2011 Posts: 6

You're right I'm running 2.2.1:
Server Revision 3.5.0 Build 7443 Branch branches_35X (411.3)

Not a lot imporvement since last message, cvfsck still don't stop before the end.
I have been able to get the list of the files on the volume and to restore some of these files using cvfsdb, but still not mounting.

Thanks for your help!

morphenine · Xsan Master Joined: 22 Dec 2008 Posts: 126

Try a cvfsck -jv to repair dirty journals
Another thing is I always use cvfsck -nv first (read-only) if -wv crashes it can do more damage. If -nv crashes you can still track down that problem without creating more. I make sure -nv always finishes first before I run a -wv.

remdem · partially protected Joined: 24 Jan 2011 Posts: 6

Thanks!

So cvfsck -jv seems to finish nicelly:

Attempting to acquire arbitration block... successful.

Creating MetadataAndJournal allocation check file.
Creating Data-1 allocation check file.
Creating Data-2 allocation check file.

Recovering Journal Log.

File System Journal Recovery completed successfully.

But tring to run read onlny test useing -nv it stops with the same error
message that the read right one:

Removing Bad NT Security descriptor: = 0x108006d0bdb
*Fatal*: Fatal error attempting to verify NTSD's
*Error*: Fatal error checking NTSD's

remdem · partially protected Joined: 24 Jan 2011 Posts: 6

Ok, so I'm still stuck with my XSAN problem.
I've tryed some other commands like
cvfsck -vCw
or
cvfsck -cKw
But with no luck, and always the same error message about NT Security Descriptor.
Do you know what these Bad NT Security descriptor are, and if there is a way to force delete them, or something?

I begin to think that there is no way I can get my volume back to work, so is there a hack or any piece of software I can try to copy some datas to another volume?

If you have anything that can help....
Thanks!
Rémi

sf809 · Been around the blocks Joined: 21 Jan 2010 Posts: 27

Hi Rémi,

maybe this Link helps you:

http://www.consol.com/apple-know-how/mac-operations/xsan-data-recovery/

Regards
Seb.

remdem · partially protected Joined: 24 Jan 2011 Posts: 6

Thanks,
I will give it a try.
I'm still hoping for a way to get the volume back to work, but his hack can be a good workaround.

Thanks again!

ravi · Xsan Master Joined: 06 Mar 2008 Posts: 149

remdem · partially protected Joined: 24 Jan 2011 Posts: 6

Thanks Ravi.
It sounds to me like a good idea, as the security descriptor really seem to be the matter for cvfsck.

But I took a look at the help page of cvfsdb and I'm not sure how to do it.
Is the command something like ondisk, or inode?

If you have further infos, I'm interested!
Thanks again.
Rémi

ravi · Xsan Master Joined: 06 Mar 2008 Posts: 149