Let say, for example, that you plan to rescue partition /dev/sdb1 (that have bad sectors). If you want an analogy, it’s like losing the map of an unknown country : cities are still there but you don’t know where. Please note that the system can’t access them, but they are physically still present. If the partition table is erased, the OS doesn’t know anymore where the partitions are. It’s used by the BIOS to boot the system, if told to do so with this disk. The beginning of those 512 bytes is the boot loader. It tells the system where the four primary partitions are located. The partition table is located at the end of the first 512 bytes of the hard disk. Please note that for the « screenshots » of this article I used a Linux VM (Ubuntu Server) in VirtualBox. I rescued everything using GNU/Linux, and this is important (in the same way, it’s easier to fix those mistakes with GNU/Linux) You may have crashed / erased stuff with whichever OS you want, it’s not important, it’s for the example. I live under GNU/Linux, so I crashed / erased under GNU/Linux (in a way, it’s easier to make mistake with GNU/Linux ) ). … Okay… Actually I successively crash my own personal data in those three ways… and finally rescued them three times. It serves another purpose : to show you how easy it is to lose data and disk. Thus, in those 3 articles I’ll expose you three different ways of crashing data and disks, and the ways to rescue them. I could show you the recipe on how to rescue your data and disks, but as it mainly depends on the way they are erased / crashed, I will show you in which particular case the rescue I expose can be made.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |