subject:"Boot Problem"

Is there a way to make sure that the interface is UP and working
before running ntpdate at boot on a box with a static IP address?

After setting ntpdate_enable=YES in rc.conf, I get the following
error on boot:

Setting date via ntp.
Error : hostname nor servname provided, or not known
 5 Nov 17:11:05
ntpdate[786]: can't find host 0.freebsd.pool.ntp.org

Error : hostname nor servname provided, or not known
 5 Nov 17:11:05
ntpdate[786]: can't find host 1.freebsd.pool.ntp.org

Error : hostname nor servname provided, or not known
 5 Nov 17:11:05
ntpdate[786]: can't find host 2.freebsd.pool.ntp.org

 5 Nov 17:11:05
ntpdate[786]: no servers can be used, exiting

I've had this problem with machines using DHCP and the solution was to
use SYNCDHCP rather than DHCP in rc.conf.  However, this box is using
a static IP address.  But the problem seems to be similar.

Rob
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

ntpdate on boot problem

Is there a way to make sure that the interface is UP and working
before running ntpdate at boot on a box with a static IP address?

After setting ntpdate_enable=YES in rc.conf, I get the following
error on boot:

Setting date via ntp.
Error : hostname nor servname provided, or not known
 5 Nov 17:11:05
ntpdate[786]: can't find host 0.freebsd.pool.ntp.org

Error : hostname nor servname provided, or not known
 5 Nov 17:11:05
ntpdate[786]: can't find host 1.freebsd.pool.ntp.org

Error : hostname nor servname provided, or not known
 5 Nov 17:11:05
ntpdate[786]: can't find host 2.freebsd.pool.ntp.org

 5 Nov 17:11:05
ntpdate[786]: no servers can be used, exiting

I've had this problem with machines using DHCP and the solution was to
use SYNCDHCP rather than DHCP in rc.conf.  However, this box is using
a static IP address.  But the problem seems to be similar.

Rob
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: ntpdate on boot problem

2011-11-05 Thread Michael Sierchio

Are you running a firewall?  Do you have a ppp connection?

This happens when there is a dependency that is not expressed in the
/etc/rc.d scripts.

- M

On Sat, Nov 5, 2011 at 2:52 PM, Robert Simmons rsimmo...@gmail.com wrote:
 Is there a way to make sure that the interface is UP and working
 before running ntpdate at boot on a box with a static IP address?

 After setting ntpdate_enable=YES in rc.conf, I get the following
 error on boot:

 Setting date via ntp.
 Error : hostname nor servname provided, or not known
  5 Nov 17:11:05
 ntpdate[786]: can't find host 0.freebsd.pool.ntp.org

 Error : hostname nor servname provided, or not known
  5 Nov 17:11:05
 ntpdate[786]: can't find host 1.freebsd.pool.ntp.org

 Error : hostname nor servname provided, or not known
  5 Nov 17:11:05
 ntpdate[786]: can't find host 2.freebsd.pool.ntp.org

  5 Nov 17:11:05
 ntpdate[786]: no servers can be used, exiting

 I've had this problem with machines using DHCP and the solution was to
 use SYNCDHCP rather than DHCP in rc.conf.  However, this box is using
 a static IP address.  But the problem seems to be similar.

 Rob
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: ntpdate on boot problem

2011-11-05 Thread Alexander Best

On Sat Nov  5 11, Robert Simmons wrote:
 Is there a way to make sure that the interface is UP and working
 before running ntpdate at boot on a box with a static IP address?
 
 After setting ntpdate_enable=YES in rc.conf, I get the following
 error on boot:
 
 Setting date via ntp.
 Error : hostname nor servname provided, or not known
  5 Nov 17:11:05
 ntpdate[786]: can't find host 0.freebsd.pool.ntp.org
 
 Error : hostname nor servname provided, or not known
  5 Nov 17:11:05
 ntpdate[786]: can't find host 1.freebsd.pool.ntp.org
 
 Error : hostname nor servname provided, or not known
  5 Nov 17:11:05
 ntpdate[786]: can't find host 2.freebsd.pool.ntp.org
 
  5 Nov 17:11:05
 ntpdate[786]: no servers can be used, exiting
 
 I've had this problem with machines using DHCP and the solution was to
 use SYNCDHCP rather than DHCP in rc.conf.  However, this box is using
 a static IP address.  But the problem seems to be similar.

same here. simply add something like the following to your crontab:

0   10  *   *   */2 /etc/rc.d/ntpdate onestart

cheers.
alex

 
 Rob
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: ntpdate on boot problem

On Sat, Nov 5, 2011 at 5:57 PM, Michael Sierchio ku...@tenebras.com wrote:
 Are you running a firewall?  Do you have a ppp connection?

I'm not running a firewall on the machine in question.  I am behind a
firewall, if that's what you mean.  I don't have a ppp connection.
The box is a server that is running on bare metal, no VM.  Fixed IP
address (198.162) behind a NAT firewall.

But, after booting, everything works correctly:

# /etc/rc.d/ntpdate onestart
Setting date via ntp.
 5 Nov 18:09:31 ntpdate[1324]: step time server 128.10.254.7 offset
-0.000537 sec


 This happens when there is a dependency that is not expressed in the
 /etc/rc.d scripts.

Can you elaborate?  My rc.conf looks like this (pretty simple):

hostname=example
ifconfig_sk0=inet 192.168.1.5 netmask 0xff00
defaultrouter=192.168.1.1
sshd_enable=YES

#Screensaver
saver=daemon

#Encrypted swap
geli_swap_flags=-d -l 256 -s 4096

#/tmp in memory
tmpmfs=YES

#Kerberos
kerberos5_server_enable=YES
kadmind5_server_enable=YES

#Time
ntpdate_enable=YES


Also, the box is 8.2-RELEASE with current updates via freebsd-update.

Rob
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: ntpdate on boot problem

On Sat, Nov 5, 2011 at 6:03 PM, Alexander Best arun...@freebsd.org wrote:
 same here. simply add something like the following to your crontab:

 0       10      *       *       */2     /etc/rc.d/ntpdate onestart

I have something similar in my crontab which is not exactly what I
need.  I want to make sure that the clock is set at every boot because
I'm using this as a kerberos server.  If the clock is not set properly
at boot, kerberos will not work properly until the nightly cron jobs
are run and the clock is set then.  I need everything working at boot.
 I can't have a window of problems between boot and midnight or
whenever cron runs ntpdate.

Rob
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: ntpdate on boot problem

2011-11-05 Thread Michael Sierchio

The keywords in /etc/rc.d/ntpdate have

# PROVIDE: ntpdate
# REQUIRE: NETWORKING syslogd named
# KEYWORD: nojail

which means that networking must be up first.  The question in your
case is why name resolution is failing.

See what happens if you pick some public stratum 1 or stratum 2
servers for your ntp.conf.  Then try specifying IP addrs instead of
FQDNs
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: ntpdate on boot problem

2011-11-05 Thread Matthew Seaman

On 05/11/2011 22:19, Robert Simmons wrote:
 On Sat, Nov 5, 2011 at 6:03 PM, Alexander Best arun...@freebsd.org wrote:
 same here. simply add something like the following to your crontab:

 0   10  *   *   */2 /etc/rc.d/ntpdate onestart
 
 I have something similar in my crontab which is not exactly what I
 need.  I want to make sure that the clock is set at every boot because
 I'm using this as a kerberos server.  If the clock is not set properly
 at boot, kerberos will not work properly until the nightly cron jobs
 are run and the clock is set then.  I need everything working at boot.
  I can't have a window of problems between boot and midnight or
 whenever cron runs ntpdate.

crontabs have this handy '@reboot' syntax...  It's all explained in
crontab(5).

However, you would be well advised to run ntpd(8) rather than bodging
the clock with ntpdate at intervals.  ntpdate is deprecated by the ntp
project, given that ntpd now has the capability to synch the clock the
first time after restart no matter what the offset.  Just add these
rc.conf settings:

ntpd_enable=YES
ntpd_sync_on_start=YES

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
  Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matt...@infracaninophile.co.uk   Kent, CT11 9PW



signature.asc
Description: OpenPGP digital signature

Re: ntpdate on boot problem

2011-11-05 Thread Warren Block


On Sat, 5 Nov 2011, Robert Simmons wrote:


Is there a way to make sure that the interface is UP and working
before running ntpdate at boot on a box with a static IP address?

After setting ntpdate_enable=YES in rc.conf, I get the following
error on boot:

Setting date via ntp.
Error : hostname nor servname provided, or not known
5 Nov 17:11:05
ntpdate[786]: can't find host 0.freebsd.pool.ntp.org

Error : hostname nor servname provided, or not known
5 Nov 17:11:05
ntpdate[786]: can't find host 1.freebsd.pool.ntp.org

Error : hostname nor servname provided, or not known
5 Nov 17:11:05
ntpdate[786]: can't find host 2.freebsd.pool.ntp.org

5 Nov 17:11:05
ntpdate[786]: no servers can be used, exiting

I've had this problem with machines using DHCP and the solution was to
use SYNCDHCP rather than DHCP in rc.conf.  However, this box is using
a static IP address.  But the problem seems to be similar.


Yes, it is.  FreeBSD 8-STABLE and 9 have /etc/rc.d/netwait just for 
this.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: ntpdate on boot problem

On Sat, Nov 5, 2011 at 6:55 PM, Warren Block wbl...@wonkity.com wrote:
 On Sat, 5 Nov 2011, Robert Simmons wrote:
 Is there a way to make sure that the interface is UP and working
 before running ntpdate at boot on a box with a static IP address?
 Yes, it is.  FreeBSD 8-STABLE and 9 have /etc/rc.d/netwait just for this.

Thanks, could you elaborate as to how I use netwait at boot to run ntpdate?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: ntpdate on boot problem

On Sat, Nov 5, 2011 at 6:33 PM, Matthew Seaman
m.sea...@infracaninophile.co.uk wrote:
 crontabs have this handy '@reboot' syntax...  It's all explained in
 crontab(5).

Thanks!

 However, you would be well advised to run ntpd(8) rather than bodging
 the clock with ntpdate at intervals.  ntpdate is deprecated by the ntp
 project, given that ntpd now has the capability to synch the clock the
 first time after restart no matter what the offset.  Just add these
 rc.conf settings:

 ntpd_enable=YES
 ntpd_sync_on_start=YES

Thanks again, this works without any problems.  I'm still curious how
to get the ntpdate adjustment to occur later in the boot process after
the network interface is UP, but now it's merely academic.

Rob
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: ntpdate on boot problem

2011-11-05 Thread Warren Block


On Sat, 5 Nov 2011, Robert Simmons wrote:


On Sat, Nov 5, 2011 at 6:55 PM, Warren Block wbl...@wonkity.com wrote:

On Sat, 5 Nov 2011, Robert Simmons wrote:

Is there a way to make sure that the interface is UP and working
before running ntpdate at boot on a box with a static IP address?

Yes, it is.  FreeBSD 8-STABLE and 9 have /etc/rc.d/netwait just for this.


Thanks, could you elaborate as to how I use netwait at boot to run ntpdate?


Untested:

netwait_enable=YES
netwait_ip=192.168.1.1 # IP address to ping to verify network is up
netwait_if=em0 # interface to use


Also there's netwait_timeout, which defaults to 60 in 
/etc/defaults/rc.conf.___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: ntpdate on boot problem

2011-11-05 Thread Warren Block


On Sat, 5 Nov 2011, d...@safeport.com wrote:


On Sat, 5 Nov 2011, Warren Block wrote:

On Sat, 5 Nov 2011, Robert Simmons wrote:


I've had this problem with machines using DHCP and the solution was to
use SYNCDHCP rather than DHCP in rc.conf.  However, this box is using
a static IP address.  But the problem seems to be similar.


Yes, it is.  FreeBSD 8-STABLE and 9 have /etc/rc.d/netwait just for this.


I do not see this in the handbook. Did I just miss it?. IMO the necessary 
synchronization should just be built in to booting.


AFAIK it's not in the Handbook yet.  The problem is that some network 
interfaces actually take a while to come up after ifconfig is done 
setting them up.  The amount of time taken could depend on the local 
network with autonegotiation and such.


Another approach is to set up the DHCP server--if there is one--to 
assign static addresses based on MAC address.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: ntpdate on boot problem

On Sat, Nov 5, 2011 at 7:43 PM, Warren Block wbl...@wonkity.com wrote:
 netwait_enable=YES
 netwait_ip=192.168.1.1 # IP address to ping to verify network is up
 netwait_if=em0 # interface to use


 Also there's netwait_timeout, which defaults to 60 in /etc/defaults/rc.conf.

I've finally got a combination of suggested configurations that get me
to where I want to be (using ntpd, ntpdate, and netwait).

However, I've found that I still need ntpdate_enable=YES rather than
ntpd_sync_on_start=YES.  The reason for this is that I'm running at
securelevel 3, and ntpd takes too long to get up, running, and sync
the clock.  By the time it tries to adjust the clock, secure level has
already been raised preventing the adjustment.

Is there a way to make securelevel wait until ntpd has made its
adjustments?  When I use ntpdate at this point, it seems like the init
scripts are sequential, and it waits until ntpdate is done before
continuing and later raising securelevel.

It seems that even though ntpdate is deprecated that it is still
required if you want to run securelevel 3.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: ntpdate on boot problem

2011-11-05 Thread Carl Johnson

Matthew Seaman m.sea...@infracaninophile.co.uk writes:

 On 05/11/2011 22:19, Robert Simmons wrote:
 On Sat, Nov 5, 2011 at 6:03 PM, Alexander Best arun...@freebsd.org wrote:
 same here. simply add something like the following to your crontab:

 0   10  *   *   */2 /etc/rc.d/ntpdate onestart
 
 I have something similar in my crontab which is not exactly what I
 need.  I want to make sure that the clock is set at every boot because
 I'm using this as a kerberos server.  If the clock is not set properly
 at boot, kerberos will not work properly until the nightly cron jobs
 are run and the clock is set then.  I need everything working at boot.
  I can't have a window of problems between boot and midnight or
 whenever cron runs ntpdate.

 crontabs have this handy '@reboot' syntax...  It's all explained in
 crontab(5).

Just be aware that 'Run once, at startup', means when 'cron' starts, not
just when the system boots, unless they have changed it recently.

-- 
Carl Johnsonca...@peak.org

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

boot problem

2011-04-21 Thread Yavuz Maşlak

Hello

I have a freebsd7 box.  I also have another PC . I removed the disk from
freebsd installed machine and fixed it to the another PC.

It Works but there is a problem.  
While opening the server it waits at boot 

FreeBSD/i386 boot:
Default:0:ad(0,a)/boot/loader
Boot:

If I press enter, the server opens and it Works.

How can I get rid off this ?   


Bu elektronik posta ve varsa ekleri tamamen gizli ve gonderilen kisiler 
listesine ozeldir. Eger adiniz gonderilen kisiler listesinde yer almiyorsa, 
lutfen derhal gonderen kisiyi bilgilendiriniz ve icerigini herhangi baska bir 
kisiye iletmeyiniz, herhangi bir amac icin kullanmayiniz, sayisal ve basili 
ortamlar dahil olmak uzere saklamayiniz ve kopyalamayiniz.


This e-mail and attachments, if any, may contain confidential and/or 
proprietary information. Please be advised that the unauthorized use or 
disclosure of the information is strictly prohibited. If you are not the 
intended recipient, please notify the sender immediately by reply e-mail and 
delete all copies of this message and attachments. Thank you.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: boot problem

2011-04-21 Thread Warren Block


On Thu, 21 Apr 2011, Yavuz Maşlak wrote:


I have a freebsd7 box.  I also have another PC . I removed the disk from
freebsd installed machine and fixed it to the another PC.


How is it connected?  USB?


It Works but there is a problem.
While opening the server it waits at boot

FreeBSD/i386 boot:
Default:0:ad(0,a)/boot/loader
Boot:

If I press enter, the server opens and it Works.

How can I get rid off this ?


Adding kern.cam.boot_delay=1 to /boot/loader.conf helps with some 
USB drives.___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

RE: boot problem

2011-04-21 Thread Yavuz Maşlak


Attached sata Disk.   it is not usb 


Namely, The sata disk  is attached to new machine.
It is connected by sata cable.
 

On Thu, 21 Apr 2011, Yavuz Maşlak wrote:

 I have a freebsd7 box.  I also have another PC . I removed the disk from
 freebsd installed machine and fixed it to the another PC.

How is it connected?  USB?

 It Works but there is a problem.
 While opening the server it waits at boot

 FreeBSD/i386 boot:
 Default:0:ad(0,a)/boot/loader
 Boot:

 If I press enter, the server opens and it Works.

 How can I get rid off this ?

Adding kern.cam.boot_delay=1 to /boot/loader.conf helps with some 
USB drives.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Boot problem after reboot during upgrade from frebsd6.1 to freebsd7.0

2008-03-13 Thread Yavuz Maslak

I followed http://www.freebsd.org/releases/7.0R/announce.html  to upgrade
freebsd6.1 to 7.0.

I forgot compile kernel for freebsd7.0. and I rebooted the machine.
The server didn't give any error message during the upgrade.
The server tried to boot at freebsd6.1. and it could not boot the system. it
came  Enter full path of shell on the screen.
How can I do correct that ?




___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: boot problem after custom kernel

2007-08-06 Thread Alain G. Fabry

On Mon, Aug 06, 2007 at 03:29:14PM +1000, Paul Fraser wrote:
 Alain G. Fabry wrote:
 First 'unload kernel' followed by 'boot /boot/kernel.GENERIC/kernel', but 
 it mentions
 that it cannot find the kernel.
 
 
 snip
 
 What can I do to boot my GENERIC kernel so I can rebuild from it and my 
 system will boot
 normal again.
 
 Hi Alain,
 
 Try replacing 'kernel.GENERIC' with 'kernel.old' in your example. If you 
 don't remember actually making a copy of your kernel and naming it 
 kernel.GENERIC, you'll be more likely to succeed with kernel.old.
 
 -- 
 Regards,
 
 Paul Fraser // Independent Technical Consultant // Ph: +61 405 341 905 
 // furyc0de.net
 
 This correspondence and any related attachments are confidential. 
 Distribution, reproduction, or release (public domain or otherwise) 
 without the author's prior written consent is STRICTLY FORBIDDEN. 
 Failure to distribute any of the aforementioned without this footer 
 (intact and unmodified) is also STRICTLY FORBIDDEN. Failure to abide by 
 these terms and conditions can result in legal action.
 
 If you have received this correspondence in error, or believe any of 
 these terms have been breached, you are requested to contact the author 
 immediately and take steps to destroy all copies in your possession.
 


Thanks, it works.
Somehow I though since the old seems to be in italics that you needed to change 
it
with the old kernel name (which in my case was GENERIC)
Back up and running.

Alain





 PGP KeyID: 0x64E635B1
 Keyserver: pgp.mit.edu:11371
 Key fingerprint: CDA3 0797 68B9 0EC1 D4D3 A7B9 D7D7 4924 64E6 35B1
 
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to [EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: boot problem after custom kernel

2007-08-05 Thread Philip M. Gollucci


Alain G. Fabry wrote:

First 'unload kernel' followed by 'boot /boot/kernel.GENERIC/kernel', but it 
mentions
that it cannot find the kernel.

try,

at loader prompt:

unload kernel
load /boot/kernel.old/kernel
boot


--

Philip M. Gollucci ([EMAIL PROTECTED]) 323.219.4708
Senior System Admin - Riderway, Inc. http://riderway.com
1024D/EC88A0BF 0DE5 C55C 6BF3 B235 2DAB  B89E 1324 9B4F EC88 A0BF

Work like you don't need the money,
love like you'll never get hurt,
and dance like nobody's watching.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: boot problem after custom kernel

2007-08-05 Thread Paul Fraser


Alain G. Fabry wrote:

First 'unload kernel' followed by 'boot /boot/kernel.GENERIC/kernel', but it 
mentions
that it cannot find the kernel.



snip


What can I do to boot my GENERIC kernel so I can rebuild from it and my system 
will boot
normal again.


Hi Alain,

Try replacing 'kernel.GENERIC' with 'kernel.old' in your example. If you 
don't remember actually making a copy of your kernel and naming it 
kernel.GENERIC, you'll be more likely to succeed with kernel.old.


--
Regards,

Paul Fraser // Independent Technical Consultant // Ph: +61 405 341 905 
// furyc0de.net


This correspondence and any related attachments are confidential. 
Distribution, reproduction, or release (public domain or otherwise) 
without the author's prior written consent is STRICTLY FORBIDDEN. 
Failure to distribute any of the aforementioned without this footer 
(intact and unmodified) is also STRICTLY FORBIDDEN. Failure to abide by 
these terms and conditions can result in legal action.


If you have received this correspondence in error, or believe any of 
these terms have been breached, you are requested to contact the author 
immediately and take steps to destroy all copies in your possession.


PGP KeyID: 0x64E635B1
Keyserver: pgp.mit.edu:11371
Key fingerprint: CDA3 0797 68B9 0EC1 D4D3 A7B9 D7D7 4924 64E6 35B1

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Boot problem after GEOM setup

2007-04-21 Thread Robert Fitzpatrick


Following the doc below, I am trying to mirror an existing disk, ad0,
which holds the root and /usr partitions (a second disk holds /var). I
have an exact same disk in as ad2 in the system and did everything in
this document top section through dumping the data and setting up
/etc/fstab and loader.conf. I created the /boot.config as shown except I
replaced the '1' with '2' just like I did for the other steps, but this
does not appear correct. I now stall when booting at the boot: prompt.
What can I type in the boot: prompt to get back in my system and make
the necessary changes? Also, what should the /boot.config look like to
boot to my new disk and continue through the steps for adding the first
disk to the mirror? I guess it looks like this now: 1:ad(2,a)/boot/loader.

http://people.freebsd.org/~rse/mirror/

--
Robert

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Boot problem after GEOM setup

2007-04-21 Thread Robert Fitzpatrick

On Sat, 2007-04-21 at 11:39 -0400, Robert Fitzpatrick wrote:
 Following the doc below, I am trying to mirror an existing disk, ad0,
 which holds the root and /usr partitions (a second disk holds /var). I
 have an exact same disk in as ad2 in the system and did everything in
 this document top section through dumping the data and setting up
 /etc/fstab and loader.conf. I created the /boot.config as shown except I
 replaced the '1' with '2' just like I did for the other steps, but this
 does not appear correct. I now stall when booting at the boot: prompt.
 What can I type in the boot: prompt to get back in my system and make
 the necessary changes? Also, what should the /boot.config look like to
 boot to my new disk and continue through the steps for adding the first
 disk to the mirror? I guess it looks like this now: 1:ad(2,a)/boot/loader.
 
 http://people.freebsd.org/~rse/mirror/
 

I was able to recover with a FreeSBIE and go back, seems I was close. I
have the GEOM working now as shown below. However, after successfully
synchronizing and doing a reboot, it shows up DEGRADED after every
reboot and synchronizes again, is that normal?

genoa# gmirror list
Geom name: gm0
State: DEGRADED
Components: 2
Balance: round-robin
Slice: 4096
Flags: NONE
SyncID: 1
ID: 4224071626
Providers:
1. Name: mirror/gm0
   Mediasize: 15364338688 (14G)
   Sectorsize: 512
   Mode: r4w3e2
Consumers:
1. Name: ad0
   Mediasize: 15364339200 (14G)
   Sectorsize: 512
   Mode: r0w1e1
   State: SYNCHRONIZING
   Priority: 0
   Flags: DIRTY, SYNCHRONIZING
   SyncID: 1
   Synchronized: 28%
   ID: 4099754703
2. Name: ad2
   Mediasize: 15364339200 (14G)
   Sectorsize: 512
   Mode: r4w3e3
   State: ACTIVE
   Priority: 0
   Flags: DIRTY
   SyncID: 1
   ID: 3454124143

Geom name: gm0.sync
Consumers:
1. Name: mirror/gm0
   Mediasize: 15364338688 (14G)
   Sectorsize: 512
   Mode: r1w0e0

-- 
Robert

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: acpi and boot problem

2006-12-03 Thread leo fante


 From a quick look at /boot/beastie.4th, I think that setting acpi_load

in your loader.conf will do the job.

also it is written in loader.help but I've already tried and it doesn't work.

thanks anyway for the advice


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: acpi and boot problem

2006-12-01 Thread Lowell Gilbert

leo fante [EMAIL PROTECTED] writes:

 Hi
 I've installed freebsd 6.1 on an old pc on which I've configured several
 services. Everything worked fine since last week when the motherboard died.
 I've replaced the mobo and found that now the acpi could work (with the old 
 motherboard
 the installation disabled the acpi at boot since the mainboard was 
 blacklisted).

 Since the old mobo was blacklisted the options on the menu were
 1 default
 2 boot with acpi

 Now I would like to have the acpi enabled by default at boot time on the 
 beastie menu.
 1 default
 2 boot without acpi

 reading the man of loader.conf I've added hint.acpi.0.disabled=0
 and now the pc boots with with acpi enabled but without having
 the correct options in the boot menu.

 How I could fix the menu?

