Leaderboard

Если бы не работало, то я бы не советовал. Проверено на себе)

Great news! Didn't know about this power button package; thank you. My J1900 is running just fine for about five days. Now I see the difference between a virtual and a barebone installation. It is running much smoother now. With surveillance station package and 5 IP camera's it's using between 4 - 8 % of CPU power. I am monitoring it with Grafana, telegraf and Influxdb.

Как вариант контроллера: https://www.ebay.com/itm/Dell-PERC-H200-6Gb-PCI-e-SAS-SATA-8-Port-Raid-Controller-9210-9211-8i-047MCV/172981732523?ssPageName=STRK%3AMEBIDX%3AIT&_trksid=p2060353.m1438.l2649 Легко перешивается в lsi 9211-8i (IT mode).

Немного поковырял загрузчик 1.04b для 918+. Отключил в модулях i915 и все прошивки к нему. Железный трнаскодинг ожидаемо не появился, но зато заработало нормально выключение/перезагрузка из ДСМ) При этом я так понимаю родной(тот что в PAT) модуль i915 пытается загрузится, но не может: Если использовать не модифицированный загрузчик, то i915 грузится, но с ошибкой вылетает прошивка bxt_dmc_ver1_07.bin. При отключении в загрузчике только прошивок, но с оставлением модифицированного i915 (тот что в загрузчике), система не поднялась. Будет время ещё поковыряюсь )

Т.е. зачем хрень на Z370 у Вас вопросов нет, а именно использование нормального контроллера - вопрос?

@manples Finally got it working by using an intel nc360t network card, disabling the internal nic. Loader 1.3b, ds3615. Should also work on ds3617. This card is cheap on eBay, so get one and update your N54L...

The idea behind the recovery-method: You cant downgrade to 6.2 easily by just reinstalling the bootloader on the sdcard/usbstick. On every boot, the installed DSM 6.2.1 will update the bootloader for you To force a downgrade without another spare hdd, you have to change your Synology Model so the DSM installer will force a "clean install" instead of updating the bootloader Because of the reasons above you have to switch the bootloader von 3615 to 3617 or vice versa depending of what you have installed currently. So if you have DS3615 you have to flash the sdcard/usbstick with DS3617 so youll get into the recovery mode on the next boot. Leave all hdds as they are Take out the sdcard/usbstick on which the bootloader is installed and flash DS3617 from jun onto it Insert sdcard/usbstick and boot Youll get the "install dsm" screen which can be found with the synology assistent (just like you did when you first installed xpenology) Install the DSM 6.2 for DS3617 by "manual install" https://archive.synology.com/download/DSM/release/6.2/23739/DSM_DS3617xs_23739.pat Optional: If you want to go back to DS3615 Repeat steps above but flash DS3615 bootloader onto scdard/usbstick Install DSM 6.2 for DS3615 https://archive.synology.com/download/DSM/release/6.2/23739/DSM_DS3615xs_23739.pat I guess thats detailed enough

Change DiskIdxMap=0C to DiskIdxMap=0C00 in grub.cfg inside sata_args. That's the starting disk number for each controller, in hex pairs. The 0C is an offset of 12, which is what pushes the boot drive to Disk 13 (so doesn't show up in the GUI with default internalportcfg in synoinfo.conf). Adding the 00 means the second controller will start numbering at 0 instead of default (so /dev/sda). I verified it here real quick--this was Disk 2 before the change: