Path: csiph.com!au2pb.net!feeder.erje.net!1.eu.feeder.erje.net!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Daniel James Newsgroups: comp.sys.ibm.pc.hardware.storage,uk.comp.homebuilt Subject: Re: Cannot access new Seagate external HD Date: Fri, 11 Sep 2015 15:17:24 +0100 Organization: A noiseless patient Spider Lines: 37 Message-ID: References: <20150910195028.47fc71c7@chronos.eternal-september.org> <3up4vadvns3th83rljvqq7enak5d0h01l8@4ax.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Injection-Info: mx02.eternal-september.org; posting-host="e16147c885e59d133f2ef7d44168f0c1"; logging-data="13351"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+lcl/am/6pSuzmYZmvRp2D" X-Newsreader: Virtual Access Open Source http://www.virtual-access.org/ Cancel-Lock: sha1:4J4xAHVeOl1kBLfPid/CZTE/rtg= Xref: csiph.com comp.sys.ibm.pc.hardware.storage:6409 uk.comp.homebuilt:40293 In article <3up4vadvns3th83rljvqq7enak5d0h01l8@4ax.com>, Terry Pinnell wrote: > I immediately started an overnight copy from K: (the slightly suspect > 6-year old drive) to F: (the new, precautionary Seagate 2 TB). I was > surprised to see this message on my screen this morning: > https://dl.dropboxusercontent.com/u/4019461/FilenameTooLong-1.jpg I think Windows is complaining about the full pathname being too long, not just the name of the file within the directory. > And it wasn't being asked to 'remove' it. Are you using a "move" command to copy these files to the new drive? That will mean that Windows has to copy the files and then delete them from the old drive. It looks like the "copy" part has worked, but (for some reason known only in Redmond) the "delete" part specifies the filename in a different way (absolute rather than relative path) and so fails. > Anyway I then re-started the copy (on the largest subfolder this time) > and soon got another message: > https://dl.dropboxusercontent.com/u/4019461/FolderNotEmpty-1.jpg Again, this seems to be because you're doing a "move", so the old files have to be deleted. Windows is complaining that it can't delete that directory because it isn't empty. If that was the folder that contained the file that wasn't deleted because of the "filename too long" thing, then that's your reason. Otherwise there's some other file in that directory that wasn't deleted ... for some unknown reason. Maybe permissions? Maybe a file with alternate data streams? -- Cheers, Daniel.