Rescue and Recovery - Revision history

DHR: /* Newer versions of Rescue and Recovery */ x61t observation; grub2 note.

2011-12-04T19:32:26Z

‎Newer versions of Rescue and Recovery: x61t observation; grub2 note.

Ackmanx: /* Using the Windows Bootloader to Boot Linux */

2011-02-06T03:36:07Z

‎Using the Windows Bootloader to Boot Linux

Voominc: Added TOC

2011-01-31T03:49:13Z

Added TOC

Voominc at 03:46, 31 January 2011

2011-01-31T03:46:46Z

Voominc: /* Using Product Recovery to Restore the Windows MBR */

2011-01-31T03:40:27Z

‎Using Product Recovery to Restore the Windows MBR

Voominc: How to overwrite the MBR using the IBM Product Recovery CD-ROM

2011-01-31T03:38:36Z

How to overwrite the MBR using the IBM Product Recovery CD-ROM

Wenzhuo: /* Proper MBR */

2009-04-07T06:30:16Z

‎Proper MBR

Wenzhuo: /* Proper MBR */

2009-04-07T05:58:24Z

‎Proper MBR

Wenzhuo: /* Proper MBR */

2009-04-07T05:50:52Z

‎Proper MBR

Wenzhuo: /* Models featuring this technology */

2009-04-07T05:23:36Z

‎Models featuring this technology

@@ Line 166: / Line 166: @@
 (_NOT_ on all T61s.  Mine has version 4, but the R&R partition is the 2nd,
-and its ID is 0x12.  More work needed here....)
+and its ID is 0x12.
 (The same here on R61 8919-CTO - R&R version 4 was second partition of type FAT32)
@@ Line 176: / Line 178: @@
 * Install GRUB on the boot sector of the newly added primary partition
 * Remove the active bit from the Windows partition and activate the boot partition with GRUB
 ==Older versions of Rescue and Recovery==

@@ Line 107: / Line 107: @@
 * After IBM Product Recovery boots, this time select ''Full Recovery''
