October 1, 20178 yr I will provide as much information as i can but a confessed noob so please help me out on this with instructions that i could understand. I have a combination of drives that is giving me alot of trouble as it is not showing up on the array setup screen. I have tried to follow instructions from previous responses but without success. 2 SSD drives (Appears in array and is not a problem!) 2 x 2TB brand new seagate drives that are not visible 3 SAS drives that i recycled from an older server and these are not visible either. I am not sure how to get the drives to show up so that i could assign them to an array. Syslog attached as per wiki instructions. syslog.txt
October 1, 20178 yr Author Hi uldise, pls let me know if this is what you are looking for... if not, what you would need. nas-diagnostics-20171001-0020.zip
October 1, 20178 yr just wait for some with more experience, simply always upload diagnostics file when you asking for such help..
October 1, 20178 yr Besides the two SSDs I only see attempts to initialize another device, which I expect is one of the 2TB Seagates, it's connected on onboard SATA port #3: Oct 1 00:20:08 NAS kernel: ata3: SATA link down (SStatus 0 SControl 310) Oct 1 00:20:08 NAS kernel: ata3: EH complete Oct 1 00:20:08 NAS kernel: ata3: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen Oct 1 00:20:08 NAS kernel: ata3: irq_stat 0x00000040, connection status changed Oct 1 00:20:08 NAS kernel: ata3: SError: { DevExch } Oct 1 00:20:08 NAS kernel: ata3: limiting SATA link speed to 1.5 Gbps Oct 1 00:20:08 NAS kernel: ata3: hard resetting link Oct 1 00:20:09 NAS kernel: ata3: SATA link down (SStatus 0 SControl 310) Oct 1 00:20:09 NAS kernel: ata3: EH complete Oct 1 00:20:10 NAS kernel: ata3: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen Oct 1 00:20:10 NAS kernel: ata3: irq_stat 0x00000040, connection status changed Oct 1 00:20:10 NAS kernel: ata3: SError: { DevExch } Oct 1 00:20:10 NAS kernel: ata3: limiting SATA link speed to 1.5 Gbps Oct 1 00:20:10 NAS kernel: ata3: hard resetting link Oct 1 00:20:11 NAS kernel: ata3: SATA link down (SStatus 0 SControl 310) Oct 1 00:20:11 NAS kernel: ata3: EH complete Oct 1 00:20:12 NAS kernel: ata3: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen Oct 1 00:20:12 NAS kernel: ata3: irq_stat 0x00000040, connection status changed Oct 1 00:20:12 NAS kernel: ata3: SError: { DevExch } Oct 1 00:20:12 NAS kernel: ata3: limiting SATA link speed to 1.5 Gbps Oct 1 00:20:12 NAS kernel: ata3: hard resetting link Device is never successfully initialized, the 3 remaining onboard SATA ports report link down, you want to try different cables on those Seagates and check if they are detected by the board bios at startup, if they aren't unRAID won't detected them either. As for the SAS disks, I assume they are connected to the LSI controller, the controller is detected by unRAID and the driver loaded but there's no attempt to find any disks, also check its bios if the disks are detected, and if it's a RAID controller (or in RAID mode) you may need to create a JBOD or a RAID0 for each disk.
January 9, 20206 yr Hello, I'm not sure if this is the correct place to ask for help, but I am out of Ideas. I'm running Unraid plus 6.8.0 on a R710. I just picked up a MD1000 . I see the device and the drives in Dell Bios ctrl-c to get to setup, highlight Bios and OS and reboot. I see the R710 search for drive, it finds them, then loads Unraid. I expect to see the drives in Unassigned devices but no Joy. I've attached the diagnosis Any suggestion is appreciated. Chas tower-diagnostics-20200108-1654.zip
January 9, 20206 yr Not seeing anything out of the ordinary on the log, is the MD1000 connected to the same Perc controller as the other disks?
January 9, 20206 yr No, the MD1000 is connected to a SAS 5/E. I see the controller load in Bios, search for drives and find them. The Odd part is that I have a R410 with the same setup that sees a MD1000 fine. That is what has me at a loss. Chas
January 9, 20206 yr That controller is being passed though: Quote 0a:08.0 SCSI storage controller [0100]: Broadcom / LSI SAS1068 PCI-X Fusion-MPT SAS [1000:0054] (rev 01) Subsystem: Dell SAS 5/E Adapter Controller [1028:1f04] Kernel driver in use: vfio-pci Kernel modules: mptsas So naturally all connected devices will be unavailable for Unraid.
January 9, 20206 yr Please pardon my ignorance. I do not know what to do with the information that you just provided? Chas
January 9, 20206 yr Perhaps I confused the situation when I mentioned my R410. The diagnostic that I provided that shows; 0a:08.0 SCSI storage controller [0100]: Broadcom / LSI SAS1068 PCI-X Fusion-MPT SAS [1000:0054] (rev 01) Subsystem: Dell SAS 5/E Adapter Controller [1028:1f04] Kernel driver in use: vfio-pci Kernel modules: mptsas was ran on the R710 yet I do not see the drives attached to the MD1000, thus my confusion. Chas
January 9, 20206 yr On the main GUI page click on cache and scroll down to "Syslinux Configuration", look for "append" and remove 1000:0054 from the boot command.
January 9, 20206 yr 7 minutes ago, kysdaddy said: Please pardon my ignorance. I do not know what to do with the information that you just provided? Did you attempt to PCIe stubbing any device in the past? It could be that you used the file method and the controller is in the same IOMMU group as the other intentionally stubbed device (probably your GPU). Unraid will try to stub everything in the same IOMMU group, which affected your controller without your realising it. If you used the syslinux method then follow Jonnie advice (click on Flash then scroll down to the syslinux section).
January 9, 20206 yr Gentleman, Thank you so much! Unraid now sees the drives and I am off to the races! Chas
January 9, 20206 yr sorry about the delay, but should I pull 8086:032c out of append as well or leave it? IOMMU group 16: [8086:032c] 04:00.0 PCI bridge: Intel Corporation 6702PXH PCI Express-to-PCI Bridge A (rev 09) [1000:0054] 05:08.0 SCSI storage controller: Broadcom / LSI SAS1068 PCI-X Fusion-MPT SAS (rev 01)
January 10, 20206 yr 2 hours ago, kysdaddy said: but should I pull 8086:032c out of append as well or leave it? I believe you should remove it as well.
January 29, 20206 yr On 1/9/2020 at 4:44 PM, johnnie.black said: On the main GUI page click on cache and scroll down to "Syslinux Configuration", look for "append" and remove 1000:0054 from the boot command. Sorry to drop in I am having the same issue.
January 29, 20206 yr 7 hours ago, Sam.Chapple said: Sorry to drop in I am having the same issue. Likely not the same issue, but please post the diagnostics: Tools -> Diagnostics
January 29, 20206 yr 12 hours ago, johnnie.black said: Likely not the same issue, but please post the diagnostics: Tools -> Diagnostics tower-diagnostics-20200129-2016.zip
January 29, 20206 yr 05:00.0 RAID bus controller [0104]: Broadcom / LSI MegaRAID SAS 2108 [Liberator] [1000:0079] (rev 05) Subsystem: Broadcom / LSI MegaRAID SAS 9260-8i [1000:9261] Kernel driver in use: megaraid_sas Kernel modules: megaraid_sas @Sam.Chapple Your controller is in RAID mode using the MegaRAID driver. You should try flashing it to IT mode. RAID cards don't work well with unRAID (emphasis on the 'un') and drives attached to them won't show up in unRAID. Edited January 29, 20206 yr by Hoopster
January 30, 20206 yr That controller most likely can't be flashed to IT mode, it still should work but you need to create a RAID0/JBOD for each disk, but like mentioned they are not recommended for various reasons, e.g., if you replace it with a different controller Unraid won't recognize the devices.
February 2, 20206 yr On 1/29/2020 at 8:37 PM, Hoopster said: 05:00.0 RAID bus controller [0104]: Broadcom / LSI MegaRAID SAS 2108 [Liberator] [1000:0079] (rev 05) Subsystem: Broadcom / LSI MegaRAID SAS 9260-8i [1000:9261] Kernel driver in use: megaraid_sas Kernel modules: megaraid_sas @Sam.Chapple Your controller is in RAID mode using the MegaRAID driver. You should try flashing it to IT mode. RAID cards don't work well with unRAID (emphasis on the 'un') and drives attached to them won't show up in unRAID. Im getting the error to the side when trying to upgrade firmware. "no lsi sas adapters found! limited command set avalible!" "Advanced mode set"
February 3, 20206 yr 15 hours ago, Sam.Chapple said: Im getting the error to the side when trying to upgrade firmware. "no lsi sas adapters found! limited command set avalible!" "Advanced mode set" Likely, because as @johnnie.black noted, that controller does not support being cross-flashed to IT mode. There are several models of LSI controllers mentioned in these forums that do support IT mode. It appears from some searching that it may not support JBOD either. The 926x line has a 2208 chip which, apparently, is RAID only. Your best bet is to pick up an LSI controller that does support cross flashing to IT mode. Those based on the 2008 or 2308 chips are popular. Someone reported having been able to flash a 2208 controller with 2308 IT firmware, but, that is risky to say the least and I am not sure I would trust that report. Edited February 3, 20206 yr by Hoopster
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.