Page 1 of 1
testdisk finds larger disk than used to be
Posted: 28 Dec 2024, 10:12
by rickert
Hi All,
I'm fairly new in this and English is not my native language, but i managed to 'clean' one of my disks, happens to be the one with all my photo's/video's and sort of stuff.
I cleaned it while i was reinstalling windows and wanted to make the windows drive a GPT disk. There were 2 similar disks (in size) and i cleaned the wrong one from the installing menu (using an bootable USB).
Now when using testdisk it finds the disk, shows the correct size (931gb) and analyzes. After that, it seems to tell me that the size of the disk is about 4000gb... and appearantly to small?
I dont understand what it is actually telling me and how i need to retrieve/recover/restore the data on the disk.
I have not allocated a new partition after cleaning. I actually did nothing to the disk other than analyzing trough this software.
I have the log from the test but can't find a way to enclose it (have seen others do it, but i don't understand how to...), and as we speak the software is performing a 'deep search'.
I truly hope you know how i can deal with this, thanks in advance!
Re: testdisk finds larger disk than used to be
Posted: 28 Dec 2024, 12:22
by recuperation
Cleaning is an undefined term.
Please specify exactly what you did!
Re: testdisk finds larger disk than used to be
Posted: 28 Dec 2024, 15:00
by rickert
I wanted to upgrade tot windows 11, but my system disk was still MBR and not GPT (so couldn't install due to secure boot issues). When i started the new win 10 installation, so i could get it to GPT instead of MBR, i accidantly formatted the wrong disk.
It was in the screen where you can select to which disk you want to install the OS.
In that same screen i managed to get the disk from MBR to GPT using cmd. I attached de log and a picture from the screen of where i formatted it.
It is not my actual screenshot of the installation, used it from inet.
Re: testdisk finds larger disk than used to be
Posted: 28 Dec 2024, 20:03
by recuperation
rickert wrote: 28 Dec 2024, 15:00
I wanted to upgrade tot windows 11, but my system disk was still MBR and not GPT (so couldn't install due to secure boot issues). When i started the new win 10 installation,
??? You are confusing me. You wanted to install Windows 11 but installed Windows 10?
so i could get it to GPT instead of MBR, i accidantly formatted the wrong disk.
According to the log file you tried to analyse not a disk but a raid array.
It was in the screen where you can select to which disk you want to install the OS.
No it wasn't. You can only format a partition or a volume but not a disk. Whatever you formatted, the untold length of the formatting process determines the extent of the possible dammage.
In that same screen i managed to get the disk from MBR to GPT using cmd. I attached de log and a picture from the screen of where i formatted it.
It is not my actual screenshot of the installation, used it from inet.
I don't understand what you did.
The log file shows the main directory of your RAID array.
I cannot see any dammage.
Use the p-key ("list files") to list, select and copy your content.
Re: testdisk finds larger disk than used to be
Posted: 28 Dec 2024, 23:25
by rickert
[/quote]??? You are confusing me. You wanted to install Windows 11 but installed Windows 10?
well yes, before i could even get to installing win 11, i understood that i needed to turn my disk from win 10 running on mbr, to a running gpt disk. I could find other methods to get it to gpt, but i just couldn't get it to work, so i reinstalled win 10, in which i used the cmd. and Diskpart to convert it to gpt.
so i could get it to GPT instead of MBR, i accidantly formatted the wrong disk.
According to the log file you tried to analyse not a disk but a raid array.
I am not sure what you mean by a 'raid array', but i tried to follow the steps displayed in the manual.
It was in the screen where you can select to which disk you want to install the OS.
No it wasn't. You can only format a partition or a volume but not a disk. Whatever you formatted, the untold length of the formatting process determines the extent of the possible dammage.
I formatted that disk from the button of which is shown in the screenshot, i am no sure if that formats the partition or a volume.
In that same screen i managed to get the disk from MBR to GPT using cmd. I attached de log and a picture from the screen of where i formatted it.
It is not my actual screenshot of the installation, used it from inet.
I don't understand what you did.
The log file shows the main directory of your RAID array.
I cannot see any dammage.
Use the p-key ("list files") to list, select and copy your content.
[/quote]
When i tried to use the P key, it gave an error. At this very moment, am trying with recuva, which had shown me the files which weren't showing to restore the disk. It is actually putting files back (on a different disk after which i can put it where-ever it want). I'll keep it posted here if it worked or not.