Zyxel Auto Repair deleted all files | How can I recover them? | NSA325 v2

Options
Hilbert
Hilbert Posts: 2  Freshman Member
edited July 2019 in Personal Cloud Storage
We have a NSA325 v2

We used only 1 drive at the moment and it crashed. Maybe because it was full? The auto repair from Zyxel deleted the whole needed folder (95% of the storage) and "fixed" the issue but now all files are gone.

What can we do to recover them?

Report:

e2fsck 1.41.14 (22-Dec-2010)
/dev/md0: recovering journal
Error reading block 121668767 (Attempt to read block from filesystem resulted in short read). Ignore error? yes
Force rewrite? yes
Pass 1: Checking inodes, blocks, and sizes
Inode 12320770 i_size is 2240512 should be 2269184. Fix? yes
Inode 12320770 i_blocks is 4384 should be 4440. Fix? yes
Inode 60819169 i_size is 1336216 should be 1351680. Fix? yes
Inode 60819169 i_blocks is 2624 should be 2648. Fix? yes
Pass 2: Checking directory structure
Entry 'themakleding.kdbx' in /keepass (1572865) references inode 1572924 found in group 192's unused inodes area.
Fix? yes
Entry 'Copy #25762 of ~hjdekoning@themakleding.nu.pst.tmp' in /outlook/recycle/Archief (12320770) references inode 12346553 found in group 1507's unused inodes area.
Fix? yes
Entry 'Copy #25377 of ~hjdekoning@themakleding.nu.pst.tmp' in /outlook/recycle/Archief (12320770) has an incorrect filetype (was 1 should be 0).
Fix? yes
Entry 'Copy #25378 of ~hjdekoning@themakleding.nu.pst.tmp' in /outlook/recycle/Archief (12320770) has an incorrect filetype (was 1 should be 0).
Fix? yes
Entry 'Copy #25380 of ~hjdekoning@themakleding.nu.pst.tmp' in /outlook/recycle/Archief (12320770) has an incorrect filetype (was 1 should be 0).
Fix? yes
Entry 'Copy #25381 of ~hjdekoning@themakleding.nu.pst.tmp' in /outlook/recycle/Archief (12320770) has an incorrect filetype (was 1 should be 0).
Fix? yes
Entry 'Copy #25375 of ~hjdekoning@themakleding.nu.pst.tmp' in /outlook/recycle/Archief (12320770) has an incorrect filetype (was 1 should be 0).
Fix? yes
Entry 'Copy #25379 of ~hjdekoning@themakleding.nu.pst.tmp' in /outlook/recycle/Archief (12320770) has an incorrect filetype (was 1 should be 0).
Fix? yes
Entry 'Copy #25383 of ~hjdekoning@themakleding.nu.pst.tmp' in /outlook/recycle/Archief (12320770) has an incorrect filetype (was 1 should be 0).
Fix? yes
Entry 'Copy #25384 of ~hjdekoning@themakleding.nu.pst.tmp' in /outlook/recycle/Archief (12320770) has an incorrect filetype (was 1 should be 0).
Fix? yes
Entry 'Copy #25385 of ~hjdekoning@themakleding.nu.pst.tmp' in /outlook/recycle/Archief (12320770) has an incorrect filetype (was 1 should be 0).
Fix? yes
Entry 'Copy #25376 of ~hjdekoning@themakleding.nu.pst.tmp' in /outlook/recycle/Archief (12320770) has an incorrect filetype (was 1 should be 0).
Fix? yes
Entry 'Copy #25374 of ~hjdekoning@themakleding.nu.pst.tmp' in /outlook/recycle/Archief (12320770) has an incorrect filetype (was 1 should be 0).
Fix? yes
Entry 'Copy #25382 of ~hjdekoning@themakleding.nu.pst.tmp' in /outlook/recycle/Archief (12320770) has an incorrect filetype (was 1 should be 0).
Fix? yes
Restarting e2fsck from the beginning...
One or more block group descriptor checksums are invalid. Fix? yes
Group descriptor 192 checksum is invalid. FIXED.
Group descriptor 1507 checksum is invalid. FIXED.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Entry 'Copy #25377 of ~hjdekoning@themakleding.nu.pst.tmp' in /outlook/recycle/Archief (12320770) has deleted/unused inode 12346168. Clear? yes
Entry 'Copy #25378 of ~hjdekoning@themakleding.nu.pst.tmp' in /outlook/recycle/Archief (12320770) has deleted/unused inode 12346169. Clear? yes
Entry 'Copy #25380 of ~hjdekoning@themakleding.nu.pst.tmp' in /outlook/recycle/Archief (12320770) has deleted/unused inode 12346171. Clear? yes
Entry 'Copy #25381 of ~hjdekoning@themakleding.nu.pst.tmp' in /outlook/recycle/Archief (12320770) has deleted/unused inode 12346172. Clear? yes
Entry 'Copy #25375 of ~hjdekoning@themakleding.nu.pst.tmp' in /outlook/recycle/Archief (12320770) has deleted/unused inode 12346166. Clear? yes
Entry 'Copy #25379 of ~hjdekoning@themakleding.nu.pst.tmp' in /outlook/recycle/Archief (12320770) has deleted/unused inode 12346170. Clear? yes
Entry 'Copy #25383 of ~hjdekoning@themakleding.nu.pst.tmp' in /outlook/recycle/Archief (12320770) has deleted/unused inode 12346174. Clear? yes
Entry 'Copy #25384 of ~hjdekoning@themakleding.nu.pst.tmp' in /outlook/recycle/Archief (12320770) has deleted/unused inode 12346175. Clear? yes
Entry 'Copy #25385 of ~hjdekoning@themakleding.nu.pst.tmp' in /outlook/recycle/Archief (12320770) has deleted/unused inode 12346176. Clear? yes
Entry 'Copy #25376 of ~hjdekoning@themakleding.nu.pst.tmp' in /outlook/recycle/Archief (12320770) has deleted/unused inode 12346167. Clear? yes
Entry 'Copy #25374 of ~hjdekoning@themakleding.nu.pst.tmp' in /outlook/recycle/Archief (12320770) has deleted/unused inode 12346165. Clear? yes
Entry 'Copy #25382 of ~hjdekoning@themakleding.nu.pst.tmp' in /outlook/recycle/Archief (12320770) has deleted/unused inode 12346173. Clear? yes
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Unattached inode 12346178
Connect to /lost+found? yes
Inode 12346178 ref count is 2 should be 1. Fix? yes
Unattached inode 12346247
Connect to /lost+found? yes
Inode 12346247 ref count is 2 should be 1. Fix? yes
Unattached inode 12346271
Connect to /lost+found? yes
Inode 12346271 ref count is 2 should be 1. Fix? yes
Unattached inode 12346304
Connect to /lost+found? yes
Inode 12346304 ref count is 2 should be 1. Fix? yes
Unattached inode 12346324
Connect to /lost+found? yes
Inode 12346324 ref count is 2 should be 1. Fix? yes
Unattached inode 12346329
Connect to /lost+found? yes
Inode 12346329 ref count is 2 should be 1. Fix? yes
Unattached inode 12346350
Connect to /lost+found? yes
Inode 12346350 ref count is 2 should be 1. Fix? yes
Unattached inode 12346362
Connect to /lost+found? yes
Inode 12346362 ref count is 2 should be 1. Fix? yes
Unattached inode 12346385
Connect to /lost+found? yes
Inode 12346385 ref count is 2 should be 1. Fix? yes
Unattached inode 12346435
Connect to /lost+found? yes
Inode 12346435 ref count is 2 should be 1. Fix? yes
Unattached inode 12346512
Connect to /lost+found? yes
Inode 12346512 ref count is 2 should be 1. Fix? yes
Unattached inode 12346582
Connect to /lost+found? yes
Inode 12346582 ref count is 2 should be 1. Fix? yes
Pass 5: Checking group summary information
Block bitmap differences: -(601504--601520) +(4555712--4556622) +(4556640--4556799) -(243334167--243334170) +(243334684--243334828) +(243334838--243334841) +(243334848--243334850) +(243334853--243334861)
Fix? yes
Free blocks count wrong for group #18 (3393 counted=3410).
Fix? yes
Free blocks count wrong for group #139 (1408 counted=337).
Fix? yes
Free blocks count wrong for group #142 (2047 counted=152).
Fix? yes
Free blocks count wrong for group #146 (1990 counted=6).
Fix? yes
Free blocks count wrong for group #149 (2047 counted=51).
Fix? yes
Free blocks count wrong for group #152 (1987 counted=3).
Fix? yes
Free blocks count wrong for group #153 (9151 counted=4804).
Fix? yes
Free blocks count wrong for group #155 (2868 counted=2406).
Fix? yes
Free blocks count wrong for group #193 (1940 counted=1937).
Fix? yes
Free blocks count wrong for group #1504 (23990 counted=23983).
Fix? yes
Free blocks count wrong for group #7425 (26007 counted=25850).
Fix? yes
Free blocks count wrong for group #7427 (29901 counted=29898).
Fix? yes
Free blocks count wrong (209177914 counted=209164022).
Fix? yes
Inode bitmap differences: +(12346177--12346582)
Fix? yes
Free inodes count wrong for group #192 (8133 counted=8132).
Fix? yes
Free inodes count wrong for group #1507 (7372 counted=6966).
Fix? yes
Free inodes count wrong (60454956 counted=60454549).
Fix? yes
/dev/md0: ***** FILE SYSTEM WAS MODIFIED *****
/dev/md0: 567659/61022208 files (1.1% non-contiguous) 34897210/244061232 blocks
e2fsck -f -y return value:1




