Leaderboard

you would just do the same as using the 2nd boot option in the 6.2 loader, a fresh install of dsm and keeping your raid as it is so its less effort to "keep" 6.2.2 and just do the install without knocking out your raid - thats a usual option on original systems too, when the dsm system is wonky for some reason or does not come up after a systemupdate you can put the loader (internal usb on original units) in fresh install mode and you can choose to install just the system (dsm) and keep your data or to a complete new install knocking out you "old" raid/data (wizard in web gui when booting up 2nd boot loader option) https://global.download.synology.com/download/Document/Software/UserGuide/Firmware/DSM/6.2/enu/Syno_UsersGuide_NAServer_enu.pdf page 25 dsm is a custom linux appliance that handles some things there own way, if you want do find out whats wrong with your upgrade attempt it can take some time, on the more you change you might make things less predictable or might come into tha same situation after a bigger uddate (like 6.2.2, full 200-300MB dsm *.pat file) whre the whole system partition is overwritten and only config data are reapplied) the efficient way (imho) is a fresh install and redo the shares/permissions in the gui and reinstall the plugins

Apart from the kernel version that changes from DSM 6.1 (3.10.102) to 6.2 (3.10.105), does syno included new protection ? The issue with 6.2 when loading drivers/modules that crash, does it crash because of protection or "just" because these modules are not build with latest GPL released ? I've been offline from long long time but I discovered that Syno released GPL sources for DSM 6.1-15047 (kernel 3.10.102) in september 2017 and no one tried to build it's own kernel from there. I am very suprised 😮 since there are loader that fool the protection, the only missing part is a working kernel that we can custom.