IG-88

it need to match you loader/dsm image type, if you installed loader 1.02b for 3615 the its the extra.lzma for 3615 its in the tutorial, the part with osf mount 4 - Now launch OSFMount. Select Mount New, then select the image file you downloaded earlier (i.e. .img extension file) to open. Now select partition 0 (the one that is 15 MB). Click Ok. Then at the bottom of the window make sure to un-tick the "Read only drive". Click Ok. The partition should now be mounted in file explorer. At this point you can navigate to the /grub directory and edit the grub.cfg file. If you need to replace the extra.lzma ramdisk with the custom ramdisk provided above then you will also need to mount partition 1 (the one that is 30 MB). as alternative you can plug you usb into a windows pc and you should see the partition with the extra.lzma (sadly the 1st partition with grub.cfg is not shown in newer win10 versions, just asks to format it instead - what you should ignore)

i'm not sure the dsm 6.1 for 3615/17 is supporting usb 3.0, there is no xhci-hcd.ko present in dsm (like it is in 918+ image) but the dsm 6.2 for 3615 has it

you can try the extra.lzma the tutorial mentions

definitely not with the 918+ image that needs a 4th gen intel but it should work with 3615/17, HP can a little of a problem some times and you might need a different loader made for mbr https://xpenology.com/forum/forum/98-member-tweaked-loaders/

für 918+ habe ich grade ein treiberpaket erstellt das mit 6.2.2 geht, da ist auch der tg3 treiber mit dabei den dein interner nic bräuchte da deine cpu aber nur 3rd gen ist kannst du das 918+ aber nicht benutzen für 3615/17 schaue ich mir das zur zeit an

/dev/md2 is just 8 x 2TB raid5, usable space 14TB and what about /dev/md3 and /dev/md4? you volume1 was more then this 14TB

you could try out the new extra.lzma's it contains latest e1000e driver 3.6.0 so you i219v should work with this

juns 1.03b had 8.045.08, i do have that as source too but plan to use 8.047.01 i also have a realtek for testing here so i will check on this one (its also very common)

ata_piix is still in the same state as documented in the old 918+ thread i guess it will present in 3615/17 extra.lzma (work in progress) […] Either confirmed by users that it is not working OR not supported for DSM 6.2 (kernel 4.4.59) OR does not load at all. Driver was compiled/tested but removed - if someone finds a way to get it working in some way, tell us here and it will be added whats your nic, i guess it should work with the new 6.2.2 capable extra.lzma if it did in the old one

see what you get when you type "dmesg" on the console, there should be something about the driver, like version number when it loads or error message when not loaded for a reason you can check in /usr/lib/modules/update/e1000e.ko 256704 bytes and file date 2019-10-02 2:32 that should be there if it would have worked as expected i used driver source e1000e 3.6.0 and in in hw.h there is your hardware's id #define E1000_DEV_ID_PCH_SPT_I219_V5 0x15D6 #define E1000_DEV_ID_PCH_CNP_I219_LM6 0x15BD #define E1000_DEV_ID_PCH_CNP_I219_V6 0x15BE #define E1000_DEV_ID_PCH_CNP_I219_LM7 0x15BB #define E1000_DEV_ID_PCH_CNP_I219_V7 0x15BC #define E1000_DEV_ID_PCH_ICP_I219_LM8 0x15DF #define E1000_DEV_ID_PCH_ICP_I219_V8 0x15E0 #define E1000_DEV_ID_PCH_ICP_I219_LM9 0x15E1 #define E1000_DEV_ID_PCH_ICP_I219_V9 0x15E2 #define E1000_DEV_ID_PCH_CMP_I219_LM10 0x0D4E #define E1000_DEV_ID_PCH_CMP_I219_V10 0x0D4F #define E1000_DEV_ID_PCH_CMP_I219_LM11 0x0D4C #define E1000_DEV_ID_PCH_CMP_I219_V11 0x0D4D #define E1000_DEV_ID_PCH_CMP_I219_LM12 0x0D53 #define E1000_DEV_ID_PCH_CMP_I219_V12 0x0D55

