NAS to USB Backup Failures

haroon · ‎02-18-2010

So, I've tried everything to resolve these constant backup failures I get. The 220 reports failures for A) Some files that don't even exist, even as hidden files or B) Some files that do exist that it says do not.

For example, here are a few lines from my iTunes daily backup:

2010/02/21 04:26:07 [16870] .d..tp..... Music/10A - The Cenobites LP (Kool Keith, Godfather Don)/

2010/02/21 04:26:07 [16870] .d...p..... Music/10A - The Cenobites LP (Kool Keith, Godfather Don)/The Cenobites/

2010/02/21 04:26:08 [16870] >f...p..... Music/10A - The Cenobites LP (Kool Keith, Godfather Don)/The Cenobites/04 Mommy.mp3

2010/02/21 04:26:09 [16870] >f...p..... Music/10A - The Cenobites LP (Kool Keith, Godfather Don)/The Cenobites/05 You're late.mp3

2010/02/21 04:26:09 [16870] .d..tp..... Music/10A - The Count Of Monte Cristal/

2010/02/21 04:26:09 [16870] cd+++++++++ Music/10A - The Count Of Monte Cristal/EP2/

2010/02/21 04:26:09 [16870] rsync: stat "/shares/usb1-1.1share1/iTunes Backups/Music/10A - The Count Of Monte Cristal/EP2" failed: No such file or directory (2)

2010/02/21 04:26:10 [16870] >f+++++++++ Music/10A - The Count Of Monte Cristal/EP2/B-More Forward - Original Mix.mp3

2010/02/21 04:26:10 [16870] .d..tp..... Music/10A - The Large Professor/

2010/02/21 04:26:10 [16870] .d...p..... Music/10A - The Large Professor/The LP/

2010/02/21 04:26:11 [16870] >f...p..... Music/10A - The Large Professor/The LP/15 Queens Lounge.mp3

I have thousands of files that get backed up, but probably a hundred errors that -- when tracked down, make no sense.

2010/02/21 04:26:49 [16870] .d...p..... Music/10A -The Travellers/

2010/02/21 04:26:49 [16870] .d...p..... Music/10A -The Travellers/Dusty Fingers Vol.12 (LP)/

2010/02/21 04:26:50 [16870] >f..tp..... Music/10A -The Travellers/Dusty Fingers Vol.12 (LP)/101 Slow Soul.mp3

2010/02/21 04:26:50 [16870] cd+++++++++ Music/10A/

2010/02/21 04:26:50 [16870] rsync: stat "/shares/usb1-1.1share1/iTunes Backups/Music/10A" failed: No such file or directory (2)

2010/02/21 04:26:51 [16870] cd+++++++++ Music/10A/Unknown Album/

2010/02/21 04:26:51 [16870] rsync: recv_generator: mkdir "/shares/usb1-1.1share1/iTunes Backups/Music/10A/Unknown Album" failed: No such file or directory (2)

2010/02/21 04:26:51 [16870] *** Skipping any contents from this failed directory ***

2010/02/21 04:26:51 [16870] .d..tp..... Music/10A_10B - Redbone/

2010/02/21 04:26:51 [16870] .d...p..... Music/10A_10B - Redbone/7_ Single/

2010/02/21 04:26:52 [16870] >f...p..... Music/10A_10B - Redbone/7_ Single/Come and Get Your Love.mp3

Eh, that directory [b]does[/b] exist. Then at the end of it all:

2010/03/02 09:50:09 [24864] >f...p..... TV Shows/WKRP In Cincinnati/Season 1/20 Young Master Carlson.m4v

2010/03/02 09:50:45 [24864] >f..tp..... TV Shows/WKRP In Cincinnati/Season 1/21 Fish Story.m4v

2010/03/02 09:51:24 [24864] >f..tp..... TV Shows/WKRP In Cincinnati/Season 1/22 The Preacher.m4v

2010/03/02 09:51:24 [24864] sent 146635765578 bytes received 235006 bytes 7070713.92 bytes/sec

