IG-88

where do you have problems with the installation, beside the added notes you follow the tutorial https://xpenology.com/forum/topic/7973-tutorial-installmigrate-dsm-52-to-61x-juns-loader/ you can try to user loader 1.03b 3615 or 3617 and install dsm 6.2.3 the steps are the same as in the tutorial for 6.1 your cpu is old but 64bit capable if you have at least 2GB ram (i guess 4GB is standard) it should work i have not seen a spec that lists the network chip but most used 1Gbit cips are supported

der satz ist ein wiederspruch in sich, auf dem stick ist eben nur der loader und nicht DSM, das kann man nur auf eine platte ausfpielen aber nicht auf den usb und die netzwerk config ist auf den platten als raid1 über alle disks (jeweils erste partition auf den disks), wenn du den loader auf default zurücksetzt dann ist auf dem loader plötzlich dsm 6.2.0 (dessen kernel) und auf den platten ist dsm 6.2.3 da will er dann eigentlich "nur" den loader reparieren indem er die neuen kernel files auf den loader packt (2. partition des loaders da wo auch die extra.lzma liegt) beim migrieren gibt es aber eigentlich auch die option die alten einstellungen nicht zu übernehmen, das wäre wie factory reset und sollte auch die netzwerkeinstellungen zurücksetzen außerdem hat der loader beim booten (grub menü) 3 optionen, drück ein paar mal die cursor tasten beim boot so das das grub menü stehen bleibt und ließ den 2. punkt, den kann man auch zum zurücksetzen benutzen andere optionen wie mit einer frisch bespielten platte werden hier behandelt https://xpenology.com/forum/topic/12778-tutorial-how-to-downgrade-from-62-to-61-recovering-a-bricked-system/ wird schwierig ohne netzwerk aber wenn man einen com1 hat und ein null-modem kabel ginge es denn man kann sich auch über die serielle console anmelden alternativ kannst du ein live/rescue linux booten, das raid1 manuell starten/mounten and die netzwerk config dann manuell in /etc zurücksertzen (ist leichter wenn man sich de default einfach mal bei einer frischen installtion ansieht oder sich die files aud dem 200-300MB vollen dsm *.pat file exttrahiert, öffnen geht mit 7zip und in dem pat dann das hda1 file öffnen) https://xpenology.com/forum/topic/7004-tutorial-how-to-access-dsms-data-system-partitions/

then if you have not already, read this for transcoding in videostation (plex with plexpass should not need this) https://xpenology.com/forum/topic/24864-transcoding-without-a-valid-serial-number/ https://xpenology.com/forum/topic/30552-transcoding-and-face-recognitionpeople-and-subjects-issue-fix-in-once/

no, that card is a r8168, check its pci id and you will fing out anyway there are drivers for r8168 aka 8111 and r8169 present the list in the older threads for 6.2 are still valid https://xpenology.com/forum/topic/12859-driver-extension-jun-103a2dsm62x-for-ds918/ can't help much with that, still try to use 918+ 1.04b, it can handle uefi and your cpu might be supported afaik it does as long as its in IT mode (usually a different firmware to flash from the default) also read the 1st post about the problems realted to this hardwre and disk hibernation check your /var/log/dmesg for information about the driver (mpt3sas) loading

no kernel driver, so it can't work wit any software ??? maybe try this, there are cases where its not just in esxi environment, afaik it it will not make anything worse on a baremetal system, i tried it at least once to see if it would interfere on a baremetal and it had no negative effect https://xpenology.com/forum/topic/28183-running-623-on-esxi-synoboot-is-broken-fix-available/

its a uefi bios but 1.03b does not support this it needs csm mode active and you need to boot from the non uefi usb boot device (that might only be seen after rebotting once with csm active) maybe read this https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ i guess the cpu might also work with 918+ loader (that can boot uefi), try 1.04b 918+ 1st not the nic driver for sure also the extra.lzma for 6.2.2 will not work properly, with dsm 6.2.3 its jun's original or the one made for 6.2.3 as i never had a card to test the hpsa.ko driver i can's say much any driver from external source for supporting newer sa's did not work and i dont know if the driver in kernel 3.10.105 will know that hba mode you could try to use iLO virtual com port to connect to an com1 and see with putty what you get, on 1st boot you should see what happens when hpsa.ko is loaded and how it reacts to the hardware i might have a p410 next month and thats the 1st driver that works with hpsa.ko, maybe i will be able to test the driver later to see if it at least starts (1st original kernel driver, if that does it then a newer driver from external source might be a test) easiest way aroud that would be a lsi sas conttroller like 9211-8i in IT mode (can be bought <100€), it comes with sas to connect to the hp backplanes sure it would be nice to use the p420 but its not even clear it it ever will work, maybe the newer driver from kernel 4.4.59 / 918+ might do the trick but thats not possible for you, gen8 cpu's are one ivy bridge and to old for 918+ , 4th gen hasswell is min. for 918+ if i have time next month and the p410 works better then expected (tried it in a skylake hp desktop at work and it went boot loop from bios - not a good sign but might be different in another hardware) i guess a 9211-8i or something cheap with sas2008 chip (lots of oem's also from HPE) will do the job and i also would suggest to use 3617 (supports more cpu cores and has newer lsi sas drivers ootb from synology)

might be interesting to know what the problem was if anyone else hast the same problem as you already wrote, its unusual that the system disk gets filled with something

kein extra treiber, die karte ist ahci (wie die onboard sata anschlüsse) und ahci ist fest im dsm kernel drin die einzige besonderheit der asm1166 karte die ich zum testen gekauft hatte war das sie hinten den 4 bz.w 6 onboard sata's 32 anschlüsse für dsm hatte von denen nur 6 wirklich da waren aber so lange man da nichts dahinter (6+6) haben will ist das erstmal kein problem, im live system habe ich eine jmb585 karte ("nur" 5 sata ports) und eine 2 oder 4 port marvell karte (von der ich nur einen port nutze) aber das die asm1166 mit dsm keine zusätzliche platte anzeigt ist eigenartig kannst du mir mal die /var/log/dmesg schicke? wenn die karte funktioniert sollte man zumindest im log was von der platte sehen, auch wenn dsm sie aus irgendwelchen grüden nicht anzeigt (z.b. wenn sie sdq oder höher wäre (>16 disks würde 918+ nicht in der gui anzeigen) du kannst auch mal testweise ein live linux strten uns sehen wie das die disk erkennt (sdX)

recent security updates, beside this its maybe check synology's publications about new features from 6.1 to 6.2

never seen a unit IRl but that looks like a common server hardware https://www.itpro.co.uk/640606/nimble-storage-cs240-review/page/0/2 "... Nimble opted for Supermicro's 6036ST-6LR Storage Bridge Bay platform. ... Motherboard: Supermicro X8DTS-F CPU: 2GHz Xeon E5504 Memory: 12GB DDR3 RAID controller: Supermicro AOM SAS2-L8 ..." the build seems to pretty non standard the controller is a good old lsi sas2008 chip based most people have here if its a sas controller and there is no limit with disk size the thing not to have is lsi SAS1068/1078 these have a 2.2TB hardware limit so older nimble versions might be a hands off if they used these older sas1xxx chips beside this you would need to check the hardware for storage before buying, dsm does nor have support for every storage controller, the only universal is the ahci support

as nimble was bought by HPE in spring 2017 it might be safe to say everything without a HPE sticker will be max. 4th gen and safe to use

no i just used a search engine to find that in a few minutes, this time you may try it yourself only thing i also found out is that later versions use a m.2 module instead of usb to boot

at least there is a pcie device present or the driver would not start is the card working in baremetal with dsm or with a normal linux (lboot a live linux instead of dsm) either the card is not working properly or the paththrough

https://xpenology.com/forum/topic/24273-login-fault-you-cannot-login-to-the-system-because-the-disk-space-is-full-currentli/ if you cant login with telnet/ssh you couls still boot a recovery linux assemble and mount /dev/md0 (system parttion raid1 over all disks) and look/clean that way https://xpenology.com/forum/topic/7004-tutorial-how-to-access-dsms-data-system-partitions/

you need to extend the script to recognize 6.2.3, the patches seem to work with u3 too beside the patch you would need my extra/extra2 for 6.2.3 to get i915 driver working, the driver in jun's original extra/extra2 will prevent the i915 from dsm 6.2.3 to work properly, my newer 6.2.3 extra/extra2 removes jun's i915 and makes properly way to make dsm's own (improved) i915 work (check /var/log/dmesg if i915 driver is loaded properly or check that devices in /dev/dri are present https://xpenology.com/forum/topic/30552-transcoding-and-face-recognitionpeople-and-subjects-issue-fix-in-once/ https://raw.githubusercontent.com/Jlozde/xpenology-6.2.3-easyfix/master/patch.sh ["1d01ee38211f21c67a4311f90315568b3fa530e6"]="6.2.1-23824-0_6.2.3-25426-2" -> ["1d01ee38211f21c67a4311f90315568b3fa530e6"]="6.2.1-23824-0_6.2.3-25426-3" and "6.2.3 25426-1" "6.2.3 25426-2" ) -> "6.2.3 25426-1" "6.2.3 25426-2" "6.2.3 25426-3" )

i found this (an as dsm relies on usb boot ....) "... All previous generaitons before Gen5 arrays ship with the USBs in the controllers. They have the bootloader loaded on them. We do not have FRU or parts for the NimbleOS USBs. ---"

maybe just try loader 1.04b as it comes without any changes or newer extra.lzma the basic boot and network operations are working without any changes, the usb vid/pid would only be important when trying to install dsm to a disk but atm you are failing even the 1st step of finding it in network, if you get this part working then you can start things like usb vid/pid and mac an grub.cfg beside synology assistant you can check your dhcp server for activity aka new addresses

neither amd cou or chipset are general problems, ryzen cpu's should work with 918+ (no gpu support for transcoding) beside the cpu' min. requirements (and csm mode when it comes to 3615/17 with loader 1.03b) https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ the key is storage and network driver with onboard ahci usually storage in no problem (ahci mode, not raid mode in bios) depending on the onboard nic it can be a problem, intel 2.5 Gbit has no driver at all and the newer realtek 2.5Gbit can be a problem depending on the revision as the driver in the extra.lzma might be to old (the latest extra from the additional driver section should be used) but when adding a "older" nic i should work Intel Gigabit CT Desktop Adapter or realtek 8168 based cards are common with 918+ the 2 nic limit is to keep in mind, when adding a 2 or 4 port nic all ports should be checked

as the 918+ only supports 2 lan ports ootb you would need to test with all 4 ports of the nic to make sure you get to a workring port the i350 should work as its not nearly as new as 2.5Gbit nic's (cant say anything about t8125 with out the pci vid/pid and its sub id's)

i don't run esxi but i'd expect it so be a passthrough problem as the driver is basic driver set of the loader there is a dedicated section for installing on virtual you have a different problem then the topic implies try to open a new thread in https://xpenology.com/forum/forum/50-dsm-6x/

this thread is about dsm 6.2.3 and you should read about the problems with lsi sas controllers with 918+ in the 1st post of this thread you should be able to update to 6.2.3 and use 0.12.1 or 0.13.3 extra/extra2 if using 0.12.1 you should disable disk hibernation

https://xpenology.com/forum/announcement/2-dsm-serial-number-must-read/ https://xpenology.com/forum/topic/9392-general-faq/?do=findComment&comment=82390 https://xpenology.com/forum/topic/24864-transcoding-without-a-valid-serial-number/ https://xpenology.com/forum/topic/30552-transcoding-and-face-recognitionpeople-and-subjects-issue-fix-in-once/

and my point is that one controller is in IT mode and the other is not on "older" (depends on generation/cip of the controller) there is a IR (raid) and IT firmware for the same chip/controller IT is for initiator target and in this mode every single disk is presented to the os as a single disk as for IR the single disks will not be seen and only raids defined from the disks will be seen on OS level DSM relies on single disks and build mdadm software raid (mdadm) sets and alongside monitors the single disks (s.m.a.r.t.) there are newer chips and firmware where you dont have to flash a new IT firmware to the controller to change the mode, i don't know when avago/broadcom started it you controller Lsi 9285CV-8e seems to be in raid mode as it refers to virtual drives in the screenshot you provided if you go int the controller bios you should se a "IR" somewhere in the upper area as reference to raid mode and in the other controller there should be "IT" in the same place so look for a IT firmware and if that does not exist there might be a way to switch the controller to a way presenting disks just as simple devices https://geeksunlimitedinc.wordpress.com/2017/02/16/flashing-lsi-hba-to-it-mode-or-ir-mode/

its not about nvme, its about storage technology and cache strategy's your link https://www.anandtech.com/show/13512/the-crucial-p1-1tb-ssd-review/7 shows very clear how terrible such qlc base dirves can be if the cache is the only thing it relies on its pretty much like with cmr disks and thencintruducing smr, parts of the smr disk (5%?) user cmr and are used as extended cache, when the cache is full and there are still data hammering the drive then it fallls back to its native speed and for smr thats pretty low, and the same goes for QLC cells, the write speed is verry low, that works ok for a typical desktop use but especially as cache drive its really not a good choice NOT the bottleneck? if you have 9.9GBit of 10GBit then its maxed out already you dont have to, afaik dsm does use ram as cache as long as its not used for other things or is reserved that get important if you measure performance just by copying files, you need to know the pipeline to interpret the results

what does that has to to with a new loader for dsm 7.0? maybe write a letter to synology if you wish to see more hardware from amd used, we more or less are bound to what the dsm kernel of the loader we have can do we have not seen any news or development for a custom kernel after dsm 5.x where we would have control over features supported by the kernel