New TS351 is unable HDD Standby => SSD caching broken HDD standby

Discussion about hard drive spin down (standby) feature of NAS.
Post Reply
hkfriends
Starting out
Posts: 12
Joined: Thu Jul 10, 2008 10:32 pm

New TS351 is unable HDD Standby => SSD caching broken HDD standby

Post by hkfriends » Sat Nov 17, 2018 3:15 pm

Hi there ,
I have my new TS 351 model (FW latest 4.35.0760) and it is unable spin down my HDD

Bay 1 - HDD RAID 5 - 4TB
Bay 2 - HDD RAID 5 - 4TB
Bay 3 - HDD RAID 5 - 4TB
Internal M.2#1 SSD NVME RAID 1 - 256GB (for cache accel)
Internal M.2#1 SSD NVME RAID 1 - 256GB (for cache accel)

I tried not to enable most of the services and not install applcations

here is the log and anyone has an idea? thanks

Code: Select all


============= 5/100 test, Sat Nov 17 14:20:18 HKT 2018 ===============
<7>[153407.802449] sshd(16070): dirtied inode 104726535 (admin) on dm-0
<7>[153413.655266] jbd2/dm-0-8(3368): WRITE block 7130696592 on dm-0 (8 sectors)
<7>[153413.655326] jbd2/dm-0-8(3368): WRITE block 408095200 on dm-1 (8 sectors)
<7>[153413.657485] jbd2/dm-0-8(3368): WRITE block 7130696600 on dm-0 (8 sectors)
<7>[153413.657509] jbd2/dm-0-8(3368): WRITE block 408095208 on dm-1 (8 sectors)
<7>[153413.657660] jbd2/dm-0-8(3368): WRITE block 7130696608 on dm-0 (8 sectors)
<7>[153427.815477] kworker/u4:2(19354): WRITE block 6702498048 on dm-0 (8 sectors)
<7>[153413.655326] jbd2/dm-0-8(3368): WRITE block 408095200 on dm-1 (8 sectors)
<7>[153413.657509] jbd2/dm-0-8(3368): WRITE block 408095208 on dm-1 (8 sectors)
<7>[153413.657582] kworker/0:0(12348): WRITE block 199240 on dm-1 (8 sectors)
<7>[153413.657713] kworker/u4:0(8972): WRITE block 408095216 on dm-1 (8 sectors)
<7>[153413.657770] kworker/0:0(12348): WRITE block 199240 on dm-1 (8 sectors)
<7>[153427.815541] kworker/u4:2(19354): WRITE block 42141520 on dm-1 (8 sectors)
53326.893782] md9_raid1(2263): WRITE block 1060216 on nvme0n1p1 (1 sectors)
<7>[153326.893800] md9_raid1(2263): WRITE block 1060216 on sdc1 (1 sectors)
<7>[153326.893813] md9_raid1(2263): WRITE block 1060216 on sdb1 (1 sectors)
<7>[153326.908511] md9_raid1(2263): WRITE block 1060232 on sda1 (1 sectors)
<7>[153326.908537] md9_raid1(2263): WRITE block 1060232 on nvme1n1p1 (1 sectors)
<7>[153326.908563] md9_raid1(2263): WRITE block 1060232 on nvme0n1p1 (1 sectors)
<7>[153326.908582] md9_raid1(2263): WRITE block 1060232 on sdc1 (1 sectors)
<7>[153326.908593] md9_raid1(2263): WRITE block 1060232 on sdb1 (1 sectors)
<7>[153413.655352] md2_raid1(2561): WRITE block 480197744 on nvme0n1p3 (1 sectors)
<7>[153413.655381] md2_raid1(2561): WRITE block 480197744 on nvme1n1p3 (1 sectors)
<7>[153413.858378] md2_raid1(2561): WRITE block 480197744 on nvme0n1p3 (1 sectors)
<7>[153413.858416] md2_raid1(2561): WRITE block 480197744 on nvme1n1p3 (1 sectors)
<7>[153427.815574] md2_raid1(2561): WRITE block 480197744 on nvme0n1p3 (1 sectors)
<7>[153427.815616] md2_raid1(2561): WRITE block 480197744 on nvme1n1p3 (1 sectors)
<7>[153428.018603] md2_raid1(2561): WRITE block 480197744 on nvme0n1p3 (1 sectors)
<7>[153326.908511] md9_raid1(2263): WRITE block 1060232 on sda1 (1 sectors)
<7>[153326.893813] md9_raid1(2263): WRITE block 1060216 on sdb1 (1 sectors)
<7>[153326.908593] md9_raid1(2263): WRITE block 1060232 on sdb1 (1 sectors)
<7>[153326.893800] md9_raid1(2263): WRITE block 1060216 on sdc1 (1 sectors)
<7>[153326.908582] md9_raid1(2263): WRITE block 1060232 on sdc1 (1 sectors)

