And a reboot is the standard configuration of the QTS operating system in case of serious failure. But this log doesn't report why the first resync happened. repair) before running into trouble, it will remain in such a reboot cycle. And if your system does not succeed in finishing both (RAID resync and file system check resp. The file system check will not be started automatically. That's why it started with a resync of the RAID and then requires a file system check too. I appreciate your interest in helping on this!Īs far as I understand those logs, it tells me that it went into an unexpected reboot, resulting in dirty RAID and dirty file system. Here are the logs from the latest restart this morning. So reverting config to a more productive (and conservative) set was sufficient to come out of those loops on my systems.Īverage_Joe wrote:There is no reason given for the resync. Before I got a deeper understanding of the QNAP NAS models with QTS operating system, I configured naively and was able to put even my strongest model into reboot cycles. That's why I decided for a low refresh rate in order to limit its impact. Top also shows which impact such monitoring has on the NAS. And the RAM was often used completely on my systems with swapping often already taking place just before reboot. If I remember right, CPU usage rating in top reached orders about 8 before crashing resp. I put such a window into still visible background and proceeded my work on my workplace. What I did to get an idea on my QNAP NAS models was to establish an ssh connection and run top at low refresh rate. The restarts are random so I am not able to monitor usage up to the point of the restart. That's still not critical enough for risking a reboot.Īverage_Joe wrote:I don't know what the CPU and RAM loads are just prior to a restart.
It is actively working on synchronizing the RAID. The first kind of support is announced to expire by February 2023 which has not yet been passed.Īverage_Joe wrote:The current CPU usage is 24-44% and RAM is 36%. I consider QNAPs use of the term EOL inappropriate as every kind of support continues. The successor modelĬomes with same CPU but better NIC. QNAP has declared your model as EOL (as they did also for my TS-431P). (And RAM is extensible for your model if RAM reveals to be the bottle neck.) So I would expect be sufficient for your 64-bit CPU.
For a 32-bit ARM CPU, it would be more than needed for smooth operation. As it is a 64-bit ARM CPU, I've little idea if that amount is appropriate. That's a bit exotic CPU for QNAP products. Storage pool: 1, Priority: Resync First.Īverage_Joe wrote:It is a TS-1232XU-RP with a 1.7 GHz quad core processor and 4 GB of RAM. Information 06:43:12 admin 127.0.0.1 Storage & Snapshots RAID Group Started resyncing RAID group "1". Information 06:42:04 admin 127.0.0.1 Network & Virtual Switch Infrastructure Set "Adapter 2" as the system default gateway. Information 06:42:03 admin 127.0.0.1 Network & Virtual Switch - Initialized Network & Virtual Switch. Information 06:42:03 admin 127.0.0.1 Power NAS Power Status System started. Warning 06:42:03 admin 127.0.0.1 Power NAS Power Status The system was not shut down properly last time. Warning 06:42:02 admin 127.0.0.1 Storage & Snapshots Volume File system not clean. Information 06:42:02 admin 127.0.0.1 Storage & Snapshots RAID Group Started resyncing RAID group "1". I appreciate your interest in helping on this! The current CPU usage is 24-44% and RAM is 36%. I don't know what the CPU and RAM loads are just prior to a restart. It is a TS-1232XU-RP with a 1.7 GHz quad core processor and 4 GB of RAM. Have you taken a look into the system logs of your QNAP to see if there is a reason mentioned or at least a hint? What's the system load and the RAM usage directly before such reboots on your model? That what happens with my QNAP TS-431P from time to time, usually around every 6-7 months now. I know that QNAP NAS reboot by themselves usually after running into some overload of CPU and/or RAM. Sorry, couldn't read which QNAP model you use.
Average_Joe wrote:Usually after this error occurs, my QNAP also performs a Resync on the RAID array and sometimes the QNAP also reboots.
0 kommentar(er)
