IG-88

2 things 1. https://xpenology.com/forum/topic/9392-general-faq/?do=findComment&comment=82391 https://xpenology.com/forum/topic/13030-dsm-5x6x-cpu-name-cores-infomation-change-tool/ so its just cosmetics 2. https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ (6 core) 12threads is ober the max of 8 in 918+, so effectively you only use 4 core 8 thread, thats about 5 real core performance, if you disable HT in bios it could be 6 core if you dont need 918+ (nvme, intel qsv hardware transcoding) you can use 3617 instead to use the whole cpu performance, 3617 is up to 16 threads if you dont give information about mobo and ram you can't expect much of a answer why 2x16GB is not working, in general if its not shown in bios you can't expect it to work in the OS for one when just having a 1 GBit nic and saturating it with restore its not to expect to have a good response, and if you just created a raid5/6 and the system is still building it it will also decrease the performance (look what the storage pool and volume shows) quick connect is not supported in a hacked version of dsm (aka xpenology) as it would need a valid combination of mac and SN of a system of the same type, the defaults in grub.cfg are not valid and even if might be blacklisted already use other ways (ddns, vpn) https://xpenology.com/forum/announcement/2-dsm-serial-number-must-read/ https://xpenology.com/forum/topic/7573-tutorial-setup-a-ddns-in-dsm/

even with a driver, it seems likely DSM will not recognize it as drive for data or cache i's say install vmware, use dsm as vm and make the fusionio drive(s) a virtual ssd for the vm

yes that would be next to try if that fails you could use a rescue linux, mount the raid1 system partitions (1st on every diks) and format that /dev/md0 (check if it contains the system before doing that, not so good to format you data volume) https://xpenology.com/forum/topic/7004-tutorial-how-to-access-dsms-data-system-partitions/ with the system partiton empty it should be possible to make a reinstall without deleting data on your data volume if you want access to you data you could boot open media vault (a nas system) from a different source (like usd) and access you data over network and backup if you want), its also possible to use a rescue linux and mount the raid1 data volume (-> tutorial section)

no difference when it comes to signal and how the system see's the drive, its just a sata drive that is not entirely correct, the 1.03b loader cant boot in uefi mode so it will at least be: it does not seem to boot or it stops qt xx% with error yy if you remove - from your point of view - non relevant information, it will be harder to track down problems, its just a example to show its better to present raw data if possible (like whole log files or the recorded outcome for all scenarios) if its 1.04b/918+ does not boot then there is something wrong as the 4th gen cpu in you nuc should be able to boot 1.04b/918+ you could also try to update the working 6.1 to 6.2 though the webgui, you would start 6.1, remove the old usb with the 6.1 loader and put in the prepared 6.2 loader and then start the update process, that way the 6.2 loader is in place (will be mounted in the update process) and gets the new kernel files, reboot should work and you can see if the outcome is better that way another method can be to install on a different system and then transfer disk and usb to the system that had problems (difficult in your case as mSATA we be hard to find in most households, some older notebook might have this one or you need some special adapter to connect it to normal sata) if you wand to get creative to try that you could install 6.2 on a normal sata disk on the other system and then connect that drive with a usb adapter to the nuc, boot a rescue linux and use dd copy the first 5GB from the sata drive (usb connected) to the mSATA drive (dsm creates 2 partitions at the start of the disk one for system and one swap) how? intel spec shows only one internal drive supported and usb drives can't be used for installing also make sure the drive you try to install to has no partitions from other installs or attempts), there can be problems with that (not i most cases bur as you have problems try to clean up by booting a rescue linux and delete the partitions)

not thought about that before but as i already modded jun's patch for deleting the old i915 drivers i could also add one line to remove the old /.xpenoboot might prevent it for some people and even if you have the problem you would just need to copy the extra.lzma to the loader and boot, nothing else would be needed

as its a 3rd gent intel cpu you can't use 918+ (that would need 4th gen min.) as its uefi bios and you will have to use loader 1.03b you need to enable CSM mode, restart once with csm active and then select the non-uefi usb boot device (there are usually 2x uefi usb and one without uefi in its name), check bios sata to be set to ahci, nic should be no problem, its the usual realtek

