Host: Drive2 Disable NCQ since timeout error

Questions about SNMP, Power, System, Logs, disk, & RAID.
Post Reply
Nees
Know my way around
Posts: 182
Joined: Sat Nov 21, 2009 12:27 am

Host: Drive2 Disable NCQ since timeout error

Post by Nees »

Topic says it all. Host: Drive2 Disabled NCQ since timeout error

But let me start with the beginning and just copy the support ticket I opened. Perhaps someone know a bit more on the subject.
I have a brand new 853 Pro and put in 4 drives. The moment I powered it on, I heard 1 drive clicking and bay 2 would not light up but flicker on/off green.

I did some tests to know if it was the drive, but it was not. Look at the video I made. This will explain it better then words.

https://www.youtube.com/watch?v=11A32mSqe6U

So the drive is fine. Tested with 2 different drives and everytime it went on/off green.

But then... I tested more. I pulled Bay1 and put that drive in Bay2 (I thought perhaps Bay2 was not getting enough power). I don't know why, it worked. Then I put the other drive in Bay1 and all bays were green and disks spin up.
I powered off/on several times. It all worked.

Then I started to initialize a Raid6 Storage Pool and then again I saw very strange activity on Bay2. It started flickering on Bay2.

And then the system logs showed this: Host: Drive2 Disabled NCQ since timeout error.

Does this mean something strange is going on with bay2? Faulty SATA bay/port?
Also, does the Disabled NCQ mean it is now forever disabled on that drive or is it back in use after a reboot or is there a reset command to test the NCQ to see if it happens again?

I just don't trust this brand new NAS.
So not sure what this is and if it is now disabled permanent and this means lower performance or can this be reset?

And before anyone asks what firmware, doesn't matter since it was the moment I pressed the powerbutton it started flickering. The drives are WD RE's.

Code: Select all

[~] # cat /sys/block/sdb/device/queue_depth
31
[~] # cat /sys/block/sda/device/queue_depth
31
[~] # cat /sys/block/sdc/device/queue_depth
31
[~] # cat /sys/block/sdd/device/queue_depth
31
[~] # cat /sys/block/sde/device/queue_depth
31
[~] # cat /sys/block/sdf/device/queue_depth
1
[~] # cat /sys/block/sdg/device/queue_depth
cat: /sys/block/sdg/device/queue_depth: No such file or directory
[~] # cat /sys/block/sdh/device/queue_depth
cat: /sys/block/sdh/device/queue_depth: No such file or directory
This is also strange. I have 5 drives in it currently (Added 4 to created storage pool and raid 6 volume to know how it would work in the future to expand it, so plugged in a 5th drive now)

So 5 drives, that should be a,b,c,d,e. But even SDF gives a queue_depth of 1! And there is not drive. G and H don't give anything as what I would expect from F also. Strange.

But the 31 depth does show NCQ still seems set.
TS-639_Pro-Raid6-WD_RE_GP-3.8.4_20130816
TS-853_Pro-Raid6-WD_RE_4-4.1.3_20150313
User avatar
pwilson
Guru
Posts: 22533
Joined: Fri Mar 06, 2009 11:20 am
Location: Victoria, BC, Canada (UTC-08:00)

Re: Host: Drive2 Disable NCQ since timeout error

Post by pwilson »

It is awesome that you took the time (and trouble) to create:
Nees wrote:[youtube=11A32mSqe6U]NAS Defect[/youtube]
You didn't provide any information about the WD RE drives. Does S.M.A.R.T. show any issues on the drive itself? Your conclusions that this is potentially a Drive "Bay" issue is probably correct. Your video does indeed demonstrate that your WD RE drive behaves differently when placed in the HDD2 slot.

Similarly, your conclusion that the Firmware is likely unrelated, I would also agree with.

You have already done the right thing by opening a ticket. As this is likely a hardware issue, it is highly unlikely that the Community can help much for this issue. You might get some additional troubleshooting information to work with, if you dumped the "dmesg" output on the NAS.

Access the NAS via SSH, login as "admin" and run:

Code: Select all

