IG-88

ist ja hier so eine art dsm forum also will ich die leute nicht zwanghaft überreden omv zu nehmen, ich spiele im kopf auch ständig ping pong ob das nicht für mich die bessere wahl wäre, ich habe mich beim umstieg 5.0->6.1 vergewissert das omv jeder zeit dsm ersetzen kann durchaus möglich das wenn dsm 6.2 nächstes jahr rauskommt es keinen gibt der einen bootloader und treiber bastelt, aber so lange es noch sicherheitsupdates für 6.1 gibt wird das nicht zum problem, ist dann also eher 2 jahre+ bis man abgeschnitten wäre aber man muss halt immer aufpassen was man bei dsm installiert und vorher im forum lesen ob man sich nicht den ast absägt auf dem man sitzt wenn man was einspielt, das problem hat man bei richtigen open source linux systemen wie omv eben nicht (oder sehr selten) und auch bei hardware ist man so wesentlich flexibler, da muss man sich fast keine gedanken machen ob es geht, ob AMD prozessoren laufen oder man hyper-v als unterlage nutzen kann tief? ich schwimm da eher nur kurz unter der oberfläche, im moment mache ich nur zusätzliche treiber, ich finde ja das könnte eigentlich jeder der schon mal selbst kernel compiliert hat (aber wer macht das heute noch selbst)

without the platform its not that usefull, if its a problem it might be only occur with ds3617xs image

as my log for the v3 say's no change to the tg3.ko, its the one jun provides as i checked the source of the tg3 module of the kernel (as i did before for the bnx2 and found out what firmware files are realy needed) there was i firmware file missing for tg3 so i added it (and docimented it in my changelog) compiling a new module for toigon/tg3 from external source is for later (maybe this weekend)

no wiki just this and some time to read here

beside the usual security issues there might be a good reason to use update 4 https://forum.synology.com/enu/viewtopic.php?t=135059 "Dear Synology users, An important update for the DiskStation Manager (DSM) 6.1 is released. We suggest users to update your DSM as soon as possible to ensure the integrity of your data. Download the update on your DSM: Control Panel > Update & Restore. An open source issue that’s prone to affect data integrity in rare situations has been identified. Although it only affects a handful of users, users are encouraged to upgrade to the latest DSM 6.1.3 update 4 and conduct RAID scrubbing to avoid running into this issue. The issue may occur only when the following conditions are all met: -The server is using RAID 5, RAID 6, RAID F1, or SHR with more than 3 disks. -The volume is created on EXT4 file system. -The server is running on DSM 6.0-8451 and above. If your DiskStation meets the criteria, please conduct the following steps: -Upgrade to DSM 6.1.3 update 4 (Download now) -Conduct RAID scrubbing. (Learn more) The issue was brought to our attention a few weeks ago when the NAS communities discussed the potential data integrity threat that may occur after a RAID 5 repair. In-house investigation revealed the issue stems from Linux feature known as skip_copy. This open source feature contains a slight design fault that may lead to potential data corruption after a RAID array is repaired from degrade mode. Synology team moved quickly to identify and reproduce the issue, which is resolved in the latest DSM 6.1.3 update. Synology is committed to high standards of data protection and safety. Keeping user information safe has always been our priority. In addition, as a vibrant supporter of Open Source, Synology has reported this issue to the Community. By calling to the attention of the mass community, we seek to join forces with influencers in the field in delivering continuous contribution on data integrity and data protection. Owners with the following models should upgrade their models to the DSM 6.1.3 update 4 as soon as possible: 17 series: RS18017xs+, RS4017xs+, RS3617xs+, RS3617xs, RS3617RPxs, DS3617xs, DS1817+, DS1817, DS1517+, DS1517 16 series: RS18016xs+, RS2416+, RS2416RP+, RS816, DS916+, DS716+II, DS716+, DS416play, DS416slim, DS416j, DS416 15 series: RS815+, RS815RP+, RS815, RC18015xs+, DS3615xs, DS2415+, DS2015xs, DS1815+, DS1515+, DS1515, DS715, DS415+, DS415play 14 series: RS3614xs+, RS3614xs, RS3614RPxs, RS2414+, RS2414RP+, RS814+, RS814RP+, RS814, RS214, DS414slim, DS414j, DS414 13 series: RS10613xs+, RS3413xs+, DS2413+, DS1813+, DS1513+, DS713+, DS413j, DS413 12 series: RS3412xs, RS3412RPxs, RS2212+, RS2212RP+, RS812+, RS812RP+, RS812, DS3612xs, DS1812+, DS1512+, DS712+, DS412+ 11 series: RS3411xs, RS3411RPxs, RS2211+, RS2211RP+, RS411, DS3611xs, DS2411+, DS1511+, DS411+II, DS411+, DS411slim, DS411j, DS411 Sincerely, Synology Development Team"

