IG-88

i did try to outline the "how" above, analyze how its done in qucknicks loader and we will try to replicate that in jun's loader (he never released it, a beta tester released it and he withdrew, so there is no extensive documentation or help and that the release was without his consent is also the reason i do not support anyone using it - even its a really good peace of work and would have deserved more attention)

if you use a 4th gen or newer you could use 1.04b 918+ dsm 6.2.3 in uefi (works csm too), only 1.03b 3615/17 needs csm/legacy https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ without exact information about the board we cant say anything about the nic if its a intel i225 its not going to work even with a extended driver version of the extra.lzma, in that case you can start looking for a additional nic any other nic will be at least possible

that "feature" can be changed at any time by synology as they have control over kernel and loader and even if they introduce it, it will be only for new types, our systems already in use like 3615/17 will have no problems for synology its not just the selling its also about support and customers that call them in case of problems and when it comes to business use you dont want trouble at all, the hardware/server i supposed to be quiet and should do the job, there are enough software troubles i would not dare to introduce "foreign" disks to our HPE SAN system just to save a few dimes, compared with the cost of disks the possible trouble is not worth the risk, even half a day storage offline is too expansive, time of people in IT and possible loss of data and employee work hours can make experiments expansive on long term i guess using a synology disk will be optional, customers wanting a full 5 year warranty for the whole system and as less trouble as possible will opt for that by themself

if you dont want to create a new loader for 6.0 you would need to ignore that my intention would have been to steer you at least to loader 1.02b with dsm 6.1 (that one does uefi and csm/legacy, 1.03b for dsm 6.2.3 does only csm/legacy bios and some people have problems to get that working as it need certain bios settings and also booting from the non uefi usb boot device) so if you just started and dont have data an your nas i would suggest you give loader 1.03b a try as this dsm version get's (security) updates

same as the youtuber, in his 3rd video he gave up on that no one did so far and as i suggested the only way to go down that line would be 1. to test quicknick's loader with more then 24 drives (a vm would be easy to do with lots of "thin" disks) 2. find out why its working (i tried to point out where to look for it) one thing i found out "new" is that its not about the sdX vs. sdXX name of the devices involved i have a asm1166 based ahci controller with 6 ports that "block" 32 ports in the kernel so controller after that one will land 32+ in name/count and are sdXX and it did work to create a raid5 in that state - thats the reason to have a closer look into quicknick's loader, we might be able to include that feature in jun's loader/patch

in general will you need a new loader for new dsm major version, 6.0, 6.1, 6.2 if you are going to make new loader it will be jun's and the procedure is the same from 6.0 to 6.2 i'd suggest using a loader for dsm 6.2.3 but it might depend on your hardware if its ahci the no problem, other wise it depends https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ https://xpenology.com/forum/topic/7848-links-to-loaders/ https://xpenology.com/forum/topic/7973-tutorial-installmigrate-dsm-52-to-61x-juns-loader/

no uefi is fine with 1.04b 918+ https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ if you get as far as seeing the booted loader in network you don't have boot problem you can try to extract zImage and rd.gz. from the 6.2.3 *.pat file (using 7zip) copy that to the 2nd partition of the loader (replace the file there) and also copy new extra/extra2.lzma from here https://xpenology.com/forum/topic/28321-driver-extension-jun-103b104b-for-dsm623-for-918-3615xs-3617xs/ to the 2nd partition, also replace the files, that way the loader will be updated to use the kernel of dsm 6.2.3 try if you still see the loader modded this way in network (before installing the *.pat file)

its a littel un-specific, "THIS" can stand for a lot of things

https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ 1.03b 3617 dsm 6.2.3 would be the one to choose if there are any problems you can try one generation back loader 1.02b with dsm 6.1 https://xpenology.com/forum/topic/7973-tutorial-installmigrate-dsm-52-to-61x-juns-loader/ for dsm 6.2.3 just use loader 1.03b instead, all the steps are the same there are some minor problems editing the loader with windows 10 https://xpenology.com/forum/topic/29872-tutorial-mount-boot-stick-partitions-in-windows-edit-grubcfg-add-extralzma/ also the faq is good to read for some basics (like that the loader is usb and the system (dsm itself) is raid1 over all disks https://xpenology.com/forum/forum/83-faq-start-here/

