gadreel

What I meant to say is that if you want to take Snapshots you will need Btrfs. If you do not need those you can stick with Ext4.

Hi, you have answered your own question . If you are not using any of those APPs that require Btrfs then there is no need for it if you are just storing data.

If you want to use Cloudflare Tunnel and you do not want others to mess with the DSM login page create application policies to protect it.

No. Raspberry Pi 4 has an ARM CPU which is not compatible. Only x86, x86-64 architecture CPUs are supported like Intel and AMD.

Yes read this guide to see the limits for each platform. As you mentioned the DS918+ cannot have more than 8 cores... Install DS3622xs+ if you want to have more cores.

If bootloader was not updated, yes. Sonoloygy does not always update it with minor patches that is why u still see U2

Hello guys, I just replaced my old motherboard with a new ASRock Rack X570D4U-2L2T/BCM. This motherboard contains the 2 x 10Gbe [14e4:16d8] 24:00.1 Ethernet controller: Broadcom Inc. and subsidiaries BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet Controller (rev 01) This motherboard also contains 2 x 1Gbe Intel I210 Previously I had a PCI card with 2 x 10gbe X550 Intel and it was working fine. To the question. I have ARPL loader v0.4-alpha 6 which works fantastic on my (Virtual) DS918+ and I do not want to replace it with an updated version. What is the correct procedure to detect this new BCM 10Gbe? I tried to only rebuild the loader and it does not work. If I pass-through the I210 it works just fine when I rebuild the loader. Any suggestions?

It's not dead, it was used for the old loaders for DSM 6.

No, DSM is not that type of OS that you can install with an ISO. Installing the DSM on Baremetal or VM still you need to follow the same procedures to do. Redpill is the loader is the code that makes all this magic work so that we can install DSM on a non-synology hardware. TinyCore and ARPL to keep it simple they are software to make us (noob users) life easier without the need to understand how this magic works. Write a few commands or press a few buttons and you are done... I do non know if downloading the image of others will work. I suggest start reading the forum and you will find that it's easy. The booting message that you see on your screen is totally normal that is what is supposed to say. In order to continue to see the log after the booting if you are on a VM you need a Serial Interface (again you need to read). After seeing the "Booting" message you need to use Synology assistant. If everything works fine and your DSM picked up an IP you will see the DSM in the synology assistant and from there you can install the DSM (like a normal synology). The whole thing about picking different models it depends on your needs and the hardware you have. See the guide below.

Hi @Valiran34, This is how Unraid's QEMU works. The 1st virtual SATA controller is there no matter what you do. I do not know the specific reasons but a virtual SATA controller is present even if you do not have a drive. I am not talking about pass-through drives. The 2nd Virtual Controller I believe that you can remove. Just go into your Unraid VM XML and see if you can remove something that looks like this: <controller type='sata' index='1'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </controller> If the above exists if you can remove it the 2nd controller should disappear... The 1st controller which should look like this, as said you cannot remove it but what you can do is go into the ARPL configuration and add those SataPortMap and SataIdxMap like the sample below. <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> I saw this before in TinyCore Red Pill. I do not know how to describe it but I think the 1st controller (The one that you cannot remove from Unraid's QEMU XML) has 1 drive or has no drives and starts at 1st position and then your 2nd controller (Your passtrough card) has 6 drives and the 1st drive starts at 1st position. Its complicate, there is a lot of trial and error to make this work. I just gave you a general idea of what is going on... SataPortMap=16 DiskIdxMap=00 Also that wrong numbering will not affect DSM in any way. It's just a cosmetic issue... you can leave it as is if you want. It should not cause any issues.

It's always a good practice to keep a backup of your data. To answer your question, updating to a new version of Synology, by design it will/should not cause any issue with your data or your configuration. There is a chance that some packages might have a repair button beside of them but that is normal I guess.

This it's NOT possible, it's against the forum rules and the ideology of the loaders. The Serial Numbers generated by the loaders are random and DO NOT represent actual serial numbers DO NOT use them to register your Xpenology with Synology. If you want to use DDNS please use one of the custom providers. The only way to use Synology's DDNS you need to have a serial number from a decommissioned/real Synology product, but in order to work it needs to be the same model. You cannot use a serial number for a DS920+ on DS918+ for example.

Hi all, Yesterday I did some modifications to my network and I changed the IPs of my 2 synologies. Now when I log-in to the one that handles my Hyper Backups the tasks disappeared most probably because of the IP change. I went to /usr/syno/etc/synobackup.conf and edited the IPs but still it does not work. I cannot see my previous Hyper Backup tasks. Any other ideas how to recover them?

I have an AMD 5950X CPU... I cannot help on that part :(.

@Valiran34 I have Unraid also and I have been using the .img files since Jun's loader and I never had a problem with it.