![]() Look how smartly the filesystem developers have written ReIsEr2Fs there! The third line, which has 2 and a space, actually contains disk label. I intended to find out the pattern with which a reiserfs superblock starts. $ dd if=/dev/zero of=check-rfs bs=1M count=200 I made a loop device out of it, and did a reiserfs format over it. I quickly made a dummy file of 200M using dd. One thing was for sure - the superblock must begin somewhere near cylinder 3856. I checked the calculations again, yet to no avail. Just data? How could it be that testdisk was lying? I started by dd'ing out from cylinder 3856 about 1MB. Recovering a partition becomes an easy job. It was found lying from cylinders 3856 to 6287.Īnybody who knows a bit about recovery knows that if you know the cylinder numbers, you've solved the problem. Fortunately, testdisk was able to see this partition, and the filenames too. I was particularly interested in recovering a ReiserFS partition, which was 20G in size. One good thing about testdisk is that it lets you peek inside partitions and read filenames. Instead, it asked me to specify which partition is primary, logical or bootable primary. In my case, though testdisk correctly guessed the partitions (it found more than actual ones), it could not guess a proper partition table. Then it shows the guess to the user, who can then choose to write the table or not. Testdisk analyses your disk for lost partitions and tries to guess the correct partition table. I was troubled when the output of cfdisk said that 30G is unusable space, out of my 60G disk.īut, I thought its just another routine partition table corruption, and I had a tool in my swiss-army knife - testdisk ( ). The grub-install would refuse, and so would the grub. ![]() As the laptop went through a series of installations, Ubuntu or Windows, the abnormality showed up.Īfter installing Windows, I found hard to install GRUB on MBR. The cylinder numbers and sizes and all, but I never cared. It just didn't have the right feel about it. Sorry if I asked a silly question, I am still learning Any kind of help would be much much appreciated.The partition table on my sister's laptop always seemed fishy to me. This is a screenshot showing what I mean. I am worried now and don't know if that's normal or not, and what should I do? This is my first time trying to recover data and also the first time I use TestDisk. However after leaving it for sometime I saw some errors were prompted, the main progress percentage stopped and another percentage was increasing alongside with another numbers other than the "380/121600" appeared and they started to increase too. Everything was fine, it was displaying : Analyse cylinder 380/121600: 00%, and gradually increasing. I opened "testdisk_win.exe" and chose: create > Disk dev/sdb - 1000 GB / 931 GIB - HGST HTS721010A9E630 >. So I decided to use TestDisk to recover my Data. I confirmed that there is data using a program called DiskGenius. However now the drive is showing as Raw (Healthy). I accidentally formatted it and I panicked and cancelled the format then immediately restarted my PC. I have a 1TB dedicated drive in my laptop that is running windows 10.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |