HDX SSD Won't Rip

I might be way out of turn here but I think the cd is ripped firstly to the serve then uploaded to the nas. So have you got some cds on the serve which never made it off, filling up the drive?

Gary did you try turning the hdx off and on? 

Garyi, you might be onto something there. I put in a CD to rip before I had my Synology setup, if I remember correctly the HDX SSD looked like it was ripping the CD but it didn't show up. It's possible there is a "ripping queue" on the HDX SSD and mine is full because I tried to rip a CD before my Synology was setup. If this is the case, how do I clear the "rip queue" on the HDX SSD?

Paul, I've been working on this issue for several weeks and have rebooted the entire system several times. The exact error message I get when trying to rip is "Not enough free space to rip the disc (less than 1000MB)". When I check the status of the music store on the HDX SSD touch screen it shows about 1.4TB free space.

When I check the status of the internal hard disc it shows: type-read only, total space 8.388MB, space remaining 799MB and number of albums-0.

I would argue then that your serve cannot get to or rip to the nas and therefore is returning the error message.

Make sure:

On the nas you have create a new share called music or similar. For ease give anyone accessing it full Read/Write privileges without the need of a password (within a LAN environment this is perfectly safe)

On the serve find this new share and promote it to a store.

Start ripping.

The read/write access is essential it might well be promoted to a store, but if it has no privileges to read/write its useless.

Are you following this specific instruction?

"It is important that the Network Share to be converted to a Music Store is either empty or contains only previously ripped files."

This trips up a lot of people.

Try setting a new share with a name that's all lower case with no gaps. The simpler the better. Full admin and guest access.

I have all the privileges set to read/write. The 2 shares I promoted to store were empty. I did add a cd to one of the stores just to see if the HDX SSD would see that file, it did. I guess I could delete my 2 music stores and try again with another new store but I've done that a few days ago with no change. I've tried caps and lower case with my stores already, I'll try a new store which I'll name "amusic".

I remember last year setting up a backup for my UnitiServe.  What a nightmare! There will be something really silly and simple that you are doing wrong - working out what it is is the challenge.

I take it that everything has been working fine with your system for some time and this is a recent, sudden development?  Sounds like something for your dealer and/or Naim to figure out.

Everything as far as playing goes is working fine, I've never been able to rip with this HDX SSD. 

I have an old Synology DS112, thought I would start fresh, put a new hard drive in the DS112 and set it up. I used no password, added all the permissions I found and gave it a few folders that I upgraded to music stores. Same results, rip error of not enough free space, I give up for tonight, thanks to all who responded.

Hi Victor12,

I believe I mailed you back last week saying that if you wanted I could log in to your setup remotely and take a look to see what was going on ... lets get something moving and I'm sure we can get you sorted.

Cheers

Phil

Phil got it fixed for me. Looks like it was a simple matter of the cash being too full on my HDX SSD.

For future reference if anyone else has this problem, first check the free space on the internal SSD by going to "Manage Stores" on the HDX SSD touch screen, select the internal hard drive then select "Status", scroll down, if your free "Space Remaining" is less than 1000MB clearing the cash will probably fix the ripping problem. To clear your cash, launch the Naim Desktop Client on a PC, tap the "Tools" button, then open "Settings & Functions" on the drop down menu, then select "System Functions" then tap the "Purge Images" button. Hope this will help others.

BIG thanks to Phil and all others who posted.

Excellent - it was something simple after all. 

Yes - the 1.7 software shouldn't allow the cache to grow to that size so this should never happen on a 1.7 machine but it looks like this was a 1.6 machine that was updated to 1.7 without clearing down the cache so it was a bit of a one off...

Phil

Presumably this is something that only applies to the SSD versions, and not those with a hard drive inside?

Correct...

Phi