============= 6/100 test, Sat Nov 17 14:21:59 HKT 2018 ===============
<7>[154884.357638] kworker/1:1(2069): READ block 42141520 on dm-1 (8 sectors)
<7>[154884.357664] kworker/1:1(2069): READ block 408095176 on dm-1

============= 7/100 test, Sat Nov 17 14:46:15 HKT 2018 ===============
<7>[154903.506714] kworker/0:0(12348): WRITE block 20552 on dm-1 (8 sectors)
<7>[154903.520991] kworker/0:0(12348): WRITE block 199240 on dm-1 (8 sectors)
<7>[154884.357790] kworker/0:0(12348): WRITE block 6702498048 on dm-7 (8 sectors)
<7>[154903.506489] kworker/0:0(12348): WRITE block 7130696568 on dm-7 (48 sectors)
<7>[154884.357816] md1_raid5(2667): WRITE block 7794127504 on sda3 (1 sectors)
<7>[154884.357844] md1_raid5(2667): WRITE block 7794127504 on sdc3 (1 sectors)
<7>[154884.357859] md1_raid5(2667): WRITE block 7794127504 on sdb3 (1 sectors)
<7>[154903.722061] md1_raid5(2667): WRITE block 7794127504 on sda3 (1 sectors)
<7>[154903.722090] md1_raid5(2667): WRITE block 7794127504 on sdc3 (1 sectors)
<7>[154903.722103] md1_raid5(2667): WRITE block 7794127504 on sdb3 (1 sectors)
<7>[154903.506805] md2_raid1(2561): WRITE block 480197744 on nvme0n1p3 (1 sectors)
<7>[154903.506822] md2_raid1(2561): WRITE block 480197744 on nvme1n1p3 (1 sectors)
<7>[154903.722120] md2_raid1(2561): WRITE block 480197744 on nvme0n1p3 (1 sectors)
<7>[154903.722160] md2_raid1(2561): WRITE block 480197744 on nvme1n1p3 (1 sectors)
<7>[154884.357816] md1_raid5(2667): WRITE block 7794127504 on sda3 (1 sectors)
<7>[154903.722061] md1_raid5(2667): WRITE block 7794127504 on sda3 (1 sectors)
<7>[154884.357859] md1_raid5(2667): WRITE block 7794127504 on sdb3 (1 sectors)
<7>[154903.722103] md1_raid5(2667): WRITE block 7794127504 on sdb3 (1 sectors)
<7>[154884.357844] md1_raid5(2667): WRITE block 7794127504 on sdc3 (1 sectors)
<7>[154903.722090] md1_raid5(2667): WRITE block 7794127504 on sdc3 (1 sectors)

============= 8/100 test, Sat Nov 17 14:48:30 HKT 2018 ===============
<7>[155112.172237] setcfg(11416): dirtied inode 7060 (CACHEDEV1_DATA.log) on md9
<7>[155112.172301] setcfg(11416): dirtied inode 7060 (CACHEDEV1_DATA.log) on md9
<7>[155112.186920] setcfg(11418): dirtied inode 7229 (CACHEDEV1_DATA.lo~) on md9
<7>[155112.193800] sed(11421): dirtied inode 7060 (CACHEDEV1_DATA.logLexg7A) on md9
<7>[155112.278771] sed(11445): dirtied inode 7229 (CACHEDEV1_DATA.logEpY3uK) on md9
<7>[155113.364249] setcfg(11751): dirtied inode 7233 (vg1.log) on md9
<7>[155113.364421] setcfg(11751): dirtied inode 7060 (vg1.lo~) on md9
<7>[155113.370852] sed(11754): dirtied inode 7233 (vg1.logdPQDJT) on md9
<7>[155113.453519] sed(11778): dirtied inode 7060 (vg1.logyBCjjQ) on md9
<7>[155114.833783] setcfg(12780): dirtied inode 7066 (vg256.log) on md9
<7>[155114.833955] setcfg(12780): dirtied inode 7233 (vg256.lo~) on md9
<7>[155114.840448] sed(12783): dirtied inode 7066 (vg256.logKdFYej) on md9
<7>[155114.924048] sed(12807): dirtied inode 7233 (vg256.logY3h0or) on md9
<7>[155115.857923] setcfg(13070): dirtied inode 7002 (vg1_snapshot_usage.log) on md9
<7>[155115.858108] setcfg(13070): dirtied inode 7066 (vg1_snapshot_usage.lo~) on md9
<7>[155115.864376] sed(13073): dirtied inode 7002 (vg1_snapshot_usage.logrlPaNn) on md9
<7>[155115.947333] sed(13097): dirtied inode 7066 (vg1_snapshot_usage.logxuH2Zv) on md9
<7>[155116.782203] setcfg(13302): dirtied inode 6807 (vg1_snapshot_reservation.log) on md9
<7>[155116.782388] setcfg(13302): dirtied inode 7002 (vg1_snapshot_reservation.lo~) on md9
<7>[155116.789972] sed(13305): dirtied inode 6807 (vg1_snapshot_reservation.logFcznfn) on md9
<7>[155116.881318] sed(13330): dirtied inode 7002 (vg1_snapshot_reservation.log4EiZZt) on md9
<7>[155117.175161] kworker/u4:2(19354): WRITE block 344104 on md9 (8 sectors)
<7>[155117.175194] md9_raid1(2263): WRITE block 1060216 on sda1 (1 sectors)
<7>[155117.175194] md9_raid1(2263): WRITE block 1060216 on sda1 (1 sectors)

============= 9/100 test, Sat Nov 17 14:50:07 HKT 2018 ===============
<7>[155117.463174] getcfg(13562): dirtied inode 7002 (vg1_snapshot_reservation.log) on md9
<7>[155117.858152] setcfg(13939): dirtied inode 7002 (vg1_snapshot_reservation.log) on md9
<7>[155117.898848] getcfg(13979): dirtied inode 6829 (vg1_snapshot_recycle.log) on md9
<7>[155117.915427] setcfg(13993): dirtied inode 6807 (vg1_snapshot_recycle.lo~) on md9
<7>[155117.924702] sed(14008): dirtied inode 6829 (vg1_snapshot_recycle.logwqBryz) on md9
<7>[155119.021857] setcfg(15921): dirtied inode 7213 (vg256_snapshot_usage.log) on md9
<7>[155119.022058] setcfg(15921): dirtied inode 6807 (vg256_snapshot_usage.lo~) on md9
<7>[155119.031746] sed(15935): dirtied inode 7213 (vg256_snapshot_usage.log5HZ0KH) on md9
<7>[155119.133049] sed(16036): dirtied inode 6807 (vg256_snapshot_usage.logehiCHO) on md9
<7>[155119.990271] setcfg(16436): dirtied inode 6998 (vg256_snapshot_reservation.log) on md9
<7>[155119.990455] setcfg(16436): dirtied inode 7213 (vg256_snapshot_reservation.lo~) on md9
<7>[155119.996870] sed(16439): dirtied inode 6998 (vg256_snapshot_reservation.logwXIB0H) on md9
<7>[155120.079490] sed(16463): dirtied inode 7213 (vg256_snapshot_reservation.logEKMZwQ) on md9
<7>[155120.882988] getcfg(16665): dirtied inode 7215 (vg256_snapshot_recycle.log) on md9
<7>[155120.896748] setcfg(16667): dirtied inode 6998 (vg256_snapshot_recycle.lo~) on md9
<7>[155120.903111] sed(16670): dirtied inode 7215 (vg256_snapshot_recycle.logDBC24C) on md9
55117.175221] md9_raid1(2263): WRITE block 1060216 on nvme1n1p1 (1 sectors)
<7>[155117.175251] md9_raid1(2263): WRITE block 1060216 on nvme0n1p1 (1 sectors)
<7>[155117.175271] md9_raid1(2263): WRITE block 1060216 on sdc1 (1 sectors)
<7>[155117.175287] md9_raid1(2263): WRITE block 1060216 on sdb1 (1 sectors)
<7>[155117.206533] md9_raid1(2263): WRITE block 1060232 on sda1 (1 sectors)
<7>[155117.206560] md9_raid1(2263): WRITE block 1060232 on nvme1n1p1 (1 sectors)
<7>[155117.206588] md9_raid1(2263): WRITE block 1060232 on nvme0n1p1 (1 sectors)
<7>[155117.206608] md9_raid1(2263): WRITE block 1060232 on sdc1 (1 sectors)
<7>[155117.206619] md9_raid1(2263): WRITE block 1060232 on sdb1 (1 sectors)
<7>[155117.223261] kworker/u4:2(19354): WRITE block 344112 on md9 (8 sectors)
<7>[155117.223278] kworker/u4:2(19354): WRITE block 344136 on md9 (8 sectors)
<7>[155117.223409] kworker/u4:2(19354): WRITE block 295096 on md9 (8 sectors)
<7>[155117.223423] kworker/u4:2(19354): WRITE block 295104 on md9 (8 sectors)
<7>[155117.223434] kworker/u4:2(19354): WRITE block 295120 on md9 (8 sectors)
<7>[155117.223515] kworker/u4:2(19354): WRITE block 377424 on md9 (8 sectors)
<7>[155117.223529] kworker/u4:2(19354): WRITE block 377432 on md9 (8 sectors)
<7>[155117.223540] kworker/u4:2(19354): WRITE block 377440 on md9 (8 sectors)
<7>[155117.223613] kworker/u4:2(19354): WRITE block 409600 on md9 (8 sectors)
<7>[155117.223627] kworker/u4:2(19354): WRITE block 409616 on md9 (8 sectors)
<7>[155117.223694] kworker/u4:2(19354): WRITE block 295128 on md9 (8 sectors)
<7>[155117.223706] kworker/u4:2(19354): WRITE block 295160 on md9 (8 sectors)
<7>[155117.223720] kworker/u4:2(19354): WRITE block 295168 on md9 (8 sectors)
<7>[155117.425310] md9_raid1(2263): WRITE block 1060216 on sda1 (1 sectors)
<7>[155117.425340] md9_raid1(2263): WRITE block 1060216 on nvme1n1p1 (1 sectors)
<7>[155117.425378] md9_raid1(2263): WRITE block 1060216 on nvme0n1p1 (1 sectors)
<7>[155117.425397] md9_raid1(2263): WRITE block 1060216 on sdc1 (1 sectors)
<7>[155117.425411] md9_raid1(2263): WRITE block 1060216 on sdb1 (1 sectors)
<7>[155117.440516] md9_raid1(2263): WRITE block 1060232 on sda1 (1 sectors)
<7>[155117.440542] md9_raid1(2263): WRITE block 1060232 on nvme1n1p1 (1 sectors)
<7>[155117.440567] md9_raid1(2263): WRITE block 1060232 on nvme0n1p1 (1 sectors)
<7>[155117.440585] md9_raid1(2263): WRITE block 1060232 on sdc1 (1 sectors)
<7>[155117.440598] md9_raid1(2263): WRITE block 1060232 on sdb1 (1 sectors)
<7>[155117.463625] kjournald(2280): WRITE block 554048 on md9 (8 sectors)
<7>[155117.463656] md9_raid1(2263): WRITE block 1060216 on sda1 (1 sectors)
<7>[155117.463681] md9_raid1(2263): WRITE block 1060216 on nvme1n1p1 (1 sectors)
<7>[155117.463713] md9_raid1(2263): WRITE block 1060216 on nvme0n1p1 (1 sectors)
<7>[155117.463731] md9_raid1(2263): WRITE block 1060216 on sdc1 (1 sectors)
<7>[155117.463744] md9_raid1(2263): WRITE block 1060216 on sdb1 (1 sectors)
<7>[155117.481708] md9_raid1(2263): WRITE block 1060232 on sda1 (1 sectors)
<7>[155117.481734] md9_raid1(2263): WRITE block 1060232 on nvme1n1p1 (1 sectors)
<7>[155117.481762] md9_raid1(2263): WRITE block 1060232 on nvme0n1p1 (1 sectors)
<7>[155117.481781] md9_raid1(2263): WRITE block 1060232 on sdc1 (1 sectors)
<7>[155117.481792] md9_raid1(2263): WRITE block 1060232 on sdb1 (1 sectors)
<7>[155117.498443] kjournald(2280): WRITE block 554056 on md9 (8 sectors)
<7>[155117.498457] kjournald(2280): WRITE block 554064 on md9 (8 sectors)
<7>[155117.498467] kjournald(2280): WRITE block 554072 on md9 (8 sectors)
<7>[155117.498477] kjournald(2280): WRITE block 554080 on md9 (8 sectors)
<7>[155117.498486] kjournald(2280): WRITE block 554088 on md9 (8 sectors)
<7>[155117.498495] kjournald(2280): WRITE block 554096 on md9 (8 sectors)
<7>[155117.498505] kjournald(2280): WRITE block 554104 on md9 (8 sectors)
<7>[155117.498514] kjournald(2280): WRITE block 554112 on md9 (8 sectors)
<7>[155117.498523] kjournald(2280): WRITE block 554120 on md9 (8 sectors)
<7>[155117.498531] kjournald(2280): WRITE block 554128 on md9 (8 sectors)
<7>[155117.498541] kjournald(2280): WRITE block 554136 on md9 (8 sectors)
<7>[155117.499055] kjournald(2280): WRITE block 554144 on md9 (8 sectors)
<7>[155117.713493] md9_raid1(2263): WRITE block 1060216 on sda1 (1 sectors)
<7>[155117.713523] md9_raid1(2263): WRITE block 1060216 on nvme1n1p1 (1 sectors)
<7>[155117.713560] md9_raid1(2263): WRITE block 1060216 on nvme0n1p1 (1 sectors)
<7>[155117.713580] md9_raid1(2263): WRITE block 1060216 on sdc1 (1 sectors)
<7>[155117.713595] md9_raid1(2263): WRITE block 1060216 on sdb1 (1 sectors)
<7>[155117.732352] md9_raid1(2263): WRITE block 1060232 on sda1 (1 sectors)
<7>[155117.732377] md9_raid1(2263): WRITE block 1060232 on nvme1n1p1 (1 sectors)
<7>[155117.732402] md9_raid1(2263): WRITE block 1060232 on nvme0n1p1 (1 sectors)
<7>[155117.732421] md9_raid1(2263): WRITE block 1060232 on sdc1 (1 sectors)
<7>[155117.732434] md9_raid1(2263): WRITE block 1060232 on sdb1 (1 sectors)
<7>[155123.777423] kjournald(2280): WRITE block 393232 on md9 (8 sectors)
<7>[155123.777450] md9_raid1(2263): WRITE block 1060216 on sda1 (1 sectors)
<7>[155123.777476] md9_raid1(2263): WRITE block 1060216 on nvme1n1p1 (1 sectors)
<7>[155123.777502] md9_raid1(2263): WRITE block 1060216 on nvme0n1p1 (1 sectors)
<7>[155123.777520] md9_raid1(2263): WRITE block 1060216 on sdc1 (1 sectors)
<7>[155123.777533] md9_raid1(2263): WRITE block 1060216 on sdb1 (1 sectors)
<7>[155123.810869] md9_raid1(2263): WRITE block 1060232 on sda1 (1 sectors)
<7>[155123.810892] md9_raid1(2263): WRITE block 1060232 on nvme1n1p1 (1 sectors)
<7>[155123.810918] md9_raid1(2263): WRITE block 1060232 on nvme0n1p1 (1 sectors)
<7>[155123.810936] md9_raid1(2263): WRITE block 1060232 on sdc1 (1 sectors)
<7>[155123.810949] md9_raid1(2263): WRITE block 1060232 on sdb1 (1 sectors)
<7>[155123.827593] kjournald(2280): WRITE block 393312 on md9 (8 sectors)
<7>[155123.827605] kjournald(2280): WRITE block 328680 on md9 (8 sectors)
<7>[155123.827615] kjournald(2280): WRITE block 328744 on md9 (8 sectors)
<7>[155123.827623] kjournald(2280): WRITE block 508200 on md9 (8 sectors)
<7>[155123.827632] kjournald(2280): WRITE block 508208 on md9 (8 sectors)
<7>[155123.827641] kjournald(2280): WRITE block 491528 on md9 (8 sectors)
<7>[155123.827649] kjournald(2280): WRITE block 491552 on md9 (8 sectors)
<7>[155123.828859] kjournald(2280): WRITE block 554152 on md9 (8 sectors)
<7>[155123.828873] kjournald(2280): WRITE block 554160 on md9 (8 sectors)
<7>[155123.828884] kjournald(2280): WRITE block 554168 on md9 (8 sectors)
<7>[155123.828896] kjournald(2280): WRITE block 554176 on md9 (8 sectors)
<7>[155123.828907] kjournald(2280): WRITE block 554184 on md9 (8 sectors)
<7>[155123.828917] kjournald(2280): WRITE block 554192 on md9 (8 sectors)
<7>[155123.828927] kjournald(2280): WRITE block 554200 on md9 (8 sectors)
<7>[155123.828939] kjournald(2280): WRITE block 554208 on md9 (8 sectors)
<7>[155123.828949] kjournald(2280): WRITE block 554216 on md9 (8 sectors)
<7>[155123.828959] kjournald(2280): WRITE block 554224 on md9 (8 sectors)
<7>[155123.828969] kjournald(2280): WRITE block 554232 on md9 (8 sectors)
<7>[155123.829393] kjournald(2280): WRITE block 554240 on md9 (8 sectors)
<7>[155124.067621] md9_raid1(2263): WRITE block 1060216 on sda1 (1 sectors)
<7>[155124.067649] md9_raid1(2263): WRITE block 1060216 on nvme
<7>[155117.206533] md9_raid1(2263): WRITE block 1060232 on sda1 (1 sectors)
<7>[155117.425310] md9_raid1(2263): WRITE block 1060216 on sda1 (1 sectors)
<7>[155117.440516] md9_raid1(2263): WRITE block 1060232 on sda1 (1 sectors)
<7>[155117.463656] md9_raid1(2263): WRITE block 1060216 on sda1 (1 sectors)
<7>[155117.481708] md9_raid1(2263): WRITE block 1060232 on sda1 (1 sectors)
<7>[155117.713493] md9_raid1(2263): WRITE block 1060216 on sda1 (1 sectors)
<7>[155117.732352] md9_raid1(2263): WRITE block 1060232 on sda1 (1 sectors)
<7>[155123.777450] md9_raid1(2263): WRITE block 1060216 on sda1 (1 sectors)
<7>[155123.810869] md9_raid1(2263): WRITE block 1060232 on sda1 (1 sectors)
<7>[155124.067621] md9_raid1(2263): WRITE block 1060216 on sda1 (1 sectors)
<7>[155117.175287] md9_raid1(2263): WRITE block 1060216 on sdb1 (1 sectors)
<7>[155117.206619] md9_raid1(2263): WRITE block 1060232 on sdb1 (1 sectors)
<7>[155117.425411] md9_raid1(2263): WRITE block 1060216 on sdb1 (1 sectors)
<7>[155117.440598] md9_raid1(2263): WRITE block 1060232 on sdb1 (1 sectors)
<7>[155117.463744] md9_raid1(2263): WRITE block 1060216 on sdb1 (1 sectors)
<7>[155117.481792] md9_raid1(2263): WRITE block 1060232 on sdb1 (1 sectors)
<7>[155117.713595] md9_raid1(2263): WRITE block 1060216 on sdb1 (1 sectors)
<7>[155117.732434] md9_raid1(2263): WRITE block 1060232 on sdb1 (1 sectors)
<7>[155123.777533] md9_raid1(2263): WRITE block 1060216 on sdb1 (1 sectors)
<7>[155123.810949] md9_raid1(2263): WRITE block 1060232 on sdb1 (1 sectors)
<7>[155117.175271] md9_raid1(2263): WRITE block 1060216 on sdc1 (1 sectors)
<7>[155117.206608] md9_raid1(2263): WRITE block 1060232 on sdc1 (1 sectors)
<7>[155117.425397] md9_raid1(2263): WRITE block 1060216 on sdc1 (1 sectors)
<7>[155117.440585] md9_raid1(2263): WRITE block 1060232 on sdc1 (1 sectors)
<7>[155117.463731] md9_raid1(2263): WRITE block 1060216 on sdc1 (1 sectors)
<7>[155117.481781] md9_raid1(2263): WRITE block 1060232 on sdc1 (1 sectors)
<7>[155117.713580] md9_raid1(2263): WRITE block 1060216 on sdc1 (1 sectors)
<7>[155117.732421] md9_raid1(2263): WRITE block 1060232 on sdc1 (1 sectors)
<7>[155123.777520] md9_raid1(2263): WRITE block 1060216 on sdc1 (1 sectors)
<7>[155123.810936] md9_raid1(2263): WRITE block 1060232 on sdc1 (1 sectors)

