Just tried a new backup, but got this:
Here’s the music store status:
Both discs are 2TB. Could there be a rogue file that is tripping up the backup as it stops after 60 files each time? If so, does the backup start with the latest files added to the music store, as I could delete them?
It could be. And yes it does start from where it left off. Does the “rogue” file play ok?
If I’ve counted back correctly 60 files, it does and so do the ones before and after.
Have you tried the usual Core switch on/off including a full power reboot and then attempted the backup…? Just a thought…
Or, better still, do you have another HDD you could use for a different backup, even if temporary…?
Out of the blue the other week I had my Core indicate a backup issue – not the same as your ‘error’ but telling me ‘No Backup Store Existed’ when I tried to backup, despite being able to see the USB drive OK and it being the very same drive it’s been using for over a year…! Re-inserted the cable a couple of times, put the Core into Standby and waked a few times, still the same….Removed the drive and plugged into a Mac and all seemed fine and normal with the drive, all the backup files present etc…
I was pondering whether to run a Disk Utility check on the HDD, but was unsure if this would cause any additional issue to the Core’s backup structure if there was already some corruption…
I use two separate USB HDD for backups, one of which I store physically elsewhere…So I wasn’t too concerned if this backup was no longer useable for whatever reason – worse case scenario I would wipe the drive and start all over on that HDD….
Ahead of doing that, I thought I’d try the other HDD and ensure that was up to date as I had added files in the few days previously…Plugged in, initiated backup, completed all ok no problem……As a final try before considering anything more serious on the problem backup, I plugged that one back in again – started a backup and completed all ok now…! 
Haven’t a clue what it was all about but it was as if doing the ‘other’ backup cleared the issue in the Core’s head and then everything was back to normal….Have had no issues with further backups since….
Weird!
I have to say, the Core’s backup function does seem to work well but having said that I’ve never had 100% confidence in it for some reason….I think it’s partly due to no form of being able to Verify and check the backups against the source – even a basic checksum indication in the UI would help……It may well be happening in the background for all I know, but it just doesn’t feel as ‘solid’ and robust as say a professional OS backup software like Carbon Copy Cloner.
It doesn’t help also when I notice the number of files being processed and backed up differing across my two HDD backups, even when done straight after one another….and I have no easy way of knowing just what those files were….The mysterious Recycle Bin that seems to appear on both of them, the contents of which are different although mostly contain empty folders, doesn’t aid confidence either…! 
I think at some point I will set up an additional backup routine but using 3rd party backup software, I guess across the LAN…just as an extra safety net….
As ever with backups, you never know all is OK until the time you need it….and with many 1000’s of music files, it’s practically impossible to know everything is back to exactly how it was in the event of a restore – how would you know if just one track was missing or corrupt within an album, until the time you come to play it which could be who knows when….
Let us know how you get on…I’d be curious to know if power off/on clears the issue or indeed if you are able to do another additional backup….Of course, you could have a failed/failing HDD on your backup drive – have you tried looking at it via a PC and verifying it…?
SC
I agree that if something odd and inexplicable with the Core is going on, a full power off, wait, restart routine of the Core does often seem to correct it.
Agree David. Thus I was surprised when it didn’t make any difference to the backup issue I had myself, as described above…Only the undertaking of a separate backup seemed to clear the issue and return things to ‘normal’….
As I said, weird!
SC
Did a Core reset and tried a backup with a different disc. Still getting the error message at file 60, so it isn’t a rogue file as it would be backing up the files on a new disc in a different order!
I am going to take the music store out and plug it into my Mac to see if it has any defects on it. Let’s see what happens.
The Core is actually working as it should as a stream source.
Hmmm…strange!
Do you know if you have any tracks/albums with any unusual characters in the metadata…?
I had a weird event the other week whilst ripping the 2011 remaster of Kate Bush’s Aerial – the track ‘Pi’ showed as the symbol π when it got the metadata from Musicbrainz but everytime it got to that track in the ripping process it would spit the disc out…! I tried numerous times thinking it was a dirty disc or something, driving me nuts…was going to give up, when I had the off the wall idea to disconnect the ethernet so it couldn’t do the initial lookup…the disc then ripped straight through no problem in 2-3mins…! I subsequently reconnected to the LAN, did a manual lookup, applied the metadata and all was fine…! The even weirder thing is I already had the 2006 original version of the album on the Core, though I think it’s metadata may have been sourced initially from Rovi – I had actually changed the meta on that track to the π symbol as that’s how I wanted it and is how it’s shown on the album artwork, but there had never been an issue with the ripping……
Don’t know, but something about the character was seemingly triggering the eject action on the Core during the rip…!
And I’ve also had other weird Core events in the past that stemmed from connection to the net – my Core used to randomly wake from Standby, went on for ages and couldn’t figure out the why…eventually with some detective work and showing some report files to Naim support, it was identified there was a issue with the Rovi API causing the Core to effectively ‘crash’ and provoke a wake-up when it was doing scheduled background lookups at Rovi….
Basically, what I’m saying, is I am at times wary of the Core’s communication to the outside world…!
I would suggest doing the backup without connection to the internet, but of course you need it on the LAN to be able to communicate with the Core and start the backup…if you have an easy way of isolating it from the internet, I’d give it a go just as a test…indulge me!
SC
I may have found offending album. Have deleted and now rebuilding music store. Once that is done will try a backup. Will report back later!
Latest is that the backup is sort of working. It still stops occasionally, so I attach it the Mac to see which album it has got to and delete the album and restart backup. This could take a few days!
Are the files Downloads or Rips…?
Of course, the ‘offending files’ may be no such thing and it’s just the random point of where the backup is getting snagged….
My gut feeling says it’s a failing HDD (on the backup) but then you said you did try another different disc and had the same error failure…?
What do you have internally in the Core…? It could actually be read errors happening there as it’s writing out during the backup process…
Strange…
SC
Files are both downloads and rips. I believe it to be the Core disc that is failing. Have tried another couple of drives for backing up and they all get the same error!
Disc in the Core is a Samsung SSD 870 EVO 2 TB bought late November 2022, so not very impressive for two years use!
Shall persevere with backup until it’s done, even if a bit long winded, then put in the original disc (Seagate 3TB Sata) for the Core and rebuild it.
Yeah might be a plan…even if it ultimately rules out the internal Evo being the issue….
Would be unusual for a issue after just 2 years with a quality SSD, but of course can happen…I also believe there were reported failings of some batches of the Evo a few years back…
If you get your backup complete, then whip it out and perhaps do a check on it (I’m not 100% sure as I’m a Mac guy, but I think there’s also a specific Samsung health check App for their SSDs available on PC)….Even if you ultimately go with another drive and rebuild, would be interesting to confirm it was indeed the current one….
Good luck!
SC
Mac guy here as well! Going to attach it to the iMac and give it a going over with disk utility…!
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
