Dmitriyus

If it was downgrading all 10 identical new disks I bought to SATA1 that would make sense, but 7 are functioning at SATA2 and 3 are stuck in SATA1.

Is the HP 487738-001 known to do this or just a guess at what the problem is?

All of the sas breakout cables from the backplane are ran to the expander and then connected to the HBA from the expander.

According to the disk identity screen. 3 out of the 10, identical 20TB drives I just installed are being downgraded to 1.5Gps. They were all ordered direct from Western Digital. I've tried moving them around to different slots but it doesn't change anything. Thanks! 3 of the disk look like this: Device model: WDC WD201KFGX-68BKJN0 Serial number: XXXXXXXXXX LU WWN device id: 5 000cca 2edc10dea Firmware version: 83.00A83 User capacity: 20,000,588,955,648 bytes [20.0 TB] Sector sizes: 512 bytes logical, 4096 bytes physical Rotation rate: 7200 rpm Form factor: 3.5 inches Device: Not in smartctl database 7.3/5440 ATA version: ACS-5 (minor revision not indicated) SATA version: SATA 3.5, 6.0 Gb/s (current: 1.5 Gb/s) <<<<<<<<<<<<<<<----------------- Local time: Fri Dec 8 12:47:10 2023 CST Other 7 all show this as the only difference: SATA version: SATA 3.2, 6.0 Gb/s (current: 3.0 Gb/s) Hardware Info: OS: Unraid 6.12.3 Chassis: SuperChassis 846BA-R920B Motherboard: Supermicro X9DRH-7TF/7F/iTF/iF , Version 1234567890 Backplane 24-Port 4U SAS 6Gbps direct-attached backplane, support up to 24x 3.5-inch SAS2/SATA3 HDD/SSD HBA card: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03) SAS/SATA EXPANDER CARD: HP 487738-001 Memory: 112 GiB DDR3 Multi-bit ECC PROCESSORS x2: Intel® Xeon® CPU E5-2680 v2 @ 2.80GHz Mellanox Technologies MT26448 [ConnectX EN 10GigE, PCIe 2.0 5GT/s] (rev b0)

Is there a limit to the "OAIWUI_GPT_MODELS:"? I have the models below but adding them in the field doesn't allow me to get past the "Enter User" screen. Checked logs but nothing. Thanks! gpt-3.5-turbo,gpt-3.5-turbo-0301,gpt-3.5-turbo-0613,gpt-3.5-turbo-1106,gpt-3.5-turbo-16k,gpt-3.5-turbo-16k-0613,gpt-3.5-turbo-instruct,gpt-3.5-turbo-instruct-0914,gpt-4 Side Note: It does NOT like when there are spaces after the commas.

I wrote this for my pi-hole docker. There was probably an easy way to change the default ram setting but this was what I came up with. I was attemping to parse logs older than 24 hours at a time and the default 128M ram causes the error: "You may need to increase the memory available". Pi-hole discourse suggested waiting for version 6 LOL. Pi-hole discourse link: Pi-hole Discourse