opentoe Posted February 5, 2011 Share Posted February 5, 2011 My unRAID is up and running and I'm currently running a pre-clear on a new drive I will be using. These errors look cryptic to me. Anyone know what they are? Feb 4 23:25:52 sun kernel: Pid: 3621, comm: hdparm Not tainted 2.6.32.9-unRAID #8 (Errors) Feb 4 23:25:52 sun kernel: Call Trace: (Errors) Feb 4 23:25:52 sun kernel: [<c102449e>] warn_slowpath_common+0x60/0x77 (Errors) Feb 4 23:25:52 sun kernel: [<c10244c2>] warn_slowpath_null+0xd/0x10 (Errors) Feb 4 23:25:52 sun kernel: [<c11b624d>] ata_qc_issue+0x10b/0x308 (Errors) Feb 4 23:25:52 sun kernel: [<c11ba260>] ata_scsi_translate+0xd1/0xff (Errors) Feb 4 23:25:52 sun kernel: [<c11a816c>] ? scsi_done+0x0/0xd (Errors) Feb 4 23:25:52 sun kernel: [<c11a816c>] ? scsi_done+0x0/0xd (Errors) Feb 4 23:25:52 sun kernel: [<c11baa40>] ata_sas_queuecmd+0x120/0x1d7 (Errors) Feb 4 23:25:52 sun kernel: [<c11bc6df>] ? ata_scsi_pass_thru+0x0/0x21d (Errors) Feb 4 23:25:52 sun kernel: [<f843369a>] sas_queuecommand+0x65/0x20d [libsas] (Errors) Feb 4 23:25:52 sun kernel: [<c11a816c>] ? scsi_done+0x0/0xd (Errors) Feb 4 23:25:52 sun kernel: [<c11a82c0>] scsi_dispatch_cmd+0x147/0x181 (Errors) Feb 4 23:25:52 sun kernel: [<c11ace4d>] scsi_request_fn+0x351/0x376 (Errors) Feb 4 23:25:52 sun kernel: [<c1126798>] __blk_run_queue+0x78/0x10c (Errors) Feb 4 23:25:52 sun kernel: [<c1124446>] elv_insert+0x67/0x153 (Errors) Feb 4 23:25:52 sun kernel: [<c11245b8>] __elv_add_request+0x86/0x8b (Errors) Feb 4 23:25:52 sun kernel: [<c1129343>] blk_execute_rq_nowait+0x4f/0x73 (Errors) Feb 4 23:25:52 sun kernel: [<c11293dc>] blk_execute_rq+0x75/0x91 (Errors) Feb 4 23:25:52 sun kernel: [<c11292cc>] ? blk_end_sync_rq+0x0/0x28 (Errors) Feb 4 23:25:52 sun kernel: [<c112636f>] ? get_request+0x204/0x28d (Errors) Feb 4 23:25:52 sun kernel: [<c11269d6>] ? get_request_wait+0x2b/0xd9 (Errors) Feb 4 23:25:52 sun kernel: [<c112c2bf>] sg_io+0x22d/0x30a (Errors) Feb 4 23:25:52 sun kernel: [<c112c5a8>] scsi_cmd_ioctl+0x20c/0x3bc (Errors) Feb 4 23:25:52 sun kernel: [<c11b3257>] sd_ioctl+0x6a/0x8c (Errors) Feb 4 23:25:52 sun kernel: [<c112a420>] __blkdev_driver_ioctl+0x50/0x62 (Errors) Feb 4 23:25:52 sun kernel: [<c112ad1c>] blkdev_ioctl+0x8b0/0x8dc (Errors) Feb 4 23:25:52 sun kernel: [<c1131e2d>] ? kobject_get+0x12/0x17 (Errors) Feb 4 23:25:52 sun kernel: [<c112b0f8>] ? get_disk+0x4a/0x61 (Errors) Feb 4 23:25:52 sun kernel: [<c101b028>] ? kmap_atomic+0x14/0x16 (Errors) Feb 4 23:25:52 sun kernel: [<c11334a5>] ? radix_tree_lookup_slot+0xd/0xf (Errors) Feb 4 23:25:52 sun kernel: [<c104a179>] ? filemap_fault+0xb8/0x305 (Errors) Feb 4 23:25:52 sun kernel: [<c1048c43>] ? unlock_page+0x18/0x1b (Errors) Feb 4 23:25:52 sun kernel: [<c1057c63>] ? __do_fault+0x3a7/0x3da (Errors) Feb 4 23:25:52 sun kernel: [<c105985f>] ? handle_mm_fault+0x42d/0x8f1 (Errors) Feb 4 23:25:52 sun kernel: [<c108b6c6>] block_ioctl+0x2a/0x32 (Errors) Feb 4 23:25:52 sun kernel: [<c108b69c>] ? block_ioctl+0x0/0x32 (Errors) Feb 4 23:25:52 sun kernel: [<c10769d5>] vfs_ioctl+0x22/0x67 (Errors) Feb 4 23:25:52 sun kernel: [<c1076f33>] do_vfs_ioctl+0x478/0x4ac (Errors) Feb 4 23:25:52 sun kernel: [<c105dcdd>] ? do_mmap_pgoff+0x232/0x294 (Errors) Feb 4 23:25:52 sun kernel: [<c1076f93>] sys_ioctl+0x2c/0x45 (Errors) Feb 4 23:25:52 sun kernel: [<c1002935>] syscall_call+0x7/0xb (Errors) Quote Link to comment
RobJ Posted February 5, 2011 Share Posted February 5, 2011 Did a little searching, and this is the fourth case of this, summarized below: (2 included the preceding messages, 2 did not) -poster--forum post--version--hdparm tainted?--ata_qc_issue warning?--mvsas/scst? opentoe here ?? No ?? ?? Lou here 4.7 Yes ?? ?? Simon here 4.7 No Yes Yes betaman here 4.7 No Yes Yes The actual Call Trace appears to be essentially the same. While I shouldn't speculate, I would not be surprised if it was in some way related to the immaturity of the mvsas & scst modules. If Lou or opentoe can provide more info, I'll update the table, might be helpful to Tom. Quote Link to comment
opentoe Posted February 5, 2011 Author Share Posted February 5, 2011 I only noticed these errors after I installed my Addon PCI-E card. I want to reboot my system, but I'm still doing a pre-clear on a new drive I installed. After I reboot I'll see if these particular errors come back. They can't be good, right? Quote Link to comment
opentoe Posted February 5, 2011 Author Share Posted February 5, 2011 I haven't shut my machine off or reboot. Here is my entire syslog from where those errors appear. syslog-2011-02-05.txt Quote Link to comment
opentoe Posted February 6, 2011 Author Share Posted February 6, 2011 Well, after I added my new drive to the array these weird errors stopped. Tom should still look into them I guess. Quote Link to comment
howardis Posted February 9, 2011 Share Posted February 9, 2011 I have the same errors. I shutdown the server. Added a AOC-SASLP-MV8 and a 2TB ears drive (jumpered). Started the server. Stopped the drives. executed the pre-clear. The restarted the drives. Found the error in the attached syslog. Not to hijack the thread but I also have a gigabyte board. To the best of my sleuthing I have no HPA issue, but can someone confirm? Thanks! syslog-2011-02-08.txt Quote Link to comment
joshpond Posted February 18, 2011 Share Posted February 18, 2011 Hi RobJ, I think you can add me to the list. http://lime-technology.com/forum/index.php?topic=10986.0 Looks the same in the syslog. Haven't had any issues since but that was trying to preclear a hdd on the supermicro SASLP MV8 card. I precleared the drive on a mobo slot and then moved it back to the SAS and no problems. the SAS card has been running for a while with other hdds on it. thanks Josh Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.