Jump to content

terry1966

Anti-Spyware Brigade
  • Content Count

    9,289
  • Joined

  • Last visited

Posts posted by terry1966


  1. what it shows as raw again in windows? it should have been showing as a 3Tb(about 2.7TB) drive with an empty single partition on it after you did the quick format.

    ok, i don't understand why it's showing as raw still but never mind.

    lets bite the bullet and write the partition and files testdisk found to the drive.

    so analyse efi gpt, quick search, etc until you get here :- image.png.b9404da14f5325f41b1fe035d73ece14.png

    then write.

    now when you look at the drive in windows it should show 1 partition with your data on it.

    :b33r:


  2. what do you see if you hit type?

    at the moment i'm not sure if it's best to just write the files it found and listed to the drive or try and see if it can find the original mft and repair that.

    i'd be a lot happier just writing the files it found if the partition started at 2048 instead of 40, does it look like all your files are there? if so then this might be best option and just write that partition table and filesystem to the drive. you might have some work still to do like search your backup files for the data that's 0kb in size and copy it back to the drive but it should now show in windows as a 3TB drive with most of your data there and useable.

    :b33r:


  3. if i remember correctly in disk management you just right click on the partitions you want to change (same way you resized the 2TB) then click on delete until all the drive shows as free space. then right click on it and click new partition then follow instructions to create 1 new partition using all the space.

    once that's done and it shows up as a single 3tb drive in windows use testdisk to analyse the drive (efi gpt) and post a screenshot of what it shows. then do a quick search and post a screenshot of that too, then we'll see where we go from there.

    :b33r:


  4. at this point, i'd just go into windows disk management delete all the partitions on the drive and create 1x3tb ntfs partition with quick format, then i'd see if testdisk could rebuild the file system on that partition so all your data showed up, if that fails then i'd simply bite the bullet and copy the backup files across even though it means a lot of work sifting through them.

    if you're not worried about the small 8mb partition on the front of the drive , then i'd simply use windows disk management to expand the 2tb partition to use all the empty space on end of drive (maybe try deleting the 8mb partition and seeing if you can expand the new larger partition into it too)then run chkdsk to see if it fixes the 0kb files that are there at the moment.

    and that i'm afraid are only  options i can think of.

    :b33r:


  5. on the one that's highlighted in last screenshot click p to list the files and then if they look ok make it primary and write it to drive.

    see how things look then, maybe run chkdsk too.

    if it won't let you list the files then to be honest i'd call it a day and delete all partitions, create 1 new one and copy your backup files across.

    :b33r:


  6. that's funny, for me it appears right next to that network symbol to share post.

    try a different browser and see what results you get. i'm on linux of course and using firefox browser.

    i'm also using noscrypt, adblockplus and an agent switcher set to firefox on os x.

    :b33r:


  7. what i think you're hoping to find is a partition that says ms data, start sector should be something like 2048 end sector something starting with 586???????

    then check what files are on it and if happy write it to drive then see what shows in windows.

     

    if things still aren't right, to be honest i'd just use windows disk management, delete all partitions do a quick format gpt so it shows a single 3tb ntfs partition then copy over your backup files to it, deleting and/or renaming any that need it.

    :b33r:


  8. was that last screen after doing a deeper search?

     

    if it wasn't i'd first run a deeper search if it was then i'd make it primary anyway even though i'm not happy with it's start sector and write it to drive, and repair bootsector again if needed, then go into windows and see what it shows in disk management and what files are shown, maybe do a chkdsk again on it.

     

    if that didn't put everything 100% back to how it was before the case migration, then i'm out of ideas and don't know what else to try.

     

    :b33r:


  9. i'd just leave every as is for now but if you want just expand the 2TB partition to use all the drive. using easus or windows disk managment makes no difference. don't use that space to create a second partition though whatever you do, and then run chkdsk on it again.

     

    caintry the reason files are found on the unallocated space is because it wasn't always unallocated it was 1 big partition that included the now unallocated partition.

     

    i've no theory of why testdisk is running slow now when checking the gpt partition, like i've said i've never ever used it on a drive that large where gpt was needed.

     

    at the end of the day if we can't get everything reading how it was before the enclosure migration then i'm afraid yes you're going to have to copy over the backup files and overwrite the 0kb files and rename them.

     

    i'm wondering why it shows an unused 8mb partition at the start of the drive, looks wrong to me and i'd expect just one 2tb partition on there, and if at the end of the day we can't fix things and it still shows the unused 8mb partition at the start of the drive, then i'd delete all partitions on there and do a quick gpt format so it shows as just 1 partition for all the drive and then copy all the files over from your backup.

     

     

    2) some of the files (notably the MP4s), are now fragmented and useless in terms of trying to run.

    i think most such files are probably old file left overs from other things that used to be on the drive, when you use file finding software like photorec to find files it doesn't just find files that were shown in windows before the problems it finds files and parts of files of everything that was ever written (and not overwritten after deletion in windows) to the drive, that's why a lot of stuff is junk, and usually where you had say 200GB of real data on there you wanted, after such a search it might find 400GB of data leaving you to go through it and keep what you needed and deleting everything else.

     

     

    I guess I let Quick Search finish its run, and report back with my results?

    yes please, got a feeling you're going to need to do a deep search too, so might as well do that at the same time and report back what that found too, if the searches find a partition that uses all the drive and all your files are on that partition as they were before the enclosure swap then write it to the drive.

     

    :b33r:


  10.  

    If I were to do a quick format of the drive as gpt, that would erase all the files I have on it, correct?

    yes and no.

    yes it would look like there were no files on there in windows but no a quick format doesn't actually delete the data on the drive so the files are still there and it's just windows doesn't know how to find them any more, but if you used photorec or the other windows program you originally used to find and backup the files it would still find them. testdisk should also still be able to find the files and fix things again so windows sees them and shows a 3TB drive.

     

     

    In this case, should I start with looking at the boot sector? I'm unclear as to what I'd be looking for after I chose EFI GPT instead of Intel.

    i'd think you'd choose the same options as if you started with the intel option, analyse, show files, etc.

    like i said earlier haven't actually used testdisk on a gpt drive and it's been a very long time since i've used testdisk at all now.

     

    As it stands right now I have complete access to the drive and all its folders. It's just that some of the files are listed at 0 kb instead of their correct file sizes, and these particular files won't open when I click on them. The majority of files do list the correct file size, and run fine when I click on them.

    if you're happy with how things are at the moment and just want to see a 3TB drive then maybe just converting it to gpt will do that for you. https://www.easeus.com/partition-manager-software/free-convert-mbr-to-gpt-without-data-loss.html

     

     

    Sorry, I guess I phrased that poorly. Yes, originally the HDD had just the one partition. Is it possible that somehow a second partition was created at some point (quite possibly by me accidentally during my attempts with TestDisk), and that it is "lost" and needs finding using Analyse or Deep Search or something? Could that be why that last picture I posted previously shows 3000 GB at the top of it, and 2199 GB at the bottom of it?

    i doubt it because testdisk would show you 2 partitions when you analyse it and if that was the case then i'd think windows (don't use windows myself.) disk management would show you a 3TB drive with at least a 2TB partition and the rest of the drive as empty space but from my understanding it only shows you a 2TB drive which to me means it only sees a mbr(basic) 2TB drive where it should see a gpt 3TB drive.

     

     

    ETA: for what it's worth, TestDisk has always detected an "Intel" partition table every time I've run the program. It has not once detected an EFI GPT partition map.

    i'm wondering if the enclosure you bought is capable of using hard drives greater than 2TB not all are, but if it is then i'd think not seeing the drive as gpt for some reason in the first place is why you had the problems to start with.

     

    :b33r:


  11. ok. i didn't notice/realize it was a 3TB drive, which means it was formatted as a gpt drive, and because windows now sees it as a 2 TB drive i think it must be seen as formatted with mbr and not gpt partition table now.

     

    i've never used testdisk on a gpt drive so don't know what exactly caused this issue, at a guess i think it must be choosing the wrong partition table type to analyse it in the first place, i'm also not sure if we can still repair it now, especially as chkdsk made changes to the files by the looks of things, so all data is seen and usable exactly like it was in the old enclosure.

     

    the way i see it is you have 2 choices.

    first is to just use windows to delete the partition and then do a quick format of the drive as gpt so windows now see's it as a 3TB drive and simple use it.

     

    second is to continue using testdisk to analyse the drive but this time using efi gpt and not intel partition table and see if it can find and repair things. might even need to rebuild the bootsector again.

    you may need to run chldsk again when windows sees it as a 3TB drive with all your files and see if it will put things back to how they were before it made the changes it did when it saw the drive as 2TB, then again you may not if everything is seen and works. (you could try this second option even after doing the first.)

     

    :b33r:

     

     

    But it was never actually partitioned in the first place,

    all drives are partitioned, they won't store data otherwise. you may not have partitioned it or formatted it yourself, but all drives need to be formatted and a single partition created before they can be used to store your data.

     

    think of it like this,

    a hard drive is a flatpack filing cabinet, useless until built.

    formatting is building the filing cabinet but it still doesn't have any draws to hold your paper work/data yet.

    partitioning is building the draws and inserting them into the filing cabinet. so now you have everything needed to store your paper work/data.

     

    good thing about a hard drive compared to a filing cabinet though, is you can easily change the layout and number of draws available to you at any time. :mrgreen:


  12. on a windows system chkdsk is always the first and easiest thing to run, and if it can't fix the problem then move onto other software.

     

    :b33r:

     

    forgot to say the seatools long test may not show up because it also see's the drive as raw and unformatted. which with luck you'll be able to fix either by running chkdsk or testdisk which i have used at least once to fix the exact same issue you're having where a hd showed as raw without losing anything on it, was a long time ago but if memory serves all i had to do was repair the boot sector from it's backup. http://www.cgsecurity.org/wiki/TestDisk_Step_By_Step#NTFS_Boot_sector_recovery


  13. once you have backed up your files using whatever software and chkdsk doesn't fix the problem then i'd suggest trying to fix the hard drive using photorecs companion software testdisk.

    step by step guide. :- http://www.cgsecurity.org/wiki/TestDisk_Step_By_Step

     

    with luck this will fix the corrupted partition/file tables and you will now have the drive back exactly how it was in the old enclosure but now in the new enclosure with all your files still on it and readable.

     

    :b33r:


  14. the 2d score difference is down to screen resolution difference. Rmegi7 is running a lower screen resolution at 1920x1080 so will score higher in the pit test video score and that's why the pit test is not really a reliable test for comparing a systems performance. you can score a lot more video points just by running low resolution and low bit colour.

     

    they are both very very nice systems and i'm totally envious of you both. :clap:

     

    :b33r:


  15. you need a motherboard with the correct socket type for the cpu, so for ryzen am4 cpu's you need an am4 socket motherboard. :- https://www.singular.com.cy/motherboards/motherboard-amd-socket-am4/

     

     

    I can install heat-sink and fan but WITH-OUT put the THERMAL INTERFACE MATERIAL for test, and after ready to install OS put this material, attach heat sink and fan, open PC, if again all ok install the OS?

    no, you always install the cpu and fit the heatsink and fan with thermal paste, then never remove heatsink and fan unless you have a problem. thermal paste will probably already be applied to the bottom of the heatsink and will just need fitting if not then you will need to add thermal paste before fitting the heatsink.

     

    how to build a pc :-

     

    :b33r:

     

    just for info.

    from my understanding with amd ryzen cpu's if the code ends with box it comes with heatsink and fan and if it ends with wof then there is no heatsink and fan included so you will need to buy one as well.

    so looks like all the x family cpu's don't come with a heatsink and fan same as all new intel k cpu's don't.


  16. just for added info to give an idea about differences between i5's and ryzen cpu's.

    best rendering cpu :- https://www.cgdirector.com/best-cpu-for-rendering/

     

    notice i5 7600k only scores 710 while ryzen r5 1600x scores 1136

     

    the cost of the i5 is 280.27 euros and the ryzen costs 292.08 euros from the site you linked.

    https://www.singular.com.cy/intel-cpu-intel-1151-i5-7600k-3-8ghz-kaby-lake-bx80677i57600k.html

    https://www.singular.com.cy/amd-cpu-amd-am4-ryzen-5-1600x-yd160xbcaewof.html

     

    :b33r:

×
×
  • Create New...