raid going off line

Discussion in 'Mac Basics and Help' started by BabaG, Jun 29, 2007.

  1. BabaG macrumors member

    Joined:
    Jan 5, 2007
    #1
    i've been trying to render out a series of stills as a qt from final cut
    and the raid, software raid set up through the disk utility, keeps
    failing in the process. the drive icon disappears from the desktop
    as well.

    when i look at the drives in the utility, they are there but not as an
    array, just as the individual drives. i know this is vague but i'm at
    something of a loss over this.

    can someone point me toward some methodologies as to how to
    get this fixed? or is this a known thing in certain software raid
    configs?

    the raid is a norco 1220 with 5 sata drives. the drives are all
    wd 500gb. the box has two raid channels and two individual
    channels. this only works with the proprietary card though which
    doesn't work with 10.4.8, which this is. because of that i have
    an e4p sonnet card providing 4 sata ports. the box is set up as
    jbod. two drives are in its channel 1 bays and striped via the
    disk utility. two drives are in the channel 2 bays, also striped.
    there is one solo drive in one of the individual channels.

    thanks for any tips or info on this issue,
    BabaG
     
  2. BabaG thread starter macrumors member

    Joined:
    Jan 5, 2007
    #2
    seems to have been corrupted files. a few of the files in the
    image sequence were corrupt and each time final cut would
    encounter them, the raid would freeze and crash.

    was able to isolate the individual files by manually doing a
    sort of recursive file copy, copying groups of files from one
    drive to another. when the copy process would hit one of
    the bad files it would put up an error with the file name
    when it crashed.

    i did this repeatedly throughout the files of the image
    sequence until i'd found all the files that would copy and
    which ones wouldn't. i then replaced the bad files with
    good ones and all is working.

    does anyone know of a better way to testing for the bad
    files? this method, while functional, is very time consuming.

    thanks,
    BabaG
     

Share This Page