Restore RAID1 with an old disk (I've been hacked) - NAS320

2»

Comments

  • garry
    garry Posts: 9  Freshman Member
    Strange. Does this disk needs more power than the encrypted disks do?
    No, I don't think. One of the encrypted disk is exactly the same as this one. Before the wrong repair process, the disk was seen through the Zyxel interface.
    So now:
    root@ubuntu:/home/ubuntu# mdadm --examine /dev/sdc2<br>/dev/sdc2:<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Magic : a92b4efc<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Version : 0.90.00<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; UUID : 346361d3:cbfe4cbd:f4fc2a5c:e6a2d6d5<br>&nbsp; Creation Time : Tue Oct 23 14:16:55 2012<br>&nbsp;&nbsp;&nbsp;&nbsp; Raid Level : raid1<br>&nbsp; Used Dev Size : 1952997888 (1862.52 GiB 1999.87 GB)<br>&nbsp;&nbsp;&nbsp;&nbsp; Array Size : 1952997888 (1862.52 GiB 1999.87 GB)<br>&nbsp;&nbsp; Raid Devices : 2<br>&nbsp; Total Devices : 2<br>Preferred Minor : 0<br><br>&nbsp;&nbsp;&nbsp; Update Time : Tue Dec 18 15:51:00 2018<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; State : clean<br>&nbsp;Active Devices : 1<br>Working Devices : 2<br>&nbsp;Failed Devices : 1<br>&nbsp; Spare Devices : 1<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Checksum : a665828a - correct<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Events : 1618289<br><br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Number&nbsp;&nbsp; Major&nbsp;&nbsp; Minor&nbsp;&nbsp; RaidDevice State<br>this&nbsp;&nbsp;&nbsp;&nbsp; 2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 8&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; spare&nbsp;&nbsp; /dev/sda2<br><br>&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 8&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 18&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; active sync<br>&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; faulty removed<br>&nbsp;&nbsp; 2&nbsp;&nbsp;&nbsp;&nbsp; 2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 8&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; spare&nbsp;&nbsp; /dev/sda2
    As requested, I tried:
    root@ubuntu:/home/ubuntu# modprobe raid1<br>root@ubuntu:/home/ubuntu# cat /proc/mdstat<br>Personalities : [raid1] <br>md0 : inactive sdc2[2](S)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1952997888 blocks<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>unused devices: <none>
    In my point of view, it's not absolutely necessary to remount the raid. Do you think just mounting the HD only is possible? I can then backup the important things.

    Thanks!




  • Mijzelf
    Mijzelf Posts: 2,858  Guru Member
    250 Answers 2500 Comments Friend Collector Seventh Anniversary
    Do you think just mounting the HD only is possible?

    Fortunately that should be quite easy. According to your header listing the array uses a version 0.9 superblock. That is at the end of the partition, so the physical start of the filesystem is also the physical start of the partition. In other words, the partition can simply be mounted.

    According to this bootlog an NSA320 uses (or at least used to use) ext3 as filesystem.

    So to mount it:

    <p>mkdir /tmp/mountpoint</p><p><br></p><p>mount -t ext3 /dev/sdc2 /tmp/mountpoint<br></p><p></p>



  • garry
    garry Posts: 9  Freshman Member
    I tried but got the same result as explained here:

    Should I try the:
    </code><code>mdadm --assemble --run /dev/md0 /dev/sdc1
    trick ?

    More info about the disk


  • Mijzelf
    Mijzelf Posts: 2,858  Guru Member
    250 Answers 2500 Comments Friend Collector Seventh Anniversary
    [quote]
    Should I try the:
    </code><code>mdadm --assemble --run /dev/md0 /dev/sdc1
    trick ?
    [/quote]
    It won't hurt, although in your case it's
    mdadm --assemble --run /dev/md0 /dev/sdc2
    Another suggestion in that forum which is worth trying is
    [quote]
    If anyone still gets the mdadm: /dev/sdb1 is busy - skipping message you can stop the device on with mdadm --stop /dev/mdx or check the /proc/mdstat to check if the device was automatically mount by your system.
    [/quote]

  • garry
    garry Posts: 9  Freshman Member
    Great, I could finally mount it!
    Thank you very much Mijzelf  ;)

Consumer Product Help Center