IG-88

also hp, alt und starte nicht - schon mal einen loaer mit MBR probiert? https://xpenology.com/forum/forum/98-member-tweaked-loaders/

if you use loader 1.04b as it is you need to go with 23739 24922 need different drivers, gets a little complicated for just trying to install the 1st time, you can update later to 24922

any additional hardware like M.2 ssd, disk controller you can remove? i've never tried that much ram, should be no problem but you can also try to strip it down to 8GB there is also the option to do a install to one disk on a different system and then move that usb/disk pair to the hp z440 and see if it boots up (kind of skipping the install step on the hardware in question) if you have a serial port you can connect a null modem cable and get a console to see what happens (after the last message on the screen the output is directed to the serial port)

you can open a ssh session with putty and type "dmesg" to see some log you can also look at files in /var/log/ the files dmesg, kernel.log or messages in this files you should see at least the time when the connection got lost if that is possible you can install a 2nd nic, configure it to a different ip and connect it parallel to you existing connection an see if it disconnects too at the same time

it should have worked wit the old extra.lzma and dsm 6.2.0, only the kernel options change by synology broke that for 6.2.2 and it needed newly compiled drivers to match the new kernel but now as there are fresh drivers for 6.2.2 it should be working with 6.2.2 when already running 6.2.2 you could add the new extra.lzma to your usb and on next reboot it should be loaded and copied to your system if you want a test without any risk there are 2 options - extract the bnx2.ko from extra.lzma (extraction is possible with 7zip or the way described in the driver injection tutorial), copy it to your running 6.2.2 dsm and insmod the driver (as the old one did not work it should not be needed to rmmod the driver), that driver needs firmware but the firmware should be already there and is still the same as in the former 6.2.0 version - create a new usb, disconnect all drives in use, use new usb (6.2.2 kernel and new 0.5 extra.lzma) and install to a empty disk to check the result if there is no one around providing new drivers then using a hardware that is directly supported by dsm is a option (the other is to stay on a older release like 6.2.0 or 6.1) on my new system i will use a 8 port ahci controller instead of the good old sas2008 (mpt2sas) based controller - as synology is not meddling in the kernel code of the network cards its still no problem to provide drivers for nic's (as long as they are in the 4.4.59 kernel or the external source is compatible with that kernel - at least for 918+, for 3615/17 its kernel 3.10.105 and that can be a problem in some cases as new external drivers might compile/work with that old kernel) edit: wait, it did not work for you on dsm 6.1 with my extra.lzma (like v4.8)? should have, the driver is there and the firmware files also match the driver, i'm sure there where people with dell's that got it working, afaik this driver was already part of jun's extra.lzma but there where 2 (mips) firmware files missing in jun's extra.lzma so it work not for all (maybe depending on hardware version of the nic)

Dell PowerEdge R410 has embedded dual-port Broadcom NetXtreme II 5716 - driver bnx2.ko, suported by new 0.5 extra.lzma for DSM 6.2.2 also any 1 Gigabit intel nic should work as there there are recent drivers in the new package

there is a md5 hash file too so you can check if you file is ok https://archive.synology.com/download/DSM/release/6.2/ also the pat files are just zip files, extracting them with 7zip or similar should show corruptions too did you enter the vid/pid of your usb flash drive in the grub.cfg like in the tutorial? https://xpenology.com/forum/topic/7973-tutorial-installmigrate-dsm-52-to-61x-juns-loader/ btw your cpu would also allow using 918+

yes, if you use 1.03b loader as it comes from jun you will have to use 6.2 v23739 and you cant update further without "loosing" the internal nic as updating to 6.2.2 (v24922) will invalidate the "old" driver from 6.2.0/6.2.1 (6.2.2 kernel used different compile options, the new drivers use these options too and will work with 6.2.2) i'd suggest you take 1.03b, add the new kernel and drivers and then install 6.2.2 with that "modded" loader, see link below https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/ that way you are on the latest version and can use all security updates availible

