« Back to all recent discussions

NAS540 data lost on harddisk after factory reset

Remco van KuilenburgRemco van Kuilenburg Posts: 4  Junior Member
edited January 31 in Questions
Hi Guys,

I hope you can help me. This is now the second time I have this problem. My NAS540 crashed last week and had to do a factory reset. After the reboot the system was telling me found new discs. Option was adopt it and after that I had to press okay to format the disk. I did not press this off course because all my data will be lost.

I had the same some years ago with the same disk and I lost my data, it is not lost but can not get to it. So not to run into the same problems I do not connect this disk.

Is there anybody who had the same and know a solution.

Cheers,

Remco


#NAS_Jan_2020
Tagged:

Answers

  • MijzelfMijzelf Posts: 1,073  Heroic Warrior Member
    Power surge?

    Anyway, you are not the only one who lost it's volume after an unclean shutdown. Read here.

    To find out how your damage is, you'll have to enable the ssh server, login over ssh, and post the output of

    cat /proc/partitions
    cat /proc/mdstat
    cat /proc/mounts
    su
    mdadm --examine /dev/sd[abcd]3


  • Remco van KuilenburgRemco van Kuilenburg Posts: 4  Junior Member
    edited January 31
    Hi,

    Thanks for your reply. For me it is like talking in a strange language to me. I'm not a skilled programmer and tried to do the SSH part and got errors.

    I'm using a Mac and tried with terminal

    MacBook-Pro:~ remcovankuilenburg$ ssh 192.168.1.14

    ssh: connect to host 192.168.1.14 port 22: Connection refused


  • MijzelfMijzelf Posts: 1,073  Heroic Warrior Member
    You have to enable the server first, in Control Panel->Terminal. Then connect with

  • Remco van KuilenburgRemco van Kuilenburg Posts: 4  Junior Member
    Aha that helps.

    I got the code here.

    ~ $ cat /proc/partitions

    major minor  #blocks  name


       7        0     147456 loop0

      31        0        256 mtdblock0

      31        1        512 mtdblock1

      31        2        256 mtdblock2

      31        3      10240 mtdblock3

      31        4      10240 mtdblock4

      31        5     112640 mtdblock5

      31        6      10240 mtdblock6

      31        7     112640 mtdblock7

      31        8       6144 mtdblock8

       8        0 3907018584 sda

       8        1    1998848 sda1

       8        2    1999872 sda2

       8        3 3903017984 sda3

      31        9     102424 mtdblock9

       9        0    1997760 md0

       9        1    1998784 md1

      31       10       4464 mtdblock10

       9        2 3902886720 md2



    ~ $ cat /proc/mdstat

    Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] 

    md2 : active raid1 sda3[0]

          3902886720 blocks super 1.2 [1/1] [U]

          

    md1 : active raid1 sda2[0]

          1998784 blocks super 1.2 [4/1] [U___]

          

    md0 : active raid1 sda1[5]

          1997760 blocks super 1.2 [4/1] [U___]

          

    unused devices: <none>


    ~ $ 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

    ubi7:ubi_rootfs2 /firmware/mnt/nand ubifs ro,relatime 0 0

    /dev/md0 /firmware/mnt/sysdisk ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0

    /dev/loop0 /ram_bin ext2 ro,relatime,user_xattr,barrier=1 0 0

    /dev/loop0 /usr ext2 ro,relatime,user_xattr,barrier=1 0 0

    /dev/loop0 /lib/security ext2 ro,relatime,user_xattr,barrier=1 0 0

    /dev/loop0 /lib/modules ext2 ro,relatime,user_xattr,barrier=1 0 0

    /dev/loop0 /lib/locale ext2 ro,relatime,user_xattr,barrier=1 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

    ubi3:ubi_config /etc/zyxel ubifs rw,relatime 0 0

    /dev/md2 /i-data/083cd5b1 ext4 rw,noatime,user_xattr,barrier=1,stripe=16,data=ordered,usrquota 0 0

    /dev/md2 /usr/local/apache/htdocs/desktop,/pkg ext4 rw,noatime,user_xattr,barrier=1,stripe=16,data=ordered,usrquota 0 0

    configfs /sys/kernel/config configfs rw,relatime 0 0



    ~ $ su

    Password: 



    BusyBox v1.19.4 (2019-09-04 14:33:19 CST) built-in shell (ash)

    Enter 'help' for a list of built-in commands.


    ~ # mdadm --examine /dev/sd[abcd]3

    /dev/sda3:

              Magic : a92b4efc

            Version : 1.2

        Feature Map : 0x0

         Array UUID : 083cd5b1:9a1d86e3:22031a75:be24d2be

               Name : NAS540:2  (local to host NAS540)

      Creation Time : Sun Jan 17 07:28:01 2016

         Raid Level : raid1

       Raid Devices : 1


     Avail Dev Size : 7805773824 (3722.08 GiB 3996.56 GB)

         Array Size : 3902886720 (3722.08 GiB 3996.56 GB)

      Used Dev Size : 7805773440 (3722.08 GiB 3996.56 GB)

        Data Offset : 262144 sectors

       Super Offset : 8 sectors

              State : clean

        Device UUID : febebea7:d85c686d:05081d38:1cc11c9f


        Update Time : Mon Feb 17 20:41:03 2020

           Checksum : 1d8ed1bc - correct

             Events : 14



       Device Role : Active device 0

       Array State : A ('A' == active, '.' == missing)

    mdadm: cannot open /dev/sdb3: No such device or address

    mdadm: cannot open /dev/sdc3: No such device or address

    mdadm: cannot open /dev/sdd3: No such device or address


  • MijzelfMijzelf Posts: 1,073  Heroic Warrior Member
    Do you have only one disk in that NAS? According to /proc/partitions there is only one disk, and that disk is fine. The raid array on the data partition is assembled and mounted.
  • Remco van KuilenburgRemco van Kuilenburg Posts: 4  Junior Member
    edited February 18
    Yes only one. I have got other ones out after the " crash" The "old" partition I can get in now and data is there. But there is also a second partition I can't enter. That was some years ago after a software upgrade of zyxel. In that partition are all pictures of my son etc. It is there but can not get in.
  • MijzelfMijzelf Posts: 1,073  Heroic Warrior Member
    On this disk there is no 2nd data partition.

    The disk is 4TB
       8        0 3907018584 sda
    The data partition is only slightly smaller
    8        3 3903017984 sda3
    And the raid array on that data partition fills the whole partition

    md2 : active raid1 sda3[0]      3902886720 blocks super 1.2 [1/1] [U]

    But there could be a non-active share. Have a look in your shares menu to see if that is the case.

Sign In or Register to comment.