IG-88

yes, but all the usual limits a re there too all about raid modes and raid extension can be checked on synology#s help and faq/kb

you can open the extra.lzma with 7zip and check rc.modules and the *.ko files in "modules" HPE uses broadcom or intel and both are there you can also use iLO's virtual com port to check you the serial console using putty, that would give you a hint about whats going on i tested the hpsa.ko driver with a p410 lately, the p410 can only use raid mode so i created a raid0 and raid5 to test if its working and it did, so maybe start with that in theory the p420 can be switched to hba mode and in theory the driver should work with that too but as the p410 does not support that, i could not test this mode just don't assume things when you can test it -> see above, check fot the *.ko and in rc.modules - it is there (just the basic version form the kernel) so if something goes south you would need to check by serial console to pin it i cant do anything as i dont have a p420 to test with where did you get thsi or how did you create this hpsa.ko? if you want to know how to mod the extra.lzma you might need to read this https://xpenology.com/forum/topic/7187-how-to-build-and-inject-missing-drivers-in-jun-loader-102a/ just to check if its working or not you can copy the *.ko file todisk and load the driver manually with insmod but the driver is working (at least in raid mode) https://xpenology.com/forum/topic/36135-how-to-install-on-hp-dl380-g7/?do=findComment&comment=186543 use serial cable or iLO's virtual com port to check whats going on when booting the system, the only way to really know whats going on

imho you need to overlap internal and usb to have the usb disks as internal, like this maxdisks="24" esataportcfg="0x0" usbportcfg="0xfff000" internalportcfg="0xffffff"

have a backup and don't restart? i dont know your hardware but maybe a pcie ahci card and "peeling" the usb drives might be possible

that type is used in sfp+ modules (network) have a close look and compare to this https://en.wikipedia.org/wiki/Serial_Attached_SCSI#Connectors lets assume SFF-8087 for now the board is ok, you could use the pcie 16x slot for a lsi sas controller with 2 x sff-8087 the 6 x sata onboard can also be used with a "reverse" cable https://www.delock.de/produkte/G_83319/merkmale.html?setLanguage=en lsi sas is used by most, 9211-8i and oem adapters with the same chip, it needs to be flashed to IT mode adaptec seemd to be a lot of trouble here, you can use the forum search, also and raid controller that does not support hba mode should be avoided and if its not lsi sas the you need to check here if a driver is available (and tested), also avoid lsis sas raid type controllers check if you can reflash it to IT mode or better buy one already in IT mode there are some problems with the lsi sas in 918+ (used when hardware transcoding or m.2 nvme is needed) https://xpenology.com/forum/topic/28321-driver-extension-jun-103b104b-for-dsm623-for-918-3615xs-3617xs/ a more failsave choice can be ahci but the amount of controllers with 4+ count is limited and and some only use 2 lane pcie 2.0 and for like 8 ports that can be a little "thin" a alternative could be using 3 x revers cable and a 6 port asm1166 based pcie controller you get your 3 x 4 ports with the 6 onboard ports, the asm1166 supports pcie 3.0 so the 2 lanes it can use are not too bad (you board supports pcie 3.0) if you dont need transcoding you can use loader 1.03b 3617 and can be happy and safe with a lsi sas controller (having 8 pcie 2.0 lanes is good enough) https://xpenology.com/forum/topic/38310-starthilfe-benötigt-asrock-j4105m-2x-4-fach-sata-controller-karten-werden-vom-biossystem-nicht-erkannt/?do=findComment&comment=186063 he used two of these cables

thats one gen to old for 918+, needs 4th gen cpu if you use 1.03b you need to keep in mind that it needs CSM mode in uefi and also needs to boot from the non uefi usb boot device https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/

could you upload it somewhere so we can use it for testing?

i#m not using vmm bu maybe this video helps? "Synology VM-Manager w/W10-1903 & Server 2019 Install & configure" https://www.youtube.com/watch?v=MwhCBTHOmVw

