Leaderboard

Hi all, A while ago I've started experimenting with a solution that would not require docker and/or a system running linux, but just a simple image that you can boot on your physical/virtual system and create the loader from there. I started with the plain disk image of 200MB size and tried to fit all in this image. As always first partition of the image is the synoboot1, second synoboot2 and third one (synoboot3) is tinycore. Tinycore is a simple linux distribution that can boot to a GUI so you can start creating the loader. Most network modules are included so you can verify also the extensions required on your system. A script will take care most of the actions that you would manually perform and just copy the loader contents to the 1st and 2nd partition. The loader is created from a pre-compiled redpill extension (should work) or you can compile it yourself (still testing). You can bring over and use the rp-helper configuration files so you dont have to do that again. To connect using ssh you will need first to reset the tc user password by typing # passwd tc The image can be found here: https://github.com/pocopico/tinycore-redpill Before starting the loader creation just run # ./rploader.sh update now and answer y I would appreciate any findings to improve the image.

После установки Synology-TorrSrver MatriX.111 замечены баги, сервер самовыгружается, даже после ручной загрузки, откатился на 110 версию

Core i7-2600 (Sandy Bridge) with lowest possible multiplicator in order to save energy and minimize cooler noises.

I haven't looked at the tool. I assume it allows you to create the loader on USB and then it downloads the .pat file from Synology for you to use when you run the install. In that case, you can download the .pat file you have linked to your PC and use that instead when prompted during the install process.

You need to install 6.2.3-25426 which is the main release. The others are minor updates. Before 6.2.4 was released, then control panel would have offered the minor updates after you installed the main release. I'm not sure whether we can get that done now (i.e it may only offer 6.2.4) but we can worry about that later. It won't change any of the functionality.

Yes. To be clear, you need to keep the USB stick with the loader inserted as well.

Yes. 6.1.7 and 6.2.3 can use the internal card. The releases in between needed an additional card. Oh and while I think about it. When you get the system up and running go to control panel and turn automatic updates off. 6.2.4 does NOT work with the current loader.

You want 6.2.3. v1.03b ds3615xs. Turn off c1e in the bios of the n36l

Hi pocopico, hi devs, thanks a lot for your outstanding work! With your developments, I'm finally able to run bromolow-7.0.1-42218 successfully on my bare-metal machine which is an ASUS P8H67-I Deluxe utilizing six disks on the onboard Intel controller and an additional ASMedia controller. Really amazing and thanks a lot again! BR, Elix

./rploader.sh identifyusb now does not output anything...but anyway I changed the user_config manually. If I set the disks to Virtio they are not detected only if I change the controller to SATA. I remember ThorGroup said it is better to set them to Virtio because they perform better. Anyway, after deleting everything and setting the USB as I have on my production Synology and the Disks controller to SATA everything worked. Great job @pocopico if you need to test something let us know.

in fact you can't really have read much, because a few pages earlier there was an approach / guide on how to create the DS3617xs loader! and yes it works...

I will send you here: For N54L read N36L

maybe they have been put off by the frustration of replying to dozens and dozens of mindless requests from posters requesting step by step install instructions, can they have a full install image regardless of being told dozens of time its includes propriety Synology code, how to get face recogonition working or a number of other out of place posts which dont add anything to the project moving forward in a developer section when THOR Group and others have said all along it isnt even in Beta stage yet. The same fate will fall to anyone else taking this on unless the Developer topic is kept right on track and we, including myself, who dont have the coding or analytiucal skills have the patience to leave it to the experts to hopefully bring it to a satisfactory conclusion.

beside what @pocopico wrote sata dom's simply use better parts and are more expansive, resulting in a better lifespan (as designed) that depends on the soc that is used and the flash chips, a better soc can handle more iops and even with the same flash will be better handling io loads also here, as designed no, not really, its usually the cheap flash chips in usb thumb drives that die early, especially when the controller does not have the ability of wear leveling as the usb loader is rarely written to (just on dsm updates) its no big deal to have lower grade hardware for booting and its also easy to replace - if you know how to deal with it you dont even need a backup of the usb thingy (i don't) the following goes for jun's loader but will be similar for redpil its just the grub.cfg where you enter usb vid/pid, mac and maybe sn (easy to have a copy of it, the usb vid/pid part might be in need of change when changing the usb device) and if you used a special exra.lzma (for drivers) you need to have that too and the often missed and not understood part is the kernel of the installed dsm version (zImage, rd.gz) that can be extracted from the *.pat file used for the last update, its not that difficult to reproduce the usb drive if needed from scratch under normal circumstances the usb flash drives are mostly used for reading and thats no problem in case of reliability, i came across one ore two cases here where lifespan was a problem but that was across the brands and more likely a issue of psu or voltage/current of the board i would be more concerned about the sata hdd's, cabling/backplane, psu and controller - read here a little and there are so much more cases about hdd's then usb flsh drive reliability also a not working boot stick does not have any effect on your stored data, you could even boot with open media vault and get insant access to you files over network (if you prepare a bootable media with it), its also possible to boot up a live/recovery linux and mount the data volume manually (-> howto section, that way you can also find out what dsm version was installed, just in case you lost track and need to recreate a broken usb) the reasons might be more like compatibility (sata boot for a running system instead of usb for just installing), speed (sata = 6G for a long time reliable), i guess you could also have slc usb drives if you want to (and be willing to order 10k+) and have more reliable usb flash drives the usb boot is just a tiny part of the system and not just by importance for the stored data also to the amount of data, just 30-40MB that is read from usb, the dsm sytem is stored in the 1st partion(s) of the disks, more or less the boot kernle, some drivers/config files and the original dsm kernel, thats it even if you speed up the usb part by 10 times its pointless compared with what you can gain when "forcing" ssd speed on the dsm system partition (in the end only one partition of the raid1 is used when starting the system and when its ssd the you might see some gain in boot speed

SATA DOM's durability (slc/mlc & SoC design) & transfer speed is much better than USB flash drive (its tiny embedded controller die earlier) gives me a peace of mind. Most common capacity varies from 1GB to 16GB while capacity is not-fully utilize, still seems acceptable to me. There is a reason why SuperMicro & other server mb usually comes with SATA DOM /Server DOM connector (even though USB is available) @urundai