Hi, 

 

I just tried to replace my old 4TB Seagate IronWolf with a 10TB WD Red Plus. However, the device is making a chirping(?) sound, which persists even after trying to reseat the drive multiple times. 

 

Because of some issue, I'm unable to mount the drive on Unraid. 

 

diagnostics are attached.

 

Thank you!

tower-diagnostics-20221130-0903.zip

No SMART report for sdi DN7M which I think must be the disk you are referring to.

 

26 minutes ago, joshsalvi said:

device is making a chirping(?) sound

Sometimes bad power will cause this.

 

Check all connections, SATA and power, both ends, including splitters.

 

Then post new diagnostics.

 

Hi, 

Thank you - I tried re-seating the device multiple times, and when I placed the old 4TB HDD back in the same NAS bay, the 4TB HDD worked just fine. Perhaps this is a faulty drive? 

 

There's also another two-pin header on the back of the drive, which my Seagate drives do not have, so I wonder if that is just a diagnostic port, or if I need to connect something there too?

 

 

1 hour ago, trurl said:

Check all connections, SATA and power, both ends, including splitters.

Did you?

1 hour ago, joshsalvi said:

when I placed the old 4TB HDD back in the same NAS bay, the 4TB HDD worked just fine

What do you mean it worked? In what way? What evidence do you have that it was working?

I was able to assign / mount the old 4TB HDD, and the array started up just fine.

 

I was not able to do this with the new 10TB HDD. 

5 minutes ago, joshsalvi said:

I was able to assign / mount the old 4TB HDD, and the array started up just fine

Still not clear what you mean.

 

Reassigned it (as disk2?) and rebuilt? Or with New Config? Or mounted it as Unassigned Device?

Here's what I was initially doing:

 

Initial Steps to Change a Disk in the Array

1. Stopped the array
2. Unassigned the 4TB disk (disk2) - Disk2 is then listed as "missing" (which is expected, I'm essentially following the steps here: https://wiki.unraid.net/Replacing_a_Data_Drive)
3. Shut downoff the server

Adding new disk to array:

1. Pulled out the 4TB disk (formerly disk2).
2. Inserted the new 10TB disk in the same location (thus, it will be rebuilt as the new disk2)
3. Powered on the server. 

ERROR Arose Here!

• Upon powering on the server with the new 10TB disk replacing the 4TB, the 10TB disk made a strange "chirping" noise. 
• The server successfully booted, and disk2 was listed as "missing", as per the plan.
• When I went to to assign the 10TB disk as disk2, I was unable to do so. What happened was that I saw the 10TB disk in the dropdown menu for disk2, but when I clicked on the 10TB disk, the 10TB disk then disappeared from the list. 
• The 10TB disk was listed as being on standby under Unassigned Devices. 
• After multiple attempts (rebooting, powering down and checking the drive and cables to ensure a good connection), the same issues occurred (chirping on boot, then unable to assign the disk OR complete a SMART test). The disk logs were filled with errors, which I believe should be in the syslog. 
• It was at this point I sent my initial message on this forum.

Reverting the process:

1. Powered down the server
2. Pulled the 10TB disk
3. Inserted the old 4TB in the same location
4. Powered on the server - there was no chirping
5. Reassigned the 4TB disk as disk2
6. Started the array

At this point, the server was functioning normally as it was before. There were previously no issues with the 4TB disk. 

Edited November 30, 20223 yr by joshsalvi

5 minutes ago, joshsalvi said:

• Reassigned the 4TB disk as disk2
• Started the array

So it is rebuilding disk2 to that original disk now?

7 minutes ago, trurl said:

So it is rebuilding disk2 to that original disk now?

NVM

 

It appears you never started the array without the original disk assigned so it doesn't know there was any change to drive assignments.

 

Still wondering about power connection though. Might seem OK with one disk and not the other. How is it connected to power? Any splitters?