lazerdave

Found it in the North Bridge settings. Disabled it and now the drives appear in Unassigned Devices!! Thank you, Johnnie.Black! Of course, I probably don't really want to live without IOMMU in the long run. Think I'll try to get a refund on this card once that Dell arrives and I get it up and running with VT-d enabled. Thanks a million everyone, especially Johnnie.

That's what I thought, too, but I can't find it anywhere in there... My System Information shows that IOMMU is enabled, so I know it's gotta be there someplace, but damned if I can find it.

Pardon my ignorance, but do I turn off IOMMU in BIOS or unRAID?

SAS#1 from the backplane also uses the same breakout cable with 4 SATA and the weird ribbon thing. Because the motherboard has sufficient SATA ports for it to be used as-is, that's what I've done.

This is what I bought and have been fighting.

Thanks for the quick reply. No luck, I'm afraid. I actually tried both solutions separately, append initrd=/bzroot scsi_mod.use_blk_mq=1 and append initrd=/bzroot iommu=pt. (I actually did it on bzroot-gui, if that matters...) Should I just give up on this controller and order a Dell H310 like I saw someone else mention in the link you sent? I found a Dell H310 6Gbps SAS HBA w/ LSI 9211-8i P20 IT Mode for ZFS FreeNAS unRAID for a good price. Just want the damned thing working, y'know?

I've got a Supermicro server with 12 drive bays running unRAID 6.8.2 Plus. Right now, the array has 5 data drives, 2 parity, and 1 SSD cache drive. It had shipped with SAS#3 completely disconnected and SAS#2 running from a breakout cable with only 2/4 of the SATA cables with anywhere to go. SAS#1 is using the first 4 SATA ports on the motherboard and has always been fine. So I bought a controller card with 2 mini SAS ports - an IOCrest 88SE9215, which according to the Hardware Compatibility List seemed it would be supported out of the box. First order of business was to get SAS#3's bays working, which it did the first time I powered it up after installing the card. Next, I disconnected the breakout cable from SAS#2 and ran it to the other port on the controller. During boot, it detects the drives connected to SAS#2, reporting their details properly. However, they don't appear in unRAID in the CA Unassigned Drives section or in the PreClear plugin. Something that might be noteworthy, the breakout cable has the usual 4 SATAs, but an additional ribbon cable going to an 8-pin power(?) connector. Can't find any other mini-SAS to SATA cables online that have that configuration. The backplane has a Molex for each of the SAS connectors, and all of the indicator lights are working, so the assumption is that the issue isn't power. The splash screen for the drives that aren't showing is: Marvell 88SE92xx Adapter - BIOS Version 1.0.0.1028 PCIe x1 5.0Gbps [Bus:Dev] = [4:0] Mode: PassThru AHCI Port Disk Name Size Speed S2 SATA: ST3000DM001-serial 3TB 6Gb/s S3 SATA: ST3000VN000-serial 3TB 6Gb/s For the ones that DO show, it's: Marvell 88SE92xx Adapter - BIOS Version 1.0.0.1028 PCIe x1 5.0Gbps [Bus:Dev] = [6:0] Mode: PassThru AHCI Port Disk Name Size Speed S0 SATA: WCB serial 8TB 6Gb/s S1 SATA: SanDisk SSD Plus Serial S2 SATA: ST2000DM006-serial 3TB 6Gb/s S3 SATA: ST2000VM001-serial 3TB 6Gb/s The mode of PassThru AHCI is concerning. I understand that many controller cards need to be placed into IT mode, but I can't find how to get into the on card BIOS to try to change that. I'm not sure what to do next to get those drives into my array. Any kind souls out there with advice, please? rack-diagnostics-20200402-1715.zip

A key portion of my physical home automation needs commands sent to it via nc, but it doesn't appear to be included as part of the Docker image. Could we get that on the list of items to add, please? Aside from this one item that I need, I'm really liking it. Great performance increase over my existing RPi instance!

Newish to Docker. FileZilla WebUI keeps firing sabNZB, even though their ports are different. FileZilla is set to 3389/tcp>192.168.1.111:3389 and sab is set to 8080/tcp>192.168.1.111:8080. I've restarted Docker by stopping and starting the array, but it still fires sab. Any tips would be most welcome. Thanks!!!

I thought I had everything configured correctly, but every time I add a show with missing episodes, SAB is not firing up. I'm not sure which files to post here that would point out the error, but you do! SHOULD SB use sab for search? I would assume that since I'm paying for NZB.SU and OMGWTFNZBs and have them set in Search Providers, it's going to use them first? or is this in my SAB settings? I hope this is the right forum. Many thanks in advance!

Told you I was doing something dumb. That worked. Thank you!!! If SB was adding a new show is used to add a folder for it so I could just Add Shows but I can't find that piece. Also, my SAB seems to be configured right, but it's not grabbing old shows either...

After a clean install of 6.1.8, I'm running fine except adding shows in SB. sab has /config <> /mnt/user/appdata/sabnzb /appdatafolder <> /mnt/user/appdata /downloads <> /mnt/user/downloads SB has /config <> /mnt/user/sickbeard /downloads <> /mnt/user/downloads/ /tv <> /mnt/user/MEDIA/TV Problem is, I can't add shows to existing folders on MEDIA. I can't even select past /mnt... Any assistance is greatly appreciated. I'm sure I'm doing something stupid. P.S. I'd really like to be able to periodically check an FTP site via SFTP and grab anything new to the correct show folder, but one thing at a time...

Do you know a thread about starting from scratch without losing data? My array itself means a lot to me.

Well, kinda sorted, my sabNZB and Sickbeard are still unreachable even though they show in the log as started. How are you installing these applications? You really should be using dockers for them but if not then you must use the v6 plugins which are only available from PhAzE. Ive been using plugins from PhAzE.