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.
hey,
quick and dirty.
connect via terminal over ssh
...
became "root" permissions
sudo -i
list disks
fdisk -l
in this example, my source drive
Disk /dev/sdr: 931.5 GiB, ...
Device Boot Start End Sectors Size Id Type
/dev/sdr1 2048 4982527 4980480 2.4G fd Linux raid autodetect
/dev/sdr2 4982528 9176831 4194304 2G fd Linux raid autodetect
/dev/sdr3 9437184 1953320351 1943883168 926.9G fd Linux raid autodetect
look for an free md-slot and change "/dev/mdX"
mdadm -A --verbose --run /dev/mdX /dev/sdr3
message...
mdadm: looking for devices for /dev/md4
mdadm: /dev/sdr3 is identified as a member of /dev/md4, slot 0.
mdadm: added /dev/sdr3 to /dev/md4 as 0
mdadm: /dev/md4 has been started with 1 drive.
... ok, its fine
needed or not?
mdadm -Sf /dev/md4
mdadm -Asf && vgchange -ay
check for correctness
fdisk -l
message...
Disk /dev/md4: 926.9 GiB, ...
Disk /dev/md127: 2 GiB, ...
Disk /dev/md126: 2.4 GiB, ...
... ok
make a dir in useable range for "File Station"
mkdir /volume1/public/tmp
mount "/dev/mdX" with read-only permission
mount /dev/md4 /volume1/public/tmp -o ro
greets Sky
Итак, случилось. HW транс заработал на моей хрени 😂. Скачал новый биос 3.5, залил, настроил северный мост как на картинке, ребут, ничего больше не делал и вуаля - заветная папка /dev/dri c содержимым на месте, железный транс работает, как при перекодировке 4К, так и блюриков (запуск файлов *.m2ts), в plex тоже нормально.