TomasMalina  Freshman Member

Just to check, what firmware version was everyone on when it happened? My NAS542 was ABAG.13 when it got attacked.

I've joined the club, NAS542, June 10-12, ransom is also 0.019 BTC. Given the same issues were discussed a few years ago among QNAP and Synology users, the case doesn't look very promising - allegedly, unless we're lucky to be encrypted by an old version (prior to June 2019), they haven't found any mistakes in the…

Just wanted to thank you Mijzelf for this thread as my NAS542 got almost bricked today by a failed firmware update (no LAN connection, no beep after startup). Using the 'RescueStick' you provided and swapping the 542 firmware from ftp2.zyxel.com resurrected it. Dank u wel!

Thank you for all your precious help, I'm already waiting for a new drive, will exchange it as soon as it arrives.

Sorry for the long pause. I've let it run over the weekend and after reaching about 80-ish % on the resync (the highest I've seen it get so far) it crashed. This time, when I looked at it after reboot, it showed a degraded array, disk 2 was indeed dropped. In the webinterface it however allowed me to rebuild it on the same…

swapfile1 is added twice, once at 817.92, and once at 9130.36 I think I did that, yes, I'm almost positive I did remove it inbetween, I was just testing whether somehow the set priority might affect its usefulness (I turned it on with priority 0 instead of -1 for the second time). Why is it missing from the log, that I…

Oh, right, so, here is the log from last crash (till now). There are some "Bad eraseblock" entries, some "EXT4-fs (sda1): unable to read superblock" (but sda1 is in my case the connected USB stick with the swapfile). Then there is a md/raid:md2: not clean -- starting background reconstruction but that may have been fixed…

Ok, I'll keep an eye on it, thank you. That doesn't tell why the resyncing starts over and over again. Maybe the kernel log can be helpful, If you catch it shortly after it restarted. I've looked around, but I cannot find a kernel log on the NAS, I assume it first has to be generated somehow (/sbin/kernelcheck maybe..?)?…

Thank you very much for all your help. The e2fsck finally finished today after many repeated attempts (every run it corrected a few errors slowly reaching the end, not e2fsck terminates shortly after starting saying :clean). Likely, this was thanks to setting up the swap file. SMART, however, still reports there had been…

Thank youfor the info! Also, is there a way to safely stop the raid resync? Even when the NAS is mid-shutdown, it still tries to sync (and fails after several hrs/days when it reaches the faulty part of the second drive, crashing the NAS). Also, it eats up a lot of processing power that I believe could be used for the…

Unfortunately, no. If adding swap doesn't solve an out-of-memory error, then possibly it can't complete. Anyway, thank you for your help. Is the box 32-bit, or would adding a swap larger than 4GB help? I already tested that adding more 2/4GB swaps doesn't help, it can only use one when running e2fsck. Edit: Or.. would…

Hm, so even though there is a swapfile for the system to use, it only uses a small portion of it and e2fsck still gives a Memory allocation error. (I've tried multiple combinations of 2-12GB files either designated as swapfiles and/or linked in the e2fsck.conf file, none of which seems to have an efect on e2fsck crashes so…

I tried to do this, allocated a 12GB swap file on the exFAT USB stick, but got an error on the last command: I'm reformatting the USB stick to ext4 to see it that helps. Edit: Yes, ext4 is accepted by the swapon command, exFAT is not. Running the e2fsck command again, hopefully it will continue for more than 15 minutes.…

Thank you for being patient with me! I've started e2fsck on /dev/dm-2 that was listed among the errors in Tweaks and now it runs. Thank you so much for your help, will report back once it finishes. Edit: So, I managed to run it, ran it a few times with the -y flag so that I don't have to click yes to repairing every inode.…

Ah, I messed up, I did instert the 5 lines, but without the spacing before the sleep. Now I was able to make the NAS hang mid-shutdown with telnet daemon active, but nevertheless, I got errors that it cannot unmount logical drives in use: Now, when I try to run e2fsck, I still get a message that md2 is in use,…