Chris Zumbrunn wrote:
We also tried to boot just from one disk (ad0) after disabling the
RAID1 (ar0). And we reinstalled the MBR/bootstrap code on the ad0 and
ad2 disks but still couldn't get them to boot.
Then we switched the disks with those from another (identical) machine
and repeated the s
On Apr 24, 2005, at 9:24 AM, Chris Zumbrunn wrote:
On Apr 23, 2005, at 3:54 PM, Chris Zumbrunn wrote:
On Apr 23, 2005, at 1:27 PM, <[EMAIL PROTECTED]> wrote:
Turn off power management in PC bios and try again.
Thanks, I'll try that.
[...]
As soon as someone goes to the datacenter, we'll see what th
On Apr 23, 2005, at 3:54 PM, Chris Zumbrunn wrote:
On Apr 23, 2005, at 1:27 PM, <[EMAIL PROTECTED]> wrote:
Turn off power management in PC bios and try again.
Thanks, I'll try that.
When this happend to me before, I fdisk'ed, disklabel'ed,
atacontrol'ed, sysinstall'ed, dd'ed, newfs'ed, boot0cfg'ed
On Apr 23, 2005, at 1:27 PM, <[EMAIL PROTECTED]> wrote:
Turn off power management in PC bios and try again.
Thanks, I'll try that.
/czv
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscri
On Apr 23, 2005, at 1:16 PM, Alex Zbyslaw wrote:
Chris Zumbrunn wrote:
Yes, I'm just waiting until someone has to go by there anyway in the
next days. No big deal, but it's not urgent enough to justify the
trip just for that. In the meantime, it is annoying to know that
ultimately I just have th
Turn off power management in PC bios and try again.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Alex
Zbyslaw
Sent: Saturday, April 23, 2005 7:16 AM
To: Chris Zumbrunn
Cc: [EMAIL PROTECTED]
Subject: Re: Stuck in bootstrapping hell - how do I troubleshoot
Chris Zumbrunn wrote:
Yes, I'm just waiting until someone has to go by there anyway in the
next days. No big deal, but it's not urgent enough to justify the trip
just for that. In the meantime, it is annoying to know that ultimately
I just have this problem because I'm doing something wrong! ..
On Apr 22, 2005, at 2:01 PM, Alex Zbyslaw wrote:
Chris Zumbrunn wrote:
The server is in a datacenter and I can only access it via ssh and
boot either from the local disks or via network (freebsd or linux) -
no serial console, so I can't see where it gets stuck during the
bootstrap.
Do you mean
Chris Zumbrunn wrote:
On Apr 22, 2005, at 2:01 PM, Alex Zbyslaw wrote:
I.e. you can boot some OS which is not the one of the local disk? If
so, then boot the network FreeBSD, mount your local disks and look at
/var/log/messages. If the machine was at least booting FreeBSD when
it died then you
On Apr 22, 2005, at 6:16 PM, Alex Zbyslaw wrote:
Chris Zumbrunn wrote:
On Apr 22, 2005, at 2:01 PM, Alex Zbyslaw wrote:
I.e. you can boot some OS which is not the one of the local disk?
If so, then boot the network FreeBSD, mount your local disks and
look at /var/log/messages. If the machine wa
Chris Zumbrunn wrote:
The server is in a datacenter and I can only access it via ssh and
boot either from the local disks or via network (freebsd or linux) -
no serial console, so I can't see where it gets stuck during the
bootstrap.
Do you mean that you can boot the machine from an OS it picks
I repeated the setup attempt on another machine with different hardware
and got stuck with the same problem. Does anybody have a idea regarding
the obvious that I could be missing in order to get these systems to
boot? Otherwise I'll get someone to sit in front of the machine and
look at the s
I'm having a hell of a time trying to get a new development server to
boot FreeBSD.
The disk contents are an exact mirror from what I have running on a
production server, except for a different IP number in rc.conf. The
hardware is identical as far as I can tell.
The server is in a datacenter
13 matches
Mail list logo