-===Using the Windows Bootloader to Boot Linux===
+===Using the Windows Bootloader to Boot Linux (this method doesn't work with Windows 7)===
 The NTLDR Windows bootloader can be configured to boot Linux in addition to Windows.  The master boot record (MBR) is unchanged, so the ThinkVantage Rescue and Recovery system boot functionality is preserved.  This clever procedure was [http://gawrysiak.org/corvus/?p=4 originally applied] to Ubuntu Dapper Drake, and is generalized here.

@@ Line 50: / Line 50: @@
 :This command is safe to run only when the first partition starts at sector 63, the 64th sector of the hard drive (probably true).
 ===MBR written by GRUB===
@@ Line 106: / Line 87: @@
 *Create a '''primary partition''' for /boot (the other stuff can go into the extended partitions) and when the time comes to install GRUB, make sure you install it into the boot sector of the boot partition.
 *Set this boot partition as active.
 ===Using the Windows Bootloader to Boot Linux===

@@ Line 10: / Line 10: @@
 </div>
 |}
+__TOC__
 ==Proper MBR==
 {{WARN|Only tinker with the MBR and the Rescue and Recovery partition if you know what you're doing. Mistakes can leave the system unbootable and can make it very difficult to retrieve the data on the harddisk.}}

@@ Line 68: / Line 68: @@
 * Reboot, press F12, select ''CD-ROM Drive'' as the boot device
-* After IBM Product Recovery boots, this time select ''Full Recovery''.
+* After IBM Product Recovery boots, this time select ''Full Recovery''
 ===MBR written by GRUB===

← Older revision		Revision as of 03:38, 31 January 2011
Line 50:		Line 50:

	:This command is safe to run only when the first partition starts at sector 63, the 64th sector of the hard drive (probably true).		:This command is safe to run only when the first partition starts at sector 63, the 64th sector of the hard drive (probably true).
		+
		+	===Using Product Recovery to Restore the Windows MBR===
		+	The Product Recovery CD/DVD-ROM erases your hard disk and restores it to its original factory state with Windows. The GRUB MBR can interfere with this. The symptom is that you try to recover, but the recovery process ends immediately, and the computer tries to boot with GRUB. The problem is that the one part of the disk that Product Recovery (version 5.6) does not overwrite is the MBR.
		+
		+	If this happens to you, first completely erase your hard disk using PC Doctor on the IBM Product Recovery CD-ROM:
		+
		+	* Insert Product Recovery Disk 1 (this procedure assumes version 5.6, circa 2002)
		+	* Power up the computer, press F12, select ''CD-ROM Drive'' as the boot device
		+	* After IBM Product Recovery boots, it will give you two choices:
		+	** ''Full Recovery''. Presumably you already tried this and failed.
		+	** ''System Utilities''. '''Select this'''.
		+	* Select ''Run diagnostics''. The PC Doctor diagnostic program will start.
		+	* In the menu along the top, choose ''Utility''.
		+	* In this menu, choose ''Full Erase Hard Drive'' and confirm that you really want to erase. ''Full Erase'' works, but takes about two minutes per gigabyte. If you find that ''Quick Erase Hard Drive'' also works, please edit that fact into this document.
		+
		+	After ''Erase Hard Drive'' finishes, your hard drive has no MBR, so Product Recovery has no choice but to install a new one.
		+
		+	* Reboot, press F12, select ''CD-ROM Drive'' as the boot device
		+	* After IBM Product Recovery boots, this time select ''Full Recovery''.

	===MBR written by GRUB===		===MBR written by GRUB===

@@ Line 43: / Line 43: @@
    bmgr32 /Fbootmgr.bin /M2 /V
-:/M0 also works, but /M2 restores it to factory state. As stated above, you must restore the Windows XP MBR before running bmgr32.exe.
+:/M0 also works, but /M2 restores it to factory state. As stated above, you must restore the MBR to the Windows XP MBR first before running bmgr32.exe.
 :If you've run bmgr32.exe too many times, you might have to clear the sectors from sector 1 to sector 62 (sector 0 is the MBR). If you know what you are doing, the following Linux dd command can do it for you:

@@ Line 38: / Line 38: @@
 *On my T42p and T43p, BMGR32.EXE was in {{path|C:\IBMTOOLS\utils}}. What seemed to work best was to run it first with /Fbootmgr.bin reboot, and if that didn't fix R&R, run it again with the /B0 /M0 /OEM switches. Have a XP install CD ready so you can do a FIXMBR from the Recovery Console if the machine won't boot (happened to me several times).
-*On my X32, BMGR32.EXE is also in {{path|C:\IBMTOOLS\utils}}. After some experimentation, I think it works best with the /M2 switch to restore the R&R MBR:
+*On my X32, BMGR32.EXE is also in {{path|C:\IBMTOOLS\utils}}. It works best with the /M2 switch to restore the R&R MBR:
    cd \IBMTOOLS\utils
    bmgr32 /Fbootmgr.bin /M2 /V
-/M0 also works. But /M2 restores to factory state.
+/M0 also works. But /M2 restores to factory state. As stated above, you must restore the Windows XP MBR before running bmgr32.exe.
-If you've run bmgr32.exe too many times, you might have to clear the sectors from sector 1 to sector 62. If you know what you are doing, the following Linux dd command can do it for you:
+If you've run bmgr32.exe too many times, you might have to clear the sectors from sector 1 to sector 62 (sector 0 is the MBR). If you know what you are doing, the following Linux dd command can do it for you:
    dd if=/dev/zero of=/dev/sda bs=512 seek=1 count=62

@@ Line 192: / Line 192: @@
 * ThinkPad {{Z60m}}
 * Thinkpad {{Z61m}}
-* Thinkpad {{X61}}
+* Thinkpad {{X61}}, {{X32}}
 [[Category:Glossary]]