Leaderboard

Not for now! First I want to fix all issues are possible.

Dosen't look like you are able to reach github from your network. Should look like this: Check you firewall settings

This is not correct. There is a finite number of threads configured by kernel parameter for each platform. These are specifically highlighted in the table. The kernel thread limit is almost always larger than the number of physical threads on the DSM platform. In the case of the DS3622xs+ we can use 24 threads, even though the actual hardware only offers 12 threads. Any additional threads available with your hardware (beyond 24) will be ignored.

FYI, that additional SATA port only runs at 3Gb/s. It's a weird SATA controller, drivebays 1 and 2 run at 6Gb/s, 3, 4 and 5 (the optical disc drive, ODD) all run at 3Gb/s. If you want more/faster storage consider adding a PCIe NVMe or SATA adapter. There's a pretty good discussion of the options over here:

This tutorial is not the place to ask for or receive handholding advice on basic installs. Please post in the DSM Installation forum. (topic that was spiraling out of control was moved) https://xpenology.com/forum/topic/65137-all-manner-of-problems-installing-tcrp-need-help/#comment-349000

Also, important to note. Be aware that you are using a development version of the loader. Stable version stops at v0.8.0.5 https://github.com/pocopico/tinycore-redpill/tree/stable

Your hardware is to old to support the apollolake platform. You need a Haswell processor for that platform. Try building a DS3622xs+ (broadwellnk) which supports most hardware. You may need to edit your user_config.json manually

There are presently 2 mainstream loaders available: https://xpenology.com/forum/topic/53817-tinycore-redpill-loader-tcrp/ (TCRP) and https://xpenology.com/forum/topic/63486-automated-redpill-loader-arpl/ (ARPL) I believe both should be able to handle the upgrade to 7.1 at least. Before that I suggest reading this: https://xpenology.com/forum/topic/61634-dsm-7x-loaders-and-platforms/ and this: https://xpenology.com/forum/topic/62221-tutorial-installmigrate-to-dsm-7x-with-tinycore-redpill-tcrp-loader/ TCRP is testing and implementing a new functionality called 'withfriend' (TCRP Friend) which is creating problems with N54L. Read this: https://xpenology.com/forum/topic/62871-tinycore-redpill-loader-tcrp-development-release-09/?do=findComment&comment=347676 If you don't use it you should be fine. I don't have a N54L so can't comment much on the specific so I'll let other chime in.

I use ssd , because when i try to wake on lan , the baremetal turn on , but it does not boot from the usb

MPT3SAS should be auto detected.

Voici : https://www.amazon.fr/gp/product/B01JOLU7YY/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1 Ce qui est important c'est le chipset. Ce qui est cool avec syno, c'est qu'ils maintiennent hyper bien leur parc de drivers... si un chipset a été utilisé à une époque dans un syno, il va être présent dans les releases pendant des années.. je viens de voir que j'ai acheté cette carte en 2016 😛

Brauchst du nicht, sind für Updates direkt aus dem ARPL. Ist eigentlich nicht schwer. Habe dazu auch einige Video auf Youtube. Habe fix ein Video dazu gemacht: Es wandelt gerade noch um. Sollte aber in den nächsten 30 Minuten verfügbar sein.

The Synology expansion units have a completely different device connectivity structure that would be very difficult to emulate, while we generally are just adding SATA ports on top of those that are natively embedded in the platform. Bluntly, our way is simpler. If you really wanted to make the graphic, somehow grafting the images and logic in from one of the other units would probably be the easiest way. But it would get overwritten on each upgrade, and it is, again, purely cosmetic. For most of us, not really worth the cycles.

I did exactly the same CPU switch in my Gen8, there's absolutely no need to rebuild the system. It will "just work", just make sure you have some thermal paste for attaching the heatsink to the new CPU, and some decent cleaning fluid to the get the old thermal paste off the heatsink.

Честно говоря, не совсем понимаю Ваши затруднения: у PhotoStation есть стандартная папка ./volume1/photo, где хранятся все ОБЩИЕ фото, Moments по дефолту работает с папкой home/photo, где лежат фото пользователя и она определяется как МояБиблиотекаФото ( пишу по памяти, у меня англоязычный интерфейс), а после включения ОбщейБиблиотекиФото прекрасно берет и индексирует папку ./volume1/photo, совершенно не мешая при этом PhotoStation/

Большое отличие, из за которого основной мой сервер с фото альбомами остается на 6.х.х и фото стейшн, это управление доступом к альбомам. Я не хочу создавать системных учеток в DSM для внешнего доступа к альбомам. Считаю это большой дырой и риском для безопасности. Пусть лучше отдельные внутренние учетки фото стейшн остаются.

Взять ненужный диск и флешку, установить 7.1.1 и посмотреть, что получится, если понравиться, то потом мигрировать на рабочих дисках. Вот 2 загрузчика на выбор...

On the surface, I would agree with your proposed command to restore the array. However I have two comments and will reiterate strongly my prior advice: 1. The sdaf disk is missing altogether from mdadm and the sdaf1 and sdaf2 partitions should be present in the md0 and md1 arrays. This is an abnormal state. If you had just dropped the disk, there should be evidence of the md0 and md1 missing array members. 2. The SHR is really, really fragmented and is a liability even if it was healthy. You will be served by rebuilding the SHR from scratch with all of the physical disks present from the beginning. I would not include the virtual disks and build a second Disk Group if you need them. Given that your data is intact, you really MUST offload the data and get a backup. You have time to procure or borrow adequate storage. Go get it. Then delete and rebuild the SHR which resolves both problems. It would also be a safe opportunity to correct the incomplete DiskIdxMap/SataPortMap.

Several people are updating ARPL to this new release. I wanted to take the opportunity to give a message for users: Before upgrading to a new release or a new smallupdate, wait for testing information on the forum, as a new release can have a lot of changes and break your installation. This is the reason for not leaving automatic update by default.