phone guy

What about performance with Quadro P2000 ? And why some work and some do not? anyone figure that one?

Rebuild your loader using JUN mode or JOT mode, then updating will work (use at your own risk)

The update procedure requires you to update to dsm7.1U3 inside dsm using manual update. Then when the system restarts, you must go back to tiny core from the initial grub menu (press down to the last item boot to tiny core), then ssh into tinycore and issue the following commands ./rploader.sh backup ./rploader.sh update now ./rploader.sh fullupgrade now ./rploader.sh postupdate <yourplatform> Then reboot, choose boot from usb again from the grub menu and you should have update 3... Thats how I did it. 👍

Thats interesting, as according to @pocopico and @flyride DS918 and DVA3221 require Haswell+ to run, because of FMA3 instruction set being required by Kernel or something else? I can verify that 918 and 3221 do not and will not load on Xeon E3-1270v2 or E5-2650v2 cpu's. I have tried in proxmox and both Kernel Panic during boot.

Which platform to pick 920? geminilake? and it does auto create the dtc ?

Make sure you run ./rploader.sh identifyusb now to make sure usb is hidden. if you are doing bare metal you are most likely booting from usb. boot back to tinycore and either clean and start fresh by whatever means makes you comforable - rewrite usb, clean, whatever, be sure to run that command and build again. Theres a way to login in telnet to get the serial logs, but I have never done it... its <ip>:7681 user is root no pw if I remember right. or you can search for the directions, theyve been posted a bunch of times. otherwise clean and start again, the basic starter commands ./rploader.sh update now ./rploader.sh fullupgrade now ./rploader.sh serialgen <your platform here> ./rploader.sh identifyusb now ./rploader.sh satamap now ./rploader.sh ext <your platform here> add <pick ext/drivers from https://github.com/pocopico/rp-ext> ./rploader.sh build <your platform here> Good luck (sorry I cant be more help)

DS3622xs+ runs on anything. I am using it in proxmox on older xeon cpus

He wants the serial output log

Haswell or better for DVA3221 😪 my E3-1270v2 or E5-2650v2 are too old too. However you could use DVA1622, but that requires integrated intel cpu graphics.

Can DVA1622 work/use more than the 2 drives? Is there a drive limit for DVA1622?

Make sure you add mpt3sas driver for the HBA card. and of course LSI card has to be in IT mode. Once you have card in HBA (IT) mode, and drivers (mpt3sas) installed, drives connected will appear. satamap and diskidxmap have no effect on HBA, so the drives on the HBA will just appear after whatever you have on built in AHCI (sata) ports. The satamap diskidxmap does effect (only effects) AHCI sata ports, not HBA.

🤣 I was expecting something a little more technical. But yeah, I guess that works too.

I personally do not use esxi, just proxmox, sorry.

I ran into a small snag doing the U3 update for a baremetal 918 build. I am in a recovery loop, it comes up with a different ip than before and says recoverable. I click recover and it repeats. Solved: did CLEAN, and rebuild, then postupdate (again) and it all came back. 🤪 just got nervous for a minute 😆

I find this interesting, but as I do believe pocopico is involved in the qnap project also, I do not think it has gotten much attention? I may be wrong. I wouldn't mind trying/playing Qnap, but overall Synology is the first name in NAS.

To be clear, has anyone used a real serial/mac from a different model than the platform they build the loader for and successfully authorized AME? Example: used real serial/mac for DS920 on loader build for DS3622 and gotten AME to authorized successfully? Syno HQ is not verifying serial/mac against model number???

I had this same battle. @flyride helped me in that link @pocopico posted on page 14... To get your HBA to start at slot 1 use i440fx system in proxmox, not Q35. Pci passthrough still works. I honestly do not know what, if any, advantages are to q35 vs i440fx in proxmox. My system (ds3622) has been in production for many weeks, is used as a backup server for ABB and HB nightly and has given me zero problems. I do not know if there are performance hits or not, I would be happy to test any performance procedures. In the end, I agree its purely cosmetic, but I wanted it to be correct, and because I saw no difference in the use case of my DSM instance, no performance hit, no operational difference, I choose i440fx. I get all actual smart data from drives, including serials, models, and temperature from the HBA in pci passthrough. If any has or knows if there are any performance or use differences between q35 and i440fx I am all ears.

Support for AMD Ryzen would be platform DS1621 or DS2422, 1621 is already part of redpill.

For the record, I quickly tested DVA1622 using arpl03-a3 in proxmox. I did use the above command to expand the arpl image to 4gb. I used the same method for settin up proxmox for arpl as I did for tcrp @pocopico release of my DS3622xs+ build, those detailed instructions are linked in my signature with pictures and can easily be used as a guide to install arpl on proxmox... the only difference (obviously) was I used the arpl image instead of the tcrp image, and again I expanded the img. I booted the VM logged into the ip:7681, added the hw misc and acpid from the list, built the loader and rebooted the vm and successfully booted into DVA1622 and completed dsm install 42661-U3. It was painless and super fast to build the loader. pretty cool. I could not test the AI as my proxmox server is running a Xeon E3-1270v2 without graphics but I did have all 8 SS licenses. Great job @fbelavenuto FYI: the acpid doesn't work, as I tried to click shutdown of the vm in proxmox and opened the console to watch dsm process shutdown, and it did not shutdown. After about 4-5 mins I manually shutdown the dsm instance. So, whichever acpid is shown does not actually work on DVA1622.

Are the drive temps reported thru dms, using redpill, HBA with pci passthrough in proxmox vm, accurate? or is the data shimmed or spoofed? I remember reading certain smart data is spoofed or shimmed in redpill, and I am not sure if this is accurate. My DS3622XS+ redpill build is in proxmox, with an HBA passthru to the DSM VM. I can accurately see s/n of drives, just not 100% sure about temp. Hoping @pocopico or @flyride can answer for sure for me. Thanks.

You should be fine

Depending on which platform you built redpill for, it should auto detect new drives, after you pass through the drive in proxmox.

I believe @pocopico worked with @fbelavenuto who did arpl project, to get that working...

After you have your xpenology setup, you can add another drive in proxmox and symbology dsm will auto detect it. Did you pass thru a pci card? Or sata controller? One just one hdd entirely thru proxmox to dsm?

In proxmox, I use usb loader (virtual usb loader) and boot usb from the redpill loader. Maybe try usb load instead of sata load for your redpill/arpl loader. Then, with no virtual sata controllers, your passthrough hba should then be correct.