that's a different driver for the pcie cards, i know because i compiled both for the new 918+ extra.lzma the 1.3.3 is the one or the usb, the chip you would have to select ends with a "U" like usb the 1.3.3 has a release date of 08 July 2019, so its not old

that looks useful one logigal volume 3 raid sets sdg to sdn (8 disks) dev/md2 over all 8 disks 2TB from every disk /dev/md3 over 5 disks 2TB from eache, even slightly different in size from md2 /dev/md4 over 3 on 2x8TB disks, 4 TB partitions exactly as it was to expect you have the mdadm infos for every partition, even the start sectors and size of the partitions also uuid for every raid set what a cant see is how the 3 raid sets where arranged to be one volume i guess with this information you should be able to use a rescue linux and read all data if you find out enough about how synology handles the stuff internally you could also try to repair it in synology - but afaik there is no documentation so the safe way would be a rescue linux and then offload the data how about this to continue?

no its just a normal (older) computer with just 4 sata ports, pretty much the same as a normal 4bay nas just as 19" version only thing you could do is kick out the original board, build in something more powerful and use the 4 hot swap bays as normal drives 2nd option - extremely ineffective - throw out the board, aggregate the for bay's with a sas cable to a external sas connector and connect this 4bay sas chassis to a xpenology system with a sas controller with external port - more of a mind play, ineffective/expensive

you just use it as in the totorial of dsm installtion here https://xpenology.com/forum/topic/7973-tutorial-installmigrate-dsm-52-to-61x-juns-loader/ if you have a already running dsm 6.2.2.2 system but want to "activate" the unused (because no driver) hardware then it should be enough to shut down your box copy the 2 files to the usb drive, overwriting the old ones (plugging it to win10 will give you access to the 2nd partition with the extra/extra2 files) if needed the old files can be extracted with 7zip from jun's original image (or with osfmount) if you want to be sure nothing is wrong you can use a clean disk and new usb to test the new extra/extra2 by doing a fresh install and check that you hardware is working properly

you should move the usb drive together with the hdd drive, on upgrading the system on disk is upgraded but also your usb drive (new kernel and rd) so if you, after upgrading the disk, reset the usb to jun's original (older) dsm state both will not match anymore, the booted kernel (older) recognizes the mismatch and will offer to migrate as long as you dont allow direct access to your dsm over internet and dont have malware in you local network the missing security patches of you "older" version you use now might be ok, but keep in mind you dsm box is vulnerable in this state as it has unpatched security issues

synology protects its dsm system, we are using the original dsm files from them so it needs a hack to circumvent this protections its supposed to still look like its running on a original hardware, so the kernel is still the original and all checks (at least on loading) will signal that the integrity is intact i guess its much easier to just squeeze around the protection then completely analyze everything and build a whole new system, especially as synology is not releasing the whole source, there is no new kernel source for dsm for about 2 years now its a hacked appliance, not a linux distribution, if you are looking for something open then open media vault or maybe freenas might be more interesting

i hope next weekend last thing i remember from last year is that i compiled some of this but people got nowhere with it because the kernel options in the synology kernel where not set (we cant change the kernel), but we might try later again atm i want to do the drivers for 3615/17, then some newer versions of drivers people need

does setting it to 100 or 1000 work? did you look in the log (like "dmesg")? 918+ uses kernel 4.4.59 so its <4.10 as mentioned in the other thread, maybe it's more then just not seeing 2.5/5G btw its i little complicate as you kind of double posted and we try to write in 2 different threads about he same thing we should continue in the other thread as its no loader problem, more a specific driver problem

read this https://xpenology.com/forum/topic/12778-tutorial-how-to-downgrade-from-62-to-61-recovering-a-bricked-system/ imho easiest is a cross upgrade (same 1.02b loader but for different image) to from 3615 to 3617 you might loose some settings (not much i'd guess), that step ignores the version number, dont change anything in that state (like plugins) then migrate back to 3615, then you can install 6.1 again, check the update settings to keep major version and only install security updates if you know how to handle a rescue linux and mdadm you can also reset the version number on the system volume (raid1 over all disks) by editing a text file, dont forget the usb drive, on updating to to 6.2 it got new kernel and rd so best to safe grub.cfg and recreate it with loader 1.2b

