Leaderboard

Patience, Yes there is a way ! And the work is being done by @pocopico with @jumkey 's help. I'm working on a ncurses interface with pocopico, maybe ... in a few weeks !

most simple solution might be that the cmos battery is down and when the power was lost also the cmos values where reset (usually you get a message about that when booting up after that) N54L is a AMD system and needs C1E disabled in bios, if that is on again it will prevent the loader from starting the DSM system https://xpenology.com/forum/topic/7973-tutorial-installmigrate-dsm-52-to-61x-juns-loader/ "... Note: Jun's loader supports Intel CPUs. For AMD CPUs Jun has stated that the loader needs some work but it has been reported by many users using HP machines that it actually works. The C1E function in the bios (in some HP machines) needs to be deactivated. I am unsure for other motherboards brands therefore if you have an AMD machine that is not an HP you might be out of luck. Try looking in the bios configuration and play around. ..." anyway, dont worry about your data, even if the loader is not working (like usb flash driver damaged, that is easy to repair) when dsm comes up and you see that the raid is damaged/offline that would be more of a concern even if you cant get DSM up and runnning and want access to your data you can prepare a media (disk/usb) with OMV and boot from that media, its still my fallback https://xpenology.com/forum/topic/42793-hp-gen8-dsm-623-25426-update-3-failed/?do=findComment&comment=200475

looks like synology still has to work in the protection before 7.1 comes out of beta ;-)))

7.1 test success.

It has been explain multiple times already. SataPortMap define the number of ports each SATA controller contains. set on 1 digit. 58 means : First SATA controller has 5 ports (5 pluggable SATA disks), Second SATA controller has 8 ports (8 pluggable SATA disks) DiskIdxMap define the starting position of disk mapping for each controller, set on 2 digits. 00 = /dev/sda 01 = /dev/sdb etc... so 0A00 means : - First 2 digits are 0A : is the 11th position : /dev/sdk - 2nd 2 digits are 00 : it is the first potition : /dev/sda So first controller disks will start from sdk to sdo and 2nd controller disk will start from sda to sdh Depending on how many SATA controller you have on your motherboard (are they all on motherboard, or do you have a PCI-card, or nmve... etc...) the number can be different from one to another configuration. Whereas on ESXi you define the SATA controller numbers (like SATA0:0 for loader, and SATA1:x for DATA disks) usually using the above settings, you are able to set SataPortMap = 18 and DiskIdxMap to something like 1000 As you only have the loader set on SATA0 you can have first digit set to only 1, where 2nd number will be 8 to be able to have 8 (virtual or RDM) disks plugged on SATA controller 1.

it does not come with a i915 driver ootb so it's a not for intel quick sync based hardware transcoding (iGPU), it will transcode based on cpu if there is not support for intel quick sync, depending on the material and cpu it can be challenging to transcode one 4k movie based on cpu power - its often possible to just stream in source quality and let the client device handle it, as the client device only has to decode and resize (no encoding as on the server) and it usually has hardware based decoding its often no problem to just stream in source quality the only thing where transcoding on the server might be needed is when there is a bandwidth limit between server and client (wifi or powerline in some home environment or when accessing dsm over the internet and having "slower" upload rates to the internet from dsm over a asymetric broadband connection) but it might be possible to compile a i915 driver and add it - problem might be that there could be something missing in synology's kernel we use as base (protection of dsm and missing source to build own kernel) with 3.10 kernel on 3615/17 on 6.2.3 it was not possible to use i915 driver from kernel 3.10 but maybe it does now with kernel 4.4, i plan to try this later when i have a few things up and running

Hi all, A while ago I've started experimenting with a solution that would not require docker and/or a system running linux, but just a simple image that you can boot on your physical/virtual system and create the loader from there. I started with the plain disk image of 200MB size and tried to fit all in this image. As always first partition of the image is the synoboot1, second synoboot2 and third one (synoboot3) is tinycore. Tinycore is a simple linux distribution that can boot to a GUI so you can start creating the loader. Most network modules are included so you can verify also the extensions required on your system. A script will take care most of the actions that you would manually perform and just copy the loader contents to the 1st and 2nd partition. The loader is created from a pre-compiled redpill extension (should work) or you can compile it yourself (still testing). You can bring over and use the rp-helper configuration files so you dont have to do that again. To connect using ssh you will need first to reset the tc user password by typing # passwd tc The image can be found here: https://github.com/pocopico/tinycore-redpill Before starting the loader creation just run # ./rploader.sh update now and answer y I would appreciate any findings to improve the image.