dmesg
I hope the Helpdesk is able to resolve this for you. I'm sure this is very frustrating for you. Hopefully they will determine that your NAS is defective, and will recommend that you return it to your retailer as a "DOA" unit, and get a replacement. Excellent troubleshooting so far.

Patrick M. Wilson
Victoria, BC Canada
QNAP TS-470 Pro w/ 4 * Western Digital WD30EFRX WD Reds (RAID5) - - Single 8.1TB Storage Pool FW: QTS 4.2.0 Build 20151023 - Kali Linux v1.06 (64bit)
Forums: View My Profile - Search My Posts - View My Photo - View My Location - Top Community Posters
QNAP: Turbo NAS User Manual - QNAP Wiki - QNAP Tutorials - QNAP FAQs

Please review: When you're asking a question, please include the following.
Nees
Know my way around
Posts: 182
Joined: Sat Nov 21, 2009 12:27 am

Re: Host: Drive2 Disable NCQ since timeout error

Post by Nees »

SMART is all fine.

2new drives showed same issue in same bay, until i pulled the first drive and put in 2nd bay. Btw, this is the first time I noticed drives are magnetic on the top. perhaps only those WD4000FYYZ drives are MAGNETIC! wow!
When I put in the first drive, it kinda attached to the 2nd bay slot. Weird sh*t.

Anyway, for what it's worth:

Code: Select all

