deleted some missing volumes from win disk management
Posted: 17 Feb 2019, 05:44
recomend testdisk incorperate the date-time into log file name.
re-writing the log everytime seems primitive doesnt it?
are you sure you people know what your're doing?
if i had yesterdays log it would explain my mistake.
i cant.
recovered wrong partition i guess.
hello, i made a bit of a pickle with my 4TB Seagate running on MBR bios in WinXP x64.
I know, I know,.. its time to upgrade OS but its on the todo list ok?
I somehow had it partitioned as one big drive but its unclear if that was a GPT partition OR if i used SEAGATE diskwizard extended capacity driver and created a dynamic disk from the smaller partitions.
a SPANNED volume comprised of the two (or three?) partitions created with Seagate ECM (diskwizard).
so thinking i had disconnected the drive i deleted some missing volumes that were cluttering my disk managment console
its really unclear if the drive was connected. or this is entirely the windows record of the dynamic pairing that was delelted as i did not discover the issue for
some days at the least.
but it was gone , the partitions or the dynamic volume or something made it go away.
i ran testdisk analyse for hours and it came back with two partitions highlighted in green.
one looked big enough to be the entire disk but i am not good with the geometry numbers.
that was identified as partition 1
and also
partition 5 however it was identified as FAT16.
they were green so i chose to WRITE rather than deeper search.
quickly came back with "write error"
i fired up r-studio to see if it would yield clue to the structure info but iot was locked out apparently write protcted by testdisk.\
so after reboot now i see divisions of THREE partitions the first ending at 2TB which suiggest i guess that i went the SEAGATE ECM route
and... only the middle partiton was apparently written or recoverd by that testdisk manuveur.
the MIDDLE partition now has drive letter but unreadable at 600+GB.
i think perhaps fixing ONE item WOULD have corrected the rest but i chose wrong.
perhaps i should have written only the ONE large partiton found by testdisk and the other would have fallen into line.
question now.... DELETE? the newly written partition to make room for the large full partiton?
the smaller partion seems to maybe have BLOCKED the larger from being corrected?
I will be including a shot of the second run at analysing with testdisk.
I have rstudio and easeus partition master also. Hirens and Gandalfs rescue disks and ultimate boot cd.
Apparently now what i need to find is a drive with 4TB free space.
re-writing the log everytime seems primitive doesnt it?
are you sure you people know what your're doing?
if i had yesterdays log it would explain my mistake.
i cant.
recovered wrong partition i guess.
hello, i made a bit of a pickle with my 4TB Seagate running on MBR bios in WinXP x64.
I know, I know,.. its time to upgrade OS but its on the todo list ok?
I somehow had it partitioned as one big drive but its unclear if that was a GPT partition OR if i used SEAGATE diskwizard extended capacity driver and created a dynamic disk from the smaller partitions.
a SPANNED volume comprised of the two (or three?) partitions created with Seagate ECM (diskwizard).
so thinking i had disconnected the drive i deleted some missing volumes that were cluttering my disk managment console
its really unclear if the drive was connected. or this is entirely the windows record of the dynamic pairing that was delelted as i did not discover the issue for
some days at the least.
but it was gone , the partitions or the dynamic volume or something made it go away.
i ran testdisk analyse for hours and it came back with two partitions highlighted in green.
one looked big enough to be the entire disk but i am not good with the geometry numbers.
that was identified as partition 1
and also
partition 5 however it was identified as FAT16.
they were green so i chose to WRITE rather than deeper search.
quickly came back with "write error"
i fired up r-studio to see if it would yield clue to the structure info but iot was locked out apparently write protcted by testdisk.\
so after reboot now i see divisions of THREE partitions the first ending at 2TB which suiggest i guess that i went the SEAGATE ECM route
and... only the middle partiton was apparently written or recoverd by that testdisk manuveur.
the MIDDLE partition now has drive letter but unreadable at 600+GB.
i think perhaps fixing ONE item WOULD have corrected the rest but i chose wrong.
perhaps i should have written only the ONE large partiton found by testdisk and the other would have fallen into line.
question now.... DELETE? the newly written partition to make room for the large full partiton?
the smaller partion seems to maybe have BLOCKED the larger from being corrected?
I will be including a shot of the second run at analysing with testdisk.
I have rstudio and easeus partition master also. Hirens and Gandalfs rescue disks and ultimate boot cd.
Apparently now what i need to find is a drive with 4TB free space.