not realy, it will work without that, you can do it later, only when using wol it will be important also the numbering starts with 1 so the second lan card will be "set mac2="

i would suggest the method i did with my barematel system remove power cables from all disks (30 TB drives), remove usb stick take new usb stick and empty single disk, prepare usb stick as in howto (vid/pid) connect empty disk to first sata port of system, cennct usb stick and power on and try to install dsm 6.x (usualy 6.1.3 would be the first choice) if you are finished testig reconnect first sata cable with old disk, reconnect 30 TB drives to power and use old stick to power up - no harm done and you know is your hardware working with the new bootloader (+extra.lzma for drivers if needed) and new dsm 6.1.3

as there are sometimes problems with realtek gigabit pcie adapters I have created two additional versions of the v3 extra.lzma each containing only the r8168.ko or the r8169.ko (not both as in jun's original and the "normal" v3 extra.lzma) the rest ist identical to the normal v3 r8168 is the version compiled from the realtek provided souce (in theory the better choice?) http://s000.tinyupload.com/?file_id=22103599631967679390 r8169 is the version that comes with the kernel (3.10.102) http://s000.tinyupload.com/?file_id=93767429277409083729 realtek lists the folowing chips supported for the r8168.ko: RTL8111B RTL8168B RTL8111 RTL8168 RTL8111C RTL8111CP RTL8111D(L) RTL8168C RTL8111DP RTL8111E RTL8168E RTL8111F RTL8411 RTL8111G RTL8111GUS RTL8411B(N) RTL8118AS

http://www.technikaffe.de/forum/index.php?thread/644-alternative-für-surveillance-station-ip-cams/ na so schlecht ist dsm nun auch nicht

cant see anything usefull in the log anyhow i send you a pm with the link to a extra.lzma that contains a new r8152.ko from the actual source that realtek offers (0008-r8152.53-2.09.0.tar.bz2) let us know what happens with this maybe lsusb shows something usefull? btw. the adapter should be present at boot to show up in the dsm gui as network card

eigentlich schon neben den plogins gibts auch docker natürlich gibts die surveilance station nicht, die ist synology eigen aber da ist mit normalen mitteln wohl nur eine cam möglich alles weitere geht in richtung nicht legales hacking wenn man keine echte synology box hat google doch mal zu omv und ip cam außerdem kannst du ja mal schauen was es an plugins gibt und wo docker nötig ist grade wenn man bei dsm hardware einsetzt die nicht mit dem grade üblichen bootloader ootb läuft wird schwer oder es wird schwer auf die neue version zu kommen da es keinein passenden treiber gibt aber ich will dich nicht abhalten, ich habe auf meiner hardware ja auch dsm 6.1, habe aber immer omv in der hinterhand (getestet), das mdadm raid und das lvm volume lassen sich auf mit omv benutzen, usb stick raus und ssd mit omv rein und weiter gehts, die grundlegenden sachen wie nfs und smb laufen sofort

no, hyper-v needs a copletely new kernel with support for hyper-v not just some drivers/modules you can load (i already wrote about it here in the forum), i only do drivers(kernel modules for existing kernel provided with jun's boot image

no, synology did a lot of modifications (and backports) to this "older" kernel, if you put in a driver without the needed additional stuff weird things can happen, from simply crashig instantly to problems when just counting the disk in the system, the fact that the driver is loaded (without the hardware present in the test system) does'nt proof anything as long as i dont know i will expect the worst case and thats data loss if you want to volunteer as guinea pig i might compile a driver from a vanilla kernel.org source and if it loads on a dsm 6.1.3 vm (imho not likely) i will provide a extra.lzma to you as pm and you try what happens to real disks and data

i was thinking the same yesterday when looking into the source (and trying to disable something kind of blindly - as to expect just disabling some stuff sparked new problems) it might be possible to compile from a kernel.org source (3.10.102 afair) but as synology did lots of mods in the libata.h, libata-scsi.c and libata-core.c (and possibly more) but even IF ("... if? ifis good .." was it pain or panic?) the drivers will load, without knowing what synology needs/changed the outcome can be fatal to the data on the disks - i dont want that to try on my disks and dont want to hear the complaints of people loosing data while beeing guinea pigs i'm not that desperade for now, maybe someone will have a bettetr idea (its odd that the drivers complain about synology function in a synology system)

hi also das mit der ssd ist nicht so wie du denkst dsm legt auf jeder platte im system eine system und eine swap partition an (raid1 über x platten) und wie werden beim schreiben natürlich auf synchron gehaltern (und von welcher gelsen wird? keine afnung wie mdadm das festlegt) ich würde keinen slot für sowas verschwenden, bringt imho nichts, selbst eine ssd als lese puffer (für schreiben brauchts 2 wegen der sicherheit) bringt im heimischen umfeld wenig, das lohnt sich imho nur bei vielen usern also so richtigem server betrieb nicht das ich dir dsm ausreden will aber hast du mal open media vault (omv) asuprobiert? dsm ist eine appliance, immer schwierig da was "rumzubasteln" (obwohl der docker support vermultich vieles davon löst, wenn man ein docker packet hat), selbst sowas simples wir treiber werden da zum problem, omv ist ein normales linux und kann entsprechend einfach aktualisert werden, treiber sind da ganz normal wie bei jedem linux möglich und packete nachinstallieren und etwas compilieren falls nötig ist da auck kein krampf (plugins wie die spk pakete bei synology gibts da auch) 3617? da laufen einige plugins nicht weil die nur für ältere plattformen "konfiguriert" sind, da kommt man mit der 3615 besser (imho), updaten auf 3617 kan nman später immer nocht falls man muss/will VMM braucht eine gültige SN? wusste ich noch nicht, wo hast du das gelesen? (habs plugin nur installiert aber noch keine VM angelegt) "Surveillance Station", das braucht imho ab mehreren cameras extra lizenzen die nur mit gültiger sn laufen (wenn überhaupt), irgendwelche hacks des plugins klammere ich mal aus

possible, but not in the next x days, its kind of more importent to bring up more drivers for 3615 (the "unknown symbol syno_libata_index_get" thing is realy anoying) from my point of view the 3617 does not offer much more then the 3615 (only more then 8 cores possible? maybe some processort features that you will not recoginse in real life situations?) good to know i naild it this time (after checking the source what firmware is needed for bnx2 it should have) maybe jun will put the 2 missing files (bnx2-mips-06-6.2.3.fw, bnx2-mips-09-6.2.1b.fw) into his next version and the case is permanently closed

means its on my list of drivers that should work but dont because the resulting driver (from synology source) does not load with the message i wrote Unknown symbol syno_libata_index_get (err 0) its no use to just compile it from source, i already did it (and jun seems to have too, as he warned about it to happen) anyway good to see that somone used it (kind of) successfull, the forcedeth.ko worked as inteded and you had at least network support

hi, contiuing from here i have created a new v3 with the source of dsm 6.1.3 (15152) there are drivers that would be usefull but do not load after compiling (SATA/PATA), i marked them and commented the reason, maybe i will find time to look into this and try to find the point in the kernel source where the function is and why it might happen (i'm coder so i dont expext much to find out), if some else is able to find out comment it here all modules are tested with 6.1.3 (sucsesfull loaded with insmod) as before it contains all modules and firmware jun has used, so in theory what worked ootb with 1.02b should also with this extra.lzma v.3: http://s000.tinyupload.com/?file_id=71323561438971251178 Modules log net/ethernet Atheros L2 Fast Ethernet support atl2.ko ---temp remove - Broadcom 440x/47xx ethernet support b44.ko -> b44: Unknown symbol ssb_device_is_enabled (err 0) b44: Unknown symbol ssb_pcicore_dev_irqvecs_enable (err 0) b44: Unknown symbol ssb_bus_may_powerdown (err 0) b44: Unknown symbol ssb_pcihost_register (err 0) b44: Unknown symbol ssb_device_disable (err 0) b44: Unknown symbol ssb_device_enable (err 0) b44: Unknown symbol ssb_driver_unregister (err 0) b44: Unknown symbol __ssb_driver_register (err 0) b44: Unknown symbol ssb_bus_powerup (err 0) b44: Unknown symbol ssb_clockspeed (err 0) b44: Unknown symbol ssb_dma_translation (err 0) Intel(R) PRO/100+ support e100.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 Marvell MDIO interface support mvmdio.ko net/usb USB RTL8150 based ethernet device support rtl8150.ko Realtek RTL8152 Based USB 2.0 Ethernet Adapters r8152.ko Conexant CX82310 USB ethernet port cx82310_eth.ko ASIX AX88xxx Based USB 2.0 Ethernet Adapters asix.ko Prolific PL-2301/2302/25A1 based cables plusb.ko block Promise SATA SX8 support sx8.ko scsi Adaptec AACRAID Support aacraid.ko Adaptec AIC94xx SAS/SATA Support aic94xx.ko 3ware 9xxx SATA-RAID support 3w-9xxx.ko 3w-sas.ko HP Smart Array SAS hpsa.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 Marvell UMI driver mvumi.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 ---temp remove - Promise SATA TX2/TX4 support sata_promise.ko ---temp remove - Promise SATA SX4 support sata_sx4.ko -> Unknown symbol syno_libata_index_get (err 0) ---temp remove - JMicron PATA support pata_jmicron.ko ---temp remove - Marvell PATA support via legacy mode pata_marevell.ko ---temp remove - VIA PATA support pata_via.ko ---temp remove - CMD / Silicon Image 680 PATA support pata_sil680 ---temp remove - Intel PATA old PIIX support pata_oldpiix.ko ---temp remove - Intel SCH PATA support pata_sch.ko ---temp remove - Intel PATA MPIIX support pata_mpiix.ko ---temp remove - SERVERWORKS OSB4/CSB5/CSB6/HT1000 PATA support pata_serverworks.ko -> Unknown symbol syno_libata_index_get (err 0) firmware bnx2/bnx2-mips-06-6.2.3.fw bnx2/bnx2-mips-09-6.2.1b.fw e100/d101m_ucode.bin e100/d101s_ucode.bin e100/d102e_ucode.bin tigon/tg357766.bin Hide The newest version for testing is down below in the tread as its still work in progess and for testing (no "stable" version)"

the files are the ones that come with the kernel sources, jun only took the rv2p files for his package, there are only those 2 mips files with the kernel but i found bnx2 firmware deb packages containig more firmware files, i will put the "b" file within my next extra.lzma that will be out in a few hours the best way is to look in the source what *.fw files are mentioned, i did it for bnx2 and it looks like this #define FW_MIPS_FILE_06 "bnx2/bnx2-mips-06-6.2.3.fw" #define FW_RV2P_FILE_06 "bnx2/bnx2-rv2p-06-6.0.15.fw" #define FW_MIPS_FILE_09 "bnx2/bnx2-mips-09-6.2.1b.fw" #define FW_RV2P_FILE_09_Ax "bnx2/bnx2-rv2p-09ax-6.0.17.fw" #define FW_RV2P_FILE_09 "bnx2/bnx2-rv2p-09-6.0.17.fw" no mention of the "a" file, the "a" seems to be wrong with the 3.10.xxx kernel, a mistake from someone who placed the firmware files in the kernel, so i will delte the "a" file from the next extra.lzma

hi, the files in that extra.lza are from 2016, it will be definatly be one for dsm 6.0.x not for 6.1.x it's never gone work for 6.1 because of different kernels the process of repacking a extra.lzma is part of my howwto about compiling drivers/kernel modules but as your *,ko file is not compatile to 6.1 you dont have to try it i'm about to make a new extra.lzma for 6.1.3 with the new sources of 6.1.3 i can try to build the module too but if the modules do not work because of kernel modifications from synology there is nothing i can do about it (see the end section of the link obove, what jun wrote)

i can try this extra.lzma for 1.02, the nic might work with this as it contains the two firmware files (but without log its just guessing and trying)

You might boot with your 1.01 installation and check what modules are actually used/loaded for your hardware and then check if the modules are present in the extra.lzma you use for 1.02 in the case of nic its bnx2, i'n not shure but afair there where firmware files missing in jun's 1.02/a not sure if its still the case with 1.02b, afair I added some in my extra.lzma (driver extension for 1.02) edit: just checked i added bnx2-mips-09-6.2.1a.fw and bnx2-mips-06-6.2.1.fw and 1.02b does not have this files, the bnx2 seems to come with two different hardware versions and will need two kinds of firmware dedending on the chip/core on the nic? if you use a serial cable to read the log of the 1.02 booting you might see more clearly what happens

ja nein, aber die usb vid/pid muss auf jeden fall angepasst werden und zu dem stick passen den du verwendest

not shure what extralzma you talking about but the one i did contain this files appart from that the first is a usb gigabit adapter, the second is about usb in generel, not important for a normal pcie nic or pcie storagr driver thats strange at least the intel should work with both, the realtek can somtimes be a problem a there are two possible drivers, the on efrom the linux kernel and the one realtek provides (as source that can be compiled) you can try this one, the network should work but your storage won't (i guess, see below) aacraid.ko is needed i guess, if not in extra.lzma no go you can check what driver is used on the old system and have a look if that module is in the extra.lzma you are intent to use

it both possible, i prefer manual download first, the download somtimes takes more time then expected, also i prefer to have more control and i can check the checksum myself before updating