I think I had just four albums with corrupt media. I'll give it a whirl, but with over 6,000 albums it seems strange that it keeps failing so regularly so early on on the process. It's got to 124 of 5978 this morning but I suspect that's because I'm at the computer.
Sooloos, Roon, G series (with LPS upgrade), 800 series (with LPS upgrade), HD621, AC200, Prime and PS, DSPs old and new.
Have you tried doing a forensic focus (select focus then the * to get the menu) and looking for corrupt media, if you find any you could exclude them from the backup and try again?
I found one album flagged as corrupt media using Forensics Focus in Core Control. I deleted the album from my MD600. Backup still fails with "Unknown Error".
First post here. I have been lurking in the background for several years and have learned a lot from you guys and I appreciate that. Thank You. I never thought I could add much value to the discussions, until I saw this thread the other day, so I registered.
I had the problem outlined by dpstjp and Soundserge for the past 3 1/2 years, and only recently solved it. Everytime I ran a backup, I would get the error screen posted by Soundserge. I would need to keep running the backup routine over and over, sometimes 20 or 30 times, until I got down to one last file that would never be successfully transferred. My dealer rep was unable to solve the problem (and gave up) and said it was likely a corrupt file (which it was).
The Focus, Forensic, Corrupt Media routine showed everything was fine.
I decided to tackle this recently as follows:
First, I made sure one of my backups was current i.e. all files transferred/updated, except that one last file. I attempted to transfer it several times.
I then opened Debug, and went to the Disk, TS, HTTP Server Log screen. I studied this otherwise meaningless information (to me) and noted that the routine had "Shutdown" immediately after the same disc/track several times, so I figured this was the corrupt file. I wrote down the 35 digit album number.
I then went back to Debug and opened the "Album Listing" and "Album IDs" screen. I searched manually for the file number, deleted that album (from my C10) and for the first time in 3 1/2 years was able to get a "backup complete" screen. The corrupt file was a high-def WAV. file I had downloaded from a service in Aug 2010. Ironically, the file played, it just wouldn't transfer.
I suspect there are easier ways to tackle this. You could use the Sooloos Library Interrogator and compare your current library to a backup library. I didn't do this as I am a MAC user and not very Excel literate.
You could also delete your Library and then restore it from Backup, which would eliminate the corrupt file, but you wouldn't know which one(s) it was.
Hope this helps.
Regards Bernardo
MD 600, MS 600, 2x C-15, Emm Labs DAC, Spectral 30SS and 400RS, Wilson Sasha.
My backup completed successfully, at least according to Control:Mac! Thanks again, Bernardo.
Per Bernardo's suggestion I looked at the HTTP log linked under the Disks heading on the Core debug page (in my case 10.0.1.4:9080/debug/http) for clues. There's not much to see but my interpretation is that I was looking at the backup process requesting albums track by track by getting the file size first, then the actual (FLAC) file, and finally doing an additional HEAD request on it. Then I noticed immediately after the backup failed that the last track requested was track 4. Something like this:
DISPATCH : HEAD /Music/music2/album/c2/1b/0101984458ade86a4b4eb0e6640063d2c21b/track04.FLAC
No errors, but no requests for subsequent tracks in the same album either. I also wasn't listening to a track #4. I figured this was the album that the backup process choked on. Then I used the URL above to find out which album this track belonged to by starting here: /Music/music2/album/c2/1b/. Turns out it was S.O.S. Band's Greatest Hits. First I tried tagging this album as Corrupt and creating a Focus that excluded albums tagged as such. Then I ran the backup on albums in that Focus. It still failed. Deleting the album and re-running backup did the trick.
I'll keep an eye on this as a run more backups and I'll also re-import this CD to see what that does.
It appears that this is the solution to the problem posted. One additional thought that May be of benefit. I was reading today about some of the power management features of OSX Mavericks. The default is to put an application into a nap state if it appears to not be actively in use. If you go to Control:Mac in Applications, right click and select get info, there is an option to switch off napping. This might help avoid some of the hanging behavior many have experienced.
Cheers, Ian
Cheers, Ian
1: Roon on Mac Studio, G-Drive 10TB, 818v3, 7200.2, UHD722, LG 77G4 2. 808.6, 8kSE 3. 218, 3200's 4: Rivian R1T - 18 speaker 1200W Elevation by Meridian premium sound system 5. G68ADV (croaked), G98DH (also croaked), [HD621, Syles SL-S/PDIF, MD600 (2*4TB), QNAP 469L (4*3TB), MS200], Ayre MX-R Twenties, TBD