Difference between revisions of "System Rebuild - Lost MBR on C drive"

From Ed's Mediawiki
Line 5: Line 5:
 
X drive comes up as J, but works. Resetting it to X
 
X drive comes up as J, but works. Resetting it to X
  
M drive is not starting.  I have had some problems with this recentlyRebooting to bring up internal drives.
+
M drive is finicky about starting.  It is still in warranty, but I managed to make it start.  Resetting to M
 +
 
 +
O drive started fine
 +
 
 +
==Bring up internal drives==
 +
 
 +
When I did the factory restore, I unplugged the SATA connectors from the internal drives, V/Y and W. When I restarted with these plugged in, the machine did not boot.  I found that the drive order was wrong in the BIOS and it was trying to boot on W, which is not bootable or active.  I did have Y set to active, though, but no boot stuff there.  I changed the BIOS to put the boot drive first, and it booted with no problem.  It does make me wonder if this was what caused the boot problem with the old drive, thoughBut the symptoms were different and why would this suddenly happen? ...unless this was the first reboot since setting Y to active?  Maybe I will check this out sometime, but now I am committed, and an occasional system rebuild is probably good to do.
 +
 
 +
Set up drive letters for V and W, then deleted and recreated the volume on Y, not active this time, and named it "spare."
 +
 
 +
==Restore user files on drive C==
 +
 
 +
Installed CrashPlan and logged into my account.  Set up the X: drive local backup for this machine as a destination, and started a restore on all of the C drive stuff I had backed up.  This includes all of the application specific user directories, email database, firefox favorites, etc.  The restore took about three hours, during most of which I was out at a meeting.
 +
 
 +
==Re-install applications==
 +
Skipped the big stuff like LabView and Inventor for now
 +
*7-zip
 +
*acritum rename 3 - applied license from kits folders
 +
*AVS Video Tools - applied license
 +
*Better file Rename - applied license
 +
*Bit Torrent
 +
*calibre - came up with all of the restored content and subscriptions.  Downloaded the latest when prompted and re-installed.
 +
*exiftool, exiftoolgui - not installable tools.  They were restored to the applications folder. 
 +
**Added C:\Applications to system PATH to access these tools.
 +
*Thunderbird - downloaded latest version (8.0) and added to kits.  As soon as I started it, it started downloading unfetched mail from the server using the restored files in my user area.

Revision as of 16:38, 1 December 2011

Something happened to my C drive and it stopped booting. Other stuff was going wrong before I discovered this because I was getting emails from Crashplan that backups were not working. I was on vacation in Tucson when this started happening, so I had to wait until I got home to check it out. The network was acting up, so I decided to re-boot. No workee. I tried the repair functions from the recovery disks I created right after getting the machine, but they did not work. I got one successful boot and then it stopped working again. I can only assume the MBR sector on the disk is bad, plus some other stuff. I also tried some third party tools, but no luck. But while I was gone, the replacement disk for the bad V drive came and was sitting on the front stoop. I installed this and tried to restore the system to it from the image I had made recently. This also would not boot. So I ran a factory restore from the recovery disks, and now things are working. Of course, now I have to re-do tool installations, etc, to get everything running.

Bring up external drives

X drive comes up as J, but works. Resetting it to X

M drive is finicky about starting. It is still in warranty, but I managed to make it start. Resetting to M

O drive started fine

Bring up internal drives

When I did the factory restore, I unplugged the SATA connectors from the internal drives, V/Y and W. When I restarted with these plugged in, the machine did not boot. I found that the drive order was wrong in the BIOS and it was trying to boot on W, which is not bootable or active. I did have Y set to active, though, but no boot stuff there. I changed the BIOS to put the boot drive first, and it booted with no problem. It does make me wonder if this was what caused the boot problem with the old drive, though. But the symptoms were different and why would this suddenly happen? ...unless this was the first reboot since setting Y to active? Maybe I will check this out sometime, but now I am committed, and an occasional system rebuild is probably good to do.

Set up drive letters for V and W, then deleted and recreated the volume on Y, not active this time, and named it "spare."

Restore user files on drive C

Installed CrashPlan and logged into my account. Set up the X: drive local backup for this machine as a destination, and started a restore on all of the C drive stuff I had backed up. This includes all of the application specific user directories, email database, firefox favorites, etc. The restore took about three hours, during most of which I was out at a meeting.

Re-install applications

Skipped the big stuff like LabView and Inventor for now

  • 7-zip
  • acritum rename 3 - applied license from kits folders
  • AVS Video Tools - applied license
  • Better file Rename - applied license
  • Bit Torrent
  • calibre - came up with all of the restored content and subscriptions. Downloaded the latest when prompted and re-installed.
  • exiftool, exiftoolgui - not installable tools. They were restored to the applications folder.
    • Added C:\Applications to system PATH to access these tools.
  • Thunderbird - downloaded latest version (8.0) and added to kits. As soon as I started it, it started downloading unfetched mail from the server using the restored files in my user area.