Recovering from Recovery CDs - Revision history

Grizz: /* Possible Causes of Failure During Recovery */

2008-07-27T12:50:12Z

‎Possible Causes of Failure During Recovery

2008-03-20T21:58:11Z

‎Possible Causes of Failure During Recovery: Typo

2008-02-04T23:32:57Z

2007-07-18T21:22:53Z

‎How does the recovery process deal with existing partition layouts?

2007-07-18T21:21:54Z

‎How does the recovery process deal with existing partition layouts?

2007-07-18T21:20:58Z

‎How does the recovery process deal with existing partition layouts?

2007-07-18T21:20:47Z

‎How does the recovery process deal with existing partition layouts?

2007-07-18T21:08:54Z

‎How does the recovery process deal with existing partition layouts?: it DOES wipe everything

2007-04-02T08:53:20Z

‎Possible Causes of Failure During Recovery

2006-09-09T02:28:35Z

‎Possible Causes of Failure During Recovery

@@ Line 31: / Line 31: @@
 {{WARN|On my T60 the recovery CDs did not start at all, just a blank screen and no further activity. My guess is that the CDs did not like my partitioning (64MB boot, 2GB swap, 4GB slash, rest extended) but also wasn't able to deal with it or to give any indication of the problem. After booting from a live CD and deleting those partitions manually, the recovery CDs booted as well.}}
 [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-4VFUDU IBMs Official recovery instructions]
 [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=TVAN-SDD&sitestyle=lenovo Deletion Tool to remove a corrupt MBR]

@@ Line 27: / Line 27: @@
 A common problem during recovery *using CD's* is that if the recovery has been started by pressing f12 and choosing the "Boot from CD" the recovery starts fine and it will until the 2nd restart of the machine at which point it hangs / gives error messages of missing files or "unable to initialise" and following recovery attempts will fail with the "unable to initialize" error.
-What happens is that pressing the F12 causes the Boot record to become corrupt, the recovery should -ALLWAYS- be started by changing the boot order in the "startup sequence" of the bios leaving the CDD as the top boot device will ensure a correct recovery.
+What happens is that pressing the F12 causes the Boot record to become corrupt, the recovery should -ALWAYS- be started by changing the boot order in the "startup sequence" of the bios leaving the CDD as the top boot device will ensure a correct recovery.
 failing to do this and thus having a corrupt boot record requires the MBR (Master boot record) to be deleted before running a recovery will work.

@@ Line 29: / Line 29: @@
 What happens is that pressing the F12 causes the Boot record to become corrupt, the recovery should -ALLWAYS- be started by changing the boot order in the "startup sequence" of the bios leaving the CDD as the top boot device will ensure a correct recovery.
 failing to do this and thus having a corrupt boot record requires the MBR (Master boot record) to be deleted before running a recovery will work.
 [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-4VFUDU IBMs Official recovery instructions]
 [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=TVAN-SDD&sitestyle=lenovo Deletion Tool to remove a corrupt MBR]

@@ Line 20: / Line 20: @@
 you have to time this carefully.
 {{WARN|On my Z61m, RnR3 wiped the WHOLE disk when booted from CD and told to install from the IBM-discs}}
-{{WARN|On my T43, the R&R process overwrites the partition table (although not the partitions after the initial 8GB). If you want your linux installation to survive "restore to factory state" from R&R (partition or optical media), write down the partition table on the piece of paper, boot off a live CD, and shrink ntfs partition and restore the original partition table, once the restoration procedure is complete.}}
+{{WARN|On my T43, the R&R process overwrites the partition table (although not the partitions after the initial 8GB). If you want your linux installation to survive "restore to factory state" from R&R (partition or optical media), write down the partition table on a piece of paper, boot off a live CD, shrink the (restored) ntfs partition and restore the original partition table, once the restoration procedure is complete.}}
 ===Possible Causes of Failure During Recovery===

@@ Line 20: / Line 20: @@
 you have to time this carefully.
 {{WARN|On my Z61m, RnR3 wiped the WHOLE disk when booted from CD and told to install from the IBM-discs}}
-{{WARN|On my T43, the R&R process overwrites the partition table (although not the partitions after the initial 8GB). If you want your linux installation to survive "restore to factory state" from R&R (partition or optical media), write down the partition table on the piece of paper}}
+{{WARN|On my T43, the R&R process overwrites the partition table (although not the partitions after the initial 8GB). If you want your linux installation to survive "restore to factory state" from R&R (partition or optical media), write down the partition table on the piece of paper, boot off a live CD, and shrink ntfs partition and restore the original partition table, once the restoration procedure is complete.}}
 ===Possible Causes of Failure During Recovery===

@@ Line 19: / Line 19: @@
 software installs, reduce the swap size and disable hibernation, but
 you have to time this carefully.
 ===Possible Causes of Failure During Recovery===
 The Recovery CDs (shipped from IBM) are a set of up to 8 CDs, one of which is bootable and takes you into an interface almost identical to the [[predesktop area]]. It is possible that when you click "Restore From Factory Contents" (which will actually restore from the other seven CDs), before it begins writing to the hard drive, it may give you an error message that says something like "Restore failed to initialize" and refuse to go further. In my case, completely wiping the hard drive (by booting from a Linux LiveCD and using gnu scrub) fixed the problem. The Restore was able to begin without further problems. Pre-restore, my preboot partition and the whole partition table were likey messed up, which may have been what caused the error.