Leaderboard

+1

Тоже за неё ..... Во первых новая, во вторых лучше НР

Думаю что ASRock J4125-ITX + 8gb будет лучше так как 4 SATA есть на плате. Что касается HP EliteDesk 800 если он в sff корпусе то там только 3 SATA и туда могут не влезть 3 диска на 3.5". Если он в корпусе Tower то там смотреть надо сколько SATA на плате. Да и Celeron J4125 по энергопотреблению не такой прожорливый.

Yesterday, I modified rploader.sh a little bit and tried TC loader build according to jumkey's instructions. rploader.sh modifies the line below under the assumption that it is the latest version 0.7.0.8. LINE #2117 # getlatestrploader LINE #1675 sudo BRP_JUN_MOD=1 BRP_DEBUG=1 BRP_USER_CFG=user_config.json ./build-loader.sh $MODEL $TARGET_VERSION-$TARGET_REVISION loader.img The log related to the loader building came out as below, and something more detailed seems to appear. Loader building is successful and DSM installation is still being tested. If you want to upgrade to 7.1 you may need to add redpill-misc in TC like this. ./rploader.sh ext apollolake-7.0.1-42218 add https://github.com/jumkey/redpill-load/raw/develop/redpill-misc/rpext-index.json

- Grub USB is to support a USB key for boot, or an emulated USB key image if desired when virtualized. - SATA USB is a disk image specifically for VMware as there is no way to emulate a USB key or boot from it. I don't know if it works on Proxmox. - PAT file needs to be downloaded by the loader in order to create the loader. DSM install also needs to use the PAT file. You can download the necessary pat files and host locally, and push to TCRP install if you don't like pulling it from the internet repeatedly. - See answer #2, you probably need to emulate or use a physical USB key. Look for folks that have installed on proxmox. Documentation on this will improve. I'm working on a general installation document and a VMware addendum. Typically others pitch in with variants for the other hypervisors.

Trying to isntall 3622xs+ on proxmox using the below steps: create the guest: # set vm id id=930 ver=0.4.6 # create image directory, download and uncomporess mkdir -p /var/lib/vz/images/${id} curl --location https://github.com/pocopico/tinycore-redpill/raw/main/tinycore-redpill.v${ver}.img.gz --output /var/lib/vz/images/${id}/tinycore-redpill.img.gz gzip --decompress /var/lib/vz/images/${id}/tinycore-redpill.img.gz --keep # create disk for sata0 pvesm alloc local-lvm ${id} vm-${id}-disk-0 100G # create vm qm create ${id} \ --args "-drive 'if=none,id=synoboot,format=raw,file=/var/lib/vz/images/${id}/tinycore-redpill.img' -device 'qemu-xhci,addr=0x18' -device 'usb-storage,drive=synoboot,bootindex=5'" \ --cores 2 \ --cpu host \ --machine q35 \ --memory 2048 \ --name DSM \ install tcrp: ./rploader.sh update now ./rploader.sh fullupgrade now ./rploader.sh serialgen DS3622xs+ ./rploader.sh identifyusb now ./rploader.sh satamap now ./rploader.sh build broadwellnk-7.0.1-42218 ./rploader.sh clean now ./rploader.sh ext broadwellnk-7.1.0-42661 add https://github.com/pocopico/redpill-load/raw/develop/redpill-virtio/rpext-index.json ./rploader.sh ext broadwellnk-7.1.0-42661 add https://github.com/pocopico/redpill-load/raw/develop/redpill-acpid/rpext-index.json ./rploader.sh build broadwellnk-7.1.0-42661 GRUB shows: RedPill DS3622xs v7.1.0-42661 Beta (USB, Verbose) * RedPill DS3622xs v7.1.0-42661 Beta (SATA, Verbose) TinyCore ... Afterwards when I go to the web page I see: Welcome! Set up your Synology DS3622xs+ now I click on Install and it prompts me for a pat file So I select and install the pat downloaded from synology and I get error: Failed to install the file is probably corrupt Questions: 1. What is the difference in GRUB between the USB and SATA entries? 2. Are these the right steps to install on proxmox? 3. Why is it asking to install a pat file when it seems that tcrp is downloading that file already for me? 4. and of course, how to fix the error

@jumkey please remember to sync your redpill-misc to the one i've modified from my repo. Takes care of several other issues. redpill-load/include/loader-ext/target_exec.sh_ is also modified in my repo to allow extension colliding dependencies to load correctly.

Hi. Unfortunately no. It's not relevant for me right now. I left my home due to war((