[~] # dmesg
[   68.148957] created bitmap (1 pages) for device md256
[   68.154156] md256: bitmap initialized from disk: read 1 pages, set 9 of 9 bit                                           s
[   68.168616] md256: detected capacity change from 0 to 542834688
[   68.174611] RAID1 conf printout:
[   68.174625]  --- wd:2 rd:2
[   68.174637]  disk 0, wo:0, o:1, dev:sdd2
[   68.174647]  disk 1, wo:0, o:1, dev:sdc2
[   68.174657] RAID1 conf printout:
[   68.174679]  --- wd:2 rd:2
[   68.174689]  disk 0, wo:0, o:1, dev:sdd2
[   68.174699]  disk 1, wo:0, o:1, dev:sdc2
[   68.174765] md: resync of RAID array md256
[   68.178885] md: minimum _guaranteed_  speed: 5000 KB/sec/disk.
[   68.184729] md: using maximum available idle IO bandwidth (but not more than                                            200000 KB/sec) for resync.
[   68.194120] md: Resyncing started: md256
[   68.198057] md: using 128k window, over a total of 530112k.
[   68.227474]  md256: unknown partition table
[   68.307341] Adding 530108k swap on /dev/md256.  Priority:-1 extents:1 across:                                           530108k
[   68.578594] md: md1 stopped.
[   68.589909] md: bind<sdc3>
[   68.592818] md: bind<sdb3>
[   68.595738] md: bind<sda3>
[   68.598630] md: bind<sdd3>
[   68.602408] md/raid:md1: device sdd3 operational as raid disk 0
[   68.608347] md/raid:md1: device sda3 operational as raid disk 3
[   68.614272] md/raid:md1: device sdb3 operational as raid disk 2
[   68.620193] md/raid:md1: device sdc3 operational as raid disk 1
[   68.633125] md/raid:md1: allocated 69504kB
[   68.637296] md/raid:md1: raid level 6 active with 4 out of 4 devices, algorit                                           hm 2
[   68.644782] RAID conf printout:
[   68.644792]  --- level:6 rd:4 wd:4
[   68.644803]  disk 0, o:1, dev:sdd3
[   68.644814]  disk 1, o:1, dev:sdc3
[   68.644824]  disk 2, o:1, dev:sdb3
[   68.644834]  disk 3, o:1, dev:sda3
[   68.644885] md1: detected capacity change from 0 to 7981186285568
[   68.660540]  md1: unknown partition table
[   68.801368]  md13: unknown partition table
[   69.973485] dm_create -1
[   69.976042] mapped_device minor=0
[   69.979802] dm_table_add_target start linear, start=0, len=41943040, param=9:                                           1 2048, type=18446744071588674400...
[   69.990088] dm-linear: ti->max_io_len = 0
[   69.994126] bio: create slab <bio-1> at 1
[   70.019286] dm_create -1
[   70.021844] mapped_device minor=1
[   70.025543] dm_table_add_target start linear, start=0, len=33161216, param=9:                                           1 15554693120, type=18446744071588674400...
[   70.036442] dm-linear: ti->max_io_len = 0
[   70.040725] dm_create -1
[   70.043276] mapped_device minor=2
[   70.046978] dm_table_add_target start linear, start=0, len=15512748032, param                                           =9:1 41945088, type=18446744071588674400...
[   70.057870] dm-linear: ti->max_io_len = 0
[   70.062387] dm_create -1
[   70.064941] mapped_device minor=3
[   70.068611] dm_table_add_target start thin-pool, start=0, len=15512748032, pa                                           ram=253:1 253:2 2048 0 1 skip_block_zeroing, type=18446744072100075200...
[   70.085482] device-mapper: thin metadata: __create_persistent_data_objects: b                                           lock manger get correctly
[   70.250870] device-mapper: thin: Data device (dm-2) discard unsupported: Disa                                           bling discard passdown.
[   70.260143] dm_create -1
[   70.262699] mapped_device minor=4
[   70.266506] dm_table_add_target start linear, start=0, len=15512748032, param                                           =253:3 0, type=18446744071588674400...
[   70.276957] dm-linear: ti->max_io_len = 0
[   70.281906] dm_table_add_target start thin-pool, start=0, len=15512748032, pa                                           ram=253:1 253:2 2048 0 1 skip_block_zeroing, type=18446744072100075200...
[   70.295515] dm_create -1
[   70.298065] mapped_device minor=5
[   70.301785] dm_table_add_target start thick, start=0, len=15508848640, param=                                           253:3 1, type=18446744072100074944...
[   70.367708] bio: create slab <bio-2> at 2
[   70.371900] device-mapper: thin: Data device (dm-2) discard unsupported: Disa                                           bling discard passdown.
[   71.501876] dm_create -1
[   71.504427] mapped_device minor=0
[   71.508121] dm_table_add_target start flashcache, start=0, len=15508848640, p                                           aram=CG0 /dev/mapper/vg1-lv1 cachedev1, type=18446744072100148000...
[   73.318923] EXT4-fs (dm-0): Mount option "noacl" will be removed by 3.5
[   73.318923] Contact linux-ext4@vger.kernel.org if you think we should keep it                                           .
[   73.318923]
[   74.154825] ext4_init_reserve_inode_table0: dm-0, 59162
[   74.160062] ext4_init_reserve_inode_table2: dm-0, 59162, 0, 0, 4096
[   74.166354] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts:                                            usrjquota=aquota.user,jqfmt=vfsv0,user_xattr,data=ordered,delalloc,noacl
[   88.583623] kjournald starting.  Commit interval 5 seconds
[   88.642829] EXT3-fs (md13): using internal journal
[   88.647631] EXT3-fs (md13): mounted filesystem with ordered data mode
[   95.337635] cryptodev: driver 0.9 loaded.
[   95.353136] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10
[   95.359554] iTCO_wdt: Found a Baytrail SoC TCO device (Version=4, TCOBASE=0x0                                           460)
[   95.369330] iTCO_wdt: initialized. heartbeat=120 sec (nowayout=0)
[   95.392329] fnotify: Load file notify kernel module.
[   95.397756] fnotify:   Launch the fnotify thread: 18446612133602078784
[   95.415566] iTCO_wdt: Timeout value (heartbeat) is set to 120
[   96.444143] usbcore: registered new interface driver snd-usb-audio
[   96.452445] usbcore: registered new interface driver snd-usb-caiaq
[   96.467557] usbcore: registered new interface driver uvcvideo
[   96.473334] USB Video Class driver (1.1.1)
[   96.538723] 8021q: 802.1Q VLAN Support v1.8
[  126.356634] 8021q: adding VLAN 0 to HW filter on device eth0
[  126.615063] 8021q: adding VLAN 0 to HW filter on device eth1
[  126.873416] 8021q: adding VLAN 0 to HW filter on device eth2
[  127.123604] 8021q: adding VLAN 0 to HW filter on device eth3
[  129.494547] igb: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/                                           TX
[  133.482836] md: md256: resync done.
[  133.486374] md: Resyncing done: md256
[  133.517362] RAID1 conf printout:
[  133.517380]  --- wd:2 rd:2
[  133.517395]  disk 0, wo:0, o:1, dev:sdd2
[  133.517407]  disk 1, wo:0, o:1, dev:sdc2
[  133.533965] RAID1 conf printout:
[  133.533976]  --- wd:2 rd:2
[  133.533987]  disk 0, wo:0, o:1, dev:sdd2
[  133.533998]  disk 1, wo:0, o:1, dev:sdc2
[  133.534007] RAID1 conf printout:
[  133.534025]  --- wd:2 rd:2
[  133.534037]  disk 0, wo:0, o:1, dev:sdd2
[  133.534049]  disk 1, wo:0, o:1, dev:sdc2
[  166.737515] igb: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/                                           TX
[  188.088801] warning: `proftpd' uses 32-bit capabilities (legacy support in us                                           e)
[  207.516819] rule type=2, num=0
[  207.588600] Loading iSCSI transport class v2.0-870.
[  207.600681] iscsi: registered transport (tcp)
[  212.708120] Set msys_nodify as 31743
[  217.558220] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery d                                           irectory
[  217.566086] NFSD: starting 90-second grace period (net ffffffff8196b040)
[  220.635586] [fintek_proc_write] cir enable
[  220.639766] fintek_cir: fintek-cir: Dump CIR logical device registers:
[  220.646308] fintek_cir:  * CR CIR BASE ADDR: 0xffff
[  220.651193] fintek_cir:  * CR CIR IRQ NUM:   0xff
[  220.655906] fintek_cir: fintek-cir: Dump CIR registers:
[  220.661148] fintek_cir:  * STATUS:     0xff
[  220.665349] fintek_cir:  * CONTROL:    0xff
[  220.669541] fintek_cir:  * RX_DATA:    0xff
[  220.673732] fintek_cir:  * TX_CONTROL: 0xff
[  220.677926] fintek_cir:  * TX_DATA:    0xff
[ 5354.449961] tun: Universal TUN/TAP device driver, 1.6
[ 5354.455025] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 5354.476637] NET: Registered protocol family 10
[ 5354.481705] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 5354.487929] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
[ 5354.493922] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
[ 5354.510814] Bridge firewalling registered
TS-639_Pro-Raid6-WD_RE_GP-3.8.4_20130816
TS-853_Pro-Raid6-WD_RE_4-4.1.3_20150313
User avatar
pwilson
Guru
Posts: 22533
Joined: Fri Mar 06, 2009 11:20 am
Location: Victoria, BC, Canada (UTC-08:00)

Re: Host: Drive2 Disable NCQ since timeout error

Post by pwilson »

Nees wrote:Anyway, for what it's worth:

Code: Select all

[~] # dmesg
[   68.148957] created bitmap (1 pages) for device md256
[   68.154156] md256: bitmap initialized from disk: read 1 pages, set 9 of 9 bit                                           s
[   68.168616] md256: detected capacity change from 0 to 542834688
[   68.174611] RAID1 conf printout:
[   68.174625]  --- wd:2 rd:2
[   68.174637]  disk 0, wo:0, o:1, dev:sdd2
[   68.174647]  disk 1, wo:0, o:1, dev:sdc2
[   68.174657] RAID1 conf printout:
[   68.174679]  --- wd:2 rd:2
[   68.174689]  disk 0, wo:0, o:1, dev:sdd2
[   68.174699]  disk 1, wo:0, o:1, dev:sdc2
[   68.174765] md: resync of RAID array md256
[   68.178885] md: minimum _guaranteed_  speed: 5000 KB/sec/disk.
[   68.184729] md: using maximum available idle IO bandwidth (but not more than                                            200000 KB/sec) for resync.
[   68.194120] md: Resyncing started: md256
[   68.198057] md: using 128k window, over a total of 530112k.
[   68.227474]  md256: unknown partition table
[   68.307341] Adding 530108k swap on /dev/md256.  Priority:-1 extents:1 across:                                           530108k
[   68.578594] md: md1 stopped.
[   68.589909] md: bind<sdc3>
[   68.592818] md: bind<sdb3>
[   68.595738] md: bind<sda3>
[   68.598630] md: bind<sdd3>
[   68.602408] md/raid:md1: device sdd3 operational as raid disk 0
[   68.608347] md/raid:md1: device sda3 operational as raid disk 3
[   68.614272] md/raid:md1: device sdb3 operational as raid disk 2
[   68.620193] md/raid:md1: device sdc3 operational as raid disk 1
[   68.633125] md/raid:md1: allocated 69504kB
[   68.637296] md/raid:md1: raid level 6 active with 4 out of 4 devices, algorit                                           hm 2
[   68.644782] RAID conf printout:
[   68.644792]  --- level:6 rd:4 wd:4
[   68.644803]  disk 0, o:1, dev:sdd3
[   68.644814]  disk 1, o:1, dev:sdc3
[   68.644824]  disk 2, o:1, dev:sdb3
[   68.644834]  disk 3, o:1, dev:sda3
[   68.644885] md1: detected capacity change from 0 to 7981186285568
[   68.660540]  md1: unknown partition table
[   68.801368]  md13: unknown partition table
[   69.973485] dm_create -1
[   69.976042] mapped_device minor=0
[   69.979802] dm_table_add_target start linear, start=0, len=41943040, param=9:                                           1 2048, type=18446744071588674400...
[   69.990088] dm-linear: ti->max_io_len = 0
[   69.994126] bio: create slab <bio-1> at 1
[   70.019286] dm_create -1
[   70.021844] mapped_device minor=1
[   70.025543] dm_table_add_target start linear, start=0, len=33161216, param=9:                                           1 15554693120, type=18446744071588674400...
[   70.036442] dm-linear: ti->max_io_len = 0
[   70.040725] dm_create -1
[   70.043276] mapped_device minor=2
[   70.046978] dm_table_add_target start linear, start=0, len=15512748032, param                                           =9:1 41945088, type=18446744071588674400...
[   70.057870] dm-linear: ti->max_io_len = 0
[   70.062387] dm_create -1
[   70.064941] mapped_device minor=3
[   70.068611] dm_table_add_target start thin-pool, start=0, len=15512748032, pa                                           ram=253:1 253:2 2048 0 1 skip_block_zeroing, type=18446744072100075200...
[   70.085482] device-mapper: thin metadata: __create_persistent_data_objects: b                                           lock manger get correctly
[   70.250870] device-mapper: thin: Data device (dm-2) discard unsupported: Disa                                           bling discard passdown.
[   70.260143] dm_create -1
[   70.262699] mapped_device minor=4
[   70.266506] dm_table_add_target start linear, start=0, len=15512748032, param                                           =253:3 0, type=18446744071588674400...
[   70.276957] dm-linear: ti->max_io_len = 0
[   70.281906] dm_table_add_target start thin-pool, start=0, len=15512748032, pa                                           ram=253:1 253:2 2048 0 1 skip_block_zeroing, type=18446744072100075200...
[   70.295515] dm_create -1
[   70.298065] mapped_device minor=5
[   70.301785] dm_table_add_target start thick, start=0, len=15508848640, param=                                           253:3 1, type=18446744072100074944...
[   70.367708] bio: create slab <bio-2> at 2
[   70.371900] device-mapper: thin: Data device (dm-2) discard unsupported: Disa                                           bling discard passdown.
[   71.501876] dm_create -1
[   71.504427] mapped_device minor=0
[   71.508121] dm_table_add_target start flashcache, start=0, len=15508848640, p                                           aram=CG0 /dev/mapper/vg1-lv1 cachedev1, type=18446744072100148000...
[   73.318923] EXT4-fs (dm-0): Mount option "noacl" will be removed by 3.5
[   73.318923] Contact linux-ext4@vger.kernel.org if you think we should keep it                                           .
[   73.318923]
[   74.154825] ext4_init_reserve_inode_table0: dm-0, 59162
[   74.160062] ext4_init_reserve_inode_table2: dm-0, 59162, 0, 0, 4096
[   74.166354] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts:                                            usrjquota=aquota.user,jqfmt=vfsv0,user_xattr,data=ordered,delalloc,noacl
[   88.583623] kjournald starting.  Commit interval 5 seconds
[   88.642829] EXT3-fs (md13): using internal journal
[   88.647631] EXT3-fs (md13): mounted filesystem with ordered data mode
[   95.337635] cryptodev: driver 0.9 loaded.
[   95.353136] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10
[   95.359554] iTCO_wdt: Found a Baytrail SoC TCO device (Version=4, TCOBASE=0x0                                           460)
[   95.369330] iTCO_wdt: initialized. heartbeat=120 sec (nowayout=0)
[   95.392329] fnotify: Load file notify kernel module.
[   95.397756] fnotify:   Launch the fnotify thread: 18446612133602078784
[   95.415566] iTCO_wdt: Timeout value (heartbeat) is set to 120
[   96.444143] usbcore: registered new interface driver snd-usb-audio
[   96.452445] usbcore: registered new interface driver snd-usb-caiaq
[   96.467557] usbcore: registered new interface driver uvcvideo
[   96.473334] USB Video Class driver (1.1.1)
[   96.538723] 8021q: 802.1Q VLAN Support v1.8
[  126.356634] 8021q: adding VLAN 0 to HW filter on device eth0
[  126.615063] 8021q: adding VLAN 0 to HW filter on device eth1
[  126.873416] 8021q: adding VLAN 0 to HW filter on device eth2
[  127.123604] 8021q: adding VLAN 0 to HW filter on device eth3
[  129.494547] igb: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/                                           TX
[  133.482836] md: md256: resync done.
[  133.486374] md: Resyncing done: md256
[  133.517362] RAID1 conf printout:
[  133.517380]  --- wd:2 rd:2
[  133.517395]  disk 0, wo:0, o:1, dev:sdd2
[  133.517407]  disk 1, wo:0, o:1, dev:sdc2
[  133.533965] RAID1 conf printout:
[  133.533976]  --- wd:2 rd:2
[  133.533987]  disk 0, wo:0, o:1, dev:sdd2
[  133.533998]  disk 1, wo:0, o:1, dev:sdc2
[  133.534007] RAID1 conf printout:
[  133.534025]  --- wd:2 rd:2
[  133.534037]  disk 0, wo:0, o:1, dev:sdd2
[  133.534049]  disk 1, wo:0, o:1, dev:sdc2
[  166.737515] igb: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/                                           TX
[  188.088801] warning: `proftpd' uses 32-bit capabilities (legacy support in us                                           e)
[  207.516819] rule type=2, num=0
[  207.588600] Loading iSCSI transport class v2.0-870.
[  207.600681] iscsi: registered transport (tcp)
[  212.708120] Set msys_nodify as 31743
[  217.558220] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery d                                           irectory
[  217.566086] NFSD: starting 90-second grace period (net ffffffff8196b040)
[  220.635586] [fintek_proc_write] cir enable
[  220.639766] fintek_cir: fintek-cir: Dump CIR logical device registers:
[  220.646308] fintek_cir:  * CR CIR BASE ADDR: 0xffff
[  220.651193] fintek_cir:  * CR CIR IRQ NUM:   0xff
[  220.655906] fintek_cir: fintek-cir: Dump CIR registers:
[  220.661148] fintek_cir:  * STATUS:     0xff
[  220.665349] fintek_cir:  * CONTROL:    0xff
[  220.669541] fintek_cir:  * RX_DATA:    0xff
[  220.673732] fintek_cir:  * TX_CONTROL: 0xff
[  220.677926] fintek_cir:  * TX_DATA:    0xff
[ 5354.449961] tun: Universal TUN/TAP device driver, 1.6
[ 5354.455025] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 5354.476637] NET: Registered protocol family 10
[ 5354.481705] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 5354.487929] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
[ 5354.493922] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
[ 5354.510814] Bridge firewalling registered
Yes, that "dmesg" output isn't very helpful to your issue. It unfortunately does not contain any information about the RAID10 array setup at boot. The output threw me off a bit, as it shows a Storage Pool, while your Forum Profile lists a "TS-639 Pro" rather than a "TS-x53 Pro", but this was easily clarified by reviewing your original message which does clearly identify that you are talking about a TS-853 Pro.

