NAS 540 has lost all data.

Options
Cha
Cha Posts: 16  Freshman Member
edited January 2019 in Personal Cloud Storage
My NAS 540 has lost all data. : / Forum please help!

#NAS_Jan_2019
«13

All Replies

  • Cha
    Cha Posts: 16  Freshman Member
    Options
    Mein NAS 540 hat alle Daten verloren. : / Bitte Forum hilf mir! : /
  • Ijnrsi
    Ijnrsi Posts: 254  Master Member
    Options
    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. 
  • JockeSve
    JockeSve Posts: 80  Ally Member
    First Anniversary 10 Comments Friend Collector First Answer
    Options
    If possible You could try to provide screenshots from "Storage Manager".
    As many as possible...
  • Cha
    Cha Posts: 16  Freshman Member
    Options
    Hier sehen Sie einige Screenshots von "Storage Manager". Ich habe sie in einer Word-Datei zusammengefügt.
  • Cha
    Cha Posts: 16  Freshman Member
    Options
    Here are some screenshots of "Storage Manager". I put them together in a Word file.


  • Cha
    Cha Posts: 16  Freshman Member
    Options
    I think the volumes are ok, but the RAID 5 array is destroyed. What do you think? Can you help me?
  • Mijzelf
    Mijzelf Posts: 2,638  Guru Member
    First Anniversary 10 Comments Friend Collector First Answer
    Options
    Can you enable the ssh server, login over ssh, and post the results of
    <div>cat /proc/mdstat</div><div><br></div><div>su</div><div><br></div><div>fdisk -l</div><div><br></div><div>mdadm --examine /dev/sd[abcd]3</div>

  • Cha
    Cha Posts: 16  Freshman Member
    Options
    ~ # 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

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

  • Mijzelf
    Mijzelf Posts: 2,638  Guru Member
    First Anniversary 10 Comments Friend Collector First Answer
    Options
    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
    <div><div>mdadm --examine /dev/sd[abcd]3</div></div><div></div>
    really give no output?


Consumer Product Help Center