SynoSendFileChangesViaMail
Synology_HDD_db
Our great sponsors
| SynoSendFileChangesViaMail | Synology_HDD_db | |
|---|---|---|
| 1 | 70 | |
| 1 | 1,872 | |
| - | - | |
| 3.2 | 9.5 | |
| almost 3 years ago | 2 days ago | |
| Shell | Shell | |
| - | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
SynoSendFileChangesViaMail
-
Cloud Sync IFTTT Integration? Webhook?
You can find the code at https://github.com/MarcoSchicke/SynoSendFileChangesViaMail
Synology_HDD_db
-
Synology 1823xs NVMe Question
I used my https://github.com/007revad/Synology_HDD_db script to add them to DSM's compatible drive database and allow creating NVMe storage pool.
- DS923+ - NVME Storage and Cache and DS220+ migration
-
Many of my functions are not recognised by GitHub as functions
The bash script is here: https://github.com/007revad/Synology_HDD_db/blob/develop/syno_hdd_db.sh
- [DS920+] 7.2.1-69057 Update 1 with M2 Volume
-
Help enabling SHR on enterprise model
You should probably schedule those commands to run at start-up in case a DSM update undoes your changes. See how_to_schedule (replace that command with the two command lines above).
-
I just lost my M.2 NVME ssd volume after an automatic update!
Update: I managed to fix it by running this script. One tip is to save your script in a place that doesn't have spaces in the location path. Part of me wonders if I should have just stayed on DSM 6 since if it isn't broke don't fix it.
- Has anyone here ditched Synology NASs because of the unverified drive annoyance?
- 2.5 ssd vs nvme for storage pool
-
unverified disks on passive server in HA setup
Or better yet, just schedule my Synology_HDD_db script to run at boot-up. https://github.com/007revad/Synology_HDD_db
-
m.2 support breaking in 7.2 update 1?
I've just done the update and had a similar experience. Drives blacklisted but storage pool still up and available. Ran the script from https://github.com/007revad/Synology_HDD_db
What are some alternatives?
docker-mbsync - A Docker container which runs the mbsync tool automatically to synchronize your email
Synology_enable_M2_volume - Enable creating volumes with non-Synology M.2 drives
synology-plex-auto-update - I propose a step-by-step tutorial to keep the native package of your Plex server automatically up to date.
Synology_M2_volume - Easily create an M.2 volume on Synology NAS
AirConnect-Synology - Updated AirConnect packages for Synology NAS and Synology Router
r8152 - Synology DSM driver for Realtek RTL8152/RTL8153/RTL8156 based adapters
brain-dump - Cheat sheets, customizations and configurations I use across multiple systems.
Synology_Plex_Backup - A script to backup Plex to a tgz file. For DSM 7 and DSM 6.
docker-mailserver - A fullstack but simple mail server (SMTP, IMAP, LDAP, Antispam, Antivirus, etc.) using Docker. [Moved to: https://github.com/docker-mailserver/docker-mailserver]
Synology_SHR_switch - Easily switch between SHR and RAID Groups, or enable RAID F1
LogAnalysis - LogAnalysis - Package for Synology NAS
synology-wireguard - WireGuard support for some Synology NAS drives