============= 10/100 test, Sat Nov 17 14:50:14 HKT 2018 ===============
<7>[155124.067679] md9_raid1(2263): WRITE block 1060216 on nvme0n1p1 (1 sectors)
<7>[155124.067698] md9_raid1(2263): WRITE block 1060216 on sdc1 (1 sectors)
<7>[155124.067710] md9_raid1(2263): WRITE block 1060216 on sdb1 (1 sectors)
<7>[155124.086154] md9_raid1(2263): WRITE block 1060232 on sda1 (1 sectors)
<7>[155124.086177] md9_raid1(2263): WRITE block 1060232 on nvme1n1p1 (1 sectors)
<7>[155124.086189] md9_raid1(2263): WRITE block 1060232 on nvme0n1p1 (1 sectors)
<7>[155124.086198] md9_raid1(2263): WRITE block 1060232 on sdc1 (1 sectors)
<7>[155124.086208] md9_raid1(2263): WRITE block 1060232 on sdb1 (1 sectors)
<7>[155132.472098] kworker/u4:0(8972): WRITE block 338896 on md9 (8 sectors)
<7>[155132.472128] md9_raid1(2263): WRITE block 1060216 on sda1 (1 sectors)
<7>[155132.472156] md9_raid1(2263): WRITE block 1060216 on nvme1n1p1 (1 sectors)
<7>[155132.472182] md9_raid1(2263): WRITE block 1060216 on nvme0n1p1 (1 sectors)
<7>[155132.472201] md9_raid1(2263): WRITE block 1060216 on sdc1 (1 sectors)
<7>[155132.472215] md9_raid1(2263): WRITE block 1060216 on sdb1 (1 sectors)
<7>[155132.508244] md9_raid1(2263): WRITE block 1060232 on sda1 (1 sectors)
<7>[155132.508256] md9_raid1(2263): WRITE block 1060232 on nvme1n1p1 (1 sectors)
<7>[155132.508273] md9_raid1(2263): WRITE block 1060232 on nvme0n1p1 (1 sectors)
<7>[155132.508288] md9_raid1(2263): WRITE block 1060232 on sdc1 (1 sectors)
<7>[155132.508298] md9_raid1(2263): WRITE block 1060232 on sdb1 (1 sectors)
<7>[155132.524988] kworker/u4:0(8972): WRITE block 0 on md9 (8 sectors)
<7>[155132.525002] kworker/u4:0(8972): WRITE block 8 on md9 (8 sectors)
<7>[155132.525013] kworker/u4:0(8972): WRITE block 262416 on md9 (8 sectors)
<7>[155132.525024] kworker/u4:0(8972): WRITE block 262424 on md9 (8 sectors)
<7>[155132.525034] kworker/u4:0(8972): WRITE block 262512 on md9 (8 sectors)
<7>[155132.525044] kworker/u4:0(8972): WRITE block 262520 on md9 (8 sectors)
<7>[155132.525055] kworker/u4:0(8972): WRITE block 262608 on md9 (8 sectors)
<7>[155132.525065] kworker/u4:0(8972): WRITE block 262640 on md9 (8 sectors)
<7>[155132.525075] kworker/u4:0(8972): WRITE block 262680 on md9 (8 sectors)
<7>[155132.525085] kworker/u4:0(8972): WRITE block 262712 on md9 (8 sectors)
<7>[155132.525095] kworker/u4:0(8972): WRITE block 262720 on md9 (8 sectors)
<7>[155132.525120] kworker/u4:0(8972): WRITE block 262728 on md9 (8 sectors)
<7>[155132.727343] md9_raid1(2263): WRITE block 1060216 on sda1 (1 sectors)
<7>[155132.727371] md9_raid1(2263): WRITE block 1060216 on nvme1n1p1 (1 sectors)
<7>[155132.727400] md9_raid1(2263): WRITE block 1060216 on nvme0n1p1 (1 sectors)
<7>[155132.727418] md9_raid1(2263): WRITE block 1060216 on sdc1 (1 sectors)
<7>[155132.727431] md9_raid1(2263): WRITE block 1060216 on sdb1 (1 sectors)
<7>[155132.741733] md9_raid1(2263): WRITE block 1060232 on sda1 (1 sectors)
<7>[155132.741750] md9_raid1(2263): WRITE block 1060232 on nvme1n1p1 (1 sectors)
<7>[155132.741772] md9_raid1(2263): WRITE block 1060232 on nvme0n1p1 (1 sectors)
<7>[155132.741787] md9_raid1(2263): WRITE block 1060232 on sdc1 (1 sectors)
<7>[155132.741798] md9_raid1(2263): WRITE block 1060232 on sdb1 (1 sectors)
<7>[155124.086154] md9_raid1(2263): WRITE block 1060232 on sda1 (1 sectors)
<7>[155132.472128] md9_raid1(2263): WRITE block 1060216 on sda1 (1 sectors)
<7>[155132.508244] md9_raid1(2263): WRITE block 1060232 on sda1 (1 sectors)
<7>[155132.727343] md9_raid1(2263): WRITE block 1060216 on sda1 (1 sectors)
<7>[155132.741733] md9_raid1(2263): WRITE block 1060232 on sda1 (1 sectors)
<7>[155124.067710] md9_raid1(2263): WRITE block 1060216 on sdb1 (1 sectors)
<7>[155124.086208] md9_raid1(2263): WRITE block 1060232 on sdb1 (1 sectors)
<7>[155132.472215] md9_raid1(2263): WRITE block 1060216 on sdb1 (1 sectors)
<7>[155132.508298] md9_raid1(2263): WRITE block 1060232 on sdb1 (1 sectors)
<7>[155132.727431] md9_raid1(2263): WRITE block 1060216 on sdb1 (1 sectors)
<7>[155132.741798] md9_raid1(2263): WRITE block 1060232 on sdb1 (1 sectors)
<7>[155124.067698] md9_raid1(2263): WRITE block 1060216 on sdc1 (1 sectors)
<7>[155124.086198] md9_raid1(2263): WRITE block 1060232 on sdc1 (1 sectors)
<7>[155132.472201] md9_raid1(2263): WRITE block 1060216 on sdc1 (1 sectors)
<7>[155132.508288] md9_raid1(2263): WRITE block 1060232 on sdc1 (1 sectors)
<7>[155132.727418] md9_raid1(2263): WRITE block 1060216 on sdc1 (1 sectors)
<7>[155132.741787] md9_raid1(2263): WRITE block 1060232 on sdc1 (1 sectors)

