@ -36,26 +36,56 @@ ### Setting up a new 2025 or later plus model with only unverified HDDs in DSM 7
Credit to Alex_of_Chaos on reddit
DSM won't install on a 2025 or later series plus model if you only have unverified HDDs. But we can get around that.
DSM 7.2.2 won't install on a 2025 or later series plus model if you only have unverified HDDs. But we can get around that.
1. Start telnet by entering `http://<NAS-IP>:5000/webman/start_telnet.cgi` into your browser's address bar.
1. Get the Synology's IP address from Synology Assistant.
2. Start DSM's telnet server by entering `http://<NAS-IP>:5000/webman/start_telnet.cgi` into your browser's address bar.
- Replace `<NAS-IP>` with the IP address of the Synology NAS.
2. Open a telnet client (powershell, PuTTY etc) on your computer and connect to the Synology with 'telnet <NAS-IP>`.
- Replace `<NAS-IP>` with the IP address of the Synology NAS.
3. Log into telnet with:
3. Open a telnet client (PowerShell, PuTTY, Terminal etc) on your computer and connect to the Synology by typing the following in the telnet window then press enter:
```
telnet <NAS-IP>
```
- Replace `<NAS-IP>` with the IP address of the Synology NAS.
- **Note:** If using a Mac you may need to install Terminal.
<details>
<summary>Click here to see how to install telnet on a Mac</summary>
**Installing telnet on a Mac**
a. Open your Terminal app.
b. If you don't have Homebrew installed, copy and paste the following command into Terminal and press Enter:
c. Once Homebrew is installed, simply run the installation command:
```
brew install telnet
```
</details>
4. When it asks you to log in use:
- `root` for the login
- `101-0101` for the password
4. Execute the following command: (using a while loop in case DSM is running in a VM)
- **Note:** When you type the password you may not see what you are typing.
5. Execute the following command:
```
touch /tmp/installable_check_pass
```
- If DSM is running in a virtual machine use this command instead:
```
while true; do touch /tmp/installable_check_pass; sleep 1; done
```
5. Refresh the web installation page and install DSM.
6. Then in the telnet window, or via SSH, execute the following command:
6. Refresh the web browser installation page and install DSM.
7. Then back in the telnet window, or via SSH, paste the following command and press enter:
```
/usr/syno/bin/synosetkeyvalue /etc.defaults/synoinfo.conf support_disk_compatibility no
```
7. If Storage Manager is already open close then open it, or refresh the web page. If refreshing the page or restarting Storage Manager is not working, try restarting your Synology NAS.
8. You can now create your storage pool from Storage Manager.
8. If Storage Manager is already open close then open it, or refresh the web page. If refreshing the page or restarting Storage Manager is not working, try restarting your Synology NAS.
9. You can now create your storage pool from Storage Manager.
- Bug fix for the wrong E10M20-T1, M2D20, M2D18 and M2D17 db files getting processed if the main drives were migrated from a different Synology model.
- Resulted in NVMe drives in one of the above PCIe cards still showing as Unverified.
v3.6.136
- Added messages when write mostly options were used but write mostly cannot be set. Issue #602
- Message for when the `-S` option is used and there are no internal 2.5 inch SDDs found.
- Message for when the user used `-ssd=nvmeNnN` as NVMe drives do not contain DSM system or swap partitions.
v3.6.135
- Changed to replace curly/smart quotes (from db files edited in Word or in iOS) before backing up db files to prevent jq errors.
- Added `/usr/syno/bin` or `/usr/syno/sbin` to the syno... commmands that were missing the full path (for people with a corrupt or edited PATH). Issue #601
- The change above also fixes jq errors caused by those commmands not returning anything. Issue #601
- Bug fix for not detecting script was running from triggered scheduled task.
v3.6.134
- Bug fix for trying to backup M.2 PCIe card's .db.new when it didn't exist which caused the following error. Issue #599
- **cp: cannot stat '': No such file or directory
- ERROR 5 Failed to backup !**
v3.6.133
- Bug fix for not updating db files with each drive's firmware version if drives were previously added to the db files without firmware version from an older script version. Issue #598
- Bug fix for restore mode not re-enabling drive database updates in DSM 7.3 and later.
- Bug fix for sometimes not detecting script was running from scheduled task.
- Bug fix for some errors showing in all red instead of just ERROR being in red.
v3.6.132
- Bug fix for expansion units that DSM reports with different model names. Issue #574
- Adds aliases from each expansion disk's runtime container, such as mapping RX1217-1 to RX1217 when detection reports RX1217RP.
- Uses exact model-family matching so RX1217 does not also edit RX1217RP or RX1217SAS database files.
- Bug fix for trying to backup non-existent file. Issue #574
- Bug fix for SynoOnlinePack version not found causing an error.
Thanks @tkirkland
v3.6.131
- Fix for DSM 7.4 including "rules" db files in the drive db files folder.
v3.6.130
- Bug fix for Samsung SSDs that have 2.5" in their model name.
- Bug fix for not removing leading spaces in drive model names (introduced in v3.6.123).
v3.6.129
- Bug fix for backing up expansion unit db files (introduced in v3.6.126).
v3.6.128
- Bug fix for trying to backup "*_v7.db.version" instead of "*_v7.version".
v3.6.127
- Bug fix for trying to backup "*_v7.db.version" instead of "*_v7.version".
- Bug fix for 6 TB drives having '"size_gb": 6001' in db files instead of '"size_gb": 6000'.
- Also replaces any existing '"size_gb": 6001' in db files with '"size_gb": 6000'.
v3.6.126
- Changed to a more reliable way of getting the NAS model name.
- Changed to keep db file backups up to date.
- If a DSM update, or the user, has updated the drive databases the old db file backups are replaced with new backups of the unedited db files.
- Bug fix for db files with a space in their name, like "rxd1219sas module_v7.db".
- Bug fix for restore mode failing to restore E10M20-T1 nic support on NAS models that don't officially support the E10M20-T1.
- Bug fix for XPE not showing drive's correct temperature. Issue #585
v3.6.125
- Bug fix for missing lvs and pvs errors for 1 bay NAS (that don't have LVM).
v3.6.124
- Bug fix for script trying to set write_mostly on SATA M.2 drives. Issue #567
- Bug fix for script trying to use nvme command to get SATA M.2 drives' vendor id. Issue #567
Add your SATA or SAS HDDs and SSDs plus SATA and NVMe M.2 drives to your Synology's compatible drive databases, including your Synology M.2 PCIe card and Expansion Unit databases.
The script works in DSM 7, including DSM 7.1, 7.2 and 7.3, and DSM 6.
The script works in DSM 7, including DSM 7.1, 7.2, 7.3 and 7.4, and DSM 6.
It also has a restore option to undo all the changes made by the script.
@ -186,7 +186,7 @@ ### vendor_ids.txt
If DSM doesn't know the brand of your NVMe drives they will show up in Storage Manager as Unknown brand, and Unrecognised firmware version.
- Synology Package Source adds DSM packages that are available from GitHub to Package Center so users can easily install packages from various GitHub developers and Package Center can update the packages when newer versions are released.
- Synology package to show drive device id, DSM drive number, location, model, serial number, health and S.M.A.R.T. values for all drives in all your Synology NAS.
- Synology package that allows you to disable and enable community package sources you have added to Package Center. It also allows adding known, working, package sources without having to type and paste anything in Package Center's settings.
- **<ahref="https://github.com/007revad/Syno_CPU_Temperature">Syno CPU Temperature</a>**
- Synology package to log CPU temperature to help troubleshooting Synology randomly shutting down due to overheating.
- Add your SATA or SAS HDDs and SSDs plus SATA and NVMe M.2 drives to your Synology's compatible drive databases, including your Synology M.2 PCIe card and Expansion Unit databases.