IG-88

cpu is to old for 918+ needs 4th gen, your cpu is 3rd gen, is documented here: https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/

vorsicht mit 6.2.3, da war grade jemand mit einem hp microserver gen7 der nach update auf 6.2.3 (vermutlich) kein netz mehr hatte

we have the kernel config from 918+ to check # # Processor type and features # CONFIG_ZONE_DMA=y CONFIG_SMP=y CONFIG_X86_FEATURE_NAMES=y # CONFIG_X86_FAST_FEATURE_TESTS is not set # CONFIG_X86_MPPARSE is not set CONFIG_RETPOLINE=y # CONFIG_X86_EXTENDED_PLATFORM is not set # CONFIG_X86_INTEL_LPSS is not set # CONFIG_X86_AMD_PLATFORM_DEVICE is not set # CONFIG_IOSF_MBI is not set CONFIG_X86_SUPPORTS_MEMORY_FAILURE=y # CONFIG_SCHED_OMIT_FRAME_POINTER is not set # CONFIG_HYPERVISOR_GUEST is not set CONFIG_NO_BOOTMEM=y # CONFIG_MK8 is not set # CONFIG_MPSC is not set # CONFIG_MCORE2 is not set CONFIG_MATOM=y # CONFIG_GENERIC_CPU is not set CONFIG_X86_INTERNODE_CACHE_SHIFT=6 CONFIG_X86_L1_CACHE_SHIFT=6 CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_X86_TSC=y CONFIG_X86_CMPXCHG64=y CONFIG_X86_CMOV=y CONFIG_X86_MINIMUM_CPU_FAMILY=64 CONFIG_X86_DEBUGCTLMSR=y CONFIG_PROCESSOR_SELECT=y CONFIG_CPU_SUP_INTEL=y # CONFIG_CPU_SUP_AMD is not set # CONFIG_CPU_SUP_CENTAUR is not set CONFIG_HPET_TIMER=y CONFIG_DMI=y # CONFIG_CALGARY_IOMMU is not set CONFIG_SWIOTLB=y CONFIG_IOMMU_HELPER=y # CONFIG_MAXSMP is not set CONFIG_NR_CPUS=8 # CONFIG_SCHED_SMT is not set CONFIG_SCHED_MC=y # CONFIG_PREEMPT_NONE is not set # CONFIG_PREEMPT_VOLUNTARY is not set CONFIG_PREEMPT=y CONFIG_PREEMPT_COUNT=y CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y # CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS is not set CONFIG_X86_MCE=y CONFIG_X86_MCE_INTEL=y # CONFIG_X86_MCE_AMD is not set CONFIG_X86_MCE_THRESHOLD=y CONFIG_X86_MCE_INJECT=m CONFIG_X86_THERMAL_VECTOR=y # CONFIG_VM86 is not set CONFIG_X86_VSYSCALL_EMULATION=y # CONFIG_I8K is not set # CONFIG_MICROCODE is not set CONFIG_X86_MSR=y CONFIG_X86_CPUID=y CONFIG_ARCH_PHYS_ADDR_T_64BIT=y CONFIG_ARCH_DMA_ADDR_T_64BIT=y CONFIG_X86_DIRECT_GBPAGES=y # CONFIG_NUMA is not set CONFIG_ARCH_SPARSEMEM_ENABLE=y CONFIG_ARCH_SPARSEMEM_DEFAULT=y CONFIG_ARCH_SELECT_MEMORY_MODEL=y CONFIG_ARCH_PROC_KCORE_TEXT=y CONFIG_ILLEGAL_POINTER_VALUE=0xdead000000000000 CONFIG_SELECT_MEMORY_MODEL=y CONFIG_SPARSEMEM_MANUAL=y CONFIG_SPARSEMEM=y CONFIG_HAVE_MEMORY_PRESENT=y CONFIG_SPARSEMEM_EXTREME=y CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y CONFIG_SPARSEMEM_ALLOC_MEM_MAP_TOGETHER=y CONFIG_SPARSEMEM_VMEMMAP=y CONFIG_HAVE_MEMBLOCK=y CONFIG_HAVE_MEMBLOCK_NODE_MAP=y CONFIG_ARCH_DISCARD_MEMBLOCK=y # CONFIG_HAVE_BOOTMEM_INFO_NODE is not set # CONFIG_MEMORY_HOTPLUG is not set CONFIG_SPLIT_PTLOCK_CPUS=4 CONFIG_ARCH_ENABLE_SPLIT_PMD_PTLOCK=y CONFIG_COMPACTION=y CONFIG_MIGRATION=y CONFIG_PHYS_ADDR_T_64BIT=y CONFIG_ZONE_DMA_FLAG=1 CONFIG_BOUNCE=y CONFIG_VIRT_TO_BUS=y CONFIG_MMU_NOTIFIER=y CONFIG_KSM=y CONFIG_DEFAULT_MMAP_MIN_ADDR=65536 CONFIG_ARCH_SUPPORTS_MEMORY_FAILURE=y # CONFIG_MEMORY_FAILURE is not set # CONFIG_TRANSPARENT_HUGEPAGE is not set # CONFIG_CLEANCACHE is not set # CONFIG_FRONTSWAP is not set # CONFIG_CMA is not set # CONFIG_ZPOOL is not set # CONFIG_ZBUD is not set CONFIG_ZSMALLOC=y # CONFIG_PGTABLE_MAPPING is not set # CONFIG_ZSMALLOC_STAT is not set CONFIG_GENERIC_EARLY_IOREMAP=y CONFIG_ARCH_SUPPORTS_DEFERRED_STRUCT_PAGE_INIT=y # CONFIG_IDLE_PAGE_TRACKING is not set CONFIG_FRAME_VECTOR=y # CONFIG_X86_PMEM_LEGACY is not set # CONFIG_X86_CHECK_BIOS_CORRUPTION is not set CONFIG_X86_RESERVE_LOW=64 CONFIG_MTRR=y # CONFIG_MTRR_SANITIZER is not set # CONFIG_X86_PAT is not set CONFIG_ARCH_RANDOM=y CONFIG_X86_SMAP=y # CONFIG_X86_INTEL_MPX is not set CONFIG_EFI=y # CONFIG_EFI_STUB is not set # CONFIG_SECCOMP is not set # CONFIG_HZ_100 is not set # CONFIG_HZ_250 is not set # CONFIG_HZ_300 is not set CONFIG_HZ_1000=y CONFIG_HZ=1000 CONFIG_SCHED_HRTICK=y CONFIG_KEXEC=y CONFIG_CRASH_DUMP=y # CONFIG_KEXEC_JUMP is not set CONFIG_PHYSICAL_START=0x100000 CONFIG_RELOCATABLE=y # CONFIG_RANDOMIZE_BASE is not set CONFIG_PHYSICAL_ALIGN=0x1000000 CONFIG_HOTPLUG_CPU=y # CONFIG_BOOTPARAM_HOTPLUG_CPU0 is not set # CONFIG_DEBUG_HOTPLUG_CPU0 is not set # CONFIG_COMPAT_VDSO is not set # CONFIG_LEGACY_VSYSCALL_NATIVE is not set CONFIG_LEGACY_VSYSCALL_EMULATE=y # CONFIG_LEGACY_VSYSCALL_NONE is not set # CONFIG_CMDLINE_BOOL is not set # CONFIG_MODIFY_LDT_SYSCALL is not set CONFIG_HAVE_LIVEPATCH=y CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y

