IG-88

keep in mind whats important and thats your 3 disks wit your raid/lvm volume containing your data, don't mess around with them without having backups of this disks (not important if its a fresh or virtual dsm, it can mess up your data) you can do a backup of these disk with dd to image files (that 8TB disk as destination), that way you would be able to restore the 2TB disks if things go wrong or you could leave the "original" disks as they are and continue with the image files and data recovery software at least you would have a backup, atm you still at risk loosing it all you would need a 2nd 8TB disk as destination for recovered files but at least you would always be in the position to still have one copy even if a disk fails and you do something wrong

why ask this in the developer section? that would be the right place https://xpenology.com/forum/forum/38-dsm-installation/ also i's suggest reading the faq https://xpenology.com/forum/forum/83-faq-start-here/ and these tutorials to get a picture (or maybe watch a youtube video as introduction - might look easier then it is) https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ https://xpenology.com/forum/topic/7973-tutorial-installmigrate-dsm-52-to-61x-juns-loader/

imho geht das nicht auf xpenology so ohne weiteres da die dafür serial und mac prüfen (die zusammen passen müssen) such mal danach, ist nicht mein spezialgebiet ist nor so was ich vom lesen so mitgenommen habe die aktuelle 6.2.2 die du instaliert haben wirst braucht neuere treiber als die die auf dem loader (1.03b) sind du musst eigentlich nur deinen loader richtig hinbekommen dann sollte die kiste wieder mit 6.2.2 starten beschrieben ist das hier, evtl. noch mal im alten tutorial nachlesen wir man den loader richtig aufsetzt (vid/pid ist am wichtigsten) https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/ ist getestet mit den neuen treibern und 6.2.2, wenn was nicht geht machst du was falsch (nur damit du nicht an der falschen stelle suchst ;-))

as in the link in the description above when you have 3615 and already installed 24922 aka 6.2.2 then the new kernel is already installed on your boot media so you download the zip file extract it to get extra.lzma and copy that to the loader, replacing the file there DS3615: extra.lzma for loader 1.03b_mod ds3615 DSM 6.2.2 v0.5_test http://s000.tinyupload.com/?file_id=87576629927396429210 SHA256: BAA019C55B0D4366864DE67E29D45A2F624877726552DA2AD64E4057143DBAF0 sd card? usually a usb flash drive is used for booting and where the *.img file is installed to if you use a sd card as boot media instead of usb then yes that would be the place its kind of dangerous to do things you dont understand, try to read the install tutorial again? the loader keeps its drivers in the file extra.lzma, to get new drivers you need to replace it and as drivers are specific for every model it needs to be the extra.lzma for the specific model (and loader version too), its linux not windows, drivers are usually very specific for one version of a distribution, any change of kernel version or even compile options of the kernel (what happend in 6.2.2) will make you need to compile drivers newly specific for that change

yes as long as you just boot the 918+ loader nothing will happen to your disks, its just to check if its found in network and the conclusion would be its about uefi/csm as 918+ does support uefi and 3615 does not if you continue installing (vid/vid must be set) the assistant will offer to migrate to the new system, you will keep your settings and data but i guess most of the (3rd party) plugins need to be reinstalled and you might not get all plugins for 918+, if that is important you can check by making a 918+ install to a single empty disk (disconnect "old" disks) and after installing check if you can get your plugins installed

start from scratch, check every file you used and if there is no name making clear what type/version it is download or unpack it again just to check for booting and to find it in network you don't need to change grub.cfg (vid/pid is most important but will only be relevant when installing the pat file) just replace extra.lzma, zImahe and rd.gz - its faster hat way and if it works you can change grub.cfg later also the dsm usb boot device should be without a partition marking, only uefi supports booting from different partitions of one device on my test system it needed a reboot (with the usb drive connected) and then to go into bios to see it as boot device also with your hardware you could use the 1.04b 918+ loader and "syno" extra/extra2

if you used the new extra.lzma, zImage and rd.gz for 6.2.2 then the only problem that might be left could be uefi/csm loader 1.03b only supports bios/csm https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ so make sure your uefi is set to csm active, save, reboot, go into bios and look for a non uefi usb boot device (usually there are two uefi devices as for 1st and 2nd partition of the usb device, there has to to be a 3rd one without mentioning of a partition as a "classic" bios like boot device)

interssant, habe das grade mal bei mir probiert, bisher gab es die 2.partition als laufwerk, jetzt nix mehr (vor 2 jahren waren mit win 10 noch beide partitonen als laufwerk nutzbar) muss aber imho nach 1909 passiert sein, vor 4-8 wochen ging das noch naja, die alternative ist halt image vom stick erzeugen, mit osfmount ändern und wieder schreiben - oder gleich unter linux bez. auf dem nas mounten, das geht auch 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

