August 5, 201015 yr So I just built another unraid server. I have one up and going, and running like a champ. This one has a little bit different hardware in it. Motherboard - Asus P7P55D 4Gbs of Ram 750W Corsair Power Supply Intel i CPU 2 - Supermicro PCIe 8 Port SATA Cards 7 - 2TB WD Green Drives 3 - 1.5TB Segate Drives I am trying to set 1 of the 2tb's as the parity, and 1 of the 1.5tbs as the cache drive. Then all the others as regular drives. One time it locked up while assigning them. And all the other times, I would get them all assigned, and get the array started, but as soon as I clicked the format button it would lock up. No response at all. I have a monitor and keyboard hooked up, and it was locked too. Here is the pastebin... http://pastebin.com/tp9mDKYA Any Help would be Much appreciated....
August 5, 201015 yr Author I am thinking it doesn't like both of the Supermicro SATA cards, because when I take one out, it works.... But them both in, and back to the same problems.... Wierd, my other motherboard would use both of them in at the same time.... Any ideas?
August 5, 201015 yr I am thinking it doesn't like both of the Supermicro SATA cards, because when I take one out, it works.... But them both in, and back to the same problems.... Wierd, my other motherboard would use both of them in at the same time.... Any ideas? Have you taken turns as to which (single) SATA card you used to verify that both of them are functioning by themselves?
August 5, 201015 yr I am thinking it doesn't like both of the Supermicro SATA cards, because when I take one out, it works.... But them both in, and back to the same problems.... Wierd, my other motherboard would use both of them in at the same time.... Any ideas? Have you taken turns as to which (single) SATA card you used to verify that both of them are functioning by themselves? Several ideas... Check if there is a BIOS update for the MB... Try different slots on the MB for the cards, they may not like sharing the interrupts on that hardware. Try some of the "boot codes" as described in the wiki. Joe L.
August 5, 201015 yr Author Okay... so i updated the bios, that didn't change anything. There are only 2 PCI-E slots these cards will fit in, so can't really try different ones. I have tried both cards independently and they work fine by themselves. I have tried pretty much every "boot code" in the wiki, and still nothing. This is the error that comes up in the syslog right after it is loading the second card.... Aug 5 09:21:03 PAULMOVIES kernel: ------------[ cut here ]------------ Aug 5 09:21:03 PAULMOVIES kernel: WARNING: at fs/proc/generic.c:590 proc_register+0x11c/0x14b() Aug 5 09:21:03 PAULMOVIES kernel: Hardware name: System Product Name Aug 5 09:21:03 PAULMOVIES kernel: proc_dir_entry 'scsi_tgt/mvst_scst' already registered Aug 5 09:21:03 PAULMOVIES kernel: Modules linked in: mvsas(+) libsas scst scsi_transport_sas Aug 5 09:21:03 PAULMOVIES kernel: Pid: 939, comm: modprobe Not tainted 2.6.32.9-unRAID #5 Aug 5 09:21:03 PAULMOVIES kernel: Call Trace: Aug 5 09:21:03 PAULMOVIES kernel: [] warn_slowpath_common+0x60/0x77 Aug 5 09:21:03 PAULMOVIES kernel: [] warn_slowpath_fmt+0x24/0x27 Aug 5 09:21:03 PAULMOVIES kernel: [] proc_register+0x11c/0x14b Aug 5 09:21:03 PAULMOVIES kernel: [] proc_mkdir_mode+0x2f/0x43 Aug 5 09:21:03 PAULMOVIES kernel: [] proc_mkdir+0xf/0x11 Aug 5 09:21:03 PAULMOVIES kernel: [] scst_build_proc_target_dir_entries+0x55/0xdc [scst] Aug 5 09:21:03 PAULMOVIES kernel: [] __scst_register_target_template+0x16c/0x3af [scst] Aug 5 09:21:03 PAULMOVIES kernel: [] mvst_init+0x3b/0x5b [mvsas] Aug 5 09:21:03 PAULMOVIES kernel: [] mvs_pci_init+0xaa5/0xaf7 [mvsas] Aug 5 09:21:03 PAULMOVIES kernel: [] ? dma_generic_alloc_coherent+0x0/0xdb Aug 5 09:21:03 PAULMOVIES kernel: [] local_pci_probe+0xe/0x10 Aug 5 09:21:03 PAULMOVIES kernel: [] pci_device_probe+0x48/0x66 Aug 5 09:21:03 PAULMOVIES kernel: [] driver_probe_device+0x79/0xed Aug 5 09:21:03 PAULMOVIES kernel: [] __driver_attach+0x43/0x5f Aug 5 09:21:03 PAULMOVIES kernel: [] bus_for_each_dev+0x39/0x5a Aug 5 09:21:03 PAULMOVIES kernel: [] ? mvs_init+0x0/0x45 [mvsas] Aug 5 09:21:03 PAULMOVIES kernel: [] driver_attach+0x14/0x16 Aug 5 09:21:03 PAULMOVIES kernel: [] ? __driver_attach+0x0/0x5f Aug 5 09:21:03 PAULMOVIES kernel: [] bus_add_driver+0x9f/0x1c5 Aug 5 09:21:03 PAULMOVIES kernel: [] ? mvs_init+0x0/0x45 [mvsas] Aug 5 09:21:03 PAULMOVIES kernel: [] driver_register+0x7b/0xd7 Aug 5 09:21:03 PAULMOVIES kernel: [] ? mvs_init+0x0/0x45 [mvsas] Aug 5 09:21:03 PAULMOVIES kernel: [] __pci_register_driver+0x39/0x8c Aug 5 09:21:03 PAULMOVIES kernel: [] ? mvs_init+0x0/0x45 [mvsas] Aug 5 09:21:03 PAULMOVIES kernel: [] mvs_init+0x30/0x45 [mvsas] Aug 5 09:21:03 PAULMOVIES kernel: [] do_one_initcall+0x4c/0x131 Aug 5 09:21:03 PAULMOVIES kernel: [] sys_init_module+0xa7/0x1dd Aug 5 09:21:03 PAULMOVIES kernel: [] syscall_call+0x7/0xb Aug 5 09:21:03 PAULMOVIES kernel: ---[ end trace 9202c4bc4fc4bc48 ]--- Aug 5 09:21:03 PAULMOVIES kernel: [939]: scst: __scst_register_target_template:253:***ERROR***: Target driver mvst_scst already registered Aug 5 09:21:03 PAULMOVIES kernel: [939]: scst: __scst_register_target_template:293:***ERROR***: Failed to register target template mvst_scst That error is not there when just a single card is in.... When I go into the settings for those cards on bootup, it shows me that both cards have the same IRQ, could this be the problem? If so, I have no idea how to change it...
August 5, 201015 yr Aug 5 09:21:03 PAULMOVIES kernel: [939]: scst: __scst_register_target_template:253:***ERROR***: Target driver mvst_scst already registered Aug 5 09:21:03 PAULMOVIES kernel: [939]: scst: __scst_register_target_template:293:***ERROR***: Failed to register target template mvst_scst That error is not there when just a single card is in.... When I go into the settings for those cards on bootup, it shows me that both cards have the same IRQ, could this be the problem? If so, I have no idea how to change it... Yes, that definitely sounds like that is the issue, IRQ conflict. Which also explains why you do not have any problems when using just one or the other card alone. Someone more knowledgable than I would need to help about getting around the IRQ conflict. Think that might be a BIOS setting?
August 5, 201015 yr Author I think I have tried every bios setting there is. IRQ Sharing problems? That is somewhat funny, I thought IRQ sharing problems were from like 10-15 years ago..... Hopefully somone can help me solve it... I do notice that when it is booting up, it says IRQ sharing disabled..... is there a way to enable it, or does this not have anything to do with the problem....
August 5, 201015 yr Yes, you can enable it in BIOS. You need to examine all the options available. Make sure you have APIC enabled.
August 5, 201015 yr Author Okay so this is interesting... I figured it was that error... But I do believe I have narrowed it down to a faulty harddrive. I went back and looked at my other system, which has been up for about 20 days without a reboot, and it has that same error in it. Don't know how I missed it before, but that system has been stable for 20 days with no hiccups or lockups.... I have removed the harddrive in question, and it boots fine now with no lockups. So is that error anything to really worry about?
August 5, 201015 yr Okay so this is interesting... I figured it was that error... But I do believe I have narrowed it down to a faulty harddrive. I went back and looked at my other system, which has been up for about 20 days without a reboot, and it has that same error in it. Don't know how I missed it before, but that system has been stable for 20 days with no hiccups or lockups.... I have removed the harddrive in question, and it boots fine now with no lockups. So is that error anything to really worry about? In light of what you just described, no.
August 12, 201015 yr Just noticed this error in my syslog too. Parity check completes fine (drives on both Supermicro cards) so guessing its nothing to worry about.
Archived
This topic is now archived and is closed to further replies.