2010/03/02 09:51:24 [24864] total size is 147673878920 speedup is 1.01

2010/03/02 09:51:24 [24864] rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1040) [sender=3.0.4]

Yeah, so I've looked for unicode, strange characters, spaces -- potential escape sequences -- I really don't know. Another BlackArmor mystery. Any takers? I had this issue with another backup but solved it by removing characters from filenames -- things as simple as an apostrophe were screwing it up. Do I really have to go through like 9000 files to look for characters the BA might bitch about? Meanwhile I can use rsync between two hard drives in Linux or OS X and not get these retarded errors -- with the same exact directories/files.

RAsg · ‎11-09-2007

Hello,

If the errors in the NAS to USB backup log are always the same path, folders and files then I would think the Rsync script running the backup, which we don't have any control over, is setting some environmental variables that can't handle certain attributes, paths, folders or file names, characters, spaces, etc. I would take some of the data in question and copy it to a new folder and back it up from there. Shorten the path, rename folders and files, exclude spaces as needed to try to isolate the causes. I know this type of troubleshooting is frustrating and who really has the time these days but it is probably the best direction to go with it.

At least the bulk of the backup transfers successfully.

Regards,

haroon · ‎02-18-2010

" I would think the Rsync script running the backup, which we don't have any control over"

This is not my rsync script, this is the BA's log.

RAsg · ‎11-09-2007

Hello,

Rsync runs in the BlackArmor NAS and it has backup scripts. When we do a NAS to USB backup the only choices we have to modify that script using the Manager page, is to select which folders to backup and to select the destination usb drive, we can also schedule it. When the backup runs the complete script though it may have variables set in it that doesn't like some of the data structure being selected and thus you get these errors in the Backup Log.

I saw a post online where someone was getting "No such file or directory" running Rsync and his own backup script from a Linux box to a USB drive. No NAS involved. He observed in his backup log that Rsync backed up a folder that was all capital letters and when it wrote the folder on the USB drive it did it with small case letters. When time to transfer the files to the folder it reported, "No such file or directory".

Something similar may be happening here. We just can't tell what it is. I reported this to the BA NAS team to see if they can tell us if there are any limitations to the way they have Rsync setup inside the BA NAS. We will just have to wait and see.
For now the troubleshooting still remains the same from our previous thread.

Regards,

LarryVA · ‎04-05-2010

I"m having the same problem, and frankly am surprised that no one else is. ALl acronym-style directories (FBI, ABA) get created on the backup us 'fbi' or 'aba', and then the file-copy part of the backup fails. I've seen this documented in UNIX/LINUX forums as caused by either an incorrect mount of the volume (wrong parms passed) or an incorrectly called rsync routine, neither of which we have control over on the BlackArmor. Therefore, it is incumbent on the good folks at Seagate to get this fixed for us -- please! The drive is really useless if we can't get a reliable backkup on it.

haroon · ‎02-18-2010

Acronyms, unicode, things with dashes in it, long filenames. What it fails on is almost arbitrary. Seems like you're onto something though. I tried to fix any potential problems at one point, but why bother? The minute I add some new files it will get screwed up again because I've violated some unknown rule Seagate has blessed this device with.

LarryVA · ‎04-05-2010

Very true. You can't taylor your live system use to satisfy some buggy backup method. I use this for business, and need to be able to just rely on a backup that I've verified to be running OK to continue to do so. This just sucks. Any word from Seagate on when a fix is in order? Does no one else care about backing up terabytes of data?

I'm pretty convinced that they just screwed up in their backup script. If we could just edit the scripts, we could get this working, but we're locked out of that. Anyone figure out a hack for this maybe(?) since Seagate is so unresponsive?

AmonReSA · ‎04-15-2010

Having the same problems cant do a backup from nas to usb on my 220 even if its a folder with 1 file! Has anyone found a workaround for this and is this the same regardless of firmware??

rripperr · ‎05-06-2010

