June 3, 201115 yr Good day, First and foremost thank you for any help you can provide. Setting up a new unraid server for the first time. No hard drives in the bays only the "soon to be" parity drive. - I get the machine to boot to : root@Tower:~# - I have the ethernet cable connected to the middle Ethernet port on the SUPERMICRO MBD-X8SIL-F-O motherboard (eth0 right ?) - Gigabyte connection: Solid Amber Light on Right and Flashing amber on the left - Connected via CAT6 to 24 port Gigabyte Netgear Switch - http://tower - Takes me to Tower records - The machine appears under Windows 7 Network Neighborhood and I can see "an" IP 192.168.1.136. However this IP takes me to Supermicro web interface for controlling the machine remotely which works fine. - Tried "ifconfig" - nothing - Tried "ifconfig eth0" shows some info but does not show an IP address - Tried "ifconfig eth1" shows some info but does not show an IP address - Tried each of the following before rebooting: different flash drives, different Ethernet ports on the motherboard, different ethernet cables Specs unRAID Server version 4.7 AiO Machine spec is same "20 Drive Beast" except had to go with the Norco Case 3216 http://lime-technology.com/wiki/index.php?title=Hardware_Compatibility#Recommended_Builds Please find attached the syslog. I must be missing something simple...... Many thanks in advance, Wayne syslog.txt
June 3, 201115 yr try "ifconfig" It should be the middle connector on that board I believe. I don't have one of that model to confirm though. What is on the other end of the Ethernet cable? Did you look at your DHCP source? do you have more addresses available? did you look to see if it is giving an address? besides the dedicated IPMI port, one of the other ports can share Data and IPMI with 2 IP addresses on that port. that is probably what you are seeing. if all else is looking bad, swap cables. sometimes even ones you think are new can have a break in the copper or you have a cat3 (unlikely but happens).
June 3, 201115 yr Well, this doesn't look too healthy: Jun 2 10:26:36 Tower kernel: scsi2 : mvsas Jun 2 10:26:36 Tower kernel: ------------[ cut here ]------------ Jun 2 10:26:36 Tower kernel: WARNING: at fs/proc/generic.c:590 proc_register+0x11c/0x14b() Jun 2 10:26:36 Tower kernel: Hardware name: X8SIL Jun 2 10:26:36 Tower kernel: proc_dir_entry 'scsi_tgt/mvst_scst' already registered Jun 2 10:26:36 Tower kernel: Modules linked in: mvsas(+) libsas scst scsi_transport_sas Jun 2 10:26:36 Tower kernel: Pid: 938, comm: modprobe Not tainted 2.6.32.9-unRAID #8 Jun 2 10:26:36 Tower kernel: Call Trace: Jun 2 10:26:36 Tower kernel: [<c102449e>] warn_slowpath_common+0x60/0x77 Jun 2 10:26:36 Tower kernel: [<c10244e9>] warn_slowpath_fmt+0x24/0x27 Jun 2 10:26:36 Tower kernel: [<c109cf0e>] proc_register+0x11c/0x14b Jun 2 10:26:36 Tower kernel: [<c109d0cc>] proc_mkdir_mode+0x2f/0x43 Jun 2 10:26:36 Tower kernel: [<c109d0ef>] proc_mkdir+0xf/0x11 Jun 2 10:26:36 Tower kernel: [<f83f6a36>] scst_build_proc_target_dir_entries+0x55/0xdc [scst] Jun 2 10:26:36 Tower kernel: [<f83ddca9>] __scst_register_target_template+0x16c/0x3af [scst] Jun 2 10:26:36 Tower kernel: [<f845bd5d>] mvst_init+0x3b/0x5b [mvsas] Jun 2 10:26:36 Tower kernel: [<f8460895>] mvs_pci_init+0xaa5/0xaf7 [mvsas] Jun 2 10:26:36 Tower kernel: [<c10062d9>] ? dma_generic_alloc_coherent+0x0/0xdb Jun 2 10:26:36 Tower kernel: [<c1142050>] local_pci_probe+0xe/0x10 Jun 2 10:26:36 Tower kernel: [<c11426ad>] pci_device_probe+0x48/0x66 Jun 2 10:26:36 Tower kernel: [<c1194956>] driver_probe_device+0x79/0xed Jun 2 10:26:36 Tower kernel: [<c1194a0d>] __driver_attach+0x43/0x5f Jun 2 10:26:36 Tower kernel: [<c11940a7>] bus_for_each_dev+0x39/0x5a Jun 2 10:26:36 Tower kernel: [<f8468000>] ? mvs_init+0x0/0x45 [mvsas] Jun 2 10:26:36 Tower kernel: [<c119482f>] driver_attach+0x14/0x16 Jun 2 10:26:36 Tower kernel: [<c11949ca>] ? __driver_attach+0x0/0x5f Jun 2 10:26:36 Tower kernel: [<c119451c>] bus_add_driver+0x9f/0x1c5 Jun 2 10:26:36 Tower kernel: [<f8468000>] ? mvs_init+0x0/0x45 [mvsas] Jun 2 10:26:36 Tower kernel: [<c1194ccf>] driver_register+0x7b/0xd7 Jun 2 10:26:36 Tower kernel: [<f8468000>] ? mvs_init+0x0/0x45 [mvsas] Jun 2 10:26:36 Tower kernel: [<c1142882>] __pci_register_driver+0x39/0x8c Jun 2 10:26:36 Tower kernel: [<f8468000>] ? mvs_init+0x0/0x45 [mvsas] Jun 2 10:26:36 Tower kernel: [<f8468030>] mvs_init+0x30/0x45 [mvsas] Jun 2 10:26:36 Tower kernel: [<c1001139>] do_one_initcall+0x4c/0x131 Jun 2 10:26:36 Tower kernel: [<c1042e6e>] sys_init_module+0xa7/0x1dd Jun 2 10:26:36 Tower kernel: [<c1002935>] syscall_call+0x7/0xb Jun 2 10:26:36 Tower kernel: ---[ end trace 242d66fa6522586e ]--- Jun 2 10:26:36 Tower kernel: [938]: scst: __scst_register_target_template:253:***ERROR***: Target driver mvst_scst already registered Jun 2 10:26:36 Tower kernel: [938]: scst: __scst_register_target_template:293:***ERROR***: Failed to register target template mvst_scst I'm guessing that this ended up with something (init ??) dying, because it appears that none of the "normal" startup scripts ever ran, one of which would use DHCP to get the IP address. Cheers.
June 3, 201115 yr Well, this doesn't look too healthy: Jun 2 10:26:36 Tower kernel: scsi2 : mvsas Jun 2 10:26:36 Tower kernel: ------------[ cut here ]------------ Jun 2 10:26:36 Tower kernel: WARNING: at fs/proc/generic.c:590 proc_register+0x11c/0x14b() Jun 2 10:26:36 Tower kernel: Hardware name: X8SIL Jun 2 10:26:36 Tower kernel: proc_dir_entry 'scsi_tgt/mvst_scst' already registered Jun 2 10:26:36 Tower kernel: Modules linked in: mvsas(+) libsas scst scsi_transport_sas Jun 2 10:26:36 Tower kernel: Pid: 938, comm: modprobe Not tainted 2.6.32.9-unRAID #8 Jun 2 10:26:36 Tower kernel: Call Trace: Jun 2 10:26:36 Tower kernel: [<c102449e>] warn_slowpath_common+0x60/0x77 Jun 2 10:26:36 Tower kernel: [<c10244e9>] warn_slowpath_fmt+0x24/0x27 Jun 2 10:26:36 Tower kernel: [<c109cf0e>] proc_register+0x11c/0x14b Jun 2 10:26:36 Tower kernel: [<c109d0cc>] proc_mkdir_mode+0x2f/0x43 Jun 2 10:26:36 Tower kernel: [<c109d0ef>] proc_mkdir+0xf/0x11 Jun 2 10:26:36 Tower kernel: [<f83f6a36>] scst_build_proc_target_dir_entries+0x55/0xdc [scst] Jun 2 10:26:36 Tower kernel: [<f83ddca9>] __scst_register_target_template+0x16c/0x3af [scst] Jun 2 10:26:36 Tower kernel: [<f845bd5d>] mvst_init+0x3b/0x5b [mvsas] Jun 2 10:26:36 Tower kernel: [<f8460895>] mvs_pci_init+0xaa5/0xaf7 [mvsas] Jun 2 10:26:36 Tower kernel: [<c10062d9>] ? dma_generic_alloc_coherent+0x0/0xdb Jun 2 10:26:36 Tower kernel: [<c1142050>] local_pci_probe+0xe/0x10 Jun 2 10:26:36 Tower kernel: [<c11426ad>] pci_device_probe+0x48/0x66 Jun 2 10:26:36 Tower kernel: [<c1194956>] driver_probe_device+0x79/0xed Jun 2 10:26:36 Tower kernel: [<c1194a0d>] __driver_attach+0x43/0x5f Jun 2 10:26:36 Tower kernel: [<c11940a7>] bus_for_each_dev+0x39/0x5a Jun 2 10:26:36 Tower kernel: [<f8468000>] ? mvs_init+0x0/0x45 [mvsas] Jun 2 10:26:36 Tower kernel: [<c119482f>] driver_attach+0x14/0x16 Jun 2 10:26:36 Tower kernel: [<c11949ca>] ? __driver_attach+0x0/0x5f Jun 2 10:26:36 Tower kernel: [<c119451c>] bus_add_driver+0x9f/0x1c5 Jun 2 10:26:36 Tower kernel: [<f8468000>] ? mvs_init+0x0/0x45 [mvsas] Jun 2 10:26:36 Tower kernel: [<c1194ccf>] driver_register+0x7b/0xd7 Jun 2 10:26:36 Tower kernel: [<f8468000>] ? mvs_init+0x0/0x45 [mvsas] Jun 2 10:26:36 Tower kernel: [<c1142882>] __pci_register_driver+0x39/0x8c Jun 2 10:26:36 Tower kernel: [<f8468000>] ? mvs_init+0x0/0x45 [mvsas] Jun 2 10:26:36 Tower kernel: [<f8468030>] mvs_init+0x30/0x45 [mvsas] Jun 2 10:26:36 Tower kernel: [<c1001139>] do_one_initcall+0x4c/0x131 Jun 2 10:26:36 Tower kernel: [<c1042e6e>] sys_init_module+0xa7/0x1dd Jun 2 10:26:36 Tower kernel: [<c1002935>] syscall_call+0x7/0xb Jun 2 10:26:36 Tower kernel: ---[ end trace 242d66fa6522586e ]--- Jun 2 10:26:36 Tower kernel: [938]: scst: __scst_register_target_template:253:***ERROR***: Target driver mvst_scst already registered Jun 2 10:26:36 Tower kernel: [938]: scst: __scst_register_target_template:293:***ERROR***: Failed to register target template mvst_scst I'm guessing that this ended up with something (init ??) dying, because it appears that none of the "normal" startup scripts ever ran, one of which would use DHCP to get the IP address. Cheers. Do not worry about the above "error." You have 2 Supermicro SASLP cards in your system and that message is a side effect of the driver trying to be loaded again, even though the driver is already loaded, from when the first SASLP card was initialized.
June 3, 201115 yr Do not worry about the above "error." You have 2 Supermicro SASLP cards in your system and that message is a side effect of the driver trying to be loaded again, even though the driver is already loaded, from when the first SASLP card was initialized. In that case, something else stopped ALL the /etc/rc.d/rc.* scripts from running. Cheers.
June 4, 201115 yr Author Thank you for all the pointers... Seems was performing a bad extract of the unraid zip file to the usb drive. Hence why "ifconfig" would return nothing and my syslog was so short. Surprised it booted and I was able to log in on the machine. Now I get two IP addresses for the case off the middle port - Data and IPMI Questions: Since I am running two Supermicro AOC-SASLP-MV8 cards and a 16 bay Norco case is there any disadvantage to just using the ports on the cards. Thus not using the motherboard SATA ports and the SFF-8087 Reverse (SFF8087OCR) SAS cable. Is there any added speed to having both Ethernet ports connected? Many thanks in advance, Wayne
June 4, 201115 yr The reason to use the motherboard Sata over the MV8 would be bus speed. The motherboard sata would get a better I/O throughput then PCIe 4x sas controller if all drives were spinning at once. In theory your parity checks and rebuilds would be a bit faster. For day to day use. there would be no differance. I would however try to connect at least the parity drive and cache drive to the motherboard. Reverse breakout cables tend to be cheaper then sas to sas cables.. a save a few bucks also..
Archived
This topic is now archived and is closed to further replies.