February 24, 201214 yr I've been moving all of my data from my NTFS drives to UNraid, and these errors have occassionally been popping up. I'm moving the files in batches so I have no idea what file exactly is causing the errors. My main concern is if its skipping a file for transfer, in which case I'm going to be missing data when its all done. Sadly, I didn't look at the syslog until now, 3 TB into the transfer, and I've been adding the drives to UNraid after I'm done moving, so if it actually did skip the files, they are gone, and I don't know which ones they were, Feb 24 00:26:59 Media kernel: NTFS-fs error (device sdd2): ntfs_ucstonls(): Unicode name contains characters that cannot be converted to character set iso8859-1. You might want to try to use the mount option nls=utf8. (Errors) Feb 24 00:26:59 Media kernel: NTFS-fs warning (device sdd2): ntfs_filldir(): Skipping unrepresentable inode 0x2e48. (Minor Issues)
February 24, 201214 yr Post full syslog. Do you have an NTFS disk setup in unraid? Use TeraCopy (or any other program that will compare directories) to make sure everything was copied before you delete from the source.
February 24, 201214 yr Author Syslog is attached. There are other errors I'm not sure about, but everything is green and working correctly. Yes I do have a NTFS disk attached, I put all of my harddrives in to transfer content. This is how I've been doing it: Harddrive 1 - Empty Harddrive 2 - NTFS Media Drive(full) Harddrive 3 - NTFS Media Drive(full) Add HDD1 to array Transfer from HDD2 > HDD1 Add HDD2 to array Transfer from HDD3 > HDD2 Add HDD3 to array So if the errors do mean that some files were skipped, they are lost from HDD2 and I'll just have to find them the hard way, hoping to catch it with HDD3 since I haven't added it to the array yet and all my media is still intact. syslog.txt
February 24, 201214 yr I've never trusted the open-source NTFS drivers and have always just used windows and SMB/FTP/SCP to copy files from windows to linux. I would just run rsync to compare the drives and see if it finds anything missing.
February 26, 201214 yr The errors indicate file names with spacial characters that unix does not like.
February 26, 201214 yr Author Yeah I forgot to post back last night, I got it working correctly using nls=utf8. I was putting it in the command but apparently in the wrong place. Instead of kicking out an error it was just ignoring it and going on with the copy. Thanks!
Archived
This topic is now archived and is closed to further replies.