DerMoeJoe

ive tested it.. on esxi after converting the vmdk its not bootable. within vmware workstation it is booting. but within the tinycorelinux ive got a couple of problems.. ssh is not installed and enabled. after installing openssh and enabling/starting it this works. next problem is that the scripts arent executeable after transfering them with chmod +x rploader.sh this is done. but unable to start them after, cause the env variables for starting bash scripts isnt setup properly.. after doing this i only got a lot of warnings within the rploader.sh script in a couple of lines... tested with the acutally newest verision from the repo (9days old v0.4.4)

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3 update 2 - Loader version and model: Jun's v1.04b - DS918+ - Using custom extra.lzma: No - Installation type: BareMetal | ASRock B250M Pro4 | i5-6400T | Intel X520-QDA1 | 4x WD Red 3TB & 2x 128GB Intenso NVME - Additional comments: before upgrade removed NVME Cache, after Upgrade recreated the Cache. All Fine including the 10G NIC

Intel x520 and the other Variants works with Stock. Gesendet von meinem Mi A3 mit Tapatalk

But the read only cache still works with the new Update. Gesendet von meinem Mi A3 mit Tapatalk

Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 - Loader version and model: JUN'S LOADER v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: BareMetal | ASRock B250M Pro4 | i5-6400T | Intel X520-QDA1 | 4x WD Red 3TB & 2x 128GB Intenso NVME - Additional comments: all fine

yes, the stick must stay in the NAS... so u can use any old 256mb usb stick for the loader...

The Boot Stick must be placed on the Board. The Boot Stick is Not o ly for the install of xpenology. Its also the Boot Stick for the Software! Gesendet von meinem Mi A3 mit Tapatalk

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25423 - Loader version and model: Jun's v1.04 - DS918+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASRock B250M Pro4 | i5-6400T | Intel x520 | 2x 120GB NVME - Additional comment : removed the NMVE Cache before Upgrade, Installd PAT Manualy, after 2 reboots and aprox. 5 minutes System was UP again. recreate the NVME Cache. 10G Nic works fine as always (without any additional drivers).

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

@The Chief @flyride thanks for your help. with the modded libary file it works again (y) important is, that the libary must be placed as u said within the /lib64/ on my first test ive searched for the original file and found it on /usr/lib/ and replaced this file, but after this the WEB GUI wasnt working. probably this is a good option to point the libary with the path in the STARTER Post. (or make another bookmarked topic or something for this)

@The Chief thanks for your work, but the new nvme patch doesnt works for me with 6.2.3. ive relpaced the old patch, modified the rights with chmod, started the script and rebooted the NAS, but im unable to see the nvme drives within the storrage manager.

Before the Upgrade to 6.2.3 i removed the Cache (aß always Before an Update). After the Update u still cann See the Hardware With console. But running the Script and performing a reboot wouldnt help until now to get the Cache up again.

Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922 Update 6 - Loader version and model: Jun's Loader v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - (ASRock B250M Pro4 | i5-6400T | Intel X520-DA1 | 4x WD Red 3TB, 2x Intenso NVME 120GB) - Additional comments: Reboot required by the update. But the Nvme Cache doesnt works after the Update!

Update: after restart the script for enabling the nvme cache and make a full reboot i was able again to setup the nvme cache with the 2 drives.

short update... ive swapped the 2 nvme ssds ports... and now i've got the following.. root@FSK-NAS:~# nvme list Node SN Model Namespace Usage Format FW Rev ---------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- -------- /dev/nvme0n1 3QLUS7RSFP174FJTPDR5 INTENSO 1 128.04 GB / 128.04 GB 512 B + 0 B R1115A0 /dev/nvme1n1 OWNUZUMYDV8D9WHNPMAA INTENSO 1 128.04 GB / 128.04 GB 512 B + 0 B R1115A0 /dev/nvme1n1p1 OWNUZUMYDV8D9WHNPMAA INTENSO 1 128.04 GB / 128.04 GB 512 B + 0 B R1115A0 root@FSK-NAS:~# does someone got any idea why i can see now 3 nvme disks within the SHELL ? and on the GUI again only 1 is usable.