Leaderboard

Vielen Dank an die hervorragende Arbeit von @AuxXxilium ! Ich habe einen gut erhaltenen Acer Aspire EasyStore H340 günstig gekauft um auf der Basis ein ASRock ITX Board einzubauen. Das original Mainboard läuft, nur ist WHS nicht mehr zeitgemäß und WHS hat sich auch recht zickig angestellt. Bevor man sich also damit rumärgert lieber Xpenology testen. Ich habe https://github.com/AuxXxilium/arc/releases/tag/23.6.34 arc-23.6.34.img.zip mit Rufus auf einen 32 GB Stick geschrieben. Den Debug Jumper gesteckt und mit F2 im BIOS den hinten angeschlossenen Stick an die erste Boot-Stelle geschubst. Dann Gebootet und die Warnung, dass nur 2GB Speicher vorhanden sind ignoriert und als RS3219+ konfiguriert. Dazu sind natürlich ein lokaler, VGA tauglicher Monitor und Tastatur erforderlich. Den Rest dann über das Web Interface erledigt. Da die MAC virtuell geändert wird, hatte das System allerdings eine neue DHCP IP zugewiesen bekommen. Nachdem die ganze Einrichtungs- und Updateprozedur problemlos durchgelaufen war, einen Speicherpool und User angelegt. Und was soll ich sagen, das Ding läuft! Der H340 ist mit der etwas betagten Hardware zwar keine Netzwerkrakete, aber es wird von Win10 sofort erkannt und funktioniert. Ich möchte es ohnehin nur als Backup Medium für mein produktives NAS nutzen und dazu reicht mir die Hardware vollkommen aus. Das System lässt sich auch sauber herunterfahren. Der automatische Xpenology Installer ist wirklich der Knaller! Damit ist es super einfach einen Acer Easystore H340 wieder zum Leben zu erwecken.

after 7.2 release they made 7.1 source available https://archive.synology.com/download/ToolChain/Synology NAS GPL Source/7.1.1-42962

Based on the package from @armanism , i wrote some scripts, for automate installation for DS3622xs+ with DSM7.2 bare metal on HP Microserver G8. hp-ams-ds3622xsp-4.4.302-Installer.zip

www.synology-forum.ru - сайт сегодня заработал, УРАААА

no if you activate that option you get a mpt2sas and a mpt3sas, usually just the unifies mpt3sas should be ok my extra.lzma for 918+ also comes with just the mpt3sas and works fine with all older sas2 contollers

"./rploader.sh ext bromolow-7.0.1-42218 add" to understand this it need to looked into kernel versions the above from @pocopico was for 918+, thats coming with kernel 4.4 and in that kernel the kernel-dev's merged mpt2sas and mpt3sas, so there is usually only mpt3sas (there is a option in the kernel for backward compatibility that will create a mpt2sas, but thats optional) config SCSI_MPT2SAS tristate "Legacy MPT2SAS config option" default n select SCSI_MPT3SAS depends on PCI && SCSI ---help--- Dummy config option for backwards compatiblity: configure the MPT3SAS driver instead. it the same kernel 4.4 for 6.2.4 and 7.0 (just a higher number because of fixes by kernel.org, more or less no new/better drivers) when it comes to 3615/17 it gets more complicated (as we need separate 6.2.4 and 7.0) 3615 is kernel 3.10 on 6.2.4 and 7.0 but 3617 its 3.10 on 6.2.4 and 4.4 on 7.0 also interesting to know is that synology adds newer mpt3sas drivers into 3617 (without providing the source) for 918+ that does not have native sas support its in addition, because of the changes synology made in the source the modules created from synologys kernel where not able to detect smart values or serial number but where stable when running with hdd power down feature where jun's modules for sas support (from non synology vanilla source?) where showing these (important) values but might loose data and destroy raids when used with hdd power down (i was able to reproduce that and documented it in the extra drivers for 6.2.3) not sure how @pocopico wants to handle that mpt2/mpt3 stuff, either differ between kernel 4.4 systems and only use mpt3 sas there and mpt2/mpt3 on 3.10 systems or make all systems have mpt2/mpt3 by compiling the optional mpt2 for kernel 4.4 synology does not use the mpt2 option with kernle 4.4, 3617 with kernel 3.10 has mpt2 (v20.00.00.00) and mpt3 (v22.00.02.00) and in 7.0 with kernel 4.4 there is only mpt3 (v22.00.02.00 - SAS 2.0,SAS 3.0 HBA & SAS3.5) - infos here where used from synologys binary kernel modules in the *pat files my suggestion would be keeping with the defaults and differ in the extension code between kernels and if mpt2 has to be used info in vanilla 4.4.180 kernel from mpt3 driver (mpt3sas_base.h), its the same in syno's kernel so they use a newer mpt3sas compared to the kernel 4.4.180 (syno's mpt3sas.ko mentions SAS 3.5, thats not in the original kernel driver) /* driver versioning info */ #define MPT3SAS_DRIVER_NAME "mpt3sas" #define MPT3SAS_AUTHOR "Avago Technologies <MPT-FusionLinux.pdl@avagotech.com>" #define MPT3SAS_DESCRIPTION "LSI MPT Fusion SAS 3.0 Device Driver" #define MPT3SAS_DRIVER_VERSION "09.102.00.00" #define MPT3SAS_MAJOR_VERSION 9 #define MPT3SAS_MINOR_VERSION 102 #define MPT3SAS_BUILD_VERSION 0 #define MPT3SAS_RELEASE_VERSION 00 #define MPT2SAS_DRIVER_NAME "mpt2sas" #define MPT2SAS_DESCRIPTION "LSI MPT Fusion SAS 2.0 Device Driver" #define MPT2SAS_DRIVER_VERSION "20.102.00.00" #define MPT2SAS_MAJOR_VERSION 20 #define MPT2SAS_MINOR_VERSION 102 #define MPT2SAS_BUILD_VERSION 0 #define MPT2SAS_RELEASE_VERSION 00 i guess i will do some experiments with 918+, newer mpt3sas drivers and scsi_transport_sas support, the 918+ vm for compiling 7.0 is already up and delivers *.ko files and as tinycore does drivers in general, there is more time for specials (like better sas support in 918+ or general nvidia gpu support for use in jellyfin, ebi and plex)

According to : https://linux-hardware.org/?id=pci:1000-0072-1000-30b0 for 918+ you should use MPT3SAS which has an alias for MPT2SAS. On kernel version 4.4+ the drivers for MPT2 and MPT3 have been merged into a single module. For kernels < 4.3 the sources provide MPT2 and MPT3 as a separate module and thats the main reason that MPT2SAS extension exists. The modules for 918+ have been compiled and are available on my GH repo. You can try to test once you have a DSM system installed.