============= 11/100 test, Sat Nov 17 14:51:42 HKT 2018 ===============
Last edited by hkfriends on Sun Nov 25, 2018 5:12 pm, edited 2 times in total.

hkfriends
Starting out
Posts: 12
Joined: Thu Jul 10, 2008 10:32 pm

Re: New TS351 is unable HDD Standby => SSD caching broken HDD standby

Post by hkfriends » Sat Nov 17, 2018 4:55 pm

sorry guys, I just found out this issue due to internal SSD M2 (RAID1 - cache for R+W for all I/O) as cache acceleration
it broken the HDD to spin down... I need to disable the cache function. I need to submit this issue to Qnap…

I am going to rebuild the SSD cache in RAID0 for read only (only DB and VM I/O) and see how is it going... :roll:
Last edited by hkfriends on Sun Nov 25, 2018 5:12 pm, edited 1 time in total.

User avatar
dolbyman
Guru
Posts: 20111
Joined: Sat Feb 12, 2011 2:11 am
Location: Vancouver BC , Canada

Re: [Solve] New TS351 is unable HDD Standby => SSD caching broken HDD standby

Post by dolbyman » Sun Nov 18, 2018 12:00 am

please codewrap long outputs


a couple of months ago we wondered who would buy this unit and use caching on it ... with db and vm/containers as the only thing we could come up with ... at least the first user with this unit,uses exactly that