#NAS_Jul_2019

All Replies

  • Mijzelf
    Mijzelf Posts: 2,645  Guru Member
    First Anniversary 10 Comments Friend Collector First Answer
    Options
    That looks bad. I don't think there is an easy way to recover it. Depending on the nature of your data PhotoRec might be able to recover some (most?) files, but as it has to work without help of the filesystem, you will loose filenames and timestamps.
    On the positive side, as it works without help of the filesystem, you can run the tool on any OS it supports, and where you can connect the disk to.
    As the disks was almost full some fragmentation will be there, so the chances are poor that recent big files can be recovered. 

    BTW, I think it all started with a hardware problem:
    Error reading block 121668767 (Attempt to read block from filesystem resulted in short read).
    The system tried to read a block which should be on about the middle of the disk, and didn't get all bytes it needed. The only reason I can think of is a hardware error.


  • Hilbert
    Hilbert Posts: 2  Freshman Member
    Options
    Thank you very much Mijzelf! :)

    I have been busy with some reading, running the programs and understanding TestDisk. PhotoRec did get some files back but didn't have the time yet to check and investigate them as the files have all new names, all office files looks like turned into .txt? and there is a lot of garbage. So I will try TestDisk as they say it keeps the original names and should be faster. Let me know if you have suggestions for this.

    We did run into 2 other issues:
    1. Every time the power is turned off, the NAS loses: Networkname, IP settings and timezone
    2. Every time we login into the NAS we get this popup: "Error" "Hard Drive is full". The brand new 4 tb drives are nearly empty (3.58T free showing in Zyxel starter). The network drive we made; Z: is showing full in windows with a max size of 10 MB. I think we are putting the files on the memory of the NAS and not on the new drives. Do you know a solution?

    The drives: WD Red 4TB - 3.5" - SATA 6Gb/s 

    Let me know if you need additional info. 
    Thanks in advance!

    Hilbert
  • Mijzelf
    Mijzelf Posts: 2,645  Guru Member
    First Anniversary 10 Comments Friend Collector First Answer
    Options
    I have no opinion about TestDisk.

    About your other issues, can you login over the Telnet Backdoor, and post the output of
    <div>cat /proc/mounts <br></div><div>cat /etc/samba/smb.conf<br></div><div></div>


Consumer Product Help Center