IG-88

i can "offer" a HP DC7600 MT, bios does not offer AHCI mode and just SATA cant be used with xpe 6.2 (i still use it for testing with a 2port jmicron sata controlles that is ahci compatible) in some other cases the bios options to switch to ahci mode can be a little cryptic (had two cases like this) there are some rare cases where you cant switch to ahci even when the chipset does support it with the new extra.lzma for 1.03b and DSM 6.2.2 it should work (again) as it uses the latest intel drivers 1.04b for 918+ will get the same drivers soon if nothing special pops up in the process

there is a new extra.lzma you can test with loader 1.03b and DSM 6.2.2 (latest update) https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/

das einzige das wir bei n54l einfällt ist wohl das es amd ist und man im bios c1e abschalten muss der nic sollte auch broadcom sein und wenn er mit 6.1 ging sollte es auch mit 6.2 gehen, ist der gleiche treiber (source) wenn du mit usb und einzelner platte testen kannst dann kannst du ja auch mal 1.03b direkt von jun und dsm 6.2.0 testen

2nd gen intel cpu -> kein 918+, get erst ab 4th gen netzwerk ist laut handbuch Intel 82579LM, schätze mal e1000e treiber sollte auf jeden fall mit mit 3615/17, loader 1.03b und der neuen extra.lzma von letzte woche gehen

you can try loader 1.03b as it comes from jun, dsm 6.2.0 and look for the esata connected disk, if its there ander this config then its my extra.lzma, if its not usable i this config either then is something different i remember taht there might be a bios update for microserver to set the esta into ahci mode look for other micriserver user in the section where people write about successfull updates, you might find hints like special mods or you can pm one or the other to ast about it

i will not do anything beside providing the modules, someone else will hat to do the tests to find out if and how its usable with kvm/proxmox there is a whole section for virtual environment, there should be people with enough experience to make it use and tell how load them without causing problems

according to specs and manual (schematic picture of the board) there are two different single port LAN's nor really one dual nic so one seems not to be supported by the driver package in use i guess with the newer extra.lzma i released last weekend you would see both ??? you can use 500G drives if you want, a raid1 will still be 500GB (minus 2+2GB from dsm and swap), if you have 4 and make it raid5 then 1,5TB will be usable with such old drives you should always use some raid option with redundancy, not basic, raid0 or jbod depending on what you have in mind but 4-8TB drives have good GB/money rate, you dont need any "boot disk" its just the loader on usb and dsm sysem on every disk you use in the system

like other kernel modules there are dependencies, you need to load some modules before the other usually modprobe will look for you (by using a file that is not present in dsm) when using insmod you will need to do it by your own in modules.dep (created where kernel compiled) there is for virtio_net: virtio_ring and virtio (same for virtio_scsi) when using google to find a load order for virtio its something like this insmod virtio.ko insmod virtio_ring.ko insmod virtio_blk.ko insmod virtio-rng.ko insmod virtio_console.ko insmod virtio_net.ko insmod scsi_transport_spi.ko insmod virtio_scsi.ko insmod virtio_balloon.ko insmod virtio_mmio.ko your extra.lzma only loads virtio_net and virtio_scsi, defiantly missing dependencies to two other drivers of virtio

rebuilding 918+ is in queue after christmas

es gab von 2-3 gen8 usern feedback das es läuft sata/ahci läuft ja automatisch, das ist bestandteil des synology kernels und der broadco netzwerk treiber der in der neuen extra.lzma für 6.2.2 drin ist ist der gleich wie vorher bei 6.2.0, nur halt für 6.2.2 compiliert, sehe nicht warum es da stabilitätsprobleme geben sollte

i guess as long as you don't create a data partition like a basic disk (like when wanting to install plugins you will be asked to create that) you can remove the disk later but why start with a single 500G disk now and add the 2nd later?

that does not depend in the board, synology has there special way about that https://xpenology.com/forum/topic/13342-nvme-cache-support/page/3/

the extra.lzma contains: virtio.ko, virtio_balloon.ko,virtio_blk.ko, virtio_console.ko, virtio_mmio.ko, virtio_net.ko, virtio_pci.ko, virtio_ring.ko, virtio_scsi.ko 9P seems also to be modules so i can add them try the attached modules for 3615 9p_3615.zip

more like, you dont know where it is - how did you intall without a proper vid/pid fro m then usb? you can read about that here https://xpenology.com/forum/topic/7973-tutorial-installmigrate-dsm-52-to-61x-juns-loader/ its also possible to mount the usb on the system where its used see this example mkdir -p /mnt/synoboot1 mkdir -p /mnt/synoboot2 echo 1 > /proc/sys/kernel/syno_install_flag mount /dev/synoboot1 /mnt/synoboot1 mount /dev/synoboot2 /mnt/synoboot2