hkfriends
Starting out
Posts: 12
Joined: Thu Jul 10, 2008 10:32 pm

Re: [un-Solved] New TS351 is unable HDD Standby => SSD caching broken HDD standby

Post by hkfriends » Sun Nov 25, 2018 5:12 pm

it is still not working if either using M2 SSD for caching or Qtiers… both cases will make HDD not going to standby mode

the only way is to stop using the M2 SSD

KubazQNAS
New here
Posts: 2
Joined: Fri Dec 13, 2019 10:46 pm

Re: New TS351 is unable HDD Standby => SSD caching broken HDD standby

Post by KubazQNAS » Fri Dec 13, 2019 11:20 pm

Hello, were you able to resolve this or do the newer firmware updates resolve this.
It's and of 2019 and I just bought the same unit and have been researching as to why my HDDs continually spin even though standby mode is on. By spinning i men high (max) rpm constant spin - the unit is humming and will not stop and I feel the vibration it in the walls upstairs. Some say this is normal but my other old NAS on the the same network only wakes up when it needs to. And this sort of Formula1-engine-like spin does not sound normal from what is being advertised as a "green" NAS. I have 8TB WD RED 5400 rpm drives btw. In any case, i stumbled across this discussion because I happened to have a 1TB m.2 stick and thought - might as well put it in the NAS.

