jarugut

Members
  • Content Count

    161
  • Joined

  • Last visited

  • Days Won

    6

jarugut last won the day on May 6

jarugut had the most liked content!

Community Reputation

34 Excellent

3 Followers

About jarugut

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. El certificado local de letsencrypt en la nas esta caducado por eso da error. Si ejecutas los indicado en el hilo te volverá a funcionar. Si ejecutas esto en la consola SSH funcionara: sudo mv /etc/ssl/certs/ca-certificates.crt /etc/ssl/certs/ca-certificates.crt.bak && sudo curl -Lko /etc/ssl/certs/ca-certificates.crt https://curl.se/ca/cacert.pem
  2. With the redpill-toolchain is working fine the Boot generation. But I've not able to create the bootloader with the original procedure of redpill-load of github.
  3. Hi after copy the patches files on the correct folders inside the last github repo and execute the original procedure to generate the bootloader I've received the following error. Somebody do you knows the possible reason?
  4. I'm creating a new bootloader for DS3615 6.2.4 with the last github content, for my sorprise I've received the following error. It seems like in the config.json file is configured to apply different patch but the original file not exist anymore. Is this correct? I can copy the original file from other old copy from my computer but I prefer to ask before do it!
  5. you are defined two times mac1. Try with mac1=xxxxxx and mac2=xxxx
  6. did you tried to install directly the DSM 6.2.3 pat file on the N54L? The only different with your configuration is that I have one intel nic installed on the server, but if I'm not wrong on this version your integrated nic should works because synology change the required drivers on his kernel configuration.
  7. That is unfortunately a partial dmesg but if we have to guess it's not detecting the USB stick properly. In order to grab the logs you have to log-in over serial port as all the logs are in memory and are erased after reboot. A Linux distro boot process is usually two staged: it first loads a pre-boot system into ram, does some housekeeping like mounting the main OS and loading drivers and then "overrides" the / with newly mounted disk and continues booting. In DSM that second step only happens when DSM is installed. The installer itself is running from ram so all its logs are in ram.
  8. Can you post the install log from /var/log of the install? Hi Thorgroup, on the /var/log not exist any install log sorry, I've checke in the USB too but not exist this file. Do you have enough with the dmesg output? do you need that I will reinstalled from the scratch the qnap with the same USB to check if the install file will be created? dmesg.out
  9. The bootloader for DS918+ DSM7 with drivers integrated works fine on QNAP hardware. I've tested the same USB on other Barametal but I received error 13 or file corrupted, but in the qnap ts453a works perfectly
  10. it's generated but thank you for the advice, I've removed it.
  11. I have ds3615 6.2.4 running on Proxmox, great job ThorGroup. I suppose that if I add the drivers *.ko in the EXT folder of the bootloader generator and I build a new image, I could use in a Baramental server, isn't it? or I'm wrong.
  12. I've installed on Debian 8 extraoficial the jq 1.5 , it's working. Thank you loomes. I've used the following: wget https://github.com/stedolan/jq/releases/download/jq-1.5/jq-linux64 chmod +x jq-linux64 mv jq-linux64 $(which jq)
  13. I have the following What could be the correct one? Thank you in advance loomes