# How read docker stats ? Node reboot when CPU and MEM are full

**URL:** <https://forum.storj.io/t/how-read-docker-stats-node-reboot-when-cpu-and-mem-are-full/5971>\
**Category:** troubleshooting\
**Tags:** docker, qnap-nas, iscsi\
**Created:** [April 17, 2020, 11:53am UTC](https://forum.storj.io/t/how-read-docker-stats-node-reboot-when-cpu-and-mem-are-full/5971 "2020-04-17T11:53:02Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\
**Post date:** [May 5, 2020, 10:26pm UTC](https://forum.storj.io/t/how-read-docker-stats-node-reboot-when-cpu-and-mem-are-full/5971/10 "2020-05-05T22:26:21Z")

</div>

Could it be possible that you have a SMR drive?  
The IOWAIT is extremely high.

> [@PSA: Beware of HDD manufacturers submarining SMR technology in HDD's without any public mention](https://forum.storj.io/t/psa-beware-of-hdd-manufacturers-submarining-smr-technology-in-hdds-without-any-public-mention/6003):
>
> Recently there have been several reports of SNOs running into massive CPU wait issues. It seems the common thread has been the use of HDD’s in which manufacturers have quietly started using SMR technology. [2003549104] Because of these overlapping tracks, when data is written to the disk, the drive has to rewrite several additional tracks. This obviously leads to much slower writes. These HDD’s usually deal with that using large caches and rewriting the shingles tracks during quiet times. How…

---

_[View the full topic](https://forum.storj.io/t/how-read-docker-stats-node-reboot-when-cpu-and-mem-are-full/5971)._