September 5, 201411 yr Hi Rob, Not sure if i should add it to the bottom of this post or start a new one so if it need to be moved to a new post please let me know an ill start a new one. Missing drives, possible card not recognised I tried to set 6.0 b8 today but all drives ( 8 ) on one of my SAS cards are not showing up when the system has started. The card in question is the IBM ServeRAID M1115, firmware details are below. Firmware has been updated from 17 to 19 today and still a no show. The Dell card has only 2 drives attached to it and shows the drives no problem A reboot doesn't bring the drives back I don't know if the card is being recognised or not but i cant see it in the syslog (attached logs "5.0.5" & "6.0 b8") if i revert back to 5.0.5 all works fine. System details are below MB - Gigabyte H55M-UD2H CPU: Intel® Core™ i3 CPU @ 2.933 GHz Memory: 8GB SAS Cards: IBM ServeRAID M1115 crossflashed to LSI SAS2008 - FWVersion(19.00.00.00), ChipRevision(0x03), BiosVersion(07.37.00.00) Dell PERC H200 8-Port crossflashed to LSI9211-8i IT - FWVersion(19.00.00.00), ChipRevision(0x03), BiosVersion(07.37.00.00) Have i missed anything out? let me know and i can provide if needed. logs have been zipped cuz they push it over the size limit. Thanks Mod edit: change icon unRAID_5.0.5_syslog.zip unRAID_6b8_syslog.zip
September 6, 201411 yr Card: IBM ServeRAID M1115 crossflashed to LSI SAS2008 - FWVersion(19.00.00.00), ChipRevision(0x03), BiosVersion(07.37.00.00) Driver: mpt2sas Problem: works in 32 bit on both the Dell and IBM ServeRAID M1115 cards, but in 64 bit does not work on the IBM card. Card is recognized and correct driver announces itself, but reset of card fails and no further initialization is done, leaving all attached drives missing. From syslog (UnRAID v5.0.5): Sep 5 12:41:31 Lion kernel: mpt2sas version 14.100.00.00 loaded Sep 5 12:41:31 Lion kernel: scsi1 : Fusion MPT SAS Host Sep 5 12:41:31 Lion kernel: mpt2sas0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (8171952 kB) Sep 5 12:41:31 Lion kernel: mpt2sas 0000:01:00.0: irq 43 for MSI/MSI-X Sep 5 12:41:31 Lion kernel: mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 43 Sep 5 12:41:31 Lion kernel: mpt2sas0: sending diag reset !! Sep 5 12:41:31 Lion kernel: mpt2sas0: diag reset: SUCCESS Sep 5 12:41:31 Lion kernel: mpt2sas0: LSISAS2008: FWVersion(19.00.00.00), ChipRevision(0x03), BiosVersion(07.37.00.00) From syslog (UnRAID v6.0-beta8): Sep 5 17:52:51 Lion kernel: mpt2sas version 16.100.00.00 loaded Sep 5 17:52:51 Lion kernel: scsi1 : Fusion MPT SAS Host Sep 5 17:52:51 Lion kernel: mpt2sas0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (8041848 kB) Sep 5 17:52:51 Lion kernel: mpt2sas 0000:01:00.0: irq 42 for MSI/MSI-X Sep 5 17:52:51 Lion kernel: mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 42 Sep 5 17:52:51 Lion kernel: mpt2sas0: doorbell is in use (line=3053) Sep 5 17:52:51 Lion kernel: mpt2sas0: _base_get_ioc_facts: handshake failed (r=-14) Sep 5 17:52:51 Lion kernel: mpt2sas0: sending diag reset !! Sep 5 17:52:51 Lion kernel: mpt2sas0: diag reset: FAILED Sep 5 17:52:51 Lion kernel: mpt2sas0: failure at drivers/scsi/mpt2sas/mpt2sas_scsih.c:8234/_scsih_probe()! For comparison from syslog (UnRAID v6.0-beta8) for similar Dell card using same driver: Sep 5 17:52:51 Lion kernel: scsi8 : Fusion MPT SAS Host Sep 5 17:52:51 Lion kernel: mpt2sas1: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (8041848 kB) Sep 5 17:52:51 Lion kernel: mpt2sas 0000:02:00.0: irq 42 for MSI/MSI-X Sep 5 17:52:51 Lion kernel: mpt2sas1-msix0: PCI-MSI-X enabled: IRQ 42 Sep 5 17:52:51 Lion kernel: mpt2sas1: sending message unit reset !! Sep 5 17:52:51 Lion kernel: mpt2sas1: message unit reset: SUCCESS Sep 5 17:52:51 Lion kernel: mpt2sas1: LSISAS2008: FWVersion(19.00.00.00), ChipRevision(0x03), BiosVersion(07.37.00.00) Sep 5 17:52:51 Lion kernel: mpt2sas1: Dell 6Gbps SAS HBA: Vendor(0x1000), Device(0x0072), SSVID(0x1028), SSDID(0x1F1C) So mpt2sas with firmware v19 works in 32 bit with both cards, and with the Dell card in 64 bit but not the IBM card in 64 bit. The above is based on my guidelines for non-working 64 bit drivers, found here. Please let me know if guidelines can be improved.
September 6, 201411 yr Look at bottom of this post: http://lime-technology.com/forum/index.php?topic=34955.msg326278#msg326278 Do you have VT-d enabled on your motherboard?
September 7, 201411 yr Author It was enabled but i disabled it and made no differenance apart from hang for about 5min on boot starting due to VT-d being disabled Starting libvirtd... modprobe: ERROR: Could not insert 'kvm_intel':Operation Not supported. Sep 7 10:54:16 Lion logger: Starting libvirt Sep 7 10:54:16 Lion kernel: tun: Universal TUN/TAP device driver, 1.6 Sep 7 10:54:16 Lion kernel: tun: (C) 1999-2004 Max Krasnyansky Sep 7 10:54:16 Lion kernel: kvm: disabled by bios Same log details for the for the cards Sep 7 10:54:12 Lion kernel: mpt2sas0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (8041848 kB) Sep 7 10:54:12 Lion kernel: mpt2sas 0000:01:00.0: irq 43 for MSI/MSI-X Sep 7 10:54:12 Lion kernel: mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 43 Sep 7 10:54:12 Lion kernel: mpt2sas0: iomem(0x00000000dbec0000), mapped(0xffffc90004f30000), size(16384) Sep 7 10:54:12 Lion kernel: mpt2sas0: ioport(0x000000000000ee00), size(256) Sep 7 10:54:12 Lion kernel: mpt2sas0: doorbell is in use (line=3053) Sep 7 10:54:12 Lion kernel: mpt2sas0: _base_get_ioc_facts: handshake failed (r=-14) Sep 7 10:54:12 Lion kernel: mpt2sas0: sending diag reset !! Sep 7 10:54:12 Lion kernel: mpt2sas0: diag reset: FAILED Sep 7 10:54:12 Lion kernel: mpt2sas0: failure at drivers/scsi/mpt2sas/mpt2sas_scsih.c:8234/_scsih_probe()!
April 22, 201511 yr Author We are now at v6 b15 and it still hasnt been fixed so i thought i would check to see if anyone else has had any problems like i have nd i found this posting http://lime-technology.com/forum/index.php?topic=39077.0 i read through it and found it to be the same driver and issue i was having. The post mentions added "pci=realloc=off" to the syslinux file, i added it and my syslinux fie looks like this now default /syslinux/menu.c32 menu title Lime Technology prompt 0 timeout 50 label unRAID OS menu default kernel /bzimage append pci=realloc=off initrd=/bzroot label unRAID OS Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot unraidsafemode label Memtest86+ kernel /memtest label Xen/unRAID OS kernel /syslinux/mboot.c32 append /xen --- /bzimage --- /bzroot label Xen/unRAID OS Safe Mode (no plugins) kernel /syslinux/mboot.c32 append /xen --- /bzimage --- /bzroot unraidsafemode I rebooted and i was able to see the drives attached to the M1115 card. So i have a work around until it in included in the kernel, but will the file be over written when a new version is released before the kernel is updated? thanks
April 22, 201511 yr The post mentions added "pci=realloc=off" to the syslinux file, i added it and my syslinux fie looks like this now default /syslinux/menu.c32 menu title Lime Technology prompt 0 timeout 50 label unRAID OS menu default kernel /bzimage append pci=realloc=off initrd=/bzroot label unRAID OS Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot unraidsafemode label Memtest86+ kernel /memtest label Xen/unRAID OS kernel /syslinux/mboot.c32 append /xen --- /bzimage --- /bzroot label Xen/unRAID OS Safe Mode (no plugins) kernel /syslinux/mboot.c32 append /xen --- /bzimage --- /bzroot unraidsafemode I rebooted and i was able to see the drives attached to the M1115 card. So i have a work around until it in included in the kernel, but will the file be over written when a new version is released before the kernel is updated? I assume you mean the syslinux.cfg file? If so then then my experience is that it does NOT get overwritten during the upgrade process if you do it from the GUI. However it still a good idea to have a backup if you have made changes relative to the LimeTech provided version of that file.
April 22, 201511 yr Author I assume you mean the syslinux.cfg file? If so then then my experience is that it does NOT get overwritten during the upgrade process if you do it from the GUI. However it still a good idea to have a backup if you have made changes relative to the LimeTech provided version of that file. yes thats the one. But i have now had to remove it as i have started to get read errors on the drives that i have connected to the Dell card. its now telling me one of the drives is missing so thats now fun to try and work out So back to square one with the IBM M1115 still not working
January 26, 201610 yr Author Its been a while since this thread had movement is in. I’m still having the same problem with the IBM M1115 cross flashed card as noted above. Today I decided to take the card out of the machine and put it into another one, I booted a fresh clean copy of unRAID and low and behold the card was recognised as shown below. Jan 26 08:16:10 Tower kernel: mpt2sas0: MSI-X vectors supported: 1, no of cores: 4, max_msix_vectors: 8 Jan 26 08:16:10 Tower kernel: mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 33 Jan 26 08:16:10 Tower kernel: mpt2sas0: iomem(0x00000000f04c0000), mapped(0xffffc90001c00000), size(16384) Jan 26 08:16:10 Tower kernel: mpt2sas0: ioport(0x000000000000be00), size(256) Jan 26 08:16:10 Tower kernel: mpt2sas0: sending message unit reset !! Jan 26 08:16:10 Tower kernel: mpt2sas0: message unit reset: SUCCESS Jan 26 08:16:10 Tower kernel: mpt2sas0: Allocated physical memory: size(7445 kB) Jan 26 08:16:10 Tower kernel: mpt2sas0: Current Controller Queue Depth(3307), Max Controller Queue Depth(3432) Jan 26 08:16:10 Tower kernel: mpt2sas0: Scatter Gather Elements per IO(128) Jan 26 08:16:10 Tower kernel: mpt2sas0: LSISAS2008: FWVersion(19.00.00.00), ChipRevision(0x03), BiosVersion(07.37.00.00) Jan 26 08:16:10 Tower kernel: mpt2sas0: Protocol=(Initiator,Target), Capabilities=(TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ) Jan 26 08:16:10 Tower kernel: mpt2sas0: sending port enable !! Jan 26 08:16:10 Tower kernel: mpt2sas0: host_add: handle(0x0001), sas_addr(0x500605b00637e460), phys( Jan 26 08:16:10 Tower kernel: mpt2sas0: port enable: SUCCESS The original machine that it doesn’t boot in is Intel based and the other one is AMD based. I put it back in the original machine and I get the same error. I checked for firmware updates for the MB and im on the latest so I cant update anything there. i have read that unRAID has issues with the P20 firmware so no point upgrading to that. Does anyone have any advice or ideas on how to get around this? thanks
January 26, 201610 yr I checked for firmware updates for the MB and im on the latest so I cant update anything there. That's regrettable, because it sounds like what you need is a motherboard BIOS update or a firmware update for the card/chipset. i have read that unRAID has issues with the P20 firmware so no point upgrading to that. Sorry to sound defensive, but I wanted to clarify that I don't believe it was unRAID's fault. If I recall correctly, the early P20 (.0?) version was buggy, the later P20 (.4?) release was fine. You might want to locate and try that.
January 26, 201610 yr Author I checked for firmware updates for the MB and im on the latest so I cant update anything there. That's regrettable, because it sounds like what you need is a motherboard BIOS update or a firmware update for the card/chipset. i have read that unRAID has issues with the P20 firmware so no point upgrading to that. Sorry to sound defensive, but I wanted to clarify that I don't believe it was unRAID's fault. If I recall correctly, the early P20 (.0?) version was buggy, the later P20 (.4?) release was fine. You might want to locate and try that. Thanks for the details about P20, I'll give it a go latter today. Im Still a bit confused as to why it it stopped working when upgrading to V 5 to V 6.
January 28, 201610 yr Author I have updated the firmware to P20.0.4.0 and still got the same error. Might try drop the firmware version on the mother board and see what this does
February 4, 201610 yr Author Well what do you know, i reverted back 1 version of MB firmware from F11 to F10 and the card is now recognised unRAID. currently running a preclear on a couple of drives that have previously had a preclear done on them to see if it has any issues. To be honest i didn't expect the older firmware to work but what do you know
Archived
This topic is now archived and is closed to further replies.