synoxpe Posted March 7, 2022 Share #326 Posted March 7, 2022 (edited) 11 minutes ago, Orphée said: In DSM I only have partial SMART data working. At disk level, click on smart, and the 4 lines are only : - No temp, no error number... Then in advanced/detailed, there, yes, SMART data appears. Both with ESXi and Proxmox. Using LSI 9207-8i. I see. Could be the controller then as in my case I'm getting complete SMART info on Proxmox by passing through the JMB 585 PCI SATA controller, where my disks are connected to. ESXi still isn't working for me (stuck at 55% as reported above), but that's another story... Edited March 7, 2022 by synoxpe Quote Link to comment Share on other sites More sharing options...
Orphée Posted March 7, 2022 Share #327 Posted March 7, 2022 (edited) 2 minutes ago, synoxpe said: I see. Could be the controller then as in my case I'm getting complete SMART info on Proxmox by passing through the JMB 585 PCI SATA controller, where my disks are connected to. ESXi still isn't working for me (stuck at 55% as reported above), but that's another story... Check my Edit. I have the same working info at this menu level. But summary is empty. So I'm not sure DSM will actually catch disk error when it will come. Edited March 7, 2022 by Orphée Quote Link to comment Share on other sites More sharing options...
synoxpe Posted March 7, 2022 Share #328 Posted March 7, 2022 2 minutes ago, Orphée said: Check my Edit. I have the same working info at this menu level. But summary is empty. So I'm not sure DSM will actually catch disk error when it will come. Seems like it's working for me... Quote Link to comment Share on other sites More sharing options...
Orphée Posted March 7, 2022 Share #329 Posted March 7, 2022 (edited) It was working for me with Jun's loader. I did not try with RP DS3615xs loader. I could try with a spare disk... but it works currently at Proxmox level... so it is fine like this. I think there may be an issue with mpt3sas drivers and some LSI cards. Edited March 7, 2022 by Orphée Quote Link to comment Share on other sites More sharing options...
synoxpe Posted March 7, 2022 Share #330 Posted March 7, 2022 2 hours ago, Orphée said: It was working for me with Jun's loader. I did not try with RP DS3615xs loader. I could try with a spare disk... but it works currently at Proxmox level... so it is fine like this. I think there may be an issue with mpt3sas drivers and some LSI cards. @Orphée OK so these logs could explain why I'm not able to see SMART info on the first screen as well on the ds3622xs: [ 944.091588] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 984.973386] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 984.993811] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 985.555614] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 986.706584] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 986.717650] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 986.728391] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 986.740350] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 987.789612] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 987.802854] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 987.810408] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 987.817559] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 987.824668] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 987.831894] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 988.439431] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 993.939070] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 999.650491] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop Quote Link to comment Share on other sites More sharing options...
yanjun Posted March 7, 2022 Author Share #331 Posted March 7, 2022 1 hour ago, synoxpe said: OK so these logs could explain why I'm not able to see SMART info on the first screen as well on the ds3622xs: The only reason you can't see the smart information is that the driver is too new and the device is too old, mpt3sas41.0 is prepared for LSI 9400/9500, I also tried to extract mpt3sas21.0 (from LSI 9207) official driver page, unfortunately It's that he can't mix with the hard disk of the sata controller to form a raid1. Probably this version of mpt3sas is too old for the 4.4.180 kernel. This means that your system partition is always in a state that needs to be repaired, and once you repair it, your dsm will directly show that you need to reinstall it. My LSI9400-16I on 3622xs+ has no issue with missing smart info. So if you guys want to try to solve the smart information problem with LSI 92xx cards. My suggestion is to try to find the driver of the LSI 9300 series card from the official boradcom, and try to compile it between 21.0 and 41.0. Maybe a certain version can satisfy both the smart information and the two conditions of creating a system partition. 1 Quote Link to comment Share on other sites More sharing options...
Orphée Posted March 7, 2022 Share #332 Posted March 7, 2022 The only reason you can't see the smart information is that the driver is too new and the device is too old, mpt3sas41.0 is prepared for LSI 9400/9500, I also tried to extract mpt3sas21.0 (from LSI 9207) official driver page, unfortunately It's that he can't mix with the hard disk of the sata controller to form a raid1. Probably this version of mpt3sas is too old for the 4.4.180 kernel. This means that your system partition is always in a state that needs to be repaired, and once you repair it, your dsm will directly show that you need to reinstall it. My LSI9400-16I on 3622xs+ has no issue with missing smart info. So if you guys want to try to solve the smart information problem with LSI 92xx cards. My suggestion is to try to find the driver of the LSI 9300 series card from the official boradcom, and try to compile it between 21.0 and 41.0. Maybe a certain version can satisfy both the smart information and the two conditions of creating a system partition.Thank you for the detail.To be honest, as I currently have access to SMART info from Proxmox menu, and as it is my "prod" environment, I won't fight against this "issue".I must compile the driver, shutdown all system, remove my prod disks and put a spare test disk, start, test... Assuming I did not fail to build the new module... etc...And in the beginning, the LSI card was to passthrough and have SMART data inside ESXi (now proxmox) VM (DS3615xs 6.2.3 Jun's loader)...I would be on baremetal, I would not need to use the LSI card at all... so I would have SMART data with native AHCI on board controller...So I personnally give up on this topic.If I had a spare system with a spare LSI / test disk, I could play with it, but currently not. Each time I shutdown the Proxmox server, I shutdown all my reverse proxy, docker containers, etc... + DSM... Quote Link to comment Share on other sites More sharing options...
cferra Posted March 7, 2022 Share #333 Posted March 7, 2022 The only reason you can't see the smart information is that the driver is too new and the device is too old, mpt3sas41.0 is prepared for LSI 9400/9500, I also tried to extract mpt3sas21.0 (from LSI 9207) official driver page, unfortunately It's that he can't mix with the hard disk of the sata controller to form a raid1. Probably this version of mpt3sas is too old for the 4.4.180 kernel. This means that your system partition is always in a state that needs to be repaired, and once you repair it, your dsm will directly show that you need to reinstall it. My LSI9400-16I on 3622xs+ has no issue with missing smart info. So if you guys want to try to solve the smart information problem with LSI 92xx cards. My suggestion is to try to find the driver of the LSI 9300 series card from the official boradcom, and try to compile it between 21.0 and 41.0. Maybe a certain version can satisfy both the smart information and the two conditions of creating a system partition.Broadcom lists drivers for the card v41 v40 v39 and v38I can provide download links If someone would be willing to compile as I don’t have the knowledge to do that. Sent from my iPhone using Tapatalk Quote Link to comment Share on other sites More sharing options...
Orphée Posted March 7, 2022 Share #334 Posted March 7, 2022 I also found v26 too. Quote Link to comment Share on other sites More sharing options...
Orphée Posted March 7, 2022 Share #335 Posted March 7, 2022 (edited) mpt3sas-26.00-Linux-v4.4.180+_DS3622xs+.zip compiled but not tested, feel free to try it on a test env. Edit : build with v38 too : mpt3sas-38.00-Linux-v4.4.180+_DS3622xs+.zip Edit : FWIW I have a warning with v26 building : Don't know if this is revelant. Edited March 7, 2022 by Orphée Quote Link to comment Share on other sites More sharing options...
Atlas Posted March 7, 2022 Share #336 Posted March 7, 2022 (edited) I was wondering if there is any way to use drive 1 in DSM with LSI 9400-16i. If I use SataPortMap=1 and DiskIdxMap=00 in user_config.json it always skip drive 1 in DSM And if I do SataPortMap=58 and DiskIdxMap=0A00 it skips 1-5 disks I am using Vmware PCI passthrough 9400-16i and using boot loader on SATA(0:0) Also if I install DSM without LSI HBA it uses disk 1 with SataPortMap=58 and DiskIdxMap=0A00 but only shows 8 disk as I have attached 16 disk Was wondering what should be the SataPortMap and DiskIdxMap value with LSI 9400-16i, I don’t want it to skip disk 1 in DSM Edited March 7, 2022 by Atlas Quote Link to comment Share on other sites More sharing options...
Orphée Posted March 7, 2022 Share #337 Posted March 7, 2022 (edited) No one found how to do this yet. DiskIdxMap is ignored with cards passed through. @haydibe gave me a suggestion, but did not try it yet : Edited March 7, 2022 by Orphée Quote Link to comment Share on other sites More sharing options...
Orphée Posted March 8, 2022 Share #338 Posted March 8, 2022 (edited) Fun fact with DVA3221 loader. The Nvidia GPU is actually not needed to install Nvidia Runtime and Surveillance Station. Advanced AI functions are of course KO, but SS works like normal SS does on a NAS, and without the GPU, there is no more CPU high usage issue... The only issue is kern.log and messages flooded by "GPU not found". I remember there were a way to block logs flood with old Jun's loader with some regex rules but can't find where it was. Currently this loader could be an alternative to c****ed SS release for those who only need more licences. With CMS feature, you can even run more than one VM instance to have 8/16/24/etc... licences available... Tomorrow I should be able to diagnose my current issue with baremetal not starting (missing DB9 serial cable) Edited March 8, 2022 by Orphée 1 Quote Link to comment Share on other sites More sharing options...
Atlas Posted March 8, 2022 Share #339 Posted March 8, 2022 (edited) I digged further into the disk 1 slot and I found it was a known issue in DSM 6.2.3 however is DSM7.0.1 the boot loader disk is not showing in storage manager but is taking up disk 1 in the background Also in dmesg I can clearly see ata1 which should be hidden. Quote [ 4.444588] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 4.444627] ata1.00: ATA-6: VMware Virtual SATA Hard Drive, 00000001, max UDMA/100 [ 4.444636] ata1.00: 2097152 sectors, multi 0: LBA48 NCQ (depth 31/32) [ 4.444646] ata1.00: SN:00000000000000000001 [ 4.444686] ata1.00: configured for UDMA/100 [ 4.444726] ata1.00: Find SSD disks. [VMware Virtual SATA Hard Drive] [ 4.444908] scsi 0:0:0:0: Direct-Access VMware Virtual SATA Hard Drive 0001 PQ: 0 ANSI: 5 [ 4.444986] <redpill/scsi_notifier.c:65> Probing SCSI device using sd_probe_shim [ 4.445044] <redpill/scsi_notifier.c:77> Triggering SCSI_EVT_DEV_PROBING notifications [ 4.445080] <redpill/native_sata_boot_shim.c:153> Found new SCSI disk vendor="VMware Virtual 0001" model="Virtual SATA Hard Drive ": checking boot shim viability [ 4.445129] <redpill/boot_shim_base.c:34> Checking if SATA disk is a shim target - id=0 channel=0 vendor="VMware Virtual 0001" model="Virtual SATA Hard Drive " [ 4.445191] <redpill/boot_shim_base.c:56> Device has capacity of ~1024 MiB - it is a shimmable target (<=1024) [ 4.445268] <redpill/native_sata_boot_shim.c:124> Trying to shim SCSI device vendor="VMware Virtual 0001" model="Virtual SATA Hard Drive " [ 4.445359] <redpill/native_sata_boot_shim.c:133> Shimming device to vendor="SATADOM-" model="TYPE D 3SE" [ 4.445390] <redpill/scsi_notifier.c:87> Calling original sd_probe() [ 4.445455] <redpill/scsi_notifier.c:91> Triggering SCSI_EVT_DEV_PROBED notifications - sd_probe() exit=0 [ 4.445498] sd 0:0:0:0: [synoboot] 2097152 512-byte logical blocks: (1.07 GB/1.00 GiB) [ 4.445530] sd 0:0:0:0: [synoboot] Write Protect is off [ 4.445532] sd 0:0:0:0: [synoboot] Mode Sense: 00 3a 00 00 [ 4.445545] sd 0:0:0:0: [synoboot] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 4.445841] synoboot: synoboot1 synoboot2 synoboot3 [ 4.446089] sd 0:0:0:0: [synoboot] Attached SCSI disk [ 4.446496] Freeing unused kernel memory: 928K [ 4.446544] Write protecting the kernel read-only data: 8192k [ 4.446649] Freeing unused kernel memory: 592K [ 4.446955] Freeing unused kernel memory: 312K [ 4.473628] ACPI: bus type USB registered [ 4.473688] usbcore: registered new interface driver usbfs [ 4.473739] usbcore: registered new interface driver hub [ 4.473795] usbcore: registered new interface driver ethub [ 4.473856] usbcore: registered new device driver usb [ 4.477658] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 4.479119] ehci-pci: EHCI PCI platform driver [ 4.487608] usbcore: registered new interface driver usb-storage [ 4.490599] mpt3sas version 41.00.00.00 loaded [ 4.490923] mpt3sas_cm0: 63 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (4012796 kB) [ 4.567585] mpt3sas_cm0: IOC Number : 0 [ 4.568589] mpt3sas0-msix0: PCI-MSI-X enabled: IRQ 57 [ 4.568599] mpt3sas0-msix1: PCI-MSI-X enabled: IRQ 58 [ 4.568609] mpt3sas0-msix2: PCI-MSI-X enabled: IRQ 59 [ 4.568618] mpt3sas0-msix3: PCI-MSI-X enabled: IRQ 60 [ 4.568628] mpt3sas_cm0: iomem(0x00000000e7900000), mapped(0xffffc90000400000), size(1048576) [ 4.568638] mpt3sas_cm0: ioport(0x0000000000004000), size(256) [ 4.644584] mpt3sas_cm0: IOC Number : 0 [ 4.680592] mpt3sas_cm0: scatter gather: sge_in_main_msg(0), sge_per_chain(7), sge_per_io(128), chains_per_io(19) [ 4.680601] mpt3sas_cm0: request pool(0xffff880134900000) - dma(0x134900000): depth(6756), frame_size(128), pool_size(844 kB) [ 4.777602] mpt3sas_cm0: sense pool(0xffff8800b7100000) - dma(0xb7100000): depth(6551), element_size(96), pool_size (614 kB) [ 4.777612] mpt3sas_cm0: reply pool(0xffff880134a00000) - dma(0x134a00000): depth(6820)frame_size(128), pool_size(852 kB) [ 4.777622] mpt3sas_cm0: config page(0xffff8800b7d4b000) - dma(0xb7d4b000): size(512) [ 4.777631] mpt3sas_cm0: Allocated physical memory: size(28966 kB) [ 4.777641] mpt3sas_cm0: Current Controller Queue Depth(6548), Max Controller Queue Depth(6656) [ 4.835637] mpt3sas_cm0: FW Package Version(22.00.00.00) [ 4.836180] mpt3sas_cm0: SAS3416: FWVersion(22.00.00.00), ChipRevision(0x01) [ 4.836189] mpt3sas_cm0: Protocol=(Initiator,Target,NVMe), Capabilities=(TLR,EEDP,Diag Trace Buffer,Task Set Full,NCQ) [ 4.836402] mpt3sas_cm0: : host protection capabilities enabled DIF1 DIF2 DIF3 [ 4.836412] scsi host1: Fusion MPT SAS Host [ 4.836647] mpt3sas_cm0: registering trace buffer support [ 4.839604] mpt3sas_cm0: Trace buffer memory 2048 KB allocated [ 4.839614] mpt3sas_cm0: sending port enable !! [ 4.839848] mpt3sas_cm0: hba_port entry: ffff8800b4f15600, port: 0 is added to hba_port list [ 4.840014] mpt3sas_cm0: hba_port entry: ffff8800b4f15740, port: 1 is added to hba_port list [ 4.840213] mpt3sas_cm0: hba_port entry: ffff8800b4f15780, port: 2 is added to hba_port list [ 4.840430] mpt3sas_cm0: hba_port entry: ffff8800b4f157c0, port: 3 is added to hba_port list [ 4.840631] mpt3sas_cm0: hba_port entry: ffff8800b4f15800, port: 4 is added to hba_port list [ 4.840860] mpt3sas_cm0: hba_port entry: ffff8800b4f15840, port: 5 is added to hba_port list [ 4.841042] mpt3sas_cm0: hba_port entry: ffff8800b4f15880, port: 6 is added to hba_port list [ 4.841267] mpt3sas_cm0: hba_port entry: ffff8800b4f158c0, port: 7 is added to hba_port list [ 4.841508] mpt3sas_cm0: hba_port entry: ffff8800b4f15900, port: 8 is added to hba_port list [ 4.841999] mpt3sas_cm0: hba_port entry: ffff8800b4f15940, port: 9 is added to hba_port list [ 4.842332] mpt3sas_cm0: hba_port entry: ffff8800b4f15980, port: 10 is added to hba_port list [ 4.842670] mpt3sas_cm0: hba_port entry: ffff8800b4f159c0, port: 11 is added to hba_port list [ 4.842896] mpt3sas_cm0: vphy entry: ffff8800b864c880, port id: 0, phy:16 is added to port's vphys_list [ 4.843521] mpt3sas_cm0: host_add: handle(0x0001), sas_addr(0x500605b0106daae0), phys(21) [ 4.844451] mpt3sas_cm0: handle(0x17) sas_address(0x5000c50095257681) port_type(0x1) [ 4.844654] mpt3sas_cm0: handle(0x1a) sas_address(0x5000c5009525989d) port_type(0x1) [ 4.844844] mpt3sas_cm0: handle(0x1b) sas_address(0x5000c50095258915) port_type(0x1) [ 4.845001] mpt3sas_cm0: handle(0x1c) sas_address(0x5000c50095257671) port_type(0x1) [ 4.845173] mpt3sas_cm0: handle(0x1d) sas_address(0x5000c5009523199d) port_type(0x1) [ 4.845410] mpt3sas_cm0: handle(0x1f) sas_address(0x5000c5009525378d) port_type(0x1) [ 4.845600] mpt3sas_cm0: handle(0x1e) sas_address(0x5000c50095257d4d) port_type(0x1) [ 4.845775] mpt3sas_cm0: handle(0x20) sas_address(0x5000c5009519be7d) port_type(0x1) [ 4.845942] mpt3sas_cm0: handle(0x18) sas_address(0x300605b0106daae9) port_type(0x1) [ 4.846121] mpt3sas_cm0: handle(0x19) sas_address(0x300605b0106daaeb) port_type(0x1) [ 4.846301] mpt3sas_cm0: handle(0x21) sas_address(0x300605b0106daaed) port_type(0x1) [ 4.846483] mpt3sas_cm0: handle(0x22) sas_address(0x300605b0106daaef) port_type(0x1) [ 4.847336] mpt3sas_cm0: handle(0x11) sas_address(0x300705b0106daae0) port_type(0x0) Quote root@NAS:~# fdisk -l /dev/synoboot Disk /dev/synoboot: 1 GiB, 1073741824 bytes, 2097152 sectors Disk model: TYPE D 3SE Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xf110ee87 Device Boot Start End Sectors Size Id Type /dev/synoboot1 * 2048 100351 98304 48M 83 Linux /dev/synoboot2 100352 253951 153600 75M 83 Linux /dev/synoboot3 253952 2097151 1843200 900M 83 Linux I think we need a script or find a way to hide synoboot from DSM so disk 1 slot can be used. Edited March 8, 2022 by Atlas Quote Link to comment Share on other sites More sharing options...
synoxpe Posted March 9, 2022 Share #340 Posted March 9, 2022 (edited) Anyone got the Virtual Machine Manager to boot a Windows VM on ds3622xs+? I'm on a bare metal installation and when I power the VM on, I see the Windows logo appearing very shortly followed by a blank screen with a blinking cursor. Nothing happens further. @yanjun perhaps you've tested this? Edit: system is too slow and I was being impatient. Working now Edited March 9, 2022 by synoxpe Quote Link to comment Share on other sites More sharing options...
Orphée Posted March 9, 2022 Share #341 Posted March 9, 2022 (edited) Hi guys ! DVA3221 loader update : Actually, Face Detection and Deep Video Analysis works (as long as you have a real SN/MAC I think) ! I had an issue/missconfiguration with PCI-e passthrough I had to add this in proxmox grub configuration : GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on iommu=pt pcie_acs_override=downstream,multifunction video=efifb:off" (details here : https://pve.proxmox.com/wiki/Pci_passthrough) # nvidia-smi Wed Mar 9 11:56:39 2022 +-----------------------------------------------------------------------------+ | NVIDIA-SMI 440.44 Driver Version: 440.44 CUDA Version: 10.2 | |-------------------------------+----------------------+----------------------+ | GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | |===============================+======================+======================| | 0 GeForce GTX 1650 On | 00000000:01:00.0 Off | N/A | | 30% 42C P0 32W / 75W | 1841MiB / 3911MiB | 29% Default | +-------------------------------+----------------------+----------------------+ +-----------------------------------------------------------------------------+ | Processes: GPU Memory | | GPU PID Type Process name Usage | |=============================================================================| | 0 19689 C ...anceStation/target/synodva/bin/synodvad 888MiB | | 0 19690 C ...ceStation/target/synoface/bin/synofaced 942MiB | +-----------------------------------------------------------------------------+ tagging @IG-88 for info Edited March 9, 2022 by Orphée 3 Quote Link to comment Share on other sites More sharing options...
synoxpe Posted March 9, 2022 Share #342 Posted March 9, 2022 Anyway to get rid of this while Plex is running? ds3622xsp running on bare metal Intel i7: @yanjun [ 671.949626] CPU9: Core temperature above threshold, cpu clock throttled (total events = 4642) [ 671.949626] CPU3: Core temperature above threshold, cpu clock throttled (total events = 4642) [ 671.949626] CPU2: Core temperature above threshold, cpu clock throttled (total events = 8533) [ 671.949626] CPU8: Core temperature above threshold, cpu clock throttled (total events = 8533) [ 671.949627] CPU1: Package temperature above threshold, cpu clock throttled (total events = 19575) [ 671.949627] CPU6: Package temperature above threshold, cpu clock throttled (total events = 19575) [ 671.949627] CPU7: Package temperature above threshold, cpu clock throttled (total events = 19575) [ 671.949627] CPU5: Package temperature above threshold, cpu clock throttled (total events = 19575) [ 671.949628] CPU0: Package temperature above threshold, cpu clock throttled (total events = 19575) [ 671.949628] CPU4: Package temperature above threshold, cpu clock throttled (total events = 19575) [ 671.949628] CPU11: Package temperature above threshold, cpu clock throttled (total events = 19575) [ 671.949628] CPU10: Package temperature above threshold, cpu clock throttled (total events = 19575) [ 671.949628] CPU3: Package temperature above threshold, cpu clock throttled (total events = 19575) [ 671.949629] CPU2: Package temperature above threshold, cpu clock throttled (total events = 19574) [ 671.949629] CPU8: Package temperature above threshold, cpu clock throttled (total events = 19575) Quote Link to comment Share on other sites More sharing options...
Orphée Posted March 9, 2022 Share #343 Posted March 9, 2022 Anyway to get rid of this while Plex is running? ds3622xsp running on bare metal Intel i7: @yanjun[ 671.949626] CPU9: Core temperature above threshold, cpu clock throttled (total events = 4642)[ 671.949626] CPU3: Core temperature above threshold, cpu clock throttled (total events = 4642)[ 671.949626] CPU2: Core temperature above threshold, cpu clock throttled (total events = 8533)[ 671.949626] CPU8: Core temperature above threshold, cpu clock throttled (total events = 8533)[ 671.949627] CPU1: Package temperature above threshold, cpu clock throttled (total events = 19575)[ 671.949627] CPU6: Package temperature above threshold, cpu clock throttled (total events = 19575)[ 671.949627] CPU7: Package temperature above threshold, cpu clock throttled (total events = 19575)[ 671.949627] CPU5: Package temperature above threshold, cpu clock throttled (total events = 19575)[ 671.949628] CPU0: Package temperature above threshold, cpu clock throttled (total events = 19575)[ 671.949628] CPU4: Package temperature above threshold, cpu clock throttled (total events = 19575)[ 671.949628] CPU11: Package temperature above threshold, cpu clock throttled (total events = 19575)[ 671.949628] CPU10: Package temperature above threshold, cpu clock throttled (total events = 19575)[ 671.949628] CPU3: Package temperature above threshold, cpu clock throttled (total events = 19575)[ 671.949629] CPU2: Package temperature above threshold, cpu clock throttled (total events = 19574)[ 671.949629] CPU8: Package temperature above threshold, cpu clock throttled (total events = 19575) Does your plex transcode ?Because if CPU temp thresold happens, you CPU must run high...Check with "top" command Quote Link to comment Share on other sites More sharing options...
synoxpe Posted March 9, 2022 Share #344 Posted March 9, 2022 1 hour ago, Orphée said: Does your plex transcode ? Because if CPU temp thresold happens, you CPU must run high... Check with "top" command Yes it does. But DSM shows max CPU usage just to be 45%, guess because of the throttling… how to get rid of that? Quote Link to comment Share on other sites More sharing options...
Orphée Posted March 9, 2022 Share #345 Posted March 9, 2022 3 minutes ago, synoxpe said: Yes it does. But DSM shows max CPU usage just to be 45%, guess because of the throttling… how to get rid of that? WIthout HW transcoding, you won't. This is where HW transcoding topics with DS918+ comes from. I did not check if HW transcoding is available on DS3622xs+ Quote Link to comment Share on other sites More sharing options...
IG-88 Posted March 9, 2022 Share #346 Posted March 9, 2022 1 hour ago, Orphée said: I did not check if HW transcoding is available on DS3622xs+ Intel Xeon D-1531, no iGPU and that goes for all units that are broadwellnk no intel gpu driver in that image and its unclear if its even possible to add that one, might end like hyper-v support (missing kernel part in syno's kernel) i have not checked that yet 2 Quote Link to comment Share on other sites More sharing options...
synoxpe Posted March 9, 2022 Share #347 Posted March 9, 2022 On 3/7/2022 at 10:51 AM, yanjun said: The only reason you can't see the smart information is that the driver is too new and the device is too old, mpt3sas41.0 is prepared for LSI 9400/9500, I also tried to extract mpt3sas21.0 (from LSI 9207) official driver page, unfortunately It's that he can't mix with the hard disk of the sata controller to form a raid1. Probably this version of mpt3sas is too old for the 4.4.180 kernel. This means that your system partition is always in a state that needs to be repaired, and once you repair it, your dsm will directly show that you need to reinstall it. My LSI9400-16I on 3622xs+ has no issue with missing smart info. So if you guys want to try to solve the smart information problem with LSI 92xx cards. My suggestion is to try to find the driver of the LSI 9300 series card from the official boradcom, and try to compile it between 21.0 and 41.0. Maybe a certain version can satisfy both the smart information and the two conditions of creating a system partition. @yanjun I doubt as the same disks do provide that info on DS918+. noop generally means no-operation. So I guess the "ATA_CMD_ID_ATA" command is not implemented in the red pill shim. Could be a bug? Quote Link to comment Share on other sites More sharing options...
msy999 Posted March 10, 2022 Share #348 Posted March 10, 2022 ds3622xs+ 7.0.1 Update 2 or Update 3 infinite restore How do I solve it? Quote Link to comment Share on other sites More sharing options...
msy999 Posted March 10, 2022 Share #349 Posted March 10, 2022 Is the loader update being improved? Quote Link to comment Share on other sites More sharing options...
RacerX Posted March 10, 2022 Share #350 Posted March 10, 2022 Just a Test with the new module Chelsio T520-CR sudo ./rploader.sh ext bromolow-7.0.1-42218 add https://raw.githubusercontent.com/pocopico/rp-ext/master/cxgb4/rpext-index.json The module seems to load correctly [OK] [#] ========================================== pocopico.cxgb4 ================== ======================== [#] Extension name: cxgb4 [#] Description: Adds Chelsio T4/T5/T6 Network Driver Support [#] To get help visit: <todo> [#] Extension preparer/packer: https://github.com/pocopico/rp-ext/tree/main/cxgb 4 [#] Software author: https://github.com/pocopico [#] Update URL: https://raw.githubusercontent.com/pocopico/rp-ext/master/cxgb4/r pext-index.json [#] Platforms supported: ds1621p_42218 ds918p_41890 ds3617xs_42218 ds918p_25556 dva3221_42218 ds3622xsp_42218 ds3615xs_41222 ds3615xs_25556 ds918p_42218 ds3615x s_42218 [#] ============================================================================ =========== ssh into tinycore tc@box:~$ uname -r 5.10.3-tinycore64 It works fine in tinycore except the firmware is old tc@box:~$ dmesg |grep cxgb4 [ 1.204078] cxgb4 0000:01:00.4: Direct firmware load for cxgb4/t5fw.bin failed with error -2 [ 1.204080] cxgb4 0000:01:00.4: Falling back to sysfs fallback for: cxgb4/t5f w.bin [ 1.207705] cxgb4 0000:01:00.4: unable to load firmware image cxgb4/t5fw.bin, error -11 [ 1.207942] cxgb4 0000:01:00.4: Coming up as MASTER: Initializing adapter [ 1.897496] cxgb4 0000:01:00.4: Direct firmware load for cxgb4/t5-config.txt failed with error -2 [ 1.897502] cxgb4 0000:01:00.4: Falling back to sysfs fallback for: cxgb4/t5-config.txt [ 2.424116] cxgb4 0000:01:00.4: Successfully configured using Firmware Configuration File "Firmware Default", version 0x0, computed checksum 0x0 [ 2.594109] cxgb4 0000:01:00.4: Hash filter supported only on T6 [ 2.644117] cxgb4 0000:01:00.4: max_ordird_qp 21 max_ird_adapter 387072 [ 2.684118] cxgb4 0000:01:00.4: Current filter mode/mask 0x632b:0x21 [ 2.750065] cxgb4 0000:01:00.4: 62 MSI-X vectors allocated, nic 12 eoqsets 12 per uld 6 mirrorqsets 12 [ 2.750081] cxgb4 0000:01:00.4: 63.008 Gb/s available PCIe bandwidth (8.0 GT/s PCIe x8 link) [ 2.779388] cxgb4 0000:01:00.4 eth0: eth0: Chelsio T520-CR (0000:01:00.4) 1G/10GBASE-SFP [ 2.780246] cxgb4 0000:01:00.4 eth1: eth1: Chelsio T520-CR (0000:01:00.4) 1G/10GBASE-SFP [ 2.817487] cxgb4 0000:01:00.4: Chelsio T520-CR rev 0 [ 2.817493] cxgb4 0000:01:00.4: S/N: PT03151028, P/N: 110118250B0 [ 2.817498] cxgb4 0000:01:00.4: Firmware version: 1.24.17.0 [ 2.817502] cxgb4 0000:01:00.4: Bootstrap version: 1.1.0.0 [ 2.817506] cxgb4 0000:01:00.4: TP Microcode version: 0.1.4.9 [ 2.817510] cxgb4 0000:01:00.4: Expansion ROM version: 1.0.0.68 [ 2.817514] cxgb4 0000:01:00.4: Serial Configuration version: 0x1005000 [ 2.817517] cxgb4 0000:01:00.4: VPD version: 0x2 [ 2.817521] cxgb4 0000:01:00.4: Configuration: RNIC MSI-X, Offload capable [ 27.104114] cxgb4 0000:01:00.4 eth0: passive DA module inserted [ 27.680816] cxgb4 0000:01:00.4 eth1: port module unplugged [ 27.706482] cxgb4 0000:01:00.4 eth0: link up, 10Gbps, full-duplex, Tx/Rx PAUS E tc@box:~$ When I boot usb I get a red light on the back of the card (not initialized) Is this a firmware thing? https://service.chelsio.com/store2/T5/Unified Wire/Linux/ChelsioUwire-3.16.0.0/README.txt The firmware (v1.26.6.0) is installed on the system, typically in /lib/firmware/cxgb4, and the driver will auto-load the firmware if an update is required. The kernel must be configured to enable userspace firmware loading support. Device Drivers -> Generic Driver Options -> Userspace firmware loading support Any advise? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.