not so fast you log shows 2 port ICH9 and if you cant switch them to ahci you cant use them but there is also 01:00.0 RAID bus controller: Marvell Technology Group Ltd. 88SE6440 SAS/SATA PCIe controller (rev 02) Subsystem: Marvell Technology Group Ltd. 88SE6440 SAS/SATA PCIe controller Kernel driver in use: mvsas Kernel modules: mvsas and that driver is in my extra.lzma (not in jun's default driver set) for 1.03b you would need the matching extra.lzma from here, just replace the one on the loader https://xpenology.com/forum/topic/28321-driver-extension-jun-103b104b-for-dsm623-for-918-3615xs-3617xs/ 88SE6440 would be a 4 port chip, so if you have 6 sata ports try different ones (maybe they have a different color or are separated) and if the board has a pcie slot you could still add a pcie card there are different ahci compatible chips jmb585 is good (5port), depending on the pcie slot the bandwidth can get in the way a picture of the backside had a slot and a spec listing hat a pcie 4x slot, so have a closer look if its open back pcie and a 8x cards fits in you could also use a lsi sas controller to make use of the 4 pcie lanes (ahci controllers available would only use 2 lanes)

is that on by default? afair IOMMU would only be in effect when using passthrough devices or maybe SR-IOV, there would be no need for this for virtual devices in a vm there are no options in the kernel settings when compiling the driver so nothing that could be done beside documenting it in the tutorial? https://xpenology.com/forum/topic/13061-tutorial-install-dsm-62-on-esxi-67/ ( @luchuma)

you can rest the whole dsm config like as it was when starting the 1st time (2nd option in grub menu of the loader) or you mount the system partitions (raid1) and restore the files manually https://xpenology.com/forum/topic/7004-tutorial-how-to-access-dsms-data-system-partitions/ the default file are in the dsm *.pat file used for installing you can open it with 7zip, in there you open the hda1.tgz, hda1, and in there \etc.defaults\sysconfig\network-scripts\ ifcfg-eth0 to ifcfg-eth7

in theory that id belongs to logilink as long as the vid/pid is right and the device works ... it was booting and the data of the image ist just 50MB, even with a device that has lees the advertised capacity, the would be at least a few hundred MB, enough for out loader you could also tr to read the data from the device on an computer to test it what hardware and dsm type did you use?

i just looked into kernel source 4.13..12 and it looks like it was implemented the same as the e2400, just a device id and a special exclusion for a quirk if you are willing to test i can try to implement it just PM me if you have the board and you want to test a modded alx driver

only up to e2400 is supported right now, if there would be a patch for that e2500 for kernel 4.4.59 i could implement this (i have a e2400 patch for kernel 3.10.105 and e2400 has native support in kernel 4.4.59) yes, afaik that just a normal intel nic that would even work with the dsm default drivers as long as you can spare a pcie slot for a nic its no problem

with hyper-v v1 it was just a 100MBit tulip nic and with its v2 version MS even removed that and now there is only the synthetic nic that needs kernel support in linux (that we don't have)

there is no maintainer of the loader, its always the original as it came from jun as base, i tinker with the extra.lzma but for legal reasons i don't offer loaders

use this to fix it https://xpenology.com/forum/topic/28183-running-623-on-esxi-synoboot-is-broken-fix-available/

yes its used for every boot, its the same as the internal usb dom in original synology systems the data raid volume is independent from sytsem and swap that is on every disk, its not bound to the installation (at least nor to the base system, the packages you install need a volume and will stored there, including configuration of the packages) the vid/pid is just a circumvented security measure, a original usb dom has f400:f400 and is checked at least on installing SN or mac can be changed in grub.cfg after install, you could also copy that to a new usb as and use it as long as you match the usb vid/pid to the new usb's values the loader and installation of the system are more or less independent, one thing that can go wrong is when having the same mac on more then one system in network

not really, as the loader uses the original dsm kernel it depends whats on the kernel and hyper-v needs kernel options that the dsm kernel does not have (that cant be loaded as a module later) it runs fine with esxi, kvm or virtualbox presumably this makes fake pci devices available the protection in dsm is looking for if you do a lspci -k on a installed system you will see some "special" devices not using a driver btw. did you read the faq or tried to use the forum search about hyper-v? https://xpenology.com/forum/topic/9393-hardware-faq/?tab=comments#comment-82383 the one who made the "hack" (loader) did not make everything available, partly to not make it to easy for synology to get around the hack there where hints from jun about one or the other thing, you would need to read his posts to gather these things i'm not so sure that is going to work the old approach of loader for dsm 4/5 where based of a custom kernel, making some synology custom things available by revers engineering, jun's approach is less invasive and try's to make dsm not see that its not running on a non-synology hardware, on long term its less problems with updates i guess, you can just install the original updates in the webgui as you would on a original system the last thing i remember about building a new custom kernel was about thr missing source for synobios.ko, but i guess there might be more to adjust as dsm check for checksums when installing/booting for integrity and also is using driver signing (but might not force that atm) https://xpenology.com/forum/topic/27005-synology-sources-for-24922branch/?tab=comments#comment-170723 circumvent the protections is one thing but a custom kernel seems to be more difficult

https://xpenology.com/forum/topic/30552-transcoding-and-face-recognitionpeople-and-subjects-issue-fix-in-once/ https://xpenology.com/forum/topic/24864-transcoding-without-a-valid-serial-number/ https://xpenology.com/forum/topic/7573-tutorial-setup-a-ddns-in-dsm/ so you don't need quick connect and inflict damage to others or synology by using sn and mac of a real 918+ you don't own

if there is no specific controller you should see that its set in bios to ahci mode dsm wants every disk to be as a single disk and then make a software raid using mdadm there are limits on the controllers that can be used after loader 6.0 there where some drivers "lost" you can try to boot a live/rescue linux and check with "lspci -k" about the drivers to be used, if its sata_* or pata_* then its not going to work, it needs to be ahci maybe post what xou find with "lspci -k"

more specific - remove all partitions of the disks (you dont have to empty/overwrite the whole thing) also here, more specific, the vid/pid of the usb device you are using is key for installing, you can leave sn and ma as it is and change it later if you need it sn will only be used for specific packakes and mac is only mandatory when using WOL (but its convenient to have the same mac all the time for a system) disk size should be fine as long as dsm can install its system and swap partitions to it (2.4GB + 2GB) did you read the faq and tutorial? the wont we anything more on the screen, everything else is on a serial console, next thing you could "see" without that would be a new dhcp address to be used when the loader really starts and has a driver for the nic, i prefer to use synology assistant program from synology to find it in network, should also be available for mac this would be the base to read: https://xpenology.com/forum/forum/83-faq-start-here/ 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/

1.03b 3617, only unit supporting more then 8 cores atm https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ you might also start reading to faq as you dont seem to be aware of the limits imposed (we cant just choose a dsm type we want to install, its bound to the ones we have loaders for) https://xpenology.com/forum/forum/83-faq-start-here/ also important is the storage controller you have/choose, original p400/p410 are not a good choice as it they can#t make disk available as single raw disks like in a hba mode

after looking up the hardware in that unit (Atom D2550, Cedarview fom q1/2012) my 1st guess would have been that might not run with loader 1.04b 918+ as it needs 4th gen intel cpu as minimum, but if it boots and you find it in network then its working the unit comes with a serial port on its back, if you have a null model cable you could use a serial console (putty) on another computer to monitor the boot process, maybe you could see more that way about whats causing the problem

try the following things 1. use sysnology assistent (program) fo find and install and don asign a static ip address in the install process, just let it go with dhcp 2. try to use loader 1.02b to install dsm 6.1, we can try to update after this to 6.2 3. use another computer for installing to the disk and then transfer usb and disk to the system you want to use