Jump to content
XPEnology Community

mcdull

Member
 View Profile  See their activity

  • Posts

    252

  • Joined

  • Last visited

  • Days Won

    4

 Content Type 

Posts posted by mcdull

    Automated RedPill Loader (ARPL)

    in Loaders

    Posted

    2 hours ago, Dreadnought said:

    I have a valid SN for DS3622xs+ too which is offically working within the synology account but ARPL is complaining that this SN is invalid too. 

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

    Automated RedPill Loader (ARPL)

    in Loaders

    Posted

    1 minute ago, Rick4 said:

    Can you used that serial with same latesd dsm, or older only? 

    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.  

    Automated RedPill Loader (ARPL)

    in Loaders

    Posted

    9 minutes ago, Rick4 said:

    You generated that within ARPL, or use it before somewhere? 

    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.

     

    Automated RedPill Loader (ARPL)

    in Loaders

    Posted

    On 10/14/2022 at 9:56 PM, kociubin said:

     

    FWIW, I also have a real serial and mac.  I'm able to use quickconnect just fine.  My goal was to get email notifications working.  I intially started out with an auto-generated serial number/mac.  This was on a working system.  I then changed the SN/MAC to a real one.  But no matter what I tried notifications just wouldn't work.  So I started over and recreated my NAS using a real SN/MAC, re-imported settings and only then notifications started to work.  I'm running ProxMox so this was pretty easy to do.

     

    It might be worth a shot.  I think you need a real SN/MAC configured in the loader when the DSM boots up for the first time.  This was certainly needed in my case to get notifications working.

    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?

    Unable to remove volume

    in General Questions

    Posted

    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

     

    TinyCore RedPill Loader (TCRP)

    in Loaders

    Posted

    I am having problem to build with v1000

     

    Error starting from 

    Quote

    NO NVME disks found, returning
    Converting dts file : ds1621p.dts to dtb file : >ds1621p.dtb
    ./rploader.sh: line 803: dtb extension is not loaded and its required for DSM to find disks on ds1621p_42218: command not found
    Copy of the DTB file ds1621p.dtb to  was not succesfull.
    Please remember to replace the dtb extension model file ...
    execute manually : cp ds1621p.dtb  and re-run
     

     

    Also I saw ^M characters after each lines in many json files. Is it normal?

     

    Thanks.

    RedPill - the new loader for 6.2.4 - Discussion

    in Developer Discussion Room

    Posted · Edited by mcdull

    On 11/18/2021 at 11:37 PM, WiteWulf said:

    Nice, and an interesting write up of how they did it (using IDA Pro), too.

     

    Be sure to read the full article if you consider using this:

    - it probably won't survive a DSM update

    - it probably won't survive a Photos app update

    - use DS3615xs if keeping Face Detection is important to you

    confirms it works on facial.

     

    Redpill - extension driver/modules request

    in Developer Discussion Room

    Posted

    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.

×
×
  • Create New...