Jump to content
XPEnology Community

pipsen

Member
 View Profile  See their activity

  • Posts

    33

  • Joined

  • Last visited

 Content Type 

Posts posted by pipsen

    Synology DSM 7.2 Beta

    in Readers News & Rumours

    Posted

    Did anybody already test the new feature with volume encryption and external kmip-server?

    I tested this deployment (https://github.com/rnurgaliyev/kmip-server-dsm) with Synology's first beta 7.2 and it was working like a charm.

     

    No I installed 7.2 RC (7.2-64551) and kmip-server on a raspberry pi and I have following behaviour:

    • kmip server deployment working
    • paring with kmip client working
    • enabling kmip server in global settings
    • => successful connected, all status green

    But after reboot, I get critical warning that volume could not be decrypted, while kmip server still shows green / connected.
    When I try to manual initiate the decrypt, I have to upload the recovery key.

    I had a look into kmip-server's logfile:

    • when I initially connect => only positive log results
    • when I try "check connection" => only positive log results
    • but after reboot of Synology client: no log file entry,.. just nothing

    Seems that Synology has a bug in the RC firmware version, that no request is sent to kmip-server?
    When using local key vault, the automatic decryption is working. Can somebody confirm this maybe? Do you have the same problem?

    Synology DSM 7.2 Beta

    in Readers News & Rumours

    Posted

    On 4/26/2023 at 2:20 PM, smilenkovski said:

    @wjz304

    I saw that You have recent updates on github, are You preparing for RC 7.2?

    RC 7.2 is already working with wjz304's build for some days.

     

    I've got another question: Did anybody succeed to manually build a img-file based on a git clone of fbelavenuto/arpl and pocopico/tinycore-redpill ?

    Obviously, both have already implemented RC7.2 but not yet released yet.

     

    If yes: Could you maybe give a detailed description incl. build environment, how you succeeded?

    Thank you!

    Synology DSM 7.2 Beta

    in Readers News & Rumours

    Posted

    @wjz304 

    Since today, Version  7.2-64551 is out. This is the official release candidate bei Synology. Could you maybe update your arpl-i18n project for this build? This would be so awesome :)

     

    I hope that "official" arpl and/or tcrp will update their loaders as well for DSM 7.2 

    Proxmox: best practice decisions for best performance

    in DSM 7.x

    Posted · Edited by pipsen

    Hi,

     

    currently I have DSM 7.1 installed via ARPL on a BAREMETAL HP ProDesk 600 G4 (Intel I5-8500, 16GB RAM).

    My Harddisk setup is:

    • 256 GB SATA SSD: Volume 1 for packages and docker container's appdata
    • 8 TB SATA HDD: Volume 2 for file storage

    Currently I can read and write and with 113 MB/sec via Gigabit Ethernet continously on both volumes.

     

    • Problem: Everytime a little risky, when DSM updates appear, whether bootloader and installation survives.
    • Idea: Using Proxmox Hypervisor to have snapshot capabilities before each update - just in case.

     

    I have now a few topics to discuss, which decisions make sense:

     

    Host file system

    What would you recommend? ZFS? ext4? These two seem to be most popular.

    https://lowendspirit.com/discussion/2786/poll-which-type-of-filesystem-you-prefer-on-proxmox-host-node

    Any suggestions in terms of Xpenology?

     

    Passthrough vs. virtual disks

    I have read here in some threads, that passing through harddisks would be best idea in terms of best performance.

    Question: I assume, that I will lose the main benefit with my snapshots, right?

    I mean, the bootloader disk can be snap-shot, but I have seen, that on each used HDD and SSD, the DSM installs two partitions with OS.

    II case of a bricked DSM after update, I restore an old snapshot before update, the bootloader is downgraded, but the passthrough HDD is unaffected and I have a version mismatch

    => DSM will automatically upgrade the bootloader to have same version => bricked again.

     

    Any Ideas, how to get bet the benefits of both worlds?

     

    Passthrough of NVMe cache

    I have an unused M.2 slot, where I could integrate a NVMe SSD as Cache device. This can be passed-through as well, as I have seen.

    Question: If I decided to have SSD and HDD as virtual disks (for snapshots), is it still possible to passthrough an NVMe SSD to attach als Cache-SSD?

     

    Virtual Disk parameters

    I case I decide for virtual disks: How to configure the parameters to have maximum write performance without running into write cache problems:

    • VirtIO SCSI
    • Bus: SATA (some say SCSI?)
    • Cache: none (some say write back?)
    • DSM write cache setting: activated?
    • Model VirtIO (some say others?)
    • SSD emulation for SSD Disk on?

     

    Problem: With my test installation witht he parameters above, I have the effect, when I copy a 20GB file, I have 113 MB/sec for the first seconds until about 5 GB, and then the write speed decreases to around 70 MB/sec. With cache settings "Write back", the effect was even worse.

     

    Encryption

    I would like to have my whole personal data encrypted. What would you recommend (in terms of performance):

    • Encryption on Host Level? If yes: Whats the best idea?
    • Encryption on DSM Level: Enrypt each Btrfs share?

     

    Synology Model

    For my setup here, I assume DS-920+ should be the best one, correct?

     

    Anything else?

    Anything else what you have in mind, which is very important to have maximum performance?

    Thank you!

     

    Thank you very much in advance for you tips and input and the discussion!

     

    DSM 7.1.1-42962

    in DSM Updates Reporting

    Posted

    - Outcome of the update: SUCCESSFUL
    - DSM version prior update: DSM 7.1.0-42661 Update 4
    - Loader version and model: Automated Redpill Loader 0.4 alpha 5 DS918+
    - Using custom extra.lzma: NO
    - Installation type: VMWare Workstation

    - Additional comments: Migration from tcrp to arpl necessary

    DSM 7.1.1-42962

    in DSM Updates Reporting

    Posted · Edited by pipsen

    DSM-7.1.1-42962-ReleaseNote.jpg

     

    https://www.synology.com/en-global/releaseNote/DSM

     

    Spoiler

    Version: 7.1.1-42962
    (2022-09-05)


    Important Notes

    • Starting from this version, the bad sector count column will not be displayed along with hard drive information. Users should go to each drive's Health Info > History to view its complete bad sector information. To determine whether bad sectors are affecting the drive, see if there's a significant increase in the number of bad sectors over time.
    • Adjusted how the system calculates the estimated lifespan for M.2 NVMe SSDs to provide a more accurate estimation.
    • Support for AAC encoded audio is widespread across end devices like smartphones, tablets, computers, and the majority of other media playback devices. The need for AAC transcoding to achieve better compatibility has significantly diminished and will be removed starting with DSM 7.1.1.
    • Surveillance Station must be updated to version 9.0.1- 7673 or above to be compatible with this update.


    What’s New

    • Added support for recipient profiles for email notifications, allowing users to add multiple email addresses under each profile and customize rules for the profiles.
    • Users can now enable the quota setting for shared folders that are located on volumes with data deduplication enabled.
    • Added support for RAID arrays with 16 and 20 hard drives when creating RAID groups.
    • Supports checking the 2-factor authentication status of user accounts at Control Panel > User & Group > Users.
    • Added support for SR-IOV on the following the Synology network interface cards: E10G21-F2, E25G21-F2.


    Fixed Issues

    • Fixed an issue where the "Enable UID/GID shifting" setting would be deactivated after modifying the time interval for updating the user/group list on an LDAP client.
    • Fixed multiple security vulnerabilities regarding CIFS-utils (CVE-2022-27239, CVE-2022-29869).
    • Fixed a security vulnerability regarding OpenLDAP (CVE-2022-29155).
    • Fixed a security vulnerability regarding cURL (CVE-2022-22576).
    • Fixed a security vulnerability regarding Zlib (CVE-2018-25032).
    • Fixed a security vulnerability regarding Freetype (CVE-2022-27406).
    • Fixed multiple security vulnerabilities regarding 802.1X (CVE-2021-30004, CVE-2021-30266).
    • Fixed multiple security vulnerabilities regarding GNU C Library(CVE-2021-43396, CVE-2022-23218, CVE-2022-23219).
    • Fixed multiple security vulnerabilities regarding YAML-cpp (CVE-2018-20573, CVE-2018-20574, CVE-2019-6285).
    • Fixed multiple security vulnerabilities regarding Linux Kernel (CVE-2019-11477, CVE-2019-11478, CVE-2019-11479, CVE-2020-12770, CVE-2019-18282, CVE-2019-19527, CVE-2019-19532, CVE-2019-19537, CVE-2021-0605, CVE-2021-3732, CVE-2021-3739, CVE-2021-3753, CVE-2021-4149, CVE-2021-4203, CVE-2021-20317, CVE-2021-20321, CVE-2021-20322, CVE-2021-29154, CVE-2021-29650, CVE-2021-34556, CVE-2021-35477, CVE-2021-39633, CVE-2021-39698, CVE-2021-45868, CVE-2022-0185, CVE-2022-0330, CVE-2022-0617, CVE-2022-0847, CVE-2022-1011, CVE-2022-1048, CVE-2022-1055, CVE-2022-1353, CVE-2022-20008, CVE-2022-27666, CVE-2022-28893, CVE-2022-29582).
    • Updated OpenSSL to version 1.1.1o to fix multiple security vulnerabilities (CVE-2022-1292, CVE-2021-3712, CVE-2022-0778).
    • Updated libarchive to version 3.6.1 to fix multiple security vulnerabilities (CVE-2021-36976, CVE-2022-26280).
    • Updated Mbed-TLS to version 2.28 to fix multiple security vulnerabilities (CVE-2021-44732, CVE-2021-45450, CVE-2021-43666).
    • Updated Python to version 3.8.12 to fix multiple security vulnerabilities (CVE-2021-3733, CVE-2021-3737, CVE-2022-0391).
    • Updated Redis to version 6.2.7 to fix multiple security vulnerabilities (CVE-2022-24735, CVE-2022-24736).
    • Updated ISC DHCP to version 4.4.3 to fix a security vulnerability (CVE-2021-25217).

     

     

    Problems with TCRP postupdate

    in General Post-Installation Questions/Discussions (non-hardware specific)

    Posted

    Hello,

    I have installed 7.1.0-42661 Update 1 on my vmware to test updates. I realized, that updating to "Update 2" ends in a recovery loop. This is what I tried next:

     

    • Applying Update 2 in DSM
    • Reboot after update directly to TCRP
    • ./rploader update (was already up to date)
    • ./rploader postupdate 918+
      • answered "yes" to both questions, whether 42661-2 shall be used
    • sudo reboot

    After reboot, I can not see my DSM any more in network. What did I forget? Is the "postupdate" really the only command? Or is it necessary to apply again the "build" command afterwards? 

    Problem Installing with TinyCore RedPill (TCRP) Loader

    in General Installation Questions/Discussions (non-hardware specific)

    Posted

    Dear all,

     

    I have used tinycore redpill during March / April several times and installed 918+ installations on several HP ProCurve Hardware machines. Everytime I was successful. Today I had the same task, but this time something is different.

     

    I installed like always - the only difference is, that there is now a version v0.8.0.0 available since two days ago. I tried now with two different PCs, two different USB sticks, two different hard disks and two different platforms (918+ / 920+).

     

    Everytime I have the same result:

    - Build process without any errors

    - DiskStation is visible after reboot "Welcome"

    - pat-file 7.1.0-42661 can be installed successfully

    -> Reboot

    - After reboot always the same:

     

    "Welcome Back! We have detected that you have moved your harddisk to a new DS918+. Please click on recovery to recover your settings"

    => Loop! Every time I press "Recover", the PC reboots and have the same situation.

     

    I have no idea, whether I am doing something wrong, but I fear it is something todo with the new 0.8.0.0 img?

     

    I need help :(

    Problem installing with TinyCore RedPill (TCRP) Loader

    in General Installation Questions/Discussions (non-hardware specific)

    Posted

    Dear all,

     

    today I tried to install from scratch a new DSM_DS918+ 7.1-42661.

    Just one Harddisk connected to SATA0 and did the steps (I did this already several times with other hardware).

    But today I have a new issue. The first *.pat file installation seems to be successful, but after reboot I always get the "Welcome Back" Message, and I have to re-install it several times... now Idea what is wrong :(

×
×
  • Create New...