The problem is due to files or folders with only capital letters in it. The original poster had a folder named something like "10A" and since all letters in this folder are upper case it generates that error. This will happen with any folder or file if all letters are in upper case even if there is only 1 letter in the name.

The problem is that Seagate using a Linux rsync script that is marketed and labeled in the web interface as a "Backup" which it is NOT. It is a simple script to sync two directories. It is not a good idea or even considered professional to incorporate a Linux tool into a device that will be used mostly in a Windows environment without fully testing it.

Just wait until you all find out that you cannot delete the log file and there is no truncation features used by Seagate either. So your log file will grow until it consumes all available space on your NAS.

Im sure some Seagate Tech will respond saying its not Seagate's fault because they have no control over how rsync works because rsync is a "public Linux project" managed and created by the project team which is not under Seagate's control. To this I say build your own tools, or fully test any free tools you use in your products, and stop false and deceptive marketing specially when it comes to the fake backup tools sold as real backup solutions.

JTR · ‎06-07-2010

I'm not sure the problem is due to capitals - or perhaps there is more than 1 problem. On my system I had OK backups then backup issues started. I had old firmware so updated to the latest and the issues went away. Now the issues have returned. This extract from my (450Mbyte) log shows good backups changing to failing ones but the folders failing were not new or renamed between the backups.

2010/05/19 00:02:16 [17741] sent 96211241403 bytes received 3045243 bytes 5341528.75 bytes/sec

2010/05/19 00:02:16 [17741] total size is 96189284388 speedup is 1.00

2010/05/19 21:45:06 [30519] sent 96213505109 bytes received 2989812 bytes 9921783.44 bytes/sec

2010/05/19 21:45:06 [30519] total size is 96191602609 speedup is 1.00

2010/05/20 21:45:11 [1887] sent 96245439990 bytes received 2990869 bytes 9930196.63 bytes/sec

2010/05/20 21:45:11 [1887] total size is 96223529634 speedup is 1.00

2010/05/21 21:51:06 [7510] sent 96332789569 bytes received 2992247 bytes 9607158.50 bytes/sec

2010/05/21 21:51:06 [7510] total size is 96310863597 speedup is 1.00

2010/05/22 21:46:31 [17306] sent 96332789398 bytes received 2992076 bytes 9872998.36 bytes/sec

2010/05/22 21:46:31 [17306] total size is 96310863597 speedup is 1.00

2010/05/23 21:47:23 [26082] sent 96332789398 bytes received 2992076 bytes 9895309.07 bytes/sec

2010/05/23 21:47:23 [26082] total size is 96310863597 speedup is 1.00

2010/05/24 21:46:04 [19458] sent 96340142729 bytes received 2992662 bytes 9932794.00 bytes/sec

2010/05/24 21:46:04 [19458] total size is 96318214073 speedup is 1.00

2010/05/25 21:44:43 [22304] sent 96374539187 bytes received 2995389 bytes 9955842.63 bytes/sec

2010/05/25 21:44:43 [22304] total size is 96352598247 speedup is 1.00

2010/05/26 19:03:32 [11435] rsync: stat "/shares/usb1-1.2share1/shares/accounts/excel" failed: no such file or directory (2)

2010/05/26 19:03:32 [11435] rsync: recv_generator: mkdir "/shares/usb1-1.2share1/shares/accounts/excel/april 2006" failed: no such file or directory (2)

2010/05/26 19:03:32 [11435] *** skipping any contents from this failed directory ***

2010/05/26 19:04:19 [11435] rsync: stat "/shares/usb1-1.2share1/shares/company/history/ibc2007" failed: no such file or directory (2)

2010/05/26 19:04:19 [11435] rsync: stat "/shares/usb1-1.2share1/shares/company/history/nab06" failed: no such file or directory (2)

2010/05/26 19:04:19 [11435] rsync: recv_generator: mkdir "/shares/usb1-1.2share1/shares/company/history/nab06/nab2006 selected photoes" failed: no such file or directory (2)

2010/05/26 19:04:19 [11435] *** skipping any contents from this failed directory ***