Sam1 Posted November 30, 2022 Share #651 Posted November 30, 2022 (edited) 8 hours ago, maxime said: Did you enable hotplug of sata disks on bios settings? Is it a new installation or an upgrade? Hi @maxime no I dont think so as its not described in the guide. I must be using the default hotpulg value. Can you please tell me what it should be and how do i set it? Edit: Ok reading it again, in BIOS SATA is set to AHCI (default was RAID). Other options are ATA/AHCI/RAID.. hope it helps. This is a new install. Though I was using DSM6.0 on this machine before but I am setting up a new system and HDD currently installed do not have any version of DSM installed. @Peter Suh & @pocopico Edited November 30, 2022 by Sam1 Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted December 1, 2022 Author Share #652 Posted December 1, 2022 (edited) 10 hours ago, Vodka2014 said: Hi @Peter Suh & @pocopico For some odd reason i am still getting No Internet on the DSM Update Page. I have installed this on my GEN8 different versions and on proxmox and all the same. can you let me know why this happens and how to fix it please. Thanks Below are APRL fabio's RSS settings. https://github.com/fbelavenuto/arpl/blob/main/files/board/arpl/overlayfs/opt/arpl/model-configs/DS923%2B.yml rss_server: "https://raw.githubusercontent.com/fbelavenuto/arpl/main/rss.xml" rss_server_ssl: "https://raw.githubusercontent.com/fbelavenuto/arpl/main/rss.xml" rss_server_v2: "https://raw.githubusercontent.com/fbelavenuto/arpl/main/rss.json" Below are pocopico's DS3622xs+ settings. https://github.com/pocopico/redpill-load/blob/develop/config/DS3622xs%2B/7.1.1-42962/config.json "rss_server": "http://example.com/null.xml", "rss_server_ssl": "https://example.com/null.xml", "small_info_path": "https://example.com/null", "rss_server_v2": "https://example.com/autoupdate/v2/getList", "security_version_server": "https://example.com/smallupdate", "updateurl": "http://example.com/", "update_server": "http://example.com/", "update_server_ssl": "https//example.com/", "myds_region_api_base_url": "https://example.com" Below are my M SHELL DS3622xs+ settings. https://github.com/PeterSuh-Q3/redpill-load/blob/master/config/DS3622xs%2B/7.1.1-42962/config.json "rss_server": "https://raw.githubusercontent.com/pocopico/redpill-load/develop/rss.xml", "rss_server_ssl": "https://raw.githubusercontent.com/pocopico/redpill-load/develop/rss.xml", "rss_server_v2": "https://raw.githubusercontent.com/pocopico/redpill-load/develop/rss.json", "small_info_path": "https://example.com/null", "security_version_server": "https://example.com/smallupdate" There is a clear difference between these 3 rss settings. ARPL is probably open to auto-update everything. However, I'm not sure how to further adjust TCRP. You can install the latest version during the DSM installation process, but I hope pocopico, fabio or someone else can guide me on what settings to modify if I need to enable automatic updates from updates within DSM to internet. It seems that pocopico's intention is still to avoid infinite recovery or KP situations when DSM updates the latest update in real time. Since pocopico is developing a more stable and improved next-generation TCRP, I would like to open real-time updates in this next-generation. Edited December 1, 2022 by Peter Suh Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted December 1, 2022 Author Share #653 Posted December 1, 2022 (edited) 12 hours ago, Sam1 said: Can someone help? When trying pocopio boot loader (0.9.8/latest) DS918+ installation gets stuck at 57% and fails due to corrupt .PAT file installation. then I used Peter Suh with friends boot loader and I can install the .PAT file and installation completes successfully but after reboot the device again asks for .PAT file to be installed again. Tried both DSM918+ and 920+. Same result. 3622xs gets stuck and fails with corrupt PAT file error. Anyone else’s seeing this issue? configuration Dell T20 G3220 CPU 4 GB RAM Baremetal install. Recently, a review on bare metal 55% ~ 57% corruption messages has been done in a server forum in Korea. A user who presented a hotplug solution related to sata multiplex in the past posted this part. The relatively slow USB stick scans the synoboot, synoboot1, synoboot2, synoboot3 partitions, which is at a disadvantage compared to the VM. The detection of these four partitions correlates directly with the 55% to 57% corruption messages. Therefore, it is recommended to use a stick with USB 3.0 specifications and a USB 3.0 port as fast as possible. In fact, this is what I also experienced with ASROCK workstation motherboards. When I used a USB 3.0 specification stick with a USB 2.0 port, I encountered a corruption message. It's gone with USB 3.0. I don't know if the Dell T20 can meet these USB 3.0 specs. And since this method is not yet 100% verified, a better solution is currently being sought. Edited December 1, 2022 by Peter Suh Quote Link to comment Share on other sites More sharing options...
Vodka2014 Posted December 1, 2022 Share #654 Posted December 1, 2022 8 hours ago, Peter Suh said: Below are APRL fabio's RSS settings. https://github.com/fbelavenuto/arpl/blob/main/files/board/arpl/overlayfs/opt/arpl/model-configs/DS923%2B.yml rss_server: "https://raw.githubusercontent.com/fbelavenuto/arpl/main/rss.xml" rss_server_ssl: "https://raw.githubusercontent.com/fbelavenuto/arpl/main/rss.xml" rss_server_v2: "https://raw.githubusercontent.com/fbelavenuto/arpl/main/rss.json" Below are pocopico's DS3622xs+ settings. https://github.com/pocopico/redpill-load/blob/develop/config/DS3622xs%2B/7.1.1-42962/config.json "rss_server": "http://example.com/null.xml", "rss_server_ssl": "https://example.com/null.xml", "small_info_path": "https://example.com/null", "rss_server_v2": "https://example.com/autoupdate/v2/getList", "security_version_server": "https://example.com/smallupdate", "updateurl": "http://example.com/", "update_server": "http://example.com/", "update_server_ssl": "https//example.com/", "myds_region_api_base_url": "https://example.com" Below are my M SHELL DS3622xs+ settings. https://github.com/PeterSuh-Q3/redpill-load/blob/master/config/DS3622xs%2B/7.1.1-42962/config.json "rss_server": "https://raw.githubusercontent.com/pocopico/redpill-load/develop/rss.xml", "rss_server_ssl": "https://raw.githubusercontent.com/pocopico/redpill-load/develop/rss.xml", "rss_server_v2": "https://raw.githubusercontent.com/pocopico/redpill-load/develop/rss.json", "small_info_path": "https://example.com/null", "security_version_server": "https://example.com/smallupdate" There is a clear difference between these 3 rss settings. ARPL is probably open to auto-update everything. However, I'm not sure how to further adjust TCRP. You can install the latest version during the DSM installation process, but I hope pocopico, fabio or someone else can guide me on what settings to modify if I need to enable automatic updates from updates within DSM to internet. It seems that pocopico's intention is still to avoid infinite recovery or KP situations when DSM updates the latest update in real time. Since pocopico is developing a more stable and improved next-generation TCRP, I would like to open real-time updates in this next-generation. Thanks, alot for this info. I was just wondering. One thing i do like is TCRP Friend is Auto Updated on reboot if there is a new version. And yes it is easier to update via the GUI then downloading the file. from Synology. 1 Quote Link to comment Share on other sites More sharing options...
maxime Posted December 1, 2022 Share #655 Posted December 1, 2022 13 hours ago, Sam1 said: Hi @maxime no I dont think so as its not described in the guide. I must be using the default hotpulg value. Can you please tell me what it should be and how do i set it? Edit: Ok reading it again, in BIOS SATA is set to AHCI (default was RAID). Other options are ATA/AHCI/RAID.. hope it helps. This is a new install. Though I was using DSM6.0 on this machine before but I am setting up a new system and HDD currently installed do not have any version of DSM installed. @Peter Suh & @pocopico My installation process was failing, until I enabled "hotplug" to all my 6 disks (yes, in AHCI mode) Quote Link to comment Share on other sites More sharing options...
WiteWulf Posted December 1, 2022 Share #656 Posted December 1, 2022 22 hours ago, Vodka2014 said: Hi @Peter Suh & @pocopico For some odd reason i am still getting No Internet on the DSM Update Page. I have installed this on my GEN8 different versions and on proxmox and all the same. can you let me know why this happens and how to fix it please. Certain versions of redpill loader (I've never managed to figure out which) block access to the Synology update servers by adding fake hosts entries (iirc). I think this was to ensure the devices never auto-updated. You'll need to download the update file you want from https://archive.synology.com/download/Os/DSM and manually upload/install it in the DSM admin interface. 1 Quote Link to comment Share on other sites More sharing options...
Sam1 Posted December 1, 2022 Share #657 Posted December 1, 2022 12 hours ago, Peter Suh said: Recently, a review on bare metal 55% ~ 57% corruption messages has been done in a server forum in Korea. A user who presented a hotplug solution related to sata multiplex in the past posted this part. The relatively slow USB stick scans the synoboot, synoboot1, synoboot2, synoboot3 partitions, which is at a disadvantage compared to the VM. The detection of these four partitions correlates directly with the 55% to 57% corruption messages. Therefore, it is recommended to use a stick with USB 3.0 specifications and a USB 3.0 port as fast as possible. In fact, this is what I also experienced with ASROCK workstation motherboards. When I used a USB 3.0 specification stick with a USB 2.0 port, I encountered a corruption message. It's gone with USB 3.0. I don't know if the Dell T20 can meet these USB 3.0 specs. And since this method is not yet 100% verified, a better solution is currently being sought. Sure I will try a USB3.0 drive. Maybe that is the cause of failure around 57% but would you expect this to not happen when using with friends bootloader? Also any though on why with friends boot loader after build is able to install correctly and boot the drive to setup page. Once the .pat file is installed as part of the post bootloader NAS setup process the subsequent boot takes back to install .pat file again.. this just keeps repeating... any guidance would be greatly appreciated. Quote Link to comment Share on other sites More sharing options...
Vodka2014 Posted December 1, 2022 Share #658 Posted December 1, 2022 2 hours ago, WiteWulf said: Certain versions of redpill loader (I've never managed to figure out which) block access to the Synology update servers by adding fake hosts entries (iirc). I think this was to ensure the devices never auto-updated. You'll need to download the update file you want from https://archive.synology.com/download/Os/DSM and manually upload/install it in the DSM admin interface. Thanks for this. So in an nutshell this safe guards users. 1 Quote Link to comment Share on other sites More sharing options...
Vodka2014 Posted December 9, 2022 Share #659 Posted December 9, 2022 Good Day. I would like to know how do i Extend the Partitions since i am getting an error copy error stating the disk is full on boot. Thanks Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted December 9, 2022 Author Share #660 Posted December 9, 2022 39 minutes ago, Vodka2014 said: Good Day. I would like to know how do i Extend the Partitions since i am getting an error copy error stating the disk is full on boot. Thanks I already created an image with the partitions adjusted to solve this problem. Replace with this image and try rebuilding the loader for the same version and syno model. https://github.com/PeterSuh-Q3/tinycore-redpill/releases/tag/v0.9.3.0-1 You have to use gparted to adjust it yourself, but it's not easy to use. 2 Quote Link to comment Share on other sites More sharing options...
Vodka2014 Posted December 9, 2022 Share #661 Posted December 9, 2022 29 minutes ago, Peter Suh said: I already created an image with the partitions adjusted to solve this problem. Replace with this image and try rebuilding the loader for the same version and syno model. https://github.com/PeterSuh-Q3/tinycore-redpill/releases/tag/v0.9.3.0-1 You have to use gparted to adjust it yourself, but it's not easy to use. AWESOME & Thanks alot Quote Link to comment Share on other sites More sharing options...
damianssj661 Posted December 12, 2022 Share #662 Posted December 12, 2022 (edited) Could somebody please explain me, is xpenology installed just on pendrive or it will be installed on hard drive? If it is installed on pendrive maybe i can use ssd disk (sata/nvme) and install xpenology on that? Edited December 12, 2022 by damianssj661 Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted December 12, 2022 Author Share #663 Posted December 12, 2022 9 hours ago, damianssj661 said: Could somebody please explain me, is xpenology installed just on pendrive or it will be installed on hard drive? If it is installed on pendrive maybe i can use ssd disk (sata/nvme) and install xpenology on that? Could somebody please explain me, is xpenology installed just on pendrive or it will be installed on hard drive? -> Does xpenology mean bootloader only? Assuming that is the case, the answer is as follows. -> Bootloader can be installed on pendrive or ssd/m-sata/m.2 sata. I haven't tried installing the bootloader on the hard drive, but it seems to be usable as a drive dedicated to the bootloader. I'm curious too, so I'll try it out. If it is installed on pendrive maybe i can use ssd disk (sata/nvme) and install xpenology on that? -> For pendrive installation, select and use the USB boot menu, If installed on ssd/m-sata/m.2 sata drive, use sata boot menu. In general, DSM cannot be installed on m.2 NVMe and can only be used as a cache. I haven't tried to install a bootloader on M.2 NVMe, but it seems to work abnormally. 1 Quote Link to comment Share on other sites More sharing options...
Orphée Posted December 12, 2022 Share #664 Posted December 12, 2022 (edited) 18 minutes ago, Peter Suh said: Could somebody please explain me, is xpenology installed just on pendrive or it will be installed on hard drive? -> Does xpenology mean bootloader only? Assuming that is the case, the answer is as follows. -> Bootloader can be installed on pendrive or ssd/m-sata/m.2 sata. I haven't tried installing the bootloader on the hard drive, but it seems to be usable as a drive dedicated to the bootloader. I'm curious too, so I'll try it out. If it is installed on pendrive maybe i can use ssd disk (sata/nvme) and install xpenology on that? -> For pendrive installation, select and use the USB boot menu, If installed on ssd/m-sata/m.2 sata drive, use sata boot menu. In general, DSM cannot be installed on m.2 NVMe and can only be used as a cache. I haven't tried to install a bootloader on M.2 NVMe, but it seems to work abnormally. Isn't it something handled by Redpill to ignore SATA disks <1Go to make them work as SATA bootloader but not detected by DSM ? I remember something like this. How will a disk >1Go handled as a SATA bootloader ? maybe a partition with max 1Go is needed... The SATA boot mode was made for Proxmox/ESXi in the beginning I think But I may be wrong. Edited December 12, 2022 by Orphée Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted December 12, 2022 Author Share #665 Posted December 12, 2022 (edited) 8 minutes ago, Orphée said: Isn't it something handled by Redpill to ignore SATA disks <1Go to make them work as SATA bootloader but not detected by DSM ? I remember something like this. How will a disk >1Go handled as a SATA bootloader ? maybe a partition with max 1Go is needed... The SATA boot mode was made for Proxmox/ESXi in the beginning I think But I may be wrong. Have you ever looked at the dmesg of redpill's sata disk boot process? Here's some of the log content: It cheat with INNODISK MSATA 16GB. No matter which large capacity SATA disk is used as a bootloader, this INNODISK MSATA 16GB will be. In fact, if you force port the bootloader to MSATA and the USB boot option is used, there is no cheating, so MSATA can be used entirely as a bootloader, up to 24GB. If MSATA of more than this capacity is used, it is used as a data disk during the DSM installation process, and the bootloader is initialized. I'm telling you based on what I've actually tested. Edited December 12, 2022 by Peter Suh 1 1 Quote Link to comment Share on other sites More sharing options...
Vodka2014 Posted December 15, 2022 Share #666 Posted December 15, 2022 Hi @Peter Suh I have an LSI Controller card 4 Port. Do i need to add any other drivers or is this all-built in. Thanks Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted December 16, 2022 Author Share #667 Posted December 16, 2022 8 hours ago, Vodka2014 said: Hi @Peter Suh I have an LSI Controller card 4 Port. Do i need to add any other drivers or is this all-built in. Thanks It's hard to give an exact answer because you didn't tell me in detail which LSI controller model you have. Quote Link to comment Share on other sites More sharing options...
Vodka2014 Posted December 16, 2022 Share #668 Posted December 16, 2022 (edited) 3 hours ago, Peter Suh said: It's hard to give an exact answer because you didn't tell me in detail which LSI controller model you have. @Peter SuhSorry about that. It is an LSI 9211-4i. When I run lspci I get this RAID bus controller: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03) When DSM Loads it states no disks. Edited December 16, 2022 by Vodka2014 Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted December 16, 2022 Author Share #669 Posted December 16, 2022 11 hours ago, Vodka2014 said: @Peter SuhSorry about that. It is an LSI 9211-4i. When I run lspci I get this RAID bus controller: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03) When DSM Loads it states no disks. Lastly, from what you mentioned, your Synology model went from DS3622xs+ to DS1621+. Device-Tree based models such as DS1621+/DS920+/DS923+ cannot use HBA. To be precise, the three platforms v1000/gemini lake/r1000 correspond to DT. In other platforms, LSI 9211-4i works by automatically injecting mpt3sas driver. Quote Link to comment Share on other sites More sharing options...
Vodka2014 Posted December 16, 2022 Share #670 Posted December 16, 2022 58 minutes ago, Peter Suh said: Lastly, from what you mentioned, your Synology model went from DS3622xs+ to DS1621+. Device-Tree based models such as DS1621+/DS920+/DS923+ cannot use HBA. To be precise, the three platforms v1000/gemini lake/r1000 correspond to DT. In other platforms, LSI 9211-4i works by automatically injecting mpt3sas driver. Thanks @Peter Suh So, I should use DS3622xs then? I am doing a new build on some old hardware I have. Or what should I use. Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted December 17, 2022 Author Share #671 Posted December 17, 2022 9 hours ago, Vodka2014 said: Thanks @Peter Suh So, I should use DS3622xs then? I am doing a new build on some old hardware I have. Or what should I use. DS3622xs+ is a model that covers even Intel 1st generation CPUs. The redpill so far works most reliably with DS3622xs+ HBA. 1 Quote Link to comment Share on other sites More sharing options...
Vodka2014 Posted December 17, 2022 Share #672 Posted December 17, 2022 (edited) 5 hours ago, Peter Suh said: DS3622xs+ is a model that covers even Intel 1st generation CPUs. The redpill so far works most reliably with DS3622xs+ HBA. Thanks again for your support and help. @Peter Suh I rebuilt the image and again no disks found on DS3622xs+ Edited December 17, 2022 by Vodka2014 Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted December 17, 2022 Author Share #673 Posted December 17, 2022 7 hours ago, Vodka2014 said: Thanks again for your support and help. @Peter Suh I rebuilt the image and again no disks found on DS3622xs+ Haw many disk do you have? If you can access the DSM installation request screen with ttyd as below, Then send me the log with the command you see. You must use a web browser. http://<youripaddr>:7681/ id : root / pw : ( no password ) cat /var/log/linuxrc.syno.log ls -l /sys/block ls -la /sys/class/ata_device ls -l /dev/syno* 1 Quote Link to comment Share on other sites More sharing options...
Vodka2014 Posted December 18, 2022 Share #674 Posted December 18, 2022 (edited) 15 hours ago, Peter Suh said: Haw many disk do you have? If you can access the DSM installation request screen with ttyd as below, Then send me the log with the command you see. You must use a web browser. http://<youripaddr>:7681/ id : root / pw : ( no password ) cat /var/log/linuxrc.syno.log ls -l /sys/block ls -la /sys/class/ata_device ls -l /dev/syno* Hi @Peter Suh Please see the below & there is 4 SAS Disks. SynologyNAS> cat /var/log/linuxrc.syno.log START /linuxrc.syno.impl Insert Marvell 1475 SATA controller driver Insert basic USB modules... :: Loading module usb-common ... [ OK ] :: Loading module usbcore ... [ OK ] :: Loading module ehci-hcd ... [ OK ] :: Loading module ehci-pci ... [ OK ] :: Loading module xhci-hcd ... [ OK ] :: Loading module xhci-pci ... [ OK ] :: Loading module usb-storage ... [ OK ] :: Loading kernel modules from extensions ... Checking if kmods for thethorgroup.virtio should run using check-virtio.sh script Checking for VirtIO *No* VirtIO hypervisor detected NOT loading kmods for thethorgroup.virtio :: Loading kernel modules from extensions ... [ OK ] :: Executing "on_boot" custom scripts ... Running "check-all-modules.sh" for all-modules->on_boot broadwellnk 4.4.180 modules.alias.4.json Copying kmod,sed,jq,lspci files to /sbin/ 'kmod' -> '/bin/kmod' 'sed' -> '/usr/sbin/sed' 'jq' -> '/usr/sbin/jq' 'lspci' -> '/usr/sbin/lspci' Copying lspci libraries to /lib/ 'libz.so.1' -> '/lib/libz.so.1' 'libudev.so.1' -> '/lib/libudev.so.1' 'libattr.so.1' -> '/lib/libattr.so.1' 'libcap.so.2' -> '/lib/libcap.so.2' link depmod, modprobe to kmod 3c59x.ko 3w-9xxx.ko 3w-sas.ko 3w-xxxx.ko BusLogic.ko a100u2w.ko aacraid.ko acenic.ko advansys.ko aic79xx.ko aic7xxx.ko aic94xx.ko altera_tse.ko alx.ko am53c974.ko amd8111e.ko aqc111.ko arcmsr.ko asix.ko atl1.ko atl1c.ko atl1e.ko atlantic.ko atp870u.ko auxiliary.ko ax88179_178a.ko bcm-phy-lib.ko bcm7xxx.ko be2net.ko bna.ko bnx2.ko bnx2x.ko bnxt_en.ko button.ko cassini.ko catc.ko cdc-wdm.ko cdc_eem.ko cdc_ether.ko cdc_mbim.ko cdc_ncm.ko cdc_subset.ko ch9200.ko cnic.ko cpsw_ale.ko crc-ccitt.ko crc-itu-t.ko cx82310_eth.ko cxgb.ko cxgb3.ko cxgb4.ko cxgb4vf.ko dc395x.ko de2104x.ko de4x5.ko dl2k.ko dm9601.ko dmfe.ko dmx3191d.ko dnet.ko dpt_i2o.ko e1000.ko e1000e.ko eata.ko ec_bhf.ko eeprom_93cx6.ko enic.ko epic100.ko esas2r.ko esp_scsi.ko et131x.ko etxhci-hcd.ko fdomain.ko fealnx.ko fixed_phy.ko fm10k.ko forcedeth.ko ftdi_sio.ko gdth.ko genet.ko gl620a.ko governor_simpleondemand.ko hamachi.ko hpsa.ko hptiop.ko huawei_cdc_ncm.ko i40e.ko i40evf.ko iavf.ko ice.ko igb.ko igbvf.ko igc.ko initio.ko int51x1.ko ipheth.ko ipr.ko ips.ko isci.ko ixgb.ko ixgbevf.ko jme.ko kalmia.ko kaweth.ko ks8851.ko ks8851_mll.ko ksz884x.ko lan78xx.ko lg-vl600.ko libiscsi.ko libphy.ko liquidio.ko macb.ko mcs7830.ko mdio-octeon.ko mdio.ko megaraid.ko megaraid_mbox.ko megaraid_mm.ko megaraid_sas.ko microchip.ko mii.ko mlx4_core.ko mlx4_en.ko mlx5_core.ko mpt3sas.ko mptbase.ko mptctl.ko mptsas.ko mptscsih.ko mptspi.ko mvmdio.ko mvsas.ko mvumi.ko myri10ge.ko natsemi.ko nb8800.ko nct6775.ko net1080.ko netxen_nic.ko nicpf.ko nicvf.ko niu.ko ns83820.ko pcnet32.ko pegasus.ko plusb.ko pm80xx.ko pmcraid.ko qed.ko qede.ko qla1280.ko qla3xxx.ko qla4xxx.ko qlcnic.ko qlge.ko qmi_wwan.ko r8101.ko r8125.ko r8152.ko r8153_ecm.ko r8168.ko r8169.ko rndis_host.ko rtl8150.ko s2io.ko samsung-sxgbe.ko scsi_transport_spi.ko sfc.ko sierra_net.ko sis190.ko skge.ko sky2.ko smsc.ko smsc75xx.ko smsc911x.ko smsc9420.ko smsc95xx.ko sr9700.ko sr9800.ko starfire.ko stex.ko sundance.ko sungem.ko sungem_phy.ko sym53c8xx.ko tehuti.ko tg3.ko thunder_bgx.ko tlan.ko tulip.ko typhoon.ko ufshcd.ko uli526x.ko usbnet.ko usbserial.ko via-velocity.ko virtio.ko virtio_blk.ko virtio_mmio.ko virtio_net.ko virtio_pci.ko virtio_ring.ko virtio_scsi.ko vmw_pvscsi.ko vmw_vmci.ko vmxnet3.ko vxge.ko wd719x.ko winbond-840.ko yellowfin.ko zaurus.ko depmod: WARNING: could not open /lib/modules//modules.order: No such file or directory depmod: WARNING: could not open /lib/modules//modules.builtin: No such file or directory insmod: can't insert '/lib/modules/ahci.ko': No such file or directory Found SATA Controller : pciid 8086d00003a22 Required Extension : Searching for matching extension for ahci Found Ethernet Interface : pciid 10ecd00008168 Required Extension : Searching for matching extension for r8168 Module r8168 loaded succesfully Found VGA Controller : pciid 10ded0000128b Required Extension : No matching extension Found SATA Controller : pciid 1b4bd00009235 Required Extension : No matching extension Found SATA Controller : pciid 1b4bd00009235 Required Extension : No matching extension Ran "check-all-modules.sh" for all-modules->on_boot - exit=0 Running "install_rd.sh" for redpill-misc->on_boot Starting ttyd, listening on port: 7681 Ran "install_rd.sh" for redpill-misc->on_boot - exit=0 Running "boot-wait.sh" for thethorgroup.boot-wait->on_boot Confirmed a valid-looking /dev/synoboot device Ran "boot-wait.sh" for thethorgroup.boot-wait->on_boot - exit=0 :: Executing "on_boot" custom scripts ... [ OK ] Extensions processed Insert net driver(Mindspeed only)... Starting /usr/syno/bin/synocfgen... /usr/syno/bin/synocfgen returns 0 Insert synorbd kernel module Insert synofsbd kernel module Insert sha256 kernel module All disk ready or timeout execeed Exit on error [1] DISK NOT INSTALLED... Sun Dec 18 04:09:02 UTC 2022 none /sys/kernel/debug debugfs rw,relatime 0 0 SynologyNAS> ls -l /sys/block lrwxrwxrwx 1 root root 0 Dec 18 04:13 ram0 -> ../devices/virtual/block/ram0 lrwxrwxrwx 1 root root 0 Dec 18 04:13 ram1 -> ../devices/virtual/block/ram1 lrwxrwxrwx 1 root root 0 Dec 18 04:13 ram10 -> ../devices/virtual/block/ram10 lrwxrwxrwx 1 root root 0 Dec 18 04:13 ram11 -> ../devices/virtual/block/ram11 lrwxrwxrwx 1 root root 0 Dec 18 04:13 ram12 -> ../devices/virtual/block/ram12 lrwxrwxrwx 1 root root 0 Dec 18 04:13 ram13 -> ../devices/virtual/block/ram13 lrwxrwxrwx 1 root root 0 Dec 18 04:13 ram14 -> ../devices/virtual/block/ram14 lrwxrwxrwx 1 root root 0 Dec 18 04:13 ram15 -> ../devices/virtual/block/ram15 lrwxrwxrwx 1 root root 0 Dec 18 04:13 ram2 -> ../devices/virtual/block/ram2 lrwxrwxrwx 1 root root 0 Dec 18 04:13 ram3 -> ../devices/virtual/block/ram3 lrwxrwxrwx 1 root root 0 Dec 18 04:13 ram4 -> ../devices/virtual/block/ram4 lrwxrwxrwx 1 root root 0 Dec 18 04:13 ram5 -> ../devices/virtual/block/ram5 lrwxrwxrwx 1 root root 0 Dec 18 04:13 ram6 -> ../devices/virtual/block/ram6 lrwxrwxrwx 1 root root 0 Dec 18 04:13 ram7 -> ../devices/virtual/block/ram7 lrwxrwxrwx 1 root root 0 Dec 18 04:13 ram8 -> ../devices/virtual/block/ram8 lrwxrwxrwx 1 root root 0 Dec 18 04:13 ram9 -> ../devices/virtual/block/ram9 lrwxrwxrwx 1 root root 0 Dec 18 04:13 synoboot -> ../devices/pci0000:00/0000:00:1d.7/usb2/2-3/2-3:1.0/host6/target6:0:0/6:0:0:0/block/synoboot SynologyNAS> ls -la /sys/class/ata_device drwxr-xr-x 2 root root 0 Dec 18 04:13 . drwxr-xr-x 54 root root 0 Dec 18 04:09 .. lrwxrwxrwx 1 root root 0 Dec 18 04:13 dev1.0 -> ../../devices/pci0000:00/0000:00:1f.2/ata1/link1/dev1.0/ata_device/dev1.0 lrwxrwxrwx 1 root root 0 Dec 18 04:13 dev2.0 -> ../../devices/pci0000:00/0000:00:1f.2/ata2/link2/dev2.0/ata_device/dev2.0 lrwxrwxrwx 1 root root 0 Dec 18 04:13 dev3.0 -> ../../devices/pci0000:00/0000:00:1f.2/ata3/link3/dev3.0/ata_device/dev3.0 lrwxrwxrwx 1 root root 0 Dec 18 04:13 dev4.0 -> ../../devices/pci0000:00/0000:00:1f.2/ata4/link4/dev4.0/ata_device/dev4.0 lrwxrwxrwx 1 root root 0 Dec 18 04:13 dev5.0 -> ../../devices/pci0000:00/0000:00:1f.2/ata5/link5/dev5.0/ata_device/dev5.0 lrwxrwxrwx 1 root root 0 Dec 18 04:13 dev6.0 -> ../../devices/pci0000:00/0000:00:1f.2/ata6/link6/dev6.0/ata_device/dev6.0 SynologyNAS> ls -l /dev/syno* crw-r--r-- 1 root root 201, 0 Dec 18 04:09 /dev/synobios brw------- 1 root root 135, 240 Dec 18 04:09 /dev/synoboot brw------- 1 root root 135, 241 Dec 18 04:09 /dev/synoboot1 brw------- 1 root root 135, 242 Dec 18 04:09 /dev/synoboot2 brw------- 1 root root 135, 243 Dec 18 04:09 /dev/synoboot3 Edited December 18, 2022 by Vodka2014 Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted December 19, 2022 Author Share #675 Posted December 19, 2022 19 hours ago, Vodka2014 said: Hi @Peter Suh Please see the below & there is 4 SAS Disks. SynologyNAS> cat /var/log/linuxrc.syno.log START /linuxrc.syno.impl Insert Marvell 1475 SATA controller driver Insert basic USB modules... :: Loading module usb-common ... [ OK ] :: Loading module usbcore ... [ OK ] :: Loading module ehci-hcd ... [ OK ] :: Loading module ehci-pci ... [ OK ] :: Loading module xhci-hcd ... [ OK ] :: Loading module xhci-pci ... [ OK ] :: Loading module usb-storage ... [ OK ] :: Loading kernel modules from extensions ... Checking if kmods for thethorgroup.virtio should run using check-virtio.sh script Checking for VirtIO *No* VirtIO hypervisor detected NOT loading kmods for thethorgroup.virtio :: Loading kernel modules from extensions ... [ OK ] :: Executing "on_boot" custom scripts ... Running "check-all-modules.sh" for all-modules->on_boot broadwellnk 4.4.180 modules.alias.4.json Copying kmod,sed,jq,lspci files to /sbin/ 'kmod' -> '/bin/kmod' 'sed' -> '/usr/sbin/sed' 'jq' -> '/usr/sbin/jq' 'lspci' -> '/usr/sbin/lspci' Copying lspci libraries to /lib/ 'libz.so.1' -> '/lib/libz.so.1' 'libudev.so.1' -> '/lib/libudev.so.1' 'libattr.so.1' -> '/lib/libattr.so.1' 'libcap.so.2' -> '/lib/libcap.so.2' link depmod, modprobe to kmod 3c59x.ko 3w-9xxx.ko 3w-sas.ko 3w-xxxx.ko BusLogic.ko a100u2w.ko aacraid.ko acenic.ko advansys.ko aic79xx.ko aic7xxx.ko aic94xx.ko altera_tse.ko alx.ko am53c974.ko amd8111e.ko aqc111.ko arcmsr.ko asix.ko atl1.ko atl1c.ko atl1e.ko atlantic.ko atp870u.ko auxiliary.ko ax88179_178a.ko bcm-phy-lib.ko bcm7xxx.ko be2net.ko bna.ko bnx2.ko bnx2x.ko bnxt_en.ko button.ko cassini.ko catc.ko cdc-wdm.ko cdc_eem.ko cdc_ether.ko cdc_mbim.ko cdc_ncm.ko cdc_subset.ko ch9200.ko cnic.ko cpsw_ale.ko crc-ccitt.ko crc-itu-t.ko cx82310_eth.ko cxgb.ko cxgb3.ko cxgb4.ko cxgb4vf.ko dc395x.ko de2104x.ko de4x5.ko dl2k.ko dm9601.ko dmfe.ko dmx3191d.ko dnet.ko dpt_i2o.ko e1000.ko e1000e.ko eata.ko ec_bhf.ko eeprom_93cx6.ko enic.ko epic100.ko esas2r.ko esp_scsi.ko et131x.ko etxhci-hcd.ko fdomain.ko fealnx.ko fixed_phy.ko fm10k.ko forcedeth.ko ftdi_sio.ko gdth.ko genet.ko gl620a.ko governor_simpleondemand.ko hamachi.ko hpsa.ko hptiop.ko huawei_cdc_ncm.ko i40e.ko i40evf.ko iavf.ko ice.ko igb.ko igbvf.ko igc.ko initio.ko int51x1.ko ipheth.ko ipr.ko ips.ko isci.ko ixgb.ko ixgbevf.ko jme.ko kalmia.ko kaweth.ko ks8851.ko ks8851_mll.ko ksz884x.ko lan78xx.ko lg-vl600.ko libiscsi.ko libphy.ko liquidio.ko macb.ko mcs7830.ko mdio-octeon.ko mdio.ko megaraid.ko megaraid_mbox.ko megaraid_mm.ko megaraid_sas.ko microchip.ko mii.ko mlx4_core.ko mlx4_en.ko mlx5_core.ko mpt3sas.ko mptbase.ko mptctl.ko mptsas.ko mptscsih.ko mptspi.ko mvmdio.ko mvsas.ko mvumi.ko myri10ge.ko natsemi.ko nb8800.ko nct6775.ko net1080.ko netxen_nic.ko nicpf.ko nicvf.ko niu.ko ns83820.ko pcnet32.ko pegasus.ko plusb.ko pm80xx.ko pmcraid.ko qed.ko qede.ko qla1280.ko qla3xxx.ko qla4xxx.ko qlcnic.ko qlge.ko qmi_wwan.ko r8101.ko r8125.ko r8152.ko r8153_ecm.ko r8168.ko r8169.ko rndis_host.ko rtl8150.ko s2io.ko samsung-sxgbe.ko scsi_transport_spi.ko sfc.ko sierra_net.ko sis190.ko skge.ko sky2.ko smsc.ko smsc75xx.ko smsc911x.ko smsc9420.ko smsc95xx.ko sr9700.ko sr9800.ko starfire.ko stex.ko sundance.ko sungem.ko sungem_phy.ko sym53c8xx.ko tehuti.ko tg3.ko thunder_bgx.ko tlan.ko tulip.ko typhoon.ko ufshcd.ko uli526x.ko usbnet.ko usbserial.ko via-velocity.ko virtio.ko virtio_blk.ko virtio_mmio.ko virtio_net.ko virtio_pci.ko virtio_ring.ko virtio_scsi.ko vmw_pvscsi.ko vmw_vmci.ko vmxnet3.ko vxge.ko wd719x.ko winbond-840.ko yellowfin.ko zaurus.ko depmod: WARNING: could not open /lib/modules//modules.order: No such file or directory depmod: WARNING: could not open /lib/modules//modules.builtin: No such file or directory insmod: can't insert '/lib/modules/ahci.ko': No such file or directory Found SATA Controller : pciid 8086d00003a22 Required Extension : Searching for matching extension for ahci Found Ethernet Interface : pciid 10ecd00008168 Required Extension : Searching for matching extension for r8168 Module r8168 loaded succesfully Found VGA Controller : pciid 10ded0000128b Required Extension : No matching extension Found SATA Controller : pciid 1b4bd00009235 Required Extension : No matching extension Found SATA Controller : pciid 1b4bd00009235 Required Extension : No matching extension Ran "check-all-modules.sh" for all-modules->on_boot - exit=0 Running "install_rd.sh" for redpill-misc->on_boot Starting ttyd, listening on port: 7681 Ran "install_rd.sh" for redpill-misc->on_boot - exit=0 Running "boot-wait.sh" for thethorgroup.boot-wait->on_boot Confirmed a valid-looking /dev/synoboot device Ran "boot-wait.sh" for thethorgroup.boot-wait->on_boot - exit=0 :: Executing "on_boot" custom scripts ... [ OK ] Extensions processed Insert net driver(Mindspeed only)... Starting /usr/syno/bin/synocfgen... /usr/syno/bin/synocfgen returns 0 Insert synorbd kernel module Insert synofsbd kernel module Insert sha256 kernel module All disk ready or timeout execeed Exit on error [1] DISK NOT INSTALLED... Sun Dec 18 04:09:02 UTC 2022 none /sys/kernel/debug debugfs rw,relatime 0 0 SynologyNAS> ls -l /sys/block lrwxrwxrwx 1 root root 0 Dec 18 04:13 ram0 -> ../devices/virtual/block/ram0 lrwxrwxrwx 1 root root 0 Dec 18 04:13 ram1 -> ../devices/virtual/block/ram1 lrwxrwxrwx 1 root root 0 Dec 18 04:13 ram10 -> ../devices/virtual/block/ram10 lrwxrwxrwx 1 root root 0 Dec 18 04:13 ram11 -> ../devices/virtual/block/ram11 lrwxrwxrwx 1 root root 0 Dec 18 04:13 ram12 -> ../devices/virtual/block/ram12 lrwxrwxrwx 1 root root 0 Dec 18 04:13 ram13 -> ../devices/virtual/block/ram13 lrwxrwxrwx 1 root root 0 Dec 18 04:13 ram14 -> ../devices/virtual/block/ram14 lrwxrwxrwx 1 root root 0 Dec 18 04:13 ram15 -> ../devices/virtual/block/ram15 lrwxrwxrwx 1 root root 0 Dec 18 04:13 ram2 -> ../devices/virtual/block/ram2 lrwxrwxrwx 1 root root 0 Dec 18 04:13 ram3 -> ../devices/virtual/block/ram3 lrwxrwxrwx 1 root root 0 Dec 18 04:13 ram4 -> ../devices/virtual/block/ram4 lrwxrwxrwx 1 root root 0 Dec 18 04:13 ram5 -> ../devices/virtual/block/ram5 lrwxrwxrwx 1 root root 0 Dec 18 04:13 ram6 -> ../devices/virtual/block/ram6 lrwxrwxrwx 1 root root 0 Dec 18 04:13 ram7 -> ../devices/virtual/block/ram7 lrwxrwxrwx 1 root root 0 Dec 18 04:13 ram8 -> ../devices/virtual/block/ram8 lrwxrwxrwx 1 root root 0 Dec 18 04:13 ram9 -> ../devices/virtual/block/ram9 lrwxrwxrwx 1 root root 0 Dec 18 04:13 synoboot -> ../devices/pci0000:00/0000:00:1d.7/usb2/2-3/2-3:1.0/host6/target6:0:0/6:0:0:0/block/synoboot SynologyNAS> ls -la /sys/class/ata_device drwxr-xr-x 2 root root 0 Dec 18 04:13 . drwxr-xr-x 54 root root 0 Dec 18 04:09 .. lrwxrwxrwx 1 root root 0 Dec 18 04:13 dev1.0 -> ../../devices/pci0000:00/0000:00:1f.2/ata1/link1/dev1.0/ata_device/dev1.0 lrwxrwxrwx 1 root root 0 Dec 18 04:13 dev2.0 -> ../../devices/pci0000:00/0000:00:1f.2/ata2/link2/dev2.0/ata_device/dev2.0 lrwxrwxrwx 1 root root 0 Dec 18 04:13 dev3.0 -> ../../devices/pci0000:00/0000:00:1f.2/ata3/link3/dev3.0/ata_device/dev3.0 lrwxrwxrwx 1 root root 0 Dec 18 04:13 dev4.0 -> ../../devices/pci0000:00/0000:00:1f.2/ata4/link4/dev4.0/ata_device/dev4.0 lrwxrwxrwx 1 root root 0 Dec 18 04:13 dev5.0 -> ../../devices/pci0000:00/0000:00:1f.2/ata5/link5/dev5.0/ata_device/dev5.0 lrwxrwxrwx 1 root root 0 Dec 18 04:13 dev6.0 -> ../../devices/pci0000:00/0000:00:1f.2/ata6/link6/dev6.0/ata_device/dev6.0 SynologyNAS> ls -l /dev/syno* crw-r--r-- 1 root root 201, 0 Dec 18 04:09 /dev/synobios brw------- 1 root root 135, 240 Dec 18 04:09 /dev/synoboot brw------- 1 root root 135, 241 Dec 18 04:09 /dev/synoboot1 brw------- 1 root root 135, 242 Dec 18 04:09 /dev/synoboot2 brw------- 1 root root 135, 243 Dec 18 04:09 /dev/synoboot3 mpt3sas does not exist in the FOUND list below. You should have found mpt3sas in the automatic recognition process of the device below. Found SATA Controller : pciid 8086d00003a22 Required Extension : Searching for matching extension for ahci Found Ethernet Interface : pciid 10ecd00008168 Required Extension : Searching for matching extension for r8168 Module r8168 loaded successfully Found VGA Controller : pciid 10ded0000128b Required Extension : No matching extension Found SATA Controller : pciid 1b4bd00009235 Required Extension : No matching extension Found SATA Controller : pciid 1b4bd00009235 Required Extension : No matching extension You already gave the HBA information through lspci a few days ago, as shown below. RAID bus controller: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03) (VID:PID) I think you need to look at additional pci devices. Please provide more information above with the command below. It must be run from the Tynicore linux prompt. lspci -nn If I know the VID / PID, let's check why it couldn't match the auto search. 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.