mojojojotroi

What model did you choose? I'm afraid the i5-2320 is a bit too old for any model... 😕

Several choices you did could lower your chances to have the DSM booting: - DS923+ is designed for AMD Ryzen R1600 - i915 driver (is for the iGPU not related to the NIC) to my knowledge the fork from 9th gen. driver is maximum for Intel Core 10th gen., so don't expect to exploit the UHD Graphics 770 (and as Synology most probably won't release anything for Gen. 11, 12, etc... as they go now with AMD). So forget about any transcoding, except with a Plex Pass subscription - Your onboard NIC is Realtek RTL8125BG, not the best chipset in the 2,5Gb/s world, but at least it works on DS918+

Sorry, I haven't this kind of stuff in my hands. I guess, if HP lets users change this kind of parameters, the naming are a bit different...

Did you tried Rick4's trick below?

Sure it's a annoying options in the loader and/or bios. For example, my old MSI B460I won't boot correctly and stable over the time when DS920+ model is chosen. Why DS918+ it's way more smooth, but I have to be careful with real S/N, MAC, modules, etc... It's a bit long to isolate what is interfering. Please details full specs of your hardware, loader version, settings chosen, otherwise it's difficult to guide you.

When you have this behaviour, it's probably bad setting(s) / option(s) chosen in the loader that conflict for DS model chosen, and this will bug / kernel panic the DSM (so you it won't boot and you can't acces it). Also ensure you didn't modify some BIOS settings, some are very important. Good luck !

Totally agreed. USE WITH EXTREME CAUTION AT YOUR OWN RISK ! If you have the skills and technical resources, put your NAS in an isolated network behind a proxy and a level 7 (OSI model = application) firewall that can do Deep Packet Inspection to see if there is something suspicious, and unusual open ports, because the downloaded file could include a trojan/backdoor integrated in the loader system, repackaged in a disk image and zipped again. So it's totally pointless to use regular AV scan on the .IMG file

I had no experience with AMD based systems, but I know there are more issues, so at least choose only the Synology models based on AMD CPU, you will have better luck 😉

Sorry, I did a mistake. I mean "I got success with... DS918+, ...", no good results with DS920+ Did you tried another models? Like DS3622xs+, DVA1622, ...?

Same here, use another loader like ARC, TCRP, … in my case I got success with 10th Gen CPU, DS920+ for several weeks : i5-10500T on MSI B460I with the abandoned ARPL-i18n 23.10.4 with the latest DSM. But since I tried to reboot to do a Memtest with the Synology Assistant, DSM won’t boot anymore. Will try also to go with another more stable loader.

Development of this loader have stopped, so you must go to another one under development like : TCRP, ARC, …

Realtek NIC are nightmares since begenning. On my case, the R8125B on the MSI B460I doesn't let DSM boot when plateform is DS920+, but OK with DS918+ (apparently with a screen plugged). Seems ARPL-i18n more stable in my case than ARC. Will have to test also TCRP when possible. But as there are designed a bit differently, and so many settings and parameters to cross-test, it's a bit hard to isolate and identify the troublemaker.

I'm devastated... How the community can help you @wjz304 ?

Hope my last discover will help some of you: My NAS based on MSI B460I motherboard (see my signature for more details) won't (re)boot sometimes because it has to have a screen plugged on HDMI (will try soon with a dummy dongle and share to you the results)

Outcome of the update: SUCCESSFUL DSM version prior update: DSM 7.2-69057 update-1 Loader version and model: ARPL-i18n v23.10.4 on Lexar V400 32GB / DS918+ Installation type: BAREMETAL - Intel i5-10500T on MSI B460I with 2x8GB DDR4 3200MHz Kingston FURY ; R8125 ; 4x WD180EDGZ ; 2x SA2000M8/1000G (as R/W cache) Additional comments: Manual update from control panel Bootloader not updated Real SN/@MAC I discovered why my NAS won't (re)boot sometimes: It has to have a screen plugged on HDMI (will try a dummy dongle)

https://www.synology.com/en-global/releaseNote/DSM

What's going on when trying to swap your SSD on other ports ?

You are right, you need to upgrade ARPL-i18n (now called RR) at least in this version https://github.com/wjz304/rr/releases/tag/23.9.6 (according to release notes) before upgrading to the DSM version you mention. By security, I suggest you to browse and note in a safe place every current boot loader settings in every menu before doing the update, in place or flashing a second boot device (USB stick, SATA DOM, what else, ...) By the way, I suggest to do the same for BIOS settings, modern motherboards offer in general some slot in memory to save settings profiles. Easy for testings and saving you lots of time 'cause it could be a real pain in the *ss to find the exact settings to make DSM boots successfully ! Good luck !

Thanks for the great advices @Peter Suh, I'll go for SATA M.2 or DOM if the 2 USB 3 sticks I just get won't do the job properly.

Unfortunately, not the right topic thread to discuss that. You will find the way of SSD (SATA or NVMe) cache works in the different NAS models directly in Synology online documentation (or YouTube demonstrations)

This enclosure (https://fr.aliexpress.com/item/1005003996419437.html) doesn't support eSATA, only USB 3.1 interface max 10Gb/s. Cable type C on enclosure side, type A on computer end. But the chipset RTL9210B supports PCIE NVMe & SATA NGFF, M.2 slot can accept B+M Key notch, making it quite universal, that's why I chosen it. In fact, that was a bad idea (at least with this paticular AliE model I bought, maybe a bad luck): I encountered several problems : read only mode, overheat, instability (disconnections), speed bandwith variations, that's with I tried to flash it with several firmware versions. Maybe the problem isn't software, but simply physical (for example: bad solderings, bad cable and no spare cable to cross-test, ...) who knows... I wasn't using this enclosure as storage device, you misunderstood. As recognized as external device, I used it as USB bootloader, and at my first thoughts (before discovering the several issues) the most reliable as NVMe are more enduring than pendrives.

I also encountered several times the missing zImage-dsm file from the /mnt/sd#3/ partition, but personally mostly with the ARC fork. And at this time my tests were only based on Intel SSDPEKKF256G8 NVMe drive in a cheap AliExpress USB3 enclosure with a shitty RTL9210B chipset that put the drive in read only mode sometimes… Already tried to flash this chipset with different firmware revisions, sadly without enhancement seen… So loader cannot been correctly built when this occurs. Problem easily visible under Windows, but not so much when on the loader. Will try another USB3 flash drives, SanDisk and Lexar, and also TCRP Friends/MShell. And also encountered several times the empty command line issue, at boots or even when making choices at loader build step. Guys, I want to thank you all for the great and hard work your produce since years. Cheers ! 🥰

I have the same behaviour with the same chipset on my MSI B460-I, seems no way to disable it, so no better when adding a Intel I350-T2 on the free PCI-E slot... Hoping good luck to you with this sh*t

What's your motherboard model ? Network chipset ? (Realtek 8125B, Intel I219-V, I215-V, ...) ? Did you tick the checkbox to load the corresponding driver when configuring the loader ?

What is the behaviour when booting on something else ? (Live CD, Linux/Windows install boot USB ?)