IG-88

thats not bios, they changed the kernel/drivers to do so same reason why a standard sata multiplier does not work on dsm like it does on a normal linux, code changes by synology, they activate that only if they detect there own multiplier with special id/bios in it https://www.synology.com/en-global/knowledgebase/DSM/tutorial/Storage/Does_the_eSATA_port_of_Synology_products_support_eSATA_disk_enclosures_with_port_multipliers a few years ago someone created a kernel patch to (re-?) enable the multiplier funtionality, cant find it atm

just follow the thread as i wrote, i explained it there i dont know if synology has anything in store for system not matching, i think its just a warning the the system has been tmapered with (in worst case a virus infection - unlikely in your case) but they might also consider it a "unrelated copy" of dsm and ... who knows what they do in future updates if they detect a "unlicenced" copy of dsm, they still try to shake off the freeloaders by protections and serial number checks

as there are chips in the synology boxes like sil3627 and this are sata portmultipliers and there are also eSATA port connections to the outside, i don't see how infiniband comes into play

hi, in some way you replaced the original kenrel modules from synology with the files from the bootloader read this and follow the thread, it was solved

soweit ich mich erinnere bracht das plugin um vm's laufen zu lassen btrfs (VMM - Virtual Machine Manager) ansonsten lies einfach was synology sagt warum das ihr neuer standard ist https://www.synology.com/de-de/dsm/Btrfs

hi, da sich hier keiner äußert geb ich mal zum besten was ich denke/meine ich habe meine 5.0 komplett verworfen da eine dinge in 6.1 btrfs als filesystem benötigen (der neue standard bei synology) und es dafür (ext4->btrfs) keinen update pfad gibt also backup aller daten und komplette neuinstallation (alles auf den disks wird gekillt), da spielt es dann keine rolle was vorher drauf war wen du bei ect4 bleiben willst und ein upgrade machen willst kannst du auch 5.0->6.1 versuchen, wenn du mit einem usb stick mit jun 1.02b (für dsm 6.1.x) bootest wird dir der synology assistent sagen ob du migrieren kannst, wenn icht dann brichst du halt ab ein update von 5.0 auf 5.2 wäre im grunde nicht so anders wie bei 6.x nur das du einen bootlaoder für 5.2 (usb stick) brauchst und dir das passende *.pat file bei synology runterladen musst, also wieder neuen usb stick rein und schauen was der synology assitent sagt was passiren kann ist das der neue bootloader keinen treiber für deine hardware (netzwerkkarte und/oder storage controller) hat und die kiste entweder nicht im netzwerk findet oder keine migrierbaren disks gefunden werden aber da der nur hochfährt und meldungen macht kannst du jeder zeit wieder den alten usb stick reinstecken und mit dem unveränderten system wieder hochfahren, erst wenn du anfängst eine neue dsm version zu installieren wird was verändert

hi, to address the problem with the sata and pata modules i have compiled this modules from a vanilla 3.10.102 kernel, without the hardware present the modules load on a dsm 6.1.3 vm but that does'nt mean they will work at all, with the hardware present they might fail, oops or worse modules in question: sata_nv.ko sata_sil.ko sata_via.ko sata_promise.ko sata_sx4.ko pata_amd.ko pata_jmicron.ko pata_marevell.ko pata_via.ko pata_sil680 pata_oldpiix.ko pata_sch.ko pata_mpiix.ko pata_serverworks.ko any volunteers (guinea pig's!!!) with test hardware without data on disk(s) (or willing to do a test with additional usb stick and empty disk on a running system)? i would pm you a link with a extra.lzma containing the modules

hi, downgrades sind nur möglich wenn man eine bestimmte datei vorher anpasst upgrade auf neues major release wie 5.2->6.x braucht neuen bootloader und man muss sehen ob die verwendete hardware unterstützt wird ist also einfacher das pat file in frage bei sysnolog ynoch mal runterzuladen falls du gleich auf 6.0/6.1 willst solltest du im engl. bereich den gepinnten tread lesen, da hat ploanskiman alles gut zusammengefasst außerdem solltest du alle platten abklemmen und den bisherigewn usb zur seite legen und zum testen einen neuen usb mit dem passenden jun loader benudelen und mit einer leeren platte testen (leer meine keine partitionen drauf) wenn das dann im netzwerk gefunden wird (=netzwerkkarte wird unterstützt)und die platte sich mit dsm bespielen lässt (= controller wird unterstützt) kannst du mit dem usb stick und deinen echten platte noch mal anlauf nehmen oder du schreibst mal was du für hardware hast, dann versuch ich mal eine vorhersage obs mit 6.1 gehen würde aber am einfachsten wäre es wohl die bisherige version noch mal zu installieren

i just had a look what this card is HighPoint Rocket 750 40-Channel SATA 6Gbps PCI-Express 2.0 x 8 HBA 160-400TB is a lot of space wow, big plans?

as i'm still extending the extra.lzma i compiled and added it i pm'd you the link to the test extra.lzma with the r750.ko

