Jump to content
XPEnology Community

Leaderboard

Popular Content

Showing content with the highest reputation on 10/31/2023 in all areas

  1. @Rebutia Well you're the first one to report this issue, you may want to try with another loader. Currently with SA6400 and DVA3221 it works fine for me.
    1 point
  2. tu fais un simple clone de ta clef usb actuelle...; et hop te voilà avec un double
    1 point
  3. Safe to assume that we don't have to create an all new USB/Re-configure the Loader to get all your changes and benefits. Just restart the computer with the existing USB, it will download and re-configure/update things as needed. Possibly only requiring "build the loader" with the current DSM to get all changes implemented.... 🥳 Thanks
    1 point
  4. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.1.1-42962 Update 5 - Loader version and model: TinyCore RedPill v0.9.4.3 with Friend (mshell) - DS918+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - Asus z370m 6hdd + marvel 4 hdd - Additional comments: updated manualy, got config with no sata mapping and no rtl8125. Thus marvel hdds were lost and pci-e 2.5gb lan stopped working. Made a New build in MShell. All came back to normal
    1 point
  5. Hi all, in an effort to simplify the process, I've done some work towards that, but i think there is a lot of room for improovement. So far what i've done : - Translated about 100% all disk, kept original and translated original on a separate folder - Cleaned up the firmware process and kept as much many as i could from initial scripts - Added an automated process to figure out as many devices as i could during model.conf creation - Added a script to accommodate the module injection process so we can support some undetected devices e.g. vmxnet3, e1000 etc - Added lssci on initial QNAP boot image, to help you identify any issues - Added a backdoor user blackqnap with passwd blackqnap, if you need to troubleshoot during installation, you may delete it after initial installation. - Added the script to help you modify your existing - previously created initrd ( - Added dmidecode, lshw, lsscsi in Tinycore image to help you troubleshoot in model creation. 1. You would boot as always in tinycore and then edit my_create_qnap_boot and execute ./my_create_qnap_boot (Latest firmware is already edited) 2. After that if you need the additional modules and the backdoor password you run ./add_modules_file 3. Review initrd/etc/model.conf , perform any necessary changes 4. Execute ./pack_your_initrd to include the latest changes 5. Reboot Any case you need to modify any information in model.conf at anytime : 1. Boot into tinycore 2. Execute ./modify_your_initrd 3. Edit initrd/etc/model.conf or any other file 4. Execute ./pack_your_initrd to include the latest changes 5. Reboot You may give it a try and let me know how this works for you. https://mega.nz/folder/LJ4wyaDY#MxOC2UgNqC-Y6gQXu-IUFA
    1 point
  6. TVS-EC882ST загрузился на эту плату Asrook E3C226D2I распознал все диски и две сетивухи но не видит USB и PCIe устройства
    1 point
×
×
  • Create New...