IG-88

you might try a scsi controller and disk instead of sata

if you google for that chip and what kernel module it uses -> atl1e.ko when checking extra.lzma from jun 1.02 there is a atl1e.ko so it is supported

my board has a SE9172 and it does work ootb with jun 1.02a (ahci.ko from synology dsm) the SE9123 is also supported by the ahci.ko (http://cateee.net/lkddb/web-lkddb/ATA.html) and that is part of dsm itself so it should be detected whats " U36S"? 1. i expect you are using 6.1.1_15101 and the kernel sources provided (yet) are only 15047 (so there is a difference and some drivers compiled with 15047 source will not work) 2. do not replace the drivers already provided by synology did you see this about already compiled drivers and the compatibility problems with 6.1.1? https://xpenology.com/forum/topic/7318-driver-extension-for-jun-102a3615xs/ whats the hardware you are using, board, nic, controller (as much facts and as less believing as possible)

hallo, ich vermute mal die 2x3TB sind ein raid1 also rein theoretisch kann man die zwei platten aus dem xpenology system in der echten hardware allein reinstecken und eine neuinstalltion des systems duchführen (synology assistent), dann sollten die daten erhalten bleiben, man müsste aber nachher noch das raid1 in raid5 migrieren um die 2 zusätzlichen platten einzubinden - würde ich aber nicht machen, wenn du schon genug platten hast würde ich die 4 neuen in der ds416p ganz normal mit dem system bespielen und eine daten volume anlegen, danach kann man entweder die daten mit hyperbackup über romote datenkopie (rsync) über netzwerk rübersyncen oder man schließt eine der "alten" platten an die neue über esata oder usb an und kopiert sich die daten "lokal" rüber imho das einfachste wäre hyperbackup/rsync, das stößt man an und wartet einfach eine nacht, wenn irgndwas schief gaht hat man nichts verändert, man kann den prozess jederzeit wiederholen, kein risiko

hallo, wo gibts den den 1.02a2 für 3615xs? im 6.0.2 thread in dem der link zu jun's loadern steht gibts bei 1.02a2 nur 3617xs und 916plus https://xpenology.com/forum/viewtopic.php?f=2&t=20216 -> https://mega.nz/#F!BtFQ2DgC!JgomNP3X8V9EuwxL4TXbng

dsm legt auf jeder paltte eine 2,4GB parttion und eine 2GB partition an die dann jeweils in /dev/md0 (systempartition) und /dev/md1 (swapfs) mitglied (beides RAID1 über alle platten) werden, das sind deine fast 5GB, in der gui heißt das initialisieren

hallo, zum einen ist die 1.02a2 nur für die 3617xs (der link zeigt auf die 3615xs, für die ist 1.02a) und zum anderen brickt man sich in den meisten fällen mit der 6.1.1_15101 bei einem update seine box weil sie nach dem install nicht mehr hoch kommt entweder mann mach ein neu install mit der 6.1.1 oder man muss nach dem update mit einem live-linux hochfahren, mit mdadm die systempartition zusammensetzen (raid1 aus der ersten partition jeder platte) und dann den inhalt von /lib/modules/update nach /lib/modules kopieren

as it is a mdadm raid1 over all disks i would not take it for granted that they are the same up to the same sector/byte maybe if you copy just the files from one disk it will work as a backup but when restoring you will need to assemble the mdadm raid1 again an overwrite it as one device i would suggest to assemble the raid as a device and then make a sector copy of all the sectors in that device with dd (read sectors, write into a file), as it's only 2,4GB it will easyly fit to a usb stick, that way you recreate even partitions and boot code, pretty much the same as you can have a copy of /dev/sda, you just make a copy of /dev/md0 with that copy you will akso be able to delete the whole /dev/md0, recreate it with mdadm and then wite your copy back, the recreated /dev/md0 must have at least the same sector count (or more) to write it back there is not much you will haveto know or to write down, the size of your image file tells you exactly how many sectors/blocks your dive had, thats all you need to know for restoring

and maybe they never will - i'd expect docker is the replacement, it not locked to synology as the spk is i think polanskiman said the 1.02a2 is pretty much the same as 1.02a, just extended for 3617xs (such as time bomb fix), so why not using 1.02a for 3615xs? it a working solution

it's just additional drivers and it will stay that way for a forseeable future edit: i used the source for 15047 (no source for 15101), the log of a 3615xs with 6.1_15047 shows less unknown symbols so the modifications for 15101 are to blame for a least 6 of the 8 removed drivers with unknown symbols i did not think about that, just took the predefined synology kernel config asuming that what was not marked as module will not be in DSM, i will check that later this evening and make a new version edit: i removed the 4 drivers that where already part of dsm

i've compiled drivers for 6.1 lately with the links you provided it does'nt look too complicated to try it (at least for dsm 6.1, thats the enviroment i have setup, 6.0.2 uses a different kernel and is not on my agenda yet) if the dvb driver works, what software you want to use on synology with it?

just take a few minutes an use the forum search (just "hyper") there a planty hits and with google translate you will even be able to read foreign language like this viewtopic.php?f=13&t=33074&hilit=hyper or have a look into the howto section (preaty old but maybe still helpful?) viewtopic.php?f=15&t=551

did you read the howto for installing? you used the synology assistant to find the system in you local network, you tryed to use the broser to use the webgui? what bootloader, hardware? too little information

maybe open media vault (omv 3.x) is a alternative for you, dvb drivers will already be inside as it is an "full" version linux (dsm/xpenology is more of a appliance) and there are already plugins using dvb (i know there is a vdr plugin)

hallo, i'v created a extra.lzma that can replace the same file in jun 1.02a as descibed in DSM 6.0.2/6.1 howto, open synoboot.img with OSFMount (read/write) and replace the extra.lzma with the one i provide, dismount it and tranfer to usb stick (don' forget the usb vid/pid) - if you unfamiliar with that you should not use it, its experimantal and for people with at least some knowlege how xpenology is installed i added 2 firmwares for bxn2 that where missing in the original removed the r8169 driver from rc.modules and replaced it with r8168 driver (compiled from source realtek is providing on there homepage) - hopefully it will work better for some people then the r8169 (the r8169.ko is still there but will not be loaded) also added drivers for virtio (as somone requested) but i have not added them into the rc.modules so they are "inactive" if someone wants to play with that stuff, place the entrys in rc.modules and ... for all the drivers i added, the intel e100 was the only one i added firmware for, so there might be some firmware missing, if you know or find out be reading the log (!!!), let me know i will add that firmware it's also possible to unpack the extra.lzma (7zip on windows can unpack it, but not modify or repack it) and place the driver directly in the right directory and modify the rc.* files to load them in a running system (or load them with insmod manualy -> less dangerous as it does not influence boot process, good if you just want to find out that the driver is working for the hardware in question) please don't fill this posting by asking for drivers, for the moment it's the first test, new stuff might be added later (or someoen comes up with a better collection?) and it will be in an new thread i tested it with 1.02a and 3615xs edit: as reported no 1.02a2/3617xs, as i already have a 1.02a2/3617xs test enviroment it should be not to much effort to build one for that too edit2: in some modules there are unknown symbols after loading, some only happen with the newer 6.1.1_15101 that uses the same kernel number but synology has modifyed it so i differs from 6.1_15047, i removed them and marked them in the list as "---temp remove - " uploaded a new v2 version of the extra.lzma here the list of drivers i added: net/ethernet ---temp remove - Broadcom 440x/47xx ethernet support b44.ko ---temp remove - Intel(R) PRO/100+ support e100.ko Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support e1000e.ko Intel(R) 82576 Virtual Function Ethernet support igbvf.ko Intel(R) PRO/10GbE support ixgb.ko Intel(R) 82599 Virtual Function Ethernet support ixgbevf.ko nForce Ethernet support forcedeth.ko Realtek 8168 gigabit ethernet support r8168.ko Virtio network driver virtio_net.ko net/usb USB RTL8150 based ethernet device support rtl8150.ko ---temp remove - Realtek RTL8152 Based USB 2.0 Ethernet Adapters r8152.ko ---temp remove - ASIX AX88xxx Based USB 2.0 Ethernet Adapters asix.ko ---temp remove - Prolific PL-2301/2302/25A1 based cables plusb.ko block Promise SATA SX8 support sx8.ko Virtio block driver virtio_blk.ko scsi 3ware 9xxx SATA-RAID support 3w-9xxx.ko 3w-sas.ko Marvell 88SE64XX/88SE94XX SAS/SATA support mvsas.ko ARECA (ARC11xx/12xx/13xx/16xx) SATA/SAS RAID Host Adapter arcmsr.ko HighPoint RocketRAID 3xxx/4xxx Controller support hptiop.ko Intel(R) C600 Series Chipset SAS Controller isci.ko ata ---temp remove - NVIDIA SATA support sata_nv.ko ---temp remove - Silicon Image SATA support sata_sil.ko ---temp remove - VIA SATA support sata_via.ko virtio PCI driver for virtio devices virtio_pci.ko Virtio balloon driver virtio_balloon.ko Platform bus driver for memory mapped virtio devices virtio_mmio.ko virtio.ko virtio_ring.ko v2 http://s000.tinyupload.com/?file_id=07550851861898450690 PS: if you raid is shredded into peaces by a driver - don't blame me i've only compiled them (maybe somone at kernel.org will listen, the only thing i can do is to remove the driver from the package)

