From owner-freebsd-questions Mon Feb 10 12:11:53 2003 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 80AC937B406 for ; Mon, 10 Feb 2003 12:11:51 -0800 (PST) Received: from cannon.ecf.utoronto.ca (cannon.ecf.utoronto.ca [128.100.8.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF8F343F75 for ; Mon, 10 Feb 2003 12:11:47 -0800 (PST) (envelope-from demonte@ecf.utoronto.ca) Received: from remote.ecf (remote.ecf [128.100.8.15]) by cannon.ecf.utoronto.ca (8.9.3/8.9.3) with ESMTP id PAA02033 for ; Mon, 10 Feb 2003 15:11:46 -0500 Received: from localhost (demonte@localhost) by remote.ecf (8.9.3/8.9.3) with ESMTP id PAA18023 for ; Mon, 10 Feb 2003 15:11:45 -0500 X-Authentication-Warning: remote.ecf: demonte owned process doing -bs Date: Mon, 10 Feb 2003 15:11:45 -0500 (EST) From: Tim DeMonte X-X-Sender: To: Subject: MBR manipulated ??? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, If anyone can suggest a solution to my problem, it would be greatly appreciated... I have a PC with one IDE harddrive, two partitions, one operating system: Windows 2000 (partitions are mapped as C: and D: under Windows). I wanted to install a second IDE harddrive that came from my colleague's PC. First, before installing new harddrive, I set jumper to "slave". I thought it should not matter what data was on new harddrive and ignored the fact that FreeBSD OS had been previously installed on this drive. I installed second drive, but PC did not boot (did not like the fact that first drive jumper was set to "cable select"). I moved jumper (too lazy to remove drive - figured I would get it right within 2 guesses), PC still did not boot. Third try - PC booted to Windows as expected, but problem: only C: mapped (no D:). Windows asked to be rebooted to update changes - okay - still no D:. Remove second drive from system (return it to original state) - still no D:. Run "Partition Magic" and find that whole first drive is designated as 'unknown' format and labelled "FreeBSD...". It seems the Master Boot Record (MBR) of the first drive was somehow manipulated by the presence/installation of the second drive. Everyone I talked says this should be impossible, but no one can offer any alternative explanation as to what happened. I have nearly 10 years experience setting various multiple OS / muliple harddrive PCs (although I haven't got around to trying FreeBSD), but I never had this problem before. Needless to say, the data on D: is fairly precious to me and I will make my next move cautiously, but does anyone have a suggestion as to what that move might be??? -- Tim DeMonte demonte@ecf.utoronto.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message