On Fri, 2 Jun 2006 15:21:13 -0400 (EDT)
Gerard E. Seibert [EMAIL PROTECTED] wrote:
The following error message suddenly appeared after I booted up my system.
The PC is connected to a small LAN. I Googled but was not able to find out
what the message is suppose to mean.
//Error Message
Andy Reitz wrote:
On Tue, 11 Apr 2006, Christopher McGee wrote:
The server I have is using an Intel SE7501CW2 server board with 1 Xeon
2.0Ghz processor. It's got a Mylex AcceleRAID 170 card with 6 - 36GB
scsi drives. When I reboot the machine, via ctrl-alt-del, or typing
reboot, it syncs
to, this wouldn't cause a
problem... but the last 3 power outages have caused reboot failures.
I will pull the box from it's headless location, plug in a keyboard and
monitor, and boot it up. Bootloader works, the boot menu comes up (where it
asks if you want single user mode, etc). It comes up and starts
The server I have is using an Intel SE7501CW2 server board with 1 Xeon
2.0Ghz processor. It's got a Mylex AcceleRAID 170 card with 6 - 36GB
scsi drives. When I reboot the machine, via ctrl-alt-del, or typing
reboot, it syncs disks, then gives the messages:
All buffers synced.
Uptime: ##m##s
On Tue, 11 Apr 2006, Christopher McGee wrote:
The server I have is using an Intel SE7501CW2 server board with 1 Xeon
2.0Ghz processor. It's got a Mylex AcceleRAID 170 card with 6 - 36GB
scsi drives. When I reboot the machine, via ctrl-alt-del, or typing
reboot, it syncs disks, then gives
info: [drm] Initialized mga 3.2.1 20051102
Also, this message comes up when the system saves the vmcore:
Reboot after panic: Page Fault
Thanks in advance for the assistance with this.
___
freebsd-questions@freebsd.org mailing list
http
To: [EMAIL PROTECTED]
Subject: Panic/reboot - a little help.
My desktop box, which has run very stable for a couple years now
using
which ever version of FreeBSD I've been running at the time, has
developed a sudden and alarming need to panic. I have two vmcore
files
at this point, but I'm unsure how
Sent: Sunday, April 09, 2006 8:57 AM
To: [EMAIL PROTECTED]
Subject: Panic/reboot - a little help.
My desktop box, which has run very stable for a couple years now
using
which ever version of FreeBSD I've been running at the time, has
developed a sudden and alarming need to panic. I have two vmcore
Setup: Dell 2850 running i386 FreeBSD 5.4-p5 (or so), ACPI enabled and
apparently working (shutdown -p or -r work fine).
After a kernel panic, the console showed Automatic reboot in 60 seconds
or press any key to interrupt, (or words to that effect), but actually
the machine just sat
and attempts to start moused again fail:
Mar 23 09:13:04 bedside moused: unable to open /dev/psm0: Device not configured
How to reinitialize/configure /dev/psm0 without reboot?
5.4-RELEASE-p3 with some security patches.
Thanks,
Lena
___
freebsd-questions
moused: unable to open /dev/psm0: Input/output error
and attempts to start moused again fail:
Mar 23 09:13:04 bedside moused: unable to open /dev/psm0: Device not
configured
How to reinitialize/configure /dev/psm0 without reboot?
5.4-RELEASE-p3 with some security patches.
Thanks,
Lena
of the various
servers on my network. It's about time when amanda reaches full speed
and the machine may be busy doing some high gzip compress.
The first reboot occured while I was running 4.10-RELEASE-p19 so it
cannot be related to the version of FreeBSD.
That machine has been running like
full speed
and the machine may be busy doing some high gzip compress.
The first reboot occured while I was running 4.10-RELEASE-p19 so it
cannot be related to the version of FreeBSD.
That machine has been running like that for about one year without
any problem.
I set dumpdev=/dev/rda0s1b
Robert Huff wrote:
Robert,
I have a -CURRENT machine - P4, 512mb RAM, SCSI disks,
de-driver ethernet, all mainstream hardware - that has this problem.
Since early last year (maybe longer) it will occasionally reboot.
Actually, I had it on three machines now. First on a P4 I leased
Olivier Nicole mailto:[EMAIL PROTECTED] wrote:
/var/log/messages just shows a user connectig via pop, and then the
next line is the machine booting.
Does the reboot correspond to the rainstorm?
Do you have UPS?
If time matches and no UPS I'd highly suspect a micro power faillure
this before. I haven't added any new hardware in a very long time. I did
upgrade mysql this morning via portupgrade, however.
The system appears to have crashed, as dmesg shows that the various
filesystems weren't unmounted correctly upon reboot, but aside from that
single error, nothing else
and haven't ever
experienced anything like this before. I haven't added any new
hardware in a very long time. I did upgrade mysql this morning via
portupgrade, however.
The system appears to have crashed, as dmesg shows that the various
filesystems weren't unmounted correctly upon reboot
correctly upon reboot, but
aside from
that single error, nothing else points to what the problem was.
/var/log/messages just shows a user connectig via pop, and
then the
next line is the machine booting.
We are having a pretty good rainstorm, but nothing else
seems to have
lost power
../../compile/SERVER
make depend
make
make install
#if all went well:
reboot
The system will then come back up with tuned parameters, allowing more
in/outbound connections and better packethandling.
Before I make these changes, I would like to just get a second opinion from
the list about
save the file, and follow these steps:
/usr/sbin/config -g SERVER
cd ../../compile/SERVER
make depend
make
make install
#if all went well:
reboot
The system will then come back up with tuned parameters, allowing more
in/outbound connections and better packethandling.
Before I
: the result is like
someone pulls the plug and puts it back in. No logs, no dumps, no
nothing. And completely normal operation right before the reboot. Pretty
annoying. I've had it on 2 machines, different hardware so far.
First I expected hardware, but now I moved everything to a freshly
options NMBUFS=40960
save the file, and follow these steps:
/usr/sbin/config -g SERVER
cd ../../compile/SERVER
make depend
make
make install
#if all went well:
reboot
The system will then come back up with tuned parameters, allowing
more in/outbound connections and better
Well, the server is an email/web server primarily. Not a
huge load, but I want to be hardened against DOS
attacks...would these help?
If you are looking to harden your server, this might be helpful. Though a bit
outdates, it still holds true for most part:
On 2006-02-16 15:18, Mike Loiterman [EMAIL PROTECTED] wrote:
Giorgos Keramidas mailto:[EMAIL PROTECTED] wrote:
On 2006-02-16 14:32, Mike Loiterman [EMAIL PROTECTED] wrote:
Wouter Spierenburg mailto:[EMAIL PROTECTED] wrote:
Try adding the following to /etc/sysctl.conf:
kern.maxfiles=65535
hardware - that has this problem.
Since early last year (maybe longer) it will occasionally reboot.
No warning, no panic, no core-dump, just - bang. If I was lucky it
would - sometimes - freeze or degrade X a few seconds before the
reboot. The shortest period between events was less than an hour
even
for sustained periods of time.
Did you do some disk stress test? The hardware problem could be
somwhere else than the MB.
Or network if your anti-spam rely on some network check?
It would be nice that you set-up your system (how?) so that it does
not reboot in case of failure, so you'd have
that it does
not reboot in case of failure, so you'd have some information on the
screen.
Olivier
Yes, I ran the unixbench port (2 instances of it) as well as the stress port
for about 4 hours. I think the hardware is fine, I believe, at least at
this point, that it was simply a micro-power
did
upgrade mysql this morning via portupgrade, however.
The system appears to have crashed, as dmesg shows that the various
filesystems weren't unmounted correctly upon reboot, but aside from that
single error, nothing else points to what the problem was.
/var/log/messages just shows a user
/var/log/messages just shows a user connectig via pop, and then the next
line is the machine booting.
Does the reboot correspond to the rainstorm?
Do you have UPS?
If time matches and no UPS I'd highly suspect a micro power faillure,
that other machines could over go, but that this specific
I've got a ppp over ssh tunnel from work, that's initiated from the remote end
by a cron task.
Friday night we lost power at our house. Most of the machines are on UPS's, so
I'm
failry certain I got them shutdown normally (it was the middle of the night
so I might have messed up).
In any case,
Running 5.3-RELEASE.
After many years of using FreeBSD, and as many reboots or more, I had
occasion to reboot today, and a few hours later discovered to my
horror that the system time had suddenly been moved ahead to the year
2020!
I did the best I could with the resulting mess, but I am curious
On Tue, 2006-01-10 at 09:01 +, Scott Ballantyne wrote:
Running 5.3-RELEASE.
After many years of using FreeBSD, and as many reboots or more, I had
occasion to reboot today, and a few hours later discovered to my
horror that the system time had suddenly been moved ahead to the year
2020
Scott Ballantyne wrote:
Running 5.3-RELEASE.
After many years of using FreeBSD, and as many reboots or more, I had
occasion to reboot today, and a few hours later discovered to my
horror that the system time had suddenly been moved ahead to the year
2020!
I did the best I could
On Jan 10, 2006, at 12:29 AM, Andreas Rudisch wrote:
On Tue, 2006-01-10 at 09:01 +, Scott Ballantyne wrote:
Running 5.3-RELEASE.
After many years of using FreeBSD, and as many reboots or more, I had
occasion to reboot today, and a few hours later discovered to my
horror that the system
does the halt command work?
and the shutdown command?
On 05/12/05, Benjamin Sobotta [EMAIL PROTECTED] wrote:
Hi!
The messages seem fine to me. However, I have no clue why it doesn't
reboot. :)
Ben
On Monday 05 December 2005 03:59, Jose Borquez wrote:
I attempted to reboot my pc using
On Mon, Dec 05, 2005 at 10:50:55AM +, Benjamin Sobotta wrote:
Hi!
The messages seem fine to me. However, I have no clue why it doesn't
reboot. :)
Try installing windows. ;)
Ben
On Monday 05 December 2005 03:59, Jose Borquez wrote:
I attempted to reboot my pc using FreeBSD 5.4
Hi!
The messages seem fine to me. However, I have no clue why it doesn't
reboot. :)
Ben
On Monday 05 December 2005 03:59, Jose Borquez wrote:
I attempted to reboot my pc using FreeBSD 5.4 and it appears to begin
the process of rebooting and then I get the following message. After
I attempted to reboot my pc using FreeBSD 5.4 and it appears to begin
the process of rebooting and then I get the following message. After
this message it just hangs and I can't do anything to reboot it.
Waiting (max 60 seconds) for system process `vnlru' to stop...done
Waiting (max 60
Jayesh Jayan wrote:
Hi,
On some of the machine where I have FreeBSD 5.4, /etc/inetd.conf becomes a
blank file soon after reboot.
I have kept a copy of the file and when the service fails after reboot I
restore the backup and restart the inetd service.
What I need to check, to solve
Hi Alex,
I have set the flags for the file. I hope this helps.
On 11/26/05, Alex Zbyslaw [EMAIL PROTECTED] wrote:
Jayesh Jayan wrote:
Hi,
On some of the machine where I have FreeBSD 5.4, /etc/inetd.conf becomes
a
blank file soon after reboot.
I have kept a copy of the file and when
I start mlnet, the daemon part of mldonkey, from it's local rc.d script on
bootup. If mlnet isn't shutdown properly, it leaves behind a pid file that
prevents the daemon running until I notice and manually delete the file.
What's the best way to deal with this? I was wondering if there is
Hi,
On some of the machine where I have FreeBSD 5.4, /etc/inetd.conf becomes a
blank file soon after reboot.
I have kept a copy of the file and when the service fails after reboot I
restore the backup and restart the inetd service.
What I need to check, to solve this issue. How can
reset. This
morning I'm trying to reinstall all the software that got lost in
last night's reset and I get another reset in the middle of
compiling. The last message in /var/log/messages before reboot is:
Nov 6 10:41:08 trisha ntpd[489]: kernel time sync enabled 6001
Nov 6 10:58:14
Micah wrote:
Except it reboot later when rebuilding the KDE stuff with portinstall
NOT the Gnome script. And I'm getting occasional segmentation faults
on Thunderbird and intermittent compiler errors like this one while
portinstalling kdepim:
then mv -f .deps/eudora_xxport.Tpo .deps
or is it covered in dust and cat hair like mine..?
Best of luck - hope this helps,
Jim Gorski
Message: 14
Date: Mon, 07 Nov 2005 00:59:37 -0800
From: Garrett Cooper [EMAIL PROTECTED]
Subject: Re: Diagnosing reboot under load
To: freebsd-questions@freebsd.org
Message-ID: [EMAIL PROTECTED]
Content-Type: text
around 11:30pm the computer reset. This
morning I'm trying to reinstall all the software that got lost in
last night's reset and I get another reset in the middle of
compiling. The last message in /var/log/messages before reboot is:
Nov 6 10:41:08 trisha ntpd[489]: kernel time sync enabled 6001
Micah [EMAIL PROTECTED] wrote:
I'm running the i386 version of FreeBSD with 1gb ram. Didn't think to
check this before, but I'm getting ~112-113 volts into the PSU from the
surge strip. I'm probably going to get a new PSU today. The parts
store has a couple of 400 watters in the $50
smoothly or is it covered in dust and cat hair like mine..?
Best of luck - hope this helps,
Jim Gorski
Message: 14
Date: Mon, 07 Nov 2005 00:59:37 -0800
From: Garrett Cooper [EMAIL PROTECTED]
Subject: Re: Diagnosing reboot under load
To: freebsd-questions@freebsd.org
Message-ID: [EMAIL PROTECTED
Bill Moran [EMAIL PROTECTED] wrote:
Micah [EMAIL PROTECTED] wrote:
I'm running the i386 version of FreeBSD with 1gb ram. Didn't think to
check this before, but I'm getting ~112-113 volts into the PSU from the
surge strip. I'm probably going to get a new PSU today. The parts
store
On Mon, Nov 07, 2005 at 07:11:42AM -0800, Micah wrote:
I cleaned out all the fans, but they weren't that dirty. I can't test
the temps while the system is under load (have to reboot and check them
in the bios).
Try xmbmon of mbmon from the/usr/ports/sysutils/xmbmon port. That should
help
Roland Smith wrote:
On Mon, Nov 07, 2005 at 07:11:42AM -0800, Micah wrote:
I cleaned out all the fans, but they weren't that dirty. I can't test
the temps while the system is under load (have to reboot and check them
in the bios).
Try xmbmon of mbmon from the/usr/ports/sysutils/xmbmon
On Mon, Nov 07, 2005 at 08:17:48AM -0800, Micah wrote:
Roland Smith wrote:
On Mon, Nov 07, 2005 at 07:11:42AM -0800, Micah wrote:
I cleaned out all the fans, but they weren't that dirty. I can't test
the temps while the system is under load (have to reboot and check them
in the bios
Bill Moran wrote:
Bill Moran [EMAIL PROTECTED] wrote:
Micah [EMAIL PROTECTED] wrote:
I'm running the i386 version of FreeBSD with 1gb ram. Didn't think to
check this before, but I'm getting ~112-113 volts into the PSU from the
surge strip. I'm probably going to get a new PSU
Micah wrote:
Roland Smith wrote:
On Mon, Nov 07, 2005 at 07:11:42AM -0800, Micah wrote:
I cleaned out all the fans, but they weren't that dirty. I can't
test the temps while the system is under load (have to reboot and
check them in the bios).
Try xmbmon of mbmon from the/usr/ports
Alex Zbyslaw wrote:
Bill Moran wrote:
Bill Moran [EMAIL PROTECTED] wrote:
Micah [EMAIL PROTECTED] wrote:
I'm running the i386 version of FreeBSD with 1gb ram. Didn't think
to check this before, but I'm getting ~112-113 volts into the PSU
from the surge strip. I'm probably going
At Mon, 7 Nov 2005 it looks like Micah composed:
Alex Zbyslaw wrote:
Bill Moran wrote:
Bill Moran [EMAIL PROTECTED] wrote:
Micah [EMAIL PROTECTED] wrote:
I'm running the i386 version of FreeBSD with 1gb ram. Didn't think to
check this before, but I'm getting ~112-113 volts into the
Micah wrote:
I'm really beginning to doubt it's the PSU. Why? I cannot get the
output voltage to drop no matter what load I throw at it. I plugged
in four additional hard drives and ran a system stress test and still
the voltages remained rock steady at the values I stated earlier. I
ran
At Mon, 7 Nov 2005 it looks like Micah composed:
Alex Zbyslaw wrote:
Bill Moran wrote:
Bill Moran [EMAIL PROTECTED] wrote:
Micah [EMAIL PROTECTED] wrote:
I'm running the i386 version of FreeBSD with 1gb ram. Didn't
think to check this before, but I'm getting ~112-113 volts into
the
Micah wrote:
I'm really beginning to doubt it's the PSU. Why? I cannot get the
output voltage to drop no matter what load I throw at it. I plugged
in four additional hard drives and ran a system stress test and still
the voltages remained rock steady at the values I stated earlier. I
Alex Zbyslaw wrote:
Micah wrote:
Roland Smith wrote:
On Mon, Nov 07, 2005 at 07:11:42AM -0800, Micah wrote:
I cleaned out all the fans, but they weren't that dirty. I can't
test the temps while the system is under load (have to reboot and
check them in the bios).
Try xmbmon
reset in the middle of compiling. The last message in /var/log/messages
before reboot is:
Nov 6 10:41:08 trisha ntpd[489]: kernel time sync enabled 6001
Nov 6 10:58:14 trisha ntpd[489]: kernel time sync enabled 2001
Nov 6 13:02:57 trisha syslogd: kernel boot file is /boot/kernel/kernel
I just ran
get another reset in the middle of compiling. The last message in
/var/log/messages before reboot is:
Nov 6 10:41:08 trisha ntpd[489]: kernel time sync enabled 6001
Nov 6 10:58:14 trisha ntpd[489]: kernel time sync enabled 2001
Nov 6 13:02:57 trisha syslogd: kernel boot file is /boot/kernel
in last night's reset and
I get another reset in the middle of compiling. The last message in
/var/log/messages before reboot is:
Nov 6 10:41:08 trisha ntpd[489]: kernel time sync enabled 6001
Nov 6 10:58:14 trisha ntpd[489]: kernel time sync enabled 2001
Nov 6 13:02:57 trisha syslogd: kernel boot
lost in last night's reset and I get another
reset in the middle of compiling. The last message in /var/log/messages
before reboot is:
Nov 6 10:41:08 trisha ntpd[489]: kernel time sync enabled 6001
Nov 6 10:58:14 trisha ntpd[489]: kernel time sync enabled 2001
Nov 6 13:02:57 trisha syslogd
the software that got lost in last night's reset and I get another
reset in the middle of compiling. The last message in /var/log/messages
before reboot is:
Nov 6 10:41:08 trisha ntpd[489]: kernel time sync enabled 6001
Nov 6 10:58:14 trisha ntpd[489]: kernel time sync enabled 2001
Nov 6 13:02
the computer reset. This morning I'm trying to reinstall
all the software that got lost in last night's reset and I get another
reset in the middle of compiling. The last message in /var/log/messages
before reboot is:
Nov 6 10:41:08 trisha ntpd[489]: kernel time sync enabled 6001
Nov 6 10:58:14
Jarrod Harch [EMAIL PROTECTED] writes:
Jarrod Harch [EMAIL PROTECTED] writes:
Hi, I just setup a new 5.4 install, which went fairly well. I added
some accounts - I used adduser to do one account, and logged on as the
user OK. The other account was created when I installed gdm as the
display
Hi Lowell, yes the home directory is intact.
I built and installed a new kernel, and after the reboot the accounts are
now staying intact. So it's a mystery. Perhaps it was some unfinished
sysinstall business, somehow overwriting the password database with the
defaults?
I'll reboot again tonight
Hi, I just setup a new 5.4 install, which went fairly well. I added some
accounts - I used
adduser to do one account, and logged on as the user OK. The other account
was
created when I installed gdm as the display manager.
On rebooting the root password is missing, the user account I created is
Hi,
I have a headless colo server and sometimes (after issuing the reboot
command) it would hang and did not reboot.
I have enabled console logging:
normal reboot:
Sep 19 13:24:26 foo kernel: Writing entropy file:
Sep 19 13:26:30 foo kernel: Pre-seeding PRNG:
Sep 19
Norberto Meijome wrote:
or figure out in which order things are started and make sure the
ttyvs are launched before syslogng
Can you recommend a good description of the FreeBSD boot process? The
handbook is a bit sketchy and only goes into the initial stages. I've
tried flirting through
Am Freitag, 16. September 2005 11:05 CEST schrieb Ashley Moran:
Norberto Meijome wrote:
or figure out in which order things are started and make sure the
ttyvs are launched before syslogng
Can you recommend a good description of the FreeBSD boot process? The
man (8) boot (excellent
Ashley Moran wrote:
Norberto Meijome wrote:
or figure out in which order things are started and make sure the
ttyvs are launched before syslogng
Can you recommend a good description of the FreeBSD boot process? The
handbook is a bit sketchy and only goes into the initial stages. I've
:
destination term { program(ccze -r /dev/ttyv7); };
I set syslog-ng to log all remote logs to this destination, and after
re-starting syslog-ng to reload the config, it worked fine. However,
for some reason way beyond me, it *will not work* after a reboot. I
have to restart syslog-ng
it as a destination:
destination term { program(ccze -r /dev/ttyv7); };
I set syslog-ng to log all remote logs to this destination, and after
re-starting syslog-ng to reload the config, it worked fine. However,
for some reason way beyond me, it *will not work* after a reboot. I
have
Alex Zbyslaw wrote:
The requirements like BEFORE: SERVERS are not honoured by scripts in
/usr/local/etc/rc.d. Try placing the script in /etc/rc.d calling it say
syslogng (i.e. without the .sh).
The BEFORE: doesn't bother me too much. I don't care enormously if I
lose a bit of logging. I
Ashley Moran wrote:
Yes, syslog-ng is running fine (I'd already configured rc.conf like you
say). The problem is that it has a destination set up to pipe to the
program ccze, and that pipe doesn't work unless I restart syslog-ng
after boot time.
I've also tried moving the script into
Norberto Meijome wrote:
Perhaps the ttyv7 isn't properly created until after all the local rc
scripts are run? That's all I can think.
you may want to edit the syslogng.sh to add some debug lines to see if
ttyv7 is up @ that point in time. based on the result of this, you may
want to
Alex Zbyslaw wrote:
Norberto Meijome wrote:
Perhaps the ttyv7 isn't properly created until after all the local rc
scripts are run? That's all I can think.
you may want to edit the syslogng.sh to add some debug lines to see if
ttyv7 is up @ that point in time. based on the result of this,
in message [EMAIL PROTECTED],
wrote Peter Matulis thusly...
Hi, I am running FreeBSD 5.4. I have upgraded my ports and recompiled the
system and kernel. I have a USB laser printer (Lexmark E310) that is
recognized
automatically when attached.
(That allows use of parallel port too.)
Hi, I am running FreeBSD 5.4. I have upgraded my ports and recompiled the
system and kernel. I have a USB laser printer (Lexmark E310) that is recognized
automatically when attached.
At first I was pleased since it appeared to work out of the box after setting
up a rudimentary printcap file.
Hi,
I just experienced a spontaneous reboot. I was fiddling a bit with
ossctl (that comes with opensound, commercial license), had finished
this (start sound with soundon) and started skype as a normal user.
Skype stalled and the next thing I saw was a black screen and a
reboot...
Below some
Ivan Carey [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
07/27/2005 02:16 PM
To
freebsd-questions@freebsd.org
cc
Subject
Shutdown -r now will not reboot pc
Hello,
I'm using FreeBSD 5.3
When I try to reboot the pc with shutdown -r now the system gets as far as
rebooting and hangs
Hello,
I'm using FreeBSD 5.3
When I try to reboot the pc with shutdown -r now the system gets as far as
rebooting and hangs there. Is there maybe a setup in the bios to allow the
pc to reboot.
Thanks,
Ivan
___
freebsd-questions@freebsd.org mailing
I would like the box to dump core and reboot on a panic. I think
I have set
the box up to do this, but on the last panic it didn't reboot. I
followed the
information at http://www.bsdatwork.com/2002/03/29/system_panics_part_1/,
and I have compiled a kernel with makeoptions DEBUG=-g
like the box to dump core and reboot on a panic. I think I have set
the box up to do this, but on the last panic it didn't reboot. I followed the
information at http://www.bsdatwork.com/2002/03/29/system_panics_part_1/,
and I have compiled a kernel with makeoptions DEBUG=-g, options KDB
Hi, I have recently installed FreeBSD 5.3 on a Dell Poweredge 650 server,
and it has panicked twice in the past 3 weeks. Unfortunately, the box is
in a server room for which I don't have a key, and access can take hours.
I would like the box to dump core and reboot on a panic. I think I have set
Hi, I have recently installed FreeBSD 5.3 on a Dell Poweredge 650 server,
and it has panicked twice in the past 3 weeks. Unfortunately, the box is
in a server room for which I don't have a key, and access can take hours.
I would like the box to dump core and reboot on a panic. I think I have set
Hi, I have recently installed FreeBSD 5.3 on a Dell Poweredge 650 server,
and it has panicked twice in the past 3 weeks. Unfortunately, the box is
in a server room for which I don't have a key, and access can take hours.
I would like the box to dump core and reboot on a panic. I think I have set
. :)
Thanks,
Drew
On 7/12/2005 9:35 AM Drew Tomlinson wrote:
On 7/11/2005 11:00 AM Drew Tomlinson wrote:
I just installed 5.4-RELEASE. I created a gstripe volume per the
example in the man page. Googling revealed that I needed to load the
geom_stripe module upon reboot so the volume can
On 7/11/2005 11:00 AM Drew Tomlinson wrote:
I just installed 5.4-RELEASE. I created a gstripe volume per the
example in the man page. Googling revealed that I needed to load the
geom_stripe module upon reboot so the volume can be created. I added
the following line to /boot/loader.conf
I just installed 5.4-RELEASE. I created a gstripe volume per the
example in the man page. Googling revealed that I needed to load the
geom_stripe module upon reboot so the volume can be created. I added
the following line to /boot/loader.conf:
geom_stripe_load=yes
Now upon reboot, I get
My hobby FreeBSD box has started to reboot at semi-regular intervals,
and I can't figure out why.
There seems to be no warning, no message at the console and no
indication of (or, probably, I don't recognize) the problem at reboot.
This happened a few months ago, and for some reason I
On Thu, Jun 30, 2005 at 10:04:15AM -0700, David Kurtz wrote:
My hobby FreeBSD box has started to reboot at semi-regular intervals,
and I can't figure out why.
Check the battery in your uninterruptable power supply.
What happens when you unplug it from the wall?
--
If the ends don't justify
On 6/30/05, Al Johnson [EMAIL PROTECTED] wrote:
On Thu, Jun 30, 2005 at 10:04:15AM -0700, David Kurtz wrote:
My hobby FreeBSD box has started to reboot at semi-regular intervals,
and I can't figure out why.
Check the battery in your uninterruptable power supply.
What happens when you
On 6/30/05, David Kurtz [EMAIL PROTECTED] wrote:
My hobby FreeBSD box has started to reboot at semi-regular intervals,
and I can't figure out why.
There seems to be no warning, no message at the console and no
indication of (or, probably, I don't recognize) the problem at reboot
[EMAIL PROTECTED]
Sorry, forgot something quick - I'm reading the MAN pages now on camcontrol
and the warnings associated with it.
If this server is in production later and has active users is there reason to
think that a rescan would cause problems with and read/writes happening at
should be able to be found without a reboot. I didn't try
dropping into single-user mode, maybe that would have done it too.
My hope was to probe for the SCSI drive and find it while the system
was fully up.
Thanks in advance -
d.
___
freebsd
the
corresponding alerts out. Still I couldn't see drive so I rebooted
system and then it was available via sysinstall.
What am I missing please? I would think with a hot-swap system the
drive should be able to be found without a reboot. I didn't try
dropping into single-user mode, maybe
On Jun 10, 2005, at 6:42 PM, Dan Nelson wrote:
Try camcontrol rescan all to tell the kernel to rescan all the scsi
busses. Otherwise there's no way for it to know you added a device.
--
Dan Nelson
[EMAIL PROTECTED]
Thank you Dan, exacty what I needed. I was unaware of camcontrol
401 - 500 of 760 matches
Mail list logo
