3doubled Posted February 23, 2011 Share Posted February 23, 2011 Hi, I just started a preclear and I received a string of errors in the syslog that I do not understand. The preclear is proceeding like normal, but the errors are worrisome still. I should probably add that I am replacing the GA-MA74GM-S2 motherboard (for HPA issues) as soon as this disk preclears (and I replace a sketchy disk) and I am confident my array is in "good condition". The new drive that I am preclearing is connected to my Supermicro SASLP-MV8. I did so without powering down or rebooting the server - perhaps that is the issue here. Any help would be appreciated. Running Unraid 4.7 and preclear 1.5. Hardware: AMD 5200+ GA-MA74GM-S2 2x2GB DDR2 800 Supermicro SASLP-MV8 PCI-e Syslog: Feb 23 11:49:45 Tower login[31717]: ROOT LOGIN on `pts/0' from `Office-PC' (Logins) Feb 23 11:50:19 Tower kernel: sdb: unknown partition table (Drive related) Feb 23 11:52:41 Tower kernel: sdb: unknown partition table (Drive related) Feb 23 11:53:42 Tower kernel: ------------[ cut here ]------------ Feb 23 11:53:42 Tower kernel: WARNING: at drivers/ata/libata-core.c:5186 ata_qc_issue+0x10b/0x308() (Minor Issues) Feb 23 11:53:42 Tower kernel: Hardware name: GA-MA74GM-S2 Feb 23 11:53:42 Tower kernel: Modules linked in: md_mod xor ide_gd_mod atiixp ahci r8169 mvsas libsas scst scsi_transport_sas (Drive related) Feb 23 11:53:42 Tower kernel: Pid: 5312, comm: hdparm Not tainted 2.6.32.9-unRAID #8 (Errors) Feb 23 11:53:42 Tower kernel: Call Trace: (Errors) Feb 23 11:53:42 Tower kernel: [<c102449e>] warn_slowpath_common+0x60/0x77 (Errors) Feb 23 11:53:42 Tower kernel: [<c10244c2>] warn_slowpath_null+0xd/0x10 (Errors) Feb 23 11:53:42 Tower kernel: [<c11b624d>] ata_qc_issue+0x10b/0x308 (Errors) Feb 23 11:53:42 Tower kernel: [<c11ba260>] ata_scsi_translate+0xd1/0xff (Errors) Feb 23 11:53:42 Tower kernel: [<c11a816c>] ? scsi_done+0x0/0xd (Errors) Feb 23 11:53:42 Tower kernel: [<c11a816c>] ? scsi_done+0x0/0xd (Errors) Feb 23 11:53:42 Tower kernel: [<c11baa40>] ata_sas_queuecmd+0x120/0x1d7 (Errors) Feb 23 11:53:42 Tower kernel: [<c11bc6df>] ? ata_scsi_pass_thru+0x0/0x21d (Errors) Feb 23 11:53:42 Tower kernel: [<f842569a>] sas_queuecommand+0x65/0x20d [libsas] (Errors) Feb 23 11:53:42 Tower kernel: [<c11a816c>] ? scsi_done+0x0/0xd (Errors) Feb 23 11:53:42 Tower kernel: [<c11a82c0>] scsi_dispatch_cmd+0x147/0x181 (Errors) Feb 23 11:53:42 Tower kernel: [<c11ace4d>] scsi_request_fn+0x351/0x376 (Errors) Feb 23 11:53:42 Tower kernel: [<c1126798>] __blk_run_queue+0x78/0x10c (Errors) Feb 23 11:53:42 Tower kernel: [<c1124446>] elv_insert+0x67/0x153 (Errors) Feb 23 11:53:42 Tower kernel: [<c11245b8>] __elv_add_request+0x86/0x8b (Errors) Feb 23 11:53:42 Tower kernel: [<c1129343>] blk_execute_rq_nowait+0x4f/0x73 (Errors) Feb 23 11:53:42 Tower kernel: [<c11293dc>] blk_execute_rq+0x75/0x91 (Errors) Feb 23 11:53:42 Tower kernel: [<c11292cc>] ? blk_end_sync_rq+0x0/0x28 (Errors) Feb 23 11:53:42 Tower kernel: [<c112636f>] ? get_request+0x204/0x28d (Errors) Feb 23 11:53:42 Tower kernel: [<c11269d6>] ? get_request_wait+0x2b/0xd9 (Errors) Feb 23 11:53:42 Tower kernel: [<c112c2bf>] sg_io+0x22d/0x30a (Errors) Feb 23 11:53:42 Tower kernel: [<c112c5a8>] scsi_cmd_ioctl+0x20c/0x3bc (Errors) Feb 23 11:53:42 Tower kernel: [<c11b3257>] sd_ioctl+0x6a/0x8c (Errors) Feb 23 11:53:42 Tower kernel: [<c112a420>] __blkdev_driver_ioctl+0x50/0x62 (Errors) Feb 23 11:53:42 Tower kernel: [<c112ad1c>] blkdev_ioctl+0x8b0/0x8dc (Errors) Feb 23 11:53:42 Tower kernel: [<c1131e2d>] ? kobject_get+0x12/0x17 (Errors) Feb 23 11:53:42 Tower kernel: [<c112b0f8>] ? get_disk+0x4a/0x61 (Errors) Feb 23 11:53:42 Tower kernel: [<c101b028>] ? kmap_atomic+0x14/0x16 (Errors) Feb 23 11:53:42 Tower kernel: [<c11334a5>] ? radix_tree_lookup_slot+0xd/0xf (Errors) Feb 23 11:53:42 Tower kernel: [<c104a179>] ? filemap_fault+0xb8/0x305 (Errors) Feb 23 11:53:42 Tower kernel: [<c1048c43>] ? unlock_page+0x18/0x1b (Errors) Feb 23 11:53:42 Tower kernel: [<c1057c63>] ? __do_fault+0x3a7/0x3da (Errors) Feb 23 11:53:42 Tower kernel: [<c105985f>] ? handle_mm_fault+0x42d/0x8f1 (Errors) Feb 23 11:53:42 Tower kernel: [<c108b6c6>] block_ioctl+0x2a/0x32 (Errors) Feb 23 11:53:42 Tower kernel: [<c108b69c>] ? block_ioctl+0x0/0x32 (Errors) Feb 23 11:53:42 Tower kernel: [<c10769d5>] vfs_ioctl+0x22/0x67 (Errors) Feb 23 11:53:42 Tower kernel: [<c1076f33>] do_vfs_ioctl+0x478/0x4ac (Errors) Feb 23 11:53:42 Tower kernel: [<c105dcdd>] ? do_mmap_pgoff+0x232/0x294 (Errors) Feb 23 11:53:42 Tower kernel: [<c1076f93>] sys_ioctl+0x2c/0x45 (Errors) Feb 23 11:53:42 Tower kernel: [<c1002935>] syscall_call+0x7/0xb (Errors) Feb 23 11:53:42 Tower kernel: ---[ end trace 8cf936d66b646943 ]--- Thanks Link to comment
dgaschk Posted February 23, 2011 Share Posted February 23, 2011 4.7 is not hot-swap capable. Restart and begin the pre-clear again. Those errors might cause your syslog to fill RAM and then -crash. Link to comment
3doubled Posted February 23, 2011 Author Share Posted February 23, 2011 Do I need to abort the preclear in any specific manner or will a powerdown/restart from the WebGUI be ok? Thanks Link to comment
Joe L. Posted February 23, 2011 Share Posted February 23, 2011 Do I need to abort the preclear in any specific manner or will a powerdown/restart from the WebGUI be ok? Thanks You can stop a preclear by typing Control-C (Holding the control key down and typingthe letter "c") Link to comment
3doubled Posted February 23, 2011 Author Share Posted February 23, 2011 Thanks Joe L. and dgaschk! Link to comment
3doubled Posted February 23, 2011 Author Share Posted February 23, 2011 So I aborted the preclear and restarted. Afterward I began the preclear and once again the errors occured: Feb 23 18:02:44 Tower login[5104]: ROOT LOGIN on `pts/0' from `Office-PC' (Logins) Feb 23 18:02:55 Tower kernel: sdb: unknown partition table (Drive related) Feb 23 18:03:24 Tower kernel: ------------[ cut here ]------------ Feb 23 18:03:24 Tower kernel: WARNING: at drivers/ata/libata-core.c:5186 ata_qc_issue+0x10b/0x308() (Minor Issues) Feb 23 18:03:24 Tower kernel: Hardware name: GA-MA74GM-S2 Feb 23 18:03:24 Tower kernel: Modules linked in: md_mod xor ide_gd_mod atiixp ahci r8169 mvsas libsas scst scsi_transport_sas (Drive related) Feb 23 18:03:24 Tower kernel: Pid: 5815, comm: hdparm Not tainted 2.6.32.9-unRAID #8 (Errors) Feb 23 18:03:24 Tower kernel: Call Trace: (Errors) Feb 23 18:03:24 Tower kernel: [<c102449e>] warn_slowpath_common+0x60/0x77 (Errors) Feb 23 18:03:24 Tower kernel: [<c10244c2>] warn_slowpath_null+0xd/0x10 (Errors) Feb 23 18:03:24 Tower kernel: [<c11b624d>] ata_qc_issue+0x10b/0x308 (Errors) Feb 23 18:03:24 Tower kernel: [<c11ba260>] ata_scsi_translate+0xd1/0xff (Errors) Feb 23 18:03:24 Tower kernel: [<c11a816c>] ? scsi_done+0x0/0xd (Errors) Feb 23 18:03:24 Tower kernel: [<c11a816c>] ? scsi_done+0x0/0xd (Errors) Feb 23 18:03:24 Tower kernel: [<c11baa40>] ata_sas_queuecmd+0x120/0x1d7 (Errors) Feb 23 18:03:24 Tower kernel: [<c11bc6df>] ? ata_scsi_pass_thru+0x0/0x21d (Errors) Feb 23 18:03:24 Tower kernel: [<f842569a>] sas_queuecommand+0x65/0x20d [libsas] (Errors) Feb 23 18:03:24 Tower kernel: [<c11a816c>] ? scsi_done+0x0/0xd (Errors) Feb 23 18:03:24 Tower kernel: [<c11a82c0>] scsi_dispatch_cmd+0x147/0x181 (Errors) Feb 23 18:03:24 Tower kernel: [<c11ace4d>] scsi_request_fn+0x351/0x376 (Errors) Feb 23 18:03:24 Tower kernel: [<c1126798>] __blk_run_queue+0x78/0x10c (Errors) Feb 23 18:03:24 Tower kernel: [<c1124446>] elv_insert+0x67/0x153 (Errors) Feb 23 18:03:24 Tower kernel: [<c11245b8>] __elv_add_request+0x86/0x8b (Errors) Feb 23 18:03:24 Tower kernel: [<c1129343>] blk_execute_rq_nowait+0x4f/0x73 (Errors) Feb 23 18:03:24 Tower kernel: [<c11293dc>] blk_execute_rq+0x75/0x91 (Errors) Feb 23 18:03:24 Tower kernel: [<c11292cc>] ? blk_end_sync_rq+0x0/0x28 (Errors) Feb 23 18:03:24 Tower kernel: [<c112636f>] ? get_request+0x204/0x28d (Errors) Feb 23 18:03:24 Tower kernel: [<c11269d6>] ? get_request_wait+0x2b/0xd9 (Errors) Feb 23 18:03:24 Tower kernel: [<c112c2bf>] sg_io+0x22d/0x30a (Errors) Feb 23 18:03:24 Tower kernel: [<c112c5a8>] scsi_cmd_ioctl+0x20c/0x3bc (Errors) Feb 23 18:03:24 Tower kernel: [<c11b3257>] sd_ioctl+0x6a/0x8c (Errors) Feb 23 18:03:24 Tower kernel: [<c112a420>] __blkdev_driver_ioctl+0x50/0x62 (Errors) Feb 23 18:03:24 Tower kernel: [<c112ad1c>] blkdev_ioctl+0x8b0/0x8dc (Errors) Feb 23 18:03:24 Tower kernel: [<c1131e2d>] ? kobject_get+0x12/0x17 (Errors) Feb 23 18:03:24 Tower kernel: [<c112b0f8>] ? get_disk+0x4a/0x61 (Errors) Feb 23 18:03:24 Tower kernel: [<c101b028>] ? kmap_atomic+0x14/0x16 (Errors) Feb 23 18:03:24 Tower kernel: [<c11334a5>] ? radix_tree_lookup_slot+0xd/0xf (Errors) Feb 23 18:03:24 Tower kernel: [<c104a179>] ? filemap_fault+0xb8/0x305 (Errors) Feb 23 18:03:24 Tower kernel: [<c1048c43>] ? unlock_page+0x18/0x1b (Errors) Feb 23 18:03:24 Tower kernel: [<c1057c63>] ? __do_fault+0x3a7/0x3da (Errors) Feb 23 18:03:24 Tower kernel: [<c105985f>] ? handle_mm_fault+0x42d/0x8f1 (Errors) Feb 23 18:03:24 Tower kernel: [<c108b6c6>] block_ioctl+0x2a/0x32 (Errors) Feb 23 18:03:24 Tower kernel: [<c108b69c>] ? block_ioctl+0x0/0x32 (Errors) Feb 23 18:03:24 Tower kernel: [<c10769d5>] vfs_ioctl+0x22/0x67 (Errors) Feb 23 18:03:24 Tower kernel: [<c1076f33>] do_vfs_ioctl+0x478/0x4ac (Errors) Feb 23 18:03:24 Tower kernel: [<c105dcdd>] ? do_mmap_pgoff+0x232/0x294 (Errors) Feb 23 18:03:24 Tower kernel: [<c1076f93>] sys_ioctl+0x2c/0x45 (Errors) Feb 23 18:03:24 Tower kernel: [<c1002935>] syscall_call+0x7/0xb (Errors) Feb 23 18:03:24 Tower kernel: ---[ end trace 52f77637a3a6440f ]--- Any idea what is going on? Thanks. Link to comment
Joe L. Posted February 23, 2011 Share Posted February 23, 2011 So I aborted the preclear and restarted. Afterward I began the preclear and once again the errors occured: Feb 23 18:02:44 Tower login[5104]: ROOT LOGIN on `pts/0' from `Office-PC' (Logins) Feb 23 18:02:55 Tower kernel: sdb: unknown partition table (Drive related) Feb 23 18:03:24 Tower kernel: ------------[ cut here ]------------ Feb 23 18:03:24 Tower kernel: WARNING: at drivers/ata/libata-core.c:5186 ata_qc_issue+0x10b/0x308() (Minor Issues) Feb 23 18:03:24 Tower kernel: Hardware name: GA-MA74GM-S2 Feb 23 18:03:24 Tower kernel: Modules linked in: md_mod xor ide_gd_mod atiixp ahci r8169 mvsas libsas scst scsi_transport_sas (Drive related) Feb 23 18:03:24 Tower kernel: Pid: 5815, comm: hdparm Not tainted 2.6.32.9-unRAID #8 (Errors) Feb 23 18:03:24 Tower kernel: Call Trace: (Errors) Feb 23 18:03:24 Tower kernel: [<c102449e>] warn_slowpath_common+0x60/0x77 (Errors) Feb 23 18:03:24 Tower kernel: [<c10244c2>] warn_slowpath_null+0xd/0x10 (Errors) Feb 23 18:03:24 Tower kernel: [<c11b624d>] ata_qc_issue+0x10b/0x308 (Errors) Feb 23 18:03:24 Tower kernel: [<c11ba260>] ata_scsi_translate+0xd1/0xff (Errors) Feb 23 18:03:24 Tower kernel: [<c11a816c>] ? scsi_done+0x0/0xd (Errors) Feb 23 18:03:24 Tower kernel: [<c11a816c>] ? scsi_done+0x0/0xd (Errors) Feb 23 18:03:24 Tower kernel: [<c11baa40>] ata_sas_queuecmd+0x120/0x1d7 (Errors) Feb 23 18:03:24 Tower kernel: [<c11bc6df>] ? ata_scsi_pass_thru+0x0/0x21d (Errors) Feb 23 18:03:24 Tower kernel: [<f842569a>] sas_queuecommand+0x65/0x20d [libsas] (Errors) Feb 23 18:03:24 Tower kernel: [<c11a816c>] ? scsi_done+0x0/0xd (Errors) Feb 23 18:03:24 Tower kernel: [<c11a82c0>] scsi_dispatch_cmd+0x147/0x181 (Errors) Feb 23 18:03:24 Tower kernel: [<c11ace4d>] scsi_request_fn+0x351/0x376 (Errors) Feb 23 18:03:24 Tower kernel: [<c1126798>] __blk_run_queue+0x78/0x10c (Errors) Feb 23 18:03:24 Tower kernel: [<c1124446>] elv_insert+0x67/0x153 (Errors) Feb 23 18:03:24 Tower kernel: [<c11245b8>] __elv_add_request+0x86/0x8b (Errors) Feb 23 18:03:24 Tower kernel: [<c1129343>] blk_execute_rq_nowait+0x4f/0x73 (Errors) Feb 23 18:03:24 Tower kernel: [<c11293dc>] blk_execute_rq+0x75/0x91 (Errors) Feb 23 18:03:24 Tower kernel: [<c11292cc>] ? blk_end_sync_rq+0x0/0x28 (Errors) Feb 23 18:03:24 Tower kernel: [<c112636f>] ? get_request+0x204/0x28d (Errors) Feb 23 18:03:24 Tower kernel: [<c11269d6>] ? get_request_wait+0x2b/0xd9 (Errors) Feb 23 18:03:24 Tower kernel: [<c112c2bf>] sg_io+0x22d/0x30a (Errors) Feb 23 18:03:24 Tower kernel: [<c112c5a8>] scsi_cmd_ioctl+0x20c/0x3bc (Errors) Feb 23 18:03:24 Tower kernel: [<c11b3257>] sd_ioctl+0x6a/0x8c (Errors) Feb 23 18:03:24 Tower kernel: [<c112a420>] __blkdev_driver_ioctl+0x50/0x62 (Errors) Feb 23 18:03:24 Tower kernel: [<c112ad1c>] blkdev_ioctl+0x8b0/0x8dc (Errors) Feb 23 18:03:24 Tower kernel: [<c1131e2d>] ? kobject_get+0x12/0x17 (Errors) Feb 23 18:03:24 Tower kernel: [<c112b0f8>] ? get_disk+0x4a/0x61 (Errors) Feb 23 18:03:24 Tower kernel: [<c101b028>] ? kmap_atomic+0x14/0x16 (Errors) Feb 23 18:03:24 Tower kernel: [<c11334a5>] ? radix_tree_lookup_slot+0xd/0xf (Errors) Feb 23 18:03:24 Tower kernel: [<c104a179>] ? filemap_fault+0xb8/0x305 (Errors) Feb 23 18:03:24 Tower kernel: [<c1048c43>] ? unlock_page+0x18/0x1b (Errors) Feb 23 18:03:24 Tower kernel: [<c1057c63>] ? __do_fault+0x3a7/0x3da (Errors) Feb 23 18:03:24 Tower kernel: [<c105985f>] ? handle_mm_fault+0x42d/0x8f1 (Errors) Feb 23 18:03:24 Tower kernel: [<c108b6c6>] block_ioctl+0x2a/0x32 (Errors) Feb 23 18:03:24 Tower kernel: [<c108b69c>] ? block_ioctl+0x0/0x32 (Errors) Feb 23 18:03:24 Tower kernel: [<c10769d5>] vfs_ioctl+0x22/0x67 (Errors) Feb 23 18:03:24 Tower kernel: [<c1076f33>] do_vfs_ioctl+0x478/0x4ac (Errors) Feb 23 18:03:24 Tower kernel: [<c105dcdd>] ? do_mmap_pgoff+0x232/0x294 (Errors) Feb 23 18:03:24 Tower kernel: [<c1076f93>] sys_ioctl+0x2c/0x45 (Errors) Feb 23 18:03:24 Tower kernel: [<c1002935>] syscall_call+0x7/0xb (Errors) Feb 23 18:03:24 Tower kernel: ---[ end trace 52f77637a3a6440f ]--- Any idea what is going on? Thanks. The kernel is attempting to interpret the MBR. It is not recognized. You might want to zero it specifically with preclear_disk.sh -z /dev/sdb Link to comment
3doubled Posted February 23, 2011 Author Share Posted February 23, 2011 I am currently in the process of preclearing the drive, so I guess it will be "zeroed" during the process. Thanks. Link to comment
bfeist Posted February 25, 2011 Share Posted February 25, 2011 Weird, I just got the same error in my syslog for the first time while trying to solve a different drive problem. We have the same motherboard. See here: http://lime-technology.com/forum/index.php?topic=11273.0 I just installed 4.7 this week. I'm going to go back to 4.6 to see if that helps. Link to comment
3doubled Posted February 25, 2011 Author Share Posted February 25, 2011 Interesting. I will keep an eye out for the same errors and I'll let you know if the above fix fails. After preclearing that disk I haven't seen the errors. Very shortly I will be replacing the motherboard as well. For me, I only found one disk with HPA and it was on my only IDE drive. I cleaned this drive two weeks ago since doing so my motherboard hasn't rewritten it (I've confirmed this by running hdparm -i -I). I've also confirmed all of my other drives are HPA free as of writing this post. The problem (or at least the error output) may be related to our Gigabyte board, but I think Joe L. was correct in that it is the MBR being invalid. Either way, you should look for an alternative motherboard and run "hdparm -i -I /dev/sdX" on all your drives and compare the "LBAsects" with the "LBA48 user addressable sectors". If they don't match, then you should clean those drives. Good luck. Link to comment
henris Posted February 25, 2013 Share Posted February 25, 2013 The kernel is attempting to interpret the MBR. It is not recognized. You might want to zero it specifically with preclear_disk.sh -z /dev/sdb Hit this very same problem when doing my first drive addition after upgrading to 4.7. I have MSI K9A2 Platinum mobo and was adding WD20EARX 2TB drive. All my previous drives have been Samsung 1, 1,5 and 2TB models. Once I saw this post, I cancelled the preclear, cleared the mbr with above command and restarted preclearing. There are no more errors reported so it seems to fix at least my problem. There are also other threads with similar situation. This (http://lime-technology.com/forum/index.php?topic=14946.0) one had a common nominator to my case, the AOC-SASLP-MVL8 sata card. Since I don't have any mobo connectors easily available I did not even try that road. Link to comment
3doubled Posted February 25, 2013 Author Share Posted February 25, 2013 Wow, I'm amazed how many times this thread has been read since it was solved! Unfortunately, it was a while ago and in fact I can hardly remember the problem I had (or much about the solution) other than what I've written there. I'm guessing it worked out OK! I think it was the MBR, which was fixed when I precleared the disk in question. Afterward I was able to rebuild the disk without any further problems. Otherwise, still trucking along with Unraid 5 and still have never lost any data [knock on wood] (but many, many drives - all while still under warranty thankfully). Anyway, glad the info here helped you fix your problem. Unfortunately, I can't remember if my troubled drive was on my AOC-SASLP-MVL8 card or my mobo, but it is very possible. Haven't had any problems from it since then.. especially when I got rid of that toxic, HPA spewing Gigabyte mobo. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.