Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.sys.ibm.pc.hardware.storage > #6409

Re: Cannot access new Seagate external HD

From Daniel James <daniel@me.invalid>
Newsgroups comp.sys.ibm.pc.hardware.storage, uk.comp.homebuilt
Subject Re: Cannot access new Seagate external HD
Date 2015-09-11 15:17 +0100
Organization A noiseless patient Spider
Message-ID <VA.00000aeb.2ed4480f@me.invalid> (permalink)
References <o2i3vahcmrj3tlsou7lu0cn4e5frk0h9h2@4ax.com> <20150910195028.47fc71c7@chronos.eternal-september.org> <o2l3vapnhfk79s59ds1oe635fr3g1mgd35@4ax.com> <tXcIRsFr9g8VFwqJ@jasper.org.uk> <3up4vadvns3th83rljvqq7enak5d0h01l8@4ax.com>

Cross-posted to 2 groups.

Show all headers | View raw


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.
 

Back to comp.sys.ibm.pc.hardware.storage | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

Cannot access new Seagate external HD Terry Pinnell <me@somewhere.invalid> - 2015-09-10 19:20 +0100
  Re: Cannot access new Seagate external HD Chronos <usenet@chronos.org.uk> - 2015-09-10 19:50 +0100
    Re: Cannot access new Seagate external HD Terry Pinnell <me@somewhere.invalid> - 2015-09-10 20:11 +0100
      Re: Cannot access new Seagate external HD Terry Pinnell <me@somewhere.invalid> - 2015-09-10 20:46 +0100
        Re: Cannot access new Seagate external HD Terry Pinnell <me@somewhere.invalid> - 2015-09-10 21:07 +0100
          Re: Cannot access new Seagate external HD Chronos <usenet@chronos.org.uk> - 2015-09-10 22:10 +0100
          Re: Cannot access new Seagate external HD Mike Tomlinson <mike@jasper.org.uk> - 2015-09-11 00:22 +0100
      Re: Cannot access new Seagate external HD Mike Tomlinson <mike@jasper.org.uk> - 2015-09-11 00:16 +0100
        Re: Cannot access new Seagate external HD Terry Pinnell <me@somewhere.invalid> - 2015-09-11 07:16 +0100
          Re: Cannot access new Seagate external HD Daniel James <daniel@me.invalid> - 2015-09-11 15:17 +0100
          Re: Cannot access new Seagate external HD Shadow <Sh@dow.br> - 2015-09-11 11:30 -0300
          Re: Cannot access new Seagate external HD Mark Perkins <mark@none.invalid> - 2015-09-11 09:35 -0500
            Re: Cannot access new Seagate external HD Mike Tomlinson <mike@jasper.org.uk> - 2015-09-11 21:22 +0100
  Re: Cannot access new Seagate external HD Shadow <Sh@dow.br> - 2015-09-10 16:18 -0300
    Re: Cannot access new Seagate external HD Terry Pinnell <me@somewhere.invalid> - 2015-09-10 21:08 +0100
  Re: Cannot access new Seagate external HD Ed Light <nobody@nobody.there> - 2015-09-10 14:30 -0700
  Re: Cannot access new Seagate external HD micky <NONONOmisc07@bigfoot.com> - 2015-09-10 21:17 -0400
    Re: Cannot access new Seagate external HD Terry Pinnell <me@somewhere.invalid> - 2015-09-11 07:23 +0100
  Re: Cannot access new Seagate external HD VanguardLH <V@nguard.LH> - 2015-09-10 21:11 -0500
    Re: Cannot access new Seagate external HD Daniel James <daniel@me.invalid> - 2015-09-11 15:17 +0100
      Re: Cannot access new Seagate external HD VanguardLH <V@nguard.LH> - 2015-09-12 05:18 -0500
        Re: Cannot access new Seagate external HD Daniel James <daniel@me.invalid> - 2015-09-12 20:46 +0100
          Re: Cannot access new Seagate external HD VanguardLH <V@nguard.LH> - 2015-09-14 04:14 -0500
            Re: Cannot access new Seagate external HD Daniel James <daniel@me.invalid> - 2015-09-14 13:03 +0100
            Re: Cannot access new Seagate external HD Mark Perkins <mark@none.invalid> - 2015-09-14 21:10 -0500
  Re: Cannot access new Seagate external HD Daniel James <daniel@me.invalid> - 2015-09-11 15:17 +0100
    Re: Cannot access new Seagate external HD Terry Pinnell <me@somewhere.invalid> - 2015-09-12 07:05 +0100

csiph-web