From a quick look at /boot/beastie.4th, I think that setting acpi_load
in your loader.conf will do the job.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

acpi and boot problem

2006-11-28 Thread leo fante


Hi
I've installed freebsd 6.1 on an old pc on which I've configured several
services. Everything worked fine since last week when the motherboard died.
I've replaced the mobo and found that now the acpi could work (with the old 
motherboard
the installation disabled the acpi at boot since the mainboard was blacklisted).

Since the old mobo was blacklisted the options on the menu were
1 default
2 boot with acpi

Now I would like to have the acpi enabled by default at boot time on the 
beastie menu.
1 default
2 boot without acpi

reading the man of loader.conf I've added hint.acpi.0.disabled=0
and now the pc boots with with acpi enabled but without having
the correct options in the boot menu.

How I could fix the menu?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

FreeBSD 6.2 PRERELEASE boot problem

2006-10-07 Thread Jack Raats

After upgrading the ports suddenly the server does not reboot.
I get the menu 'Welcome to FreeBSD'; after pressing 1 (boot FreeBSD
default) the system halts with '/boot/kernel/acpi.ko text=0x43670
data=0x23c0+0x10f0 syms=[0x4+0x7ba+0x4+0xa828]

We tried acessing thru live cdrom whilst mounting the partition, but that
does not work.

Any suggestions how to get the system pass booting again?

Jack

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

intermittent boot problem

2006-09-27 Thread Marty Landman


I've got a new FBSD 5.3 release install on an old Compaq pII-233 w/ 128M
ram. What I get when the boot fails is

tx underrun -- using store and forward mode

repeating infinitely.

Now that a reboot has succeeded here's what dmesg shows for dc0:

dc0: 82c169 PNIC 10/100BaseTX port 0x1400-0x14ff mem 0x4090-0x409000ff
irq 11 at device 4.0 on pci0
miibus0: MII bus on dc0
lxtphy0: LXT970 10/100 media interface on miibus0
lxtphy0:  100baseFX, 100baseFX-FDX, 10baseT, 10baseT-FDX, 100baseTX,
100baseTX-FDX, auto
dc0: Ethernet address: 00:a0:cc:40:3e:9b
dc0: if_start running deferred for Giant
dc0: [GIANT-LOCKED]


Any idea on what is going wrong and how I can fix it?


Marty

--
Web Installed Formmail - http://face2interface.com/formINSTal/
Webmaster's BBS - http://bbs.face2interface.com/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: intermittent boot problem

2006-09-27 Thread Marty Landman


Sorry there's a bit more info available for my problem:

$ dmesg | grep dc0
dc0: 82c169 PNIC 10/100BaseTX port 0x1400-0x14ff mem 0x4090-0x409000ff
irq 11 at device 4.0 on pci0
miibus0: MII bus on dc0
dc0: Ethernet address: 00:a0:cc:40:3e:9b
dc0: if_start running deferred for Giant
dc0: [GIANT-LOCKED]
atkbdc0: Keyboard controller (i8042) at port 0x64,0x60 on isa0
atkbd0: AT Keyboard irq 1 on atkbdc0
fdc0: Enhanced floppy controller at port 0x3f0-0x3f5 irq 6 drq 2 on isa0
fdc0: [FAST]
fd0: 1440-KB 3.5 drive on fdc0 drive 0
dc0: failed to force tx and rx to idle state
dc0: failed to force tx and rx to idle state
dc0: failed to force tx and rx to idle state
$


On 9/27/06, Marty Landman [EMAIL PROTECTED] wrote:


I've got a new FBSD 5.3 release install on an old Compaq pII-233 w/ 128M
ram. What I get when the boot fails is

tx underrun -- using store and forward mode

repeating infinitely.

Now that a reboot has succeeded here's what dmesg shows for dc0:

dc0: 82c169 PNIC 10/100BaseTX port 0x1400-0x14ff mem
0x4090-0x409000ff irq 11 at device 4.0 on pci0
miibus0: MII bus on dc0
lxtphy0: LXT970 10/100 media interface on miibus0
lxtphy0:  100baseFX, 100baseFX-FDX, 10baseT, 10baseT-FDX, 100baseTX,
100baseTX-FDX, auto
dc0: Ethernet address: 00:a0:cc:40:3e:9b
dc0: if_start running deferred for Giant
dc0: [GIANT-LOCKED]


Any idea on what is going wrong and how I can fix it?


Marty

--
Web Installed Formmail - http://face2interface.com/formINSTal/
Webmaster's BBS - http://bbs.face2interface.com/





--
Web Installed Formmail - http://face2interface.com/formINSTal/
Webmaster's BBS - http://bbs.face2interface.com/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: intermittent boot problem

2006-09-27 Thread Chuck Swiger


Marty Landman wrote:

I've got a new FBSD 5.3 release install on an old Compaq pII-233 w/ 128M
ram. What I get when the boot fails is

tx underrun -- using store and forward mode

repeating infinitely.

Now that a reboot has succeeded here's what dmesg shows for dc0:

dc0: 82c169 PNIC 10/100BaseTX port 0x1400-0x14ff mem 


You've got an Asante/Kingston/Linksys PNIC clone of the DEC 21x4x Tulip 
chipset.  I've had four out of five of those cards die within two years.  If 
upgrading to 5-STABLE or 6.2 BETA doesn't fix it, consider replacing the NIC 
with something else:


 The dc driver programs 82c168 and 82c169 PNIC chips to use the store and
 forward setting for the transmit start threshold by default.  This is to
 work around problems with some NIC/PCI bus combinations where the PNIC
 can transmit corrupt frames when operating at 100Mbps, probably due to
 PCI DMA burst transfer errors.

 The 82c168 and 82c169 PNIC chips also have a receiver bug that sometimes
 manifests during periods of heavy receive and transmit activity, where
 the chip will improperly DMA received frames to the host.  The chips
 appear to upload several kilobytes of garbage data along with the
 received frame data, dirtying several RX buffers instead of just the
 expected one.  The dc driver detects this condition and will salvage the
 frame; however, it incurs a serious performance penalty in the process.

 The PNIC chips also sometimes generate a transmit underrun error when the
 driver attempts to download the receiver filter setup frame, which can
 result in the receive filter being incorrectly programmed.  The dc driver
 will watch for this condition and requeue the setup frame until it is
 transfered successfully.

--
-Chuck
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Boot problem

2006-06-27 Thread Winston


I tried to boot via a serial console, so I modified/added the
following config files:
---
/boot/loader.conf:
boot_multicons=YES
boot_serial=YES
console=comconsole
---
/boot.config
# wyt: added
-Dh
---
Changed /etc/ttys:
ttyd0   /usr/libexec/getty std.9600   dialup  off secure
to
ttyd0   /usr/libexec/getty std.9600   xterm  on secure

However, I got the following messages while booting:
/boot.config: #
FreeBSD/i386 boot
Default: 0:ad(0,a)boot
boot:

I think I prob. made a mistake by putting a line of comment #wyt:
added at the beginning of /boot.conf and the boot loader doesn't like
it.

But if I specify /boot/kernel/kernel after the line boot:
I got a bunch of reg dumps and finally:
BTX halted

The kernel was booting fine before I make the changes. I now have the
chicken and egg problem: I need to get rid of the line of comment in
boot.conf for it to boot, but I can't access it without booting into
it.

Any hint?

WT
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Boot problem

2006-06-27 Thread Steve Kargl

On Tue, Jun 27, 2006 at 11:49:59AM -0700, Winston wrote:
 
 Any hint?
 

Find a live cd and boot it.  Mount partition and edit files
that you munged.

-- 
Steve
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

FreeBSD Boot Problem on Multiple HDDs

2006-06-11 Thread Sean M.

I just did my first ever bit of hardware hacking--salvaging a 6GB HDD
from a useless computer and installing it as a slave--and went and put
FreeBSD on it and a 3151MB partition on the master drive, which already
had Windows 2000 Professional SP1. Here is how I chopped up the disks:

ad0s1: FAT32 W2K (I have since converted to NTFS)
ad0s2: /, swap, /tmp, /etc, and /var
ad1s1: /usr

The problem is that I can't start FreeBSD. When I get to the boot
loader, I see:

F1 DOS
F2 FreeBSD
F5 Disk 1

Pressing F2 starts the typical hardware listing, then I see:

Manual root filesystem specification
...
mountroot

And the crux of the problem is that I can't type anything because the
keyboard is frozen! What can I do here?

__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: FreeBSD Boot Problem on Multiple HDDs

2006-06-11 Thread Derek Ragona

You may need to do an upgrade reinstall.  It sounds like the boot block is 
foobar.  If you reinstall the same version using the upgrade option, that 
should take care of the problem.


-Derek


At 01:38 AM 6/11/2006, Sean M. wrote:

I just did my first ever bit of hardware hacking--salvaging a 6GB HDD
from a useless computer and installing it as a slave--and went and put
FreeBSD on it and a 3151MB partition on the master drive, which already
had Windows 2000 Professional SP1. Here is how I chopped up the disks:

ad0s1: FAT32 W2K (I have since converted to NTFS)
ad0s2: /, swap, /tmp, /etc, and /var
ad1s1: /usr

The problem is that I can't start FreeBSD. When I get to the boot
loader, I see:

F1 DOS
F2 FreeBSD
F5 Disk 1

Pressing F2 starts the typical hardware listing, then I see:

Manual root filesystem specification
...
mountroot

And the crux of the problem is that I can't type anything because the
keyboard is frozen! What can I do here?

__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Odd boot problem

2005-11-06 Thread Joao Barros

On 11/5/05, Joao Barros [EMAIL PROTECTED] wrote:
 Hi,

 I needed to add an IDE disk to an already running SCSI booting machine
 for testing.
 Recently upgraded to 6.0 :) with the IDE disk connected to the
 machine, although not mounted.
 After a make kernel the machine boots fine but only if I have the IDE
 disk connected.
 Booting from the scsi disk I can clearly see it's trying to find the
 load from the ide disk.
 I tried 'atacontrol detach ata0' and reinstalling the kernel and tried
 a bsdlabel -B da0 but I still get the error, boot message follows:

 F1 FreeBSD

 Default: F1

 Invalid partition
 Invalid partition
 No /boot/loader

 FreeBSD/i386 boot
 Default: 0:ad(0,a)/boot/kernel/kernel
 boot:


 I tried 0:da(0,a)/boot/kernel/kernel but still no go.
 How can I fix this?


 --
 Joao Barros


One more odd thing I noticed:
With ad0 attached like as before this problem occurred I correctly see
this at the loader:
F1 FreeBSD
F5 Drive 1

Drive 1 is a raid array on another controller.

With ad0 disconnected and da0 being the boot drive I only see:
F1 FreeBSD

Considering that doing a make work  kernel with a ad0(which I guess
BIOS will see as the new drive 0) attached after the initial system
installation on da0 rendered booting from
da0 unusable, I think something very wrong must be happening.
The disk to consider writing any new boot information should be the
one where / lives in, not disk 0 reported by the BIOS. Well, that's my
view of it anyway...

I'm really unable to restore booting capabilities to da0 so any hints
are highly appreciated.

--
Joao Barros
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Odd boot problem

2005-11-05 Thread Joao Barros

Hi,

I needed to add an IDE disk to an already running SCSI booting machine
for testing.
Recently upgraded to 6.0 :) with the IDE disk connected to the
machine, although not mounted.
After a make kernel the machine boots fine but only if I have the IDE
disk connected.
Booting from the scsi disk I can clearly see it's trying to find the
load from the ide disk.
I tried 'atacontrol detach ata0' and reinstalling the kernel and tried
a bsdlabel -B da0 but I still get the error, boot message follows:

F1 FreeBSD

Default: F1

Invalid partition
Invalid partition
No /boot/loader

FreeBSD/i386 boot
Default: 0:ad(0,a)/boot/kernel/kernel
boot:


I tried 0:da(0,a)/boot/kernel/kernel but still no go.
How can I fix this?


--
Joao Barros
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: FreeBSD 5.2.1-STABLE boot problem

2005-10-13 Thread Kris Kennaway