if someone with a J1800/J1900 is willing to try the new 6.2.2 driver package i would make a version without the new i915 driver - in that case the synology drivers should be loaded and /dev/dri should be there after boot (under best conditions) atm it seems the safest way to offer two different versions .of extra/extra2.lzma (for my own system i will use the one with newer drivers as i'm using a coffee lake cpu)

i had a case once (avoton system) where installing failed but running from a installed usb/disk combination worked i'd try that that 1.03b usb and one of the disks you want to use in a different hardware, if the usb is ok then it should work on a different hardware, after installing move both to your C2538 system and see if it boots i never found out why it was not installing, you would need to connect a serial (null modem) cable to find out whats going on and even then you might not want to dig in that deep into the synology install process, much easier to try to "skip" install and doing this step on a different hardware also to spare some update trouble you might start with the latest 6.2.2 version (there are matching drives available now) https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/

to what version? if you use 6.2.2 then the new 0.5_test is ok but you also need to copy the zImage and rd.gz of 6.2.2 to the same location as the extra.lzma if you skip that then kernel and driver (in extra.lzma) do not match

beside the faq https://xpenology.com/forum/forum/83-faq-start-here/ you need to read this https://xpenology.com/forum/topic/7973-tutorial-installmigrate-dsm-52-to-61x-juns-loader/ the extra.lzma is a addition to the install tutorial and my text assumes that you know how to handle the boot image and the usb flash drive especially when installing the latest 6.2.2 you will need the new drivers as most drivers dont work with the drivers (in extra.lzma) that comes with the boot image

most likely only the nic ahci is working for sure assuming 6.2/6.2.1 you can try risk free by using a fresh usb with 1.03/b1.04b (when just booting without intent to install even vid/pid not needed) copy new kernel (zImage and rd.gz) from 6.2.2 pat file to 2nd partition of usb and adding a 6.2.2 aware extra.lzma (3615/17 official test available in thread, 918+ for testing from me if you want) when booting from usb with a newer kernel dsm (from disk) will not be loaded, it will stop in the state it would be on a fresh install, you could search in network and when succesfull you would see that the system is migrateable, if nic or storage does not work you will not find it in network or it will not show migrate (instead it will show no disks) if the test looks good you can copy the same files to you real usb and boot again, then migrate with 6.2.2 pat file (web gui or nynology assistant), that way you should know of a problem before installing 6.2.2 (and having to downgrade in case of problems)

maybe you should leave it the way it is, might not be worth the time you would need to invest to do it the way suggested above, also no guarantee it will work as intended as its just theoretical as can be seen in the link above someone already tried exfat as package and did not manage it to work the way it was intended, in the end it looks like as the code was removed about 2 years ago whats not part of dsm will not be overwritten so the stuff in /usr/local should stay there and the files that belong to the package are stored on the data partition you have to create after installing (when not done automatic) /dev/md0 is you system (raid1 over every disk) /dev/md1 is swap (also raid1 on every disk) /dev/md2 is your 1st data volume/raid you create and that's also the default place for packages/plugins (usually /volume1/@appstore/, and usually not a place to do things manually, its used by the package center and meddling there might break packages or worth) so be careful and experiment with a spare system or a virtual dsm (dsm can be used in virtual box or vmware as vm, there are tutorials for this)

what was not working? 918+? there are differences in the kernel of 6.2.2 that make most of the additional drivers useless when updating to 6.2.2 it needs a new extra.lzma with new drivers (or hardware that is supported by dsm by default) for 3615/17 it was released mid december, for 918+ is a new version nearly ready, not perfect but better then the one already available, intel and realtek nic drivers in recent version

i think you would not need this if you use proper drivers after update to 6.2.1+ you use a newer kernel that contains changes that makes (most) drivers from before (default drivers from jun) incompatible, when using new compiled drivers with the right kernel options it should work as before (no scsi/sas controllers in the vm, all sata) in your case you would just need to copy the new extra.lzma into your bootimage (that was already updated to the new kernel) https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/ https://xpenology.com/forum/topic/13061-tutorial-install-dsm-62-on-esxi-67/

https://synocommunity.com/packages the file extension of Synology PacKages or plugins not really, thats inside the system partition and has limited space there are symlinks to the data volume where spk's or your data are stored if you want to manually integrate it you can look how the docker "plugin" is installed (in data volume) and to make its binary and files available to the system it created symlinks in the partition, that seems to (at least one) official way to have it integrated in a way it will survive updates you can read a littel here and see on in the code snippets about the linking into /usr/local/bin (from install directory - located on the data volume) https://github.com/SynoCommunity/spksrc/pull/1913 afair exfat was made open source or at least free a while ago by microsoft, is the exfat plugin from synology still a payed extension? i guess it will go into kernel at some point and be part of the system by default (might take a while)

http://www.mediasmartserver.net/forums/viewtopic.php?f=26&t=13602 aber ich habe so meine zweifel ob das lohnt, die J3xxx/J4xxx Systeme könnten das vermutlich einfacher und besser oder irgend ein gerauchter pc mit 4core cpu kommt natürlich auch drauf an wo man so dran kommt, auf arbeit fliegen im nächten quartal ca. 250 hp desk pro 6305 mt A8 cpu und 8GB raus und die meisten werden wohl im schrott landen, ein oder zwei werde ich mir da als xpe test system nehmen können und dann fliegt der murx den ich hier zum testen habe auch raus (u.a. ein q6600 system, ein hp dc7600 und ein hp dc7800)

i found this usefull (picture of windows device manager) https://www.smallnetbuilder.com/nas/nas-reviews/31022-hp-storageworks-data-vault-x510-reviewed

der scheint einen realtek 8111 onboard zu haben, sollte aber auch gehen, die extra.lzma hat auch aktuelle realtek treiber

habe ich vor nicht ganz 2 wochen in dem thread für zusätzliche treiber veröffentlicht (ist nur nicht so gut zu finden da es kein neuer ist sondern nur der 1. beitrag angepasst wurde, wird dann beim neuen paket für 918+ auch so sein) ist nur alt test deklariert da es einschränkungen mit den storage treibern gibt und ich etliche nicht testen konnte, die netzwerk treiber funktionieren eigentlich recht gut (ob der auantia 10G treiber geht würde mich ja interessieren) https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/

the thanks goes to @luchuma for making a good tutorial that helps people

then giving the nas a static address seems to be the best choice left

if not you can boot up a live/rescue linux from usb and use ifconfig to show the mac's

for this you need a MAC for the dhcp server in this case i'd strongly suggest using the real MAC of the nic in grub.cfg so it will always have the same MAC