-
-
Notifications
You must be signed in to change notification settings - Fork 159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
M2 FireCuda 530 Not Detected on Synology DS923+ #292
Comments
Did storage manager show the NVMe drive before you ran the script? |
Actually, everything was working perfectly on DSM version 7.1.1, but then I updated DSM to its latest version and it started saying that the M2 disk was unknown. I completely formatted my DSM and now I realize it no longer detects my M2 disk even before running the script, and even after running the script, the disk remains undetectable. I suspect it might be due to the latest DSM version 7.2.1, but I'm not certain. |
Schedule syno_hdd_db.sh to run the with -n option at startup as root: Then reboot. If the NVMe drive is still missing, reboot again. |
I've scheduled the script and restart multiple times, but I still can't see my disk appearing. |
Make sure the only script scheduled to run at boot is Then remove the NVMe drive. Reboot the NAS. Shut down the NAS and reinstall the NVMe drive. Then boot the NAS. While the NVMe drive is out of the NAS you could delete all the partitions that are on it (if you can connect it to a computer). |
I followed the procedure but the disk is still not found on DSM. I formatted the disk and deleted all the partitions, but it didn't help. The only script scheduled to run at boot is syno_hdd_db.sh -n. Despite these steps, the disk remains undetected on DSM. |
Can you run this script and reply with a screenshot of the output: https://github.com/007revad/Synology_HDD_db/blob/test/nvme_check.sh |
Here's the result : /volume1/Scripts$ sudo ./nvme_check.sh Checking support_m2_pool setting Checking supportnvme setting Checking synodisk --enum -t cache Checking syno_slot_mappingSystem Disk Esata port count: 0 Internal SSD Cache: Checking udevadm nvme paths Checking if nvme drives are detected with synonvme Checking nvme drives in /run/synostorage/disks Checking nvme block devices in /sys/block Checking logsCurrent date/time: 2024-06-02 11:50:29
|
Your NVMe drive is missing in syno_slot_mapping and /run/synostorage/disks. If I remember correctly this can be caused by the device tree blob (model.dtb) not containing the correct nvme information, or it's missing the power_limit which Synology added in DSM 7.2.1 Update 1. Someone else has 2 NVMe drives that DSM is not seeing and they're sending those NVMe drives to me so I can work out why DSM is not seeing them. You could reinstall DSM 7.2.1 which will restore any corrupt or missing files. It's no different than doing a DSM update.
|
I followed the steps exactly as described, and it successfully reinstalled DSM. However, when I go to Storage Manager, nothing is displayed. I think the issue might be related to DSM 7.2.1 because I never had this problem with the previous version. |
Is it possible to downgrade to version 7.1.1 to confirm that the problem is with the new version ? |
You can downgrade to 7.1.1 but it's not easy. And you can lose all the data on the drives. If you're going to try it you'd want to:
Then see if you can downgrade to DSM 7.1.1 I'd follow these steps https://www.blackvoid.club/dsm-7-to-dsm-6-downgrade/ but modify them for 7.2 to 7.1.1 In steps 3 and 5
In step 5
Or if you prefer python: https://blog.thomasmarcussen.com/synology-nas-recovery-password-telnet/ In step 6 |
Weird that the M.2 drive isn't detected by DSM 7.2.1 but is in DSM 7.1.1 |
Hello,
I'm experiencing an issue where my M2 storage FireCuda 530 is not being detected on my Synology DS923+, currently running DSM 7.2.0.
Ive executing the script here's the result :
I reboot but still not working, It only detected my SSD SATA :
![image](https://private-user-images.githubusercontent.com/114397057/329863401-17ff0afa-71e8-44f6-8a9a-236de6e7ac56.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjIyODYyNjgsIm5iZiI6MTcyMjI4NTk2OCwicGF0aCI6Ii8xMTQzOTcwNTcvMzI5ODYzNDAxLTE3ZmYwYWZhLTcxZTgtNDRmNi04YTlhLTIzNmRlNmU3YWM1Ni5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNzI5JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDcyOVQyMDQ2MDhaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT03OTBhZWJkN2ZlODIwNWE3MzZjNmUzNmJjZTcyZmZlYTE3ZTc0NjdmM2I5YTNiNWNiODg0ZGRjNGQ1NTBlZmZlJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.oKJGcOBEp2WSIqC-Qov_0Jyq-aJmFJ_5x6vFcFSRipk)
The text was updated successfully, but these errors were encountered: