Peter Suh Posted April 19, 2022 Share #2826 Posted April 19, 2022 (edited) @pocopico (DS920+ BAREMETAL, DSM 7.0.1-42661) The Sata controller seems to have found stabilization now, and there is an inquiry about the HBA. The internal Sata controller was turned off under the condition that only HBAs were used. All other platforms (including ds918+) of this HBA normally recognize all the hard drives during DSM installation. Is it correct that the 4 drives installed in the HBA are also related to the DTC? Automatic recognition of patchdtc() of TC is recorded as below referring to HBA information. And the result is that the hard drive cannot be found on the DSM installation screen. The log on the last telnet shows an error when loading mpt3sas ext. Check please. Found 4 disks and 0 nvme Collecting disk paths Found local disk sdb with path 00:01.1,00.0, adding into internal_slot 1 with portnumber 1 Found local disk sdc with path 00:01.1,00.0, adding into internal_slot 2 with portnumber 1 Found local disk sdd with path 00:01.1,00.0, adding into internal_slot 3 with portnumber 1 Found local disk sde with path 00:01.1,00.0, adding into internal_slot 4 with portnumber 1 NO NVME disks found, returning Patching USB to include your loader. Loader found in 3-3 port Converting dts file : ds920p.dts to dtb file : >ds920p.dtb Copying patched dtb file ds920p.dtb to /home/tc/redpill-load/custom/extensions/redpill-dtb/ds920p_42661/model_ds920p.dtb -> OK ! File copied and verified ! lrwxrwxrwx 1 root root 0 Apr 19 15:33 sda -> ../devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.0/host0/target0:0:0/0:0:0:0/block/sda lrwxrwxrwx 1 root root 0 Apr 19 15:35 sdb -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host1/port-1:0/end_device-1:0/target1:0:0/1:0:0:0/block/sdb lrwxrwxrwx 1 root root 0 Apr 19 15:35 sdc -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host1/port-1:1/end_device-1:1/target1:0:1/1:0:1:0/block/sdc lrwxrwxrwx 1 root root 0 Apr 19 15:35 sdd -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host1/port-1:2/end_device-1:2/target1:0:2/1:0:2:0/block/sdd lrwxrwxrwx 1 root root 0 Apr 19 15:35 sde -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host1/port-1:3/end_device-1:3/target1:0:3/1:0:3:0/block/sde lrwxrwxrwx 1 root root 0 Apr 19 15:33 zram0 -> ../devices/virtual/block/zram0 tc@box:~$ udevadm info --query path --name sdb /devices/pci0000:00/0000:00:01.1/0000:02:00.0/host1/port-1:0/end_device-1:0/target1:0:0/1:0:0:0/block/sdb tc@box:~$ udevadm info --query path --name sdc /devices/pci0000:00/0000:00:01.1/0000:02:00.0/host1/port-1:1/end_device-1:1/target1:0:1/1:0:1:0/block/sdc tc@box:~$ udevadm info --query path --name sdd /devices/pci0000:00/0000:00:01.1/0000:02:00.0/host1/port-1:2/end_device-1:2/target1:0:2/1:0:2:0/block/sdd tc@box:~$ udevadm info --query path --name sde /devices/pci0000:00/0000:00:01.1/0000:02:00.0/host1/port-1:3/end_device-1:3/target1:0:3/1:0:3:0/block/sde tc@box:~$ lspci -tvnnq -[0000:00]-+-00.0 Intel Corporation Xeon E3-1200 v3 Processor DRAM Controller [8086:0c08] +-01.0-[01]-- +-01.1-[02]----00.0 LSI Logic / Symbios Logic SAS2004 PCI-Express Fusion-MPT SAS-2 [Spitfire] [1000:0070] +-14.0 Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI [8086:8c31] +-19.0 Intel Corporation Ethernet Connection I217-LM [8086:153a] +-1a.0 Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 [8086:8c2d] +-1c.0-[03]-- +-1c.4-[04]----00.0 Intel Corporation I210 Gigabit Network Connection [8086:1533] +-1c.7-[05-06]----00.0-[06]----00.0 ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] +-1d.0 Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 [8086:8c26] +-1f.0 Intel Corporation C222 Series Chipset Family Server Essential SKU LPC Controller [8086:8c52] \-1f.3 Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller [8086:8c22] internal_slot@1 { protocol_type = "sata"; power_pin_gpio = <0x14 0x0>; detect_pin_gpio = <0x23 0x1>; led_type = "lp3943"; ahci { pcie_root = "00:01.1,00.0"; ata_port = <0x1>; }; led_green { led_name = "syno_led0"; }; led_orange { led_name = "syno_led1"; }; }; internal_slot@2 { protocol_type = "sata"; power_pin_gpio = <0x15 0x0>; detect_pin_gpio = <0x24 0x1>; led_type = "lp3943"; ahci { pcie_root = "00:01.1,00.0"; ata_port = <0x1>; }; led_green { led_name = "syno_led2"; }; led_orange { led_name = "syno_led3"; }; }; internal_slot@3 { protocol_type = "sata"; power_pin_gpio = <0x16 0x0>; detect_pin_gpio = <0x25 0x1>; led_type = "lp3943"; ahci { pcie_root = "00:01.1,00.0"; ata_port = <0x1>; }; led_green { led_name = "syno_led4"; }; led_orange { led_name = "syno_led5"; }; }; internal_slot@4 { protocol_type = "sata"; power_pin_gpio = <0x17 0x0>; detect_pin_gpio = <0x26 0x1>; led_type = "lp3943"; ahci { pcie_root = "00:01.1,00.0"; ata_port = <0x1>; }; led_green { led_name = "syno_led6"; }; led_orange { led_name = "syno_led7"; }; }; SynologyNAS> cat /var/log/junior_reason Exit on error [99] rp ext init exec failure... SynologyNAS> cat /var/log/*rc* START /linuxrc.syno.impl '/etc.defaults/model.dtb' -> '/var/run/model.dtb' Insert basic USB modules... :: Loading module usb-common ... [ OK ] :: Loading module usbcore ... [ OK ] :: Loading module xhci-hcd ... [ OK ] :: Loading module xhci-pci ... [ OK ] :: Loading module usb-storage ... [ OK ] :: Loading kernel modules from extensions ... Loading kmod #0 "e1000e.ko" for pocopico.e1000e (args: ) Loading kmod #0 "igb.ko" for pocopico.igb (args: ) Loading kmod #0 "raid_class.ko" for pocopico.mpt3sas (args: ) Loading kmod #1 "scsi_transport_sas.ko" for pocopico.mpt3sas (args: ) Loading kmod #2 "mpt3sas.ko" for pocopico.mpt3sas (args: ) Killed ERROR: kernel extensions "mpt3sas.ko" from pocopico.mpt3sas failed to load Exit on error [99] rp ext init exec failure... Tue Apr 19 15:42:06 UTC 2022 none /sys/kernel/debug debugfs rw,relatime 0 0 SynologyNAS> Edited April 19, 2022 by Peter Suh Quote Link to comment Share on other sites More sharing options...
Oli5 Posted April 19, 2022 Share #2827 Posted April 19, 2022 On 4/17/2022 at 5:14 PM, Peter Suh said: This does not mean modifying the grub.cfg file. Press the 'e' key as shown at the bottom of this screen. still no success with my baremetal installation SynologyNAS> cat *rc*.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 ... Loading kmod #0 "e1000e.ko" for pocopico.e1000e (args: ) :: Loading kernel modules from extensions ... [ OK ] :: Executing "on_boot" custom scripts ... Running "check-e1000e.sh" for pocopico.e1000e->on_boot Loading module e1000e -> Module e1000e loaded succesfully Ran "check-e1000e.sh" for pocopico.e1000e->on_boot - exit=0 Running "boot-wait.sh" for redpill-boot-wait->on_boot Still waiting for boot device (waited 1 of 30 seconds) Still waiting for boot device (waited 2 of 30 seconds) Still waiting for boot device (waited 3 of 30 seconds) Confirmed a valid-looking /dev/synoboot device Ran "boot-wait.sh" for redpill-boot-wait->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 :: Executing "on_boot" custom scripts ... [ OK ] Extensions processed insmod: can't insert '/lib/modules/etxhci-hcd.ko': No such file or directory 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 Assemble args: Exit on error [12] No raid status in path /sys/block/md0/md/array_state, go to junior mode... Tue Apr 19 19:42:06 UTC 2022 none /sys/kernel/debug debugfs rw,relatime 0 0 Quote Link to comment Share on other sites More sharing options...
pocopico Posted April 19, 2022 Author Share #2828 Posted April 19, 2022 1 hour ago, Peter Suh said: @pocopico (DS920+ BAREMETAL, DSM 7.0.1-42661) The Sata controller seems to have found stabilization now, and there is an inquiry about the HBA. The internal Sata controller was turned off under the condition that only HBAs were used. All other platforms (including ds918+) of this HBA normally recognize all the hard drives during DSM installation. Is it correct that the 4 drives installed in the HBA are also related to the DTC? Automatic recognition of patchdtc() of TC is recorded as below referring to HBA information. And the result is that the hard drive cannot be found on the DSM installation screen. The log on the last telnet shows an error when loading mpt3sas ext. Check please. Found 4 disks and 0 nvme Collecting disk paths Found local disk sdb with path 00:01.1,00.0, adding into internal_slot 1 with portnumber 1 Found local disk sdc with path 00:01.1,00.0, adding into internal_slot 2 with portnumber 1 Found local disk sdd with path 00:01.1,00.0, adding into internal_slot 3 with portnumber 1 Found local disk sde with path 00:01.1,00.0, adding into internal_slot 4 with portnumber 1 NO NVME disks found, returning Patching USB to include your loader. Loader found in 3-3 port Converting dts file : ds920p.dts to dtb file : >ds920p.dtb Copying patched dtb file ds920p.dtb to /home/tc/redpill-load/custom/extensions/redpill-dtb/ds920p_42661/model_ds920p.dtb -> OK ! File copied and verified ! lrwxrwxrwx 1 root root 0 Apr 19 15:33 sda -> ../devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.0/host0/target0:0:0/0:0:0:0/block/sda lrwxrwxrwx 1 root root 0 Apr 19 15:35 sdb -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host1/port-1:0/end_device-1:0/target1:0:0/1:0:0:0/block/sdb lrwxrwxrwx 1 root root 0 Apr 19 15:35 sdc -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host1/port-1:1/end_device-1:1/target1:0:1/1:0:1:0/block/sdc lrwxrwxrwx 1 root root 0 Apr 19 15:35 sdd -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host1/port-1:2/end_device-1:2/target1:0:2/1:0:2:0/block/sdd lrwxrwxrwx 1 root root 0 Apr 19 15:35 sde -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host1/port-1:3/end_device-1:3/target1:0:3/1:0:3:0/block/sde lrwxrwxrwx 1 root root 0 Apr 19 15:33 zram0 -> ../devices/virtual/block/zram0 tc@box:~$ udevadm info --query path --name sdb /devices/pci0000:00/0000:00:01.1/0000:02:00.0/host1/port-1:0/end_device-1:0/target1:0:0/1:0:0:0/block/sdb tc@box:~$ udevadm info --query path --name sdc /devices/pci0000:00/0000:00:01.1/0000:02:00.0/host1/port-1:1/end_device-1:1/target1:0:1/1:0:1:0/block/sdc tc@box:~$ udevadm info --query path --name sdd /devices/pci0000:00/0000:00:01.1/0000:02:00.0/host1/port-1:2/end_device-1:2/target1:0:2/1:0:2:0/block/sdd tc@box:~$ udevadm info --query path --name sde /devices/pci0000:00/0000:00:01.1/0000:02:00.0/host1/port-1:3/end_device-1:3/target1:0:3/1:0:3:0/block/sde tc@box:~$ lspci -tvnnq -[0000:00]-+-00.0 Intel Corporation Xeon E3-1200 v3 Processor DRAM Controller [8086:0c08] +-01.0-[01]-- +-01.1-[02]----00.0 LSI Logic / Symbios Logic SAS2004 PCI-Express Fusion-MPT SAS-2 [Spitfire] [1000:0070] +-14.0 Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI [8086:8c31] +-19.0 Intel Corporation Ethernet Connection I217-LM [8086:153a] +-1a.0 Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 [8086:8c2d] +-1c.0-[03]-- +-1c.4-[04]----00.0 Intel Corporation I210 Gigabit Network Connection [8086:1533] +-1c.7-[05-06]----00.0-[06]----00.0 ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] +-1d.0 Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 [8086:8c26] +-1f.0 Intel Corporation C222 Series Chipset Family Server Essential SKU LPC Controller [8086:8c52] \-1f.3 Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller [8086:8c22] internal_slot@1 { protocol_type = "sata"; power_pin_gpio = <0x14 0x0>; detect_pin_gpio = <0x23 0x1>; led_type = "lp3943"; ahci { pcie_root = "00:01.1,00.0"; ata_port = <0x1>; }; led_green { led_name = "syno_led0"; }; led_orange { led_name = "syno_led1"; }; }; internal_slot@2 { protocol_type = "sata"; power_pin_gpio = <0x15 0x0>; detect_pin_gpio = <0x24 0x1>; led_type = "lp3943"; ahci { pcie_root = "00:01.1,00.0"; ata_port = <0x1>; }; led_green { led_name = "syno_led2"; }; led_orange { led_name = "syno_led3"; }; }; internal_slot@3 { protocol_type = "sata"; power_pin_gpio = <0x16 0x0>; detect_pin_gpio = <0x25 0x1>; led_type = "lp3943"; ahci { pcie_root = "00:01.1,00.0"; ata_port = <0x1>; }; led_green { led_name = "syno_led4"; }; led_orange { led_name = "syno_led5"; }; }; internal_slot@4 { protocol_type = "sata"; power_pin_gpio = <0x17 0x0>; detect_pin_gpio = <0x26 0x1>; led_type = "lp3943"; ahci { pcie_root = "00:01.1,00.0"; ata_port = <0x1>; }; led_green { led_name = "syno_led6"; }; led_orange { led_name = "syno_led7"; }; }; SynologyNAS> cat /var/log/junior_reason Exit on error [99] rp ext init exec failure... SynologyNAS> cat /var/log/*rc* START /linuxrc.syno.impl '/etc.defaults/model.dtb' -> '/var/run/model.dtb' Insert basic USB modules... :: Loading module usb-common ... [ OK ] :: Loading module usbcore ... [ OK ] :: Loading module xhci-hcd ... [ OK ] :: Loading module xhci-pci ... [ OK ] :: Loading module usb-storage ... [ OK ] :: Loading kernel modules from extensions ... Loading kmod #0 "e1000e.ko" for pocopico.e1000e (args: ) Loading kmod #0 "igb.ko" for pocopico.igb (args: ) Loading kmod #0 "raid_class.ko" for pocopico.mpt3sas (args: ) Loading kmod #1 "scsi_transport_sas.ko" for pocopico.mpt3sas (args: ) Loading kmod #2 "mpt3sas.ko" for pocopico.mpt3sas (args: ) Killed ERROR: kernel extensions "mpt3sas.ko" from pocopico.mpt3sas failed to load Exit on error [99] rp ext init exec failure... Tue Apr 19 15:42:06 UTC 2022 none /sys/kernel/debug debugfs rw,relatime 0 0 SynologyNAS> Of course, thats the reason that you need to manually edit the dts. There are so many options. Here the port is represented by : lrwxrwxrwx 1 root root 0 Apr 19 15:35 sde -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host1/port-1:3/end_device-1:3/target1:0:3/1:0:3:0/block/sde on other systems the target will change and no port will be listed. The automatic patching of the port will be different in so many systems that actually renders the process useless. Quote Link to comment Share on other sites More sharing options...
pocopico Posted April 19, 2022 Author Share #2829 Posted April 19, 2022 4 minutes ago, Oli5 said: still no success with my baremetal installation SynologyNAS> cat *rc*.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 ... Loading kmod #0 "e1000e.ko" for pocopico.e1000e (args: ) :: Loading kernel modules from extensions ... [ OK ] :: Executing "on_boot" custom scripts ... Running "check-e1000e.sh" for pocopico.e1000e->on_boot Loading module e1000e -> Module e1000e loaded succesfully Ran "check-e1000e.sh" for pocopico.e1000e->on_boot - exit=0 Running "boot-wait.sh" for redpill-boot-wait->on_boot Still waiting for boot device (waited 1 of 30 seconds) Still waiting for boot device (waited 2 of 30 seconds) Still waiting for boot device (waited 3 of 30 seconds) Confirmed a valid-looking /dev/synoboot device Ran "boot-wait.sh" for redpill-boot-wait->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 :: Executing "on_boot" custom scripts ... [ OK ] Extensions processed insmod: can't insert '/lib/modules/etxhci-hcd.ko': No such file or directory 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 Assemble args: Exit on error [12] No raid status in path /sys/block/md0/md/array_state, go to junior mode... Tue Apr 19 19:42:06 UTC 2022 none /sys/kernel/debug debugfs rw,relatime 0 0 No disks found ? Quote Link to comment Share on other sites More sharing options...
loomes Posted April 19, 2022 Share #2830 Posted April 19, 2022 I have read here some time. I build the Loader with my own Scripts for myself, but this is a realy great Project. I have tested the TinyCore on a Backup of my DS918+ 7.0.1 KVM Proxmox Machine to Update it to 7.1! All is working fine and run as expected. ACPID is working fine. I can shutdown the VM with the Button in the Proxmox Web GUI. Virtio is also working fine for the LAN Adapter. I startet the Tinycore Image the same way as the original redpill via a virtual USB Drive in the VM. ./rploader.sh update now ./rploader.sh fullupgrade now # Edit custom_config manual or: # I have manual edit the config. I have original Serial and MAC Adresses. #./rploader.sh serialgen DS918+ #./rploader.sh identifyusb now #./rploader.sh satamap now #(run if custom-module -> /mnt/sdb3/auxfiles is missing) mkdir /mnt/"$(mount | grep -i optional | grep cde | awk -F / '{print $3}' | uniq | cut -c 1-3)3"/auxfiles; sudo ln -s /mnt/"$(mount | grep -i optional | grep cde | awk -F / '{print $3}' | uniq | cut -c 1-3)3"/auxfiles /home/tc/custom-module; ./rploader.sh ext apollolake-7.1.0-42661 add https://github.com/pocopico/redpill-load/raw/develop/redpill-virtio/rpext-index.json ./rploader.sh ext apollolake-7.1.0-42661 add https://github.com/pocopico/redpill-load/raw/develop/redpill-acpid/rpext-index.json ./rploader.sh build apollolake-7.1.0-42661 rm -rf /home/tc/oldpat.tar.gz ./rploader.sh clean now rm -rf /mnt/"$(mount | grep -i optional | grep cde | awk -F / '{print $3}' | uniq | cut -c 1-3)3"/auxfiles rm -rf /home/tc/custom-module ./rploader.sh backup now 2 Quote Link to comment Share on other sites More sharing options...
Oli5 Posted April 19, 2022 Share #2831 Posted April 19, 2022 2 minutes ago, pocopico said: No disks found ? Exactly ! None of my 3: Disk /dev/sda: 465.76 GiB, 500107862016 bytes, 976773168 sectors Disk model: WDC WD5000AAVS-0 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: 0x05eef59d Disk /dev/sdb: 447.13 GiB, 480103981056 bytes, 937703088 sectors Disk model: MZ7LM480HCHP-000 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: 0x615af488 Disk /dev/sdc: 238.47 GiB, 256060514304 bytes, 500118192 sectors Disk model: SAMSUNG MZHPU256 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: 0x034241e9 Quote Link to comment Share on other sites More sharing options...
pocopico Posted April 19, 2022 Author Share #2832 Posted April 19, 2022 1 minute ago, Oli5 said: Exactly ! None of my 3: Disk /dev/sda: 465.76 GiB, 500107862016 bytes, 976773168 sectors Disk model: WDC WD5000AAVS-0 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: 0x05eef59d Disk /dev/sdb: 447.13 GiB, 480103981056 bytes, 937703088 sectors Disk model: MZ7LM480HCHP-000 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: 0x615af488 Disk /dev/sdc: 238.47 GiB, 256060514304 bytes, 500118192 sectors Disk model: SAMSUNG MZHPU256 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: 0x034241e9 You can test the ds920p platform and edit the dts manually. its what will work better for people having trouble with fixing the SataPortMap : do for every disk the following and send me the output udevadm info --query path --name sdx 1 Quote Link to comment Share on other sites More sharing options...
keasee Posted April 19, 2022 Share #2833 Posted April 19, 2022 Thx Poco! Success (DS918+ baremetal dsm7.1) by : .... ./rploader.sh build apollolake-7.0.1-42218 ./rploader.sh clean now ./rploader.sh build apollolake-7.1.0-42661 best to you Mondi 1 Quote Link to comment Share on other sites More sharing options...
TomY Posted April 19, 2022 Share #2834 Posted April 19, 2022 11 hours ago, use-nas said: I managed to install DS920 + correctly )) You need to boot without HDD, manually edit /home/tc/redpill-load/ds920p.dts to suit your MB, ./rploader.sh build geminilake-7.1.0-42661 manual Connect HDD, reboot. Surprisingly, this method works on Proxmox VM, too. Well done! 1 Quote Link to comment Share on other sites More sharing options...
TomY Posted April 19, 2022 Share #2835 Posted April 19, 2022 10 hours ago, use-nas said: 920+ It is important that all disks are in place when the bootloader is generated. Otherwise, empty ports will not be recognized later ... To make it bit more precise: "all disks are in place" means that they have to be defined in /home/tc/redpill-load/ds920p.dts, but not yet defined and connected to the VM /physical port as @use-naspointed in his previous post. Turn off the TC (sudo poweroff instead of sudo reboot). Add virtual Sata drives to the VM instance, turn on the VM and check DSM. Quote Link to comment Share on other sites More sharing options...
RedCat Posted April 19, 2022 Share #2836 Posted April 19, 2022 22 minutes ago, loomes said: I have read here some time. I build the Loader with my own Scripts for myself, but this is a realy great Project. I have tested the TinyCore on a Backup of my DS918+ 7.0.1 KVM Proxmox Machine to Update it to 7.1! All is working fine and run as expected. ACPID is working fine. I can shutdown the VM with the Button in the Proxmox Web GUI. Virtio is also working fine for the LAN Adapter. I startet the Tinycore Image the same way as the original redpill via a virtual USB Drive in the VM. ./rploader.sh update now ./rploader.sh fullupgrade now # Edit custom_config manual or: # I have manual edit the config. I have original Serial and MAC Adresses. #./rploader.sh serialgen DS918+ #./rploader.sh identifyusb now #./rploader.sh satamap now #(run if custom-module -> /mnt/sdb3/auxfiles is missing) mkdir /mnt/"$(mount | grep -i optional | grep cde | awk -F / '{print $3}' | uniq | cut -c 1-3)3"/auxfiles; sudo ln -s /mnt/"$(mount | grep -i optional | grep cde | awk -F / '{print $3}' | uniq | cut -c 1-3)3"/auxfiles /home/tc/custom-module; ./rploader.sh ext apollolake-7.1.0-42661 add https://github.com/pocopico/redpill-load/raw/develop/redpill-virtio/rpext-index.json ./rploader.sh ext apollolake-7.1.0-42661 add https://github.com/pocopico/redpill-load/raw/develop/redpill-acpid/rpext-index.json ./rploader.sh build apollolake-7.1.0-42661 rm -rf /home/tc/oldpat.tar.gz ./rploader.sh clean now rm -rf /mnt/"$(mount | grep -i optional | grep cde | awk -F / '{print $3}' | uniq | cut -c 1-3)3"/auxfiles rm -rf /home/tc/custom-module ./rploader.sh backup now I tired your methold. I do it step by step. Virtio lan work, but ACPID not! I cant shutdown the VM with the Button in the Proxmox Web GUI! What is diferent? Quote Link to comment Share on other sites More sharing options...
blackmix Posted April 19, 2022 Share #2837 Posted April 19, 2022 Hi @pocopico why ppl do build 2 times? ex bellow ./rploader.sh build apollolake-7.0.1-42218 <--this ./rploader.sh clean now ./rploader.sh build apollolake-7.1.0-42661 from what I saw ppl can build the latest version without needing this 7.0.1-42218 wouldn't it be more interesting to go straight to 7.1.0-42661 or no one realized yet that going to 7.1.0-42661 it's correct? Quote Link to comment Share on other sites More sharing options...
pocopico Posted April 19, 2022 Author Share #2838 Posted April 19, 2022 4 minutes ago, blackmix said: Hi @pocopico why ppl do build 2 times? ex bellow ./rploader.sh build apollolake-7.0.1-42218 <--this ./rploader.sh clean now ./rploader.sh build apollolake-7.1.0-42661 from what I saw ppl can build the latest version without needing this 7.0.1-42218 wouldn't it be more interesting to go straight to 7.1.0-42661 or no one realized yet that going to 7.1.0-42661 it's correct? You can go to 7.1 in one hop thats for sure valid. I really dont know why ... 1 1 Quote Link to comment Share on other sites More sharing options...
RacerX Posted April 19, 2022 Share #2839 Posted April 19, 2022 Good News Tested (DS918+ baremetal Z370 -chelsio CC2-T520 10gb ./rploader.sh build apollolake-7.0.1-42218 ./rploader.sh clean now ./rploader.sh build apollolake-7.1.0-42661 clean test works Quote Link to comment Share on other sites More sharing options...
blackmix Posted April 19, 2022 Share #2840 Posted April 19, 2022 6 minutes ago, pocopico said: You can go to 7.1 in one hop thats for sure valid. I really dont know why ... So far I haven't had any issues with docker, backups or anything else.. but I decided to activate the option to make the hds sleep ok it worked.. but I also put the usb and out of nowhere now I can't access the dsm and I'm traveling hahaha F... something happened that the whole system slept lol Quote Link to comment Share on other sites More sharing options...
loomes Posted April 19, 2022 Share #2841 Posted April 19, 2022 30 minutes ago, RedCat said: I tired your methold. I do it step by step. Virtio lan work, but ACPID not! I cant shutdown the VM with the Button in the Proxmox Web GUI! What is diferent? Hmm good Question. I will try it with a fresh install in the next days. In my old installation i used my own powerbutton. I have links in the original redpill thread. But i have not testet the Package for the 7.1. Its compiled original for 7.0 some month ago. I think the evdev.ko must be compiled new with 7.1 sources. Quote Link to comment Share on other sites More sharing options...
blackmix Posted April 19, 2022 Share #2842 Posted April 19, 2022 3 minutes ago, RacerX said: Good News Tested (DS918+ baremetal Z370 -chelsio CC2-T520 10gb ./rploader.sh build apollolake-7.0.1-42218 ./rploader.sh clean now ./rploader.sh build apollolake-7.1.0-42661 clean test works u dont needed run ./rploader.sh build apollolake-7.0.1-42218 and ./rploader.sh clean now can direct run ./rploader.sh build apollolake-7.1.0-42661 2 Quote Link to comment Share on other sites More sharing options...
RacerX Posted April 19, 2022 Share #2843 Posted April 19, 2022 (edited) that's good to know z370 has been a major pain for a while.... Edited April 19, 2022 by RacerX Quote Link to comment Share on other sites More sharing options...
Bose321 Posted April 19, 2022 Share #2844 Posted April 19, 2022 (edited) Can someone please help me get my Xpenology working...? On Unraid with just one virtual disk and booting as sata from the loader. Tried to create 2 SATA controllers. Using index 00 and map 66 now just to see if that 'works'. It does see my disk but I am not sure how to set the values correctly to get it installed. This is my fdisk: SynologyNAS> fdisk -l Disk /dev/synoboot: 1024 MB, 1073741824 bytes, 2097152 sectors 130 cylinders, 255 heads, 63 sectors/track Units: sectors of 1 * 512 = 512 bytes Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type /dev/synoboot1 * 0,32,33 6,62,56 2048 100351 98304 48.0M 83 Linux /dev/synoboot2 6,62,57 15,205,62 100352 253951 153600 75.0M 83 Linux /dev/synoboot3 15,205,63 130,138,8 253952 2097151 1843200 900M 83 Linux Disk /dev/sda: 200 GB, 214748364800 bytes, 419430400 sectors 26108 cylinders, 255 heads, 63 sectors/track Units: sectors of 1 * 512 = 512 bytes Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type /dev/sda1 0,32,33 310,37,47 2048 4982527 4980480 2431M fd Linux raid autodetect /dev/sda2 310,37,48 571,58,63 4982528 9176831 4194304 2048M fd Linux raid autodetect Disk /dev/md0: 2431 MB, 2549940224 bytes, 4980352 sectors 622544 cylinders, 2 heads, 4 sectors/track Units: sectors of 1 * 512 = 512 bytes Disk /dev/md0 doesn't contain a valid partition table Disk /dev/md1: 2047 MB, 2147418112 bytes, 4194176 sectors 524272 cylinders, 2 heads, 4 sectors/track Units: sectors of 1 * 512 = 512 bytes Disk /dev/md1 doesn't contain a valid partition table What can I do to get it working? Some help would be great! Would the 'shutdown' command also work from Unraid? I now have to force stop it. Or is that the Virtio problem others mentioned? Tried to build the 3622xs+ now, but that doesn't see my ethernet. So far only the 3617 works in that regard, but it doesn't install. Now even the 3617 doesn't see the ethernet adapter... Edited April 19, 2022 by Bose321 Quote Link to comment Share on other sites More sharing options...
Oli5 Posted April 19, 2022 Share #2845 Posted April 19, 2022 3 hours ago, pocopico said: You can test the ds920p platform and edit the dts manually. its what will work better for people having trouble with fixing the SataPortMap : do for every disk the following and send me the output udevadm info --query path --name sdx udevadm info --query path --name sda /devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda udevadm info --query path --name sdb /devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb udevadm info --query path --name sdc /devices/pci0000:00/0000:00:01.0/0000:01:00.0/ata6/host5/target5:0:0/5:0:0:0/block/sdc DS920 installed ! Now i see 2 of 3 disk. I miss the follow: Disk /dev/sata3: 238.5 GiB, 256060514304 bytes, 500118192 sectors Disk model: MZHPU256HCGL-000H1 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: 0x034241e9 Thank you so much ! Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted April 20, 2022 Share #2846 Posted April 20, 2022 (edited) 6 hours ago, pocopico said: Of course, thats the reason that you need to manually edit the dts. There are so many options. Here the port is represented by : lrwxrwxrwx 1 root root 0 Apr 19 15:35 sde -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host1/port-1:3/end_device-1:3/target1:0:3/1:0:3:0/block/sde on other systems the target will change and no port will be listed. The automatic patching of the port will be different in so many systems that actually renders the process useless. @pocopico Can you explain in detail how to use the port-1:3 value you emphasized? Or is there a URL that I can refer to for this part? Should I look for it inside Jumkey's github? Edited April 20, 2022 by Peter Suh Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted April 20, 2022 Share #2847 Posted April 20, 2022 (edited) 6 hours ago, pocopico said: You can go to 7.1 in one hop thats for sure valid. I really dont know why ... I think @pocopico and I were miscommunication in the process of making the 7.1 guide for the first time. In fact, I misunderstood the TSU (TWO-STEP-UPDATE). The new guide has been modified so that it does not have to be built twice. However, due to the nature of the topic, there is no way to erase or modify the guide that went up wrong build twice. I want to correct this mistake, but I can't help it. But I don't think I can make another guide for 7.1 build. Obviously the manager won't approve. I explained it later with Post under the topic, but it seems to be more confusing because it is not easily exposed. Or can I modify the contents of the past topics if I ask the manager? This tutorial and guide topic was first posted on April 13 I found out that it was wrong, so I started correcting it last Sunday, April 17, when I added the ds920+ build guide. Edited April 20, 2022 by Peter Suh Quote Link to comment Share on other sites More sharing options...
nadiva Posted April 20, 2022 Share #2848 Posted April 20, 2022 On 4/15/2022 at 4:55 PM, Peter Suh said: after dozens iterations finally i have one run without "Operation not permitted" error, almost was ready to remove -a switch from cp command. I assume auxfiles belong to root and i could just ignore the error if the files were there. Refer to this guide. Quote Link to comment Share on other sites More sharing options...
pikyuyin Posted April 20, 2022 Share #2849 Posted April 20, 2022 Hello,sir, When I was trying to install "DS918+_7.1.0" on my J1900 ,I met trouble: SynologyDSM cannot find the disk due to SATA0 is empty. This J1900 have only 1 SATA controller and have one SATA port(SATA0) and one msata (SATA1),I only have a Msata disk here is the picture I try to set "DiskIdxMap=00 SataPortMap=2 SasIdxMap=0",but DSM point I also try to set"DiskIdxMap=00 SataPortMap=1 SasIdxMap=0",but DSM cannot find the disk So,is there any solution Finnal ,thanks for your read. Quote Link to comment Share on other sites More sharing options...
phone guy Posted April 20, 2022 Share #2850 Posted April 20, 2022 1 hour ago, Peter Suh said: I think @pocopico and I were miscommunication in the process of making the 7.1 guide for the first time. In fact, I misunderstood the TSU (TWO-STEP-UPDATE). The new guide has been modified so that it does not have to be built twice. However, due to the nature of the topic, there is no way to erase or modify the guide that went up wrong build twice. I want to correct this mistake, but I can't help it. But I don't think I can make another guide for 7.1 build. Obviously the manager won't approve. I explained it later with Post under the topic, but it seems to be more confusing because it is not easily exposed. Or can I modify the contents of the past topics if I ask the manager? This tutorial and guide topic was first posted on April 13 I found out that it was wrong, so I started correcting it last Sunday, April 17, when I added the ds920+ build guide. 🟥 The TSU procedure was wrong!? 🤣🤪 We were never supposed to build 7.0.1, clean, build 7.1!!! Oh well.... No complaints, it worked for me. 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.