On Tue, Apr 11, 2006 at 01:27:03PM -0400, Jerry McAllister wrote:
On Tue, April 11, 2006 09:08, Jerry McAllister wrote:
I'm in a bit of a mess here. I've got an Asus P4C800-E Deluxe
motherboard with two on-board SATA RAID controllers, an Intel
MatrixRAID (ICH5R) and Promise
On Tue, Apr 11, 2006 at 01:27:03PM -0400, Jerry McAllister wrote:
On Tue, April 11, 2006 09:08, Jerry McAllister wrote:
I'm in a bit of a mess here. I've got an Asus P4C800-E Deluxe
motherboard with two on-board SATA RAID controllers, an Intel
MatrixRAID (ICH5R) and
have used a FreeBSD MBR to fix a hosed
MBR (hosed by Ghost) on an XP only (eg. no FreeBSD on it) machine and
it worked fine.
really? I suspect it was sysinstall's fdisk that hosed my MBR on the
Intel controller in the first place. Cause now it brings up a broken
FreeBSD boot loader instead
, the FreeBSD MBR is. I have used a FreeBSD MBR to fix a hosed
MBR (hosed by Ghost) on an XP only (eg. no FreeBSD on it) machine and
it worked fine.
really? I suspect it was sysinstall's fdisk that hosed my MBR on the
Intel controller in the first place. Cause now it brings up a broken
FreeBSD
On Fri, Apr 14, 2006 at 12:49:50PM -0400, Jerry McAllister wrote:
I can still boot FreeBSD off my FastTrack controller (ar0), that's
where I'm writing this email from. I can see both the Intel RAID
device (ar1), and mount the data from NTFS (ar1s1), and newly
created UFS-2 (ar1s2). I
FreeBSD/i386 boot
Default: 0:ad(0,a)/boot/kernel/kernel
boot:
---
So it would seem I hosed my MBR. The question is, how did I do it and
how do I fix it? I would think that when I choose to leave the MBR
untouched in sysinstall, that it would do just that.
I cannot use the old DOS boot
On Tue, April 11, 2006 09:08, Jerry McAllister wrote:
I'm in a bit of a mess here. I've got an Asus P4C800-E Deluxe
motherboard with two on-board SATA RAID controllers, an Intel
MatrixRAID (ICH5R) and Promise Fasttrak (PDC20378). My BIOS allows
me to boot from either the Promise or the
On Tue, April 11, 2006 09:08, Jerry McAllister wrote:
I'm in a bit of a mess here. I've got an Asus P4C800-E Deluxe
motherboard with two on-board SATA RAID controllers, an Intel
MatrixRAID (ICH5R) and Promise Fasttrak (PDC20378). My BIOS allows
me to boot from either the Promise or
/kernel/kernel
boot:
---
So it would seem I hosed my MBR. The question is, how did I do it and
how do I fix it? I would think that when I choose to leave the MBR
untouched in sysinstall, that it would do just that.
I cannot use the old DOS boot floppy trick of: fdisk /MBR as DOS
seem I hosed my MBR. The question is, how did I do it and
how do I fix it? I would think that when I choose to leave the MBR
untouched in sysinstall, that it would do just that.
I cannot use the old DOS boot floppy trick of: fdisk /MBR as DOS will
not recognize my Intel controller. Windows
(PDC20378). My BIOS allows me to boot
from either the Promise or the Intel controller.
...
The problem is, now, when I attempt to boot off the Intel controller, I
get a FreeBSD boot load failure:
Invalid Partition
Invalid Partition
So it would seem I hosed my MBR. The question
11 matches
Mail list logo