Loading ...
Sorry, an error occurred while loading the content.

BSD disk image on Linux?

Expand Messages
  • David Kovar
    Good morning, I have what should be an image of a reconstructed RAID 1+0 array from a freebsd system. RAID Reconstructor blessed one particular configuration
    Message 1 of 1 , Nov 1, 2008
    • 0 Attachment
      Good morning,

      I have what should be an image of a reconstructed RAID 1+0 array from
      a freebsd system. RAID Reconstructor "blessed" one particular
      configuration and didn't like any of the other options. The blessed
      configuration matches the owners recollection of the configuration. If
      I run a carving tool over the image, I can find shell scripts,
      executables, etc. But, I'm unable to get anything to recognize any
      partitions in the image. I only have Linux, OS X, and Windows tools
      available at the moment, so perhaps I am missing something. Some
      research suggests that the stock Linux kernel will not recognize the
      FreeBSD 4.2BSD partitions. Is this correct? How best to get around
      this on a CentOS 5 system?

      Thanks....

      -David


      RAID configuration. from the owner:

      "RAID was originally configured as RAID 1+0 via a SATA firmware RAID
      controller (blech, I know) with 128K stripe).
      The controller is a SI 3114.

      However, in FreeBSD, this was detected as pseudo-raid RAID0+1 with
      64KB stripe.

      ar0 had 4 members, ad4, ad6, ad8 and ad10.
      From what I can tell, ad4 and ad6 were a mirror, and ad8 and ad10
      were a mirror, although this could have been ad4/ad8 and ad6/ad10.
      After the two drives were reported missing, the OS reported:

      ar0: 305255MB <FreeBSD PseudoRAID RAID0+1 (stripe 64 KB)> status:
      DEGRADED

      ar0: disk0 READY (master) using ad4 at ata2-master

      ar0: disk1 DOWN no device found for this subdisk

      ar0: disk2 DOWN no device found for this subdisk

      ar0: disk3 READY (mirror) using ad10 at ata5-master"

      I could rebuild the array using two different pairs of disks, so the
      +1 aspect seemed accurate.



      The map from a similar, though not identical system:

      8 partitions:
      # size offset fstype [fsize bsize bps/cpg]
      a: 2097152 16 4.2BSD 2048 16384 28528
      b: 4194304 2097168 swap
      c: 572315624 0 unused 0 0 # "raw"
      part, don't edit
      d: 8388608 6291472 4.2BSD 2048 16384 28528
      e: 33554432 14680080 4.2BSD 2048 16384 28528
      f: 33554432 48234512 4.2BSD 2048 16384 28528
      g: 490526680 81788944 4.2BSD 2048 16384 47872



      [Non-text portions of this message have been removed]
    Your message has been successfully submitted and would be delivered to recipients shortly.