« Back to all recent discussions

NAS 540 has lost all data.

ChaCha Posts: 16  Junior Member
edited January 4 in Questions
My NAS 540 has lost all data. : / Forum please help!

#NAS_Jan_2019
Tagged:
«1

Answers

  • ChaCha Posts: 16  Junior Member
    Mein NAS 540 hat alle Daten verloren. : / Bitte Forum hilf mir! : /
  • IjnrsiIjnrsi Posts: 254  Advanced Warrior Member
    Is your volume gone? Or HDD can be detected and volume still there, but you can't see the shared folder?
    You may describe more about your problem, if possible, that you can provide the sceenshot for your problem. 
  • JockeSveJockeSve Posts: 25  Junior Member
    If possible You could try to provide screenshots from "Storage Manager".
    As many as possible...
  • ChaCha Posts: 16  Junior Member
    Hier sehen Sie einige Screenshots von "Storage Manager". Ich habe sie in einer Word-Datei zusammengefügt.
  • ChaCha Posts: 16  Junior Member
    Here are some screenshots of "Storage Manager". I put them together in a Word file.


  • ChaCha Posts: 16  Junior Member
    I think the volumes are ok, but the RAID 5 array is destroyed. What do you think? Can you help me?
  • MijzelfMijzelf Posts: 622  Heroic Warrior Member
    Can you enable the ssh server, login over ssh, and post the results of
    cat /proc/mdstat
    su
    fdisk -l
    mdadm --examine /dev/sd[abcd]3

  • ChaCha Posts: 16  Junior Member
    ~ # cat /proc/mdstat
    Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
    md1 : active raid1 sdb2[1] sdd2[3] sdc2[2] sda2[4]
          1998784 blocks super 1.2 [4/4] [UUUU]

    md0 : active raid1 sda1[0] sdd1[3] sdc1[2] sdb1[1]
          1997760 blocks super 1.2 [4/4] [UUUU]

    unused devices: <none>
    ~ # su


    BusyBox v1.19.4 (2017-05-26 16:43:23 CST) built-in shell (ash)
    Enter 'help' for a list of built-in commands.

    ~ # fdisk -l

    Disk /dev/loop0: 153 MiB, 160432128 bytes, 313344 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk /dev/mtdblock0: 256 KiB, 262144 bytes, 512 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk /dev/mtdblock1: 512 KiB, 524288 bytes, 1024 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk /dev/mtdblock2: 256 KiB, 262144 bytes, 512 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk /dev/mtdblock3: 10 MiB, 10485760 bytes, 20480 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk /dev/mtdblock4: 10 MiB, 10485760 bytes, 20480 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk /dev/mtdblock5: 110 MiB, 115343360 bytes, 225280 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk /dev/mtdblock6: 10 MiB, 10485760 bytes, 20480 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk /dev/mtdblock7: 110 MiB, 115343360 bytes, 225280 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk /dev/mtdblock8: 6 MiB, 6291456 bytes, 12288 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk /dev/sda: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disklabel type: gpt
    Disk identifier: F153C90E-A2A3-4EE6-A08E-170D293952D6

    Device       Start        End    Sectors  Size Type
    /dev/sda1     2048    3999743    3997696  1.9G Linux RAID
    /dev/sda2  3999744    7999487    3999744  1.9G Linux RAID
    /dev/sda3  7999488 5860532223 5852532736  2.7T Linux RAID

    Disk /dev/sdb: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disklabel type: gpt
    Disk identifier: 06A9E941-0131-4C6D-947E-3FA1F4CA085B

    Device       Start        End    Sectors  Size Type
    /dev/sdb1     2048    3999743    3997696  1.9G Linux RAID
    /dev/sdb2  3999744    7999487    3999744  1.9G Linux RAID
    /dev/sdb3  7999488 5860532223 5852532736  2.7T Linux RAID

    Disk /dev/sdd: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disklabel type: gpt
    Disk identifier: DBE96E54-F999-4953-A2B2-B0E5E534C386

    Device       Start        End    Sectors  Size Type
    /dev/sdd1     2048    3999743    3997696  1.9G Linux RAID
    /dev/sdd2  3999744    7999487    3999744  1.9G Linux RAID
    /dev/sdd3  7999488 5860532223 5852532736  2.7T Linux RAID

    Disk /dev/sdc: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disklabel type: gpt
    Disk identifier: 9700C7E5-9A84-4A20-95CE-C10CD7731E88

    Device       Start        End    Sectors  Size Type
    /dev/sdc1     2048    3999743    3997696  1.9G Linux RAID
    /dev/sdc2  3999744    7999487    3999744  1.9G Linux RAID
    /dev/sdc3  7999488 5860532223 5852532736  2.7T Linux RAID

    Disk /dev/md0: 1.9 GiB, 2045706240 bytes, 3995520 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disk /dev/md1: 1.9 GiB, 2046754816 bytes, 3997568 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    ~ # mdadm --examine /dev/sd[abcd]3

  • ChaCha Posts: 16  Junior Member
    Hello !
    Unfortunately I can not interpret that. Maybe you can explain that to me. What is the next step? Thank you for your help.

  • MijzelfMijzelf Posts: 622  Heroic Warrior Member
    So far it tells that the raid manager has assembled the system- and swap volume. But it doesn't do anything with the data volume.
    The 4 disks all have 3 partitions, and a GPT.
    But the most interesting piece of information is lacking. Does
    mdadm --examine /dev/sd[abcd]3
    really give no output?


  • ChaCha Posts: 16  Junior Member
    Thanks for your detailed explanation. I entered the command. Here is the result:


    ~ $ mdadm --examine / dev / sd [abcd] 3
    mdadm: Can not open / dev / sda3: permission denied
    mdadm: Can not open / dev / sdb3: permission denied
    mdadm: Can not open / dev / sdc3: Permission Denied
    mdadm: Can not open / dev / sdd3: permission denied


    Can it be that it is related to the fact that the volumes are no longer set up in the Raid 5 array?

    -------------------------------------------------- ---------------------------------

    On closer inspection, I found that only the user admins are available. Everyone else is gone.
    The shared folders are still visible, but have the status: Lost (see pictures in the appendix).

    Maybe that helps to get a clearer picture of the whole thing.
    Greetings and thanks
  • ChaCha Posts: 16  Junior Member
    Is there a way to restore permissions to access all the System Admin folders? Probably before the data belongs to the folder restored?
  • MijzelfMijzelf Posts: 622  Heroic Warrior Member
    mdadm: Can not open / dev / sda3: permission denied

    Ah, sorry. after a new login a new 'su' is needed:

    su
    mdadm --examine /dev/sd[abcd]3
    On closer inspection, I found that only the user admins are available. Everyone else is gone. The shared folders are still visible, but have the status: Lost (see pictures in the appendix).


    The 'shares' are no more than pointers to a directory on the data volume. There is no data volume, so the shares point to nothing. The share database is stored outside the data volume, and so it's still there.
  • ChaCha Posts: 16  Junior Member
    ~ # mdadm --examine /dev/sd[abcd]3
    /dev/sda3:
              Magic : a92b4efc
            Version : 1.2
        Feature Map : 0x2
         Array UUID : 04004588:1416a156:bfa20978:5756d5aa
               Name : NAS540:2  (local to host NAS540)
      Creation Time : Sat Sep 19 19:20:34 2015
         Raid Level : raid5
       Raid Devices : 4

     Avail Dev Size : 5852270592 (2790.58 GiB 2996.36 GB)
         Array Size : 8778405312 (8371.74 GiB 8989.09 GB)
      Used Dev Size : 5852270208 (2790.58 GiB 2996.36 GB)
        Data Offset : 262144 sectors
       Super Offset : 8 sectors
    Recovery Offset : 0 sectors
              State : clean
        Device UUID : fabc850c:d92b27c4:ef5b37de:ffcafb50

        Update Time : Fri Dec 21 05:39:03 2018
           Checksum : 7de6aeb1 - correct
             Events : 24293

             Layout : left-symmetric
         Chunk Size : 64K

       Device Role : Active device 0
       Array State : AAAA ('A' == active, '.' == missing)
    /dev/sdb3:
              Magic : a92b4efc
            Version : 1.2
        Feature Map : 0x0
         Array UUID : 04004588:1416a156:bfa20978:5756d5aa
               Name : NAS540:2  (local to host NAS540)
      Creation Time : Sat Sep 19 19:20:34 2015
         Raid Level : raid5
       Raid Devices : 4

     Avail Dev Size : 5852270592 (2790.58 GiB 2996.36 GB)
         Array Size : 8778405888 (8371.74 GiB 8989.09 GB)
        Data Offset : 262144 sectors
       Super Offset : 8 sectors
              State : clean
        Device UUID : 7adf8778:894abce0:2146d412:c64e1c7f

        Update Time : Fri Dec 21 05:48:28 2018
           Checksum : 693c6190 - correct
             Events : 24301

             Layout : left-symmetric
         Chunk Size : 64K

       Device Role : Active device 1
       Array State : .AAA ('A' == active, '.' == missing)
    /dev/sdc3:
              Magic : a92b4efc
            Version : 1.2
        Feature Map : 0x0
         Array UUID : 04004588:1416a156:bfa20978:5756d5aa
               Name : NAS540:2  (local to host NAS540)
      Creation Time : Sat Sep 19 19:20:34 2015
         Raid Level : raid5
       Raid Devices : 4

     Avail Dev Size : 5852270592 (2790.58 GiB 2996.36 GB)
         Array Size : 8778405888 (8371.74 GiB 8989.09 GB)
        Data Offset : 262144 sectors
       Super Offset : 8 sectors
              State : clean
        Device UUID : 1f1b9e0e:9a037d12:13ff3598:3e948926

        Update Time : Fri Dec 21 05:48:28 2018
           Checksum : 5de254b0 - correct
             Events : 24301

             Layout : left-symmetric
         Chunk Size : 64K

       Device Role : Active device 2
       Array State : .AAA ('A' == active, '.' == missing)
    /dev/sdd3:
              Magic : a92b4efc
            Version : 1.2
        Feature Map : 0x0
         Array UUID : 04004588:1416a156:bfa20978:5756d5aa
               Name : NAS540:2  (local to host NAS540)
      Creation Time : Sat Sep 19 19:20:34 2015
         Raid Level : raid5
       Raid Devices : 4

     Avail Dev Size : 5852270592 (2790.58 GiB 2996.36 GB)
         Array Size : 8778405888 (8371.74 GiB 8989.09 GB)
        Data Offset : 262144 sectors
       Super Offset : 8 sectors
              State : clean
        Device UUID : 8728209d:b362321a:0fbc6cd2:e3926f5d

        Update Time : Fri Dec 21 05:48:28 2018
           Checksum : 65367cd4 - correct
             Events : 24301

             Layout : left-symmetric
         Chunk Size : 64K

       Device Role : Active device 3
       Array State : .AAA ('A' == active, '.' == missing)

  • ChaCha Posts: 16  Junior Member
    Sorry, that with the "su", could have thought me too!
Sign In or Register to comment.