Pre-clearing a WD20EARS drive. Errors in syslog. [4.7]

I upgrade to 4.7 and everything seemed fine.  Today I picked up a new 2TB WD20EARS and I'm running a pre-clear on it.

• The drive is attached to a AOC-SASLP-MV8 (my first and only drive plugged into this)
  
• The drive is not jumpered
  
• I'm running pre-clear with -A
  

The pre-clear looks normal so far (15% during initial Pre-Read), but I noticed this in the Syslog.  Any idea what it means?

Jan 27 22:25:18 NAS kernel: ------------[ cut here ]------------
Jan 27 22:25:18 NAS kernel: WARNING: at drivers/ata/libata-core.c:5186 ata_qc_issue+0x10b/0x308()
Jan 27 22:25:18 NAS kernel: Hardware name: X7SPA-HF
Jan 27 22:25:18 NAS kernel: Modules linked in: md_mod xor i2c_i801 i2c_core ahci e1000e mvsas libsas scst scsi_transport_sas
Jan 27 22:25:18 NAS kernel: Pid: 15824, comm: hdparm Not tainted 2.6.32.9-unRAID #8
Jan 27 22:25:18 NAS kernel: Call Trace:
Jan 27 22:25:18 NAS kernel:  [<c102449e>] warn_slowpath_common+0x60/0x77
Jan 27 22:25:18 NAS kernel:  [<c10244c2>] warn_slowpath_null+0xd/0x10
Jan 27 22:25:18 NAS kernel:  [<c11b624d>] ata_qc_issue+0x10b/0x308
Jan 27 22:25:18 NAS kernel:  [<c11ba260>] ata_scsi_translate+0xd1/0xff
Jan 27 22:25:18 NAS kernel:  [<c11a816c>] ? scsi_done+0x0/0xd
Jan 27 22:25:18 NAS kernel:  [<c11a816c>] ? scsi_done+0x0/0xd
Jan 27 22:25:18 NAS kernel:  [<c11baa40>] ata_sas_queuecmd+0x120/0x1d7
Jan 27 22:25:18 NAS kernel:  [<c11bc6df>] ? ata_scsi_pass_thru+0x0/0x21d
Jan 27 22:25:18 NAS kernel:  [<f842f69a>] sas_queuecommand+0x65/0x20d [libsas]
Jan 27 22:25:18 NAS kernel:  [<c11a816c>] ? scsi_done+0x0/0xd
Jan 27 22:25:18 NAS kernel:  [<c11a82c0>] scsi_dispatch_cmd+0x147/0x181
Jan 27 22:25:18 NAS kernel:  [<c11ace4d>] scsi_request_fn+0x351/0x376
Jan 27 22:25:18 NAS kernel:  [<c1126798>] __blk_run_queue+0x78/0x10c
Jan 27 22:25:18 NAS kernel:  [<c1124446>] elv_insert+0x67/0x153
Jan 27 22:25:18 NAS kernel:  [<c11245b8>] __elv_add_request+0x86/0x8b
Jan 27 22:25:18 NAS kernel:  [<c1129343>] blk_execute_rq_nowait+0x4f/0x73
Jan 27 22:25:18 NAS kernel:  [<c11293dc>] blk_execute_rq+0x75/0x91
Jan 27 22:25:18 NAS kernel:  [<c11292cc>] ? blk_end_sync_rq+0x0/0x28
Jan 27 22:25:18 NAS kernel:  [<c112636f>] ? get_request+0x204/0x28d
Jan 27 22:25:18 NAS kernel:  [<c11269d6>] ? get_request_wait+0x2b/0xd9
Jan 27 22:25:18 NAS kernel:  [<c112c2bf>] sg_io+0x22d/0x30a
Jan 27 22:25:18 NAS kernel:  [<c112c5a8>] scsi_cmd_ioctl+0x20c/0x3bc
Jan 27 22:25:18 NAS kernel:  [<c11b3257>] sd_ioctl+0x6a/0x8c
Jan 27 22:25:18 NAS kernel:  [<c112a420>] __blkdev_driver_ioctl+0x50/0x62
Jan 27 22:25:18 NAS kernel:  [<c112ad1c>] blkdev_ioctl+0x8b0/0x8dc
Jan 27 22:25:18 NAS kernel:  [<c1131e2d>] ? kobject_get+0x12/0x17
Jan 27 22:25:18 NAS kernel:  [<c112b0f8>] ? get_disk+0x4a/0x61
Jan 27 22:25:18 NAS kernel:  [<c101b028>] ? kmap_atomic+0x14/0x16
Jan 27 22:25:18 NAS kernel:  [<c11334a5>] ? radix_tree_lookup_slot+0xd/0xf
Jan 27 22:25:18 NAS kernel:  [<c104a179>] ? filemap_fault+0xb8/0x305
Jan 27 22:25:18 NAS kernel:  [<c1048c43>] ? unlock_page+0x18/0x1b
Jan 27 22:25:18 NAS kernel:  [<c1057c63>] ? __do_fault+0x3a7/0x3da
Jan 27 22:25:18 NAS kernel:  [<c105985f>] ? handle_mm_fault+0x42d/0x8f1
Jan 27 22:25:18 NAS kernel:  [<c108b6c6>] block_ioctl+0x2a/0x32
Jan 27 22:25:18 NAS kernel:  [<c108b69c>] ? block_ioctl+0x0/0x32
Jan 27 22:25:18 NAS kernel:  [<c10769d5>] vfs_ioctl+0x22/0x67
Jan 27 22:25:18 NAS kernel:  [<c1076f33>] do_vfs_ioctl+0x478/0x4ac
Jan 27 22:25:18 NAS kernel:  [<c105dcdd>] ? do_mmap_pgoff+0x232/0x294
Jan 27 22:25:18 NAS kernel:  [<c1076f93>] sys_ioctl+0x2c/0x45
Jan 27 22:25:18 NAS kernel:  [<c1002935>] syscall_call+0x7/0xb
Jan 27 22:25:18 NAS kernel: ---[ end trace 7b27dc1e470a781b ]---

syslog-2011-01-27.zip