raeesumer
-
Posts
25 -
Joined
-
Last visited
Posts posted by raeesumer
-
-
- Outcome of the Installation: SUCCESSFUL
- DSM version prior update: DSM 7.1.1-42962 Update 1 (DVA3221)
- Loader version and model: PeterSuh-Q3 TCRP Friend 0.0.7 (DDSML) DVA3221
- Installation type: BAREMETAL - ASROCK Z390M-ITX/AC, Intel Core i7 8700, 16GB RAM on U-NAS 410 Chassis with Noctua NH-L9i CPU fan
-Additional comments: Manually updated via DSM Web GUI
-
- Outcome of the Installation: SUCCESSFUL
- DSM version post update: TCRP Friend DSM 7.1.1-42962 Update 1 (DVA3221)
- DSM version prior update: ARPL v1.0-beta6 DSM 7.1.1-42962 Update 4 ( DS3622xs+)
- Loader version and model: TCRP Friend 0.0.7 (DDSML) DVA3221
- Installation type: BAREMETAL - ASROCK Z390M-ITX/AC, Intel Core i7 8700, 16GB RAM on U-NAS 410 Chassis with Noctua NH-L9i CPU fan
-Additional comments: Booted with TCRP Friend USB and the entire system migrated from DS3622xs+ to DVA3221
-
1
-
-
- Outcome of the Installation: SUCCESSFUL
- DSM version prior update: ARPL v1.0-beta9 DSM 7.1.1-42962 Update 4 ( DS3622xs+)
- Loader version and model: ARPL v1.0-beta9 DSM 7.1.1-42962 Update 5 ( DS3622xs+)
- Installation type: BAREMETAL - ASROCK Z390M-ITX/AC, Intel Core i7 8700, 16GB RAM on U-NAS 410 Chassis with Noctua NH-L9i CPU fan
-Additional comments: Updated Via DSM GUI
-
On 7/7/2022 at 5:50 AM, merve04 said:
Out of curiosity, why run dva1622? Why not ds3615 or the like?
DVA model has 8 free camera license and all DS model is with 2 camera license
-
GPU showing no detected even if i passthrough Graphics card.
Any suggestion, how to get GPU getting detected.
-
- Outcome of the Installation: SUCCESSFUL
- DSM version prior update: ARPL v1.0-beta9 DSM 7.1.1-42962 Update 3 ( DS3622xs+)
- Loader version and model: ARPL v1.0-beta9 DSM 7.1.1-42962 Update 4 ( DS3622xs+)
- Installation type: BAREMETAL - ASROCK Z390M-ITX/AC, Intel Core i7 8700, 16GB RAM on U-NAS 410 Chassis with Noctua NH-L9i CPU fan
-Additional comments: Updated Via DSM GUI
-
I have a plan to buy new box with onboard CPU china made NAS motherboard. The processor is AMD Ryzen 7 5825U with AMD Radeon™ Graphics + four 2.5G Ethernet port. Anyone has any experience. My plan is to go for DVA3221 with ARPL. Anybody has any suggestion or feedback regarding the compatibility or any issues while running surveillance system.
-
On 2/7/2023 at 11:53 AM, oswaldini said:
Hi, I want to buy H370M-ITX/ac. This motherboard has two network cards: Intel I219V and I211AT - will both NICs work? The information I found are not unequivocal.
I am using the similar ASRock Z390M-ITX/ac, ARPL with DS3622xs+ is running good in my box with two active network. I configured teaming with two NIC. Hope your Mobo H370M-ITX/ac will good to go also
-
Installed fresh DSM7.1 using ARPL v1.0-beta9 DSM 7.1.1-42962 Update 2 with NAS Model DS3622xs+, All done successfully in first try itself.
MB: Asrock Z390M-ITX/AC | CPU: Intel Core i7 8700 | Ram: Patriot 16GB | Chasis: U-NAS 410 with Noctua NH-L9i fan
-
- Outcome of the Installation: SUCCESSFUL
- DSM version prior update: ARPL v1.0-beta9 DSM 7.1.1-42962 Update 2 ( DS3622xs+)
- Loader version and model: ARPL v1.0-beta9 DSM 7.1.1-42962 Update 3 ( DS3622xs+)
- Installation type: BAREMETAL - ASROCK Z390M-ITX/AC, Intel Core i7 8700, 16GB RAM on U-NAS 410 Chassis with Noctua NH-L9i CPU fan
-Additional comments: Reboot Required
-
- Outcome of the Installation: SUCCESSFUL
- DSM version prior update: FRESH INSTALLATION (Before running DSM 6.3 + Jun's Loader v1.04b - DS918+)
- Loader version and model: ARPL v1.0-beta9 DSM 7.1.1-42962 Update 2 ( DS3622xs+)
- Installation type: BAREMETAL - ASROCK Z390M-ITX/AC, Intel Core i7 8700, 16GB RAM on U-NAS 410 Chassis with Noctua NH-L9i CPU fan
-Additional comments: Reboot Required
-
Hi,
Anybody has any success in installing fresh DSM 7.* or upgrading from DSM 6.2.3-25426 Update 2 to DSM 7.* in ASRock Z390M-ITX/ac motherboard.
-
So far i connected 6 drives and all detected and no issues
-
1
-
-
Hi
For me only one of the NIC worked. So please try switching the network cable to other network card and start the process again. I just followed the procedure for DS918+
Hope it will help you too.
-
1
-
-
- Outcome of the Installation: SUCCESSFUL
- DSM version prior update: DSM 6.2.3-25426
- Loader version and model: Jun's Loader v1.04b - DS918+
- Using custom extra.lzma: NO
- Installation type: BAREMETAL - ASROCK Z390M-ITX/AC, Intel Core i7 8700, 16GB RAM on U-NAS 410 Chassis with Noctua NH-L9i CPU fan
-Additional comments: Reboot Required
-
- Outcome of the Installation: SUCCESSFUL
- DSM version prior update: DSM 6.2.2-24922 Update 4
- Loader version and model: Jun's Loader v1.04b - DS918+
- Using custom extra.lzma: NO
- Installation type: BAREMETAL - ASROCK Z390M-ITX/AC, Intel Core i7 8700, 16GB RAM on U-NAS 410 Chassis with Noctua NH-L9i CPU fan
-Additional comments: Reboot Required
-
- Outcome of the Installation: SUCCESSFUL
- DSM version prior update: DSM 6.2.2-24922
- Loader version and model: Jun's Loader v1.04b - DS918+
- Using custom extra.lzma: NO
- Installation type: BAREMETAL - ASROCK Z390M-ITX/AC, Intel Core i7 8700, 16GB RAM on U-NAS 410 Chassis with Noctua NH-L9i CPU fan
-Additional comments: Reboot Required
-
- Outcome of the Installation: SUCCESSFUL
- DSM version prior update: DSM 6.2.1-23824 update 4
- Loader version and model: Jun's Loader v1.04b - DS918+
- Using custom extra.lzma: NO
- Installation type: BAREMETAL - ASROCK Z390M-ITX/AC, Intel Core i7 8700, 16GB RAM on U-NAS 410 Chassis with Noctua NH-L9i CPU fan
-
Thanks for the script. CPU information updated successfully.
But the number of threads shows wrong.
For Intel core i7 8700 processor, It is 6 core and 12 threads. But system shows 8 threads only.
-
1
-
-
- Outcome of the Installation: SUCCESSFUL
- DSM version prior update: Fresh Installation
- Loader version and model: Jun's Loader v1.04b - DS918+
- Using custom extra.lzma: NO
- Installation type: BAREMETAL - ASROCK Z390M-ITX/AC, Intel Core i7 8700, 16GB RAM on U-NAS 410 Chassis with Noctua NH-L9i CPU fan
- Additional comments: Only one NIC works
-
My first Xpenology is running with same specs
Mobo: Asrock Z390M-ITX/AC
CPU: Intel Core i7 8700
Ram: Patriot 16GB
Chasis: U-NAS 410 with Noctua NH-L9i fan
HDD: Ordinary HDD from old ReadyNAS and Media Center devices.
Xpenology: DSM 6.2.1-23824 Update 4 for DS918+ on Jun's Loader 1.04b
Only one NIC is working, even though I added entries for mac2(Second NIC) and mac3(Wireless)
-
25 minutes ago, Olegin said:
Hi, only NIC's i210/i211 and r8111 are able to work in 6.2.1 DSM version with this loader. Syno signed own drivers and nothing more can't to be loaded yet.
Wireless adapter in M.2 socket will not working too, but you can use USB Wifi dongle to make wireless network with your xpenology.
You can ignore this information, it's not true. The right info you can see in ssh by cat /proc/cpuinfo command. Our comrade FOXBI done this script to correct displaying cpu info.
Thanks Olegin,
I will try this
-
Hi , Olegin
I successfully installed my first Xpenology. Thanks for your guide.
Hardware Specs:
Mobo: Asrock Z390M-ITX/AC
CPU: Intel Core i7 8700
Ram: Patriot 16GB
Chasis: U-NAS 410 with Noctua NH-L9i fan
HDD: Ordinary HDD from old ReadyNAS and Media Center devices.
Xpenology: DSM 6.2.1-23824 Update 4 on Jun's Loader 1.04b
Only one NIC is working, even though I added entries for mac2(Second NIC) and mac3(Wireless)
In my system info, it shows Intel Celeron J3455 Quad-Core and Number of cores as 4 only even though my processor is Intel Core i7 8700 (6 Core).
Do you have a solution to fix this issue?
DSM 7.2-64561
in DSM Updates Reporting
Posted · Edited by Polanskiman
Added missing tags and corrected link
https://www.synology.com/en-global/releaseNote/DSM
Version: 7.2-64561
(2023-05-22)
Important Note
After installing this update, you will not be able to downgrade to a previous DSM version.
This update will restart your Synology NAS.
Starting from this version, logs for drives will no longer appear in Storage Manager > HDD and will be available only in Log Center.
Removed the "Automatically create port forwarding rules" option from QuickConnect advanced settings to increase network security.
Users can now create a Btrfs volume of up to 1 PB on specific Synology NAS models. This update automatically converts existing volumes that use the Btrfs (Peta Volume) file system to Btrfs. However, to create a volume larger than 200 TB, a RAID 6 storage pool and at least 64 GB of system memory are still required.Learn more
The maximum single volume size supported by RS2423+/RS2423RP+ has been adjusted to 200 TB (with a minimum system memory requirement of 32 GB).
Starting from this version, only Windows Server 2008 R2 and above versions will be supported. After installing this update, the current Windows Server 2008 domain and earlier versions will be unavailable.
For the models below, you can only download the upgrade patch from Synology Download Center because you won't receive notifications for this update on your DSM.
FS Series: FS3017, FS2017, FS1018
XS Series: RS18016xs+, RS4017xs+, RS3617xs+, RS3617xs, RS3617RPxs, RS18017xs+, DS3617xs, DS3617xsII, DS3018xs
Plus Series: RS2416RP+, RS2416+, DS916+, DS716+II, DS716+, DS216+II, DS216+, DS1817+, DS1517+, RS2818RP+, RS2418RP+, RS2418+, RS818RP+, RS818+, DS1618+, DS918+, DS718+, DS218+, RS1219+
Value Series: DS416, DS416play, DS216, DS216play, DS116, RS816, DS1817, DS1517, RS217, DS418play
J Series: DS416slim, DS416j, DS216j, DS418j, DS218j, DS419slim, DS119j
What’s New
Added support for WriteOnce shared folders. This feature is based on the Write Once, Read Many (WORM) technology and can be enabled to prevent files from being modified, deleted, or renamed for a specified period.
Added support for volume encryption. All volume encryption keys are stored in the Encryption Key Vault, which can be set up on a local Synology NAS or via KMIP on a remote Synology NAS.
Added more Synology NAS models to support M.2 NVMe SSD storage pools. Learn more
Added more Synology NAS models to support the M2D18 adapter card: RS822RP+, RS822+, RS1221RP+, and RS1221+.
Added more SSD cache group management options, including changing the RAID type and replacing a drive.
Added support for inline zero-block removal to increase the efficiency of data deduplication.
Adjusted how drive information is presented in Storage Manager. Users can now quickly check the condition of their drives by looking at the "Drive Status" field.
Users can now view the amount of used and free space for each storage pool and volume in Storage Manager.
Added a warning notification for when the available shared folder quota is low.
Supports deleting individual desktop notifications.
Supports sending DSM notifications via additional webhook providers, including LINE and Microsoft Teams.
Supports creating custom notification rules for system events, giving users greater control over what notifications to receive.
Supports exporting a list of users and of groups.
Added support for SAML to integrate DSM with external SSO servers.
Added the option to allow non-admin users to safely eject USB devices.
Users can now manually input the IP addresses or FQDNs of one or more domain controllers in the trusted domain. This allows Synology NAS to sync domain data directly with the specified domain controllers.
Users can now enable Synology's email server to send DSM notifications directly to their Synology Account.
Fixed Issues
Fixed an issue where adding drives to a JBOD storage pool did not expand its capacity.
Updated Mbed-TLS to version 2.28.2 to fix multiple security vulnerabilities (CVE-2021-36647, CVE-2022-46392, CVE-2022-46393).
Updated Libksba to version 1.6.3 to fix a security vulnerability (CVE-2022-3515).
Updated SQLite to version 3.40.0 to fix a security vulnerability (CVE-2022-46908).
Updated Certifi to version 2022.12.07 to fix a security vulnerability (CVE-2022-23491).
Updated Node.js to version 14.21.1 to fix a security vulnerability (CVE-2022-43548).
Updated cURL to version 7.86.0 to fix multiple security vulnerabilities (CVE-2022-27774, CVE-2022-27775, CVE-2022-27776, CVE-2022-27781, CVE-2022-27782, CVE-2022-32205, CVE-2022-32206, CVE-2022-32207, CV E-2022-32221, CVE-2022-35252, CVE-2022-42915, CVE-2022-42916).
Updated PHP to version 8.1.9 to fix multiple security vulnerabilities (CVE-2019-11043, CVE-2021-21705, CVE-2022-31625).
Updated Sysstat to version 12.7.1 to fix a security vulnerability (CVE-2022-39377).
Updated OpenSSL to version 3.0.7 to fix multiple security vulnerabilities (CVE-2022-2068, CVE-2022-2097, CVE-2022-2274, CVE-2022-3358, CVE-2022-3602, CVE-2022-3786).
Updated Expat to version 2.5.0 to fix a security vulnerability (CVE-2022-43680).
Updated Libtirpc to version 2.87 to fix a security vulnerability (CVE-2021-46828).
Updated GnuPG to version 2.2.39 to fix a security vulnerability (CVE-2022-34903).
Updated OpenVPN to version 2.5.8 to fix a security vulnerability (CVE-2022-0547).
Updated libxml2 to version 2.9.14 to fix a security vulnerability (CVE-2022-23308).
Updated GMP to version 6.2.1 to fix a security vulnerability (CVE-2021-43618).
Updated ImageMagick to version 6.9.12-61 to fix multiple security vulnerabilities (CVE-2020-25664, CVE-2020-25665, CVE-2020-25666, CVE-2020-25667, CVE-2020-25674, CVE-2020-25675, CVE-2020-25676, CVE-2020-27560, CVE-2020-27750, CVE-2020-27751, CVE-2020-27752, CVE-2020-27753, CVE-2020-27754, CVE-2020-27755, CVE-2020-27756, CVE-2020-27757, CVE-2020-27758, CVE-2020-27759, CVE-2020-27760, CVE-2020-27761, CVE-2020-27762, CVE-2020-27763, CVE-2020-27764, CVE-2020-27765, CVE-2020-27766, CVE-2020-27767, CVE-2020-27768, CVE-2020-27769, CVE-2020-27770, CVE-2020-27771, CVE-2020-27772, CVE-2020-27773, CVE-2020-27774, CVE-2020-27775, CVE-2020-27776, CVE-2020-29599, CVE-2021-20176, CVE-2021-20224, CVE-2021-20241, CVE-2021-20245, CVE-2021-20246, CVE-2021-20309, CVE-2021-3574, CVE-2021-3596, CVE-2021-39212, CVE-2021-4219, CVE-2022-1114, CVE-2022-1115, CVE-2022-28463, CVE-2022-32545, CVE-2022-32546, CVE-2022-32547).
Updated FFmpeg to version 4.1.9 to fix multiple security vulnerabilities (CVE-2020-20892, CVE-2020-20902, CVE-2020-21688, CVE-2020-21697, CVE-2021-3566, CVE-2021-38114, CVE-2021-38291).
Fixed a security vulnerability regarding Netatalk (CVE-2022-45188).
Fixed multiple security vulnerabilities regarding Python3 (CVE-2020-10735, CVE-2021-28861, CVE-2022-45061).
Fixed multiple security vulnerabilities regarding iproute2 (CVE-2022-3527, CVE-2022-3529, CVE-2022-3530).
Fixed multiple security vulnerabilities regarding D-Bus (CVE-2022-42010, CVE-2022-42011, CVE-2022-42012).
Fixed a security vulnerability regarding syslog-ng (CVE-2022-38725).
Fixed a security vulnerability regarding inetutils (CVE-2022-39028).
Fixed a security vulnerability regarding DNSmasq (CVE-2022-0934).
Fixed a security vulnerability regarding BusyBox-udhcp (CVE-2019-5747).
Fixed multiple security vulnerabilities regarding Linux Kernel (CVE-2021-22600, CVE-2021-38209, CVE-2021-4037, CVE-2022-0168, CVE-2022-1016, CVE-2022-1729, CVE-2022-1786, CVE-2022-20141, CVE-2022-20368, CVE-2022-2078, CVE-2022-2639, CVE-2022-2905, CVE-2022-29581, CVE-2022-32250, CVE-2022-3524, CVE-2022-3566, CVE-2022-3567, CVE-2022-36879, CVE-2022-36946, CVE-2022-42703).
Fixed a security vulnerability regarding Nginx (CVE-2022-3638).
Fixed a security vulnerability regarding ghostscript (CVE-2023-28879).
Fixed a security vulnerability regarding curl (CVE-2023-23916).
Limitation
S.M.A.R.T. testing for M.2 NVMe SSDs is no longer supported.
Starting from DSM 7.2 Beta, Virtual Machine Manager will no longer support creating clusters with older DSM versions. Please update each host in the cluster to the same DSM version or above versions for the Virtual Machine Manager cluster to operate properly.