did you use a serial port as console or are you just guessing as it did not show up in network? i still have a test hardware with a 1G broadcom nic so i might be able to test it @hardware transcoding users i had a quick glance at the i915 driver from 6.2.3, it is from 22.12.2017, newer then the one in 6.2.2 (19.09.2016) but slightly older then the i915 created by jun for loader 1.04b (14.05.2018) there are firmware references to "glk_dmc_ver1_04.bin" so it should support gemini lake there are some already people that dont have transcoding support after update without digging in i think the reason will be missing firmware, 918+ original image does not contain all i915 firmware files, just the one needed for apollo lake (bxt), it also contains glk firmware that indicates that gemini lake should work ootb without any additional extra.lzma changes so people with "normal" gen4-9 cpu's should be fine with a updated extra/extra2 "syno" that would contain additional i915 firmware files for people who cant wait firmware files referenced in new 6.2.3 i915 driver: bxt_dmc_ver1_07.bin bxt_guc_ver9_29.bin bxt_huc_ver01_07_1398.bin cnl_dmc_ver1_06.bin glk_dmc_ver1_04.bin kbl_dmc_ver1_04.bin kbl_guc_ver9_39.bin kbl_huc_ver02_00_1810.bin skl_dmc_ver1_27.bin skl_guc_ver9_33.bin skl_huc_ver01_07_1398.bin firmware download from here: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915 copy files in dsm to \usr\lib\firmware\i915\