I would like ask if Asrock H170M-ITX/ac motherboard with Dual LAN : Intel I219V and Realtek RTL8111H works with Xpenology. I want use both LANs for LACP. Is it possible? Has anybody use it in that configuration? Thanks H170M-ITXac

i made some kind of documentation in 2020 in the tutorials section to keep it here in the forum because external links will vanish contains synologys explanations from older kernel source https://xpenology.com/forum/topic/32867-sata-and-sas-config-commands-in-grubcfg-and-what-they-do/

its possible to have nvidia drivers the way a DVAxxxx has it but afaik no one tried if it would be usable in videostation or survailancestation without "tweaking", there might be some specialty's like serial number check for nvidia support in general there does not seem to be a special version of videostation or survailancestation for DVA's there is just the x64 version so i would assume nvidia support is build in atm thats only available for 6.2 https://xpenology.com/forum/topic/22272-nvidia-runtime-library/ using it in plex/emby/jellyfin and docker should be possible, main problem was ffmpeg with nvidia support but that was solved lately it would be the drivers (*.ko) and the matching NVIDIA Runtime Library from synology https://archive.synology.com/download/Package/NVIDIARuntimeLibrary

Thanks for this, first time I see it...

i already compiled a i915 driver for 918+ having all gpu id's in it up to 12th gen (as long as it still is UHD xxx) not tried it yet on my skylake test system and i can't on 10th or up as i dont have that (my main system is just coffee lake and that works ootb with 918+ default driver) the main problem would be if the driver halt's the system on loading (as seen with some systems on 6.2.3 and the patched driver), then you will need to remove the new i915.ko in some way, its its done the dump and easy way as i suggested in the 6.2.3 thread you would have to test that on a non productive environment and just kill it if it goes wrong (can be a productive hardware if you just use a new usb and a empty disk) or you would need to access it as if you would do a recovery like booting up a recue linux assemble the raid1 (system) with mdadm, access the system partition and delete the i915.ko it would need to be a plugin in @pocopico's tinycore that could be added manually by command and if it does not work it could be removed from the loader the same way it was added, in that case it should be reversible edit: i also made a diff patch file that i can provide so anyone could build that driver (its not best practice to just provide a binary), i will also provide patches for smaller things i did to 3.10 and 4.4 source to add some missing hardware (mvsas and killer E2400/E2500 in atheros)

About transcoding in Plex, in dsm 7.-1 918+ is not working at the moment on newer intel cpu's (my is 10 gen). I've tried different methods using plex forums (docker and native Plex media sever together workaround on original Synology) with no success. Maybe IG-88 will find solution modifying i915 from previous dsm.

I figured it out after 5 edits and reboots... DiskIdMap=01 SataPortMap=02 Thanks again

i always like to start with SataPortMap=58 and DiskIdxMap=0800 and evaluate results accordingly

Not exactly. I build a 6.2.4 fresh install DS3615xs. I had also a fresh built 7.0.1 DS3622xs+ confirmed as running (just to be sure all settings was OK (sata etc...) I stopped both VMs, I deleted 16GB virtual disk (SATA 1:0) from DS3622xs+ and added/replaced with the 16GB virtual disk from 6.2.4 VM At boot I was "ready to migrate" I gave the 7.0.1 pat file to launch migration, it rebooted as usual, done.

Hi all, there is an update for tinycore redpill and version has been shifted to version 0.4.5. Both vmdk and raw boot images have been updated as well. Some fixes have been implemented and the platform DS3622xs+ is integrated. - Serial number generation for DS3622xs+ - Module / extension detection is now separated to version 3 and version 4 kernels to avoid conflicting module identification. - EFI boot should work - Static redpill module for DS3622xs+ has been created and the extension is updated - Module extensions have been created for DS3622xs+ but still need some testing. You can test and let me know.

Yes, i've updated rploader and i have tested a successful creation. You can test as well and let me know

Almost there. I need a bit of time for the extensions. The load/unload loop is being taken care off also.