Well, I wasn't able to continue troubleshooting. I took the
opportunity that the server was already down to upgrade the BIOS. HP
kindly does not provide any checks or warnings letting you know that
you need to do a stepped upgrade, so the server is bricked. *sigh*. So
this likely won't get
On 25. sep. 2013, at 06:59, Tyler Sweet ty...@tsweet.net wrote:
I tried reinstalling the boot blocks from both
the fixit live filesystem and also mounting zroot and using the files
there in case they were different.
Disclaimer: I haven't gotten (enough) morning-coffee yet, but...
Disclaimer
Luckily, in this case, I had set a cron job long, long ago to do daily
snapshots. So I have a snapshot from before the upgrade - There are
indeed two different loaders. The newer one matches zfs when
grepped, the older one does not... But, since it was working before, I
restored the older loader
Hello all,
Not sure if this is the correct list. I've run into a problem with one
of my servers where it no longer boots. It uses GPT and ZFS for root.
Recently, I did an upgrade from 8.2 up to 8.4. That went fine, and I
rebooted a few times after that to finish installing updates. During
those
This actually made for an interesting bug, once I dug into it some more:
http://www.freebsd.org/cgi/query-pr.cgi?pr=164861
If you build a zfs in degraded mode, it's not bootable. But if you build
it normally, then remove a disk to put it in degraded mode, it is bootable.
Chris
On 2/4/2012
On Wed, Feb 8, 2012 at 6:03 PM, Chris Jones ch...@cjones.org wrote:
This actually made for an interesting bug, once I dug into it some more:
http://www.freebsd.org/cgi/query-pr.cgi?pr=164861
If you build a zfs in degraded mode, it's not bootable. But if you build it
normally, then remove a
On 2/8/2012 12:42 PM, George Kontostanos wrote:
On Wed, Feb 8, 2012 at 6:03 PM, Chris Jonesch...@cjones.org wrote:
If you build a zfs in degraded mode, it's not bootable. But if you build it
normally, then remove a disk to put it in degraded mode, it is bootable.
I might be missing something
I have a raidz1 in degraded mode, with only 1 disk available. When I try
to boot it, I get this:
ZFS: can only boot from disk, mirror, raidz1, raidz2 and raidz3 vdevs
ZFS: i/o error - all block copies unavailable
ZFS: can't read MOS
ZFS: unexpected object set type 0
...followed by a couple of
___
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
Dear Sirs
After I had downloaded 8.0beta4 amd64 and recorded it on DVD on my
Linux, I dont get booting this OS from DVD. I've followed all the info
from man growisofs but it's unable to boot
# growisofs -dvd-compat -Z /dev/dvd=8.0-BETA4... what's wrong?
On Thu, Sep 17, 2009 at 05:13:26PM -0300, LuizBCampos wrote:
After I had downloaded 8.0beta4 amd64 and recorded it on DVD on my
Linux, I dont get booting this OS from DVD. I've followed all the info
from man growisofs but it's unable to boot
Can you be somewhat more specific? What is the
On Sat, Aug 08, 2009 at 11:29:13PM -0400, Karl Vogel wrote:
On Sat, 8 Aug 2009 15:38:25 +0200, Roland Smith rsm...@xs4all.nl said:
R At $WORK the Dell computers (both desktops and servers AFAIK) that we
R use are ditched at the first problem after the warranty runs out which
R is after
Looks like your hardware is dying/dead.
Sadly, I agree.
Reset BIOS CMOS data (hardware jumper on motherboard)
Enter RAID controller BIOS, (re)set your boot drive
But it looks like a fundamental BIOS control issue is malfunctioning.
Do you have a PCI Diagnostics card? One like the
I'd get to the point of swapping hardware one at a time until it
fixes, or until you exhaust your options. Have any kind of support
contract with the OEM?
I do have a support contract and I'm going to dump this right in their
lap. Two machines we bought from them -- pretty expensive ones --
On Sat, Aug 08, 2009 at 07:53:40AM -0400, Identry wrote:
Looks like your hardware is dying/dead.
Sadly, I agree.
snip
I'd get to the point of swapping hardware one at a time until it
fixes, or until you exhaust your options. Have any kind of support
contract with the OEM?
I do have
On Sat, 8 Aug 2009 15:38:25 +0200
Roland Smith rsm...@xs4all.nl wrote:
On Sat, Aug 08, 2009 at 07:53:40AM -0400, Identry wrote:
Looks like your hardware is dying/dead.
Sadly, I agree.
snip
I'd get to the point of swapping hardware one at a time until it
fixes, or until you
On Sat, Aug 08, 2009 at 10:12:16AM -0400, Jerry wrote:
On Sat, 8 Aug 2009 15:38:25 +0200
Roland Smith rsm...@xs4all.nl wrote:
On Sat, Aug 08, 2009 at 07:53:40AM -0400, Identry wrote:
Looks like your hardware is dying/dead.
Sadly, I agree.
snip
I'd get to the point of
On Sat, 8 Aug 2009 15:38:25 +0200, Roland Smith rsm...@xs4all.nl said:
R At $WORK the Dell computers (both desktops and servers AFAIK) that we
R use are ditched at the first problem after the warranty runs out which
R is after three years, I believe.
Interesting. I've used a Dell GX260 for
Identry wrote:
Try downloading and booting the livefs environment (I think you need cd1
and the livefs cd or just the DVD) and see if you can mount it from
that, if not it could be a controller issue. If you can then its
probably your OS/kernel but at least you now have access to your
I'd give it an fsck or two (more than one has been needed once or
twice),
I was afraid to run fsck before backing up everything I might possibly
need, so I spent most of last night mounting all the partitions and
backing up things.
I was able to manually mount all the partitions and all the
Are you using the GENERIC kernel
After more research, I think the answer to this is no. There is a
directory called /boot/kernel.old. From my reading, I believe this is
the original generic kernel?
if not have you tried it?
Not yet. Section 24.2.3 Major and Minor Upgrades of the Handbook
says
On Fri, Aug 7, 2009 at 5:08 PM, Identry jalmb...@identry.com wrote:
I'd give it an fsck or two (more than one has been needed once or
twice),
I was afraid to run fsck before backing up everything I might possibly
need, so I spent most of last night mounting all the partitions and
backing
On Fri, Aug 07, 2009 at 10:31:01AM -0400, Identry wrote:
Are you using the GENERIC kernel
After more research, I think the answer to this is no. There is a
directory called /boot/kernel.old. From my reading, I believe this is
the original generic kernel?
Try this:
# strings
On Fri, Aug 7, 2009 at 5:31 PM, Identry jalmb...@identry.com wrote:
Are you using the GENERIC kernel
After more research, I think the answer to this is no. There is a
directory called /boot/kernel.old. From my reading, I believe this is
the original generic kernel?
if not have you tried
Try this:
# strings /boot/kernel/kernel | grep ':/usr/obj/usr/src/sys/'
# strings /boot/kernel.old/kernel | grep ':/usr/obj/usr/src/sys/'
$ strings kernel/kernel |grep ':/usr/obj/usr/src/sys'
r...@on.identry.com:/usr/obj/usr/src/sys/INET_ON
$ strings kernel.old/kernel |grep
On Fri, Aug 07, 2009 at 10:59:13AM -0400, Identry wrote:
Try this:
# strings /boot/kernel/kernel ? ? | grep ':/usr/obj/usr/src/sys/'
# strings /boot/kernel.old/kernel | grep ':/usr/obj/usr/src/sys/'
$ strings kernel/kernel |grep ':/usr/obj/usr/src/sys'
If you did not touch the kernel, there is no need to boot GENERIC! Plus you
have said that this box is running PF, which is not in the GENERIC kernel!
Personally, I am interested in knowing why the system does not mount the
root partition on its own when you can do it by hand and it does not
On Fri, Aug 07, 2009 at 10:08:44AM -0400, Identry wrote:
if not have you tried it?
No. I need to figure out how to do that, and I didn't have enough
brain power last night after doing all those backups.
After sleeping on it, I am wondering if I can kill two birds with one
stone... by
So I guess the question now is, if I can mount it manually, why
doesn't it mount during the boot process?
I'd give it an fsck or two (more than one has been needed once or
twice)
So I've been thinking about how to run fsck...
At the moment, I have to boot from an install cd, go into fixit
On Fri, Aug 07, 2009 at 11:25:48AM -0400, Identry wrote:
So I guess the question now is, if I can mount it manually, why
doesn't it mount during the boot process?
I'd give it an fsck or two (more than one has been needed once or
twice)
So I've been thinking about how to run fsck...
Realize that if you upgrade to 7.x, you'll have to remove and reinstall
all ports because the version number of shared system libraries will
have changed.
Yes, I've decided this is way too complicated.
Or would it be safer to try to bring up the machine on it's own with a
6.2 generic
On Fri, Aug 7, 2009 at 6:25 PM, Identry jalmb...@identry.com wrote:
So I guess the question now is, if I can mount it manually, why
doesn't it mount during the boot process?
I'd give it an fsck or two (more than one has been needed once or
twice)
So I've been thinking about how to run
fsck is run when all file systems are unmounted!
If you can, choose single use mode, press enter when it says something like
/bin/sh (I don't remember the wordings) and then on the subsequent
prompt,,
# fsck -y [Press enter here]
That is all you need. Once it completes, it will bring back
Should I use any flags? Should I mount the filesystems read write or read
only?
You should never fsck a filesystem when its mounted!
Ah... glad I asked.
I think you should start by reading the manual pages for fsck and
fsck_ffs. I would start with 'fsck_ffs -fp /dev/yourdevicenode'.
On Fri, Aug 07, 2009 at 12:26:10PM -0400, Identry wrote:
Should I use any flags? Should I mount the filesystems read write or read
only?
You should never fsck a filesystem when its mounted!
Ah... glad I asked.
Actually it is only when a filesystem is mounted read-write that you must
On 8/7/09, Identry iden...@gmail.com wrote:
If you did not touch the kernel, there is no need to boot GENERIC! Plus
you
have said that this box is running PF, which is not in the GENERIC kernel!
Personally, I am interested in knowing why the system does not mount the
root partition on its own
I think you should start by reading the manual pages for fsck and
fsck_ffs. I would start with 'fsck_ffs -fp /dev/yourdevicenode'.
Okay, back in the data center. I ran fsck_ffs -fp on my root file
system and it returned with no errors. It just printed some
information about number of files,
Non-printable-character (NPC)
NPCs may be a culprit for a file that used to work, now doesn't. Or a
inode oddity.
I've been following this thread but haven't chipped in because of
timing (you driving to the datacenter).
Here's what I'd consider:
# mv /etc/fstab /etc/old-fstab
and
Okay, back in the data center. I ran fsck_ffs -fp on my root file
system and it returned with no errors. It just printed some
information about number of files, used, free space, etc., ending with
the interesting fact of .3% fragmentation.
Then I reran it without the -fp and it printed Phase
Well, something got worse. After running fsck_ffs with no errors, I
tried to boot the machine. It got to the point where it printed:
snip
Booting from BIOS Partition 0
PS2 keyboard detected
PS2 mouse detected
and it just hangs at that point.
Worse and worse... The machine won't boot from
On Fri, Aug 07, 2009 at 04:41:57PM -0400, Identry wrote:
Okay, back in the data center. I ran fsck_ffs -fp on my root file
system and it returned with no errors. It just printed some
information about number of files, used, free space, etc., ending with
the interesting fact of .3%
On Fri, Aug 07, 2009 at 11:47:58AM -0400, Identry wrote:
Realize that if you upgrade to 7.x, you'll have to remove and reinstall
all ports because the version number of shared system libraries will
have changed.
Yes, I've decided this is way too complicated.
Or would it be safer to
On 8/7/09, Roland Smith rsm...@xs4all.nl wrote:
Looks like your hardware is dying/dead.
Sadly, I agree.
Reset BIOS CMOS data (hardware jumper on motherboard)
Enter RAID controller BIOS, (re)set your boot drive
But it looks like a fundamental BIOS control issue is malfunctioning.
Do you
Tim Judd wrote:
On 8/7/09, Roland Smith rsm...@xs4all.nl wrote:
Looks like your hardware is dying/dead.
Sadly, I agree.
Reset BIOS CMOS data (hardware jumper on motherboard)
Enter RAID controller BIOS, (re)set your boot drive
But it looks like a fundamental BIOS control issue
Well, the bad day has come... My primary server won't boot. I have
backups of databases and user directories, but I need to try to get
this server back up again.
During the boot sequence, it freezes at the statement:
Trying to mount root from ufs:/dev/mfid0s1a
I tried booting into single
Identry wrote:
Well, the bad day has come... My primary server won't boot. I have
backups of databases and user directories, but I need to try to get
this server back up again.
During the boot sequence, it freezes at the statement:
Trying to mount root from ufs:/dev/mfid0s1a
I
Try downloading and booting the livefs environment (I think you need cd1
and the livefs cd or just the DVD) and see if you can mount it from
that, if not it could be a controller issue. If you can then its
probably your OS/kernel but at least you now have access to your
data/configs etc etc
Identry wrote:
During the boot sequence, it freezes at the statement:
Trying to mount root from ufs:/dev/mfid0s1a
Try downloading and booting the livefs environment (I think you need cd1
and the livefs cd or just the DVD) and see if you can mount it from
that, if not it could be a
On Thu, Aug 06, 2009 at 05:31:49PM -0400, Identry wrote:
Try downloading and booting the livefs environment (I think you need cd1
and the livefs cd or just the DVD) and see if you can mount it from
that, if not it could be a controller issue. If you can then its
probably your OS/kernel but
Identry wrote:
Try downloading and booting the livefs environment (I think you need cd1
and the livefs cd or just the DVD) and see if you can mount it from
that, if not it could be a controller issue. If you can then its
probably your OS/kernel but at least you now have access to your
On Thu, 6 Aug 2009 18:31:12 -0400, Identry jalmb...@identry.com wrote:
I've booted the install CD1 and found something called 'fixit' mode.
I've been googling, but can't seem to find any info on 'fixit'. Is it
possible to use this instead of a livefs disk?
As far as I remember, that's correct.
Try downloading and booting the livefs environment (I think you need cd1
and the livefs cd or just the DVD) and see if you can mount it from
that, if not it could be a controller issue. If you can then its
probably your OS/kernel but at least you now have access to your
data/configs etc etc
Hello,
When I boot a Dell Optiplex 320 running FreeBSD 7.0 the boot sequence
hangs at USB3: OHCI version 1.0, legacy support if a keyboard is plugged
in. It will boot successfully if the keyboard is not plugged in until
after the boot sequence is completed.
Normally this would not be that
Greetings,
I just re-installed an old file server from stable 6.1 to 7.1 stable,
and I'm having a problem with my 3ware 7000-2 card.
After sysinstall completes, and I try to boot from the SCSI HDD (not
connected to the 3ware) for the first time, the system hangs immediatly after
John H. Nyhuis wrote:
Greetings,
I just re-installed an old file server from stable 6.1 to 7.1 stable,
and I'm having a problem with my 3ware 7000-2 card.
After sysinstall completes, and I try to boot from the SCSI HDD (not
connected to the 3ware) for the first time, the system hangs
Chris Pratt wrote:
On Nov 20, 2008, at 4:31 PM, Vinny wrote:
Hi,
A friend of mine is trying out FreeBSD and ran into
a booting problem. Here is his message:
Well, that's discouraging.
I have put together an old PII 400 with three 20GB drives and a CDROM
that I'd like to run BSD on.
Hi,
A friend of mine is trying out FreeBSD and ran into
a booting problem. Here is his message:
Well, that's discouraging.
I have put together an old PII 400 with three 20GB drives and a CDROM
that I'd like to run BSD on. Half a GB of RAM I figured would be
respectable.
Downloaded the
On Nov 20, 2008, at 4:31 PM, Vinny wrote:
Hi,
A friend of mine is trying out FreeBSD and ran into
a booting problem. Here is his message:
Well, that's discouraging.
I have put together an old PII 400 with three 20GB drives and a
CDROM that I'd like to run BSD on. Half a GB of RAM I
Vinny wrote:
Hi,
A friend of mine is trying out FreeBSD and ran into
a booting problem. Here is his message:
Well, that's discouraging.
I have put together an old PII 400 with three 20GB drives and a CDROM
that I'd like to run BSD on. Half a GB of RAM I figured would be
respectable.
that the kernel sees during the boot failure
all I see is an ad14 device(Which doesn't exist) and acd0.
When I select the old kernel it boots without a problem. My boot device
is ad10s1 which the November 1st kernel finds without a problem.
I'm running a generic SMP kernel.
Any ideas on what the problem
I am running FreeBSD 6.3-PRERELEASE with my last successful kernel build
of 11/1/07. I successfully have built two kernels, one a couple of weeks
ago and one just today but when I attempt to boot them the kernel isn't
able to identify my boot partition. I query the devices that the kernel
sees are
Will someone please explain in detail how to run the FreeBSD fdisk util
outside of the freebsd installer? Please provide detailed steps.
You just type fdisk devname where devname is the disk device.
There are a number of flags and parameters you may need to use.
Have you read the fdisk
, and setting da0 as bootable, and installing the FreeBSD
boot manager on da0. OK?
I also found an IDE HDD yesterday, and installed Linux on ad0 (the IDE HDD),
but am getting the exact same boot failure.
I tried setting my bios to try booting from IDE drives first (before SCSI), and
vice-versa (SCSI
On Tue, Apr 10, 2007 at 07:48:07PM -0700, L Goodwin wrote:
Is there a way to run the FDISK tool outside of the freebds installer?
How do I change the disk configuration without reinstalling freebsd
every @[EMAIL PROTECTED] time?
Yes, all sysinstall does is collect the information and run
Will someone please explain in detail how to run the FreeBSD fdisk util outside
of the freebsd installer? Please provide detailed steps.
What would the experts do next in this situation? I've checked and
double-checked BIOS (current version is same as what I have -- 1013, so did not
re-flash),
ACPI.
RESULT: FAIL - Still getting DISK BOOT FAILURE, INSERT SYSTEM DISK AND
PRESS ENTER
4) Ran Verify Disk Media on SCSI ID #0: Disk Verification Complete
What else could it possibly be? Are there any other diagnostics I can run?
What do you think of the fact that this machine was booting Windows
it looks as if you've an IDE Interface onboard, too. Is it possible
that there are two ATA disks installed? Because the SCSI BIOS is only
installed when there are less then two ATA *disks* installed. Having
one Disk and one CD ROM should be fine, though.
Either try removing the ATA disks, or
Is there a way to run the FDISK tool outside of the freebds installer? How do
I change the disk configuration without reinstalling freebsd every @[EMAIL
PROTECTED] time?
I really want to set up a FreeBSD server and appreciate the learning
experience, but it's way past the point where I should
always fails with DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS
ENTER.
In order to boot the install CD on this machine, I have to disable ACPI by
selecting
2. Boot FreeBSD with ACPI disabled from the boot loader menu (the AWARD BIOS
does not allow
for disabling ACPI from the BIOS setup program
a
successful install,
(re-)boot always fails with DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS
ENTER.
In order to boot the install CD on this machine, I have to disable ACPI by
selecting
2. Boot FreeBSD with ACPI disabled from the boot loader menu (the AWARD
BIOS does not allow
for disabling
. After a
successful install,
(re-)boot always fails with DISK BOOT FAILURE, INSERT SYSTEM DISK AND
PRESS ENTER.
In order to boot the install CD on this machine, I have to disable ACPI by
selecting
2. Boot FreeBSD with ACPI disabled from the boot loader menu (the AWARD
BIOS does not allow
ID #15:No device
Derek Ragona [EMAIL PROTECTED] wrote: At 12:56 AM 4/9/2007, L Goodwin wrote:
I'm having trouble getting FreeBSD 6.2 to boot after installation. After a
successful install,
(re-)boot always fails with DISK BOOT
BOOT FAILURE, INSERT SYSTEM DISK AND PRESS
ENTER
4) Ran Verify Disk Media on SCSI ID #0: Disk Verification Complete
What else could it possibly be? Are there any other diagnostics I can run?
What do you think of the fact that this machine was booting Windows 2000 from
the same
SCSI drive prior
Looking over the installation FAQ, the only reference I see to a crash has to
do with turning off ACPI in the BIOS. I have already done that, and have
successfully installed Net and Open on an HP xw4300 workstation (64-bit Intel
Pentium D).
The amd64 bootonly 6.1RELEASE CD (burned from your
Erik Nørgaard wrote:
/home -alldirs -network 192.168.0.0 -mask 255.255.255.0
/var/diskless/FreeBSD -ro -mapall=root:wheel -network 192.168.0.0
-mask 255.255.255.0
/var/diskless/192.168.0.16/var 192.168.0.16
42cm error: -mapall should be -maproot
Erik
--
Ph: +34.666334818
Hi,
I have just tried to setup 6.0BETA5 for diskless clients - just for the
sport :-) I have installed the full system into /var/diskless/FreeBSD.
Everything actually went fine, I could boot up, got root mounted and the
home dir.
So, next step was to install X.Org: chroot into
Hi,
I'm running FreeBSD on a CompaQ PL5000. I installed 5.3 which worked ok,
I then CVSup'd to using RELENG_5 tag. After buildworld and build kernel
the system fails to reboot. As far as I can tell, it is trying to load
GEOM which fails to find any drives. I end up at a prompt - mountroot
using
Hello,
I'm trying to get pxeboot running without any success so far.
I get 'BTX halted' after a register dump showing an int 6.
I read almost anything, I could find about that problem.
I tried with/without LOADER_TFTP_SUPPORT, I uncommented
those delay() lines in pxe.c and enlarged the delays.
I
Danny Horne [EMAIL PROTECTED] writes:
I'm trying to replace the motherboard in my FreeBSD 4.11-RELEASE
server for a different one. The old board has on-board Adaptec
AIC-7896N SCSI, the new one has on-board Symbios Ultra3 SCSI, on
bootup I get the following error -
Mounting root from
Hi all,
I'm trying to replace the motherboard in my FreeBSD 4.11-RELEASE
server for a different one. The old board has on-board Adaptec
AIC-7896N SCSI, the new one has on-board Symbios Ultra3 SCSI, on
bootup I get the following error -
Mounting root from ufs:/dev/da0s0a
setrootbyname failed
If it does not continue from there (did you press return?) something
went wrong during the installation process because apparently the kernel
is not where the bootloader expects it. Try to do the install again and
make sure the bootloader is installed on the right place. The handbooks
install
Hai every body
Recently i have installed FreeBSD5.3
the installation process is quiet nice
when the system reboots
it prompts with the message as follows
FreeBSD ..
Default : 0(1,a)/kernel
boot:
Hi,
Could it be that you forgot to remove the mfsroot floppy from the
diskdrive when you rebooted?
Regards,
Alex.
ramuK hsiraH wrote:
Hai every body
Recently i have installed FreeBSD5.3
the installation process is quiet nice
when the system reboots
it prompts
I have a system here that occasionally hangs while the kernel is booting. It
happens as the CD-ROM drive is being initialized. Here's the error:
acd0: WARNING - MODE_SENSE_BIG interrupt was seen but taskqueue stalled
This doesn't happen every time - usually if I restart the system following the
to: [EMAIL PROTECTED]
Subject:Re: 4.9, 5.1 boot failure after install
From: Lowell Gilbert [EMAIL PROTECTED]
Date sent: 27 Dec 2003 10:11:21 -0500
[EMAIL PROTECTED] writes:
Hello,
I had 4.9 release working and did a clean install of 5.1
On Sat, 27 Dec 2003 02:53 am, [EMAIL PROTECTED] wrote:
Hello,
I had 4.9 release working and did a clean install of 5.1 release over
the 4.9 and ended up with boot failure after install. Using allBSD
partition and standard MBR I get a missing operating system error. If I
use the FreeBSD boot
[EMAIL PROTECTED] writes:
Hello,
I had 4.9 release working and did a clean install of 5.1 release over
the 4.9 and ended up with boot failure after install. Using allBSD
partition and standard MBR I get a missing operating system error. If I
use the FreeBSD boot I just get default F1
successfully then reinstalled FreeBSD and the
geometry was changed in fdisk. Is there a geometry issue?
thanks,
Dan
To: [EMAIL PROTECTED]
Copies to: [EMAIL PROTECTED]
Send reply to: [EMAIL PROTECTED]
Subject:Re: 4.9, 5.1 boot failure
Hello,
I had 4.9 release working and did a clean install of 5.1 release over
the 4.9 and ended up with boot failure after install. Using allBSD
partition and standard MBR I get a missing operating system error. If I
use the FreeBSD boot I just get default F1 and a beep. Now trying to
install
I would welcome any suggestions on a boot problem with an SMP kernel for
FreeBSD 4.8 (RELENG_4_8 obtained May 21). GENERIC (uniprocessor) kernel
works fine and FreeBSD uniprocessor has worked fine on this machine for
a couple years. (Opensound now supports SMP, so I'm finally trying the
SMP
No, I just meant that I copied MAKEDEV from /usr/src into /dev, and
then ran ./MAKEDEV std from /dev, as per the UPDATING instructions.
hmm, does UPDATING say you should do that? all I know is
mergemaster
asks whether I want to have /dev/* rebuilt, and I let it do so.
, no problems.
Rebooted.. and problems. Upon boot, it tries to load up the root partition
off of /dev/ad4s1a (which is correct), but brings up a Mount boot failure:
16 error, and asks for a good ufs root location. Typing in
ufs:/dev/ad4s1a does no good.
IDE controller = Highpoint
please at least keep the mailing list among recipients: see my
signature.
# [EMAIL PROTECTED] / 2003-01-21 08:36:33 -0800:
Or maybe, are you really sure you have the proper devices in /dev?
No, I'm not. At this point I'm not sure of anything, seems like. All I've
done in /dev
# [EMAIL PROTECTED] / 2003-01-21 08:36:33 -0800:
Or maybe, are you really sure you have the proper devices in /dev?
No, I'm not. At this point I'm not sure of anything, seems like. All
I've
done in /dev is a MAKEDEV std with the MAKEDEV directly from /usr/src,
without removing the
did you let mergemaster run MAKEDEV for you, or did you run
/dev/MAKEDEV std
while being in /usr/src? If the latter, you didn't rebuild the
devices in /dev/, you created them in /usr/src instead! That would
indeed explain your problems.
No, I just meant that I copied MAKEDEV
# [EMAIL PROTECTED] / 2003-01-21 09:42:23 -0800:
# [EMAIL PROTECTED] / 2003-01-21 08:36:33 -0800:
Or maybe, are you really sure you have the proper devices in /dev?
No, I'm not. At this point I'm not sure of anything, seems like. All
I've
done in /dev is a MAKEDEV std with the
From: Roman Neuhauser [EMAIL PROTECTED]
did you let mergemaster run MAKEDEV for you, or did you run
/dev/MAKEDEV std
while being in /usr/src? If the latter, you didn't rebuild the
devices in /dev/, you created them in /usr/src instead! That would
indeed explain
, no problems.
Rebuilt kernel and installed the new 4.7 GENERIC kernel, no problems.
Ran mergemaster, did a MAKEDEV, no problems.
Rebooted.. and problems. Upon boot, it tries to load up the root partition
off of /dev/ad4s1a (which is correct), but brings up a Mount boot failure:
16 error
98 matches
Mail list logo
