New Raid subsystem freezes when two computers write to it

huntson's picture

So I bought a new raid system from Enhance-tech (an RS16FS). I wanted to replace a bunch of my old Xserve raids. It appears fine in Xsan admin and I create a volume out of it. When one computer at a time writes to it, it is fine but when two computers write to it simultaneously the transfer process on both freezes. Unless I reboot the controller on the raid system it won't show up in disk utility or on the desktop after a reboot.

Logs from the MDC:

3/27/12 12:15:02.324 AM postfix/local: 1AF2A304EC7: to=, orig_to=, relay=local, delay=0.81, delays=0.67/0.11/0/0.03, dsn=2.0.0, status=sent (delivered to file: /dev/null)
3/27/12 12:15:02.325 AM postfix/qmgr: 1AF2A304EC7: removed
3/27/12 12:16:01.326 AM postfix/master: master exit time has arrived
3/27/12 12:17:12.324 AM ScreensharingAgent: [CL_INVALID_DEVICE] : OpenCL Error : Failed to create context! Invalid device
3/27/12 12:17:12.587 AM screensharingd: Authentication: SUCCEEDED :: User Name: ianliuzzi-fedun :: Viewer Address: 192.168.1.130 :: Type: DH
3/27/12 12:17:19.042 AM Xsan Admin: ERROR: No session for computer xserve (00000000-0000-1000-8000-0019E3E85206)
3/27/12 12:17:19.043 AM Xsan Admin: ERROR: No session for computer xserve (00000000-0000-1000-8000-0019E3E85206)
3/27/12 12:17:19.101 AM Xsan Admin: ERROR: No session for computer xserve (00000000-0000-1000-8000-0019E3E85206)
3/27/12 12:17:19.102 AM Xsan Admin: ERROR: No session for computer xserve (00000000-0000-1000-8000-0019E3E85206)
3/27/12 12:17:19.103 AM Xsan Admin: ERROR: No session for computer xserve (00000000-0000-1000-8000-0019E3E85206)
3/27/12 12:17:19.104 AM Xsan Admin: ERROR: No session for computer xserve (00000000-0000-1000-8000-0019E3E85206)
3/27/12 12:17:19.105 AM Xsan Admin: ERROR: No session for computer xserve (00000000-0000-1000-8000-0019E3E85206)
3/27/12 12:17:19.105 AM Xsan Admin: ERROR: No session for computer xserve (00000000-0000-1000-8000-0019E3E85206)
3/27/12 12:17:19.108 AM Xsan Admin: ERROR: No session for computer xserve (00000000-0000-1000-8000-0019E3E85206)
3/27/12 12:17:19.864 AM Xsan Admin: ERROR: Error getting list of volumes: kOfflineError (0)
3/27/12 12:17:19.865 AM Xsan Admin: ERROR: Error reading volume statistics for shared_video: kOfflineError (0)
3/27/12 12:17:19.865 AM Xsan Admin: ERROR: Error reading volume statistics for xsansone: kOfflineError (0)
3/27/12 12:17:19.865 AM Xsan Admin: ERROR: Error reading volume statistics for xsan: kOfflineError (0)
3/27/12 12:17:19.866 AM Xsan Admin: ERROR: Error reading volume statistics for fcpproj: kOfflineError (0)
3/27/12 12:17:19.866 AM Xsan Admin: ERROR: Error reading san information: kOfflineError (0)
3/27/12 12:17:19.936 AM Xsan Admin: ERROR: No session for computer xserve (00000000-0000-1000-8000-0019E3E85206)
3/27/12 12:17:19.938 AM Xsan Admin: ERROR: No session for computer xserve (00000000-0000-1000-8000-0019E3E85206)
3/27/12 12:17:19.938 AM Xsan Admin: ERROR: No session for computer xserve (00000000-0000-1000-8000-0019E3E85206)
3/27/12 12:17:19.938 AM Xsan Admin: ERROR: No session for computer xserve (00000000-0000-1000-8000-0019E3E85206)
3/27/12 12:17:19.938 AM Xsan Admin: ERROR: No session for computer xserve (00000000-0000-1000-8000-0019E3E85206)
3/27/12 12:17:19.939 AM Xsan Admin: ERROR: No session for computer xserve (00000000-0000-1000-8000-0019E3E85206)
3/27/12 12:17:19.971 AM Xsan Admin: ERROR: Error reading san information: kOfflineError (0)
3/27/12 12:17:20.005 AM Xsan Admin: ERROR: Error getting list of volumes: kOfflineError (0)
3/27/12 12:17:20.005 AM Xsan Admin: ERROR: Error reading volume statistics for xsansone: kOfflineError (0)
3/27/12 12:17:20.005 AM Xsan Admin: ERROR: Error reading volume statistics for shared_video: kOfflineError (0)
3/27/12 12:17:20.006 AM Xsan Admin: ERROR: Error reading volume statistics for fcpproj: kOfflineError (0)
3/27/12 12:17:20.006 AM Xsan Admin: ERROR: Error reading volume statistics for xsan: kOfflineError (0)
3/27/12 12:17:20.925 AM librariand: changing log level to 5
3/27/12 12:17:22.073 AM librariand: no ubiquity account configured, not creating collection
3/27/12 12:17:22.074 AM librariand: error in handle_client_request: LibrarianErrorDomain/10/Unable to configure the collection.
3/27/12 12:17:24.216 AM Xsan Admin: ERROR: No session for computer xserve (00000000-0000-1000-8000-0019E3E85206)
3/27/12 12:17:24.218 AM Xsan Admin: ERROR: No session for computer xserve (00000000-0000-1000-8000-0019E3E85206)
3/27/12 12:17:24.218 AM Xsan Admin: ERROR: No session for computer xserve (00000000-0000-1000-8000-0019E3E85206)
3/27/12 12:17:24.218 AM Xsan Admin: ERROR: No session for computer xserve (00000000-0000-1000-8000-0019E3E85206)
3/27/12 12:17:24.218 AM Xsan Admin: ERROR: No session for computer xserve (00000000-0000-1000-8000-0019E3E85206)
3/27/12 12:17:24.219 AM Xsan Admin: ERROR: No session for computer xserve (00000000-0000-1000-8000-0019E3E85206)
3/27/12 12:17:24.220 AM Xsan Admin: ERROR: No session for computer xserve (00000000-0000-1000-8000-0019E3E85206)
3/27/12 12:17:24.225 AM Xsan Admin: ERROR: No session for computer xserve (00000000-0000-1000-8000-0019E3E85206)
3/27/12 12:17:24.225 AM Xsan Admin: ERROR: No session for computer xserve (00000000-0000-1000-8000-0019E3E85206)
3/27/12 12:17:24.231 AM Xsan Admin: ERROR: Error reading san information: kOfflineError (0)
3/27/12 12:17:24.232 AM Xsan Admin: ERROR: Error reading volume statistics for xsan: kOfflineError (0)
3/27/12 12:17:24.232 AM Xsan Admin: ERROR: Error reading volume statistics for xsansone: kOfflineError (0)
3/27/12 12:17:24.232 AM Xsan Admin: ERROR: Error reading volume statistics for fcpproj: kOfflineError (0)
3/27/12 12:17:24.233 AM Xsan Admin: ERROR: Error reading volume statistics for shared_video: kOfflineError (0)
3/27/12 12:17:24.233 AM Xsan Admin: ERROR: Error getting list of volumes: kOfflineError (0)
3/27/12 12:17:24.233 AM Xsan Admin: ERROR: Error reading lun information: kOfflineError (0)
3/27/12 12:17:25.000 AM kernel: 9.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/27/12 12:17:25.000 AM kernel: /SourceCache/xnu/xnu-1699.24.8/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}

bs3375's picture

Sounds more like a hardware setup issue than software.

1.What fc switch are you using? Did you configure the ports the RAID is connected to as targets?
2.Is the RAID dual controller? Did you supply the hard drives or did the vendor? Did they also supply MUX adapters? MUX adapters would be required for a dual controller active/active RAID with SATA drives.
3. Does the RAID use LUN level or device level mapping?
4. Does the RAID support advanced features like ALUA?
5. Have you contacted the storage vendor for advice?

JSamuel's picture

I'm all too familiar with the RS16FS..
Which territory are you in?

3. Does the RAID use LUN level or device level mapping?

LUN level.

4. Does the RAID support advanced features like ALUA?

No.

5. Have you contacted the storage vendor for advice?

Do this...

Joel Samuel.
/thirtytwo - Apple Consultancy & Direction
Proud sponsor of Xsanity.com

All contributions are my own personal opinions - not those of any entity I represent.

bs3375's picture

JSamuel wrote:
I'm all too familiar with the RS16FS..
/quote

Sounds ominous… since OS X requires device level mapping, can he change the SCSI ID on the RAID controller channels and alternate his LUN mappings so that it acts kind of like the Xserve RAID used to?

huntson's picture

All the cables and switches are good as this whole setup works with my old Xserve Raid. I can change the LUN but I see nothing about the SCSI ID. If I can change it - what do you suggest I change it to? I am planning on contacting the vendor but it sounds like you folks know a bit more than you are letting on.