never heard of that, the only thing that comes to mind is related to 5.x (no problems with 6.1) and coming to 6.2, but usually the whole webgui does not start if thats the case but it does not hurt to check https://xpenology.com/forum/topic/26723-network-down-after-dsm-login/?do=findComment&comment=137953 did you install update3 to 6.2.3? if not do so maybe related to smb v1, check if the other dsm has smb v3 enabled

there is a "VERSION" file in /etc and /etc.defauls replace the content or the whole file with the one from 6.2.3 *.pat file (use 7zip, you will need to go into hda1.tgz) (just to make sure, you did reset the kernel files on the loader?) majorversion="6" minorversion="2" productversion="6.2.3" buildphase="GM" buildnumber="25426" smallfixnumber="0" builddate="2020/05/12" buildtime="06:07:06"

https://wrgms.com/synologys-secret-telnet-password/ You've probably tried telneting to your NAS. Maybe you've even tried opening the case and hacking the serial port, only to discover that you don't have the root password. The DS Assistant password doesn't work, and you exhausted all obvious guesses - blank, synopass, synology, password, admin, root, etc. ... Bonus tip: if you're curious how exactly the password is generated, here's the gist: 1st character = month in hexadecimal, lower case (1=Jan, ... , a=Oct, b=Nov, c=Dec) 2-3 = month in decimal, zero padded and starting in 1 (01, 02, 03, ..., 11, 12) 4 = dash 5-6 = day of the month in hex (01, 02 .., 0A, .., 1F) 7-8 = greatest common divisor between month and day, zero padded. This is always a number between 01 and 12. So, let's say today is October 15, the password would be: a10-0f05 (a = month in hex, 10 = month in dec, 0f = day in hex, 05 = greatest divisor between 10 and 15).

i already used core2duo and quad cpu's for DSM but it needs to be ahci (sata), some might not offer that in bios, its safer to go with a 1155 min requirements for cpu can be seen here https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/

if its booting on the R430 you could switch it off and then use a rescue linux to mount the system partition and then extract /var/log/dmesg, we would be able to see what driver is loaded just to make sure - you dont use the same loader (same mac addrerss in grub.cfg) more then once in you network? check you dhcp server (internet router?) for info's about ip and mac

no its not, thats from jun's 1.03b 3617 grub.cfg set vid=0x058f set pid=0x6387 some people forget the "0x...", swap vid and pid or its can by a typo also used lower case myself yes, just grub and kernel files and some drivers maybe you should start reading the FAQ https://xpenology.com/forum/topic/9392-general-faq/?do=findComment&comment=86731 https://xpenology.com/forum/topic/9394-installation-faq/?do=findComment&comment=81096 if its a synology nas then maybe, if not then its a 100% no (if you want to do that you might have a look into open media vault) yes, the system and swap take 4.4GB (see faq) and on the remaining part you could create a basic volume (no redundancy), but having a 10GB volume will not help much with anything and as its so small its presumably a older ssd so the performance is mediocre at best (and it cant be used as cache drive, that type need to be a exclusive drive and with just one drive it would only be usable as read cache and in most home use cases thats not very useful)

what makes you think it does not work? any log? as long as its in ahci mode it should work

thats supposed to work, jun's extra.lzma already has a driver for this nic, might be other reasons, if possible you can add nic, install that way and then check /var/log/dmesg for the atl1c driver (thats the one used for ar8151) check the bios, sata need to be in ahci mode, you can also boot a live/rescue linux and check with "lspci -k" what drivers are used if its "ata_piix" then its not in ahci mode

se the other thread where you posted about your 95% problem

in some cases it is possible to install on a different system and after installing take disk and usb flash drive to the other system that did not install

this thread might be interesting for you https://xpenology.com/forum/topic/41065-ds1010-internal-usb-bootloader-repair-dsm-upgrade-to-6/?do=findComment&comment=195019 especially this one is for 1511+, contains a boot image plus explanation on how to patch for your serial and mac's (you might use google translate or similar) https://xpenology.com/forum/topic/9787-восстановление-загрузочной-флешки-на-ds1511/?do=findComment&comment=90382