Issue 1 - 2GB of RAM is not enough to support SSD of this size and the entire volume must be used. I put in another 2GB of RAM to make the total RAM 4GB and i was then able to configure the m.2 1TB stick for caching. NAS will boot up faster but I can't say i see any other difference other than

Issue 2 - the thing will NOT STOP SPINNING and never sleeps even when everything is disconnected. (I am not sure why, but what this could be it?)

I am not home now but I just found this post so logged into the NAS remotely and turned the caching off. If I come home and the thing is sleeping then this is still an issue. If it's still spinning then i will try to take the stick out completely. Another thought is - since the amount of SSD Cache i have pretty much maxes out the available RAM - in other words 4GB RAM is the minimum for 1TB of single SSD cache - would increasing the RAM to 8GB (max supported) solve this? Not sure but will try when my new RAM arrives. Would appreciate some thoughts on this. Another reason why my drives are spinning without sleep now is that i copied a large volume of data/media to it recently and it could be still indexing and waht not... But it's been days and the thing has not stopped emitting high-spin humming noise.

User avatar
dolbyman
Guru
Posts: 20111
Joined: Sat Feb 12, 2011 2:11 am
Location: Vancouver BC , Canada

Re: New TS351 is unable HDD Standby => SSD caching broken HDD standby

Post by dolbyman » Fri Dec 13, 2019 11:39 pm

side question
what do you mean by max rpm spin?besides wd green there is no variable speed drives(that I know of)

Post Reply

Return to “HDD Spin Down (HDD Standby)”