mirror of
https://github.com/007revad/Synology_HDD_db.git
synced 2026-04-25 13:45:59 +03:00
[GH-ISSUE #377] Lost M.2 PCIe Card E10M20-T1 after update to DSM 7.2.2-72806 #634
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Synology_HDD_db#634
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @RozzNL on GitHub (Oct 24, 2024).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/377
After updating my DS1821+ to DSM 7.2.2-72806 the M.2 PCIe card E10M20-T1 is not found and i have "lost" my Storage Pool
Ran great with DSM 7.2.1xxxx
@RozzNL commented on GitHub (Oct 24, 2024):
root@DS1821:~# /volume1/homes/admin/Scripts/syno_hdd_db.sh -nfr
Synology_HDD_db v3.5.103
DS1821+ DSM 7.2.2-72806
StorageManager 1.0.0-00502
ds1821+_host_v7 version 8058
Using options: -nfr
Running from: /volume1/homes/admin/Scripts/syno_hdd_db.sh
HDD/SSD models found: 2
ST14000NM001G-2KJ103,SN03,14000 GB
ST16000NM001G-2KK103,SN03,16000 GB
M.2 drive models found: 1
Samsung SSD 970 EVO 1TB,2B2QEXE7,1000 GB
No M.2 PCIe cards found
No Expansion Units found
ST14000NM001G-2KJ103 already exists in ds1821+_host_v7.db
ST16000NM001G-2KK103 already exists in ds1821+_host_v7.db
Samsung SSD 970 EVO 1TB already exists in ds1821+_host_v7.db
Support disk compatibility already disabled.
Support memory compatibility already disabled.
Max memory already set to 64 GB.
NVMe support already enabled.
M.2 volume support already enabled.
Drive db auto updates already disabled.
DSM successfully checked disk compatibility.
You may need to reboot the Synology to see the changes.
@RozzNL commented on GitHub (Oct 24, 2024):
@RozzNL commented on GitHub (Oct 24, 2024):
Tried to use your Reinstall_DSM but can not roll-back to DSM 7.2.1xxx
@RozzNL commented on GitHub (Oct 24, 2024):
/volume1/homes/admin/Scripts/syno_enable_m2_card.sh
Synology_enable_M2_card v1.0.6
DS1821+ DSM 7.2.2-72802 (=due to multiple dsm_reinstall.sh)
There is a newer version of this script available.
Current version: v1.0.6
Latest version: v3.1.16
Do you want to download v3.1.16 now? [y/n]
y
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 366k 0 366k 0 0 642k 0 --:--:-- --:--:-- --:--:-- 642k
v3.1.16 and changes.txt downloaded to: /volume1/homes/admin/Scripts
Synology_enable_M2_card v3.1.16
DS1821+ DSM 7.2.2-72802
StorageManager 1.0.0-00502
Running from: /volume1/homes/admin/Scripts/syno_enable_m2_card.sh
Select your M.2 Card: 1
Backed up /usr/syno/etc.defaults/adapter_cards.conf
Enabled E10M20-T1 NIC for DS1821+
Enabled E10M20-T1 NVMe for DS1821+
Need to download dtc
Do you want to download dtc? [y/n]
y
Downloading dtc
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 146k 100 146k 0 0 624k 0 --:--:-- --:--:-- --:--:-- 626k
Downloaded md5: 01381dabbe86e13a2f4a8017b5552918
Backed up /etc.defaults/model.dtb
Added E10M20-T1 to model.dtb
The Synology needs to restart.
Type yes to reboot now.
Type anything else to quit (if you will restart it yourself).
@RozzNL commented on GitHub (Oct 24, 2024):
After running syno_enable_m2_card.sh, E10M20-T1 with its storagepool came back online!
@RozzNL commented on GitHub (Oct 24, 2024):
@007revad commented on GitHub (Oct 24, 2024):
After the last DSM update I discovered you can set a "pre-task" to a triggered scheduled task. This will make sure that "syno_enable_m2_card.sh --model=E10M20-T1" runs before syno_hdd_db.sh
But I'd still need to reboot after a DSM update has finished and booted up.
This is strange. Syno_hdd_db should have installed dtc, and when syno_enable_m2_card updated it should have included /bin/dtc
@RozzNL commented on GitHub (Oct 26, 2024):
Changed the taskscheduler to include the pre-task, thanks.
Is there any way i can help you further to prevent this happening again or to others?
What is dtc? saw in your github comment this was applicable so said YES to install.
@007revad commented on GitHub (Oct 26, 2024):
dtc (device tree compiler) is a tiny linux cli program used to decompile and compile device tree blobs, which allows adding device information without compiling a new kernel. Synology models from 2020 onwards that use a CPU that Synology hadn't used before all use a device tree blob named model.dtb. To enable E10M20-T1, M2D20, M2D18 or M2D17 on NAS models that don't already support them the script needs dtc, which is not included in DSM.
I'm trying to think how to prevent the same thing happening to other people.
@RozzNL commented on GitHub (Oct 26, 2024):
Before this 7.2.2 update all was well, i did however use the hdd_db at shutdown instead of at bootup, but it should not matter i think?
@barthuijgen commented on GitHub (Nov 2, 2024):
My M2 storage pool also broke after 7.2.2 update. But I can't find this
syno_enable_m2_card.shscript you are referring to, its not in this repository, where can I find it?@RozzNL commented on GitHub (Nov 2, 2024):
https://github.com/007revad/Synology_enable_M2_card
@daviddesmet commented on GitHub (Nov 5, 2024):
You just saved my day!
I recently updated to 7.2.2 and faced the same issue; I created a new task that runs the
syno_enable_m2_card.shscript and updated thesyno_hdd_db.shto run that previous task before. Did a reboot and my storage pool is back!In my specific case it is the E10M20-T1 in a RS822+
@Samt563 commented on GitHub (Nov 28, 2024):
Hello and thanks for the script its been awesome so far, unfortunately the update to 7.2.2 broke my m.2 storage pool too, after a manual task scheduler run (with the latest Script release [v3.5.104]) and the corresponding restart it came back online and everything seems normal.
BUT Synology drive lost its settings, does anybody have some hints/advice on how to proceed? a have a Backup from 28.11.24 04:28 but with the old Synology Drive Server App (3.5.0-26085).
In my specific case it is the DS 920+ 4x HDDs and 2x M.2 SSDs
@007revad commented on GitHub (Dec 1, 2024):
After DSM update the M.2 storage pool won't be available until after:
For the Synology apps that use DSM's pgsql database this can be a problem because DSM will create a new pgsql database on volume1.
Did you previously move
@databaseto the volume2?Which volume does the following command return:
You could try restoring Synology Drive from your backup.
If that doesn't work we can:
@Samt563 commented on GitHub (Dec 7, 2024):
Hello, first of all thank you very much for your help.
That's what i did:
I did move the Database a long time ago
the command returns:
/volume1/@database/pgsql
Thanks again for your work and have a nice day! I hope this helps someone else too.
@pergolafabio commented on GitHub (Feb 20, 2025):
i'm also running 7.2.1 , is it better to wait before installing 7.2.2 ? are you going to change the script?
i have all my apps running/installed on this volume, do i risk to loose everything?
@007revad commented on GitHub (Feb 20, 2025):
DSM 7.2.2 is not a problem. Just make sure the pgsql is on the HDDs' volume before doing the DSM update.
readlink /var/services/pgsql@pergolafabio commented on GitHub (Feb 20, 2025):
Sorry, what is pgsql? Is that a synopackage? Postgress SQL?
@007revad commented on GitHub (Feb 20, 2025):
It's the Postgress SQL database where many Synology packages save their data. If you haven't moved
@database, or deleted volume 1, the database will be located in/volume1/@database.The following are some of the Synology packages that use Synology PostgreSQL
Audio Station
Download Station
Note Station
Synology Application Service
Synology Calendar
Synology Chat
Synology Contacts
Synology Drive Server
Synology MailPlus
Synology Media Server
Synology Photos
Video Station
@pergolafabio commented on GitHub (Feb 20, 2025):
Ah, it's by default volume1 ,? cause my nvme disk is volume2 anyway
@007revad commented on GitHub (Feb 20, 2025):
Correct.
@pergolafabio commented on GitHub (Feb 20, 2025):
But this issue is specific for the E10 ?
I have an Samsung nvme, I don't need that pre-task?
I only need to check the postgre SQL, update DSM , rerun script and good to go?
Never did an DSM update yet, since I bought the 423+
@007revad commented on GitHub (Feb 20, 2025):
The issues discussed in this thread relate only to when the NAs has a NVMe volume setup in a E10M20-T1, M2D20 or M2D18.
If you have not moved the
@databasefolder to the NVMe volume via SSH commands or with the https://github.com/007revad/Synology_app_mover script then you only need to: