NSA325v2 RAID 1 recovery

13»

All Replies

  • Mr_C
    Mr_C Posts: 14  Freshman Member
    With just one disk, OB, results as follows:

    ~ # cat /proc/mdstat
    Personalities : [linear] [raid0] [raid1]
    md0 : inactive sda2[2](S)
          1952996928 blocks super 1.2

    ~ # cat /proc/mounts
    rootfs / rootfs rw 0 0
    /proc /proc proc rw,relatime 0 0
    /sys /sys sysfs rw,relatime 0 0
    none /proc/bus/usb usbfs rw,relatime 0 0
    devpts /dev/pts devpts rw,relatime,mode=600 0 0
    /dev/mtdblock8 /zyxel/mnt/nand yaffs2 ro,relatime 0 0
    /dev/sda1 /zyxel/mnt/sysdisk ext2 ro,relatime,errors=continue 0 0
    /dev/loop0 /ram_bin ext2 ro,relatime,errors=continue 0 0
    /dev/loop0 /usr ext2 ro,relatime,errors=continue 0 0
    /dev/loop0 /lib/security ext2 ro,relatime,errors=continue 0 0
    /dev/loop0 /lib/modules ext2 ro,relatime,errors=continue 0 0
    /dev/ram0 /tmp/tmpfs tmpfs rw,relatime,size=5120k 0 0
    /dev/ram0 /usr/local/etc tmpfs rw,relatime,size=5120k 0 0
    /dev/ram0 /usr/local/var tmpfs rw,relatime,size=5120k 0 0
    /dev/mtdblock4 /etc/zyxel yaffs2 rw,relatime 0 0
    /dev/mtdblock4 /usr/local/apache/web_framework/data/config yaffs2 rw,relatime 0
    ~ # killall mdadm
    ~ # killall mdadm
    killall: mdadm: no process killed
    ~ # lsof | grep /dev/md0
    ~ # lsof | grep /dev/md0
    ~ # mdadm --stop /dev/md0
    mdadm: stopped /dev/md0
    ~ # mdadm --create --assume-clean --level=1 --raid-devices=2 --metadata=1.2 /dev
    /md0/mdaissing /dev/sda2
    mdadm: You haven't given enough devices (real or missing) to create this array


    So, the $64m question, what's next?  Do I put the new disk "N" in with OB and try again?
  • Mijzelf
    Mijzelf Posts: 2,598  Guru Member
    First Anniversary 10 Comments Friend Collector First Answer
    what's next?
    There's a typo in your 'mdadm --create' command
  • Mr_C
    Mr_C Posts: 14  Freshman Member
    D'oh.  Well that's embarrassing.  However, thanks to you, I now have a working volume!  What's more, I've switched back in the replacement disk and it's recovering.

    I do have a whole directory which isn't showing up however, despite the capacity of the volume suggesting it's there though... any more suggestions you clever person you?

    Can't thank you enough for all of your help so far Mijzelf.
  • Mr_C
    Mr_C Posts: 14  Freshman Member
    Hold that thought, now drive OB is showing as faulty and the RAID has gone from repairing to degraded.  AAAAAAAAAARGHHHHHHHHHHH!!!!!!!!  Two knackered disks?  Jeez.
  • Mijzelf
    Mijzelf Posts: 2,598  Guru Member
    First Anniversary 10 Comments Friend Collector First Answer
    That was to be expected, somehow. Disk OB was kicked from the array originally. Apparently not without reason. Yet there are still possibilities.

    When you have a Linux box, you can use dd_rescue to copy the content of sdOA2 or sdOB2 to sdN2. dd_rescue does a binary copy, and just skips the sectors it can't read. That can cause dataloss in some files, but it's also possible the unreadable sectors do not even contain filesystem data.

  • Mr_C
    Mr_C Posts: 14  Freshman Member
    Sorry for the silence - I've been spending the last few days trying to get off what I can (just not my iTunes library annoyingly).  I think it's time to write it off, especially as I can't seem to get dd_rescue to install.  
  • Sbradee
    Sbradee Posts: 1
    Mijzelf,
    Stumbled upon this RAID 1 'problem solve' only to find that at the end of the story your valiant efforts were 'written off' when an annoying iTunes library was lost and a dd_rescue install failed.
    Keep solving those variable hardware failure problems. Thanks for great insight on RAID recovery. 

Consumer Product Help Center