On Thu, Oct 13, 2005 at 08:50:19AM +0300, Sergey Khenkin wrote:
 Hi All,
 
 I ran into a problem installing FreeBSD 5.2.1-STABLE on an old PC
 (Am5x86, 133MHz, 40M RAM, 700M HDD).
 After I finish the install and reboot the PC under FreeBSD it fails to
 load the kernel. Here's what is on the screen (manually copied):
 
 Loading /boot/defaults/loader.conf
 /boot/kernel/kernel text=0x45d64c -
 elf32_loadexec: archsw.readin failed
 /boot/kernel/kernel text=0x45d64c -
 elf32_loadexec: archsw.readin failed
 /boot/kernel/kernel text=0x45d64c -
 elf32_loadexec: archsw.readin failed
 Unable to find a kernel!
 |
 Hit [Enter] to boot immediately, or any other key for command prompt.
 Booting [/boot/kernel/kernel] ...
 /boot/kernel/kernel text=0x45d64c -
 elf32_loadexec: archsw.readin failed
 can't load 'kernel'
 
 I successfully installed the same system on several other modern PCs.
 Can anyone assist me in solving this problem and making FreeBSD boot
 up?

Step 1: Try a modern release of FreeBSD like 5.4.  5.2.1 was an early
adopter's release not intended for production use.

Kris


pgpWlc0gCSUZG.pgp
Description: PGP signature

FreeBSD 5.2.1-STABLE boot problem

2005-10-12 Thread Sergey Khenkin

Hi All,

I ran into a problem installing FreeBSD 5.2.1-STABLE on an old PC
(Am5x86, 133MHz, 40M RAM, 700M HDD).
After I finish the install and reboot the PC under FreeBSD it fails to
load the kernel. Here's what is on the screen (manually copied):

Loading /boot/defaults/loader.conf
/boot/kernel/kernel text=0x45d64c -
elf32_loadexec: archsw.readin failed
/boot/kernel/kernel text=0x45d64c -
elf32_loadexec: archsw.readin failed
/boot/kernel/kernel text=0x45d64c -
elf32_loadexec: archsw.readin failed
Unable to find a kernel!
|
Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/boot/kernel/kernel] ...
/boot/kernel/kernel text=0x45d64c -
elf32_loadexec: archsw.readin failed
can't load 'kernel'

I successfully installed the same system on several other modern PCs.
Can anyone assist me in solving this problem and making FreeBSD boot
up?

-- 
Best regards,
 Sergey  mailto:[EMAIL PROTECTED]

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

FreeBSD 5.2.1-STABLE boot problem

2005-10-12 Thread Sergey Khenkin

Hi All,

I ran into a problem installing FreeBSD 5.2.1-STABLE on an old PC
(Am5x86, 133MHz, 40M RAM, 700M HDD).
After I finish the install and reboot the PC under FreeBSD it fails to
load the kernel. Here's what is on the screen (manually copied):

Loading /boot/defaults/loader.conf
/boot/kernel/kernel text=0x45d64c -
elf32_loadexec: archsw.readin failed
/boot/kernel/kernel text=0x45d64c -
elf32_loadexec: archsw.readin failed
/boot/kernel/kernel text=0x45d64c -
elf32_loadexec: archsw.readin failed
Unable to find a kernel!
|
Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/boot/kernel/kernel] ...
/boot/kernel/kernel text=0x45d64c -
elf32_loadexec: archsw.readin failed
can't load 'kernel'

I successfully installed the same system on several other modern PCs.
Can anyone assist me in solving this problem and making FreeBSD boot
up?

-- 
Best regards,
 Sergey  mailto:[EMAIL PROTECTED]

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Diskless Boot Problem

2005-09-22 Thread Erik Norgaard


kevin stovall wrote:
I am trying to set up diskless boot with FreeBSD 6.0 BETA2. I am using 
PXE which is successful and the diskless box finds the kernel fine, but 
it hangs right before it would normally give the login prompt. It 
displays the date and then hangs. I am unable to SSH in from other 
machine. It boots fine into single user mode. Has anyone experienced 
this or have any ideas?


I just followed my own guide (www.daemonsecurity.com/pxe) from the 
beginning again and ended up with a login prompt and could login and get 
a shell.


I have learned that dhclient should not be used, the interface is 
correctly configured on boot and any further client specific 
configuration can be passed by other means, I am considering LDAP or 
some specially formatted config file.


Cheers, Erik
--
Ph: +34.666334818  web: www.locolomo.org
S/MIME Certificate: www.daemonsecurity.com/ca/8D03551FFCE04F06.crt
Subject ID:  9E:AA:18:E6:94:7A:91:44:0A:E4:DD:87:73:7F:4E:82:E7:08:9C:72
Fingerprint: 5B:D5:1E:3E:47:E7:EC:1C:4C:C8:3A:19:CC:AE:14:F5:DF:18:0F:B9
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Diskless Boot Problem


kevin stovall wrote:

Thanks for responding and sorry it took me so long to respond. I am 
still having the same problem that I was. / is mounted through nfs. Do 
you know if the dhclient does the same as you described  in 6? Also, I 
think that they did away with mfs in version 6.


you should (and have?) mount / read-only, then mount /var either as a 
mfs or nfs mounted read-write. If there is no writable /var, dhclient 
cannot store the lease - this is true both in 5.x and 6.x.


If you look through /etc/rc.d/var (there is an equivalent one for tmp) 
you will see it has three modes: yes, no and auto. If set to yes, a mfs 
/var partition is created, if auto, the startup scripts will check if 
there is a writable /var, if not, then an mfs /var is created - this is 
default.


There are good reasons for using mfs for /tmp and /var, as well as for 
not: by using mfs you have no cleanup, and no personal data is disclosed 
if logout causes a reboot every time. However, in particular for /var 
there are data that is usefull to keep: IIRC latex stores generated 
fonts there.


If you have an mfs /var then the problem mentioned should not cause 
nfs-mounts to be lost because the lease is stored in the mfs. But if 
/var is an nfs mount then you may have a problem.