yes and the solution is also there, look in bios to set sata to ahci (ide or raid are wrong) - if there is such switch, you never know with HP as they customize the bios heavily its not going to be much better, you would not need mbr loader and the switch for sata ahci might be present and easier to find but you would still be bound to 3615/3617

sahte ich ja schon der treiber an sich ist in der extra.lzma von mir drin (nutze selbst eine solche karte) aber wenn keine device da ist wird halt nur versucht der treibe zu laden und das wars dann, wenn etwas erkannt wird spuckt er auch noch ein paar mehr infos als die treiberversion aus hatte ich ein paar posts zuvor beschrieben https://xpenology.com/forum/topic/28879-brauche-hilfe-beim-sata-mapping-asus-p9d-i-9211-8i/?do=findComment&comment=189080 man sucht nach der pci id des vendors broadcom und kann sich auch alle den treiber betreffeden meldungen ausfiltern lassen ansonsten kannst du auch mit einem editor in dem text file nach den geannten strings suchen aber die sind beide nicht in der lspci ausgabe die du angehängt hast nein, wenn kein pci(e) device angezeigt wird (hattest du ja nicht mal bei einem gebooteten alternativen linux) gibts kein treiber problem, ist ja nichts da für den treiber zumindest kein netwerk treiber problem, pci als kernel grudfunktion hat natürlich auch treiber die fest im kernel sind aber da auch ein anderes "normales" linux die akrte nicht angezeigt hat muss es etwas anderes sein so ziemlich jede die ich gemacht habe da ich die karte schon fast 5 jahre lang habe das mit sfp+ oder 10GBASE-T hängt nicht vom netzwerk chip ab das ist der phy dahinter entscheidend ist die pci vendor und product id und evtl. noch die sub id's dazu, darauf spricht der treiber (bnx2x.ko) an wenn du nachsehen willst, kannst du die extra.lzma mit 7zip öffnen und in /lib/modules/ liegen die treiber (*.ko), geladen wird was in der rc.modules steckt

wouldn't a backup with hyperbackup (incl. configuration) restore users and shares? the simplyfied calculation for "resulting size" is ti sum up the capacity of all drives and remove the size of the biggest drive, there would be a huge portion wasted if you dont add a 2nd or 3rd big hdd synology has a lot material online that you can use https://www.synology.com/en-us/knowledgebase/DSM/tutorial/Storage/What_is_Synology_Hybrid_RAID_SHR

you log say's differently, sataportmap=414 but you usually can leave with the default value me too, because asm1061 is a 2 port sata controller chip that would be a typical card https://www.sybausa.com/index.php?route=product/product&product_id=151 maybe its a card with a sata port multiplier? ASM1061+ASM1093 (asm1092 is a one to two port multiplier so i guess 1093 is the same but one to three ports) https://www.orico.cc/usmobile/product/detail/id/3898 in that case you will only be able to use the two ports of the 1061 as synology blocks port multiplier and as we dont have a custom kernel it can't be changed use a pcie 1x marvell 88se9215 based card instead and maybe 2x jmb585 based card in the pcie 16x slots? lsi sas2008 based pcie cards (8 port sata with sas to sata cable) are a option too (i prefer ahci for my builds) also keep in mind that that 12 is the max. for 3615/17 without manually tweaking the synoinfo.conf and when modding you will loos that change on bigger updates making the raid missing disks over 12 and will result in raid not starting or starting without redundancy - if that is new to you then start reading about it here in the forum

you might need mbr version of the loader with HP https://xpenology.com/forum/forum/98-member-tweaked-loaders/ try loader 1.03b and dsm 6.2.3