probleme mit vdr das er den stream nicht hinbekommt oder freezed die r1? hatte das nur kurz im testbetrieb bevor ich es eingemottet habe (samt vdr), aber wegen der stream kompatibilität für vdr hatte ich die extra firmware von usb am laufen ??? mit dd? https://www.thomas-krenn.com/en/wiki/Linux_I/O_Performance_Tests_using_dd

yes, but you can have a look into the update section lots of hardware infos https://xpenology.com/forum/forum/78-dsm-updates-reporting/ that depends on the limits you set my where h max19cm, d max 40cm, w max 55cm and i wanted ti integrate 10-12 disks i came up with Streacom F12C (expansive), SST-PS13B Precision Midi-Tower, Kolink Victory A Midi-Tower ended with a SST-GD09B and reworking it, throwing out all inner stuff and building a wooden frame for the disk to fill up the front with 12 disk, replacing disk will be pain that way but when using HGST disks thats minimal (never lost a 4TB drive in 5 years, 12 disks raid6), its quiet and compact (living room) Silverstone DS380 always looked nice for a easy build, but usable for micro/FlexATX (btw. i was wrong above my gigabate it's microATX, so even wider but less depth then FlexATX, just 185mm, had miniITX before and had to squeeze something into the GD09 housing and miniITX is a problem when you want 12port, 10G network and cpu you can replace) but silverstone has other options (now) https://silverstonetek.com/product_server.php?bno=0&tb=44&area=en here the board sizes (max), helps to decide about limits to set Mini-ITX 170×170 Mini-DTX 203×170 FlexATX 229×191 µATX 244×244 DTX 203×244 ATX 305×244 but they can be smaller (as seen with my choice, but that can be hard to find, i ended up looking at photos on geizhals to find a flexatx that was smaller) also most "normal" cases have not a good thermal management, when putting in a lot of disks that it can be important to have air on all disks, so its also good to check the manual for airflow www.caseking.de has a good selection option to slim the candidate list but you can also try a simple "nas case" search on amazon or google, you might find something interesting

DSM 7.0 what i've read in the last days its like beta in q1/2020, maybe in december my guess, release q3/2020? so nothing we need to think about, 6.2 will be the thing to use for another year

"... Enabling Dual Channel memory mode will double the original memory bandwidth. ..." so only using one DIMM will result in lower performance realtek lan chips are not 1st choice but as this chip is part of the 918+ it is part of generic dsm driver set (if it work with the original driver needs to be tested, if that is of importance) "T" type only use max 35W, might be a better choice when it runs 24/7, but 9xxxT seem not available atm if it does not have to by miniITX, FlexATX give more options for the same money, more pcie slots "only" 4 SATA Ports onboard, there are also chipsets having 6 ports i dont know about hardware transcoding with that 9th gen cpu, if thats of interest you might search the board for it, in some cases a slightly older cpu can be a better choice my choice was Gigabyte B360M HD3, nearly the depth of miniITX and a little wider (because of 4 pcie slots) keeps you open for options like more sata ports with 4/8 port card and 10G nic's usually have 4x, some 8x pcie in general this should work with the 918+ image

i've downloaded the latest driver "AQ_USBDongle_LinuxDriver_1.3.3.0.zip" and the fiji.tar.gz contains a "README.md" but nothing like this what readme? where did you downlaod it?

if you are willing to to a little more then the most, there is a com port connector right beside the ram sockets manual states: COM Header (COM1)-(Optional), (for H310M-STX/COM) so with a Null modem cable and a corresponding com port on you other computer (only this can be a usb2serial cable/converter - i use a over the counter bought usb to SubD9) you could have a closer look (even login) using putty BUT i just released a new driver package for 918+ containing the latest e1000e driver and your onboard Intel Gigabit i219V is a nic running with this driver so in theory it should work with this new package my new thread needs to be approved by a mod but if there are no complains that i just made a draft test ... i could be seen online shortly look here for a new one with DSM 6.2.2 in the topic https://xpenology.com/forum/forum/91-additional-compiled-modules/