May 18, 201016 yr I recently picked up three Samsung HD203WI 2TB drives. Getting them working correctly with a AOC-SASLP-MV8 controller was not without issues. Ultimately they are working fine. Maybe this will help someone else to understand any odditites they might run into. All drives were first run through a standalone, multi pattern, multi pass wipe and verify operation so when they were first add to the unRAID box they had already been through a couple of days of operation and were completely erased to zeros. I first connected a drive to the MV8 and used unMenu to check it out. Here is what I got. (During all this the array was stopped) First time I clicked "Disk Management": <-------------- May 17 18:29:56 Cyclops kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 May 17 18:29:56 Cyclops kernel: ata1: status=0x51 { DriveReady SeekComplete Error } May 17 18:29:56 Cyclops kernel: ata1: error=0x04 { DriveStatusError } May 17 18:29:56 Cyclops kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 May 17 18:29:56 Cyclops kernel: ata1: status=0x51 { DriveReady SeekComplete Error } May 17 18:29:56 Cyclops kernel: ata1: error=0x04 { DriveStatusError } May 17 18:29:56 Cyclops kernel: ------------[ cut here ]------------ May 17 18:29:56 Cyclops kernel: WARNING: at drivers/ata/libata-core.c:5186 ata_qc_issue+0x10b/0x308() May 17 18:29:56 Cyclops kernel: Hardware name: To Be Filled By O.E.M. May 17 18:29:56 Cyclops kernel: Modules linked in: md_mod xor atiixp ahci r8169 mvsas libsas scst scsi_transport_sas May 17 18:29:56 Cyclops kernel: Pid: 2424, comm: smartctl Tainted: G W 2.6.32.9-unRAID #1 May 17 18:29:56 Cyclops kernel: Call Trace: May 17 18:29:56 Cyclops kernel: [] warn_slowpath_common+0x60/0x77 May 17 18:29:56 Cyclops kernel: [] warn_slowpath_null+0xd/0x10 May 17 18:29:56 Cyclops kernel: [] ata_qc_issue+0x10b/0x308 May 17 18:29:56 Cyclops kernel: [] ata_scsi_translate+0xd1/0xff May 17 18:29:56 Cyclops kernel: [] ? scsi_done+0x0/0xd May 17 18:29:56 Cyclops kernel: [] ? scsi_done+0x0/0xd May 17 18:29:56 Cyclops kernel: [] ata_sas_queuecmd+0x120/0x1d7 May 17 18:29:56 Cyclops kernel: [] ? ata_scsi_pass_thru+0x0/0x21d May 17 18:29:56 Cyclops kernel: [] sas_queuecommand+0x65/0x20d [libsas] May 17 18:29:56 Cyclops kernel: [] ? scsi_done+0x0/0xd May 17 18:29:56 Cyclops kernel: [] scsi_dispatch_cmd+0x147/0x181 May 17 18:29:56 Cyclops kernel: [] scsi_request_fn+0x351/0x376 May 17 18:29:56 Cyclops kernel: [] __generic_unplug_device+0x26/0x29 May 17 18:29:56 Cyclops kernel: [] blk_execute_rq_nowait+0x56/0x73 May 17 18:29:56 Cyclops kernel: [] blk_execute_rq+0x75/0x91 May 17 18:29:56 Cyclops kernel: [] ? blk_end_sync_rq+0x0/0x28 May 17 18:29:56 Cyclops kernel: [] ? get_request+0x204/0x28d May 17 18:29:56 Cyclops kernel: [] ? get_request_wait+0x2b/0xd9 May 17 18:29:56 Cyclops kernel: [] ? __blk_put_request+0x8c/0x92 May 17 18:29:56 Cyclops kernel: [] scsi_execute+0xbf/0x113 May 17 18:29:56 Cyclops kernel: [] ata_task_ioctl+0xb4/0x165 May 17 18:29:56 Cyclops kernel: [] ata_sas_scsi_ioctl+0x1d5/0x1e8 May 17 18:29:56 Cyclops kernel: [] ? sched_clock_local+0x11/0x135 May 17 18:29:56 Cyclops kernel: [] sas_ioctl+0x36/0x43 [libsas] May 17 18:29:56 Cyclops kernel: [] scsi_ioctl+0x299/0x2ad May 17 18:29:56 Cyclops kernel: [] ? sas_ioctl+0x0/0x43 [libsas] May 17 18:29:56 Cyclops kernel: [] sd_ioctl+0x80/0x8c May 17 18:29:56 Cyclops kernel: [] __blkdev_driver_ioctl+0x50/0x62 May 17 18:29:56 Cyclops kernel: [] blkdev_ioctl+0x8b0/0x8dc May 17 18:29:56 Cyclops kernel: [] ? kobject_get+0x12/0x17 May 17 18:29:56 Cyclops kernel: [] ? get_disk+0x4a/0x61 May 17 18:29:56 Cyclops kernel: [] ? kmap_atomic+0x14/0x16 May 17 18:29:56 Cyclops kernel: [] ? radix_tree_lookup_slot+0xd/0xf May 17 18:29:56 Cyclops kernel: [] ? filemap_fault+0xb8/0x305 May 17 18:29:56 Cyclops kernel: [] ? unlock_page+0x18/0x1b May 17 18:29:56 Cyclops kernel: [] ? __do_fault+0x3a7/0x3da May 17 18:29:56 Cyclops kernel: [] ? handle_mm_fault+0x42d/0x8f1 May 17 18:29:56 Cyclops kernel: [] block_ioctl+0x2a/0x32 May 17 18:29:56 Cyclops kernel: [] ? block_ioctl+0x0/0x32 May 17 18:29:56 Cyclops kernel: [] vfs_ioctl+0x22/0x67 May 17 18:29:56 Cyclops kernel: [] do_vfs_ioctl+0x478/0x4ac May 17 18:29:56 Cyclops kernel: [] ? expand_downwards+0x109/0x136 May 17 18:29:56 Cyclops kernel: [] sys_ioctl+0x2c/0x45 May 17 18:29:56 Cyclops kernel: [] syscall_call+0x7/0xb May 17 18:29:56 Cyclops kernel: ---[ end trace 170bf42208302810 ]--- May 17 18:29:56 Cyclops ata_id[2445]: HDIO_GET_IDENTITY failed for '/dev/block/8:32' Everytime I clicked "Disk Management" after the first time: <------- May 17 18:31:39 Cyclops kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 May 17 18:31:39 Cyclops kernel: ata1: status=0x51 { DriveReady SeekComplete Error } May 17 18:31:39 Cyclops kernel: ata1: error=0x04 { DriveStatusError } May 17 18:31:39 Cyclops kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 May 17 18:31:39 Cyclops kernel: ata1: status=0x51 { DriveReady SeekComplete Error } May 17 18:31:39 Cyclops kernel: ata1: error=0x04 { DriveStatusError } May 17 18:31:39 Cyclops ata_id[2643]: HDIO_GET_IDENTITY failed for '/dev/block/8:32' Every time I clicked "Smart Status" for the drive: <---------- SMART status Info for /dev/sdb smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: SAMSUNG HD203WI Serial Number: S1UYJ1KZ402329 Firmware Version: 1AN10002 User Capacity: 2,000,398,934,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Not recognized. Minor revision code: 0x28 Local Time is: Mon May 17 18:33:16 2010 GMT+5 ==> WARNING: May need -F samsung or -F samsung2 enabled; see manual for details. SMART support is: Available - device has SMART capability. SMART support is: Disabled SMART Disabled. Use option -s with argument 'on' to enable it. When running preclear on the drive: <------------- May 17 18:40:19 Cyclops kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 May 17 18:40:19 Cyclops kernel: ata1: status=0x51 { DriveReady SeekComplete Error } May 17 18:40:19 Cyclops kernel: ata1: error=0x04 { DriveStatusError } May 17 18:40:19 Cyclops kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 May 17 18:40:19 Cyclops kernel: ata1: status=0x51 { DriveReady SeekComplete Error } May 17 18:40:19 Cyclops kernel: ata1: error=0x04 { DriveStatusError } May 17 18:40:19 Cyclops kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 May 17 18:40:19 Cyclops kernel: ata1: status=0x51 { DriveReady SeekComplete Error } May 17 18:40:19 Cyclops kernel: ata1: error=0x04 { DriveStatusError } May 17 18:40:19 Cyclops kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 May 17 18:40:19 Cyclops kernel: ata1: status=0x51 { DriveReady SeekComplete Error } May 17 18:40:19 Cyclops kernel: ata1: error=0x04 { DriveStatusError } May 17 18:40:19 Cyclops kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 May 17 18:40:19 Cyclops kernel: ata1: status=0x51 { DriveReady SeekComplete Error } May 17 18:40:19 Cyclops kernel: ata1: error=0x04 { DriveStatusError } May 17 18:40:19 Cyclops kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 May 17 18:40:19 Cyclops kernel: ata1: status=0x51 { DriveReady SeekComplete Error } May 17 18:40:19 Cyclops kernel: ata1: error=0x04 { DriveStatusError } The above set of messages were displayed every time the preclear Telnet status screen was updated. This went on through the entire pre read and post read. No messages while writing zeros. Even though one drive would exibit all these issues a second HD203WI, that had already been "fixed" was connected to another port of the MV8 and it was working perfectly at exactly the same time. I had these same problems with every new 2TB drive until they were "fixed". From then on all was good. So what did it take to "fix" (very bad word, it has more to do with configuration than fixing) the drive? It seems all that was really necessary is to follow the advice of SMART status display and enable SMART using command: smartctl -s on /dev/sdb (if you issue this command be sure to use your device ID) The really interresting thing is there seems to be something that does this automatically in certain situations. Before I figured this out I had moved on of the drives from an MV8 port to a mobo port, clicked the Smart Status button and to my surprise a full SMART status was displayed. Moved the drive back to a MV8 port and all the problems were gawn. On another drive I issued the smartctl command to enable SMART reporting without ever moving the drive and that fixed the probelms too. So there must be something that comes into play when running a SmartStatus from a mobo port connected drive that stays sitting on the sideline while the drive is connected to the MV8.
May 18, 201016 yr Actually, the preclear_disk.sh script has this code for getting the starting "smart" report get_start_smart() { # just in case, enable SMART monitoring smartctl -s on $1 >/dev/null 2>&1 smartctl -d ata -a $1 2>&1 | egrep -v "Power_On_Minutes|Temperature_Celsius" >/tmp/smart_start$$ cat /tmp/smart_start$$ | logger -tpreclear_disk-start -plocal7.info -i } It might have been you using the pre-clear script that "fixed" the drives.
May 18, 201016 yr Author Unfortunately the syslog I saved after letting the preclear run through the full script had so many error messages in it that it had wrapped. Here is what came out at the end of the preclear. May 15 23:53:51 Cyclops kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 May 15 23:53:51 Cyclops kernel: ata1: status=0x51 { DriveReady SeekComplete Error } May 15 23:53:51 Cyclops kernel: ata1: error=0x04 { DriveStatusError } May 15 23:53:51 Cyclops preclear_disk-finish[12377]: smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen May 15 23:53:51 Cyclops preclear_disk-finish[12377]: Home page is http://smartmontools.sourceforge.net/ May 15 23:53:51 Cyclops preclear_disk-finish[12377]: May 15 23:53:51 Cyclops preclear_disk-finish[12377]: Smartctl: Device Read Identity Failed (not an ATA/ATAPI device) May 15 23:53:51 Cyclops preclear_disk-finish[12377]: May 15 23:53:51 Cyclops preclear_disk-finish[12377]: A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. May 15 23:53:51 Cyclops kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 May 15 23:53:51 Cyclops kernel: ata1: status=0x51 { DriveReady SeekComplete Error } May 15 23:53:51 Cyclops kernel: ata1: error=0x04 { DriveStatusError } May 15 23:53:51 Cyclops preclear_disk-diff[12390]: ============================================================================ May 15 23:53:51 Cyclops preclear_disk-diff[12390]: == May 15 23:53:51 Cyclops preclear_disk-diff[12390]: == Disk /dev/sdb has been successfully precleared May 15 23:53:51 Cyclops preclear_disk-diff[12390]: == May 15 23:53:51 Cyclops preclear_disk-diff[12390]: == Ran 1 preclear-disk cycle May 15 23:53:51 Cyclops preclear_disk-diff[12390]: == May 15 23:53:51 Cyclops preclear_disk-diff[12390]: == Using :Read block size = 8225280 Bytes May 15 23:53:51 Cyclops preclear_disk-diff[12390]: == Last Cycle's Pre Read Time : 7:28:13 (74 MB/s) May 15 23:53:51 Cyclops preclear_disk-diff[12390]: == Last Cycle's Zeroing time : 6:41:36 (83 MB/s) May 15 23:53:51 Cyclops preclear_disk-diff[12390]: == Last Cycle's Post Read Time : 15:01:32 (36 MB/s) May 15 23:53:51 Cyclops preclear_disk-diff[12390]: == Last Cycle's Total Time : 29:12:25 May 15 23:53:51 Cyclops preclear_disk-diff[12390]: == May 15 23:53:51 Cyclops preclear_disk-diff[12390]: == Total Elapsed Time 29:12:25 May 15 23:53:51 Cyclops preclear_disk-diff[12390]: == May 15 23:53:51 Cyclops preclear_disk-diff[12390]: == May 15 23:53:51 Cyclops preclear_disk-diff[12390]: ============================================================================ May 15 23:53:51 Cyclops preclear_disk-diff[12390]: S.M.A.R.T. error count differences detected after pre-clear May 15 23:53:51 Cyclops preclear_disk-diff[12390]: note, some 'raw' values may change, but not be an indication of a problem May 15 23:53:51 Cyclops preclear_disk-diff[12390]: 4,11c4 May 15 23:53:51 Cyclops preclear_disk-diff[12390]: < === START OF INFORMATION SECTION === May 15 23:53:51 Cyclops preclear_disk-diff[12390]: < Device Model: SAMSUNG HD203WI May 15 23:53:51 Cyclops preclear_disk-diff[12390]: < Serial Number: S1UYJ1KZ402327 May 15 23:53:51 Cyclops preclear_disk-diff[12390]: < Firmware Version: 1AN10002 May 15 23:53:51 Cyclops preclear_disk-diff[12390]: < User Capacity: 2,000,398,934,016 bytes May 15 23:53:51 Cyclops preclear_disk-diff[12390]: < Device is: In smartctl database [for details use: -P show] May 15 23:53:51 Cyclops preclear_disk-diff[12390]: < ATA Version is: 8 May 15 23:53:51 Cyclops preclear_disk-diff[12390]: < ATA Standard is: Not recognized. Minor revision code: 0x28 May 15 23:53:51 Cyclops preclear_disk-diff[12390]: --- May 15 23:53:51 Cyclops preclear_disk-diff[12390]: > Smartctl: Device Read Identity Failed (not an ATA/ATAPI device) May 15 23:53:51 Cyclops preclear_disk-diff[12390]: 13,18c6 May 15 23:53:51 Cyclops preclear_disk-diff[12390]: < ==> WARNING: May need -F samsung or -F samsung2 enabled; see manual for details. May 15 23:53:51 Cyclops preclear_disk-diff[12390]: < May 15 23:53:51 Cyclops preclear_disk-diff[12390]: < SMART support is: Available - device has SMART capability. May 15 23:53:51 Cyclops preclear_disk-diff[12390]: < SMART support is: Disabled May 15 23:53:51 Cyclops preclear_disk-diff[12390]: < May 15 23:53:51 Cyclops preclear_disk-diff[12390]: < SMART Disabled. Use option -s with argument 'on' to enable it. May 15 23:53:51 Cyclops preclear_disk-diff[12390]: --- May 15 23:53:51 Cyclops preclear_disk-diff[12390]: > A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. May 15 23:53:51 Cyclops preclear_disk-diff[12390]: ============================================================================ May 15 23:53:51 Cyclops preclear_disk-diff[12390]:
May 18, 201016 yr I gave up on the batch of these drives I bought and sent them back. AOC-SASLP-MV8 x 2 here. There is definately something going on with the sammy 2TB and either the AOC-SASLP-MV8 or unraid.. or some combination. Shame because I really like the Sammy drives.
May 19, 201016 yr I had similar issues with this drive and the AOC-SASLP-MV8 but managed to solve it by removing my Adatec 1210SA card. http://lime-technology.com/forum/index.php?topic=6191.0 What other cards have you got in the machine. Do you see a correct bios init for the card when booting up?
June 10, 201016 yr Hmm I just got one of these drives and it seems fine in my system. Have it hanging off the AOC-SASLP-MV8.
November 13, 201015 yr bit of a bump... I've just put one of these disks onto a saslp-mv8 too and it's working ok. I did see the same issues as the OP, but once the drive was pre cleared and added to the array everything was fine. During the preclear I manually enabled the smart monitoring on the drive (it was off by default) and still couldn't get anything back until the preclear had finished. Once the preclear was finished, but before adding to the array, the smart status would finally return some info. However unmenu's main page was unable to report it's temperature. The mymain page in umenu could. Once fully added to the array, everything was fine. So a bit weird, but it is working ok.
December 7, 201015 yr Just noticed this error on a newly built system with a AOC-SASLP-MV8. Not sure what to make of it. I currently have only one drive running off the MV8 and it's outside the array. Dec 6 18:52:56 Clara-Belle kernel: ------------[ cut here ]------------ Dec 6 18:52:56 Clara-Belle kernel: WARNING: at drivers/ata/libata-core.c:5186 ata_qc_issue+0x10b/0x308() Dec 6 18:52:56 Clara-Belle kernel: Hardware name: X8SIL Dec 6 18:52:56 Clara-Belle kernel: Modules linked in: md_mod xor i2c_i801 i2c_core ata_piix e1000e mvsas libsas scst scsi_transport_sas Dec 6 18:52:56 Clara-Belle kernel: Pid: 10026, comm: smartctl Not tainted 2.6.32.9-unRAID #8 Dec 6 18:52:56 Clara-Belle kernel: Call Trace: Dec 6 18:52:56 Clara-Belle kernel: [] warn_slowpath_common+0x60/0x77 Dec 6 18:52:56 Clara-Belle kernel: [] warn_slowpath_null+0xd/0x10 Dec 6 18:52:56 Clara-Belle kernel: [] ata_qc_issue+0x10b/0x308 Dec 6 18:52:56 Clara-Belle kernel: [] ata_scsi_translate+0xd1/0xff Dec 6 18:52:56 Clara-Belle kernel: [] ? scsi_done+0x0/0xd Dec 6 18:52:56 Clara-Belle kernel: [] ? scsi_done+0x0/0xd Dec 6 18:52:56 Clara-Belle kernel: [] ata_sas_queuecmd+0x120/0x1d7 Dec 6 18:52:56 Clara-Belle kernel: [] ? ata_scsi_pass_thru+0x0/0x21d Dec 6 18:52:56 Clara-Belle kernel: [] sas_queuecommand+0x65/0x20d [libsas] Dec 6 18:52:56 Clara-Belle kernel: [] ? scsi_done+0x0/0xd Dec 6 18:52:56 Clara-Belle kernel: [] scsi_dispatch_cmd+0x147/0x181 Dec 6 18:52:56 Clara-Belle kernel: [] scsi_request_fn+0x351/0x376 Dec 6 18:52:56 Clara-Belle kernel: [] __generic_unplug_device+0x26/0x29 Dec 6 18:52:56 Clara-Belle kernel: [] blk_execute_rq_nowait+0x56/0x73 Dec 6 18:52:56 Clara-Belle kernel: [] blk_execute_rq+0x75/0x91 Dec 6 18:52:56 Clara-Belle kernel: [] ? blk_end_sync_rq+0x0/0x28 Dec 6 18:52:56 Clara-Belle kernel: [] ? get_request+0x204/0x28d Dec 6 18:52:56 Clara-Belle kernel: [] ? get_request_wait+0x2b/0xd9 Dec 6 18:52:56 Clara-Belle kernel: [] ? __blk_put_request+0x8c/0x92 Dec 6 18:52:56 Clara-Belle kernel: [] scsi_execute+0xbf/0x113 Dec 6 18:52:56 Clara-Belle kernel: [] ata_cmd_ioctl+0xf8/0x1ba Dec 6 18:52:56 Clara-Belle kernel: [] ata_sas_scsi_ioctl+0x1ae/0x1e8 Dec 6 18:52:56 Clara-Belle kernel: [] ? native_smp_send_reschedule+0x46/0x48 Dec 6 18:52:56 Clara-Belle kernel: [] ? resched_task+0x58/0x5b Dec 6 18:52:56 Clara-Belle kernel: [] sas_ioctl+0x36/0x43 [libsas] Dec 6 18:52:56 Clara-Belle kernel: [] scsi_ioctl+0x299/0x2ad Dec 6 18:52:56 Clara-Belle kernel: [] ? sas_ioctl+0x0/0x43 [libsas] Dec 6 18:52:56 Clara-Belle kernel: [] sd_ioctl+0x80/0x8c Dec 6 18:52:56 Clara-Belle kernel: [] __blkdev_driver_ioctl+0x50/0x62 Dec 6 18:52:56 Clara-Belle kernel: [] blkdev_ioctl+0x8b0/0x8dc Dec 6 18:52:56 Clara-Belle kernel: [] ? kmap_atomic+0x14/0x16 Dec 6 18:52:56 Clara-Belle kernel: [] ? radix_tree_lookup_slot+0xd/0xf Dec 6 18:52:56 Clara-Belle kernel: [] ? filemap_fault+0xb8/0x305 Dec 6 18:52:56 Clara-Belle kernel: [] ? unlock_page+0x18/0x1b Dec 6 18:52:56 Clara-Belle kernel: [] ? __do_fault+0x3a7/0x3da Dec 6 18:52:56 Clara-Belle kernel: [] ? handle_mm_fault+0x42d/0x8f1 Dec 6 18:52:56 Clara-Belle kernel: [] block_ioctl+0x2a/0x32 Dec 6 18:52:56 Clara-Belle kernel: [] ? block_ioctl+0x0/0x32 Dec 6 18:52:56 Clara-Belle kernel: [] vfs_ioctl+0x22/0x67 Dec 6 18:52:56 Clara-Belle kernel: [] do_vfs_ioctl+0x478/0x4ac Dec 6 18:52:56 Clara-Belle kernel: [] ? blk_done_softirq+0x4e/0x5c Dec 6 18:52:56 Clara-Belle kernel: [] ? __do_softirq+0xf0/0xf8 Dec 6 18:52:56 Clara-Belle kernel: [] sys_ioctl+0x2c/0x45 Dec 6 18:52:56 Clara-Belle kernel: [] syscall_call+0x7/0xb Dec 6 18:52:56 Clara-Belle kernel: ---[ end trace f10ff175798574c6 ]---
December 10, 201015 yr Which version of unRAID are you running? That would be 4.6. Driver related issue with mvsas I assume. Don't know the severity of this trace.
December 12, 201015 yr I just had the same show up, and I am running the AOC-SASLP-MV8. I have a lot of drives connected through. Dec 12 09:21:11 Tower kernel: ------------[ cut here ]------------ Dec 12 09:21:11 Tower kernel: WARNING: at drivers/ata/libata-core.c:5186 ata_qc_issue+0x10b/0x308() (Minor Issues) Dec 12 09:21:11 Tower kernel: Hardware name: GA-MA770-DS3P Dec 12 09:21:11 Tower kernel: Modules linked in: md_mod xor atiixp ahci r8169 sata_sil24 mvsas libsas scst scsi_transport_sas [last unloaded: xor] (Drive related) Dec 12 09:21:11 Tower kernel: Pid: 12499, comm: smartctl Tainted: G W 2.6.32.9-unRAID #8 (Errors) Dec 12 09:21:11 Tower kernel: Call Trace: (Errors) Dec 12 09:21:11 Tower kernel: [<c102449e>] warn_slowpath_common+0x60/0x77 (Errors) Dec 12 09:21:11 Tower kernel: [<c10244c2>] warn_slowpath_null+0xd/0x10 (Errors) Dec 12 09:21:11 Tower kernel: [<c11b624d>] ata_qc_issue+0x10b/0x308 (Errors) Dec 12 09:21:11 Tower kernel: [<c11ba260>] ata_scsi_translate+0xd1/0xff (Errors) Dec 12 09:21:11 Tower kernel: [<c11a816c>] ? scsi_done+0x0/0xd (Errors) Dec 12 09:21:11 Tower kernel: [<c11a816c>] ? scsi_done+0x0/0xd (Errors) Dec 12 09:21:11 Tower kernel: [<c11baa40>] ata_sas_queuecmd+0x120/0x1d7 (Errors) Dec 12 09:21:11 Tower kernel: [<c11bc6df>] ? ata_scsi_pass_thru+0x0/0x21d (Errors) Dec 12 09:21:11 Tower kernel: [<f841d69a>] sas_queuecommand+0x65/0x20d [libsas] (Errors) Dec 12 09:21:11 Tower kernel: [<c11a816c>] ? scsi_done+0x0/0xd (Errors) Dec 12 09:21:11 Tower kernel: [<c11a82c0>] scsi_dispatch_cmd+0x147/0x181 (Errors) Dec 12 09:21:11 Tower kernel: [<c11ace4d>] scsi_request_fn+0x351/0x376 (Errors) Dec 12 09:21:11 Tower kernel: [<c11269a8>] __generic_unplug_device+0x26/0x29 (Errors) Dec 12 09:21:11 Tower kernel: [<c112934a>] blk_execute_rq_nowait+0x56/0x73 (Errors) Dec 12 09:21:11 Tower kernel: [<c11293dc>] blk_execute_rq+0x75/0x91 (Errors) Dec 12 09:21:11 Tower kernel: [<c11292cc>] ? blk_end_sync_rq+0x0/0x28 (Errors) Dec 12 09:21:11 Tower kernel: [<c112636f>] ? get_request+0x204/0x28d (Errors) Dec 12 09:21:11 Tower kernel: [<c11269d6>] ? get_request_wait+0x2b/0xd9 (Errors) Dec 12 09:21:11 Tower kernel: [<c1125ce9>] ? __blk_put_request+0x8c/0x92 (Errors) Dec 12 09:21:11 Tower kernel: [<c11ac58a>] scsi_execute+0xbf/0x113 (Errors) Dec 12 09:21:11 Tower kernel: [<c11bb527>] ata_task_ioctl+0xb4/0x165 (Errors) Dec 12 09:21:11 Tower kernel: [<c11bb967>] ata_sas_scsi_ioctl+0x1d5/0x1e8 (Errors) Dec 12 09:21:11 Tower kernel: [<c11334a5>] ? radix_tree_lookup_slot+0xd/0xf (Errors) Dec 12 09:21:11 Tower kernel: [<f841d33d>] sas_ioctl+0x36/0x43 [libsas] (Errors) Dec 12 09:21:11 Tower kernel: [<c11a94c8>] scsi_ioctl+0x299/0x2ad (Errors) Dec 12 09:21:11 Tower kernel: [<f841d307>] ? sas_ioctl+0x0/0x43 [libsas] (Errors) Dec 12 09:21:11 Tower kernel: [<c104c98a>] ? get_page_from_freelist+0x70/0x344 (Errors) Dec 12 09:21:11 Tower kernel: [<c11b326d>] sd_ioctl+0x80/0x8c (Errors) Dec 12 09:21:11 Tower kernel: [<c112a420>] __blkdev_driver_ioctl+0x50/0x62 (Errors) Dec 12 09:21:11 Tower kernel: [<c112ad1c>] blkdev_ioctl+0x8b0/0x8dc (Errors) Dec 12 09:21:11 Tower kernel: [<c1131e2d>] ? kobject_get+0x12/0x17 (Errors) Dec 12 09:21:11 Tower kernel: [<c112b0f8>] ? get_disk+0x4a/0x61 (Errors) Dec 12 09:21:11 Tower kernel: [<c101b028>] ? kmap_atomic+0x14/0x16 (Errors) Dec 12 09:21:11 Tower kernel: [<c11334a5>] ? radix_tree_lookup_slot+0xd/0xf (Errors) Dec 12 09:21:11 Tower kernel: [<c104a179>] ? filemap_fault+0xb8/0x305 (Errors) Dec 12 09:21:11 Tower kernel: [<c1048c43>] ? unlock_page+0x18/0x1b (Errors) Dec 12 09:21:11 Tower kernel: [<c1057c63>] ? __do_fault+0x3a7/0x3da (Errors) Dec 12 09:21:11 Tower kernel: [<c105985f>] ? handle_mm_fault+0x42d/0x8f1 (Errors) Dec 12 09:21:11 Tower kernel: [<c108b6c6>] block_ioctl+0x2a/0x32 (Errors) Dec 12 09:21:11 Tower kernel: [<c108b69c>] ? block_ioctl+0x0/0x32 (Errors) Dec 12 09:21:11 Tower kernel: [<c10769d5>] vfs_ioctl+0x22/0x67 (Errors) Dec 12 09:21:11 Tower kernel: [<c1076f33>] do_vfs_ioctl+0x478/0x4ac (Errors) Dec 12 09:21:11 Tower kernel: [<c129f124>] ? schedule+0x691/0x72f (Errors) Dec 12 09:21:11 Tower kernel: [<c1076f93>] sys_ioctl+0x2c/0x45 (Errors) Dec 12 09:21:11 Tower kernel: [<c1002935>] syscall_call+0x7/0xb (Errors) Dec 12 09:21:11 Tower kernel: ---[ end trace 4eaa2a86a8e2da24 ]--- How serious is this? Everything seems to be working fine.
December 13, 201015 yr Author WARNING: at drivers/ata/libata-core.c:5186 ata_qc_issue+0x10b/0x308() I got this message and all the crud that followed it when one of my drives had the SMART function disabled. A SMART report would look something like this SMART support is: Available - device has SMART capability. SMART support is: Disabled SMART Disabled. Use option -s with argument 'on' to enable it. There are probably other reasons for that warning message but I don't know what they are.
Archived
This topic is now archived and is closed to further replies.