QNAP should be open this evening. (It is already Jan 2nd, 2015 in Taiwan). Hopefully they will respond to your "ticket" soon.

Patrick M. Wilson
Victoria, BC Canada
QNAP TS-470 Pro w/ 4 * Western Digital WD30EFRX WD Reds (RAID5) - - Single 8.1TB Storage Pool FW: QTS 4.2.0 Build 20151023 - Kali Linux v1.06 (64bit)
Forums: View My Profile - Search My Posts - View My Photo - View My Location - Top Community Posters
QNAP: Turbo NAS User Manual - QNAP Wiki - QNAP Tutorials - QNAP FAQs

Please review: When you're asking a question, please include the following.
Nees
Know my way around
Posts: 182
Joined: Sat Nov 21, 2009 12:27 am

Re: Host: Drive2 Disable NCQ since timeout error

Post by Nees »

Still no reply, but send it back the the vendor anyway, just now.

Bay2 is still acting up from time to time.

Just for fun:MORE YOUTUBE! D:

Bay2 strange flicker from time to time. Did it twice in 5 boots.

[youtube=MU_sNf9bOmU][/youtube]

And today something strange started to happen with the fans.

[youtube=yVs4R7gPvXs][/youtube]

And even louder!

(not sure why the video's aint working...)

[youtube=ObV5ftHPEPI][/youtube]
Last edited by Nees on Sun Jan 04, 2015 3:40 am, edited 1 time in total.
TS-639_Pro-Raid6-WD_RE_GP-3.8.4_20130816
TS-853_Pro-Raid6-WD_RE_4-4.1.3_20150313
User avatar
pwilson
Guru
Posts: 22533
Joined: Fri Mar 06, 2009 11:20 am
Location: Victoria, BC, Canada (UTC-08:00)

Re: Host: Drive2 Disable NCQ since timeout error

Post by pwilson »

Nees wrote:Still no reply, but send it back the the vendor anyway, just now.

Bay2 is still acting up from time to time.

Just for fun:MORE YOUTUBE! D:

Bay2 strange flicker from time to time. Did it twice in 5 boots.

[youtube=]http://www.youtube.com/watch?v=MU_sNf9bOmU[/youtube]


Try this instead:

Code: Select all

[youtube=MU_sNf9bOmU]Bay2 boot problem[/youtube]
This produces the following:
[youtube=MU_sNf9bOmU]Bay2 boot problem[/youtube]
Nees wrote:And today something strange started to happen with the fans.

[youtube=]http://www.youtube.com/watch?v=yVs4R7gPvXs[/youtube]

And even louder!

(not sure why the video's aint working...)
For this one use:

Code: Select all

[youtube=yVs4R7gPvXs]Ticking fan no drives[/youtube]
Which produces:
[youtube=yVs4R7gPvXs]Ticking fan no drives[/youtube]

And for this:
Nees wrote:[youtube=]http://www.youtube.com/watch?v=ObV5ftHPEPI[/youtube]

Code: Select all

[youtube=ObV5ftHPEPI]Fans ticking[/youtube]
For:
[youtube=ObV5ftHPEPI]Fans ticking[/youtube]

Patrick M. Wilson
Victoria, BC Canada
QNAP TS-470 Pro w/ 4 * Western Digital WD30EFRX WD Reds (RAID5) - - Single 8.1TB Storage Pool FW: QTS 4.2.0 Build 20151023 - Kali Linux v1.06 (64bit)
Forums: View My Profile - Search My Posts - View My Photo - View My Location - Top Community Posters
QNAP: Turbo NAS User Manual - QNAP Wiki - QNAP Tutorials - QNAP FAQs

Please review: When you're asking a question, please include the following.
Nees
Know my way around
Posts: 182
Joined: Sat Nov 21, 2009 12:27 am

Re: Host: Drive2 Disable NCQ since timeout error

Post by Nees »

Fixed it. Thx

they repsonded to the ticket. try this, try that... ignoring the fact how I got it to work without any reason and ignoring the time error in logs. But now that the fans make that strange noise and the blinking light at boot from time to time... This isn't just a nas to trust anymore.
TS-639_Pro-Raid6-WD_RE_GP-3.8.4_20130816
TS-853_Pro-Raid6-WD_RE_4-4.1.3_20150313
User avatar
McBride
Know my way around
Posts: 107
Joined: Fri Jun 07, 2013 3:00 pm
Location: Vienna

Re: Host: Drive2 Disable NCQ since timeout error

Post by McBride »

@Nees
Found the same error message in my log. Therefore the question: How did you fix it? Did it just start to work for no apparent reason?
stephanek
Starting out
Posts: 42
Joined: Wed Feb 16, 2011 10:43 pm

Re: Host: Drive2 Disable NCQ since timeout error

Post by stephanek »

Just facing the same here with a brand new TS-851 and WD pruple 4To.. Seems the drive is DOA as it is not seen either on a Windows computer using a USB/SATA dock !
User avatar
pwilson
Guru
Posts: 22533
Joined: Fri Mar 06, 2009 11:20 am
Location: Victoria, BC, Canada (UTC-08:00)

Re: Host: Drive2 Disable NCQ since timeout error

Post by pwilson »

WD Purples are not recommended for NAS use anyway.... :roll: :roll: :roll: :roll:

Buy WD Reds instead....

Patrick M. Wilson
Victoria, BC Canada
QNAP TS-470 Pro w/ 4 * Western Digital WD30EFRX WD Reds (RAID5) - - Single 8.1TB Storage Pool FW: QTS 4.2.0 Build 20151023 - Kali Linux v1.06 (64bit)
Forums: View My Profile - Search My Posts - View My Photo - View My Location - Top Community Posters
QNAP: Turbo NAS User Manual - QNAP Wiki - QNAP Tutorials - QNAP FAQs

Please review: When you're asking a question, please include the following.
stephanek
Starting out
Posts: 42
Joined: Wed Feb 16, 2011 10:43 pm

Re: Host: Drive2 Disable NCQ since timeout error

Post by stephanek »

Why not ? Isn't the 24x7 capabilites of the purple at least as good as WD Red ?
I might be missing some tech details here....
User avatar
schumaku
Guru
Posts: 43579
Joined: Mon Jan 21, 2008 4:41 pm
Location: Kloten (Zurich), Switzerland -- Skype: schumaku
Contact:

Re: Host: Drive2 Disable NCQ since timeout error

Post by schumaku »

pwilson wrote:WD Purples are not recommended for NAS use anyway....
QNAP has started listing the WDPURxx (the WDPUR40) on the compatibility lists :?
stephanek wrote:Just facing the same here with a brand new TS-851 and WD pruple 4To.. Seems the drive is DOA as it is not seen either on a Windows computer using a USB/SATA dock !
This perfectly explains.

So we can close this thread again. 8)
User avatar
pwilson
Guru
Posts: 22533
Joined: Fri Mar 06, 2009 11:20 am
Location: Victoria, BC, Canada (UTC-08:00)

Re: Host: Drive2 Disable NCQ since timeout error

Post by pwilson »

schumaku wrote:
pwilson wrote:WD Purples are not recommended for NAS use anyway....
QNAP has started listing the WDPURxx (the WDPUR40) on the compatibility lists :?
WD still doesn't recommend them for NAS use despite what QNAP might claim.

Patrick M. Wilson
Victoria, BC Canada
QNAP TS-470 Pro w/ 4 * Western Digital WD30EFRX WD Reds (RAID5) - - Single 8.1TB Storage Pool FW: QTS 4.2.0 Build 20151023 - Kali Linux v1.06 (64bit)
Forums: View My Profile - Search My Posts - View My Photo - View My Location - Top Community Posters
QNAP: Turbo NAS User Manual - QNAP Wiki - QNAP Tutorials - QNAP FAQs

Please review: When you're asking a question, please include the following.
User avatar
schumaku
Guru
Posts: 43579
Joined: Mon Jan 21, 2008 4:41 pm
Location: Kloten (Zurich), Switzerland -- Skype: schumaku
Contact:

Re: Host: Drive2 Disable NCQ since timeout error

Post by schumaku »

pwilson wrote:WD still doesn't recommend them for NAS use despite what QNAP might claim.
Yes, of course. Bet you recognized the Smiley .... :roll:
Post Reply

Return to “System & Disk Volume Management”