from memory i thought it would be enough to change the synoinfo.conf in /etc.defaults and then reboot to see the change in /etc/synoinfo.conf too so it you do the change for both it should work

can you read the image from your working 3617 and the 918+ loader with "Win32DiskImager 1.0" with activ "read only allocated partitions", apload it somewhere (tinyupload is easy) and pm me the links? the conrolle config from dmesg is 4+6 ahci ports and 8 from sas, so its sda to sdr and 18 ports sdu and sdv are the usb drive and a virtual cd/floppy - so they dont count as dsm drives can you disable the 6port ahci controller in bios? 4+8 would a good combination

its not just wd, seagate does that too, they tried to hide the recording type and when you looked closer they invented n new name (tgmr) for it and you had to dig much deep to read that its just smr with some cmr as buffer, afair it was seagate barracuda at 1st (but these are desktop drives by the spec not nas drives) BUT they also sell Iron Wolf drives (nas) with "tgmr" so they are in the same boat as wd and there are a lot nas users in the last two years with such slow drives(?) https://www.seagate.com/www-content/product-content/ironwolf/en-us/docs/100807039b.pdf edit: seagate's TGMR stands for "Tunneling Giant Magneto-Resistive" and thechnology for the read/write of the head (used in the hdd for each plate) it seems it can be used for PMR and SMR so it depends on the hdd modell and how its pre formated and its firmware (PMR only or SMR with PMR zones as cache) the key word for seagate to look for might be "MTC Technology" or "Multi-Tier Caching Technology" on the barracuda webpage this tech is explicitly named for 2.5" drives (higher density for recording then 3.5") and "normal" barracuda drives https://www.seagate.com/internal-hard-drives/hdd/barracuda/ (lower section with 5 types of barracuda compared) "Multi-Tier Caching Technology" itself includes SMR as the lowest tech/tier as shown here https://www.seagate.com/files/www-content/product-content/barracuda-fam/barracuda-new/files/multi-tier-caching-technology-white-paper-2017.pdf the product manual for the ST4000DM004 does not mention it but it IS a SMR drive so its hard to guess what drives uses SMR for a 4TB drive it might be 2 plates / 4 heads for SMR and 3 plates / 6 heads for PMR drives barracuda pro drives might not use smr but as there is no indication of how to determine it can be changed at any time by seagate the only safe way to determine seem to flood all "caches" by hammering the drive with ~20% of its capacity and have a eagle eye on the data rate, if it plummets significantly below 100MB/s for some time or stops responding for some time (flushing the pmr cache to smr) it must me a smr drive seagate actually stated that there is no SMR used in iron wolf drives its also a good idea to look into the official compatibility chart for DSM from synology (example 918+ for 4TB seagate drives) https://www.synology.com/en-global/compatibility?search_by=products&model=DS918%2B&category=hdds_no_ssd_trim&filter_brand=Seagate&filter_size=4TB&p=1 no ST4000DM004 (2plates/4heads) there but ST4000DM005 (3plates/6heads) is ok also iron wolf ST4000VN008 (3plates/6heads) is there