I sent a problem report on this, it was closed because I didn't get back 
on it. Reason is that I haven't had time to set up diskless FBSD6 
environment. So, I'm not sure, however, if you include output from the 
terminal (yes I know it's tideus to copy), I can see if I can interpret it.


Cheers, Erik

--
Ph: +34.666334818  web: www.locolomo.org
S/MIME Certificate: www.daemonsecurity.com/ca/8D03551FFCE04F06.crt
Subject ID:  9E:AA:18:E6:94:7A:91:44:0A:E4:DD:87:73:7F:4E:82:E7:08:9C:72
Fingerprint: 5B:D5:1E:3E:47:E7:EC:1C:4C:C8:3A:19:CC:AE:14:F5:DF:18:0F:B9
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Diskless Boot Problem


Yes, / is read-only and /var is rw. Here is my fstab:

192.168.0.200:/home/diskless_ro / nfsro 0 0
192.168.0.200:/home/diskless_rw/var /var nfs rw 0 0
192.168.0.200:/home/diskless_rw/tmp /tmp nfs rw 0 0
192.168.0.200:/usr  /usr  nfsrw 0 0
proc/proc procfs rw 0 0

I will try to get more of the terminal input tomorrow. Here is the last few 
lines


Trying to mount root from nfs:192.168.0.200:/home/diskless_ro
NFS ROOT: 192.168.0.200:/home/diskless_ro
Interface fxp0 IP-Address 192.168.0.196 Broadcast 192.168.0.255

Date

Also, I will try setting varmfs and tmpmfs to YES tomorrow to see if that 
works.




you should (and have?) mount / read-only, then mount /var either as a mfs or 
nfs mounted read-write. If there is no writable /var, dhclient cannot store 
the lease - this is true both in 5.x and 6.x.


If you look through /etc/rc.d/var (there is an equivalent one for tmp) you 
will see it has three modes: yes, no and auto. If set to yes, a mfs /var 
partition is created, if auto, the startup scripts will check if there is a 
writable /var, if not, then an mfs /var is created - this is default.


There are good reasons for using mfs for /tmp and /var, as well as for not: 
by using mfs you have no cleanup, and no personal data is disclosed if 
logout causes a reboot every time. However, in particular for /var there are 
data that is usefull to keep: IIRC latex stores generated fonts there.


If you have an mfs /var then the problem mentioned should not cause 
nfs-mounts to be lost because the lease is stored in the mfs. But if /var is 
an nfs mount then you may have a problem.


I sent a problem report on this, it was closed because I didn't get back on 
it. Reason is that I haven't had time to set up diskless FBSD6 environment. 
So, I'm not sure, however, if you include output from the terminal (yes I 
know it's tideus to copy), I can see if I can interpret it.



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Diskless Boot Problem


kevin stovall wrote:

Yes, / is read-only and /var is rw. Here is my fstab:

192.168.0.200:/home/diskless_ro / nfsro 0 0
192.168.0.200:/home/diskless_rw/var /var nfs rw 0 0
192.168.0.200:/home/diskless_rw/tmp /tmp nfs rw 0 0
192.168.0.200:/usr  /usr  nfsrw 0 0
proc/proc procfs rw 0 0


Question: what is your /etc/exports? Did you export all rw or 
/home/diskless_ro ro? Thing is that it's tricky to have both rw and ro 
exports on the same partition.


Cheers, Erik
--
Ph: +34.666334818  web: www.locolomo.org
S/MIME Certificate: www.daemonsecurity.com/ca/8D03551FFCE04F06.crt
Subject ID:  9E:AA:18:E6:94:7A:91:44:0A:E4:DD:87:73:7F:4E:82:E7:08:9C:72
Fingerprint: 5B:D5:1E:3E:47:E7:EC:1C:4C:C8:3A:19:CC:AE:14:F5:DF:18:0F:B9
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Diskless Boot Problem


I exported everything rw.

/ -alldirs -maproot=root -network 192.168.0 -mask 255.255.255.0
/home -alldirs -maproot=root -network 192.168.0.0 -mask 255.255.255.0





Question: what is your /etc/exports? Did you export all rw or 
/home/diskless_ro ro? Thing is that it's tricky to have both rw and ro 
exports on the same partition.



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Diskless Boot Problem


kevin stovall wrote:

I exported everything rw.

/ -alldirs -maproot=root -network 192.168.0 -mask 255.255.255.0
/home -alldirs -maproot=root -network 192.168.0.0 -mask 255.255.255.0


and what do you see if you run showmount(8) ?

Cheers, Erik
--
Ph: +34.666334818  web: www.locolomo.org
S/MIME Certificate: www.daemonsecurity.com/ca/8D03551FFCE04F06.crt
Subject ID:  9E:AA:18:E6:94:7A:91:44:0A:E4:DD:87:73:7F:4E:82:E7:08:9C:72
Fingerprint: 5B:D5:1E:3E:47:E7:EC:1C:4C:C8:3A:19:CC:AE:14:F5:DF:18:0F:B9
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Diskless Boot Problem


kevin stovall wrote:

I exported everything rw.

/ -alldirs -maproot=root -network 192.168.0 -mask 255.255.255.0
/home -alldirs -maproot=root -network 192.168.0.0 -mask 255.255.255.0


is /usr a separate disklabel? because, then it doesn't appear to be 
exported.


Cheers, Erik
--
Ph: +34.666334818  web: www.locolomo.org
S/MIME Certificate: www.daemonsecurity.com/ca/8D03551FFCE04F06.crt
Subject ID:  9E:AA:18:E6:94:7A:91:44:0A:E4:DD:87:73:7F:4E:82:E7:08:9C:72
Fingerprint: 5B:D5:1E:3E:47:E7:EC:1C:4C:C8:3A:19:CC:AE:14:F5:DF:18:0F:B9
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Diskless Boot Problem


# showmount
Hosts on localhost:
192.168.0.196




and what do you see if you run showmount(8) ?


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Diskless Boot Problem


kevin stovall wrote:

# showmount
Hosts on localhost:
192.168.0.196


It's ok if you read the manpage to see what interesting options there 
are to get some more info. If you want help, then you also need to 
provide the interesting stuff. Using -e you can see what mounts are 
actually exported, fx. I have:


# showmount -e
Exports list on localhost:
/var/diskless/FreeBSD  192.168.0.0
/var/diskless/192.168.0.16 192.168.0.16
/home  192.168.0.0

I pointed you to a guide I wrote - although I haven't finished it 
because I haven't got to the true diskless system yet - most of the 
advice I have given here is actually explained.


Cheers, Erik
--
Ph: +34.666334818  web: www.locolomo.org
S/MIME Certificate: www.daemonsecurity.com/ca/8D03551FFCE04F06.crt
Subject ID:  9E:AA:18:E6:94:7A:91:44:0A:E4:DD:87:73:7F:4E:82:E7:08:9C:72
Fingerprint: 5B:D5:1E:3E:47:E7:EC:1C:4C:C8:3A:19:CC:AE:14:F5:DF:18:0F:B9
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Diskless Boot Problem


No, I have two disks, / and /home.


is /usr a separate disklabel?


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Diskless Boot Problem

2005-09-20 Thread kevin stovall

Thanks for responding and sorry it took me so long to respond. I am still 
having the same problem that I was. / is mounted through nfs. Do you know if 
the dhclient does the same as you described  in 6? Also, I think that they 
did away with mfs in version 6.


BLOCKQUOTE style='PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #A0C6E5 
2px solid; MARGIN-RIGHT: 0px'font 
style='FONT-SIZE:11px;FONT-FAMILY:tahoma,sans-serif'hr color=#A0C6E5 
size=1
From:  iErik Norgaard lt;[EMAIL PROTECTED]gt;/ibrTo:  ikevin 
stovall lt;[EMAIL PROTECTED]gt;/ibrCC:  
ifreebsd-questions@freebsd.org/ibrSubject:  iRe: Diskless Boot 
Problem/ibrDate:  iWed, 14 Sep 2005 11:10:37 +0200/ibrgt;kevin 
stovall wrote:brgt;gt;The root file system seems to mount correctly, but 
I am not sure brgt;gt;how to tell. The root file system is 
/home/diskless_ro which is set brgt;gt;up correctly for NFS. I don't 
have a memory file system set up, so brgt;gt;this is likely the 
problem.brgt;brgt;You will use either or, not both. A memory file 
system will ocupy brgt;ram so if you don't have much it's not a good 
idea. Also, var and brgt;tmp may be created as mfs if these are not 
mounted or toggled in brgt;rc.conf. (see /etc/rc.d/var and /etc/rc.d/tmp) 
so you may run out of brgt;ram.brgt;brgt;Check that you can mount 
the nfs root device. There are some brgt;permission stuff to be aware of 
if you have multiple exports on the brgt;same device.brgt;brgt;I 
tried once, a while ago to set up diskless systems, and wrote my brgt;own 
guide to keep track of what I was doing, you can read it 
here:brgt;brgt;   www.daemonsecurity.com/pxebrgt;brgt;I didn't 
get it working, my problem was that the dhclient of 5.4 brgt;would 
unconfigure the NIC before obtaining a new lease meaning that brgt;any 
NFS mounted filesystems was lost and then it couldn't write the 
brgt;lease file. This problem could posibly be solved by using mfs for 
brgt;/var and / but I only have 112 MB ram, so I prefered to have it nfs 
brgt;mounted.brgt;brgt;Cheers, Erikbrgt;brgt;--brgt;Ph: 
+34.666334818  web: 
brgt;www.locolomo.orgbrgt;S/MIME Certificate: 
www.daemonsecurity.com/ca/8D03551FFCE04F06.crtbrgt;Subject ID:  
brgt;9E:AA:18:E6:94:7A:91:44:0A:E4:DD:87:73:7F:4E:82:E7:08:9C:72brgt;Fingerprint: 
brgt;5B:D5:1E:3E:47:E7:EC:1C:4C:C8:3A:19:CC:AE:14:F5:DF:18:0F:B9brgt;___brgt;freebsd-questions@freebsd.org 
mailing 
listbrgt;http://lists.freebsd.org/mailman/listinfo/freebsd-questionsbrgt;To 
unsubscribe, send any mail to 
brgt;quot;[EMAIL PROTECTED]quot;br/font/BLOCKQUOTE



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Diskless Boot Problem

2005-09-14 Thread kevin stovall

I am trying to set up diskless boot with FreeBSD 6.0 BETA2. I am using PXE 
which is successful and the diskless box finds the kernel fine, but it hangs 
right before it would normally give the login prompt. It displays the date 
and then hangs. I am unable to SSH in from other machine. It boots fine into 
single user mode. Has anyone experienced this or have any ideas?



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Diskless Boot Problem

2005-09-14 Thread Erik Norgaard


kevin stovall wrote:
I am trying to set up diskless boot with FreeBSD 6.0 BETA2. I am using 
PXE which is successful and the diskless box finds the kernel fine, but 
it hangs right before it would normally give the login prompt. It 
displays the date and then hangs. I am unable to SSH in from other 
machine. It boots fine into single user mode. Has anyone experienced 
this or have any ideas?


Does it correctly mount the root file system? What is your root file 
system? a memory file system downloaded with tftp or nfs mount?


I had the same problem (I recall it hanging just after displaying the 
date) recently on my disked laptop because /etc/ttys was corrupt after a 
crash. Also, I had no problems booting in single-user mode.


Cheers, Erik

--
Ph: +34.666334818  web: www.locolomo.org
S/MIME Certificate: www.daemonsecurity.com/ca/8D03551FFCE04F06.crt
Subject ID:  9E:AA:18:E6:94:7A:91:44:0A:E4:DD:87:73:7F:4E:82:E7:08:9C:72
Fingerprint: 5B:D5:1E:3E:47:E7:EC:1C:4C:C8:3A:19:CC:AE:14:F5:DF:18:0F:B9
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Diskless Boot Problem

2005-09-14 Thread kevin stovall

The root file system seems to mount correctly, but I am not sure how to 
tell. The root file system is /home/diskless_ro which is set up correctly 
for NFS. I don't have a memory file system set up, so this is likely the 
problem.


BLOCKQUOTE style='PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #A0C6E5 
2px solid; MARGIN-RIGHT: 0px'font 
style='FONT-SIZE:11px;FONT-FAMILY:tahoma,sans-serif'hr color=#A0C6E5 
size=1
From:  iErik Norgaard lt;[EMAIL PROTECTED]gt;/ibrTo:  ikevin 
stovall lt;[EMAIL PROTECTED]gt;/ibrCC:  
ifreebsd-questions@freebsd.org/ibrSubject:  iRe: Diskless Boot 
Problem/ibrDate:  iWed, 14 Sep 2005 10:00:09 +0200/ibrgt;kevin 
stovall wrote:brgt;gt;I am trying to set up diskless boot with FreeBSD 
6.0 BETA2. I am brgt;gt;using PXE which is successful and the diskless 
box finds the kernel brgt;gt;fine, but it hangs right before it would 
normally give the login brgt;gt;prompt. It displays the date and then 
hangs. I am unable to SSH in brgt;gt;from other machine. It boots fine 
into single user mode. Has anyone brgt;gt;experienced this or have any 
ideas?brgt;brgt;Does it correctly mount the root file system? What is 
your root file brgt;system? a memory file system downloaded with tftp or 
nfs mount?brgt;brgt;I had the same problem (I recall it hanging just 
after displaying brgt;the date) recently on my disked laptop because 
/etc/ttys was corrupt brgt;after a crash. Also, I had no problems booting 
in single-user mode.brgt;brgt;Cheers, 
Erikbrgt;brgt;--brgt;Ph: +34.666334818  
web: brgt;www.locolomo.orgbrgt;S/MIME Certificate: 
www.daemonsecurity.com/ca/8D03551FFCE04F06.crtbrgt;Subject ID:  
brgt;9E:AA:18:E6:94:7A:91:44:0A:E4:DD:87:73:7F:4E:82:E7:08:9C:72brgt;Fingerprint: 
brgt;5B:D5:1E:3E:47:E7:EC:1C:4C:C8:3A:19:CC:AE:14:F5:DF:18:0F:B9brgt;___brgt;freebsd-questions@freebsd.org 
mailing 
listbrgt;http://lists.freebsd.org/mailman/listinfo/freebsd-questionsbrgt;To 
unsubscribe, send any mail to 
brgt;quot;[EMAIL PROTECTED]quot;br/font/BLOCKQUOTE



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Diskless Boot Problem

2005-09-14 Thread Erik Norgaard


kevin stovall wrote:
The root file system seems to mount correctly, but I am not sure how to 
tell. The root file system is /home/diskless_ro which is set up 
correctly for NFS. I don't have a memory file system set up, so this is 
likely the problem.


You will use either or, not both. A memory file system will ocupy ram so 
if you don't have much it's not a good idea. Also, var and tmp may be 
created as mfs if these are not mounted or toggled in rc.conf. (see 
/etc/rc.d/var and /etc/rc.d/tmp) so you may run out of ram.


Check that you can mount the nfs root device. There are some permission 
stuff to be aware of if you have multiple exports on the same device.


I tried once, a while ago to set up diskless systems, and wrote my own 
guide to keep track of what I was doing, you can read it here:


  www.daemonsecurity.com/pxe

I didn't get it working, my problem was that the dhclient of 5.4 would 
unconfigure the NIC before obtaining a new lease meaning that any NFS 
mounted filesystems was lost and then it couldn't write the lease file. 
This problem could posibly be solved by using mfs for /var and / but I 
only have 112 MB ram, so I prefered to have it nfs mounted.


Cheers, Erik

--
Ph: +34.666334818  web: www.locolomo.org
S/MIME Certificate: www.daemonsecurity.com/ca/8D03551FFCE04F06.crt
Subject ID:  9E:AA:18:E6:94:7A:91:44:0A:E4:DD:87:73:7F:4E:82:E7:08:9C:72
Fingerprint: 5B:D5:1E:3E:47:E7:EC:1C:4C:C8:3A:19:CC:AE:14:F5:DF:18:0F:B9
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: boot problem - how can I access the file system

2005-09-06 Thread Norberto Meijome


Robert Fitzpatrick wrote:

I made a mistake to my /boot/loader.conf file and now the system hangs
after pressing F1 and before the boot options menu. How can I access the
file to edit it? I have the install CD, but can't seem to figure out how
to get to the file system.


Hi Robert,
I'd get FreesBie (live FreeBSD CD, like knoppix is to linux) from 
http://www.freesbie.org/ and use it. it's a fully working system in a CD 
so you wont have to fight with the restricted shells of fixit CDs,etc 
(which most of the times I've found to be more frustrating than the 
actual problem I'm trying to solve).


good luck,
Beto
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: boot problem - how can I access the file system

2005-09-03 Thread Robert Fitzpatrick

On Sat, 2005-09-03 at 13:31 -0500, Kevin Kinsey wrote:
 I made a mistake to my /boot/loader.conf file and now the system hangs
 after pressing F1 and before the boot options menu. How can I access the
 file to edit it? I have the install CD, but can't seem to figure out how
 to get to the file system.
 3] sysinstall's emergency holographic shell -
dunno if it can edit.  Might be able to cp
a backup, though, if you have one.
  

I booted from CD and initiated the holographic shell, where can I find
help on how to access the drive and edit the file? Thanks.

-- 
Robert

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: boot problem - how can I access the file system

2005-09-03 Thread Kevin Kinsey


Robert Fitzpatrick wrote:


I made a mistake to my /boot/loader.conf file and now the system hangs
after pressing F1 and before the boot options menu. How can I access the
file to edit it? I have the install CD, but can't seem to figure out how
to get to the file system.

 



When it happened to me, I had the good fortune to
have another FBSD system nearby.  Mounted it there,
edited mistake, voila.

What resources do you have? 


Further thoughts: 1] Boot off of a live CD
(Matt Olander posted a link to a nice, fairly small
one on advocacy@ yesterday, IIRC).

2] Fixit CD or Fixit floppy.  Available via FTP
from ftp.freebsd.org.

3] sysinstall's emergency holographic shell -
  dunno if it can edit.  Might be able to cp
  a backup, though, if you have one.

HTH,

Kevin Kinsey
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

boot problem - how can I access the file system

2005-09-03 Thread Robert Fitzpatrick

I made a mistake to my /boot/loader.conf file and now the system hangs
after pressing F1 and before the boot options menu. How can I access the
file to edit it? I have the install CD, but can't seem to figure out how
to get to the file system.

-- 
Robert

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: boot problem - how can I access the file system

2005-09-03 Thread Robert Fitzpatrick

On Sat, 2005-09-03 at 13:31 -0500, Kevin Kinsey wrote:
 What resources do you have? 
Don't have another FreeBSD machine at this location. I have my SuSE 9.2
linux workstation and Windows 2003 server machine.

 2] Fixit CD or Fixit floppy.  Available via FTP
 from ftp.freebsd.org.