was genau meinst du mit es klappt nicht, ist es so wie am anfang oder bootet es erst garnicht mehr in die weboberfläche? prizipiell kann man die gleiche dsm version drüber installieren die man hatte ohne das daten verloren gehen, das dsm betriessystem leigt auf einer extra partition die dann überschrieben wird, da die plugins und andere daten woanders liegen sollte die erhalten bleiben

me either, my intension was to save time i'm still thinking why its unstable (sbv300 seemed to have the same experiace with faster hardware) such simple algorithms should be more digital like yes or no, not maybe

would be interesting to know how a original 3615/3617 box handles the two optional 12slot extensions they wil be attached by esata and multiplexer but the config has max.12 drives in it (maybe a process will change that if a external unit is detected?) and as the design is for 36 drives already as the name "36xx" implies they must be capale of more then 24 drives

as it was your question, its up to you the result seems mixed, but does not sound promising, crashes when doing a raid extensions are never a good thing but i guess its kind of academic, in 99.99% of the xpenology cases max 24 disks does the job bigger systems are realy noisy and consume a lot of power and most of the privat use cases go for size and not for speed (more disks, more speed), with affordable 8 and 10 TB disks tere is only a slim possebility that you need more then 24 disks btw. if someone realy wants to build a system with a lot of disks in one case (like 45 to 60), have a look at backblaze's blog, nice technical details, open hardware design (storage ppd's) and fun to read, also intresting to see the changes of the hardware design (like multiplexer vs. full speed ports)

@SteinerKD you do it more complicated then i would have done it i would have changed the config once to support 48 disks (as long as there are not more then 26 disks plugged in nothing strange will happen) and would create and destroy simple raid units (basic, raid 0) for every try (24, 26, 27, 36, 48), expanding might take to long, when the problem is about sda-sdz then the raid type does'nt matter, if 27 works then 48 should work too

present in my source, 13885 bytes long Synology NAS GPL Source - 15152branch - bromolow-source.txz also present in this, can't see how that can't be in your file and extracted souce usimg modinfo <module>.ko i get 3.10.77 kernel as to expect with mine i get the right version 3.10.102 9) so I just copied .ko from chroot environment to non chroot environment with root privileges as i already had problems with loading (-> driver extension log/status test file) i do that befor putting them in the extra.lzma I cant use 3617 variant since there arent debian-chroot and/or python extra packages on this architecture i was thinking about using the ,config for x86_64 instead of bromolow so the resulting modules might work an all three images (3615/3617/916+) that one of the things i wanted to test next i will pm you the virtio files i created from my source of 15152 for 3615

well if anyone realy wants to know, it should be possible to do this in a vm with thin disks does'nt take much resources, just 1-2h

well he just defined it in the config and only had one drive in maybe he will be suprised if he try's to add the physical drives he had in store lets see his next vidoe ...

yes, the extra.lzma contain the additional driver that dsm/synology does not provide don't mix loaders for 6.1 (jun 1.02) with extra.lzma from 6.0 (jun 1.01/quicknick2.2) or vice versa, it will not work you might consider buying something a little bit more recent (ahci sata), like intel J1800 based or newer (2-6 sata), as they are cheap, much easier to get to work with xpenology

you will have to try by yourself, i dont use i notebook for dsm

i was cut&paste'ing, that would be kernel headers, but we dont need them, we use the kernel source fom synology i dont catch this, i download the kernel sources synology provieds and use them to build the kernel modules, on my system is no 3.10.77 source, so it can't buid for this are you doing this an a dsm 6.0 installation?i did it on 6.1 and installed she chroot in this enviroment that would indicate you are using 6.1 as base, so were does the 3.10.77 come from? dis you install any other source? in 15152? as the source is provided by synology i can't do anything about it maybe i never recognised as i only build modules (not the whole kernel)? i will check the vm i use for compiling the modules as i did it only once i can't give be shure, i'm still using this vm (updates to 6.1.3 and copyed new source in new test directory)

ich7 would be "ata_piix .ko" and promise fasttrack tx4310 would be "sata_promise.ko" both atm not availible for dsm 6.1 with 6.0 it might be possible polanskimans extra.lzma contains the sata_promise.ko

2. like this? https://superuser.com/questions/1057868/shutdown-a-linux-computer-depending-on-the-battery-level

from the descrition it looks like its still (stuck?) in raid1 creation (only 2 disks, no access to shares) having a look with the cammand i posted does'nt hurt, its just showing the status still unusual that just makeing a copy of the basic disk (basic->raid1) takes that long do you still see disk acrivity?

when in storage manager / hdd/ssd you see disk1, disk2, ... on the right there is a arrow showing down to indicate it can be opend to see more, if opend on normal systems you will see the disks name like Hitachi HDS6C5050ALS650, the serial number of the disk, ... with the serial number you know what disk to change, without it can be somtimes hard to figure out what disk is faulty (in non sysnology hardware there is no "slot" number or the conting of the slots can be different when changing dsm version like 5.2 -> 6.1)