pggx999 Posted June 27, 2022 Share #1 Posted June 27, 2022 1st post here. Tags or Magick words related to this issue: Failed to install DSM, Error trying to load PAT at 55%, Prior things done/check Install TinyCore Boot USB to TinyCore Build with DS3622xs+ USB Kingston (good compatibility) Supermicro Board (good compatibility) Boot correctly into DSM Loader Problem: After loading PAT file (proper version) you get the message "Failed to install the file. The file is probably corrupted" Spoiler Analyzis: After finding the serial console provided by TinyCore on http://<yourip>:7681 (user/pass root/<blank>). If you check with cat/vi the log file linuxrescue.... cat /var/log/*rc* You will see some error messages like this ... Still waiting for boot device (waited 28 of 30 seconds) Still waiting for boot device (waited 29 of 30 seconds) Still waiting for boot device (waited 30 of 30 seconds) ERROR: Timeout waiting for /dev/synoboot device to appear. Most likely your vid/pid configuration is not correct, or you don't have drivers needed for your USB/SATA controller ... If this is the case.... maybe (but maybe) DSM Loader cant find the USB drive, despite from the fact that you correctly set the PID VID on the config. *You can check also running df -h or any other commando showing that the USB stick wasnt mounted/detected Cause: This could be caused by many things, but the one I found in this case is that the USB is connected in another port not used by DSM. I will be as simple as posible... DSM 7.1 on 3622xs+ looks at firsts BUS/PCI combination for the USB VID/PID provided, so bad luck on my trying to boot. My hardware has the USB port on BUS/Device: 2-3 (Reference photo) Solution: Here comes the good part.. How can we specify a new BUS/Device location on 3622? no idea.... xD But i've found that models DS920+ and DS1621+ have some .dts files on the redpill github. And they show at the very bottom the following curious info usb_slot@1 { vbus {syno_gpio = <0x2a 0x1>;}; usb2 {usb_port = "1-2";}; usb3 {usb_port = "2-2";}; }; usb_slot@2 { vbus {syno_gpio = <0xb 0x1>;}; usb2 {usb_port = "3-1";}; usb3 {usb_port = "4-1";}; }; usb_slot@3 { vbus {syno_gpio = <0xc 0x1>;}; usb2 {usb_port = "1-3";}; usb3 {usb_port = "2-3";}; }; }; I guess you've realized were we are going. the rploader.sh script updates ONLY the line for usb_slot@1 on this file with the proper PID/VID of your USB stick. So what I did was, after runing identifyusb, I've changed manually the usb_port for usb2 on usb_slot@1 with the proper BUS/Device info obtain from the lsusb command on tinycore (where my usb were connected) Bonus: You can use 1Gb USB Stick with no problem Bonus2: I guess this applies to all DSMs and Loaders Hope this helps, took me 1 day to figure out. 3 Quote Link to comment Share on other sites More sharing options...
Castelrink Posted October 4, 2022 Share #2 Posted October 4, 2022 Hola, Tengo justo este problema, me da error cuando la instalación está en el 55%. Me parece muy interesante tu explicación y me te agradecería si me ayudaras... Como puedo abrir el archivo .pat para modificar los puertos USB? Un saludo. Quote Link to comment Share on other sites More sharing options...
Polanskiman Posted October 13, 2022 Share #3 Posted October 13, 2022 On 10/5/2022 at 5:31 AM, Castelrink said: Hola, Tengo justo este problema, me da error cuando la instalación está en el 55%. Me parece muy interesante tu explicación y me te agradecería si me ayudaras... Como puedo abrir el archivo .pat para modificar los puertos USB? Un saludo. This is the English section of the forum. Please post in English. Quote Link to comment Share on other sites More sharing options...
apriliars3 Posted October 13, 2022 Share #4 Posted October 13, 2022 This is very interesting. Can someone explain how map this ports with .dts? .dts is here on stable version of tcrp GitHub - pocopico/tinycore-redpill at stable I think need modify .dts and add to /home/tc/custom-modules folder and then apply ./rploader.sh <platform> patchdtc Quote Link to comment Share on other sites More sharing options...
pggx999 Posted March 4, 2023 Author Share #5 Posted March 4, 2023 On 10/4/2022 at 7:31 PM, Castelrink said: Hola, Tengo justo este problema, me da error cuando la instalación está en el 55%. Me parece muy interesante tu explicación y me te agradecería si me ayudaras... Como puedo abrir el archivo .pat para modificar los puertos USB? Un saludo. Greetings from Chile no es el .pat el archivo que se "abre" ya que eso es el "software", son los archivos .dts. Te sugiero primero intentar ver en la seccion del analisis si te da el mismo error por la consola (terminal web) Please write in english, remember, "english section" On 10/13/2022 at 5:53 AM, apriliars3 said: This is very interesting. Can someone explain how map this ports with .dts? .dts is here on stable version of tcrp GitHub - pocopico/tinycore-redpill at stable I think need modify .dts and add to /home/tc/custom-modules folder and then apply ./rploader.sh <platform> patchdtc Exactly, everything is explained in the post, you have to see the USB location of yout ports with lsusb command and then put those numbers in the .dts file Quote Link to comment Share on other sites More sharing options...
slinpk Posted April 15, 2023 Share #6 Posted April 15, 2023 I've run on the same problem as pggx99. fanless nettop with: core i5-4th generation CPU 4GB RAM SATA HDD (AHCI mode) tried 6 different USB sticks from 2Gb up to 16Gb. tried with https://github.com/fbelavenuto/arpl but had no success. succesfully installed in Promox on VM, but it is not my aim, it was just an experiment. now i am trying to do the same with https://github.com/pocopico/tinycore-redpill also no success. checked the lsusb and got the following: tc@box:~$ lsusb Protocol spec without prior Class and Subclass spec at line 23281 Bus 001 Device 002: ID 8087:8000 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 005: ID 13d3:3408 IMC Networks Bus 002 Device 004: ID 248a:00da Maxxter Bus 002 Device 003: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive Bus 002 Device 002: ID 1ea7:0066 SHARKOON Technologies GmbH [Mediatrack Edge Mini Keyboard] Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub seems like my problem could be solved by the solution described above by pggx99, but i cannot find .dts files, due to i am not an expert with linux/github. Could you please explain, where can i get these .dts files? Quote Link to comment Share on other sites More sharing options...
pggx999 Posted April 17, 2023 Author Share #7 Posted April 17, 2023 On 4/15/2023 at 7:03 AM, slinpk said: I've run on the same problem as pggx99. fanless nettop with: core i5-4th generation CPU 4GB RAM SATA HDD (AHCI mode) tried 6 different USB sticks from 2Gb up to 16Gb. tried with https://github.com/fbelavenuto/arpl but had no success. succesfully installed in Promox on VM, but it is not my aim, it was just an experiment. now i am trying to do the same with https://github.com/pocopico/tinycore-redpill also no success. checked the lsusb and got the following: tc@box:~$ lsusb Protocol spec without prior Class and Subclass spec at line 23281 Bus 001 Device 002: ID 8087:8000 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 005: ID 13d3:3408 IMC Networks Bus 002 Device 004: ID 248a:00da Maxxter Bus 002 Device 003: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive Bus 002 Device 002: ID 1ea7:0066 SHARKOON Technologies GmbH [Mediatrack Edge Mini Keyboard] Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub seems like my problem could be solved by the solution described above by pggx99, but i cannot find .dts files, due to i am not an expert with linux/github. Could you please explain, where can i get these .dts files? First try with this versions DS920+ and DS1621 After downloading the custom modules, find the dts files in the folder /home/tc/custom-module/${dtbfile}.dts If not, try with find finding them. After you find them, modify them as will Quote Link to comment Share on other sites More sharing options...
jMiguel Posted August 10, 2023 Share #8 Posted August 10, 2023 On 4/17/2023 at 4:36 PM, pggx999 said: First try with this versions DS920+ and DS1621 After downloading the custom modules, find the dts files in the folder /home/tc/custom-module/${dtbfile}.dts If not, try with find finding them. After you find them, modify them as will Hello, The same thing happened to me, and I spent several days looking for the solution, I finally got it by chance, this is what I did: 1. Load the loader and install DSM 2. When the progress reaches approximately 58% the server restarts. 3. Then load "Tiny Core Friend" in Grub and wait for the process to finish, you will see that it says something like "ramdisk upgrade" 4. Reboot the server and select "redpill dsxxx ..... (USB, Verbose) At that moment you will see that the installation continues and DSM starts. Very important that you execute: ./rploader.sh ext apollolake-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/rp-ext/master/redpill-acpid/rpext-index.json ./rploader.sh ext denverton-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/rp-ext/master/v9fs/rpext-index.json I hope this works for you. Greetings Quote Link to comment Share on other sites More sharing options...
ikkeenjij36 Posted August 18, 2023 Share #9 Posted August 18, 2023 I had the same problem that every build would fail on installing the .pat file Solution for me was to plug in the usb in a different usb port on my duild Starnge but true Quote Link to comment Share on other sites More sharing options...
Cyborg666 Posted October 5, 2023 Share #10 Posted October 5, 2023 (edited) I also had such a problem, I wanted to get away from the ARPL loader on ARC, after configuring the loader, I saw an offer to update YOU, but after selecting the downloaded DSM 7.2, I got a 55% error, in my case everything was solved simply, I disconnected the USB cable from the UPS and bluetooth dongle from the motherboard, reassembled the loader and everything worked from the first three times. Edited October 5, 2023 by Cyborg666 correct Quote Link to comment Share on other sites More sharing options...
Tomte Posted December 6, 2023 Share #11 Posted December 6, 2023 Hello, unfortunately, the way to solve the problem is not clear to me. How do I get the patch? Do I actually have to build a DS920+? Any help/hint is appreciated Regards, Tomte Quote Link to comment Share on other sites More sharing options...
Tomte Posted December 8, 2023 Share #12 Posted December 8, 2023 I solved my problem using Arc DSM loader. 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.