I tried the Fixit CD (disc 2) and it says 'ldconfig could not create the
ld.so hints' and that my dynamic executables from the disc most likely
won't work. When I Alt+F4, typing any command such as 'ls' gives me a
segmentation fault. I am running 5.3 on a old AMD 500 with 512MB RAM.

Not sure how to get the images for floppies on to my floppy. The 'dd'
command does not seem to work in my linux env and I don't find the
fdimage.exe for Windows.

Appreciate any help.

-- 
Robert

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: boot problem - how can I access the file system

2005-09-03 Thread nawcom


http://uranus.it.swin.edu.au/~jn/linux/

and specifically:

http://uranus.it.swin.edu.au/~jn/linux/rawwrite.htm

these are all windows programs that take away the frustration
of installing linux. however freebsd and any os follows the same concept 
when it comes

to boot disks (.img) - so give rawwrite a try.

if you really want to do it unix style via dd he has a windows copy of 
dd on there:


http://uranus.it.swin.edu.au/~jn/linux/rawwrite/dd.htm

Let me know if you need any help making the fixit disk via any of the 
utilities i just mentioned.

-Ben


Robert Fitzpatrick wrote:


On Sat, 2005-09-03 at 13:31 -0500, Kevin Kinsey wrote:
 

What resources do you have? 
   


Don't have another FreeBSD machine at this location. I have my SuSE 9.2
linux workstation and Windows 2003 server machine.

 


2] Fixit CD or Fixit floppy.  Available via FTP
from ftp.freebsd.org.
   



I tried the Fixit CD (disc 2) and it says 'ldconfig could not create the
ld.so hints' and that my dynamic executables from the disc most likely
won't work. When I Alt+F4, typing any command such as 'ls' gives me a
segmentation fault. I am running 5.3 on a old AMD 500 with 512MB RAM.

Not sure how to get the images for floppies on to my floppy. The 'dd'
command does not seem to work in my linux env and I don't find the
fdimage.exe for Windows.

Appreciate any help.

 



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

How do I diagnose and fix a boot problem?

2005-09-02 Thread Frederick N. Brier

I had an old FreeBSD 4.8 server and wanted to upgrade it to 5.4. So I
backed it up to both DVD and to another 5.4 system. The only change in
the hardware was adding a Zonet ZEN3300E gigabit PCI adapter (Realtek
RTL8169S-32). It is an old dual 600 P3 with 1GB RAM and a 3Ware 7000-2
controller with 2 160GB drives. I wiped the system and started from
scratch with a standard (everything) install. I added the updated
packages and got Samba, Apache2, the TWiki installed with all the shared
files and twiki files restored. The system was rebooted at least 5-6
times to make sure everything started up properly, and it did great. I
was just tweaking the sshd settings so that I could run cygwin XFree86
over ssh, and did a ps to get the pid of sshd, and ps came back with
an error message. I had never seen this before and so figured perhaps a
reboot was in order. So I did and ended up with this::

--
FreeBSD/i386 bootstrap loader, Revision 0.8

Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [kernel]...
can't load 'kernel'
can't load 'kernel.old'

Type '?' for a list of commands, 'help' for more detailed help.
ok
--
So I booted using floppies and a CD (the SCSI CD is not bootable - old Adaptec controller) and loaded
the Live CD (disk 1). Going into Fixit mode, I mounted the first slice. Everything was fine no damage.
The kernel was there with the same date and size as the version on the Live CD. I read through the
Handbook section 12.3. None of the files had a recent timestamp. I thought perhaps the MBR a file had
been corrupted. I tried the command disklabel -B twed0s1 which executed with no errors.
When I tried the command fdisk -B -b /boot/boot0 twed0 It failed saying it could not find
/dev/twed0 or if the correct directory was /dev, then twedo could not be found. Yet the device
file was in /dev, the values looked reasonable, and df and other file system utilities were returning
valid values.

I tried rebooting again and looked variable values. Currdev and Loaddev are both
disk1s1a which I am not sure is correct, but I get an error message if I try
to change it to twed0s1a.

Not sure what to try next. I don't know what the problem is or what caused the
it. Any help or hints as to how to diagnose the problem or fix this would be
greatly appreciated. Thank you.

Frederick N. Brier

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem RESOLVED

2005-09-01 Thread Robert Slade

On Wed, 2005-08-31 at 17:26, Robert Slade wrote:
 On Wed, 2005-08-31 at 00:21, Vizion wrote:
  On Tuesday 30 August 2005 13:31,  the author Robert Slade contributed to 
  the 
  dialogue on-
   Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem: 
  
  On Tue, 2005-08-30 at 21:20, Vizion wrote:
   On Tuesday 30 August 2005 13:22,  the author Robert Slade contributed to
   the dialogue on-
  
Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem:
   On Tue, 2005-08-30 at 20:10, Vizion wrote:
On Tuesday 30 August 2005 12:05,  the author Robert Slade contributed
to the dialogue on-
   
 Proliant 5000 sever Fbsd 5.4 (re)boot problem:
Hiya,

I've been working on this beasty on and off for some time. It's a 
Quad
processor 1 Gbyte of memory and 5 scsi drives using the 2p raid
controller setup as 2 raid arrays + 1 spare.

The machine works fine with 5.4 release #0 with the supplied generic
kernel.

The problem(s) I have been having are:

1. When I recompiled the Kernel with SMP support, I get random
 reboots. It also fails to boot sometimes failing at the point after
 waiting for the scsi drives to settle. I get some error codes and
 Fbsd fails to find the boot device.

2. I CVSuped to 5.4 release #2 and recompiled the Kernel with SMP
support. This does to boot at all. It gets as far as the waiting 15s
 for scsi devices to settle, then (appears to) reset the scsi
 controller and immediately tries to access the drives (does not
 wait). I have tried recompiling with scsi_delay set to 3 (30s)
 with no change.

I have checked dmesg and message logs but there is nothing related to
the problem(s) there.

I have gone back to the 5.4 release #0 single processor kernel for 
now
which is a shame as the machine is slow without the multi processor
support.

The only thing out of the ordinary I have noted is a tx underunn --
increasing threshold to 512 bytes  message which appears related to
running kde remotely via vncserver and tinync.

Any ideas, I can send conf files etc if needed.

Thanks

Rob
   
What are your bios setting?
My guess is that you have not made the right setting using the 
siftware
and configuration utilities
david
   
   David,
   
   Thanks. The BIOS setting appear ok - OS type is set as UNIX (Small disk
   geometry) and the machine passes all the diagnostics.
   
   Rob
  
   I cannot remember - but I have sneaking notion that you need to set it as
   linux
  
  Tried that too :-). I think that the problem is that with 5.4 release #2
  it is trying to access that scsi drives immediately then inducing the
  kernel panic for 15s.  Rather than inducing the panic 1st.
  
  Rob
  
  
  Did you follow my suggestion and search the HP resources with freebsd and 
  your 
  model.  I have had the same problem myself I am pretty certain it was fixed 
  by changes using the Proliant Essrntial Foundation Pack.. but my memory may 
  not be accurate.
  david
 
 David,
 
 I did update the system and controller ROMs whne the machine was running
 windows. I have been on the HP site and as far as I can tell I have the
 latest.
 
 Rob

For the record, lucking under SCO Unix is an update to the Raid
Controller firmware which fixes the problem. You do need Dos or Windows
to create the self booting disks. Only disk 1 is needed for the SMART 2P
controller. The update appears to be only listed under SC Unix though.

Rob


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

RE: Proliant 5000 sever Fbsd 5.4 (re)boot problem

2005-08-31 Thread Ted Mittelstaedt

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Vizion
Sent: Tuesday, August 30, 2005 4:21 PM
To: freebsd-questions@freebsd.org
Cc: Robert Slade
Subject: Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem

Did you follow my suggestion and search the HP resources with
freebsd and your
model.  I have had the same problem myself I am pretty certain
it was fixed
by changes using the Proliant Essrntial Foundation Pack.. but
my memory may
not be accurate.

Yeah, what a awful design!  You have to load an entire full-blown
Windows install just to update the microcode in the SCSI raid
controller.  I saw they had done this the last time I setup a
Compaq server and nearly barfed.

You can still firmware update the machines' BIOS with a bootable
floppy but that's it.  To get anything else, helo Windows!

At least you get the satisfaction of scratching it off once you've
done the update.

Ted
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.344 / Virus Database: 267.10.17/85 - Release Date: 8/30/2005

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

RE: Proliant 5000 sever Fbsd 5.4 (re)boot problem

2005-08-31 Thread Robert Slade

On Wed, 2005-08-31 at 07:01, Ted Mittelstaedt wrote:
 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] Behalf Of Vizion
 Sent: Tuesday, August 30, 2005 4:21 PM
 To: freebsd-questions@freebsd.org
 Cc: Robert Slade
 Subject: Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem

 Did you follow my suggestion and search the HP resources with
 freebsd and your
 model.  I have had the same problem myself I am pretty certain
 it was fixed
 by changes using the Proliant Essrntial Foundation Pack.. but
 my memory may
 not be accurate.

 Yeah, what a awful design!  You have to load an entire full-blown
 Windows install just to update the microcode in the SCSI raid
 controller.  I saw they had done this the last time I setup a
 Compaq server and nearly barfed.

 You can still firmware update the machines' BIOS with a bootable
 floppy but that's it.  To get anything else, helo Windows!

 At least you get the satisfaction of scratching it off once you've
 done the update.

 Ted
 --

Thanks Ted  David,

The HP site does not turn up anything about FreeBSD and the Proliant.
However I have found out that the Smart-2 family controllers do have an
update. There is a Linux version of the flash utility so I'll try that
first.

Rob

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem

2005-08-31 Thread Robert Slade

On Wed, 2005-08-31 at 00:21, Vizion wrote:
 On Tuesday 30 August 2005 13:31,  the author Robert Slade contributed to the 
 dialogue on-
  Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem: 
 
 On Tue, 2005-08-30 at 21:20, Vizion wrote:
  On Tuesday 30 August 2005 13:22,  the author Robert Slade contributed to
  the dialogue on-
 
   Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem:
  On Tue, 2005-08-30 at 20:10, Vizion wrote:
   On Tuesday 30 August 2005 12:05,  the author Robert Slade contributed
   to the dialogue on-
  
Proliant 5000 sever Fbsd 5.4 (re)boot problem:
   Hiya,
   
   I've been working on this beasty on and off for some time. It's a Quad
   processor 1 Gbyte of memory and 5 scsi drives using the 2p raid
   controller setup as 2 raid arrays + 1 spare.
   
   The machine works fine with 5.4 release #0 with the supplied generic
   kernel.
   
   The problem(s) I have been having are:
   
   1. When I recompiled the Kernel with SMP support, I get random
reboots. It also fails to boot sometimes failing at the point after
waiting for the scsi drives to settle. I get some error codes and
Fbsd fails to find the boot device.
   
   2. I CVSuped to 5.4 release #2 and recompiled the Kernel with SMP
   support. This does to boot at all. It gets as far as the waiting 15s
for scsi devices to settle, then (appears to) reset the scsi
controller and immediately tries to access the drives (does not
wait). I have tried recompiling with scsi_delay set to 3 (30s)
with no change.
   
   I have checked dmesg and message logs but there is nothing related to
   the problem(s) there.
   
   I have gone back to the 5.4 release #0 single processor kernel for now
   which is a shame as the machine is slow without the multi processor
   support.
   
   The only thing out of the ordinary I have noted is a tx underunn --
   increasing threshold to 512 bytes  message which appears related to
   running kde remotely via vncserver and tinync.
   
   Any ideas, I can send conf files etc if needed.
   
   Thanks
   
   Rob
  
   What are your bios setting?
   My guess is that you have not made the right setting using the siftware
   and configuration utilities
   david
  
  David,
  
  Thanks. The BIOS setting appear ok - OS type is set as UNIX (Small disk
  geometry) and the machine passes all the diagnostics.
  
  Rob
 
  I cannot remember - but I have sneaking notion that you need to set it as
  linux
 
 Tried that too :-). I think that the problem is that with 5.4 release #2
 it is trying to access that scsi drives immediately then inducing the
 kernel panic for 15s.  Rather than inducing the panic 1st.
 
 Rob
 
 
 Did you follow my suggestion and search the HP resources with freebsd and 
 your 
 model.  I have had the same problem myself I am pretty certain it was fixed 
 by changes using the Proliant Essrntial Foundation Pack.. but my memory may 
 not be accurate.
 david

David,

I did update the system and controller ROMs whne the machine was running
windows. I have been on the HP site and as far as I can tell I have the
latest.

