NooL Posted August 22, 2022 Share #551 Posted August 22, 2022 Anyone seen this error before? Quote Link to comment Share on other sites More sharing options...
iansc Posted August 22, 2022 Share #552 Posted August 22, 2022 On 7/1/2022 at 4:45 PM, fbelavenuto said: Hello everyone, I would like to share a personal project that I am developing. It is another loader for TTG Redpill, intended to be as automatic and user-friendly as possible. The link is below, download the image and record it on a flash drive, the rest is done on the same computer. I'm Brazilian and I'm not good at English language, so forgive me for translation errors. I used forum knowledge and code from various loaders developed by TTG, pocopico, jumkey, Jun and many others. Hope you like it. https://github.com/fbelavenuto/arpl Edit: An important information that I forgot to mention is that I developed a simple patch to no longer display the DUMMY port error on models without device-tree, the user will be able to install without having to worry about it Hi man. I'm Brazilian too. I'm using version 0.4-alpha3 on the barematel and everything is working perfectly. Running the DVA1622. If you need help with testing, I'm available 1 Quote Link to comment Share on other sites More sharing options...
blindspot Posted August 23, 2022 Share #553 Posted August 23, 2022 Hi fbelavenuto, Please, can you help with atheros ar8131 addon? I have IP while building the loader for v1000-42218, but no IP after. Thank you very much. 1 Quote Link to comment Share on other sites More sharing options...
blindspot Posted August 23, 2022 Share #554 Posted August 23, 2022 (edited) db post Edited August 23, 2022 by blindspot Quote Link to comment Share on other sites More sharing options...
tooobe Posted August 23, 2022 Share #555 Posted August 23, 2022 (edited) I have a server running DSM 6 on a i7 4770k server emulating 918+ Would it be easy for me to use this tool/guide to update to DSM 7 without too much difficulty or risk to my data? I'm pretty tech savvy but would prefer for nothing to go wrong. Edited August 23, 2022 by tooobe Quote Link to comment Share on other sites More sharing options...
kekesed97 Posted August 23, 2022 Share #556 Posted August 23, 2022 32 minutes ago, tooobe said: I have a server running DSM 6 on a i7 4770k server emulating 918+ Would it be easy for me to use this tool/guide to update to DSM 7 without too much difficulty or risk to my data? I'm pretty tech savvy but would prefer for nothing to go wrong. I think it's pretty safe to upgrade. I've upgraded from Jun's 1.03b to redpill without a hitch sometime ago. But to be extra safe, you can emulate your current confing using different USB and HDD or VM and see if the update will work for you. 1 Quote Link to comment Share on other sites More sharing options...
fbelavenuto Posted August 24, 2022 Author Share #557 Posted August 24, 2022 On 8/23/2022 at 10:39 AM, blindspot said: Hi fbelavenuto, Please, can you help with atheros ar8131 addon? I have IP while building the loader for v1000-42218, but no IP after. Thank you very much. Please type the command "lspci -nnk" into ARPL shell and post the results. Quote Link to comment Share on other sites More sharing options...
mmkt Posted August 24, 2022 Share #558 Posted August 24, 2022 @fbelavenuto Hi, 0.4a4 is the first version which is working again with HP microserver gen8. 😀👍🤗 I testet with embedded Broadcom NIC only, Intel e1000e NIC only and both active. All combinations are working! The cmdline parameter netif_num is the amount of all network cards or ports? I used 2 and the loader corrected it to four with both dualport nics active. Great work and thanks for your patience! mmkt Quote Link to comment Share on other sites More sharing options...
fbelavenuto Posted August 24, 2022 Author Share #559 Posted August 24, 2022 3 minutes ago, mmkt said: @fbelavenuto Hi, 0.4a4 is the first version which is working again with HP microserver gen8. 😀👍🤗 I testet with embedded Broadcom NIC only, Intel e1000e NIC only and both active. All combinations are working! The cmdline parameter netif_num is the amount of all network cards or ports? I used 2 and the loader corrected it to four with both dualport nics active. Great work and thanks for your patience! mmkt Seriously? So it was something to do with the drivers as I didn't change anything in particular. netif_num is the number of ethernet ports, so for you must have the value 4. Quote Link to comment Share on other sites More sharing options...
mmkt Posted August 24, 2022 Share #560 Posted August 24, 2022 I use the same hardware, did the same, started all over with rewriting the arpl.img to the usb stick and deleting the partitions on the ssd disk. Only difference may be that one additional HDD was on port 3. But now I can format the disks and install DSM and do not end up in a boot loop. Maybe the change "eudev" Or what is for? Quote Link to comment Share on other sites More sharing options...
Green Posted August 24, 2022 Share #561 Posted August 24, 2022 To fbelavenuto , Excellent Thank You Bare metal install Dell Precision T1700 i7-4790 These are made to hold four hard drives. Installing DS 918+ with Automated redpill loader made everything so simple. Installed perfect on first attempt 1 1 Quote Link to comment Share on other sites More sharing options...
vinhnguyen Posted August 25, 2022 Share #562 Posted August 25, 2022 @fbelavenuto Can you add e1000e for DS3622xs ? Quote Link to comment Share on other sites More sharing options...
blindspot Posted August 25, 2022 Share #563 Posted August 25, 2022 (edited) 16 hours ago, fbelavenuto said: Please type the command "lspci -nnk" into ARPL shell and post the results. 01:00.0 Ethernet controller [0200]: Qualcomm Atheros AR8131 Gigabit Ethernet [1969:1063] (rev c0) Subsystem: Device [104d:9082] Kernel driver in use: atl1c 02:00.0 Network controller [0280]: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) [168c:002b] (rev 01) Subsystem: Device [105b:e017] 01:00.0 Ethernet controller [0200]: Qualcomm Atheros AR8131 Gigabit Ethernet [1969:1063] (rev c0) 02:00.0 Network controller [0280]: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) [168c:002b] (rev 01) Edited August 25, 2022 by blindspot Quote Link to comment Share on other sites More sharing options...
beefyjoe Posted August 26, 2022 Share #564 Posted August 26, 2022 Howdy, I just found this tool today and thought that it was my saving grace, had Jun's loader setup as DS3617xs on a Lenovo y410p laptop witha mediasonic probox 4 bay the new 2022 version as an external USB enclosure for the drives, since they obviously wont fit in the laptop. This was rock solid. had going for 2 weeks uptime after initial install. Was trying to get DSM 7.1 installed with regular TCRP but ran into the Bad Ports issue, so I found the automated loader since it resolves that for me. I was able to get it setup and working no problems, I switched my build to a DS918+ since it seems a better match for my hardware (i7-4800mq 4core core 8 thread, 8GB RAM, Haswell, which should support apollolake according to sheet) Everything also seemed fine after install, it migrated my RAID 5 Array of 3 14TB drives in the MediaSonic USb enclosure, and I was also able to setup SSD cache as well with 2 internal 120GB SATA SSDs. I was able to get all these listed and identified by the computer by modifying the user config json so that everything was an internal port Internalportcfg: "0xffffffffff" esataportcfg: "0" usbportcfg: "0" This is also what i had to do on the DS3617xs build with jun's loader to get it to work with the usb drive enclosure. The problem happened after I rebooted. The system did not go back to DSM... i had no idea what was going on and thought to open the Synology assistant app. Lo and behlod, there is the DSM 7.1 machine now saying that DSM is not installed, and going to find.synology.com starts the installation process all over again. Looking for some help in getting this fixed... I have tried rebuilding the loader with arcl but it seems that now every DSM release from Synology that I am trying to install is corrupted. Should I update to 7.1.1 ? This seems like a bad idea considering its still only RC and arcl itself is in alpha... I tried looking through the forums and google already but there were only a couple of mentions of this problem with other users and they did not receive answers. Quote Link to comment Share on other sites More sharing options...
neonflx Posted August 27, 2022 Share #565 Posted August 27, 2022 anyone has any ideas why the internal sata ports on a X10SDV-6C+-TLN4F are not recognized by ARPL? I can build and load the loader, find it but every time it says no hard drives detected any suggestions? Quote Link to comment Share on other sites More sharing options...
mmkt Posted August 30, 2022 Share #566 Posted August 30, 2022 On 8/25/2022 at 2:52 AM, vinhnguyen said: @fbelavenuto Can you add e1000e for DS3622xs ? it's included, my intel NIC use the same driver and it works... Quote Link to comment Share on other sites More sharing options...
fbelavenuto Posted August 30, 2022 Author Share #567 Posted August 30, 2022 On 8/25/2022 at 10:59 PM, beefyjoe said: I have tried rebuilding the loader with arcl but it seems that now every DSM release from Synology that I am trying to install is corrupted Check if .pat file is correct, the filename has the format "DSM_<model>_42661.pat" and the filesize is more or less 350MB Quote Link to comment Share on other sites More sharing options...
fbelavenuto Posted August 30, 2022 Author Share #568 Posted August 30, 2022 On 8/27/2022 at 1:01 PM, neonflx said: anyone has any ideas why the internal sata ports on a X10SDV-6C+-TLN4F are not recognized by ARPL? I can build and load the loader, find it but every time it says no hard drives detected any suggestions? Please type into loader: lspci -nnk And post the results Quote Link to comment Share on other sites More sharing options...
nemesis122 Posted August 30, 2022 Share #569 Posted August 30, 2022 Hi Thank you for this great Loader it was sucessfully by the first try in VMM . Is there en img file generated by this loader for future use ? thank you very much Michael Quote Link to comment Share on other sites More sharing options...
vinhnguyen Posted August 31, 2022 Share #570 Posted August 31, 2022 19 hours ago, mmkt said: it's included, my intel NIC use the same driver and it works... My Intel I219-LM it doesn't work. Main Gigabyte W480M. Quote Link to comment Share on other sites More sharing options...
mmkt Posted August 31, 2022 Share #571 Posted August 31, 2022 i found this information: Klick The device is supported by kernel versions 4.12 an newer. I don't exactly know which kernel we are using at DSM 7 but pocopicos modules are for 4.4.180. Maybe this is the reason why your card isn't working. Quote Link to comment Share on other sites More sharing options...
neonflx Posted August 31, 2022 Share #572 Posted August 31, 2022 00:00.0 Host bridge [0600]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DMI2 [8086:6f00] (rev 03) Subsystem: Super Micro Computer Inc Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DMI2 [15d9:086d] 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 1 [8086:6f02] (rev 03) Kernel driver in use: pcieport 00:02.0 PCI bridge [0604]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 2 [8086:6f04] (rev 03) Kernel driver in use: pcieport 00:02.2 PCI bridge [0604]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 2 [8086:6f06] (rev 03) Kernel driver in use: pcieport 00:03.0 PCI bridge [0604]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 3 [8086:6f08] (rev 03) Kernel driver in use: pcieport 00:03.1 PCI bridge [0604]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 3 [8086:6f09] (rev 03) Kernel driver in use: pcieport 00:03.2 PCI bridge [0604]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 3 [8086:6f0a] (rev 03) Kernel driver in use: pcieport 00:03.3 PCI bridge [0604]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 3 [8086:6f0b] (rev 03) Kernel driver in use: pcieport 00:05.0 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Map/VTd_Misc/System Management [8086:6f28] (rev 03) Subsystem: Super Micro Computer Inc Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Map/VTd_Misc/System Management [15d9:086d] 00:05.1 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D IIO Hot Plug [8086:6f29] (rev 03) Subsystem: Super Micro Computer Inc Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D IIO Hot Plug [15d9:086d] 00:05.2 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D IIO RAS/Control Status/Global Errors [8086:6f2a] (rev 03) Subsystem: Super Micro Computer Inc Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D IIO RAS/Control Status/Global Errors [15d9:086d] 00:14.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI [8086:8c31] (rev 05) Subsystem: Super Micro Computer Inc 8 Series/C220 Series Chipset Family USB xHCI [15d9:086d] Kernel driver in use: xhci_hcd 00:16.0 Communication controller [0780]: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 [8086:8c3a] (rev 04) Subsystem: Super Micro Computer Inc 8 Series/C220 Series Chipset Family MEI Controller [15d9:086d] 00:16.1 Communication controller [0780]: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #2 [8086:8c3b] (rev 04) Subsystem: Super Micro Computer Inc 8 Series/C220 Series Chipset Family MEI Controller [15d9:086d] 00:1a.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 [8086:8c2d] (rev 05) Subsystem: Super Micro Computer Inc 8 Series/C220 Series Chipset Family USB EHCI [15d9:086d] Kernel driver in use: ehci-pci 00:1c.0 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 [8086:8c10] (rev d5) Kernel driver in use: pcieport 00:1c.4 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #5 [8086:8c18] (rev d5) Kernel driver in use: pcieport 00:1d.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 [8086:8c26] (rev 05) Subsystem: Super Micro Computer Inc 8 Series/C220 Series Chipset Family USB EHCI [15d9:086d] Kernel driver in use: ehci-pci 00:1f.0 ISA bridge [0601]: Intel Corporation C224 Series Chipset Family Server Standard SKU LPC Controller [8086:8c54] (rev 05) Subsystem: Super Micro Computer Inc C224 Series Chipset Family Server Standard SKU LPC Controller [15d9:086d] 00:1f.3 SMBus [0c05]: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller [8086:8c22] (rev 05) Subsystem: Super Micro Computer Inc 8 Series/C220 Series Chipset Family SMBus Controller [15d9:086d] Kernel driver in use: i801_smbus 00:1f.6 Signal processing controller [1180]: Intel Corporation 8 Series Chipset Family Thermal Management Controller [8086:8c24] (rev 05) Subsystem: Super Micro Computer Inc 8 Series Chipset Family Thermal Management Controller [15d9:086d] 01:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961 [144d:a804] Subsystem: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961/SM963 (SM963 2.5" NVMe PCIe SSD) [144d:a801] Kernel driver in use: nvme 02:00.0 System peripheral [0880]: Intel Corporation Xeon Processor D Family QuickData Technology Register DMA Channel 0 [8086:6f50] Subsystem: Super Micro Computer Inc Xeon Processor D Family QuickData Technology Register DMA Channel 0 [15d9:086d] 02:00.1 System peripheral [0880]: Intel Corporation Xeon Processor D Family QuickData Technology Register DMA Channel 1 [8086:6f51] Subsystem: Super Micro Computer Inc Xeon Processor D Family QuickData Technology Register DMA Channel 1 [15d9:086d] 02:00.2 System peripheral [0880]: Intel Corporation Xeon Processor D Family QuickData Technology Register DMA Channel 2 [8086:6f52] Subsystem: Super Micro Computer Inc Xeon Processor D Family QuickData Technology Register DMA Channel 2 [15d9:086d] 02:00.3 System peripheral [0880]: Intel Corporation Xeon Processor D Family QuickData Technology Register DMA Channel 3 [8086:6f53] Subsystem: Super Micro Computer Inc Xeon Processor D Family QuickData Technology Register DMA Channel 3 [15d9:086d] 03:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection X552/X557-AT 10GBASE-T [8086:15ad] DeviceName: Intel X557-AT2 Ethernet #1 Subsystem: Super Micro Computer Inc Ethernet Connection X552/X557-AT 10GBASE-T [15d9:15ad] Kernel driver in use: ixgbe Kernel modules: ixgbe 03:00.1 Ethernet controller [0200]: Intel Corporation Ethernet Connection X552/X557-AT 10GBASE-T [8086:15ad] DeviceName: Intel X557-AT2 Ethernet #2 Subsystem: Super Micro Computer Inc Ethernet Connection X552/X557-AT 10GBASE-T [15d9:15ad] Kernel driver in use: ixgbe Kernel modules: ixgbe 07:00.0 Serial Attached SCSI controller [0107]: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] [1000:0072] (rev 03) Subsystem: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] [1000:3020] Kernel driver in use: mpt3sas Kernel modules: mpt3sas 08:00.0 Ethernet controller [0200]: Intel Corporation I350 Gigabit Network Connection [8086:1521] (rev 01) DeviceName: Intel i350 Ethernet #1 Subsystem: Super Micro Computer Inc I350 Gigabit Network Connection [15d9:1521] Kernel driver in use: igb Kernel modules: igb 08:00.1 Ethernet controller [0200]: Intel Corporation I350 Gigabit Network Connection [8086:1521] (rev 01) DeviceName: Intel i350 Ethernet #2 Subsystem: Super Micro Computer Inc I350 Gigabit Network Connection [15d9:1521] Kernel driver in use: igb Kernel modules: igb 09:00.0 PCI bridge [0604]: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge [1a03:1150] (rev 03) 0a:00.0 VGA compatible controller [0300]: ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 30) DeviceName: ASPEED Video AST2400 Subsystem: Super Micro Computer Inc ASPEED Graphics Family [15d9:086d] ff:0b.0 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link 0/1 [8086:6f81] (rev 03) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link 0/1 [8086:6f81] ff:0b.1 Performance counters [1101]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link 0/1 [8086:6f36] (rev 03) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link 0/1 [8086:6f36] Kernel driver in use: bdx_uncore ff:0b.2 Performance counters [1101]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link 0/1 [8086:6f37] (rev 03) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link 0/1 [8086:6f37] Kernel driver in use: bdx_uncore ff:0b.3 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link Debug [8086:6f76] (rev 03) ff:0c.0 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6fe0] (rev 03) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6fe0] ff:0c.1 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6fe1] (rev 03) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6fe1] ff:0c.2 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6fe2] (rev 03) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6fe2] ff:0c.3 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6fe3] (rev 03) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6fe3] ff:0c.4 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6fe4] (rev 03) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6fe4] ff:0c.5 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6fe5] (rev 03) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6fe5] ff:0f.0 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6ff8] (rev 03) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6ff8] ff:0f.4 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6ffc] (rev 03) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6fe0] ff:0f.5 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6ffd] (rev 03) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6fe0] ff:0f.6 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6ffe] (rev 03) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6fe0] ff:10.0 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R2PCIe Agent [8086:6f1d] (rev 03) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R2PCIe Agent [8086:6f1d] ff:10.1 Performance counters [1101]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R2PCIe Agent [8086:6f34] (rev 03) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R2PCIe Agent [8086:6f34] Kernel driver in use: bdx_uncore ff:10.5 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Ubox [8086:6f1e] (rev 03) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Ubox [8086:6f1e] ff:10.6 Performance counters [1101]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Ubox [8086:6f7d] (rev 03) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Ubox [8086:6f7d] ff:10.7 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Ubox [8086:6f1f] (rev 03) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Ubox [8086:6f1f] ff:12.0 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Home Agent 0 [8086:6fa0] (rev 03) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Home Agent 0 [8086:6fa0] ff:12.1 Performance counters [1101]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Home Agent 0 [8086:6f30] (rev 03) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Home Agent 0 [8086:6f30] Kernel driver in use: bdx_uncore ff:13.0 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Target Address/Thermal/RAS [8086:6fa8] (rev 03) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Target Address/Thermal/RAS [8086:6fa8] ff:13.1 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Target Address/Thermal/RAS [8086:6f71] (rev 03) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Target Address/Thermal/RAS [8086:6f71] ff:13.2 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder [8086:6faa] (rev 03) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder [8086:6faa] ff:13.3 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder [8086:6fab] (rev 03) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder [8086:6fab] ff:13.4 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder [8086:6fac] (rev 03) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder [8086:6fac] ff:13.5 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder [8086:6fad] (rev 03) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder [8086:6fad] ff:13.6 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Broadcast [8086:6fae] (rev 03) ff:13.7 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Global Broadcast [8086:6faf] (rev 03) ff:14.0 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 0 Thermal Control [8086:6fb0] (rev 03) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 0 Thermal Control [8086:6fb0] Kernel driver in use: bdx_uncore ff:14.1 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 1 Thermal Control [8086:6fb1] (rev 03) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 1 Thermal Control [8086:6fb1] Kernel driver in use: bdx_uncore ff:14.2 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 0 Error [8086:6fb2] (rev 03) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 0 Error [8086:6fb2] ff:14.3 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 1 Error [8086:6fb3] (rev 03) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 1 Error [8086:6fb3] ff:14.4 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Interface [8086:6fbc] (rev 03) ff:14.5 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Interface [8086:6fbd] (rev 03) ff:14.6 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Interface [8086:6fbe] (rev 03) ff:14.7 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Interface [8086:6fbf] (rev 03) ff:15.0 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 2 Thermal Control [8086:6fb4] (rev 03) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 2 Thermal Control [8086:6fb4] Kernel driver in use: bdx_uncore ff:15.1 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 3 Thermal Control [8086:6fb5] (rev 03) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 3 Thermal Control [8086:6fb5] Kernel driver in use: bdx_uncore ff:15.2 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 2 Error [8086:6fb6] (rev 03) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 2 Error [8086:6fb6] ff:15.3 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 3 Error [8086:6fb7] (rev 03) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 3 Error [8086:6fb7] ff:1e.0 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit [8086:6f98] (rev 03) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit [8086:6f98] ff:1e.1 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit [8086:6f99] (rev 03) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit [8086:6f99] ff:1e.2 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit [8086:6f9a] (rev 03) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit [8086:6f9a] ff:1e.3 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit [8086:6fc0] (rev 03) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit [8086:6fc0] ff:1e.4 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit [8086:6f9c] (rev 03) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit [8086:6f9c] ff:1f.0 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit [8086:6f88] (rev 03) ff:1f.2 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit [8086:6f8a] (rev 03) root@arpl:/opt/arpl# Quote Link to comment Share on other sites More sharing options...
fbelavenuto Posted August 31, 2022 Author Share #573 Posted August 31, 2022 5 minutes ago, neonflx said: 07:00.0 Serial Attached SCSI controller [0107]: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] [1000:0072] (rev 03) Subsystem: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] [1000:3020] Kernel driver in use: mpt3sas Kernel modules: mpt3sas Your machine does not have a SATA controller, only this SAS controller. Despite using the same connector, the controllers are different. In the "cmdline" menu, no port will appear, as it only works if you have native SATA ports. Test with the 3615/17/22 models that have native support for SAS, there will be a correct reading of the serials and SMART data. DT (device-tree) models do not recognize non-SATA disks. Quote Link to comment Share on other sites More sharing options...
neonflx Posted August 31, 2022 Share #574 Posted August 31, 2022 tried 3622 , build , boots, when I go to the install , No Drives Detected Quote Link to comment Share on other sites More sharing options...
WiteWulf Posted August 31, 2022 Share #575 Posted August 31, 2022 (edited) 30 minutes ago, neonflx said: tried 3622 , build , boots, when I go to the install , No Drives Detected You need to set the correct satamap and idxmap parameters for your system as cmdline options. I had the same problem running 918+ on ESXi. The parameters vary based on what your hardware is. Read back through this thread and you'll find information on how to configure/fix it. Edited August 31, 2022 by WiteWulf 1 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.