mw10dot1's picture

Hi huntson

If it the same device i have come across before. The pics certainly look the same. I would return it if you can.

It is not worth the time and effort to make it work. And even if it looks ok latter down the road you could end up with files magically linking to the wrong bits of video.

Michael

JSamuel's picture

bs3375 wrote:
Sounds ominous… since OS X requires device level mapping, can he change the SCSI ID on the RAID controller channels and alternate his LUN mappings so that it acts kind of like the Xserve RAID used to?/quote

I wouldn't even go this far to try and tweak… It's far easier to trash the config and set it up from scratch properly.

huntson wrote:
I am planning on contacting the vendor but it sounds like you folks know a bit more than you are letting on./quote

Unfortunately...

mw10dot1 wrote:
If it the same device i have come across before. The pics certainly look the same. I would return it if you can.

It is not worth the time and effort to make it work. And even if it looks ok latter down the road you could end up with files magically linking to the wrong bits of video./quote

+1

Don't expect predictable sustained performance (let alone behaviour) from this box… I would hope the firmware/hardware has improved since I was burdened with a client having one.

Happy to take a look at it for you, but in reality it's a lost cause if this is meant to be primary creative storage unless they have refreshed the unit in the last 2 years.

Joel Samuel.
/thirtytwo - Apple Consultancy & Direction
Proud sponsor of Xsanity.com

All contributions are my own personal opinions - not those of any entity I represent.

bs3375's picture

huntson wrote:
I am planning on contacting the vendor but it sounds like you folks know a bit more than you are letting on./quote

I can honestly say I know nothing about this particular box. In fact I had to do a google search just to find some info about it. I do know a thing or two about other RAIDs and I know that not all RAIDs support Mac very well.

Are you stuck with the box? It sounds like everyone's opinion would be to return it if possible. My guess is you can make it work but you'll have to work at it — pun intended.

huntson's picture

The unit works with Mac very well - just not Xsan.

JSamuel's picture

huntson wrote:
The unit works with Mac very well - just not Xsan./quote

Barely... See what happens when it's fragmented to high hell or quite full... Or when you just need it to provide stable streams of usable data for FCP purposes, and it doesn't :shock:

Joel Samuel.
/thirtytwo - Apple Consultancy & Direction
Proud sponsor of Xsanity.com

All contributions are my own personal opinions - not those of any entity I represent.