[HELP]Partition is not accessible

[kalashnikova]

I using dual boot for my laptop(windows&ubuntu), 2 days ago, when i use ubuntu, i copied a .mpeg file to windows partition using command "#cp /home/klash/video.mpeg /dev/sda2" in terminal(ubuntu detected my D partition as /dev/sda2) , but when i logged on into windows and try to access partition D(/dev/sda2 in ubuntu), there is a pop up window appear, to tell that my D partition is needed to be format, i pretended to not format it, and try to recover my data, so i pressed cancel button and new pop up window appear
"Location is not available
D:\ is not accessible.
The volume does not contain a recognized file system.."
my question is, can i get my data back? ,there is a important file that i need to,

i tried all recover tools like, easus,stellar,getdataback,testdisk,iRecover to recover my data, but it just 30% data that can be recovered, please help me
and, sorry for my bad english

[bcometa]

Try UFS Explorer and Rstudio.

[labtech]

What model drive is this? See MDL label.

[aicm]

right follow bcometa....
no need of model or f/w.


-aicm

[labtech]

right follow bcometa....
no need of model or f/w.


-aicm

If can only get 30% with GDB, then will not be able to get more with any other tool. There is something else going on. Bads, heads, translator, etc.

Just know that the more you scan from now on, the higher the chances of killing your drive.

[bcometa]

If can only get 30% with GDB, then will not be able to get more with any other tool.

I may be wrong, but GDB (and most or all of the other software he listed) doesn't work on Linux (the D drive which is "bad"), so it makes sense that Rstudio or UFS could get back more, since they both support Linux drives. No?

Just know that the more you scan from now on, the higher the chances of killing your drive.

This is very true. If your data is important and can't be lost, may want to send out to a data recovery company.

[labtech]

Yes, that is true. If it is ext3,4 file system, then GDB will not find it as it does not support those.

But then I wonder why the OP chose to run GDB?!

Also, if it an ext3,4, then it makes sense that Windows does not recognize it.

Seems like more explaining is needed.

[Vulcan]

@labtech,

Seems like more explaining is needed.

Agreed - the OP needs to give more details about the filesystem type(s) involved.

As I read it, the OP said that the (now corrupted) /dev/sda2 partition was their "windows partition" and hence it will likely be formatted as NTFS.

@kalashnikova,

- How big is the /dev/sda2 partition?
- How big is the file /home/klash/video.mpeg?
- Did the copying of that file into the (raw) partition actually finish, or did you interrupt it before it finished?
- What filesystem was used in that partition, before it was corrupted?

[bcometa]

Given his interaction (or lack there of) I think we may be more interested in solving this then OP.

[northwind]

Sometimes this is very frustarating.
Someone asks a question (posting as little details as possible), gets a ton of kind responses from people willing to help, but never returns to give additional details

[bcometa]

yep. if this forum made ppl post 5 times or something in an "introductions" forum, or wait 2 days before posting, we'd probably get more reliable posters.

[olkon]

i tried all recover tools like, easus,stellar,getdataback,testdisk,iRecover to recover my data, but it just 30% data that can be recovered, please help me

Here this command:

Code:

#cp file /dev/sda2

you have beaten file system on /dev/sda2. Would be correct to make so:

Code:

#mount /dev/sda2 /mnt/sda2 && cp file /mnt/sda2


But it so, deviation. A lesson on the future.
Treatment in your case consists in restoration of file system. I would arrive so:
1. Has made an image of a disk

Code:

#dd if=/dev/sda of=/mnt/sdb1/sda.img conv=noerror,sync


2. Has restored file system with the help testdisk

Code:

#testdisk /mnt/sdb1/sda.ing


Further - scanning of an image, search lost fs, restoration fs, result record.
3. Mount the restored parttition from the corrected image

Code:

#kpartx -av `losetup -sf /mnt/sdb1/sda.img`
#mkdir /mnt/windows
#mount /dev/mapper/loop2p2 /mnt/windows


4. Has copied the necessary files

Code:

#cp -R /mnt/windows/* /home/restore/


So I do. You, on the taste, can simplify a problem without creation of an image. But so it will be much more dangerous.

to Vulcan:
Most likely, at it on /dev/sda2 ntfs. As those versions windows which used fat32 would never be established on /dev/sda2, but only on /dev/sda1.

[Vulcan]

to Vulcan:
Most likely, at it on /dev/sda2 ntfs.

Yes, I know I said that myself 2 days ago in this thread...

I was asking this question very clearly (among others) in order to try to get a definite answer from the OP, since another member believed there was a different filesystem type. Unfortunately the OP has not contributed to this thread for several days, so I expect they don't care any more.