大网数据广告活动
服务器运维问答

Synology Storage Manager rejects healthy disks as "Critical" because of "reset commands"?

· 52CE 我爱测

I am trying to install a new HDD in my DS1515+. The hard drives are brand new Seagate Exos X. I have bought 3 of these drives, and 1 of them works fine and is now part of my storage pool, but the other 2 gives me an error when I …

问题原文

原帖链接 · Esben von Buchwald · CC BY-SA 4.0

I am trying to install a new HDD in my DS1515+. The hard drives are brand new Seagate Exos X.

I have bought 3 of these drives, and 1 of them works fine and is now part of my storage pool, but the other 2 gives me an error when I install them in the DS. The error is "Multiple reset command errors have occurred...".

From the Storage Manager, I cannot continue and the system won't let me intialize the disk to make it part of a storage pool. I've tried secure erasing one of the disks, with no luck.

I've looked in the dmesg output from the linux terminal of the DS, with no errors for the disks that cause me trouble.

But I can see in all the extended views that no errors regarding reset/reidentification/reconnection etc have occurred. So why is Storage Manager stuck on the Critical status?

Both disks work completely fine when connected to another computer, so I believe they are physically 100% OK.

I suspect that the disks are rejected by the DS because of some historic data. First, I tried connecting the two problematic disks using the 2 ESATA ports of the DS1515+, but the disks did never appear in the storage manager, and I saw some reset/connection errors in the dmesg log (using the linux terminal). This was probably because of older unstable ESATA cables. But my theory is that these events when the disks were connected by ESATA, has caused the DS to "blacklist" these disks, as they have once caused "reset commands" due to flaky cables.

How can I force the DS to accept these disk and let me use them? Is there a way to reset any historic knowledge about these disks, and let the DS re-evaluate them?

已采纳解答

原帖链接 · Esben von Buchwald · CC BY-SA 4.0

I managed to fix this myself. I was right about the assumption that the unstable ESATA connection a few days ago, made my NAS believe that the drive was faulty.

What I did to fix it:

root@diskstation:/# grep -r ZR52AGQE /var/*
...
Binary file /var/log/synolog/.SYNODISKDB matches
Binary file /var/log/synolog/.SYNODISKHEALTHDB matches
Binary file /var/log/synolog/.SYNODISKTESTDB matches
...

I dumped these databases to SQL files using the sqlite3 commmand line tool, and imported the dumps in a DB on my laptop, and inspected the content.

Then I could see the events of the connections resets from the ESATA connection a few days ago int the logs table

Then I did this

root@diskstation:/var/log/synolog# sqlite3 .SYNODISKDB

DELETE FROM logs WHERE serial = 'ZR51TPNF';
DELETE FROM logs WHERE serial ='ZR52AGQE';

And rebooted the NAS - now it's rebuilding my storage pool to the new disk :)

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2022-03-07)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。