poloschka

Understood. By restore I meant make it accessible. I moved them as you suggested and now I can browse them from my PC. Indeed and most of them a centered around finding the home directory... Well, here comes the hard part, to review the files and move them back where they were. Thank you again Mijzelf!

I have 95113 items in lost+found. There are files and directories. How can I restore them? Guides online mention the "file" command but that is missing from the NAS.

Thank you for the guide Mijzelf! Now the Filesystem errors are gone, the file browser does not give HTTP 500 error and the media server is also working fine. Unfortunately there was data loss. Is there a way to tell which files have been lost? 

Thanks for the advice, fortunately to my surprise, resync has completed without rebooting. I rebooted the NAS myself to check if the resync is whether permanent or not and the volume is not resyncing now. I am not sure what had happened. The resync was running from 2023-01-10 22:56:49 to 2023-01-11 21:19:21 and I caught…

As I was writing my previous post, the NAS restarted and the resync was nowhere near completion. Attached the log of this. Although it contains nothing more than the logs before. Only filesystem errors. Needless to say resync has started again from 0%.

Since the resync is restarted, I started to collect the logs again with putty configured properly. I might catch something this time. Yes, aside from dmesg output, I added /proc/mdstat to the output logfile as well. That showed me this: <div>Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5]…

Well the crontab solution didn't work as well, so I wrote a script to catch the logs. These logs repeat right before the NAS would restart after resync completes: [83984.552585] EXT4-fs error (device md2): htree_dirblock_to_tree:587: inode #11864587: block 94900400: comm smbd: bad ent ry in directory: rec_len is smaller…

Disabled Twonky, much less log is generated now. Unfortunately tail -f gave me the below error: <div>~ # tail -f /dev/kmsg</div><div>tail: read error: Invalid argument</div><div>tail: read error: Invalid argument</div><div>tail: read error: Invalid argument</div> Do I need some additional switch to make the command usable?…

Here is the output of that command: ~ # cat /proc/partitions major minor #blocks name 7 0 146432 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 1953514584 sda 8 1 1998848 sda1 8…

Hi Mijzelf, the output of cat /proc/mdstat should be normal I guess, since the array is resyncing. ~ # cat /proc/mdstat Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] md2 : active raid5 sda3[0] sdd3[4] sdc3[2] sdb3[1] 5848151040 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/4] [UUUU]…

I fiddled with it again. Since I don't have a spare 2 TB disk, I put the faulty one back just to have one last attempt, but made no progress. I left the NAS to resync for two days and it keeps doing it. Funny thing is, when I checked it today the status was not saying it is resync-ing. I was hopeful, that it finally…

Thanks for the reply! I have 2 TB disks. I'll take look at recovery again.