July 16, 201114 yr Caught this while moving some media from an ntfs drive to my array. Not really sure what it means. Any ideas? I'm running Unraid 4.7 Plus. I stopped the transfer after I saw the errors. The drive is a Samsung hd204ui directly connected to the unraid machines board. The media I am moving is tv episodes that were all named by SickBeard on a windows 7 machine. Jul 15 18:07:03 Tower kernel: NTFS driver 2.1.29 [Flags: R/O MODULE]. (System) Jul 15 18:07:03 Tower kernel: NTFS volume version 3.1. (System) Jul 15 18:12:51 Tower kernel: NTFS-fs error (device sde1): 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) Jul 15 18:12:51 Tower kernel: NTFS-fs warning (device sde1): ntfs_filldir(): Skipping unrepresentable inode 0x1bd0. (Minor Issues) Jul 15 18:12:51 Tower kernel: NTFS-fs error (device sde1): 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) Jul 15 18:12:51 Tower kernel: NTFS-fs warning (device sde1): ntfs_filldir(): Skipping unrepresentable inode 0x1bd1. (Minor Issues) Jul 15 18:12:51 Tower kernel: NTFS-fs error (device sde1): 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) Jul 15 18:12:51 Tower kernel: NTFS-fs warning (device sde1): ntfs_filldir(): Skipping unrepresentable inode 0x1bd2. (Minor Issues) Jul 15 18:12:51 Tower kernel: NTFS-fs error (device sde1): 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) Jul 15 18:12:51 Tower kernel: NTFS-fs warning (device sde1): ntfs_filldir(): Skipping unrepresentable inode 0x20e7. (Minor Issues) Jul 15 18:12:51 Tower kernel: NTFS-fs error (device sde1): 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) Jul 15 18:12:51 Tower kernel: NTFS-fs warning (device sde1): ntfs_filldir(): Skipping unrepresentable inode 0x20e8. (Minor Issues) I am using this command to mount: mount -r -t ntfs /dev/sdX /mnt/imported_files How would I change it to use the nls=utf8 option? I didn't notice the log area when transferring my movies, I hope those transferred ok. Thanks for any help.
July 18, 201114 yr I would guess that there are some directory or file names on the NTFS drive that have "odd characters" in them. If you can put the drive back into a Windows box look for things like accented characters (or worse yet, things like the Chinese characters) and then you might be able to work around the issue by editing the names to remove the odd characters. If its just media (and not installed programs) then this shouldn't break anything. Regards, Stephen
July 18, 201114 yr Author I hate to BUMP but.... see here: http://tinyurl.com/4xbrbz2 Your google-fu must be stronger than mine. I might be a worthless sack of blood and bone but I did google before posting. Oh and please don't bother going and posting your google results to make me look even more like an ass. I would go on but i'm sure it would be a waste of key strokes. VCA thank you for your reply. I really appreciate it. I will check into that, though I do not believe there are any odd characters since they were all named by sick beard which as far as I know uses "regular" characters.
July 18, 201114 yr I hate to BUMP but.... see here: http://tinyurl.com/4xbrbz2 Your google-fu must be stronger than mine. I might be a worthless sack of blood and bone but I did google before posting. Oh and please don't bother going and posting your google results to make me look even more like an ass. I would go on but i'm sure it would be a waste of key strokes. VCA thank you for your reply. I really appreciate it. I will check into that, though I do not believe there are any odd characters since they were all named by sick beard which as far as I know uses "regular" characters. I never said you were "worthless", just that the post you made suggested using the "mount" option, and it is not too hard to locate using a google search. Now, there may be other issues, as the utf8 character set might not be defined in the version of unRAID you are using. I've no idea. I've never tried that option. furthermore, it might not be recognized by the read-only driver in unRAID... although if it is what is complaining, it should. Try: umount /mnt/imported_files mount -r -o nls=utf8 -t ntfs /dev/sdX /mnt/imported_files
July 18, 201114 yr Author I hate to BUMP but.... see here: http://tinyurl.com/4xbrbz2 Your google-fu must be stronger than mine. I might be a worthless sack of blood and bone but I did google before posting. Oh and please don't bother going and posting your google results to make me look even more like an ass. I would go on but i'm sure it would be a waste of key strokes. VCA thank you for your reply. I really appreciate it. I will check into that, though I do not believe there are any odd characters since they were all named by sick beard which as far as I know uses "regular" characters. I never said you were "worthless", just that the post you made suggested using the "mount" option, and it is not too hard to locate using a google search. Now, there may be other issues, as the utf8 character set might not be defined in the version of unRAID you are using. I've no idea. I've never tried that option. furthermore, it might not be recognized by the read-only driver in unRAID... although if it is what is complaining, it should. Try: umount /mnt/imported_files mount -r -o nls=utf8 -t ntfs /dev/sdX /mnt/imported_files I never suggested you said it, it's just a fact. I was never able to figure out how to place the option in the string. Your suggestion seems to have stopped it from throwing errors. Thank you very much for you help. I will try to search more thoroughly in the future.
July 31, 201114 yr When we receive this type of error does the file or directory with the corrupted/unreadable name still get transferred? Seems like it would be a daunting task to try and run down exactly which item had the problem, especially with a large data transfer. Thanks. V
Archived
This topic is now archived and is closed to further replies.