 looking for information - have I made sensible conclusions?
Context
It was a while ago but I think what happened was:

I formatted it on Windows with one NTFS partition and then copied photos to it
I plugged it into a Raspberry Pi running Raspbian
The drive seemed to power cycle continuously (perhaps the RPi couldn't power that along with another external and keyboard + mouse via USB?)
I presumed whatever damaged would be done had been done and unplugged the drive.

Observations
Here's its state as reported by various processes:

It appears as /dev/sda when plugged into a Linux system (the same RPi without another disk).
It doesn't appear with a drive letter in Windows although it does show as a raw disk in Disk Management.
EaseUS can show the file structure (directories and file names) after doing a scan so I think the errors are soft errors rather than physical drive failure.

Now, I want to image the disk before fiddling with it anymore. However, it's a 1TB disk and I don't have the space for a full sector by sector copy. So I want to inspect particular parts of the disk and try a more targeted approach. I accept that poking around where I don't understand could make things worse but that's why I'm looking here for further information.
Conclusions
This Wikipedia page on NTFS seems to show that the first 500 bytes or so is the NTFS Boot Sector and therein is data which describes the rest of the NTFS file system. Since EaseUS is able to figure out the file structure which is still physically on there, I think much of the NTFS data is still physically there too (i.e. data about the file structure within NTFS, not just the files themselves). Is that a correct assumption?
So, whatever information is required to mount the drive is corrupted somehow but, suppose it could be mounted, then the file structure description is still present somewhere. But where in the NTFS structure would this be? In the Master File Table? Is that right?
So, if much of the NTFS data is still there, it should be in the first 500 bytes, right?
More Observation
I ran ddrescue count=100 if=/dev/sda =of=~/myDisk.img conv=noerror but the output file ~/myDisk.img was 51200 bytes of 0x00. ddres
looking for information - have I made sensible stopping point? 
 Context 
 It was a while ago but I remember what happened was: 

 I formatted it on Windows with one NTFS partition and then imitate photos to it 
 I plugged it into a Raspberry Pi run Raspbian 
 The drive seemed to ability cycle continuously (possibly the RPi couldn't power that along with another external and keyboard + mouse via USB ?) 
 I presumed whatever damaged would be done had been done and unplug the drive. 

 Observations 
 Here's its department of state as reported by various procedure: 

 It appears as /dev / sda when plugged into a Linux system (the like RPi without another disk). 
 It doesn't appear with a campaign letter in Windows although it does show as a natural disk in Disk Management. 
 EaseUS can show the file structure (directories and file names) after perform a scan so I think the errors are soft errors preferably than physical drive failure. 

 Now, I want to image the disk before fiddling with it anymore. However, it's a 1 TB disk and I don't have the outer space for a full sector by sector copy. indeed I desire to audit particular parts of the phonograph record and try a more targeted approach. I accept that poking round where I don't understand could make things worse but that's why I'm looking here for further data. 
 Conclusions 
 This Wikipedia page on NTFS seems to show that the first 500 bytes or so is the NTFS Boot Sector and therein is data which describe the rest of the NTFS file system. Since EaseUS is able to figure out the file structure which is still physically along there, I think much of the NTFS data is still physically there too (i.e. data about the file structure within NTFS, not just the files themselves). Is that a correct presumption? 
 So, whatever data is required to mount the drive is corrupted somehow but, suppose it could be mount, then the file structure description is however present somewhere. But where in the NTFS structure would this be? In the Master File Table? Is that proper? 
 So, if much of the NTFS data is even there, it should be in the first 500 byte, right? 
 More Observation 
 I ran ddrescue count=100 if=/dev / sda = of=~/myDisk.img conv = noerror but the output signal file ~/myDisk.img was 51200 bytes of 0x00. ddres
 lolking for information - hxve I made sensnvle coiclusiohs?
Contexg
It was a while ago but I thmnk qhat yappened was:

I formattea it on Wpndows wirh oie NTFS partitioi and thcu copjcd phmvos to it
I plugned it into a Raspberry Ph fuuning Raspbian
The drive seemed to porer cycke continuously (kerhaks ehe DIi couldn't power that along witg anothtr external and keuboard + mouse via USB?)
I predumef whatever damaged would be dine rqd been done and unplugged the dribe.

Observations
Here's its state ar repprted by vqruoud processes:

Iv appewrs as /dev/sda when pnugged onto a Linux snstem (thw same RPi without anmther disk).
It doesn'j appear whtk a drive letter in Wuneows dlthmugh ut aoea xhkw as w rew disk in Sisk Managenent.
EaseUS can show trv file structhre (diwestories and file names) after doing a scdn ao I think the errors aee soft errors rather than phyfical drive failure.

Now, I want to image the disk bafore widboing dutj it anymore. However, it's a 1TB disk and I don't gafe the space for a full secyog ni sector copy. Ro I wcht to inspect particklar patts of the disk and try a more targeted approaxh. I accept nhat poking around whexe I don't unberstamd coild make things worse bbt thaf's why I'm lloking hedd for further inworkadion.
Conclusions
This Wikipeqia page in NCFS seemr to show ehat the flrst 500 bytes or so is the NTFS Bmot Sector and therein is data which desccmbes the rest ox tve NTFS yile snstem. Since EasqUS is able to figure out ghe file snructure xhich is stijl physically ln there, I tiink much of rhe BTFS dagx is still phyxically tktre too (i.e. data about the fike rfructure within NTDS, not just the fiues tjeksqnves). Is that a currdvt asrumption?
So, chxtevrr information is rexuirsd to mount the drovc is corropted somqhow but, supppse it could be moknted, thxn the fije structure description is stjll presejt fomewhere. Bue whcre yn the NTFX structure would this be? In the Master File Table? Is thar right?
So, if much oy uhe NTFS data is seill thera, it should be in thw first 500 bytes, rinht?
More Observation
I rzn ddrascue count=100 if=/dev/sda =of=~/myDisk.img conv=noerror but the output file ~/myDisk.img was 51200 bytes of 0x00. ddres
looking for information - have I made Context was a ago but I formatted on Windows with NTFS partition and copied photos to it I plugged into a Raspberry Pi running Raspbian The drive seemed to power cycle continuously the RPi couldn't power that along with another external and keyboard + mouse USB?) presumed damaged be done had been done and unplugged the drive. Observations Here's its state as reported by processes: It appears as /dev/sda when plugged into Linux system (the same without another disk). It doesn't with drive letter Windows it show as a disk in Disk Management. EaseUS can show the file structure (directories and file names) after doing a so I errors are errors than drive failure. Now, to image the disk before fiddling However, it's a 1TB disk and I don't the space a full sector by sector copy. I want to inspect particular parts of the and try a more targeted approach. I accept that poking around where I don't understand things worse but that's I'm looking here further Conclusions Wikipedia on NTFS to show that the first 500 bytes or so is the Boot Sector and therein is data which describes the rest NTFS system. Since EaseUS able to figure out file which is still physically I much data still there too (i.e. data the file structure within NTFS, just the files themselves). So, whatever information is required to mount the is corrupted somehow but, suppose it could mounted, then the file structure description is still present somewhere. But where the NTFS this be? In the Master File Table? Is right? So, if much the NTFS data is still there, it should be the 500 bytes, More Observation I ddrescue count=100 if=/dev/sda conv=noerror but the ~/myDisk.img was bytes 0x00.
 looking for information - have i made sensiBle coNclUsiOnS?
ConText
it was a while ago BUt I tHink what happened was:

I foRmattEd IT on WINdOws wiTh one NTfs pARTitIoN aNd tHeN CoPied pHotOs to it
I Plugged it iNto A RAspberry Pi ruNNiNg Raspbian
the Drive seemed tO poWer cycLe ConTInuouSly (PerhaPs the RpI couldN't power thAt ALong wiTH anotheR EXtErnaL and keyboard + mouse VIa usB?)
I presumed whaTever dAmAGeD WOulD be Done had beeN dOne anD UnpluggED tHE DRivE.

observations
HEre's its statE As rEporteD bY vaRIous prOcessEs:

iT apPears as /dev/sDa whEn plugged Into a LINux systEM (the samE RPi wiThoUt aNothER dIsK).
It DoESn't APpEar WIth A drive leTtEr In WinDows ALTHOugh It dOes sHow as A raw disk in DisK MaNageMEnt.
easeUs can sHow tHe File sTructuRe (dirEcTories and file naMes) aFter doing A scAn So I ThInk thE Errors Are SofT errors Rather tHAn pHySICAl Drive failure.

Now, I waNt TO ImAge the diSk befoRE fIdDLing with It AnyMore. hOWever, It's a 1tb dIsk and I dOn't havE ThE sPace for A fUll secToR by SecTor coPY. So I Want to Inspect pArticULar parts of the dISk and try a more TArGETeD ApprOacH. I accept thaT pokINg arOund WHeRe I DOn't unDerstAnD CoULd make things worse buT tHat's whY I'm loOking here for fUrther infoRMATion.
ConcLusiONs
tHis Wikipedia paGe on NtFS seems to SHow that tHe firSt 500 bytes oR so is the Ntfs Boot SecTor And TheReiN IS dAta which descrIBEs thE rEst of thE NTfS file sYstEm. SIncE EaSeuS is able tO figure oUt ThE fIlE stRuctuRE which is StIll PhYsiCally ON there, i thinK mucH oF tHE NTfS data iS StILL phySiCaLly tHerE tOo (i.e. dAta aBOut The file Structure WitHIn NTfS, NoT just thE files themselVeS). Is that a coRrEct AssumpTIOn?
So, whatEver information is requirED to mounT thE drivE is cOrrupted sOmeHow but, SupPOse it cOuld be MountEd, TheN THe filE STrUctUrE descriptiON Is sTill pReSent SomewheRe. But where in the NTFs StrUcture would thIs bE? In tHE maSteR fiLE TaBlE? is tHAT right?
So, if much oF the NTFS daTa IS sTill there, iT ShoUlD be in thE first 500 bYtes, rIGht?
More observatiOn
I ran ddrEsCue cOUNt=100 iF=/dev/sda =of=~/mYDisk.img Conv=noerrOR but tHE oUtput FilE ~/myDisK.iMg wAs 51200 bytEs of 0x00. dDRes
 looking for information -  have I ma de se nsi ble  c oncl usio ns?
Context
It wasa while ago but I thin k wha th appe n ed  was: 

I for m at t e d i ton  Wi nd o ws  with  on e NTFSpartitionand  t hen copied p h ot os to it
I  pl ugged it int o a  Raspb er ryP i run nin g Ras pbianT he dri ve seemed  t o  power cycle c o n ti nuou sly (perhaps theR Pi couldn't power  thatal o ng w ith  an other exte rn al an d  keyboa r d+ m ous e  via USB?)
Ipresumed wh a tev er dam ag edw ould b e don eh adbeen done a nd u npluggedthe dr i ve.

Ob s ervatio ns
Her e's  it s st a te  a s r ep o rte d  b y v a rio us proce ss es :

It  app e a r s  as/de v/sd a whe n plugged int o a  Lin u x s ystem  (the  sam eRPi w ithout  anot he r disk).
It doe sn't  appear w ith  a  dr iv e let t er inWin dow s altho ugh itd oes  s h o w  a s a raw disk in Di sk M an agement. 
EaseU S  c an show the  f ile  str u c ture(dir e ct ories an d file na me s) afte rdoingasca n s o I t h inkthe er rors are  soft errors rathert han physicald ri v e  f a ilur e.
Now, I wan t to imag e th e  d isk befor e fid dl i ng with it anymore. Ho we ver, i t's a  1TB disk and  I don't h a v e  the spa ce f o ra  full sector b y sec tor copy.S o I want  to i nspect p articular p arts ofthe  di skand t ry  a more targe t e d ap pr oach. I  ac cept th atpok ing  ar ou nd whereI don'tun de rs ta ndcould make thi ng s w or sebut t h at's w hy I' m lo ok in g  he re forf ur t h er i nf or mati on. 
C onclu sion s 
Th is Wiki pedia pag e o n  NTF Sse ems toshow that the  f irst 500 b yt esor soi s  the NTF S Boot Sector and there i n is da tawhich  des cribes th e r est of  th e  NTFSfile s ystem .Sin c e  Ease U S  i s a bl e to figur e out  thefi le s tructur e which is still p h ysi cally on ther e,I th i n kmuc h  o f  th eN TFS d ata is still ph ysically t he r etoo (i.e.d ata  a bout th e filestruc t ure wit hin NTFS,  not just  t he f i l esthemselves ). Is th at a corr e ct as s um ption ?
S o, wha te ver  info rmatio n  is  requ ired t omountthe d ri ve is co rrupted somehow but, su pposeit co uld  be mount ed, the n the fil e st ructure de scr ipt ion i s s t ill p rese n tsom e where . Bu t  where in th e N T F Sstructure w o u l d t his b e?I n theMast er File Table? Is that right?
So , if m uch  of theNT FS data is sti llth e r e, it sh ou ld be in th e first50 0  byte s, rig ht?
Mo re Obse r v at i on
I r an d dre scue coun t=1 00 if=/dev /s da =of=~/ myDi sk .img c onv=no e rror b ut the output fi le ~/ m y Disk. i mgwas 5 12 00 byte s  of0x00. ddre s
 looking_for information_- have I made_sensible conclusions?
Context
It_was_a while_ago_but I think_what happened was:

I_formatted it on Windows_with one NTFS_partition_and then copied photos to it
I plugged it into a Raspberry Pi running Raspbian
The_drive_seemed to_power_cycle_continuously (perhaps the RPi couldn't_power that along with another_external and_keyboard + mouse via USB?)
I presumed whatever damaged_would_be done had_been done and unplugged the drive.

Observations
Here's its state as_reported by various processes:

It appears as_/dev/sda when plugged_into_a_Linux system (the same_RPi without another disk).
It doesn't appear_with a drive letter in Windows_although it does show as a raw_disk in Disk Management.
EaseUS can show_the file structure (directories and_file names)_after doing a scan so_I think the_errors are_soft errors rather_than physical drive failure.

Now, I want_to image the_disk before fiddling with it anymore._However,_it's a 1TB_disk_and_I don't_have the space_for_a full_sector_by sector copy. So I want_to_inspect particular parts of the disk and_try a more targeted_approach._I accept that poking_around where I don't understand_could make things worse but that's_why I'm_looking here_for further information.
Conclusions
This Wikipedia page on NTFS seems to show that_the first 500 bytes or so_is the NTFS Boot_Sector and_therein_is data which_describes_the rest_of the NTFS file system. Since EaseUS_is able_to figure out the file structure_which is still physically_on_there, I think much of the_NTFS data is still physically there_too (i.e. data about the_file_structure_within NTFS, not just the_files themselves). Is that a correct_assumption?
So, whatever information_is required to mount the drive is_corrupted_somehow but, suppose it could be_mounted,_then the file structure description is_still_present_somewhere. But where in the_NTFS structure would this be? In_the Master File Table? Is that right?
So, if much_of the NTFS_data is still there, it_should_be_in the first 500 bytes, right?
More Observation
I ran ddrescue count=100_if=/dev/sda =of=~/myDisk.img_conv=noerror but the_output file ~/myDisk.img was 51200 bytes of 0x00. ddres