8 Replies Latest reply: Sep 23, 2013 10:14 PM by sgrappone
Shaggy Level 1 Level 1 (50 points)

Hi,

 

We are having a major issue with one of our XSAN setups. During my breah one of the Xsan controller crashed and burned. So a college that to resuce it by rebuilding the contoller and adding the Luns to the Xsan volume.

 

The files are not showing up but they are still there when doing a data recovery scan.

So where I Need help with (never done this before) to get the files back. What would be next steps to get the data back?

Oh yeah, I will veryfy this today but I think the LUNS have the same identifiers and LUN ID asigned as the previous controller settings.

 

This Xsan setup is made out of Mac Pro Mountain Lion Xsan 3.0 (controller), two Promise Vtrak E-Class Raids and one Sandbox.

 

Appreciate any help thanks!

  • 1. Re: HELP (after XSAN controller crash files are not accessible)
    sgrappone Level 1 Level 1 (5 points)

    I would be more than happy to help you, unfortunately I do not have that much information, I have some questions below.

     

    -Are you able to mount a volume with nothing in it?

    -Did you have a backup of the configuration files?

    -What do you mean by "Data recovery scan?"    are you talking about cvfsck?

    -If you are referring to a cvfsck what flags did you use after the command for example did you run cvfsck -nv

    -What are the logs saying?

     

    If you want me to login and fix it please let me know the best way to chat. e-mail, phone, skype.

  • 2. Re: HELP (after XSAN controller crash files are not accessible)
    Shaggy Level 1 Level 1 (50 points)

    Hi sgrappone

     

    -Are you able to mount a volume with nothing in it?

    Correct

    -Did you have a backup of the configuration files?

    I would have to check.

    -What do you mean by "Data recovery scan?"    are you talking about cvfsck?

    No a third party Data recovery software was used.

    -If you are referring to a cvfsck what flags did you use after the command for example did you run cvfsck -nv

    I can run that code in the morning.

    -What are the logs saying?

    I will check th elogs tomorrow when I get back into the shop. I do recall that coworker mentioned first it had icb mismatch. But when the new controller went online the error wasnt present. I will check in the morning.

     

     

    Thanks!

  • 3. Re: HELP (after XSAN controller crash files are not accessible)
    Shaggy Level 1 Level 1 (50 points)

    Here is the result for cvfsck -nv

     

    Re-creating File System cvfsck Directory '/Library/Logs/Xsan/data/XSAN/trace'.

     

     

    Created directory /tmp/cvfsck15730a for temporary files.

    Creating MetadataAndJournal allocation check file.

    Creating Video allocation check file.

     

     

    ** NOTE ** Read Only Check.

    File system journal will not be recovered.

    The results may be inconsistent and mis-leading.

     

     

     

     

    Super Block information.

      FS Created On               : Tue Aug  6 13:15:39 2013

      Inode Version               : '2.7' - 4.0 big inodes + NamedStreams (0x207)

      File System Status          : *Dirty*

      Allocated Inodes            : 1536

      Free Inodes                 : 1527

      FL Blocks                   : 1

      Next Inode Chunk            : 0x2934

      Metadump Seqno              : 0

      Restore Journal Seqno       : 0

      Windows Security Indx Inode : 0x5

      Windows Security Data Inode : 0x6

      Quota Database Inode        : 0x7

      Client Write Opens Inode    : 0x8

     

     

    Stripe Group MetadataAndJournal             (  0) 0x2ba7b90 blocks.

    Stripe Group Video                          (  1) 0x3691cc40 blocks.

     

     

    Inode block size is 1024

     

     

    Building Inode Index Database 1536 (100%).       

       1536 inodes found out of 1536 expected.

     

     

    Verifying NT Security Descriptors

     

     

    Verifying Free List Extents.

     

     

    Scanning inodes 1536 (100%).         

     

     

    Sorting extent list for MetadataAndJournal pass 1/1

    Updating bitmap for MetadataAndJournal extents 4 (100%).                   

     

     

    Checking for dead inodes 1536 (100%).         

     

     

    Checking directories 1 (100%).        

     

     

    Scanning for orphaned inodes 1536 (100%).       

     

     

    Verifying link & subdir counts 1536 (100%).         

     

     

    Checking free list. 1536 (100%).          

    Checking pending free list.                       

     

     

    Checking Arbitration Control Block.

     

     

    Checking MetadataAndJournal allocation bit maps (100%).        

    Checking Video allocation bit maps (100%).        

     

     

    File system 'XSAN' was modified.

     

     

    File system 'XSAN'. Blocks-915524672 free-915514163 Inodes-1536 free-1527.

     

     

    File System Check finished.

  • 4. Re: HELP (after XSAN controller crash files are not accessible)
    Shaggy Level 1 Level 1 (50 points)

    Anybody that can help me out here?

  • 5. Re: HELP (after XSAN controller crash files are not accessible)
    sgrappone Level 1 Level 1 (5 points)

    Hi Shaggy, Give me a call I will give you a hand.

     

    Steve

    sgrappone@belltechlogix.com

  • 6. Re: HELP (after XSAN controller crash files are not accessible)
    Shaggy Level 1 Level 1 (50 points)

    Call you over iChat?

  • 7. Re: HELP (after XSAN controller crash files are not accessible)
    Shaggy Level 1 Level 1 (50 points)

    Hi Steve are you still willing to help out?

     

    What is the process?


    Thanks

  • 8. Re: HELP (after XSAN controller crash files are not accessible)
    sgrappone Level 1 Level 1 (5 points)

    I will definately help you out. I apologize that I do not have iChat. But you can e-mail my personal e-mail sgrappone@icloud.com