0 Replies Latest reply on Nov 20, 2009 6:53 AM by bcann

    Raid 5 - Hot expanded 3 drive to 5 drive and converted to dynamic disk, now array broken

    bcann

      Gday ALL,

      I just hot expanded my Raid 5 array, and all went great. i upgraded from a 3 disk Raid 5 system to a 5 Dsk Raid 5 system.

      I then wanted to expand the partition size, so i converted to a dynamic disk, and thought i'd restart the server, before doing an expansion. well i was wrong there as when i brought the server back up the boot drive (seperate to the raid 5 array) booted, but the raid 5 dynamic disk is showing as unreadable.

      So i ran dmview /v and it shows the partition table on the raid 5 drive as having 0 cylinders and most of the rest of the info is zero.

      Can anyone suggest an easier way then restoring 2TB of backup files to recover the data, prefeably through fixing the partition table? ANy suggestions would be greatly appreciated.

      Thanks

      Here is the output of DMview /V

      ---------- Partition Table Info Disk 1 ----------


      0 Cylinders
      1 Tracks/Cylinder
      1 Sectors/Track
      512 Bytes/Sector
      12 MediaType
      0 Sectors (total)
      0 Bytes (total)
      0 KB
      0 MB
      0.0 GB

      0 StartingOffset
      0 PartitionLength
      0 HiddenSectors
      0 PartitionNumber
      0 PartitionType
      0 BootIndicator
      0 RecognizedPartition
      0 RewritePartition
      IOCTL_DISK_GET_DRIVE_LAYOUT_EX failed (error 21)

      0 Bytes (       0 sectors) Geometric size
      0 Bytes (       0 sectors) True size (measured)
      0 Bytes (       0 sectors) Reported size (Partition0)
      0 Bytes (       0 sectors) missing/wasted

      ---------- DMIO Kernel List ----------

      Basic-info: version=21 maxspecio=512 maxio=512 maxkio=2048
      Ktrans-state: dg=0.0 pendtid=0.0 state=UNKNOWN
      #
      # Kmem-regions:
      #
      #
      # Disks: (cnt: 0)
      #
      #
      # Devices: (cnt: 0)
      #
      #
      # Groups: (cnt: 1)
      #
      Group NULLDG: iid=0.0 id=
      diskset=00000000-0000-0000-0000-000000000000
      configtid=0.0 logsize=0
      kflag=()
      vflag=(created|notempdb|noautoreimport|secondary)
      # Group-Objects: (cnt: 0)
      # End-group: NULLDG

      ---------- LDM Disk Header Harddisk0 ----------

      ERROR: scan operation failed:
      A format error was found in the private region of the disk

      ---------- LDM Disk Header Harddisk1 ----------

      ERROR: Cannot get disk layout:
      The device is not ready.

      ---------- LDM Disk Config Harddisk0 ----------

      ERROR: scan operation failed:
      A format error was found in the private region of the disk

      ---------- LDM Disk Config Harddisk1 ----------

      ERROR: Cannot get disk layout:
      The device is not ready.

      ---------- LDM Disk KLOG Harddisk0 ----------

      ERROR: scan operation failed:
      A format error was found in the private region of the disk

      ---------- LDM Disk KLOG Harddisk1 ----------

      ERROR: Cannot get disk layout:
      The device is not ready.

      ---------- DMAdmin Simple Query ----------

      dmdiag: ERROR: No disk groups loaded

      ---------- DMAdmin Verbose Query ----------

      dmdiag: ERROR: No disk groups loaded