so then use the hp to prepare a usb/disk just use the usb you intended for the whyse (match the usb's vid/pid in grub.cfg) disconnect alls disks and the hp's usb and use the new usb and a empty disk to intall after you are done you copy off the grub.cfg from you new usb, rewrite it with the non mbr version of the loader and copy your tested grub.cfg back to that new non mbr version that usb and the disk you prepared will hopefully boot on the whyse

imho install with usb nic is not supported, you should install with a onboard nic or a pci/pcie card nic and after that you could add the usb nic (before starting dsm) if the usb nic is supported you should see a additional network card in dsm and should be able to use it (keep in mind that the usb 2.0 bandwidth can't be more then 40 MB/s) whats wrong with the onboard nic? according to asus its a marvell 88E8056 gigabit nic and its driver sky2 is supported in the loader also i would suggest using loader 1.02b, the "a" and "a2" had problems and where replaced by "b" https://xpenology.com/forum/topic/7848-links-to-loaders/ not shure why is has to be 1.02 and dsm 6.1, you could also use 1.03b and dsm 6.2.3, all the same when it comes to installing and loader preparation

no msata is still sata and boot is from usb, a possible alternative are internal sd/micro sd card readers as the usually are usb devices (like on some hpe microservers) and you would need to know the vid/pid of that usb device to boot from it

https://xpenology.com/forum/topic/28321-driver-extension-jun-103b104b-for-dsm623-for-918-3615xs-3617xs/

afaik thats just mellanox cards for 3615/17 because the driver is not in extra.lzma and also not in rd.gz (from synology), the original hardware has 1G onboard so they dont need that to be present at boot and as the drivers from synology are working there are no drivers in the extra.lzma i'm nitpicking here (and it depends a little on the bios settings) but if you boot with csm on and choose the uefi device as boot media you end up in uefi mode that's partly the reason why people have problems to get it to boot in csm/legacym, the csm switch is just a option on top of uefi (in most cases, i've also seen bios that would disable uefi boot when csm was activated, but that's rare) if the bios is in clean uefi and csm is activated it would need one boot with csm active to see the legacy boot device and if not chosen manually at boot process the system will usually prefer the uefi boot device so often just activating csm is not enough

yes ??? https://www.synology.com/en-ph/knowledgebase/DSM/tutorial/Backup/How_to_migrate_between_Synology_NAS_DSM_6_0_and_later#FgL7hWweWr "... HDD migration ... You may choose to either migrate between different Synology models or identical models. ..." for the running dsm system there is no difference if its original hardware or a xpenology on custom hardware so you can do it exactly like synology suggests it

you will not find much about that scenario here, most use esxi or kvm based proxmox thats the one i know about but i did not try it myself https://www.uxora.com/other/virtualization/57-xpenology-on-docker

ahh, ok thats good to hear i'd suggest checking the disks with a tool from the manufacturer and removing every partition so you will have a complete fresh install and volumes if you use loader 1.02b and dsm 6.1 you dont have to bother about uefi/csm if the hardware is at least 4th gen intel (haswell) you could use 1.04b 918+ with 6.2.3 (there are no information about the hardware you use) the normal affordable home units are a little under powered and can't be much extended beside too expansive external synology disk enclusures (no pcie slots) but the hardware is reliable, if you have a more basic nas in mind without VM's or docker its not a bad choice Qnap does more or less have the same but some better extendability like pcie slots (for 10g nic and nvme) in smaller units, nvme as data volume (synology only supports that as cache)

loader 1.03b is for dsm 6.2, extra.lzma 4.8 is for dsm 6.1 loader 1.02b for loader 1.03b you need this source for download https://xpenology.com/forum/topic/28321-driver-extension-jun-103b104b-for-dsm623-for-918-3615xs-3617xs/

das ist ein 8GBbit FC, nicht Ethernet oder Converged, der nutzt dir nichts normalerweise nicht, sollte einfach so laufen, du kannst ja mal im bios anchsehen ob es irgendwelche pcie einstellungen gibt

i've had sometime problems when assigning a static ip address when installing, dhcp always worked so far you can also try to use usb/disk combo on another system for installing and then take both back to your wyse system