Rob

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Proliant 5000 sever Fbsd 5.4 (re)boot problem

2005-08-30 Thread Robert Slade

Hiya, 

I've been working on this beasty on and off for some time. It's a Quad
processor 1 Gbyte of memory and 5 scsi drives using the 2p raid
controller setup as 2 raid arrays + 1 spare.

The machine works fine with 5.4 release #0 with the supplied generic
kernel. 

The problem(s) I have been having are:

1. When I recompiled the Kernel with SMP support, I get random reboots.
It also fails to boot sometimes failing at the point after waiting for
the scsi drives to settle. I get some error codes and Fbsd fails to find
the boot device. 

2. I CVSuped to 5.4 release #2 and recompiled the Kernel with SMP
support. This does to boot at all. It gets as far as the waiting 15s for
scsi devices to settle, then (appears to) reset the scsi controller and
immediately tries to access the drives (does not wait). I have tried
recompiling with scsi_delay set to 3 (30s) with no change.

I have checked dmesg and message logs but there is nothing related to
the problem(s) there.

I have gone back to the 5.4 release #0 single processor kernel for now
which is a shame as the machine is slow without the multi processor
support.

The only thing out of the ordinary I have noted is a tx underunn --
increasing threshold to 512 bytes  message which appears related to
running kde remotely via vncserver and tinync.

Any ideas, I can send conf files etc if needed.

Thanks

Rob

  



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem

2005-08-30 Thread Vizion

On Tuesday 30 August 2005 12:05,  the author Robert Slade contributed to the 
dialogue on-
 Proliant 5000 sever Fbsd 5.4 (re)boot problem: 

Hiya,

I've been working on this beasty on and off for some time. It's a Quad
processor 1 Gbyte of memory and 5 scsi drives using the 2p raid
controller setup as 2 raid arrays + 1 spare.

The machine works fine with 5.4 release #0 with the supplied generic
kernel.

The problem(s) I have been having are:

1. When I recompiled the Kernel with SMP support, I get random reboots.
It also fails to boot sometimes failing at the point after waiting for
the scsi drives to settle. I get some error codes and Fbsd fails to find
the boot device.

2. I CVSuped to 5.4 release #2 and recompiled the Kernel with SMP
support. This does to boot at all. It gets as far as the waiting 15s for
scsi devices to settle, then (appears to) reset the scsi controller and
immediately tries to access the drives (does not wait). I have tried
recompiling with scsi_delay set to 3 (30s) with no change.

I have checked dmesg and message logs but there is nothing related to
the problem(s) there.

I have gone back to the 5.4 release #0 single processor kernel for now
which is a shame as the machine is slow without the multi processor
support.

The only thing out of the ordinary I have noted is a tx underunn --
increasing threshold to 512 bytes  message which appears related to
running kde remotely via vncserver and tinync.

Any ideas, I can send conf files etc if needed.

Thanks

Rob

What are your bios setting?
My guess is that you have not made the right setting using the siftware and 
configuration utilities
david
-- 
40 yrs navigating and computing in blue waters.
English Owner  Captain of British Registered 60' bluewater Ketch S/V Taurus.
 Currently in San Diego, CA. Sailing bound for Europe via Panama Canal after 
completing engineroom refit.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem

2005-08-30 Thread Robert Slade

On Tue, 2005-08-30 at 20:10, Vizion wrote:
 On Tuesday 30 August 2005 12:05,  the author Robert Slade contributed to the 
 dialogue on-
  Proliant 5000 sever Fbsd 5.4 (re)boot problem: 
 
 Hiya,
 
 I've been working on this beasty on and off for some time. It's a Quad
 processor 1 Gbyte of memory and 5 scsi drives using the 2p raid
 controller setup as 2 raid arrays + 1 spare.
 
 The machine works fine with 5.4 release #0 with the supplied generic
 kernel.
 
 The problem(s) I have been having are:
 
 1. When I recompiled the Kernel with SMP support, I get random reboots.
 It also fails to boot sometimes failing at the point after waiting for
 the scsi drives to settle. I get some error codes and Fbsd fails to find
 the boot device.
 
 2. I CVSuped to 5.4 release #2 and recompiled the Kernel with SMP
 support. This does to boot at all. It gets as far as the waiting 15s for
 scsi devices to settle, then (appears to) reset the scsi controller and
 immediately tries to access the drives (does not wait). I have tried
 recompiling with scsi_delay set to 3 (30s) with no change.
 
 I have checked dmesg and message logs but there is nothing related to
 the problem(s) there.
 
 I have gone back to the 5.4 release #0 single processor kernel for now
 which is a shame as the machine is slow without the multi processor
 support.
 
 The only thing out of the ordinary I have noted is a tx underunn --
 increasing threshold to 512 bytes  message which appears related to
 running kde remotely via vncserver and tinync.
 
 Any ideas, I can send conf files etc if needed.
 
 Thanks
 
 Rob
 
 What are your bios setting?
 My guess is that you have not made the right setting using the siftware and 
 configuration utilities
 david

David,

Thanks. The BIOS setting appear ok - OS type is set as UNIX (Small disk
geometry) and the machine passes all the diagnostics.

Rob

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem

2005-08-30 Thread Robert Slade

On Tue, 2005-08-30 at 21:20, Vizion wrote:
 On Tuesday 30 August 2005 13:22,  the author Robert Slade contributed to the 
 dialogue on-
  Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem: 
 
 On Tue, 2005-08-30 at 20:10, Vizion wrote:
  On Tuesday 30 August 2005 12:05,  the author Robert Slade contributed to
  the dialogue on-
 
   Proliant 5000 sever Fbsd 5.4 (re)boot problem:
  Hiya,
  
  I've been working on this beasty on and off for some time. It's a Quad
  processor 1 Gbyte of memory and 5 scsi drives using the 2p raid
  controller setup as 2 raid arrays + 1 spare.
  
  The machine works fine with 5.4 release #0 with the supplied generic
  kernel.
  
  The problem(s) I have been having are:
  
  1. When I recompiled the Kernel with SMP support, I get random reboots.
  It also fails to boot sometimes failing at the point after waiting for
  the scsi drives to settle. I get some error codes and Fbsd fails to find
  the boot device.
  
  2. I CVSuped to 5.4 release #2 and recompiled the Kernel with SMP
  support. This does to boot at all. It gets as far as the waiting 15s for
  scsi devices to settle, then (appears to) reset the scsi controller and
  immediately tries to access the drives (does not wait). I have tried
  recompiling with scsi_delay set to 3 (30s) with no change.
  
  I have checked dmesg and message logs but there is nothing related to
  the problem(s) there.
  
  I have gone back to the 5.4 release #0 single processor kernel for now
  which is a shame as the machine is slow without the multi processor
  support.
  
  The only thing out of the ordinary I have noted is a tx underunn --
  increasing threshold to 512 bytes  message which appears related to
  running kde remotely via vncserver and tinync.
  
  Any ideas, I can send conf files etc if needed.
  
  Thanks
  
  Rob
 
  What are your bios setting?
  My guess is that you have not made the right setting using the siftware
  and configuration utilities
  david
 
 David,
 
 Thanks. The BIOS setting appear ok - OS type is set as UNIX (Small disk
 geometry) and the machine passes all the diagnostics.
 
 Rob
 
 I cannot remember - but I have sneaking notion that you need to set it as 
 linux

Tried that too :-). I think that the problem is that with 5.4 release #2
it is trying to access that scsi drives immediately then inducing the
kernel panic for 15s.  Rather than inducing the panic 1st.

Rob 

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem

2005-08-30 Thread Vizion

On Tuesday 30 August 2005 13:31,  the author Robert Slade contributed to the 
dialogue on-
 Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem: 

On Tue, 2005-08-30 at 21:20, Vizion wrote:
 On Tuesday 30 August 2005 13:22,  the author Robert Slade contributed to
 the dialogue on-

  Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem:
 On Tue, 2005-08-30 at 20:10, Vizion wrote:
  On Tuesday 30 August 2005 12:05,  the author Robert Slade contributed
  to the dialogue on-
 
   Proliant 5000 sever Fbsd 5.4 (re)boot problem:
  Hiya,
  
  I've been working on this beasty on and off for some time. It's a Quad
  processor 1 Gbyte of memory and 5 scsi drives using the 2p raid
  controller setup as 2 raid arrays + 1 spare.
  
  The machine works fine with 5.4 release #0 with the supplied generic
  kernel.
  
  The problem(s) I have been having are:
  
  1. When I recompiled the Kernel with SMP support, I get random
   reboots. It also fails to boot sometimes failing at the point after
   waiting for the scsi drives to settle. I get some error codes and
   Fbsd fails to find the boot device.
  
  2. I CVSuped to 5.4 release #2 and recompiled the Kernel with SMP
  support. This does to boot at all. It gets as far as the waiting 15s
   for scsi devices to settle, then (appears to) reset the scsi
   controller and immediately tries to access the drives (does not
   wait). I have tried recompiling with scsi_delay set to 3 (30s)
   with no change.
  
  I have checked dmesg and message logs but there is nothing related to
  the problem(s) there.
  
  I have gone back to the 5.4 release #0 single processor kernel for now
  which is a shame as the machine is slow without the multi processor
  support.
  
  The only thing out of the ordinary I have noted is a tx underunn --
  increasing threshold to 512 bytes  message which appears related to
  running kde remotely via vncserver and tinync.
  
  Any ideas, I can send conf files etc if needed.
  
  Thanks
  
  Rob
 
  What are your bios setting?
  My guess is that you have not made the right setting using the siftware
  and configuration utilities
  david
 
 David,
 
 Thanks. The BIOS setting appear ok - OS type is set as UNIX (Small disk
 geometry) and the machine passes all the diagnostics.
 
 Rob

 I cannot remember - but I have sneaking notion that you need to set it as
 linux

Tried that too :-). I think that the problem is that with 5.4 release #2
it is trying to access that scsi drives immediately then inducing the
kernel panic for 15s.  Rather than inducing the panic 1st.

Rob


Did you follow my suggestion and search the HP resources with freebsd and your 
model.  I have had the same problem myself I am pretty certain it was fixed 
by changes using the Proliant Essrntial Foundation Pack.. but my memory may 
not be accurate.
david
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

-- 
40 yrs navigating and computing in blue waters.
English Owner  Captain of British Registered 60' bluewater Ketch S/V Taurus.
 Currently in San Diego, CA. Sailing bound for Europe via Panama Canal after 
completing engineroom refit.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem

2005-08-30 Thread Vizion

On Tuesday 30 August 2005 16:21,  the author Vizion contributed to the 
dialogue on-
 Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem: 

On Tuesday 30 August 2005 13:31,  the author Robert Slade contributed to the
dialogue on-



Is this any use:
http://ezine.daemonnews.org/23/cpqraid.html
 
-- 
40 yrs navigating and computing in blue waters.
English Owner  Captain of British Registered 60' bluewater Ketch S/V Taurus.
 Currently in San Diego, CA. Sailing bound for Europe via Panama Canal after 
completing engineroom refit.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

boot problem (stage 2 boot?)


Just installed on a new system and I am unable to boot.

Currently when that system boots it comes up with what looks like the 
following example from the handbook


 FreeBSD/i386 BOOT
Default: 0:ad(0,a)/kernel
boot:

from my reading this is a boot2 stage

booting from cd and going into Fixit it fdisk shows partition 1, 2, and 
3 unused, and Freebsd is on partition 4.

I thought it should be on partition 1?

Note: on install I choose the Standard boot manager.

I have tried playing with fdisk and disklabel to try to cure this 
problem, but continually get the example shown above.
With none of the above efforts working I have tried changing the boot 
manager and no luck, both by reinstalling and just by using sysinstall 
to modify the boot manager.I did get F1 FreeBSD when trying the FreeBSD 
boot manager option, but it still did not start the system.



Thanks
Sean
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: boot problem (stage 2 boot?)


At 06:04 AM 8/27/2005, Sean wrote:

Just installed on a new system and I am unable to boot.

Currently when that system boots it comes up with what looks like 
the following example from the handbook


 FreeBSD/i386 BOOT
Default: 0:ad(0,a)/kernel
boot:

from my reading this is a boot2 stage

booting from cd and going into Fixit it fdisk shows partition 1, 2, 
and 3 unused, and Freebsd is on partition 4.

I thought it should be on partition 1?


How did you arrange the file systems when you installed.  Did you use 
the defaults, or your own layout?


The defaults would have given you 5 partitions inside of the first 
slice.  For example:

ad0s1a - /
ad0s1b - swap
ad0s1d - /var
ad0s1e - /tmp
ad0s1f - /usr

Did you not use the 'a' partition for your root file system?  Second 
stage boot code only knows how to find third stage on the 'a' partition.


More details on your installation would help in trying to figure out 
what the problem is.


-Glenn



Note: on install I choose the Standard boot manager.

I have tried playing with fdisk and disklabel to try to cure this 
problem, but continually get the example shown above.
With none of the above efforts working I have tried changing the 
boot manager and no luck, both by reinstalling and just by using 
sysinstall to modify the boot manager.I did get F1 FreeBSD when 
trying the FreeBSD boot manager option, but it still did not start the system.



Thanks
Sean
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: boot problem (stage 2 boot?)


Glenn Dawson wrote:

At 06:04 AM 8/27/2005, Sean wrote:


Just installed on a new system and I am unable to boot.

Currently when that system boots it comes up with what looks like the 
following example from the handbook


 FreeBSD/i386 BOOT
Default: 0:ad(0,a)/kernel
boot:

from my reading this is a boot2 stage

booting from cd and going into Fixit it fdisk shows partition 1, 2, 
and 3 unused, and Freebsd is on partition 4.

I thought it should be on partition 1?



How did you arrange the file systems when you installed.  Did you use 
the defaults, or your own layout?


The defaults would have given you 5 partitions inside of the first 
slice.  For example:

ad0s1a - /
ad0s1b - swap
ad0s1d - /var
ad0s1e - /tmp
ad0s1f - /usr

Did you not use the 'a' partition for your root file system?  Second 
stage boot code only knows how to find third stage on the 'a' partition.


More details on your installation would help in trying to figure out 
what the problem is.


-Glenn


Note: on install I choose the Standard boot manager.

I have tried playing with fdisk and disklabel to try to cure this 
problem, but continually get the example shown above.
With none of the above efforts working I have tried changing the boot 
manager and no luck, both by reinstalling and just by using sysinstall 
to modify the boot manager.I did get F1 FreeBSD when trying the 
FreeBSD boot manager option, but it still did not start the system.



Thanks
Sean


I created the above partitions you listed manually and specified to my 
choice sizes, and i did choose 'a', or entire disk on creation.


No matter how I approach this problem I always wind up in the same place.
I am guessing now that the MBR has a problem.

Thanks
Sean
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: boot problem (stage 2 boot?)


At 02:13 PM 8/27/2005, Sean wrote:

Glenn Dawson wrote:

At 06:04 AM 8/27/2005, Sean wrote:


Just installed on a new system and I am unable to boot.

Currently when that system boots it comes up with what looks like 
the following example from the handbook


 FreeBSD/i386 BOOT
Default: 0:ad(0,a)/kernel
boot:

from my reading this is a boot2 stage

booting from cd and going into Fixit it fdisk shows partition 1, 
2, and 3 unused, and Freebsd is on partition 4.

I thought it should be on partition 1?


How did you arrange the file systems when you installed.  Did you 
use the defaults, or your own layout?
The defaults would have given you 5 partitions inside of the first 
slice.  For example:

ad0s1a - /
ad0s1b - swap
ad0s1d - /var
ad0s1e - /tmp
ad0s1f - /usr
Did you not use the 'a' partition for your root file 
system?  Second stage boot code only knows how to find third stage 
on the 'a' partition.
More details on your installation would help in trying to figure 
out what the problem is.

-Glenn


Note: on install I choose the Standard boot manager.

I have tried playing with fdisk and disklabel to try to cure this 
problem, but continually get the example shown above.
With none of the above efforts working I have tried changing the 
boot manager and no luck, both by reinstalling and just by using 
sysinstall to modify the boot manager.I did get F1 FreeBSD when 
trying the FreeBSD boot manager option, but it still did not start the system.



Thanks
Sean


I created the above partitions you listed manually and specified to 
my choice sizes, and i did choose 'a', or entire disk on creation.


The entire disk option is in the screen that lest you create 
slices, which is completely different from the screen that lets you 
create your partitions. (a, b, d, e, f, etc)


Keep in mind that what is called a partition in other OS's is 
called a slice in FreeBSD.


You mentioned above that FreeBSD was installed in partition 
4.  Assuming that's slice 4, are the device names something like 
/dev/ads4x. where the x is the partition.




No matter how I approach this problem I always wind up in the same place.
I am guessing now that the MBR has a problem.


I doubt there's nothing wrong with the MBR per se, but if it's 
looking in the wrong place for the third stage loader you'll see 
exactly the problem you have.


-Glenn



Thanks
Sean
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: boot problem (stage 2 boot?)

2005-08-27 Thread Gary W. Swearingen

Sean [EMAIL PROTECTED] writes:

 Just installed on a new system and I am unable to boot.

You might get better help if you include details like what you installed.

 Currently when that system boots it comes up with what looks like the 
 following example from the handbook

   FreeBSD/i386 BOOT
 Default: 0:ad(0,a)/kernel
 boot:

Of course, standard 5.x kernel is in /boot/kernel/kernel

 booting from cd and going into Fixit it fdisk shows partition 1, 2, and 3 
 unused, and Freebsd is on partition 4.
 I thought it should be on partition 1?

I suppose you've tried
0:ad(3,a)/kernel
but maybe not:
0:ad(3,a)/boot/loader

but I doubt if either will work because it's supposed to be done
automatically.  But if you got to the boot: prompt, you shouldn't
need to worry about the boot manager (i.e., the MBR).  It looks like
the system is reading the boot records at the start of some FreeBSD
primary partition (presumably, the 4th) and it should then try to run
/boot/loader.  Some disk geometry problem?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: boot problem (stage 2 boot?)


Glenn Dawson wrote:

At 02:13 PM 8/27/2005, Sean wrote:


Glenn Dawson wrote:


At 06:04 AM 8/27/2005, Sean wrote:


Just installed on a new system and I am unable to boot.

Currently when that system boots it comes up with what looks like 
the following example from the handbook


 FreeBSD/i386 BOOT
Default: 0:ad(0,a)/kernel
boot:

from my reading this is a boot2 stage

booting from cd and going into Fixit it fdisk shows partition 1, 2, 
and 3 unused, and Freebsd is on partition 4.

I thought it should be on partition 1?



How did you arrange the file systems when you installed.  Did you use 
the defaults, or your own layout?
The defaults would have given you 5 partitions inside of the first 
slice.  For example:

ad0s1a - /
ad0s1b - swap
ad0s1d - /var
ad0s1e - /tmp
ad0s1f - /usr
Did you not use the 'a' partition for your root file system?  Second 
stage boot code only knows how to find third stage on the 'a' partition.
More details on your installation would help in trying to figure out 
what the problem is.

-Glenn


Note: on install I choose the Standard boot manager.



I created the above partitions you listed manually and specified to my 
choice sizes, and i did choose 'a', or entire disk on creation.



The entire disk option is in the screen that lest you create slices, 
which is completely different from the screen that lets you create your 
partitions. (a, b, d, e, f, etc)


Keep in mind that what is called a partition in other OS's is called a 
slice in FreeBSD.


You mentioned above that FreeBSD was installed in partition 4.  Assuming 
that's slice 4, are the device names something like /dev/ads4x. where 
the x is the partition.


Through Fitit,
fdisk shows partions 1,2,and 3 unused, and Freebsd sitting in 4.
bsdlabel shows on /dev/ad0s1 the six partitions, a, b, c, d, e, f

Sysinstall, from the boot cd, shows the following
disk name: ad0 and freebsd on ad0s1

disklabel shows
ad0s1a, ad0s1d, ad0s1b, ad0s1e, ad0s1f, none of these partitions 
currently show a mount point, with the exception of b, which is swap.

so now am even more puzzled by no mount showing.


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: boot problem (stage 2 boot?)

2005-08-27 Thread Gary W. Swearingen

Glenn Dawson [EMAIL PROTECTED] writes:

 I doubt there's nothing wrong with the MBR per se, but if it's looking in the 
 wrong place for the third stage loader
 you'll see exactly the problem you have.

Where it's probably refers to boot code, not to the MBR, which
doesn't look for anything except the confusingly-named first-stage
boot loader (same as /boot/boot1) in the first sector of your 4th
primary partition.  Then that loads the second-stage boot loader (same
as /boot/boot2) which gives the boot: prompt after failing to run
/boot/loader and failing to run a kernel.

It seems that finding boot1 and boot2 is possible with bad geometry,
but finding /boot/loader or the kernel is not.   ???
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: boot problem (stage 2 boot?)


At 02:40 PM 8/27/2005, Sean wrote:

Glenn Dawson wrote:

At 02:13 PM 8/27/2005, Sean wrote:


Glenn Dawson wrote:


At 06:04 AM 8/27/2005, Sean wrote:


Just installed on a new system and I am unable to boot.

Currently when that system boots it comes up with what looks 
like the following example from the handbook


 FreeBSD/i386 BOOT
Default: 0:ad(0,a)/kernel
boot:

from my reading this is a boot2 stage

booting from cd and going into Fixit it fdisk shows partition 1, 
2, and 3 unused, and Freebsd is on partition 4.

I thought it should be on partition 1?



How did you arrange the file systems when you installed.  Did you 
use the defaults, or your own layout?
The defaults would have given you 5 partitions inside of the 
first slice.  For example:

ad0s1a - /
ad0s1b - swap
ad0s1d - /var
ad0s1e - /tmp
ad0s1f - /usr
Did you not use the 'a' partition for your root file 
system?  Second stage boot code only knows how to find third 
stage on the 'a' partition.
More details on your installation would help in trying to figure 
out what the problem is.

-Glenn


Note: on install I choose the Standard boot manager.



I created the above partitions you listed manually and specified 
to my choice sizes, and i did choose 'a', or entire disk on creation.


The entire disk option is in the screen that lest you create 
slices, which is completely different from the screen that lets you 
create your partitions. (a, b, d, e, f, etc)
Keep in mind that what is called a partition in other OS's is 
called a slice in FreeBSD.
You mentioned above that FreeBSD was installed in partition 
4.  Assuming that's slice 4, are the device names something like 
/dev/ads4x. where the x is the partition.


Through Fitit,
fdisk shows partions 1,2,and 3 unused, and Freebsd sitting in 4.


Can you send the output that shows that?


bsdlabel shows on /dev/ad0s1 the six partitions, a, b, c, d, e, f


/dev/ad0s1 is slice one. (partition 1 in the dos/windows world)


Sysinstall, from the boot cd, shows the following
disk name: ad0 and freebsd on ad0s1


That is exactly as it should be.



disklabel shows
ad0s1a, ad0s1d, ad0s1b, ad0s1e, ad0s1f, none of these partitions 
currently show a mount point, with the exception of b, which is swap.

so now am even more puzzled by no mount showing.


disklabel output can't give you mount points.  Can you provide the 
output from disklabel?  That would help in figuring out what's going on.


Here's a sample output from one of my systems:

# /dev/ad0s1:
8 partitions:
#size   offsetfstype   [fsize bsize bps/cpg]
  a:   52428804.2BSD0 0 0
  b:  2045600   524288  swap
  c: 209647620unused0 0 # raw 
part, don't edit

  d:   524288  25698884.2BSD0 0 0
  e:   524288  30941764.2BSD0 0 0
  f: 17346298  36184644.2BSD0 0 0

-Glenn




___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: boot problem (stage 2 boot?)


At 02:47 PM 8/27/2005, Gary W. Swearingen wrote:

Glenn Dawson [EMAIL PROTECTED] writes:

 I doubt there's nothing wrong with the MBR per se, but if it's 
looking in the wrong place for the third stage loader

 you'll see exactly the problem you have.

Where it's probably refers to boot code, not to the MBR, which
doesn't look for anything except the confusingly-named first-stage
boot loader (same as /boot/boot1) in the first sector of your 4th
primary partition.  Then that loads the second-stage boot loader (same
as /boot/boot2) which gives the boot: prompt after failing to run
/boot/loader and failing to run a kernel.

It seems that finding boot1 and boot2 is possible with bad geometry,
but finding /boot/loader or the kernel is not.   ???


The restriction on where stage 2 finds the stage 3 loader, 
/boot/loader, is that it must be on the 'a' partition.  Something like:


/dev/ad0s1a

If it's somewhere else, like /dev/ad0s1e, then you'll land at the 
boot: prompt every time.


-Glenn


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: boot problem (stage 2 boot?)