[Sungwoo Kang]

Thanks for your comment Bob!

Since S3 bucket uses linux also, it has strict file name restriction, too. So sync from S3 to NAS should be fine.
Actually, a QNAP support guy connected my laptop through Teamview and look into my NAS. And we reproduced the shut down. All we did was launch a Filestation and go to the folder that has 4 video files and refresh the Filestation. After I turned it on again, RAID sync started. The support team suggested that after sync finished, connect the NAS to the direct power source.
I did the test this morning and it worked well. I found that when the file station making the thumbnails of videos, CPU utilization goes 99%. That means high power consumption so I assumed UPS is faulty. So I tested UPS with 2 laptops running full load test, but it could handle up to 380W which is more than the QNAP NAS and switch’s power consumption.
Anyway, since it’s working well and I need to comback home today, I decided to let our editors use QNAP without UPS until we get another UPS. If you feel I miss something or have some other advice, please let me know.
Thanks!

[Sungwoo Kang]

I just found out that one specific file was the problem. If I try to rename it, the system goes down. Is it a sign of HDD fault?

[Sungwoo Kang]

The 1685 is connected UPS, when it shut down other devices were fine I can say UPS is fine. I deleted my RAID 6 volume last Friday night and the NAS was up and running during whole weekend without any issue. So it is unlikely the PSU is a faulty one. Yesterday I updated latest firmware, 4.3.4.0695 and this morning the RAID sync was done without issue. So I synced 4 video files from AWS S3 and it also went well. But when I rename one of the video files, it suddenly turned off again. I could rename the file after reboot, but I don’t think I can rely on this machine.
I am a software engineer working at a VR company located in Silicon Valley, but our production team is in LA so I went to LA and installed the system. Now that the system became unstable, I came to LA again yesterday and have been trying to fix the issue. But I think I am stuck again.