use Win32DiskImager 1.0 and activate "read only allocated partitions" (you presumably used it already to write the image, you can use it to read to a image file too) you would only need to backup after dsm updates

from lspi its the C610 chipset ahci with 4+2 ports and a sas3108 controller (8 ports) 0000:00:11.4 Class 0104: Device 8086:8d66 (rev 05) Subsystem: Device 1028:0601 Kernel driver in use: ahci -> C610/X99 series chipset SATA Controller [RAID mode] 0000:00:1f.2 Class 0104: Device 8086:8d06 (rev 05) Subsystem: Device 1028:0601 Kernel driver in use: ahci -> C610/X99 series chipset SATA Controller [RAID mode] 0000:02:00.0 Class 0104: Device 1000:005d (rev 02) Subsystem: Device 1028:1f49 Kernel driver in use: megaraid_sas -> MegaRAID SAS-3 3108 [Invader] aka PERC H730 Mini RAID Controller 1 the drive list might indicate you have used 3 x sata and 8 sas ports /dev/sdi - /dev/sdk /dev/sdl /dev/sdm /dev/sdn /dev/sdo /dev/sdp /dev/sdq /dev/sdr - - /dev/sdu /dev/sdv strange is the "missing" sda to sdh, thats 8 ports so the layout for dsm looks like this 8 ??? 2 ahci 8 sas3108 4 ahci these 8 ports shift most of the drives into the >12 area, no idea where they come from nut even without these leading 8 ports you would be above 12 ports with 2 +8+4 = 14 and you would be needing to find a way to place the two last drives in a way that they would be /dev/sds and /dev/sdt can you send me a copy of /var/log/dmesg ? there might be a clue to see why 8 ports are skipped did you try loader 1.04b again? if that would be used then you could change the drive count in the patch og the loader to 24 and make the drive number persistent for updates if you want to go the way of modding the /etc.defaults/synoinfo.conf then you would have to change it like this (and reboot after changing it) original: maxdisks="12" esataportcfg="0xff000" internalportcfg="0xfff" usbportcfg="0x300000" new: maxdisks="24" internalportcfg="0xffffff" esataportcfg="0x0" usbportcfg="0x3000000"

for ??? reasons most of the drives are above the 12 drive limit and wont be shown (might be visible as external drives) what controllers are in this system (onboard and as pcie card) any sas extenders? how are the disks connected (what controller) please do some information gathering lspci -k ls /dev/sd* quick and easy might be to raise the allowed disk amount to 24 but that will be gone after a bigger update (full ~250MB pat file) better to locate the problem and solve it otherwise, so so funny if you raid breaks after such a update from above it should be solved by tweaking the the loader, bios or hardware itself

the limit is the default from synology and its 12 drives for 3615/17

sure? SAS3408 is dev id 00af https://pci-ids.ucw.cz/read/PC/1000 and that supported with the driver in the 0.5 extra.lzma for dsm 6.2.2 3617, mpt3sas.ko (not with 3615 or 918+) only sas38xx/39xx is not supported (at least when it comes to the device list from the driver

i know this one, with all this corona trouble my delivery if way off schedule pcie is usually backward compatible, i'd expect it to work in a pcie 2.0 slot

würde es reichen wenn der loader nicht mit dhcp sondern mit einer bestimmten ip adresse startet? jun patcht bei start einige systemdateien, rein theoretisch könnte man ja auch versuchen die config datei für das netzwerk zu patchen um eine bestimmte statische ip zu haben \etc\sysconfig\network-scripts\ifcfg-eth0 dazu müsste man die extra.lzma auspacken, den patch mit diff erzeugen und an die jun.patch anfügen, danach die extra wieder einpacken und in das loader image kopieren