hallo, derzeit nicht zu empfehlen, zumindest 6.1, zum einen wird amd nicht unterstützt da probleme bekannt sind und es gibt auch leute die wieder zurück auf 6.0 mit der hardware sind https://xpenology.com/forum/viewtopic.php?f=2&t=20216&p=101717&hilit=7GB#p101707 wenn wäre 6.0.2 + update xx möglich aber nicht 6.0.3 keine ahnung, ich habe meine 5.0 komplett verworfen da es ohnehin zu viele unterschiede gibt und ich mein daten volume ohnehin in in btrfs statt ext4 haben wollte kannst es ja ohne zwischenschritt auf 6.0.2 versuchen, der syno assistent zeigt dir eigentlich an ob es ein update wird oder nicht 6.0 - jun 1.01 6.1 - jun 1.02a/a2 6.0.2 und 6.1 gibts hier viewtopic.php?f=2&t=22100 viewtopic.php?f=2&t=20216

realtek rtl8111 are not the best choice https://unixblogger.com/2011/10/18/the-pain-of-an-realtek-rtl8111rtl8168-ethernet-card/ if you have the option (other nic at hand and free slot) try to disable the onboard realtek and use another card for testing (most people prefer intel, prooven to work good and reliable) i expect the rtl8169.ko driver is used when dsm is running, you might try to change that so the rtl8168.ko driver is used, try to find soemthing here in the forum (search function) on how to do that (i think you are not the first)