i'd suggest to read and understand about the main process off installing/updating here https://xpenology.com/forum/topic/7973-tutorial-installmigrate-dsm-52-to-61x-juns-loader/ without doing it as there are specialties about 6.2.2 you need to read on a 2nd article https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/ if you last did this 4 years ago then its better to "re-understand" the process before starting the gen8 is tested with 6.2.2 and the new drivers you should start with creating a new usb (keep the old, at least as image file created with win32diskimager) and try that one with a single empty disk, if you get a satisfying result you can use this new usb later to boot your new 6.2.2 reconnect all disks with 6.0 on it and now you have 2 possible ways 1. re-insert old usb, boot up and let dsm do the update from web gui, that one has a step i'm uncomfortable with, after unpacking the update and installing the new kernel to the (old) usb it will not be able to reboot as the loader is for 6.0 and not for 6.2.2 so it will be stuck in the middle and it can be hard to judge when it is in that state in with you cant properly shut down, you would need to hard switch off, swap usb to the new (6.2.2, tested) and start again, it should continue the update to the finishing line, it might be ok o wait a overly long time like 2h to make sure its finished preparing the update (the time depends on the speed of the system/disks its usually <30 min) 2. use the new 6.2.2 /tested) usb to boot, use the synology assistant to find the system in network (same as on fresh install) and let it "migrate" to the new dsm 6.2.2 version by installing the 6.2.2 *.pat file, imho that is the safer and cleaner way and what i suggest in the 2nd link above usually some of the plugins fail after update and need to be installed in newer version (if available, if important you can check that with the test install of the one single disk) if anything goes wrong with the updating your 6.0 to 6.2 config you still have the option to use the 2nd option in the boot loader to reinstall the system with its factory defaults and still keep the data/raid volume, after that it will be like a fresh 6.2.2 install but with your old raid volume present (its still suggested to have a backup even when this step does not delete your data)

hallo, hätte ich mir auch anders vorgestellt, wenn du schon 6.2.2 hast hätte extra/extra2 eigentlich reichen sollen da dsm beim update (auf 6.2.2) zImage und rd.gz neu auf den usb stick geschrieben hat, nur wenn du einen neuen usb aus dem orginal von jun erzeugt hättest würden die neuen zInage und rd.gz benötigt das du osf mount erwähnst könnte auf neu erzeugtesn usb hindeuten, der "normale" weg wäre gesesen den laufenden stick unter windows anschließen und die extra/extra2 ainfach draufkopieren (und die alten ersetzen), man kann zwar auch das imgae vom usb mit win32diskimage lesen, mit osfmount bearbeiten und dann wieder mit win32diskimage auf den usb schreiben aber das werden vermutlich nicht viele machen ein special dabei (das in dem treiber artikel nicht vorkommt) ist das auch der kernel mit Updates zu 6.2.2 erneuert werden kann und man in dem fall dann in dem updater file (das lezte beinhaltet alles von den vorherigen update files) nach "flashupdate_6.2-24922-....deb" suchen muss und darin findet man dann die aktuellen zImage und rd.gz in dem fall kam mit update 5 der letzte neue kernel mit filedatum 14.01.2020 und das wäre die files die jetzt auf dem usb stick liegen sollte wenn auf dem system U6 installiert war (auf dem system meint in dem fall die systempartitionen auf den disks dia e als raid1 laufen) - wenn auch mit den files aus dem original 6.2.2 geht ok aber dann gibts ungefixte lücken aus dem update pack im kernel (kann wichtig für funktion aber auch sicherheit sein)

the synology kernel does not have amd support so it seems unlikley that a feature like SVM will be usable in DSM/VMM

the output of the serial console will be the thing to check but some system dont have a serial port anymore and most people dont have a nullmodem cable around (millennials might not even know what a nullmodem cable is without looking it up), you could even login the system this way (if it comes up its also possible that there is a kernel crash and the system freezes, you cant see the difference from looking at the video signal, that stops soon after booting) that at least looks like the i915 driver was loaded as there are devices below /dev/dri if you see this and you have network working your problem could be seen as solved i cant do anything about the driver itself as i dont have the source (jun included newer i915 drivers in 1.04b but i dont have source to recompile them and i also not able to do a new backuprt of i915 drivers to the 4.4.59 kernel of dsm) its kind of the same for the native driver from sysnology that comes with dsm thats more or less the reasons why there are syno and std to choose, binary drivers from two partys we cant change you can try to use the internal transcoding from synology with this https://xpenology.com/forum/topic/24864-transcoding-without-a-valid-serial-number/ plex can have issues by itself on some systems, i doe remember some threads about specific problems with synology and plex where you had to delete some files from plex to make it work i was about so say it should be possible to see this by looking at "drivers included (Reveal hidden contents)" in the 1st post here but looks like i did not look into that list for a while, i added 4 realtek nic's and now your r8125 is there too - so yes it should work, i did a new driver and if there is newer source and a newer chip/phy turrns up that need a newer version i will make a newer driver beside my list you can also open the extra.lzma and look what *.ko files are in, you should see r8125.ko there too

what did you replace? if you change the packeges without cleaning the drivers in upddate folder you might get different results depending on what you had there before how doe you know? the fact you can't find it in network is no proof of that, more likely the kernel/driver crash on boot try a fresh install to a empty disk with syno

the card is original synology but its not supported on all hardware (and it needs a minimal dsm version 6.2-23739-2 or 6.1-15284-2), a atlantic.ko driver is only present in 3615/17 not in 918+ image to it should have been working ootb as native drivers with 3615/17, but doesn't matter as the driver is also in the extra drivers

thats only true if you don't install the *.pat file and use it to test if you can find it in network if vid/pid in grub do not match the real one's of you usb device you will get error 13 when installing the mac is only needed when using WOL or for some reason you need to use a pair of valid serial and mac i guess you meant to say you dont need serial and mac for installing (both can be changed later in the grub.cfg if needed)

that limit is just a few entry's in a config file, jun's 1.04b loader default is 16 and it can easiely modded to 24

its pretty new, i have not seen one yet here but from the hardware it should be ok with loader 1.04b (918+), also G5400, i5-9400 are tested with hardware transcoding so i'd assume the G5420 will work too storage is standard intel (so its ahci) and nic is intel i350, we use recent intel drivers for the driver extension so it should work (and if not i will have a look) https://xpenology.com/forum/forum/83-faq-start-here/ 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/

thats usually a sigh for crashed drivers (kernel oops, check the log) you istalled 24922 aka 6.2.2, did you also copy new drives to you usb boot device? 6.2.0 -> 6.2.2 had kernel oprion changes requiring new drivers so the drivers that come with jun's loader will not work and you fall back to drivers delivered with dsm https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/

beside you are cross posting (its in general not a good behavior) you don't write anything about your hardware, i can assume you connected at least a hdd to your board/controller but there are limitations what storage hardware is supported (ahci is ok in general), it also depends on the loader and dsm version you try for more "ancient" hardware loader 1.01 or quicknicks 2.2 loader with DSM 6.0 might be a good choice DSM is not a full linux its a hacked appliance and drive can be a problem

that board is for Ivy Bridge and Sandy Bridge CPU's so no 918+ image for you depends of the loader you choose there is still 3615 or 3617 to choose for you for the start stay below v24922 file and do not update to the latest in the web gui, it would complicate the install further https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ as always - it depends on your choices loader 1.02b = DSM 6.1 loader 1.03b = DSM 6.2 enough time to read a lot and try things?

1.04b is only 918+ and accourding to the cpu support its to old for this type (4th gen intel, haswell minimum) https://support.hp.com/us-en/document/c01683078 dsm 6.2.2 is also available for 3615/17 so even a older system can run the "latest" dsm when it comes to m.2 nvme and hardware transcoding of videos then 918+ will be the choice, 918+ also has a newer kernel but you will not recognise it for now when it comes to driver support

wenn du über virtuellen seriell port dran kommst kannst du sehen was die ip adresse ist und du könntest dich auch lokal anmelden um sachen zu konfigurieren nested vm - ganz allgemein geht das, habe z.b. win10 mit virtualbox and darin esxi 6.5 gestartet, vm in vm ist kein allgemeines ausschluss kriterium, mit moderner hard- und software geht das prinzipiell

manual load with insmod and check where? i did not get any positive feedback that anything with virtio was working, maybe two negatives, as there is the recent source now available i will make new drivers, also virtio, maybe i will make a special test version for this to make it easier for people to test, might produce more feedback (not that i could answer question about kvm, never used it)

I'd say wrong thread, please open a topic in the install section https://xpenology.com/forum/forum/38-dsm-installation/ and choose a sub section if it fits your hardware

1.04b is just for 918+, read this to get more information https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ if you use 24922 then you will need different drivers (as of changes in the kernel of synology in dsm s6.2.2 aka 24922) https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/ just copy the extra.lzma (depending on you loader type) to the 2nd partition of your usb replacing the files there and you should be good after the next reboot this card might be a aquantia based card (older 10G Base-T from synology was a tehuti)