NAS542 keeps beeping after I Installed a new 16TB disk

Oscwo

Installed a new 16TB HDD (Refurbed) and the NAS just keeps beeping and the new drive does not show up under disks in the UI. From what I could gather online the NAS should support 16TB, right?

If yes, what could be wrong and is there anything I can try?

Edit:

Found nothing to sugest a 16TB drive should not be compatible in the manual.

I have tried restarting the NAS as well as changing bays to a bay I know to be functional…Same beeping…No Drive showing in UI.

Can I confidently send this back to the seller saying the drive is broken or is there anything else to try? I have no other hardware to try the disk with.

Mijzelf

A 16TB disk should be no problem, at least not on this level.

As far as I know there are only 3 reasons why the NAS should start beeping. When the fan doesn't run, when an array is degraded, and when it fails to boot. In all cases you should be able to see it in the webinterface.

Oscwo

Maybe I'm looking in the wrong place but you are saying in: Storage manager > Internal storage > Hard Disk…It should show up in all cases?

Is there any chance my disk is not compatible? The manual said nothing about that.

If not, does that mean the disk is completely broken? I assume it's connecting somehow because of the beeping.

Edit: After 10-15 minutes with the disk in it stops beeping. The disk is not very warm after about one hour inside the NAS.

Mijzelf

Storage manager > Internal storage > Hard Disk…It should show up in all cases?

AFAIK yes.

Is there any chance my disk is not compatible?

You can never rule it out, but normally SATA is SATA.

I assume it's connecting somehow because of the beeping.

Agree. If it isn't recognized as disk, why would it beep anyway? Maybe the kernel log can shine some light. If you enable the SSH server (Somewhere in Network→TCP/IP) you can login over ssh. (ssh admin@<ip-of-nas> on a command prompt) and execute 'dmesg' to see the kernel log.

Oscwo

https://community.zyxel.com/en/discussion/comment/72845#Comment_72845

So I went to Network > Terminal, and enabled the SSH service. What is the next step? How and where do I execute "

ssh admin@<ip-of-nas" ?

Mijzelf

On a command prompt. Also called 'Hackerz screen'. 'cmd' in Windows. On a Mac I don't know. On Linux it's called a 'terminal emulator'.

Oscwo

https://community.zyxel.com/en/discussion/comment/73180#Comment_73180

I think it's "terminal" on a mac but I'm on a Windows PC right now, so what I should do is open cmd and put in "ssh admin@<ip-of-nas>"?

When I do that I get "The syntax of the command is incorrect."

What did I miss?

Mijzelf

What did I miss?

Don't know. I don't use Windows often, and when I use it ssh always works. As far as I remember it is added as default program to W10. But maybe it's a part of Windows which is not installed by default, and has to be enabled.

Anyway, you can also use another ssh client like PuTTY.

Oscwo

https://community.zyxel.com/en/discussion/comment/73202#Comment_73202

I'm not familiar with SSH at all but there is a built in SSH client in windows, it just crashes when I open it with no error message though.

I did connect with some other people on this who thought the issue might be that my new HDD has the 3.3V/power disable function. Do you know if this is a known compatibility issue with Zyxel NASs? None of my other HDDs in the NAS has them so it sounds plausible.

Mijzelf

No, I'm not aware of that. But indeed it sounds plausible. According to this page the PWDIS feature is added to the SATA standard in the begin of 2016. The NSA540 was launched in the end of 2014, so that easily predates it.

The problem arises if the power connector supplies 3.3V on the 3th pin. Don't know if that is the case, but I certainly do know there is 3.3V in the box. The I/O of the CPU runs on 3.3V, so at least the voltage is generated, somewhere.

Maybe you could try to tape-off the 3th pin? That can damage the corresponding connector in the NAS, but when Tom is right, pins 1 and 2 deliver the same signal, and 3.3V isn't used anyway by the disk.

Oscwo

https://community.zyxel.com/en/discussion/comment/73363#Comment_73363

I did try and tape of the connectors but it did not make a difference (I used regular tape tough and not the correct kind so maybe that's why it did not work).

Ended up returning the drive and buying another that did not have the 3.3v function. This one worked with no issues so I still suspect the 3.3v might have been the problem.