if you boot from a live linux, assemble the system partition with mdadm (first partition on every drive) and format that partition, there will be no dsm left (data are in another partition that is usualy the 3rd partiton on every drive - so dont touch those) and you can reinstall dsm (loosing all settings and plugins - but that might be easyly recreated), it will ask for a new root/admin password as it is a completely new install the data (volume1) will be tound again when the new install of dsm comes up (as it would be a system update from a earlier system of dsm) there are other methodes, maybe someone else comes up with a better/easyer plan, that one is to succeed in a forseen time if you can handle the line linux and still have acces to the old dsm 4.x install files if you try to install a newer dsm (5 or 6) you might hit new problems with unsopported hardware, so try to stick with what you know is working how to hande the live linux and mdadm: https://xpenology.com/forum/viewtopic.php?f=2&t=30805

whats the hardware (systemboard, controller, nic)?

as you have now 16 LSI ports you may simply swith off all onbord sata ports and just let the last 2 or 4 lsi ports be esata 0000 0000 0000 1111 1111 1111 = internal 0000 0000 1111 0000 0000 0000 = esata 1111 1111 0000 0000 0000 0000 = usb satamax=12 4 ports left out for esata (one multilane connector on the lsi card) as there are cable "multilane to 4xsata" you might be able to use 2 as internal ports and connect 2 to a slot bracket to make them esata https://www.startech.com/eu/Cables/Drive/SATA/2-Port-SATA-to-eSATA-Plate-Adapter-Female-to-Male~ESATAPLT2M its a lot of waste but it will surely work - depends on how you plan to extend your box (someone in the 6.0.2 thead did it this way as he was not willing to invest more time to find out the hard way how to get all sata ports to work - just beat it with the force of hardware and money to spare time an concentrate on the goal to get the system working with the disks at hand)

virtio drivers are part of libvirt? as there is a (beta) virtualization package vom synology with libvirt, qemu(KVM) i'd expect that to part of dsm or that package? https://xpenology.com/forum/viewtopic.php?f=2&t=32744

not excatly what i thougt, the spk format is sorted into platforms (processor/chipset) with cetain name the spk istself can be opend like a zip file and inside is a file INFO there you find things like arch="broadwell" or arch="bromolow broadwell" or arch="x86 cedarview avoton bromolow evansport" it ssems that arch="x86_64" is universal? at least synology packages contain that if your packeage in question does not contain the "bromolow" it will not show up on 3617xs if you look here you will see the names of the plattfoems supported by dsm 6.1 https://sourceforge.net/projects/dsgpl/ ... 047branch/ so if a new platfoem is introduced and the package is not maintained it might happen that the new device does not offer the package, even if it would run on that plattform (hardware/processor), it will depend on how the package was created - at least as i understand it it might work to manualy modify the package by writing the plattform into the INFO file, but i expect it will break the signirure of the file und i dont konw how such a spk file will be handled if installed be the manual install button in package center (never tryed that) so as the 3615xs is longer around, it might be the better choice (at the moment) wenn it comes to packages

well i took you word for granted that the mobo has 6 ports, if there are 8 (6+2) and they are found before the lsi it will look different in the mapping the bits/ports in the mapping have to tke all "visible" sata ports into account so if its 6+2+8 the correct mapping will look like this 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 1100 0000 = esataportcfg 0000 0000 0000 0000 0000 0000 0011 1111 0000 0000 0000 0000 = usbportcfg 0000 0000 0000 0000 0000 0000 0000 0000 1111 1111 0011 1111 = internalportcfg esataportcfg="0xc0" usbportcfg="0x‭3f0000‬" internalportcfg="0x‭ff3f" maxdisks="14"

https://www.synology.com/en-global/know ... d_RAID_SHR https://www.synology.com/en-global/supp ... calculator

the date is the date inside the synology (bios date), check if that is correct if he still has valid user accounts, maybe one with admin rights? then you can try to login with this do a sudo -i and you are root