Hibernation not working?

Permissions, domain/LDAP, power, security, notification and more.
Post Reply
User avatar
dmderev
Posts: 8
Joined: 23 May 2020, 13:05

Re: Hibernation not working?

Post by dmderev » 29 May 2020, 08:12

A week is nearly over. The head activity has stopped. The disks are still continuously spinning. The current consumption is ~1A (12W).
I purchased this NAS because it was advertised as consuming ~2W when not spinning (my use case is to keep it mostly idle).
So far these expectations did not materialize.

I learned to log in to OpenWRT (this is "TOS") and check some activities.
root@TNAS-01052F_4TB:~# uname -a
Linux TNAS-01052F_4TB 4.4.18-g8bcbd8a-dirty #884 SMP Tue Jan 15 16:25:11 CST 2019 aarch64 GNU/Linux
root@TNAS-01052F_4TB:~# cat /proc/version
Linux version 4.4.18-g8bcbd8a-dirty (root@developer) (gcc version 4.9.4 (OpenWrt/Linaro GCC 4.9-2015.06 r48422) ) #884 SMP Tue Jan 15 16:25:11 CST 2019

The APM policy is set to 128 (hdparm -B /dev/sdb) on both disks /dev/sdb, /dev/sdc; this by description is the power management policy with most optimizations which *does not allow spin down*. I tried to change it by setting it to 1 on both drives (I am using RAID1 configuration). It created and interesting effect: the disks do spin down (current consumption 0.4A (~5W). It stays in stopped mode for ~45-100 seconds, and then spins up the disks, to go to spin down state in few minutes, then spins up again. Durning spin=up, the power consumption is ~3A and it creates spin up noise. So I think that it is actually worse than keeping the disks spinning all the time.

The RAID1 array is actually mounted filesystem /mnt/md0 from mdarm driver:

root@TNAS-01052F_4TB:~# mdadm --misc --detail /dev/md0
/dev/md0:
Version : 1.2
Creation Time : Thu May 21 21:14:26 2020
Raid Level : raid1
Array Size : 3901593408 (3720.85 GiB 3995.23 GB)
Used Dev Size : 3901593408 (3720.85 GiB 3995.23 GB)
Raid Devices : 2
Total Devices : 2
Persistence : Superblock is persistent

Intent Bitmap : Internal

Update Time : Thu May 28 17:14:51 2020
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0

Name : TNAS-01052F:UTOSUSER-X86-S64
UUID : 2fa9f21f:0743a644:0e138aea:3ec0390b
Events : 2

Number Major Minor RaidDevice State
0 8 20 0 active sync /dev/sdb4
1 8 36 1 active sync /dev/sdc4

Nothing special, and so far no explanation to make it go into spin-down state.

User avatar
Joe-CCS
Posts: 1
Joined: 29 May 2020, 16:10

Re: Hibernation not working?

Post by Joe-CCS » 29 May 2020, 16:20

I have done everything suggested by support and my F4-210 has been running for a week and has never activated hibernation. Not running any applications just want to use it to hold backups once in a while. After reading all the issues with this I am assuming this device is not being supported. I would not recommend it to anyone unless this gets fixed. I have not been given any specific details on anything to try and have the latest software installed from the website. Please let me know if this will be fixed or I will return it to AMAZON.

User avatar
TMroy
Customer Service
Posts: 635
Joined: 10 Mar 2020, 14:04

Re: Hibernation not working?

Post by TMroy » 30 May 2020, 10:54

Adam804t wrote:
20 May 2020, 06:10
I have only just purchased a f2-210 and set it up on Saturday (4 days ago) I purchased it to store and stream my extensive media library from and only have the emby app installed. I have also had hibernation issues I have it set to 30 mins but I have gone hours with the lights solid green lights without hibernating. I have manually updated it to the TOS recommended on the previous page but so far not change. For this reason I have been turning it off over night. Will it just need left on constantly for a period of time before it will start hibernating.
Only one Emby will good enough to stop your drive hibernation.
To contact our tech team or want a remote session, please email to support(at)terra-master.com

User avatar
TMroy
Customer Service
Posts: 635
Joined: 10 Mar 2020, 14:04

Re: Hibernation not working?

Post by TMroy » 30 May 2020, 10:59

To all who concerning the drive hibernation feature, please read following post and specially the NOTE in the post.
viewtopic.php?f=75&t=473
To contact our tech team or want a remote session, please email to support(at)terra-master.com

User avatar
dmderev
Posts: 8
Joined: 23 May 2020, 13:05

Re: Hibernation not working?

Post by dmderev » 30 May 2020, 14:28

This post unfortunately does not solve the problems in the software. One major problem is that you left debug logs to be written to disk. For instance, every time it renews IP address, the log is written and the disks are spinning. There are also error messages about missing paths and components. For instance, if the DHCP lease time is set to 40 minutes (default in my router), the NAS re-requests IP address every 20 minutes and writes these events into log files, and with 30 mins disk stop delay disks never spin down. You guys can easily verify it in your lab.
It is also desirable to reduce the option to 10 and 20 mins. I sent the detailed e-mail with attached error logs and hope that you fix your software.
"As Is" it is not a very usable box for home user.

As for the NOTE - it makes sense to list a period at which applications are accessing the drive, and explain why they should not be enabled in the user manual and datasheet. When claiming that NAS supports specific application while it really does not support them with low power mode means that the buyer may look for a different product. Same about logging and the debug logs that cannot be disabled from menus. They must be fixed. Besides, in few cases these are not "applications" that access disk for good, but rather debug logs which were not removed when releasing the firmware.
Attachments
LOGS.zip
Logs showing errors and frequency of the events when the NAS is NOT accessed by anyone.
(6.19 KiB) Downloaded 27 times

User avatar
TMroy
Customer Service
Posts: 635
Joined: 10 Mar 2020, 14:04

Re: Hibernation not working?

Post by TMroy » 30 May 2020, 17:42

Thank you! I will forward your post to the tech guys, I will keep you be updated.
To contact our tech team or want a remote session, please email to support(at)terra-master.com

User avatar
TMroy
Customer Service
Posts: 635
Joined: 10 Mar 2020, 14:04

Re: Hibernation not working?

Post by TMroy » 01 Jun 2020, 17:33

Hi dmderev,
Please find following answer from our tech guys.

all the logs you mentioned was written to a var directory,var is a virtual tmpfs space in ram, it does not write to drive, so such log writting will not spin up your drives. Only when you write to /dev/md9 and /dev/mapper/vg0-lv0, drives may spin up. following is a example for your to understand.
root@TNAS-011745:/var/log# df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 512 0 512 0% /dev
/dev/md9 2885520 342264 2376964 13% /
tmpfs 491164 1532 489632 0% /tmp
tmpfs 512 0 512 0% /dev
tmpfs 491164 1984 489180 0% /var
/dev/mapper/vg0-lv0 971333632 17008 969218768 0% /mnt/md0

by the way, the errors you mentioned like missing path and components are normal system responds you can even not call them issues, that will not spin up your drives too. We are still checking the possibility of drive spin up, but until this moment, there is nothing alnormal found here.
To contact our tech team or want a remote session, please email to support(at)terra-master.com

User avatar
dmderev
Posts: 8
Joined: 23 May 2020, 13:05

Re: Hibernation not working?

Post by dmderev » 04 Jun 2020, 04:29

Ok, I understand about /var; the writes to it alone may not create spin-ups.

However, the out-of the box installation of most recent TOS does write into md9 every time the DHCP lease for the drive is requested as demonstrated in the log below. With user accessing only the browser interface, it is impossible to have it stop disk when DHCP lease validity is less than 1 hour.

I managed to disable these writes by implementing attached configuration. I am not 100% positive that the disk is not spinning up now on this event exactly but I manually changed the spindown time to 5 minutes and increased lease time to 3 hours. In this case I mostly see the disks stopped when I pay attention to it. They mostly reporting status "standby". IMHO, it would be great if this status could be reported through LEDs on the front panel also.

I see that there were and are errors in iptables on every DHCP renewal: xt_unregister_matches and the missing CP850 from inetifd.

Maybe these are the cause of accessing md9? It would be a good idea to fix the production software at least to eliminate error messages.

[Fri May 29 01:22:44 2020] sed(28691): WRITE block 270504 on md9 (8 sectors)
[Fri May 29 01:22:44 2020] md9_raid1(236): WRITE block 8 on sdc2 (1 sectors)
[Fri May 29 01:22:44 2020] md9_raid1(236): WRITE block 8 on sdb2 (1 sectors)
[Fri May 29 01:22:44 2020] sed(28707): WRITE block 270872 on md9 (8 sectors)
[Fri May 29 01:22:44 2020] sed(28708): WRITE block 271248 on md9 (8 sectors)
[Fri May 29 01:22:44 2020] sed(28712): WRITE block 273872 on md9 (8 sectors)
[Fri May 29 01:22:44 2020] sed(28716): WRITE block 274784 on md9 (8 sectors)
[Fri May 29 01:22:44 2020] sed(28717): WRITE block 274840 on md9 (8 sectors)
[Fri May 29 01:22:44 2020] sed(28722): WRITE block 274856 on md9 (8 sectors)
[Fri May 29 01:22:44 2020] sed(28726): WRITE block 274952 on md9 (8 sectors)
[Fri May 29 01:22:44 2020] sed(28727): WRITE block 276072 on md9 (8 sectors)
[Fri May 29 01:22:44 2020] uci(28730): WRITE block 1015856 on md9 (8 sectors)
[Fri May 29 01:22:44 2020] jbd2/md9-8(258): WRITE block 2628376 on md9 (8 sectors)
[Fri May 29 01:22:44 2020] jbd2/md9-8(258): WRITE block 2628384 on md9 (8 sectors)
[Fri May 29 01:22:44 2020] jbd2/md9-8(258): WRITE block 2628392 on md9 (8 sectors)
[Fri May 29 01:22:44 2020] jbd2/md9-8(258): WRITE block 2628400 on md9 (8 sectors)
[Fri May 29 01:22:44 2020] jbd2/md9-8(258): WRITE block 2628408 on md9 (8 sectors)
[Fri May 29 01:22:44 2020] jbd2/md9-8(258): WRITE block 2628416 on md9 (8 sectors)
[Fri May 29 01:22:44 2020] jbd2/md9-8(258): WRITE block 2628424 on md9 (8 sectors)
[Fri May 29 01:22:44 2020] jbd2/md9-8(258): WRITE block 2628432 on md9 (8 sectors)
[Fri May 29 01:22:44 2020] jbd2/md9-8(258): WRITE block 2628440 on md9 (8 sectors)
[Fri May 29 01:22:44 2020] jbd2/md9-8(258): WRITE block 2628448 on md9 (8 sectors)
[Fri May 29 01:22:44 2020] jbd2/md9-8(258): WRITE block 2628456 on md9 (8 sectors)
[Fri May 29 01:22:44 2020] jbd2/md9-8(258): WRITE block 2628464 on md9 (8 sectors)
[Fri May 29 01:22:44 2020] xt_iprange: Unknown symbol xt_unregister_matches (err 0)
[Fri May 29 01:22:44 2020] xt_iprange: Unknown symbol xt_register_matches (err 0)
[Fri May 29 01:22:44 2020] md9_raid1(236): WRITE block 8 on sdc2 (1 sectors)
[Fri May 29 01:22:44 2020] md9_raid1(236): WRITE block 8 on sdb2 (1 sectors)
[Fri May 29 01:22:50 2020] jbd2/md9-8(258): WRITE block 2628472 on md9 (8 sectors)
[Fri May 29 01:22:50 2020] md9_raid1(236): WRITE block 8 on sdc2 (1 sectors)
[Fri May 29 01:22:50 2020] md9_raid1(236): WRITE block 8 on sdb2 (1 sectors)
[Fri May 29 01:22:50 2020] jbd2/md9-8(258): WRITE block 2628480 on md9 (8 sectors)
[Fri May 29 01:22:50 2020] jbd2/md9-8(258): WRITE block 2628488 on md9 (8 sectors)
[Fri May 29 01:22:50 2020] jbd2/md9-8(258): WRITE block 2628496 on md9 (8 sectors)
[Fri May 29 01:22:50 2020] jbd2/md9-8(258): WRITE block 2628504 on md9 (8 sectors)
[Fri May 29 01:22:50 2020] jbd2/md9-8(258): WRITE block 2628512 on md9 (8 sectors)
[Fri May 29 01:22:50 2020] jbd2/md9-8(258): WRITE block 2628520 on md9 (8 sectors)
[Fri May 29 01:22:50 2020] jbd2/md9-8(258): WRITE block 2628528 on md9 (8 sectors)
[Fri May 29 01:22:50 2020] jbd2/md9-8(258): WRITE block 2628536 on md9 (8 sectors)
[Fri May 29 01:22:50 2020] md9_raid1(236): WRITE block 8 on sdc2 (1 sectors)
[Fri May 29 01:22:50 2020] md9_raid1(236): WRITE block 8 on sdb2 (1 sectors)
[Fri May 29 01:23:19 2020] kworker/u8:1(9768): WRITE block 68536 on md9 (8 sectors)
[Fri May 29 01:23:19 2020] md9_raid1(236): WRITE block 8 on sdc2 (1 sectors)
[Fri May 29 01:23:19 2020] md9_raid1(236): WRITE block 8 on sdb2 (1 sectors)
[Fri May 29 01:23:19 2020] kworker/u8:1(9768): WRITE block 68592 on md9 (8 sectors)
[Fri May 29 01:23:19 2020] kworker/u8:1(9768): WRITE block 0 on md9 (8 sectors)
[Fri May 29 01:23:19 2020] kworker/u8:1(9768): WRITE block 8 on md9 (8 sectors)
[Fri May 29 01:23:19 2020] kworker/u8:1(9768): WRITE block 2944 on md9 (8 sectors)
[Fri May 29 01:23:19 2020] kworker/u8:1(9768): WRITE block 2960 on md9 (8 sectors)
[Fri May 29 01:23:19 2020] kworker/u8:1(9768): WRITE block 3072 on md9 (8 sectors)
[Fri May 29 01:23:19 2020] kworker/u8:1(9768): WRITE block 3224 on md9 (8 sectors)
[Fri May 29 01:23:19 2020] kworker/u8:1(9768): WRITE block 3304 on md9 (8 sectors)
[Fri May 29 01:23:19 2020] kworker/u8:1(9768): WRITE block 7960 on md9 (8 sectors)
[Fri May 29 01:23:19 2020] md9_raid1(236): WRITE block 8 on sdc2 (1 sectors)
[Fri May 29 01:23:19 2020] md9_raid1(236): WRITE block 8 on sdb2 (1 sectors)
[Fri May 29 01:42:43 2020] sed(22418): WRITE block 270504 on md9 (8 sectors)
[Fri May 29 01:42:43 2020] md9_raid1(236): WRITE block 8 on sdc2 (1 sectors)
[Fri May 29 01:42:43 2020] md9_raid1(236): WRITE block 8 on sdb2 (1 sectors)
[Fri May 29 01:42:44 2020] sed(22442): WRITE block 270872 on md9 (8 sectors)
[Fri May 29 01:42:44 2020] sed(22443): WRITE block 271120 on md9 (8 sectors)
[Fri May 29 01:42:44 2020] uci(22450): WRITE block 1032264 on md9 (8 sectors)
[Fri May 29 01:42:44 2020] jbd2/md9-8(258): WRITE block 2628544 on md9 (8 sectors)
[Fri May 29 01:42:44 2020] jbd2/md9-8(258): WRITE block 2628552 on md9 (8 sectors)
[Fri May 29 01:42:44 2020] jbd2/md9-8(258): WRITE block 2628560 on md9 (8 sectors)
[Fri May 29 01:42:44 2020] jbd2/md9-8(258): WRITE block 2628568 on md9 (8 sectors)
[Fri May 29 01:42:44 2020] jbd2/md9-8(258): WRITE block 2628576 on md9 (8 sectors)
[Fri May 29 01:42:44 2020] jbd2/md9-8(258): WRITE block 2628584 on md9 (8 sectors)
[Fri May 29 01:42:44 2020] jbd2/md9-8(258): WRITE block 2628592 on md9 (8 sectors)
[Fri May 29 01:42:44 2020] jbd2/md9-8(258): WRITE block 2628600 on md9 (8 sectors)
[Fri May 29 01:42:44 2020] jbd2/md9-8(258): WRITE block 2628608 on md9 (8 sectors)
[Fri May 29 01:42:44 2020] jbd2/md9-8(258): WRITE block 2628616 on md9 (8 sectors)
[Fri May 29 01:42:44 2020] jbd2/md9-8(258): WRITE block 2628624 on md9 (8 sectors)
[Fri May 29 01:42:44 2020] jbd2/md9-8(258): WRITE block 2628632 on md9 (8 sectors)
[Fri May 29 01:42:44 2020] xt_iprange: Unknown symbol xt_unregister_matches (err 0)
[Fri May 29 01:42:44 2020] xt_iprange: Unknown symbol xt_register_matches (err 0)
[Fri May 29 01:42:44 2020] md9_raid1(236): WRITE block 8 on sdc2 (1 sectors)
[Fri May 29 01:42:44 2020] md9_raid1(236): WRITE block 8 on sdb2 (1 sectors)
[Fri May 29 01:42:49 2020] jbd2/md9-8(258): WRITE block 2628640 on md9 (8 sectors)
[Fri May 29 01:42:49 2020] md9_raid1(236): WRITE block 8 on sdc2 (1 sectors)
[Fri May 29 01:42:49 2020] md9_raid1(236): WRITE block 8 on sdb2 (1 sectors)
[Fri May 29 01:42:49 2020] jbd2/md9-8(258): WRITE block 2628648 on md9 (8 sectors)
[Fri May 29 01:42:49 2020] jbd2/md9-8(258): WRITE block 2628656 on md9 (8 sectors)
[Fri May 29 01:42:49 2020] jbd2/md9-8(258): WRITE block 2628664 on md9 (8 sectors)
[Fri May 29 01:42:49 2020] jbd2/md9-8(258): WRITE block 2628672 on md9 (8 sectors)
[Fri May 29 01:42:49 2020] jbd2/md9-8(258): WRITE block 2628680 on md9 (8 sectors)
[Fri May 29 01:42:49 2020] jbd2/md9-8(258): WRITE block 2628688 on md9 (8 sectors)

[Tue Jun 2 11:44:11 2020] xt_iprange: Unknown symbol xt_unregister_matches (err 0)
[Tue Jun 2 11:44:11 2020] xt_iprange: Unknown symbol xt_register_matches (err 0)
[Tue Jun 2 13:14:11 2020] xt_iprange: Unknown symbol xt_unregister_matches (err 0)
[Tue Jun 2 13:14:11 2020] xt_iprange: Unknown symbol xt_register_matches (err 0)
[Tue Jun 2 14:44:11 2020] xt_iprange: Unknown symbol xt_unregister_matches (err 0)
[Tue Jun 2 14:44:11 2020] xt_iprange: Unknown symbol xt_register_matches (err 0)
[Tue Jun 2 16:14:12 2020] xt_iprange: Unknown symbol xt_unregister_matches (err 0)
[Tue Jun 2 16:14:12 2020] xt_iprange: Unknown symbol xt_register_matches (err 0)
[Tue Jun 2 17:44:12 2020] xt_iprange: Unknown symbol xt_unregister_matches (err 0)
[Tue Jun 2 17:44:12 2020] xt_iprange: Unknown symbol xt_register_matches (err 0)
[Tue Jun 2 19:14:12 2020] xt_iprange: Unknown symbol xt_unregister_matches (err 0)
[Tue Jun 2 19:14:12 2020] xt_iprange: Unknown symbol xt_register_matches (err 0)
[Tue Jun 2 20:44:11 2020] xt_iprange: Unknown symbol xt_unregister_matches (err 0)
[Tue Jun 2 20:44:11 2020] xt_iprange: Unknown symbol xt_register_matches (err 0)
[Tue Jun 2 22:14:12 2020] xt_iprange: Unknown symbol xt_unregister_matches (err 0)
[Tue Jun 2 22:14:12 2020] xt_iprange: Unknown symbol xt_register_matches (err 0)
[Tue Jun 2 23:44:12 2020] xt_iprange: Unknown symbol xt_unregister_matches (err 0)
[Tue Jun 2 23:44:12 2020] xt_iprange: Unknown symbol xt_register_matches (err 0)
[Wed Jun 3 01:14:12 2020] xt_iprange: Unknown symbol xt_unregister_matches (err 0)
[Wed Jun 3 01:14:12 2020] xt_iprange: Unknown symbol xt_register_matches (err 0)
[Wed Jun 3 02:44:12 2020] xt_iprange: Unknown symbol xt_unregister_matches (err 0)
[Wed Jun 3 02:44:12 2020] xt_iprange: Unknown symbol xt_register_matches (err 0)
[Wed Jun 3 04:14:12 2020] xt_iprange: Unknown symbol xt_unregister_matches (err 0)
[Wed Jun 3 04:14:12 2020] xt_iprange: Unknown symbol xt_register_matches (err 0)
[Wed Jun 3 04:54:45 2020] r8169 98016000.gmac eth0: link down
[Wed Jun 3 04:54:48 2020] r8169 98016000.gmac eth0: link up
[Wed Jun 3 04:54:48 2020] r8169 98016000.gmac eth0: rtl_csiar_cond == 0 (loop: 100, delay: 10).
[Wed Jun 3 04:54:48 2020] r8169 98016000.gmac eth0: rtl_csiar_cond == 1 (loop: 100, delay: 10).
[Wed Jun 3 04:54:48 2020] r8169 98016000.gmac eth0: link up
[Wed Jun 3 04:54:49 2020] r8169 98016000.gmac eth0: link down
[Wed Jun 3 04:54:52 2020] r8169 98016000.gmac eth0: link up
[Wed Jun 3 04:54:52 2020] r8169 98016000.gmac eth0: rtl_csiar_cond == 0 (loop: 100, delay: 10).
[Wed Jun 3 04:54:52 2020] r8169 98016000.gmac eth0: rtl_csiar_cond == 1 (loop: 100, delay: 10).
[Wed Jun 3 04:54:52 2020] r8169 98016000.gmac eth0: link up
[Wed Jun 3 04:54:53 2020] r8169 98016000.gmac eth0: link down
[Wed Jun 3 04:54:56 2020] r8169 98016000.gmac eth0: link up
[Wed Jun 3 04:54:56 2020] r8169 98016000.gmac eth0: rtl_csiar_cond == 0 (loop: 100, delay: 10).
[Wed Jun 3 04:54:56 2020] r8169 98016000.gmac eth0: rtl_csiar_cond == 1 (loop: 100, delay: 10).
[Wed Jun 3 04:54:56 2020] r8169 98016000.gmac eth0: link up
[Wed Jun 3 04:55:04 2020] xt_iprange: Unknown symbol xt_unregister_matches (err 0)
[Wed Jun 3 04:55:04 2020] xt_iprange: Unknown symbol xt_register_matches (err 0)
[Wed Jun 3 04:55:30 2020] r8169 98016000.gmac eth0: link down
[Wed Jun 3 04:55:34 2020] r8169 98016000.gmac eth0: link up
[Wed Jun 3 04:55:34 2020] r8169 98016000.gmac eth0: rtl_csiar_cond == 0 (loop: 100, delay: 10).
[Wed Jun 3 04:55:34 2020] r8169 98016000.gmac eth0: rtl_csiar_cond == 1 (loop: 100, delay: 10).
[Wed Jun 3 04:55:34 2020] r8169 98016000.gmac eth0: link up
[Wed Jun 3 04:55:34 2020] r8169 98016000.gmac eth0: link down
[Wed Jun 3 04:55:42 2020] r8169 98016000.gmac eth0: link up
[Wed Jun 3 04:55:42 2020] r8169 98016000.gmac eth0: rtl_csiar_cond == 0 (loop: 100, delay: 10).
[Wed Jun 3 04:55:42 2020] r8169 98016000.gmac eth0: rtl_csiar_cond == 1 (loop: 100, delay: 10).
[Wed Jun 3 04:55:42 2020] r8169 98016000.gmac eth0: link up
[Wed Jun 3 04:55:43 2020] r8169 98016000.gmac eth0: link down
[Wed Jun 3 04:55:46 2020] r8169 98016000.gmac eth0: link up
[Wed Jun 3 04:55:46 2020] r8169 98016000.gmac eth0: rtl_csiar_cond == 0 (loop: 100, delay: 10).
[Wed Jun 3 04:55:46 2020] r8169 98016000.gmac eth0: rtl_csiar_cond == 1 (loop: 100, delay: 10).
[Wed Jun 3 04:55:46 2020] r8169 98016000.gmac eth0: link up
[Wed Jun 3 04:55:47 2020] xt_iprange: Unknown symbol xt_unregister_matches (err 0)
[Wed Jun 3 04:55:47 2020] xt_iprange: Unknown symbol xt_register_matches (err 0)
[Wed Jun 3 06:11:04 2020] r8169 98016000.gmac eth0: link down
[Wed Jun 3 06:11:07 2020] r8169 98016000.gmac eth0: link up
[Wed Jun 3 06:11:07 2020] r8169 98016000.gmac eth0: rtl_csiar_cond == 0 (loop: 100, delay: 10).
[Wed Jun 3 06:11:07 2020] r8169 98016000.gmac eth0: rtl_csiar_cond == 1 (loop: 100, delay: 10).
[Wed Jun 3 06:11:07 2020] r8169 98016000.gmac eth0: link up
[Wed Jun 3 06:11:08 2020] r8169 98016000.gmac eth0: link down
[Wed Jun 3 06:11:11 2020] r8169 98016000.gmac eth0: link up
[Wed Jun 3 06:11:11 2020] r8169 98016000.gmac eth0: rtl_csiar_cond == 0 (loop: 100, delay: 10).
[Wed Jun 3 06:11:11 2020] r8169 98016000.gmac eth0: rtl_csiar_cond == 1 (loop: 100, delay: 10).
[Wed Jun 3 06:11:11 2020] r8169 98016000.gmac eth0: link up
[Wed Jun 3 06:11:13 2020] r8169 98016000.gmac eth0: link down
[Wed Jun 3 06:11:16 2020] r8169 98016000.gmac eth0: link up
[Wed Jun 3 06:11:16 2020] r8169 98016000.gmac eth0: rtl_csiar_cond == 0 (loop: 100, delay: 10).
[Wed Jun 3 06:11:16 2020] r8169 98016000.gmac eth0: rtl_csiar_cond == 1 (loop: 100, delay: 10).
[Wed Jun 3 06:11:16 2020] r8169 98016000.gmac eth0: link up
[Wed Jun 3 06:11:16 2020] r8169 98016000.gmac eth0: link down
[Wed Jun 3 06:11:19 2020] xt_iprange: Unknown symbol xt_unregister_matches (err 0)
[Wed Jun 3 06:11:19 2020] xt_iprange: Unknown symbol xt_register_matches (err 0)
[Wed Jun 3 06:11:20 2020] r8169 98016000.gmac eth0: link up
[Wed Jun 3 06:11:20 2020] r8169 98016000.gmac eth0: rtl_csiar_cond == 0 (loop: 100, delay: 10).
[Wed Jun 3 06:11:20 2020] r8169 98016000.gmac eth0: rtl_csiar_cond == 1 (loop: 100, delay: 10).
[Wed Jun 3 06:11:20 2020] r8169 98016000.gmac eth0: link up
[Wed Jun 3 06:11:20 2020] xt_iprange: Unknown symbol xt_unregister_matches (err 0)
[Wed Jun 3 06:11:20 2020] xt_iprange: Unknown symbol xt_register_matches (err 0)
[Wed Jun 3 06:11:38 2020] r8169 98016000.gmac eth0: link down
[Wed Jun 3 06:11:50 2020] r8169 98016000.gmac eth0: link up
[Wed Jun 3 06:11:50 2020] r8169 98016000.gmac eth0: rtl_csiar_cond == 0 (loop: 100, delay: 10).
[Wed Jun 3 06:11:50 2020] r8169 98016000.gmac eth0: rtl_csiar_cond == 1 (loop: 100, delay: 10).
[Wed Jun 3 06:11:50 2020] r8169 98016000.gmac eth0: link up
[Wed Jun 3 06:11:51 2020] xt_iprange: Unknown symbol xt_unregister_matches (err 0)
[Wed Jun 3 06:11:51 2020] xt_iprange: Unknown symbol xt_register_matches (err 0)
[Wed Jun 3 07:09:35 2020] r8169 98016000.gmac eth0: link down
[Wed Jun 3 07:09:38 2020] r8169 98016000.gmac eth0: link up
[Wed Jun 3 07:09:38 2020] r8169 98016000.gmac eth0: rtl_csiar_cond == 0 (loop: 100, delay: 10).
[Wed Jun 3 07:09:38 2020] r8169 98016000.gmac eth0: rtl_csiar_cond == 1 (loop: 100, delay: 10).
[Wed Jun 3 07:09:38 2020] r8169 98016000.gmac eth0: link up
[Wed Jun 3 07:09:46 2020] xt_iprange: Unknown symbol xt_unregister_matches (err 0)
[Wed Jun 3 07:09:46 2020] xt_iprange: Unknown symbol xt_register_matches (err 0)
[Wed Jun 3 07:10:02 2020] r8169 98016000.gmac eth0: link down
[Wed Jun 3 07:10:06 2020] r8169 98016000.gmac eth0: link up
[Wed Jun 3 07:10:06 2020] r8169 98016000.gmac eth0: rtl_csiar_cond == 0 (loop: 100, delay: 10).
[Wed Jun 3 07:10:06 2020] r8169 98016000.gmac eth0: rtl_csiar_cond == 1 (loop: 100, delay: 10).
[Wed Jun 3 07:10:06 2020] r8169 98016000.gmac eth0: link up
[Wed Jun 3 07:10:06 2020] r8169 98016000.gmac eth0: link down
[Wed Jun 3 07:10:10 2020] r8169 98016000.gmac eth0: link up
[Wed Jun 3 07:10:10 2020] r8169 98016000.gmac eth0: rtl_csiar_cond == 0 (loop: 100, delay: 10).
[Wed Jun 3 07:10:10 2020] r8169 98016000.gmac eth0: rtl_csiar_cond == 1 (loop: 100, delay: 10).
[Wed Jun 3 07:10:10 2020] r8169 98016000.gmac eth0: link up
[Wed Jun 3 07:10:11 2020] r8169 98016000.gmac eth0: link down
[Wed Jun 3 07:10:26 2020] r8169 98016000.gmac eth0: link up
[Wed Jun 3 07:10:26 2020] r8169 98016000.gmac eth0: rtl_csiar_cond == 0 (loop: 100, delay: 10).
[Wed Jun 3 07:10:26 2020] r8169 98016000.gmac eth0: rtl_csiar_cond == 1 (loop: 100, delay: 10).
[Wed Jun 3 07:10:26 2020] r8169 98016000.gmac eth0: link up
[Wed Jun 3 07:10:27 2020] xt_iprange: Unknown symbol xt_unregister_matches (err 0)
[Wed Jun 3 07:10:27 2020] xt_iprange: Unknown symbol xt_register_matches (err 0)
[Wed Jun 3 08:40:34 2020] xt_iprange: Unknown symbol xt_unregister_matches (err 0)
[Wed Jun 3 08:40:34 2020] xt_iprange: Unknown symbol xt_register_matches (err 0)
[Wed Jun 3 10:10:34 2020] xt_iprange: Unknown symbol xt_unregister_matches (err 0)
[Wed Jun 3 10:10:34 2020] xt_iprange: Unknown symbol xt_register_matches (err 0)
[Wed Jun 3 11:40:33 2020] xt_iprange: Unknown symbol xt_unregister_matches (err 0)
[Wed Jun 3 11:40:33 2020] xt_iprange: Unknown symbol xt_register_matches (err 0)
[Wed Jun 3 13:10:34 2020] xt_iprange: Unknown symbol xt_unregister_matches (err 0)
[Wed Jun 3 13:10:34 2020] xt_iprange: Unknown symbol xt_register_matches (err 0)
Attachments
UPDATE.zip
Updates to configuration files which allow to keep disks mostly stopped.
(8.81 KiB) Downloaded 27 times

User avatar
Jawik
Posts: 4
Joined: 04 Jun 2020, 14:47

Re: Hibernation not working?

Post by Jawik » 04 Jun 2020, 15:19

I bought the device on Amazon about a week ago. I set hibernation for 30min. The device wakes me up several times at night with the noise of starting disks. I turned off the internet so no one but me is able to start them but the problem has not disappeared. I noticed that not only I have the problem. Do you help with the return of the device? Now, during pandemics I can wait for the money very long

Thanks

User avatar
TMroy
Customer Service
Posts: 635
Joined: 10 Mar 2020, 14:04

Re: Hibernation not working?

Post by TMroy » 05 Jun 2020, 11:37

Thank you, dmderev. I will keep you updated.
To contact our tech team or want a remote session, please email to support(at)terra-master.com

Post Reply