da fehlen dann halt ein paar sicherheits updated wenn du updaten willst must auf jeden fall den 2. link beachten , da habe ich kurz das update 6.2.0 -> 6.2.2 beschrieben (der einfachste fall beim update auf 6.2.2) https://xpenology.com/forum/topic/7973-tutorial-installmigrate-dsm-52-to-61x-juns-loader/ https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/

see one reply above, 8111 should be usable with the new 3615/17 0.5 test extra.lzma ??? whats 9P for one we never got it working the last time and gave up on that driver, 2nd read my comment about compiled scsi/sas drivers for 6.2.2 i will not do anything further, if the kernel build in driver does not work and the latest from external source dont either i will not put more effort into this

the raid /dev/md2 seems to be ok, the fstab (mountig) looks good, no lvm when using a simple raid type is normal (i use raid6 and dont have lv), you see in your fstab that not lv is mounted its md2 that is mounted check your log files, maybe a problem with the file system (btrfs) and mountig fails because of this, try to user the check/repair for the filesystem and device /dev/md2

to be more precise, your system partition with dsm is always raid1 over all disks, it will "block" ~2GB system + 2GB for swap, that default on you might see something about a disk needing to be "inizialized" bofore you can make it a part of a data raid set, this data raid set can have different types of raid but the system/dsm partition is not to choose, its a fixed thing and bound to how dsm works

wenn du den onboard netzwerk adapter nutzt (broadcom) dann brauchst du für dieses update eine neue extra.lzma (da stecken die treiber drin) https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/

habe noch nie versucht unterschiedlich schnelle ports zu aggregieren, sag ich mal lieber nichts zu aber lacp mach nur sinn wenn merere rechner gleichzeitig zugreifen macht in der richtung oder wegen redundanz sinn lieber kiss prinzip wenn man man es nicht explizit braucht wird von 3615/17 ootb unterstützt, sollte gegen ich dachte eigentlich das mit dem spindown gilt immer für eine raid group, ssd weil sachen die ständig zugreifen evtl. hohen load haben und da hilft ssd und es ist leise (mein nas steht im wohnzimmer, da spielt das eine rolle) nein, system part. auf jeder disk ist nur dsm (2GB partition), plugins gehen immer auf auf "primare" volume, ohne volume (nur system installiert) kannst du kein plugin istallieren, wenn die plaugins dann auf einem volume liegen kann man eine extra raidgroup hinzufügen die dann unabhängig ist da dort keine plugins liegen und sol lange die plugins da nicht extra zugreifen sollten die auch runterfahren, das ist was ich aus den diskussionen hier mitgenommen habe, aber das nutze ich nicht ich habe ziemlich plain nas als datensilo und da fahren dis disks auch runter schau dir mal die "T" typen an, die sind deutlich weniger hungrig und wären meine erst wahl bei nas, 9100T wäre gur gewesen kann intel aber seint monaten nicht leifern, nur eine wesentlich teurere 9500T https://geizhals.de/?cat=cpu1151&xf=16690_T~820_1151+v2&sort=p#productlist also nach der letzen beschreibug (nicht wirklich games) dann eher esxi für die win10 kiste, mit ssd und ausreichend ram für esxi sollte das eigentlich gehen und es hat vorteile beim handling (snapshot, sicherung) aber dann musst du auch bei der nas hardware etwas mehr in ram und cpu investieren (6-8 core cpu?)

thats supported by the "normal" realtek r8168 driver i used r8168-8.047.04, pretty much the latest driver and your nic should work

hpsa is the driver from the 3.10.105, so its pretty old, likely not supporting your h240 i've tried to compile a recent driver from here https://sourceforge.net/projects/cciss/files/hpsa-3.0-tarballs/ i did not compile by default so i tricked it to expect redhat server 7.3 that seems to use kernel 3.10.x, it compiled that way try the attached driver and tell us about what happens when you load it in 6.2.2, 3615 edit: did you set the h240 into HBA mode? hpsa.ko

not much you could win by that, maybe a little more ntwork performace by using vmxnet as nic? but you could also extract that driver, copy it to your system load it with insmod and test it you would also need to snapshot the other disks as the loader copys the contend (driver) from the extra.lzma to your system partition (lib/modules/update)

as connect-3 qsfp worked i guess the older one will too but imho qsfp is overkill and with qsfp you can't add a cheap switch, these are only sfp+ yes https://www.synology.com/en-us/knowledgebase/DSM/help/DSM/AdminCenter/connection_network_linkaggr usually not with a single computer and a managed switch with lacp support is also a littel more expansive i'd suggest to use sfp+, already cheap, works reliable and can easily used with one computer for high speed just search the forum or internet about using lag/lacp for higher speed with one computer and you will see what i meant

https://xpenology.com/forum/topic/9392-general-faq/?tab=comments#comment-86731 usb is just the loader to boot and the system (dsm) is installed on every disk as raid1, so even when all disk but one fail you can still boot dsm