On Fri, 23 Nov 2012, free...@johnea.net wrote:
One of the complications was getting old metadata off of the drive. After
trying a couple of 'dd' invocations:
# overwriting the first sector
dd if=/dev/zero of=/dev/ada0 bs=512 count=1
# also tried overwriting the last sector
diskinfo ada0 | cut -
On 2012-11-20 21:10, Warren Block wrote:
> On Tue, 20 Nov 2012, free...@johnea.net wrote:
>
>> On 2012-11-20 14:28, Gary Aitken wrote:
>>> On 11/20/12 13:34, free...@johnea.net wrote:
>>
freebsd-update upgrade -r 9.1-RC3
>> ...
"Not UFS" "No ada0" "No boot"
>>
>>>
>>> Seems like it isn'
On Wed, 21 Nov 2012, Arthur Chance wrote:
On 11/21/12 05:11, Warren Block wrote:
gptboot looks for the first UFS partition. Maybe /boot/boot can be
modified to do that also.
It's a little more complicated than that Warren.
AIUI gptboot first looks (in partition order) for partitions with bo
On 11/21/12 05:11, Warren Block wrote:
gptboot looks for the first UFS partition. Maybe /boot/boot can be
modified to do that also.
It's a little more complicated than that Warren.
AIUI gptboot first looks (in partition order) for partitions with both
the bootme and bootonce attributes set.
On Tue, 20 Nov 2012, free...@johnea.net wrote:
On 2012-11-20 14:28, Gary Aitken wrote:
On 11/20/12 13:34, free...@johnea.net wrote:
freebsd-update upgrade -r 9.1-RC3
...
"Not UFS" "No ada0" "No boot"
Seems like it isn't supposed to work for 9.1-RC2
I previously used binary update t
On 2012-11-20 14:28, Gary Aitken wrote:
> On 11/20/12 13:34, free...@johnea.net wrote:
>> freebsd-update upgrade -r 9.1-RC3
...
>> "Not UFS" "No ada0" "No boot"
>
> Seems like it isn't supposed to work for 9.1-RC2
>
I previously used binary update to migrate from 9.0 to 9.1, via:
freebsd-upd
On 11/20/12 13:34, free...@johnea.net wrote:
>
> Hello,
>
> I recently installed a 9.1-RC2 system using gmirror with MBR, and swap in
> first bsdlabel.
>
> orsbackup# gpart show
> =>63 3907029104 mirror/gm0 MBR (1.8T)
>63 63 - free - (31k)
>
Hello,
I recently installed a 9.1-RC2 system using gmirror with MBR, and swap in first
bsdlabel.
orsbackup# gpart show
=>63 3907029104 mirror/gm0 MBR (1.8T)
63 63 - free - (31k)
126 3907028979 1 freebsd [active] (1.8T)
390702
Hi all
I have some problems in the second phase of running a
device from a nanobsd image.
After copying the image on a flash memory, and after I set
the system to boot up from flash memory, I just see a black screen and a
blinking cursor ! looks like the boot device ( flash memory ) is not recogni
On 11/05/2011 14:52, 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
On 6 November 2011 02:51, Robert Simmons wrote:
> On Sat, Nov 5, 2011 at 7:43 PM, Warren Block 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 default
Matthew Seaman writes:
> On 05/11/2011 22:19, Robert Simmons wrote:
>> On Sat, Nov 5, 2011 at 6:03 PM, Alexander Best wrote:
>>> same here. simply add something like the following to your crontab:
>>>
>>> 0 10 * * */2 /etc/rc.d/ntpdate onestart
>>
>> I have something
On Sat, Nov 5, 2011 at 7:43 PM, Warren Block 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 combinatio
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
On Sat, 5 Nov 2011, Robert Simmons wrote:
On Sat, Nov 5, 2011 at 6:55 PM, Warren Block 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-ST
On Sat, Nov 5, 2011 at 6:33 PM, Matthew Seaman
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
> pro
On Sat, Nov 5, 2011 at 6:55 PM, Warren Block 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
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
On 05/11/2011 22:19, Robert Simmons wrote:
> On Sat, Nov 5, 2011 at 6:03 PM, Alexander Best 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 no
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
On Sat, Nov 5, 2011 at 6:03 PM, Alexander Best 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
On Sat, Nov 5, 2011 at 5:57 PM, Michael Sierchio 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
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
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 wrote:
> Is there a way to make sure that the interface is UP and working
> before running ntpdat
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
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
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 P
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
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 ser
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
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.
> >
>
>
>
> >What can I do to boot my GENERIC kernel so I can rebuild from it and m
Alain G. Fabry wrote:
First 'unload kernel' followed by 'boot /boot/kernel.GENERIC/kernel', but it
mentions
that it cannot find the kernel.
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' wi
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
--
Phil
Hello,
After making some changes to my kernel and rebuilding (traditional way), my
system does not
boot anymore. I tried to boot from the GENERIC kernel following the
instructions in the
handbook.
First 'unload kernel' followed by 'boot /boot/kernel.GENERIC/kernel', but it
mentions
that it ca
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 s
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
>>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.o
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 ins
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 main
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
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/100Bas
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: on dc0
dc0: Ethernet address: 00:a0:cc:40:3e:9b
dc0: if_start running deferred for Giant
dc0: [GIANT-LOCKE
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-0x14f
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/fr
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 /et
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--salvagi
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 W
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
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 c
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 s
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/ke
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/ke
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 othe
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]"
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, f
# 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 PROTECTE
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.66633481
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
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 r
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
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/pr
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 (a
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.
style='FONT-SIZE:11px;FONT-FAMILY:ta
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 f
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.
style='FONT-SIZE:11px;FONT-FAMILY:tahoma,sans-serif'>size=1>
From:
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 othe
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 fi
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 FreesB
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 raw
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 Fi
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
__
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
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 f
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
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 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 200
>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 us
>-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 f
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.daemonnew
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 dialogu
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 200
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 so
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 t
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 havi
Hi guys,
Just wanted to say thanks for all the helpful suggestions.
Played with things and got into the geometry idea as the possible cause.
Did some more work, adjusting bios and geometry settings around the disk
and just a few minutes ago after yet another go at installing the laptop
just boo
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 cod
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
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 anythin
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
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
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
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
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
boo
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
On 7/28/05, asd asd <[EMAIL PROTECTED]> wrote:
> Hello!
> I have problem with booting FreeBSD 5.4 on my laptop Toshiba Satellite
> 2410-304:
> sometimes it boots without problem but sometimes it stops at line "uhci0:
> 82801CA/CAM (ICH3) USB controller USB-A> port 0xefe0-0xefff irq 11 at device
Hello!
I have problem with booting FreeBSD 5.4 on my laptop Toshiba Satellite 2410-304:
sometimes it boots without problem but sometimes it stops at line "uhci0: port 0xefe0-0xefff irq 11 at device
29.0 on pci0". Previous line is initialization of the Nvidia Grforce4 420Go
graphic adapter.
Any ide
Sorry.My linux kernel does support ufs.Anyway for working with ufs on
linux see
http://ufs-linux.sourceforge.net/
Sorry for the trouble.
On Sat, 07 May 2005 18:14:50 +0530, "Koushik Narayanan"
<[EMAIL PROTECTED]> said:
> Thanks for helping.I couldn't do anything with the fixit disk.Is there
> some
Thanks for helping.I couldn't do anything with the fixit disk.Is there
some method or tool using which I can copy all files in the ufs partiton
to some other partition using DOS,Windows,or Linux(my kernel won't
support ufs.) .Something like ltools which allows me to copy,delete
files in ext2 partit
Am Freitag, 6. Mai 2005 03:59 schrieb Koushik Narayanan:
> Hello,
> I have a PC with Windows XP,FreeBSD-5.3 and Linux(Fedora).I use GRUB as
> my boot manager and I boot into FreeBSD using chainloader.
> I have XP and FreeBSD on primary partitions.I had a linux primary
> partion apart from these.I w
Hello,
I have a PC with Windows XP,FreeBSD-5.3 and Linux(Fedora).I use GRUB as
my boot manager and I boot into FreeBSD using chainloader.
I have XP and FreeBSD on primary partitions.I had a linux primary
partion apart from these.I wanted to convert that to UFS2 as my /usr
partition (FreeBSD) was al
1 - 100 of 140 matches
Mail list logo
