UnitiServe-SSD. "updating"

Posted by: Nacho on 15 November 2018

I have a UnitiServe-SSD with 10,000 discs ripped in a Nas Synology. From time to time he goes into "updating" mode and brings about four or more  days to complete the process. While in "updating" mode I can not rip.

The question is whether the process can be stopped without harming the system and how to do it.

Posted on: 15 November 2018 by David Hendon

I suspect that it is looking to get info from AMG (which no longer exists) and it needs time for each look up to time out.

Naim are working on a fix for the AMG issue, so hopefully not too long to wait now.

best

David

Posted on: 15 November 2018 by Richard Morris

My US (not SSD), with nearly 4,000 ripped cds goes into 'updating mode' frequently, usually after restarting, which I have to do frequently because of network issues. However it only takes an hour or so each time. I've never tried to stop it.

Posted on: 15 November 2018 by Nacho

Thank you. I guess with the new Uniti Core there would not be this problem.

Posted on: 15 November 2018 by David Hendon

There isn’t a problem with the Core, because the Core never used AMG. But anyway this issue will get fixed by Naim. I’m a beta tester and I’m not allowed to say anything about what’s going on, but be patient a bit longer.....

By the way the time the updating referred to by the OP takes is related to the number of discs in the lookup data queue not the total number of discs ripped.

best

David

Posted on: 15 November 2018 by Nacho

Thank you very much again. Two issues:
1.- Can I stop the "updating" in some way ?. It takes more than four days and I can not rip.
2.- When does the "updating" start? Does the system do it automatically?
best

Nacho

Posted on: 15 November 2018 by David Hendon
Nacho posted:

Thank you very much again. Two issues:
1.- Can I stop the "updating" in some way ?. It takes more than four days and I can not rip.
2.- When does the "updating" start? Does the system do it automatically?
best

Nacho

I am not an expert on this but I think the answer to 1. Is no and 2. Is yes.

best

David

Posted on: 15 November 2018 by Richard Morris
David Hendon posted:

…By the way the time the updating referred to by the OP takes is related to the number of discs in the lookup data queue not the total number of discs ripped.

best

David

Which leads me to ask the OP - do you have a lot of discs with incomplete data? I don't have any, as far as I know.

Posted on: 15 November 2018 by ChrisSU

My Unitiserve (HDD version) never does this. My library is not that large, but I don’t see that message even briefly. The AMG lookup issue causes a brief one-off delay during the ripping process, then the alternative lookups kick in, and that’s the end of it. So I don’t see why that would cause your issue, unless the subsequent metadata lookups are unsuccessful. Or if you have edited any metadata or files on your music store using a non-Naim interface that would damage the database.