Troubleshooting

Troubleshooting :: RE: Remote Access to XSan via Spashtop or similar ?

alavelle — Fri, 24 May 2013 16:15:53 GMT

Author: alavelle
Posted: Fri May 24, 2013 11:15 am (GMT -5)

So now a few weeks later I'm totally banging my head on a wall.

I've posted this on the Adobe forums, but figured I'd circle back here in case anyone knows more about this.

I'm trying to use sceensharing apps to allow me to edit in Adobe Pr CS6 yet despite a variety of attempts and many many hours of fiddling I haven't gotten any audio to output when scrubbing. I've tried a variety of Screen Sharing apps - my preferred one being SplashTop. They all seem to do something along the lines of installing a virtual audio device like Soundflower. This works great for sound output pretty much everwhere except when scrubbing within Adobe Premiere. For example even playing files from the media browser in Premiere works, so its specifically isolated to playback of a timeline.

System info:

Here's what I've tried:

I'm not totally familar with all the settings within Pr, so perhaps there is something I'm missing?

Or maybe I'm going about this in the wrong way and there is a better alternative then using screensharing via Splashtop? Really looking to avoid putting things on a USB drive and copying stuff back and forth.

Any help is greatly appreciated!

Thanks,
Adam

Troubleshooting :: RE: Xsan volume "greyed out" in Finder, still mounted

Rhino — Wed, 22 May 2013 20:51:07 GMT

Author: Rhino
Subject: Post subject: Xsan volume "greyed out" in Finder,
Posted: Wed May 22, 2013 3:51 pm (GMT -5)

Apparently the issue I was receiving was related to volumes being hidden. No clue what caused that yet, but it may have been related to an upgrade to OS X 10.8.3 or the Mac OS X Server.app upgrade we just performed.

In any case, I was able to fix with the help of the following link:

http://krypted.com/xsan/holy-cow-batman-my-xsan-volume-is-invisible/

Troubleshooting :: RE: Xsan volume "greyed out" in Finder, still mounted

Rhino — Wed, 22 May 2013 20:06:43 GMT

Author: Rhino
Subject: Re: Xsan volume "greyed out" in Finder, still moun
Posted: Wed May 22, 2013 3:06 pm (GMT -5)

I just got the same issue. Any chance you came up with a solution?

Troubleshooting :: RE: Cannot not mount Volume (anymore).

becurious — Wed, 22 May 2013 19:46:50 GMT

Author: becurious
Posted: Wed May 22, 2013 2:46 pm (GMT -5)

bump
should I just delete all the stuff... and... well... keep living with my backups?

Troubleshooting :: RE: uh oh...I have a ghost affinity

abstractrude — Tue, 21 May 2013 19:11:45 GMT

Author: abstractrude
Posted: Tue May 21, 2013 2:11 pm (GMT -5)

Troubleshooting :: RE: uh oh...I have a ghost affinity

returnofxsan — Tue, 21 May 2013 19:03:17 GMT

Author: returnofxsan
Posted: Tue May 21, 2013 2:03 pm (GMT -5)

Thanks for the reply, abstractrude. I may have fixed it last night. In the file /Library/Preferences/Xsan/Xsan.cfg the new stripe group was called "enhance3-spin". However it looks like affinity names are always truncated to eight characters (in 2013!). I guess because I had run the expansion twice it changed the last character of the affinity name. I changed it back to "enhance3" and I think its working. I don't have the ghost and I ran a cvfsck with no errors. I'm trying to snfsdefrag now to move the files over. It looks like this defrag operation is much slower than the original copy operation though so it will take some time to see how it fares.

So my advise to anyone new to volume expansions is run the Xsan Admin local to the server and be prepared to wait a very long time for the expand operation to complete.

Troubleshooting :: RE: uh oh...I have a ghost affinity

abstractrude — Tue, 21 May 2013 14:40:58 GMT

Author: abstractrude
Posted: Tue May 21, 2013 9:40 am (GMT -5)

so you created a new storage pool with the expansion? Lets take a look at your config file.

Troubleshooting :: uh oh...I have a ghost affinity

returnofxsan — Mon, 20 May 2013 23:20:04 GMT

Author: returnofxsan
Subject: uh oh...I have a ghost affinity
Posted: Mon May 20, 2013 6:20 pm (GMT -5)

I have tried to be so careful being new to Xsan but it looks like I've messed something up. This is Xsan 3.0 (Mountain Lion). I tried to do my first volume expansion and was following the Apple KB article which says you need to fsck the volume before and after expansion. So I did so but the expansion appeared to be stalled after 30 minutes and so I pressed stop. I later found by running top that the expand operation now does fsck during the expansion which is why it takes so long.

Turns out that it was a big mistake to stop it because I ended up having my two MDCs out of sync where one showed the new affinity and the other didn't. I ejected the MDC that showed the new affinity from the Xsan and then still had the new LUNs showing up in Xsan Admin so I could not perform the expansion. I rebooted and the LUNs were gone so I breathed a sigh of relief and did the expansion to completion.

Now I've realized that data has stopped going to the new affinity. I tried to reset the affinity for the target folder and got the error "There was some sort of error in the connection manager" and "Error: Error setting affinity". I noticed when I pick expand volume just to see what is listed, that I now have two affinities with the same name listed. One with no LUNs in it and one with the correct LUNs listed. I'm sure this ghost affinity is what is causing the problem.

Does anyone know if there is a way possibly using the command line StorNext commands that I can get in there and ninja out that bad affinity?

Thanks,
Doug

Troubleshooting :: RE: where is .auth_secret in 10.8?

returnofxsan — Thu, 16 May 2013 23:50:30 GMT

Author: returnofxsan
Posted: Thu May 16, 2013 6:50 pm (GMT -5)

When I was trying SNFX I was going to use Windows 2012 until I found out it wasn't supported. Then I tried Windows 7. I would have loved to use CentOS 6 (unix is much more in my comfort zone than windows) but there isn't ACL support in the Linux SNFX and that was a requirement.

Troubleshooting :: Block Allocation Size and metadata

aaron311 — Thu, 16 May 2013 02:19:54 GMT

Author: aaron311
Subject: Block Allocation Size and metadata
Posted: Wed May 15, 2013 9:19 pm (GMT -5)

Hello all! I have the opportunity to setup an Xsan environment from scratch, so I want to make sure I have my bases covered. As it's primarily going to be volume for video editing, I'm intending on setting the Block Allocation Size to 64 KB. From my research, it appears I can only set the block allocation size per volume, not per affinity tag. So my metadata affinity tag (and LUN) will also be using 64 KB blocks, which is not ideal. So my question is, do I set it to 64 KB for video performance and live with the non-ideal block size for metadata, or stick with the default 16 KB? I guess the last option is I'm totally misunderstanding these settings. Please set me straight! Thanks everyone.

Troubleshooting :: RE: Using Xserve RAID with xMac mini Server

wrstuden — Tue, 14 May 2013 20:36:22 GMT

Author: wrstuden
Posted: Tue May 14, 2013 3:36 pm (GMT -5)

If you already have a volume, why are you labeling LUNs? You should retain the old SAN config rather than trying to make a new one.

If you are wiping everything out, it sounds like your LUNs still have labels.

Troubleshooting :: RE: Metadata volume deleted (corrupted)

abstractrude — Tue, 14 May 2013 01:21:03 GMT

Author: abstractrude
Posted: Mon May 13, 2013 8:21 pm (GMT -5)

recovery only option. make sure you get xsan/stornext recovery services. just getting files recovered may not help

Troubleshooting :: RE: where is .auth_secret in 10.8?

lucasnap — Mon, 13 May 2013 14:25:23 GMT

Author: lucasnap
Posted: Mon May 13, 2013 9:25 am (GMT -5)

I'm curious, what client OS and version do you use for your SNFX?

I'm asking this because I had to buy the whole SN client licence for a CentOS 6 (Similar to RHEL 6) client. This because FX only went up to RHEL 5.

Troubleshooting :: RE: Metadata volume deleted (corrupted)

lucasnap — Mon, 13 May 2013 14:15:48 GMT

Author: lucasnap
Posted: Mon May 13, 2013 9:15 am (GMT -5)

I know one company who can probably help you, but it will not be cheap:

http://www.werecoverdata.com

Troubleshooting :: RE: Metadata volume deleted (corrupted)

vinnih — Sun, 12 May 2013 19:54:21 GMT

Author: vinnih
Posted: Sun May 12, 2013 2:54 pm (GMT -5)

Unfortunately resurrecting the metadata volume can not happen. We only have the the volume with the data itself but it is not accessible. Can we use the information there and somehow rebuilt the metadata?

Troubleshooting :: RE: Integration Issue

xsanguy — Sun, 12 May 2013 19:23:38 GMT

Author: xsanguy
Posted: Sun May 12, 2013 2:23 pm (GMT -5)

Also one more thing, don't name your storage pools the exact same thing. Keep labels under 8 char, and put a 1 or 2 at the end.

Troubleshooting :: RE: Metadata volume deleted (corrupted)

cinedigital — Sun, 12 May 2013 18:52:23 GMT

Author: cinedigital
Posted: Sun May 12, 2013 1:52 pm (GMT -5)

Desperate indeed, I don't think there is a way to recover your data without the metadata volume

I recommend contacting a data recovery specialist who have experience with enterprise file systems and RAID arrays

They may be able to repair the failed drive to resurrect the metadata volume

Good luck!

Troubleshooting :: Metadata volume deleted (corrupted)

vinnih — Sun, 12 May 2013 17:59:43 GMT

Author: vinnih
Subject: Metadata volume deleted (corrupted)
Posted: Sun May 12, 2013 12:59 pm (GMT -5)

Hello

I am in a desperate situation.
Our Metadata volume which was on RAID 0 instead on RAID 1 failed due to bad HDD.

Now the data volume is not accessible. Can I still reach the information there?
What can I do to save the information on the data volume?
If I connect the RAID system to a computer without XSAN and try to mount just the data volume will i be able to retrieve the information?
I do not have to say that there is critical information which costs a lot.

Thank you for your help.

Troubleshooting :: RE: Using Xserve RAID with xMac mini Server

xsanguy — Sun, 12 May 2013 02:11:20 GMT

Author: xsanguy
Posted: Sat May 11, 2013 9:11 pm (GMT -5)

What model is your Xserve? Xserve '09s run 10.8 just fine.

Troubleshooting :: Volume "not mounted" in xsan prefs; No LUNs in Xsa

xsanguy — Sun, 12 May 2013 02:09:53 GMT

Author: xsanguy
Subject: Volume "not mounted" in xsan prefs; No LUNs in Xsa
Posted: Sat May 11, 2013 9:09 pm (GMT -5)

...but it's mounted! It's mounted on the desktop, it shows in "mount" and I can read/write files to/from it...

Same behavior across all 3 clients (2MDC, 3 client system)

Thoughts? Anyone seen this behavior before?

Troubleshooting :: RE: where is .auth_secret in 10.8?

xsanguy — Sun, 12 May 2013 02:06:38 GMT

Author: xsanguy
Posted: Sat May 11, 2013 9:06 pm (GMT -5)

Also happily running SNFX

Curriously, I upgraded a 10.7 xsan system to 10.8 recently, by installing 2 new MDCs and demoting the 10.7 ones.

The .auth_secret file was deleted. HOWEVER - I found out that .auth_secret is actually an optional encryption system.

Ie, if it's not present on the MDCs, then you don't need it on the clients either...