mcdull

Turns out I lost every config and reconfig using tinycore redpill again, and the SN works flawlessly.

if I have a working config with latest dsm, why should I bother to do it again? I just tried update my version togehter with the loader. It was good with my 2nd latest DSM version.

I used it with tinycore loader for a long time. And both QC and Transcoding work. Now I messed up the DSM, and now force reinstalled and lost all settings. But still the serial number was report wrong and in DSM I cannot sign in my synology account.

Interestingly my working SN / MAC in tinycore redpill loader is being reported invalid under automated loader. How does it verify serial number?

Thanks for your information, but I have the same mac and sn when mirgating from a working DSM 7 of TinyCore RedPill Loader. I am also using Proxmox as well, should I start up another vm and put back all hdd?

May I have a quick question? is this loader blocking quickconnect or transcoding service? I have a valid serial number and mac under vm but cannot get either to work. with the TinyCore RedPill Loader I have no such issue. Thanks.

I have some issue after moving to ARPL. My usb hdd is now detected as internal drive, and I would like it to behave as normal. Any help or guide I can refer to? DSM7.1, with DS918+ image in a VM.

as a supplement, du -h -d1 | sort -h -r shows that it is also 4TB.

I have a basic volume on a VM running 918 image. it was a 10TB disk and were filled with 8TB, and after deleting files and the volume size still 8TB, and using file explorer to check the file size should be around 4TB. No recyclebin, no versioning. Any hint? Thanks.

I would like to remove volume2 originally serves as a backup volume with single basic disk. But tried in GUI, it prompt me for password, and then end with no messages. The volume is still there. Thanks alot for assistance 2022-08-23T11:28:27+08:00 XPE root[26422]: [/volume1/@database/synologan/alert.sqlite] is not on [/volume2], skip... [558036.488778] Synotify use 16384 event queue size 2022-08-23T11:28:27+08:00 XPE fileindeX[26437]: fileindex.cpp:763 (UpdateLogLocation) fileindex update log location 2022-08-23T11:28:27+08:00 XPE fileindeX[26437]: fileindex.cpp:767 (UpdateLogLocation) ignored volume: ["/volume2"] 2022-08-23T11:28:27+08:00 XPE fileindeX[26437]: fileindex.cpp:440 (PickDir) enum [volume1] 2022-08-23T11:28:27+08:00 XPE fileindeX[26437]: fileindex.cpp:440 (PickDir) enum [volume2] 2022-08-23T11:28:27+08:00 XPE fileindeX[26437]: fileindex.cpp:440 (PickDir) enum [volume3] 2022-08-23T11:28:27+08:00 XPE fileindeX[26437]: fileindex.cpp:770 (UpdateLogLocation) picked new log dir [/volume1/@SynoFinder-log] 2022-08-23T11:28:27+08:00 XPE fileindeX[26437]: fileindex.cpp:725 (MoveOldLogLocationLink) Old log dir link does not exist [/var/log/SynoFinder] 2022-08-23T11:28:27+08:00 XPE fileindeX[26437]: fileindex.cpp:525 (relocateTo) link exists [/var/packages/SynoFinder/var/log] -> [/volume1/@SynoFinder-log] 2022-08-23T11:28:27+08:00 XPE fileindeX[26444]: fileindex.cpp:786 (UpdateEtcLocation) fileindex update etc location 2022-08-23T11:28:27+08:00 XPE fileindeX[26444]: fileindex.cpp:790 (UpdateEtcLocation) ignored volume: ["/volume2"] 2022-08-23T11:28:27+08:00 XPE fileindeX[26444]: fileindex.cpp:440 (PickDir) enum [volume1] 2022-08-23T11:28:27+08:00 XPE fileindeX[26444]: fileindex.cpp:440 (PickDir) enum [volume2] 2022-08-23T11:28:27+08:00 XPE fileindeX[26444]: fileindex.cpp:440 (PickDir) enum [volume3] 2022-08-23T11:28:27+08:00 XPE fileindeX[26444]: fileindex.cpp:793 (UpdateEtcLocation) picked new etc dir [/volume1/@SynoFinder-etc-volume] 2022-08-23T11:28:27+08:00 XPE fileindeX[26444]: fileindex.cpp:525 (relocateTo) link exists [/var/packages/SynoFinder/etc/etc-volume] -> [/volume1/@SynoFinder-etc-volume] 2022-08-23T11:28:28+08:00 XPE root[26664]: [/volume1/@database/synologan/alert.sqlite] is not on [/volume2], skip... 2022-08-23T11:28:28+08:00 XPE synocheckshare[26650]: synocheckshare_vol_unmount.c:147 Unmount Share [INTERNAL] [/dev/mapper/cachedev_0] [/volume2] 2022-08-23T11:28:28+08:00 XPE syno-coredump-store.sh[26679]: Set coredump path to [/var/crash] 2022-08-23T11:28:29+08:00 XPE syno-coredump-store.sh[26872]: Set coredump path to [/volume1] 2022-08-23T11:28:30+08:00 XPE epck[26906]: vol_del_jnl_replay(2836) Start epck --vol-del-jnl-replay 2022-08-23T11:28:30+08:00 XPE epck[26906]: vol_del_jnl_replay(2884) Finish epck --vol-del-jnl-replay

Sorry. bad post. Got the answer. Thanks.

May I know except SS, what benefit it has to use DVA3221? I have an AMD + 1050Ti setup, and would like to see if it makes general application better than 1621+

Would like to ask a noob question on the AI model of DSM. Does it serves similar function of photo subject recognition as in earlier moment app in DSM6? Thanks.

I uses it with proxmox, AMD 3900x + Asrock X470 TaiChi I recommend to use xpenology always with hypervisor for best compatibility and minimum loss of performance.

after update and upgrade, 1621+ is working very fine. The only downside for me is lacking of valid SN/MAC.

I am having problem to build with v1000 Error starting from Also I saw ^M characters after each lines in many json files. Is it normal? Thanks.

so may I clarify tinycore supports 1621+ or 2422+ or not?

confirms it works on facial.

I suggest to wait to see how the new AMD p state driver works before deciding which system to pick.

DSM 7.0.1-42214 No issue on hyper backup. backup were on Google Drive

do u have vt-x enabled?

I think the bare minimal is a set of drivers keep up-to-date for virtualization on qmeu for basic functioning and immediate update-proof. Then the SAS / LSI driver for passthrough TI mode as most of us are running it for storage purpose. My concerns is the ability to catch up with the update from DSM version if a huge database of drivers needs to be maintained. Its not about feature, but security if we would like to use it in production environment. It would be quite scary to have a production system running with old version known to have serious exploit.

I guess we should open another thread for helping others to use the loader and to leave this thread for development needs. now this thread is flooding with operational issue.

if you say passthrough, it will be raw SATA disk. if you add lvm as qcow, it is not passthrough.

it should work if you only have a few and make rdm as SATA drives.