[GH-ISSUE #499] HGST HUS724040ALA640 still not working on DS1512+ with DX513 expansion (DSM 6.2.4-25556 U8) #672

New issue

Closed

opened 2026-03-11 12:59:29 +03:00 by kerem · 3 comments

kerem commented

2026-03-11 12:59:29 +03:00

Owner

Originally created by @MortenCB on GitHub (Jul 31, 2025).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/499

First run (with no parameters):

Second run, with -w and -n:

I have also added the scipt as a startup task as "/volume2/Backups/Synology_HDD_db-3.6.111/syno_hdd_db.sh -n -w --autoupdate=3"

Rebooted many times, it still won't let me add this drive as a hot spare and rebuild my array.

Originally created by @MortenCB on GitHub (Jul 31, 2025). Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/499 <img width="1042" height="277" alt="Image" src="https://github.com/user-attachments/assets/9c0129e3-c7ab-4ab3-8cc9-7a13d72939ae" /> First run (with no parameters): <img width="673" height="1051" alt="Image" src="https://github.com/user-attachments/assets/e2ba3d05-0c72-4461-adc1-ca848007603c" /> Second run, with -w and -n: <img width="703" height="877" alt="Image" src="https://github.com/user-attachments/assets/11feae68-0717-48a0-ad83-2e6880da37ee" /> I have also added the scipt as a startup task as "/volume2/Backups/Synology_HDD_db-3.6.111/syno_hdd_db.sh -n -w --autoupdate=3" Rebooted many times, it still won't let me add this drive as a hot spare and rebuild my array.

kerem closed this issue

2026-03-11 12:59:35 +03:00

kerem commented

2026-03-11 12:59:40 +03:00

Author

Owner

@MortenCB commented on GitHub (Aug 1, 2025):

The drive has been used in a virtual Synology before, with DSM7. Could that have something to do with it? Is there a way to format the drive when the gui says it isn't supported to see if it helps removing the old traces of DSM on it?

@MortenCB commented on GitHub (Aug 1, 2025): The drive has been used in a virtual Synology before, with DSM7. Could that have something to do with it? Is there a way to format the drive when the gui says it isn't supported to see if it helps removing the old traces of DSM on it?

kerem commented

2026-03-11 12:59:45 +03:00

Author

Owner

@MortenCB commented on GitHub (Aug 1, 2025):

Seems like it was some remains from the old Synology that made this Synology say it was not supported. After buying a USB-SATA adapter and connecting it to my computer and removing the partitions, it came up as supported and works fine.

@MortenCB commented on GitHub (Aug 1, 2025): Seems like it was some remains from the old Synology that made this Synology say it was not supported. After buying a USB-SATA adapter and connecting it to my computer and removing the partitions, it came up as supported and works fine.

kerem commented

2026-03-11 12:59:50 +03:00

Author

Owner

@007revad commented on GitHub (Aug 2, 2025):

As you've discovered DSM does not like drives that already has partitions on them.

@007revad commented on GitHub (Aug 2, 2025): As you've discovered DSM does not like drives that already has partitions on them.