you can try to use loader 1.02b and my extra.lzma for 6.1, the isci driver is also in that one, maybe there is a problem with the driver in 6.2.3 if dmesg can't be used then there is still the serial console (null modem cable), you would see when the driver is loaded and a kernel panic is produced maybe just forget about the isci and add a controller (4-6 port ahci or lsi sas for 8 ports)

dsm 6.2 does support ACMEv2 but you could also try this https://workit.kz/synology-dsm-6-1-xpenology-lets-encrypt-acmev1-to-acmev2/ more recent security updates if you dont miss anything, you microserver is not going to work much better in its basic tasks afair also the older amd version run with 6.2 (3615/17) you could check here for reports https://xpenology.com/forum/forum/78-dsm-updates-reporting/

i already answered this https://xpenology.com/forum/topic/28321-driver-extension-jun-103b104b-for-dsm623-for-918-3615xs-3617xs/?do=findComment&comment=198248 it does, this whole thread is about 6.2.3, not any other older version, there are other threads with dsm version numbers like this one specific for 6.2.2 https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/ i did that: its a complex matter and synology has no intentions to make it smooth for us as already stated, its not a tutorial or step by step how to, you could also read 1st posts of the threads for loader 1.03b/1.04b to get a better picture, on long term its better to understand why its working or not

if using jun's loader with its 6.2.0 kernel then it would imply the driver is not working with 6.2.3 as when installing the kernel of 6.2.3 gets copied to the loader and on next boot it's kernel 6.2.3 with the driver (extra.lzma), but the thing is the driver is made for 6.2.3, it might work with 6.2.0 but should work with 6.2.3 it would be possible to see that in dmesg if 6..2.3 starts and r8125 is just used as additional 2nd nic

my suggestion would have been to install with the onboard nic and after dsm is running checking the r8125 its much easier to look for problems in a running system by checking /var/log/dmesg the alternative might be a serial console and some system dont have a com port anymore and its also more difficult to do adding changing driver can be easy, copy newer extra.lzma to the loader, boot and you are done if dsm/xpenology is to cumbersome maybe try open media vault, dsm is a closed appliance, omv is a real linux based on a major distribution no, the whole thread and even the topic is about 6.2.3, there is a extra thread for 6.2.2 and in the 1st post in this 6.2.3 thread i tried to explain the difference and that its not meant to be used wit 6.2.2, when you update from 6.2.2 to 6.2.3 you will need new drivers as the 6.2.2 drivers are incompatible and the drivers (added drivers) are in the extra.lzma i refer to the 6.2.2 as of reading it and that's about the procedure when updating or how to handle the files in general its not a howto or tutorial more grown and pieces added, no, might even be harder as 1.03b needs csm mode in uefi bios and also legacy/non-uefi usb boot device https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ sure, the extra.lzma's from the 1st post have r8125 drivers, not the latest but at least most of the r8125 cards will work and some people use r8125 cards

the mac address that is double is in your grub.cfg its best to change both as to prevent that happening again, no good to knock out a running server that way afaik the mac of the virtulbox vm hardware needs to be the same as in the grub.cfg so you mifgt use the vm's mac in enter that in the grub.cfg

me too, you dont give much detail about your hardware, what cpu/systemboard, any additional controllers? is the r8125 a added 2nd nic or onboard? try using synology assistant and check the versions of loader recoverable can be a mismatch of installed dsm and loader, like having 6.2.3 on disk and bootig with a vanilla loader from jun's image that contains the kernel of 6.2.0 letting dsm fix it does result in a bootable system - but maybe your state is different if you see 6.2.4 with assistant then start from scratch, copy img of the loader again and remove partitions from disk for what reason you put a diffrent dsm 6.2.2 on the loader? it sure does not work as the drivers for 6.2.2 and 6.2.3 are different just stick to the versions in this thread, if you want to copy a kernel to the loader then use a matching 6.2.3 files

kann durchaus ein das es mit anderen platten läuft, egal wie es ausgeht es wird dir keine neuen erkenntnisse bringen die erkenntnis ist das es auch bei sata schlechte kabel gibt und das kabel auch schlecht ausgesteckt sein können