thats boot problems, you initial description was about a error when already installing dsm (and it was not the typical error 13 when vid/pid is wrong) maybe there could be other problems like having 2 dhcp servers in network and nic getting a new address from the 2nd? also possible if there are more then one dsm system in network and two having the same mac will also result into problems in situations like this its helpful to have the serial console, you might see if drivers fail or you can see what ip address the system uses and you can also login to have a closer look https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/?do=findComment&comment=140359

you loose network support while iinstalling my assumption would be you used the loader in its original state with its "old" extra/extra2.lzma and the old zImage and rd.gz (6.2.0) when installing 6.2.2 your zImage and rd.gz is from kernel 6.2.2 and you drivers fail because of the changes in 6.2.2 make sure to copy new extra/extra2 and new zImage/rd.gz before you start to install (as in the description in the 1st post)

the uneven number is usually a warning, dsm/xpenology does not support port multiplier only "real" sata ports but from the specs it does look like a real 5 port controller AND it has PCIe 3.0, even with its 2 lanes it should be more capable than one of the usual 4port marvell chips 88SE92xx (1.000 GB/s vs 1.969 GB/s per lane) https://www.jmicron.com/file/download/996/JMB585.pdf its ahci so it will work ootb

yes, synology published recent source so we can try newer drivers, i guess in e few days you can try i cant test lsi 9400, has it IT firmware?

kannst du evtl. ein fertiges image (platte) einspielen? dann würdest du alles vorbereiten und dann das fertig installierte image einspielen, da wäre die ip adresse dann auf dem stand den du brauchst oder wenn du meherre vm's in kvm habe kannst dann ein normales linux mit dhcp server und dann dsm in eine andere vm installieren

there is a special section "Loader Releases & Extras" why not just look there? https://xpenology.com/forum/topic/7848-links-to-loaders/ not sure what your hardware is (just can'd find my crystal ball) but i guess dsm 6.0 should be working for most cases

thats sandy bridge, 3rd gen intel 1.04b needs at least 4th gen haswell cpu's try 1.03b for 3615 or 3617 - > !!! this will need CSM/BIOS and also look for non uefi boot usb device (depending on bios you might see two uefi and one dsm usb device) https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ if you already read the install tutorial you should also read what might be needed when you want to update to the latest 6.2.2 version https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/

if someone hack it the too afaik gemini lake works with 6.2.0 and jun's drivers from 1.04b the fact that its not working with 6.2.2 indicates that it might be as simple as recompiling the driver for 6.2.2, so the "smallest" solution might be if jun still have the i915 source he used for 1.04b and drop it somewhere

no, as jun left no source code to recompile the driver we would need to have someone backporting i915 driver to synology's DSM 6.2.2 kernel (4.4.59) https://01.org/linuxgraphics https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/24922branch/apollolake-source/linux-4.4.x.txz/download

mal als beispiel https://www.vmwareblog.org/nested-virtualization-vmware-esxi-vs-microsoft-hyper-v/ https://docs.fedoraproject.org/en-US/quick-docs/using-nested-virtualization-in-kvm/

look closer to the nameing, its just 2 disks The NVMe naming standard describes: nvme0: first registered device's device controller nvme0n1: first registered device's first namespace nvme0n1p1: first registered device's first namespace's first partition dev/nvme0n1 3QLUS7RSFP174FJTPDR5 INTENSO -> nvme0, your 1st disk /dev/nvme1n1 OWNUZUMYDV8D9WHNPMAA INTENSO -> nvme1, your 2nd disk /dev/nvme1n1p1 OWNUZUMYDV8D9WHNPMAA INTENSO -> nvme1, still your 2nd disk but "p1" tells you its the 1st partition on that disk