This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
haas:spring2016:unix:projects:udr1 [2016/03/15 12:07] – [Backstory] wedge | haas:spring2016:unix:projects:udr1 [2016/03/15 13:37] (current) – [Partition Layout] wedge | ||
---|---|---|---|
Line 21: | Line 21: | ||
Turns out this one had a few tricks up its sleeve. Of particular note: partition scrambling. Oh no! All the memes! | Turns out this one had a few tricks up its sleeve. Of particular note: partition scrambling. Oh no! All the memes! | ||
- | After downing two Mr. Pibbs and a pack of Necco Wafers (saving the purple ones for last), you sit down to correct your most grievous of oversights. Chiptunes blazing, extra monitors displaying terminals covering nearly every square decimeter of desk space, you have a hard drive partition map to restore. | + | After downing two Mr. Pibbs, a Mars bar, and a pack of Necco Wafers (saving the purple ones for last), you sit down to correct your most grievous of oversights. Chiptunes blazing, |
Turns out there was at least **some** redundancy... a backup of the partition table/ | Turns out there was at least **some** redundancy... a backup of the partition table/ | ||
Line 57: | Line 57: | ||
=====Process===== | =====Process===== | ||
- | In order to gain access to the drive (in the form of the file called **disk.image**, | + | In order to gain access to the drive (in the form of the file called **disk.image**, |
- | There is a backup stored on the drive... you were informed of its location when you successfully ran prep. Extract | + | There is a backup stored on the drive... you were informed of its location when you successfully ran **prep**. Obtain |
- | Once you have it, you'll want to restore it onto the drive; it occupies | + | Once you have it, you'll want to restore it onto the drive; it needs to occupy |
Once you have that in place, we can use a hex editor to study the partition table and determine the starting sectors and overall sizes of each partition. | Once you have that in place, we can use a hex editor to study the partition table and determine the starting sectors and overall sizes of each partition. | ||
- | You'll want to extract each partition individually from the disk image so you can better interact with it. You'll need to determine the partition type and ensure a filesystem is in place. Ultimately you'll want to be able to view and copy data to/from the various partitions. | + | You'll want to extract each partition individually from the disk image so you can better interact with it. You'll need to determine the partition type and ensure a viable |
- | As this is a disk image of the chief meme archivist' | + | To facilitate your efforts, please name each extracted partition files as follows: |
+ | |||
+ | * partition #1: **udr1.part1.img** | ||
+ | * if there' | ||
+ | * if there' | ||
+ | * if there' | ||
+ | |||
+ | As this is a disk image of the chief meme archivist' | ||
Finally, reintegrating the changed fourth partition over the old one, so that you can submit the whole restored image, along with a list of command-lines you performed (and other information gathered) to accomplish this task. | Finally, reintegrating the changed fourth partition over the old one, so that you can submit the whole restored image, along with a list of command-lines you performed (and other information gathered) to accomplish this task. | ||
Line 95: | Line 102: | ||
====Partition Layout==== | ====Partition Layout==== | ||
A partition is defined in 16 bytes (the classic PC layout allows for four primary partitions). The byte layout is as follows: | A partition is defined in 16 bytes (the classic PC layout allows for four primary partitions). The byte layout is as follows: | ||
- | |||
- | Structure of a 16-byte Partition Table Entry | ||
- | Relative Offsets | ||
- | (within entry) | ||
- | Length | ||
- | (bytes) | ||
- | Contents | ||
^ Byte ^ Description | ^ Byte ^ Description |