Re: Boot hangs in single-user mode

[Andrew Hamilton-Wright]

I have tracked down the issue.  Not sure whether this is a PR issue or not...

On 2013-06-06, at 11:18 AM, Polytropon wrote:

> On Thu, 6 Jun 2013 10:24:52 -0300, Andrew Hamilton-Wright wrote:
>> 
>> Strangely, it seems that I cannot boot single user, either
>> using "boot -s" from the boot loader, or using the boot menu. 
>> When I get to the point where the root filesystem is mounted,
>> it hangs right after printing the message:
>> Trying to mount root from ufs:/dev/ada0s1a
> 
> Have you tried hitting the RETURN key several times? 

   [ ... ]

> It's important to identify if the system is _really_ hanging,
> or if the message "just isn't visible"...

This is indeed the crux of the issue.  While hammering on the RETURN key did 
not produce a prompt, it turns out that there was a prompt...

At some time in the relatively distant past, I had configured this machine to 
allow display to a serial console (long since disconnected) by adding these 
lines to /boot/loader.conf 

boot_multicons="YES"
boot_serial="YES"
comconsole_speed="19200"
console="comconsole,vidconsole"

My notes say "These came from the serial console setup page, and do work for 
vt100", however I did not note exactly which man page they came from, 
unfortunately.  I do not see these lines on syscons(4), sio(4) or dcons(4).

Similar lines are mentioned in the handbook regarding setting up a serial 
console (there is no mention of single-user mode here):
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/serialconsole-setup.html



The issue, as it relates to single-user mode, is essentially this:  if the 
system is configured to boot with multi-console options, then when the single 
user prompt is printed, it is only printed on the "second" console (which is 
also the only valid source of keyboard input) -- in this case, the configured 
but unattached serial port.


I'm not sure what the best strategy is here.  Having only one console that is 
accepting input for the single-user shell certainly makes sense.  The question 
is, which of potentially several consoles should it be?

IMO, it would be better/clearer if (for i386/amd64 anyway) the console was the 
one associated with the motherboard-based keyboard and video card.  An argument 
here would be that the [CTRL]-[ALT]-[DEL] sequence is still valid when 
associated with this keyboard, so it does seem odd that other input on that 
device is ignored.

I can see arguments for other setups, also, mostly revolving around the "why 
would you _have_ another console configured if you didn't need it, so the 
configured console must therefore be the important one" -- though the FreeBSD 
user base is certainly willing enough to experiment that I am sure I am not the 
only person who set up multi-console for a "fun" project.

Perhaps the best strategy would be to add a message printed on all consoles (as 
the rest of the boot information is) just before the prompt is printed (singly) 
to let people know that this is happening?  I'm not sure if a way to 100% 
predict the desired console is possible.


Thoughts?  If figure I will put a PR in, so that at least this is tracked, even 
if we don't change anything.  I will reference this thread in the PR, but if 
anyone has input as to what to suggest, I would appreciate it.  At the very 
least, the handbook should get updated to indicate that this may happen.

Andrew.


___
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 Loader Issue

[Warren Block]

On Sun, 23 Jun 2013, Doug Hardie wrote:



On 23 June 2013, at 20:39, Warren Block  wrote:


On Sun, 23 Jun 2013, Doug Hardie wrote:


I had to convert a system from GPT to MBR.  All went fine till I tried to 
reboot the system.  It gets to mountroot and dies trying to mount from 
ufs:/dev/ada0p2.  That won't work.


The loader should be getting that information from /etc/fstab.  Have the 
entries there been changed?


That was the problem.  The system used GPT before and I can't believe I forgot 
to update fstab.  That was a really dumb mistake.


Not really, the only reason it occurred to me was because I've forgotten 
to do it many, many times.


As Polytropon points out, labels can help avoid the problem.  In this 
case, it would have had to be a UFS label on the filesystem:


http://www.wonkity.com/~wblock/docs/html/labels.html
___
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 Loader Issue

[Polytropon]

On Sun, 23 Jun 2013 21:35:20 -0700, Doug Hardie wrote:
> 
> On 23 June 2013, at 20:39, Warren Block  wrote:
> > The loader should be getting that information from /etc/fstab.  Have the 
> > entries there been changed?
> 
> That was the problem.  The system used GPT before and I can't
> believe I forgot to update fstab.  That was a really dumb
> mistake.  Thanks very much.

If you can use labels instead of device names, this problem
can be avoided. :-)





-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
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 Loader Issue

[Doug Hardie]

On 23 June 2013, at 20:39, Warren Block  wrote:

> On Sun, 23 Jun 2013, Doug Hardie wrote:
> 
>> I had to convert a system from GPT to MBR.  All went fine till I tried to 
>> reboot the system.  It gets to mountroot and dies trying to mount from 
>> ufs:/dev/ada0p2.  That won't work.
> 
> The loader should be getting that information from /etc/fstab.  Have the 
> entries there been changed?

That was the problem.  The system used GPT before and I can't believe I forgot 
to update fstab.  That was a really dumb mistake.  Thanks very much.

> 
>> If I enter ufs:/dev/ada0s1a then the system boots fine and runs.  I need to 
>> alter mountroot so it tries the right partition/slice.  How do I do that?  I 
>> couldn't find anything in the handbook on that.
> 
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/boot-blocks.html 
> has some information.
> 

___
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 Loader Issue

[Warren Block]

On Sun, 23 Jun 2013, Michael Sierchio wrote:


On Sun, Jun 23, 2013 at 4:12 PM, Polytropon  wrote:

On Sun, 23 Jun 2013 15:47:53 -0700, Doug Hardie wrote:

I need to alter mountroot so it tries the right partition/slice.
How do I do that?  I couldn't find anything in the handbook on that.


You need to install the GPT boot code, e. g.

# gpart add -t freebsd-boot -l gpboot -b 40 -s 512K ad0


Why the offset?  Why 512k?


Block 40 is the first 4K-aligned block after the 32 blocks occupied by 
the GPT.  It won't hurt anything if the drive is not a 4K "Advanced 
Format" drive, won't really make a big difference if it is since 
bootcode is not really disk I/O-limited.  Just good practice to keep 
everything aligned.


512K is the largest size of bootcode that will work.  The loader loads 
the whole partition regardless of how large the bootcode is, and will 
fail with larger sizes.  It's no loss of space because the first UFS 
partition will start at 1M.  Why 1M?  Because it's an unofficial 
standard, and aligned with 4K, 8K, 128K, and so on.


This article talks about it a bit more:
http://www.wonkity.com/~wblock/docs/html/ssd.html


# gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 ad0


I think it's simpler to make an entry in /boot/loader.conf:

vfs.root.mountfrom="ufs:/dev/ada0s1a"


These are different things.  The command is for a GPT disk, and the boot 
device being set is for MBR.

___
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 Loader Issue

[Warren Block]

On Mon, 24 Jun 2013, Polytropon wrote:


On Sun, 23 Jun 2013 15:47:53 -0700, Doug Hardie wrote:

I need to alter mountroot so it tries the right partition/slice.
How do I do that?  I couldn't find anything in the handbook on that.


You need to install the GPT boot code, e. g.

# gpart add -t freebsd-boot -l gpboot -b 40 -s 512K ad0
# gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 ad0

See http://www.wonkity.com/~wblock/docs/html/disksetup.html for
details.


That is GPT bootcode, but he was switching to MBR.  That is documented 
in the second half of the link.

___
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 Loader Issue

[Warren Block]

On Sun, 23 Jun 2013, Doug Hardie wrote:

I had to convert a system from GPT to MBR.  All went fine till I tried 
to reboot the system.  It gets to mountroot and dies trying to mount 
from ufs:/dev/ada0p2.  That won't work.


The loader should be getting that information from /etc/fstab.  Have the 
entries there been changed?


If I enter ufs:/dev/ada0s1a then the system boots fine and runs.  I 
need to alter mountroot so it tries the right partition/slice.  How do 
I do that?  I couldn't find anything in the handbook on that.


http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/boot-blocks.html 
has some information.

___
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 Loader Issue

[Michael Sierchio]

On Sun, Jun 23, 2013 at 4:12 PM, Polytropon  wrote:
> On Sun, 23 Jun 2013 15:47:53 -0700, Doug Hardie wrote:
>> I need to alter mountroot so it tries the right partition/slice.
>> How do I do that?  I couldn't find anything in the handbook on that.
>
> You need to install the GPT boot code, e. g.
>
> # gpart add -t freebsd-boot -l gpboot -b 40 -s 512K ad0

Why the offset?  Why 512k?

> # gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 ad0

I think it's simpler to make an entry in /boot/loader.conf:

vfs.root.mountfrom="ufs:/dev/ada0s1a"
___
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 Loader Issue

[Polytropon]

On Sun, 23 Jun 2013 15:47:53 -0700, Doug Hardie wrote:
> I need to alter mountroot so it tries the right partition/slice. 
> How do I do that?  I couldn't find anything in the handbook on that.

You need to install the GPT boot code, e. g.

# gpart add -t freebsd-boot -l gpboot -b 40 -s 512K ad0
# gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 ad0

See http://www.wonkity.com/~wblock/docs/html/disksetup.html for
details.

-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
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 hangs in single-user mode

[Andrew Hamilton-Wright]

Hi Everyone,

On Thu, 6 Jun 2013 10:24:52 -0300, Andrew Hamilton-Wright wrote:
> 
> Strangely, it seems that I cannot boot single user, either
> using "boot -s" from the boot loader, or using the boot menu. 
> When I get to the point where the root filesystem is mounted,
> it hangs right after printing the message:
> Trying to mount root from ufs:/dev/ada0s1a


There was a bit of a delay getting back to this, as I needed to move the 
internals over to a replacement server in a planned upgrade.

I have left the boot disk in the machine demonstrating this problem with the 
intention of coming back to determine what is going on (mount points to 
now-missing data disks have been removed from /etc/fstab).

In the resulting stripped down system, I have the same behaviour as before -- I 
cannot get to single-user mode, but multi-user is fine.

If in multi-user mode, if I issue "kill -TERM 1" to go to single-user mode, I 
would get a single console message:  "pflog0:  promiscuous mode disabled", then 
nothing.  While I would expect pflog to shut down in this case, I have now 
disabled everything pf related (I cannot imagine that it would interfere with 
console operation), and now have the situation where kill -TERM 1 simply locks 
the console.

Plugging in a USB device while the console is locked does produce the expected 
dmesg updates, and the system does respond to [CTRL]-[ALT]-[DEL]


I will also add that I can boot to a single-user prompt when booting off of the 
9.1 media via DVD and mounting the root filesystem from the disk.  (This 
motherboard+kernel have never gotten along particularly well with the DVD 
reader/writer in the machine, so mounting the filesystem from the DVD usually 
fails with various atapi based timeouts).

Does anyone have any thoughts on how to further explore this?  As the situation 
was more than mildly annoying, and could certainly have been worse, if this is 
likely to occur for anyone else, I would like to file a PR.

Thanks,
Andrew.

___
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 hangs in single-user mode

[Andrew Hamilton-Wright]

[ Condensation of earlier comments below ]

On 2013-06-06, at 11:18 AM, Polytropon wrote:

> On Thu, 6 Jun 2013 10:24:52 -0300, Andrew Hamilton-Wright wrote:
>> 
>> When I get to the point where the root filesystem is mounted,
>> it hangs right after printing the message:
>> Trying to mount root from ufs:/dev/ada0s1a
> 
> Have you tried hitting the RETURN key several times?
...
> It's important to identify if the system is _really_ hanging,
> or if the message "just isn't visible"...

I did try that -- I have seen that behaviour before too.  I tried hitting return
a half-dozen times, and have additionally tried waiting (up to 20 min) to
see if it would come back, to no avail.


>> Interestingly, there seems to be a bit of a sequence issue,
>> as I have also seen the mount message appear before the audio
>> system comes up, so occasionally, the last item printed is:
>> pcm0:   on uaudio0
> 
> This seems to indicate that the system is still responding,
> i. e., the kernel is "up and running". Whenever "new" hardware
> is detected, the kernel will issue a console message.

That is a good point -- I will try plugging in an external USB device
at this point, and see what happens then.  It certainly appears that
the system is generally running to me, as well.  I should also mention
that the system does respond nicely to [CTRL]-[ALT]-[DEL], which
triggers the expected reboot process.


>> I am rebooting the machine at the moment as I wish to ensure
>> that I know which physical disk is ada2, so want to boot the
>> machine without it plugged in.
> 
> A suggestion: I tend to keep a tendency to use labels instead
> of device names to identify disks. This is handy in case you're

This is an excellent idea.  I do follow some variant of this (however
work at a high enough level of paranoia that I want to be able to
perform the "did the right drive disappear when I unplugged it"
check just to ensure that I wasn't asleep when making up the labels.
;-)


Thanks for the suggestions -- I will keep looking at it, and will try
adding a USB device once this restore eventually completes.

Thanks,
Andrew.

___
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 hangs in single-user mode

[Polytropon]

On Thu, 6 Jun 2013 10:24:52 -0300, Andrew Hamilton-Wright wrote:
> 
> Strangely, it seems that I cannot boot single user, either
> using "boot -s" from the boot loader, or using the boot menu. 
> When I get to the point where the root filesystem is mounted,
> it hangs right after printing the message:
> Trying to mount root from ufs:/dev/ada0s1a

Have you tried hitting the RETURN key several times? I've
seen what you've described once (I think on a FreeBSD 5
system): The prompt

Enter full pathname of shell or RETURN for /bin/sh: _

would not appear, but the system was still responding.
Hitting RETURN made that prompt visible and the SUM shell
prompt was properly displayed.

It's important to identify if the system is _really_ hanging,
or if the message "just isn't visible"...



> Interestingly, there seems to be a bit of a sequence issue,
> as I have also seen the mount message appear before the audio
> system comes up, so occasionally, the last item printed is:
> pcm0:   on uaudio0

This seems to indicate that the system is still responding,
i. e., the kernel is "up and running". Whenever "new" hardware
is detected, the kernel will issue a console message.

For example, on my home system the detection of the built-in
USB is sometimes a bit slow, so its messages appear "later on"
in the booting sequence, _after_ the initial kernel messages
(e. g., during firewall initialisation).



> I suspect that this may be a race condition of some kind, as
> yesterday I am sure I successfully booted to single-user while
> trying to solve a separate problem.

Try some more. :-)



> I am rebooting the machine at the moment as I wish to ensure
> that I know which physical disk is ada2, so want to boot the
> machine without it plugged in.

A suggestion: I tend to keep a tendency to use labels instead
of device names to identify disks. This is handy in case you're
running some kind of RAID configuration or use striping and
mirroring. Mark the disks with numbers and colors, as you prefer
(for example this nomenclature: color = stripe, number = mirror),
to reflect "being element of a stripe" and "being one of the
mirrors of N" properties both by the label (software) and the
physical disk (hardware). So you can _directly_ deduct from
a label (for example of a disk that is reported as failing)
like "red 2" that the disk is the 2nd mirror disk in the "red"
stripe, and _which_ physical disk is it? The one with a red "2"
on it. :-)





-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
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-time hard drive errors

[b w]

This is not very helpful, but you can try Pause, Scroll Lock, high FPS
filming and pause or taking pictures with short exposure.


On Mon, Feb 25, 2013 at 6:20 AM, Martin Alejandro Paredes Sanchez <
mapsw...@prodigy.net.mx> wrote:

> On Sunday 24 February 2013 14:33:06 Ronald F. Guilmette wrote:
> > I have a somewhat eclectic system, currently running (or at any rate,
> > trying to run) 9.1-RELEASE.  The system in question contains three
> > drives, to wit:
> >
> > ATA-8 SATA 3.x device
> > ATA-8 SATA 1.x device
> > ATA-8 SATA 3.x device
> >
> > Previously, I had the ST3500320AS in this system, along with one other
> > entirely different Seagate drive, i.e. one not shown in the list above.
> > (Also, I was previously running 8.3-RELEASE and only recently updated
> > to 9.1-RELEASE.)
> >
> > Since I reconfigured the system to its current state, i.e. with the set
> > of three drives listed above, whenever I reboot the system, about 50%
> > of the time, when the boot process gets down to the point where it
> > would ordinarily be printing out the messages relating to ada0, ada1,
> > etc. suddenly I start to get a massive and apparently endless stream
> > of error messages, apparently relating to one of the drives listed
> > above, but the stream actually alternates between two consecutive
> > error messages, both undoubtedly related to each other.
> >
>
> Does your HDD controller is SATA 3?
>
> I had a similar problem (some times could not boot) and was caused because
> my
> HDD controller is SATA 1
>
> Intel ICH5 SATA150 controller
>
> And my hard disk is SATA 2
>
> WDC WD2500AVVS-00L2B0 01.03A01
>
> The problem disapear when I lock the HDD at 150 MB/s (jumper settings the
> HDD
> to SATA 1)
> ___
> 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: Boot-time hard drive errors

[Martin Alejandro Paredes Sanchez]

On Sunday 24 February 2013 14:33:06 Ronald F. Guilmette wrote:
> I have a somewhat eclectic system, currently running (or at any rate,
> trying to run) 9.1-RELEASE.  The system in question contains three
> drives, to wit:
>
> ATA-8 SATA 3.x device
> ATA-8 SATA 1.x device
> ATA-8 SATA 3.x device
>
> Previously, I had the ST3500320AS in this system, along with one other
> entirely different Seagate drive, i.e. one not shown in the list above.
> (Also, I was previously running 8.3-RELEASE and only recently updated
> to 9.1-RELEASE.)
>
> Since I reconfigured the system to its current state, i.e. with the set
> of three drives listed above, whenever I reboot the system, about 50%
> of the time, when the boot process gets down to the point where it
> would ordinarily be printing out the messages relating to ada0, ada1,
> etc. suddenly I start to get a massive and apparently endless stream
> of error messages, apparently relating to one of the drives listed
> above, but the stream actually alternates between two consecutive
> error messages, both undoubtedly related to each other.
>

Does your HDD controller is SATA 3?

I had a similar problem (some times could not boot) and was caused because my 
HDD controller is SATA 1

Intel ICH5 SATA150 controller

And my hard disk is SATA 2

WDC WD2500AVVS-00L2B0 01.03A01

The problem disapear when I lock the HDD at 150 MB/s (jumper settings the HDD 
to SATA 1)
___
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-time hard drive errors

[Simon]

Have you tried Pause/Break to see if you could feeze the screen to get the
error message?

I would stress test all three drives to see if they pass with flying colors. One
or more of your drives could be indeed flaky, regardless being new, that means
little. Also, something could be conflicting from time to time, that could also
show up under stress testing.

Make backup if you have important data before stress testing.

-Simon

On Sun, 24 Feb 2013 13:33:06 -0800, Ronald F. Guilmette wrote:



>I have a somewhat eclectic system, currently running (or at any rate,
>trying to run) 9.1-RELEASE.  The system in question contains three
>drives, to wit:

>ATA-8 SATA 3.x device
>ATA-8 SATA 1.x device
>ATA-8 SATA 3.x device

>Previously, I had the ST3500320AS in this system, along with one other
>entirely different Seagate drive, i.e. one not shown in the list above.
>(Also, I was previously running 8.3-RELEASE and only recently updated
>to 9.1-RELEASE.)

>Since I reconfigured the system to its current state, i.e. with the set
>of three drives listed above, whenever I reboot the system, about 50%
>of the time, when the boot process gets down to the point where it
>would ordinarily be printing out the messages relating to ada0, ada1,
>etc. suddenly I start to get a massive and apparently endless stream
>of error messages, apparently relating to one of the drives listed
>above, but the stream actually alternates between two consecutive
>error messages, both undoubtedly related to each other.

>The boot process never completes, and I am just left staring at a
>screen that's displaying, in very rapid succession, first the one
>error message and then the other, and then the first one again, and
>then the second one again, and on and on like that.

>Unfortunately, the two error messages are being printed on the screen
>so fast (and alternating, as described above) that I cannot even read
>them, but I could just barely make out that they seem to relate to ada2...
>well, anyway, one or another of the hard drives.

>I do not know the proper way to rectify whatever is causing these "flaky"
>errors.  I use the term "flaky" because, as I have said, this boot-time
>problem only seems to occur maybe about 50% of the time, and the rest
>of the time when I boot up there is no problem whatsoever.

>Because I am able to boot up successfully, with no problems whatsoever,
>a significant fraction of the time, I am inclined to think that whatever
>is causing the failure is not actually a hardware fault.  (And by the way,
>the WDC drive and the Hitachi drive are both practically brand new.  That
>doesn't prove anything, of course, but it does make me think that they
>are unlikely to have serious hardware faults.)

>I would report this problem by filing a standard PR, but as I've said
>above, I can't even read the error messages, because they are being
>printed in such rapid succession, so I'm not sure that filing a PR
>would be useful to anybody.  I mean what would it say?  That I'm getting
>some unspecified failure at boot time that seems to relate to the hard
>drives in this system?  That kind of PR would clearly not be very helpful.

>Has anyone else ever encountered symptoms like those I have listed
>above, either with 9.1-RELEASE or with any other version of FreeBSD?


>Regards,
>rfg
>___
>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: Boot of 9.1 under qemu-kvm 1.3 hangs at pci probing

[Juergen Lock]

In article <50ce5805.7010...@cran.org.uk> you write:
>I'm trying to install FreeBSD 9.1 in a Proxmox KVM, using qemu-kvm 1.3, 
>but the boot process is hanging:
>
>pbib0: matched entry for 0.1 INTA
>pbib0: slot 1 INTA hardwired to IRQ 9
>ioapic0: Changing polarity for pin 9 to low
>found -> vendor=0x1013, dev=0x00b8, revid=0x00
>domain=0, bus=0, slot=2, func=0
>class=03-00-00, hdrtype=0x00, mfdev=0
>cmdreg=0x0103, statreg=0x, cachelnsz=0 (dwords)
>   lattimer=0x00 (0 ns), mingnt=0x00 (0ns), maxlat=0x00 (0ns)
>[hang]
>
>Has anyone come across this before and know of any workarounds?

Just in case you haven't meanwhile found this yourself (and for the
archives), this is caused by an incompatible change in seabios [1]
that qemu uses.  I hope this will be fixed for qemu 1.3.1, a fixed
bios.bin that you can pass to qemu/kvm with -bios has been posted
in this thread:

https://lists.nongnu.org/archive/html/qemu-devel/2012-12/msg01703.html

 HTH, :)
Juergen

[1] 
http://git.qemu.org/?p=seabios.git;a=commit;h=4540409d19a4baeec5006d925cfca19f8038a96e
___
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: Should newfs include -S 4096? was Re: boot problem after freebsd-update from 9.1-RC2 to 9.1-RC3

[Warren Block]

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 -f4
3907029168
(subtract 34, per WB) (I actually just subtracted the trailing 68)
dd if=/dev/zero of=/dev/ada0 seek=3907029100

This would still seem to not delete all of the metadata, since after issuing:

gmirror label -b split gm0 /dev/ada0
gmirror load
# repartition new mirror
gpart create -s MBR mirror/gm0
# ignore "mirror/gm0s1 added, but partition is not aligned on 4096 bytes" after 
add
gpart add -t freebsd -a 4k mirror/gm0
# create the bsdlabel partitions in slice 1 (s1)
gpart create -s BSD mirror/gm0s1

I would see that the old gm0s1a and gm0s1b had reappeared, even though I had 
not yet issued the 'add -t freebsd-ufs'. I'm not sure if they came back with 
the 'add -t freebsd' or the 'create -s BSD'.


Saved this since yesterday, thinking maybe I could come up with an idea, 
but so far I can't think what would cause that.  It might not hurt to 
force a retaste after the dd.



The only thing that seemed to fix it was:

gpart destroy -F /dev/ada0

I also tried at one point:

gpart destroy -F ada0
gpart create -s gpt ada0
gpart destroy -F ada0



The thing I wonder about now: Should newfs include -S 4096?

I used:

newfs -U /dev/mirror/gm0s1a

Will this lead to 512 byte sector access to the disk through the file system?

Will this impact performance or longevity of the mirror?


It's a good question; I have not tried it.
___
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"

Should newfs include -S 4096? was Re: boot problem after freebsd-update from 9.1-RC2 to 9.1-RC3

[freebsd]

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't supposed to work for 9.1-RC2
>>>
>>
>> I previously used binary update to migrate from 9.0 to 9.1, via:
>>
>> freebsd-update upgrade -r 9.1-RC1
>> freebsd-update install
>> reboot
>> freebsd-update install
>> reboot
>>
>> I'm starting to think having the swap partition in gm0s1a and the booting 
>> UFS partition in ada0s1b is the problem:
>> http://forums.freebsd.org/showthread.php?t=31954
>>
>> The "Not UFS" error comes immediately on boot.
>>
>> If I boot from rescue media, I can start the gmirror, mount it and chroot 
>> into it.
>>
>> The whole install seems fine except for the first stage boot loader finding 
>> the UFS partition.
>>
>> A handy bootloader config trick would be greatly appreciated!
> 
> boot(8) says
> 
>   The automatic boot will attempt to load /boot/loader from partition
>   `a' of either the floppy or the hard disk.
> 
> You could try setting the correct device path in /boot/boot.config, but I 
> suspect that won't be read until too late.
> 
> gptboot looks for the first UFS partition.  Maybe /boot/boot can be modified 
> to do that also.

I ended up booting from rescue media, removing one drive and stopping the 
gmirror, creating a new gmirror on the removed drive to place the UFS partition 
first, and performing a dump/restore to transfer the system. Then I was able to 
boot from the new gmitrror and add the second drive to it.

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 -f4
3907029168
(subtract 34, per WB) (I actually just subtracted the trailing 68)
dd if=/dev/zero of=/dev/ada0 seek=3907029100

This would still seem to not delete all of the metadata, since after issuing:

gmirror label -b split gm0 /dev/ada0
gmirror load
# repartition new mirror
gpart create -s MBR mirror/gm0
# ignore "mirror/gm0s1 added, but partition is not aligned on 4096 bytes" after 
add
gpart add -t freebsd -a 4k mirror/gm0
# create the bsdlabel partitions in slice 1 (s1)
gpart create -s BSD mirror/gm0s1

I would see that the old gm0s1a and gm0s1b had reappeared, even though I had 
not yet issued the 'add -t freebsd-ufs'. I'm not sure if they came back with 
the 'add -t freebsd' or the 'create -s BSD'. 

The only thing that seemed to fix it was:

gpart destroy -F /dev/ada0

I also tried at one point:

gpart destroy -F ada0
gpart create -s gpt ada0
gpart destroy -F ada0

After that I could create the new partitions within the slice, with freebsd-ufs 
first:

# size of ufs partition must be calculated, from 'diskinfo -v /dev/ada0':
2000398934016 # media size in bytes (1.8T)
; 1024*1024*1024
1073741824
; 2000398934016/1073741824
1863.01668548583984375
# subtract 8G from 1863 = 1855G
gpart add -t freebsd-ufs -a 4k -s 1855G mirror/gm0s1
gpart add -t freebsd-swap -a 4k mirror/gm0s1

Everything looks good with 4K alignment, and freebsd-ufs first:

gpart show
=>63  3907029104  mirror/gm0  MBR  (1.8T)
  63  63  - free -  (31k)
 126  3907028979   1  freebsd  [active]  (1.8T)
  3907029105  62  - free -  (31k)

=> 0  3907028979  mirror/gm0s1  BSD  (1.8T)
   0   2- free -  (1.0k)
   2  3890216960 1  freebsd-ufs  (1.8T)
  389021696216812016 2  freebsd-swap  (8.0G)
  3907028978   1- free -  (512B)

After newfs, I was able to dump/restore to transfer the installed system from 
ada1 to gm0 (which is 9.1-RC3 now).

The thing I wonder about now: Should newfs include -S 4096?

I used:

newfs -U /dev/mirror/gm0s1a

Will this lead to 512 byte sector access to the disk through the file system?

Will this impact performance or longevity of the mirror?

Thanks again for the sage advice!

johnea
___
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: gpt booting (Was: Re: boot problem after freebsd-update from 9.1-RC2 to 9.1-RC3)

[Warren Block]

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 both the 
bootme and bootonce attributes set. If it doesn't find any, or if they all 
failed to boot it then tries booting partitions with just the bootme 
attribute. It only boots the first UFS partition if no partitions have the 
bootme attribute set, and IIRC that is for compatibility with the 8.x gptboot 
which didn't know the boot* attributes.


Confusingly, there's no manual page for gptboot to document this. It's sort 
of implicit in the gpart manual page, in the section on ATTRIBUTES for GPT, 
but the best way to understand it is to read the code for gptfind in


/usr/src/sys/boot/common/gpt.c


Well, yes.  The point is that gptboot doesn't just assume that p2, say, 
is where the bootable UFS partition must be.


I've also noted the lack of a gptboot man page, and it's on my long list 
of Things That Should Be Done.  There was a thread on -doc:

http://lists.freebsd.org/pipermail/freebsd-doc/2012-June/020060.html

Help would be greatly appreciated.
___
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"

gpt booting (Was: Re: boot problem after freebsd-update from 9.1-RC2 to 9.1-RC3)

[Arthur Chance]

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. If it doesn't find any, or if 
they all failed to boot it then tries booting partitions with just the 
bootme attribute. It only boots the first UFS partition if no partitions 
have the bootme attribute set, and IIRC that is for compatibility with 
the 8.x gptboot which didn't know the boot* attributes.


Confusingly, there's no manual page for gptboot to document this. It's 
sort of implicit in the gpart manual page, in the section on ATTRIBUTES 
for GPT, but the best way to understand it is to read the code for 
gptfind in


/usr/src/sys/boot/common/gpt.c


___
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 after freebsd-update from 9.1-RC2 to 9.1-RC3

[Warren Block]

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 to migrate from 9.0 to 9.1, via:

freebsd-update upgrade -r 9.1-RC1
freebsd-update install
reboot
freebsd-update install
reboot

I'm starting to think having the swap partition in gm0s1a and the booting UFS 
partition in ada0s1b is the problem:
http://forums.freebsd.org/showthread.php?t=31954

The "Not UFS" error comes immediately on boot.

If I boot from rescue media, I can start the gmirror, mount it and chroot into 
it.

The whole install seems fine except for the first stage boot loader finding the 
UFS partition.

A handy bootloader config trick would be greatly appreciated!


boot(8) says

  The automatic boot will attempt to load /boot/loader from partition
  `a' of either the floppy or the hard disk.

You could try setting the correct device path in /boot/boot.config, but 
I suspect that won't be read until too late.


gptboot looks for the first UFS partition.  Maybe /boot/boot can be 
modified to do that also.

___
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 after freebsd-update from 9.1-RC2 to 9.1-RC3

[freebsd]

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-update upgrade -r 9.1-RC1
freebsd-update install
reboot
freebsd-update install
reboot

I'm starting to think having the swap partition in gm0s1a and the booting UFS 
partition in ada0s1b is the problem:
http://forums.freebsd.org/showthread.php?t=31954

The "Not UFS" error comes immediately on boot. 

If I boot from rescue media, I can start the gmirror, mount it and chroot into 
it.

The whole install seems fine except for the first stage boot loader finding the 
UFS partition.

A handy bootloader config trick would be greatly appreciated!

johnea
___
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 after freebsd-update from 9.1-RC2 to 9.1-RC3

[Gary Aitken]

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)
>   126  3907028979   1  freebsd  [active]  (1.8T)
>3907029105  62  - free -  (31k)
> 
> => 0  3907028979  mirror/gm0s1  BSD  (1.8T)
> 0   2- free -  (1.0k)
> 216777216 1  freebsd-swap  (8.0G)
>  16777218  3890251760 2  freebsd-ufs  (1.8T)
>3907028978   1- free -  (512B)
> 
> The drive was setup with the following commands:
> 
> orsbackup# gpart create -s MBR mirror/gm0
> mirror/gm0 created
> orsbackup# gpart add -t freebsd -a 4k mirror/gm0
> # ignored "mirror/gm0s1 added, but partition is not aligned on 4096 bytes"
> # create the bsdlabel partitions in slice 1 (s1)
> orsbackup# gpart create -s BSD mirror/gm0s1
> orsbackup# gpart add -t freebsd-swap -a 4k -s 8g mirror/gm0s1
> orsbackup# gpart add -t freebsd-ufs -a 4k mirror/gm0s1
> # put bootcode on the MBR and mark the first slice active
> orsbackup# gpart bootcode -b /boot/mbr mirror/gm0
> orsbackup# gpart set -a active -i 1 mirror/gm0
> # put bootcode on the bsdlabel
> orsbackup# gpart bootcode -b /boot/boot mirror/gm0s1
> 
> 
> The system rebooted several times without issue. This system is a testbed for 
> 9.1 and is not yet deployed as a production server.
> 
> I thought I'd update to 9.1-RC3, so I ran:
> 
> freebsd-update upgrade -r 9.1-RC3
> freebsd-update install
> reboot
> 
> The system won't boot and complains about:
> 
> "Not UFS"  "No ada0" "No boot"
> 
> Before I charge ahead with reissuing the gpart bootcode commands I thought 
> I'd:
> 
> a) make others aware there may be issues in freebsd-update with the 9.1 
> release candidates
> 
> b) ask about the best way to resolve this bootloader issue.
> 
> Thanks you for any pointers in resolving this bootloader issue!
> 
> johnea

Not sure, but this might apply:

 The freebsd-update tool is used to fetch, install, and rollback binary
 updates to the FreeBSD base system.  Note that updates are only available
 if they are being built for the FreeBSD release and architecture being
 used; in particular, the FreeBSD Security Team only builds updates for
 releases shipped in binary form by the FreeBSD Release Engineering Team,
 e.g., FreeBSD 7.3-RELEASE and FreeBSD 8.0-RELEASE, but not FreeBSD
 6.3-STABLE or FreeBSD 9.0-CURRENT.

Seems like it isn't supposed to work for 9.1-RC2


___
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 error

[jb]

Per olof Ljungmark  intersonic.se> writes:

> ... 
> Try a verbose boot.

I forgot to mention:
$ uname -a
FreeBSD localhost.localdomain 9.1-RC1 FreeBSD 9.1-RC1 #0: Tue Aug 14 03:56:40
UTC 2012 r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386

I set Verbose ON and put hw.usb.ugen.debug="1" in /boot/loader.conf as
originally ugen(4) driver followed the point of lockup.

This time the log sequence was a little different - the ata(4) driver
followed the point of lockup.

If I understand it correctly, these log messages may be recorded in somewhat
random sequence, so the dmesg output sequence in not 100% reliable.
Anyway, here it is:

$ dmesg -a
...
usbus0: 12Mbps Full Speed USB v1.0
usbus1: 12Mbps Full Speed USB v1.0
usbus2: 480Mbps High Speed USB v2.0
usbus3: 12Mbps Full Speed USB v1.0
usbus4: 12Mbps Full Speed USB v1.0
usbus5: 12Mbps Full Speed USB v1.0
usbus6: 480Mbps High Speed USB v2.0
< HERE THE BOOT LOCKUP HAPPENED <=
ata0: reset tp1 mask=03 ostat0=50 ostat1=00
ata0: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb
ata0: stat1=0x00 err=0x00 lsb=0x00 msb=0x00
ata0: reset tp2 stat0=00 stat1=00 devices=0x1
ugen0.1:  at usbus0
uhub0:  on usbus0
ugen1.1:  at usbus1
uhub1:  on usbus1
ugen2.1:  at usbus2
uhub2:  on usbus2
ugen3.1:  at usbus3
uhub3:  on usbus3
ugen4.1:  at usbus4
uhub4:  on usbus4
ugen5.1:  at usbus5
uhub5:  on usbus5
ugen6.1:  at usbus6
uhub6:  on usbus6
ahcich0: AHCI reset...
...

More ideas what to look for or catch ?
jb






___
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 error

[Per olof Ljungmark]

On 2012-09-28 14:16, jb wrote:

Hi,

the boot of my notebook Lenovo TP r61i stops (sometimes) after usbus6.
$ dmesg
...
atkbdc0:  port 0x60,0x64 irq 1 on acpi0
atkbd0:  irq 1 on atkbdc0
...skipping...
hdaa0:  at nid 1 on hdacc0
pcm0:  at nid 16,17 and 20 on
hdaa0
unknown:  at nid 2
on hdacc0 (no driver attached)
usbus0: 12Mbps Full Speed USB v1.0
usbus1: 12Mbps Full Speed USB v1.0
usbus2: 480Mbps High Speed USB v2.0
usbus3: 12Mbps Full Speed USB v1.0
usbus4: 12Mbps Full Speed USB v1.0
usbus5: 12Mbps Full Speed USB v1.0
usbus6: 480Mbps High Speed USB v2.0
< IT STOPS HERE <= >
ugen0.1:  at usbus0
uhub0:  on usbus0
ugen1.1:  at usbus1
uhub1:  on usbus1
ugen2.1:  at usbus2
uhub2:  on usbus2
ugen3.1:  at usbus3
uhub3:  on usbus3
ugen4.1:  at usbus4
uhub4:  on usbus4
ugen5.1:  at usbus5
uhub5:  on usbus5
ugen6.1:  at usbus6
uhub6:  on usbus6
uhub0: 2 ports with 2 removable, self powered
uhub1: 2 ports with 2 removable, self powered
uhub3: 2 ports with 2 removable, self powered
uhub4: 2 ports with 2 removable, self powered
uhub5: 2 ports with 2 removable, self powered
uhub2: 4 ports with 4 removable, self powered
uhub6: 6 ports with 6 removable, self powered
...

$ pciconf -lv
hostb0@pci0:0:0:0:  class=0x06 card=0x20b317aa chip=0x2a008086 rev=0x0c
hdr=0x00
 vendor = 'Intel Corporation'
 device = 'Mobile PM965/GM965/GL960 Memory Controller Hub'
 class  = bridge
 subclass   = HOST-PCI
vgapci0@pci0:0:2:0: class=0x03 card=0x20b517aa chip=0x2a028086 rev=0x0c
hdr=0x00
 vendor = 'Intel Corporation'
 device = 'Mobile GM965/GL960 Integrated Graphics Controller (primary)'
 class  = display
 subclass   = VGA
vgapci1@pci0:0:2:1: class=0x038000 card=0x20b517aa chip=0x2a038086 rev=0x0c
hdr=0x00
 vendor = 'Intel Corporation'
 device = 'Mobile GM965/GL960 Integrated Graphics Controller
  (secondary)'
 class  = display
uhci0@pci0:0:26:0:  class=0x0c0300 card=0x20aa17aa chip=0x28348086 rev=0x03
hdr=0x00
 vendor = 'Intel Corporation'
 device = '82801H (ICH8 Family) USB UHCI Controller'
 class  = serial bus
 subclass   = USB
uhci1@pci0:0:26:1:  class=0x0c0300 card=0x20aa17aa chip=0x28358086 rev=0x03
hdr=0x00
 vendor = 'Intel Corporation'
 device = '82801H (ICH8 Family) USB UHCI Controller'
 class  = serial bus
 subclass   = USB
ehci0@pci0:0:26:7:  class=0x0c0320 card=0x20ab17aa chip=0x283a8086 rev=0x03
hdr=0x00
 vendor = 'Intel Corporation'
 device = '82801H (ICH8 Family) USB2 EHCI Controller'
 class  = serial bus
 subclass   = USB
hdac0@pci0:0:27:0:  class=0x040300 card=0x20ac17aa chip=0x284b8086 rev=0x03
hdr=0x00
 vendor = 'Intel Corporation'
 device = '82801H (ICH8 Family) HD Audio Controller'
 class  = multimedia
 subclass   = HDA
pcib1@pci0:0:28:0:  class=0x060400 card=0x20ad17aa chip=0x283f8086 rev=0x03
hdr=0x01
 vendor = 'Intel Corporation'
 device = '82801H (ICH8 Family) PCI Express Port 1'
 class  = bridge
 subclass   = PCI-PCI
pcib2@pci0:0:28:1:  class=0x060400 card=0x20ad17aa chip=0x28418086 rev=0x03
hdr=0x01
 vendor = 'Intel Corporation'
 device = '82801H (ICH8 Family) PCI Express Port 2'
 class  = bridge
 subclass   = PCI-PCI
pcib3@pci0:0:28:2:  class=0x060400 card=0x20ad17aa chip=0x28438086 rev=0x03
hdr=0x01
 vendor = 'Intel Corporation'
 device = '82801H (ICH8 Family) PCI Express Port 3'
 class  = bridge
 subclass   = PCI-PCI
uhci2@pci0:0:29:0:  class=0x0c0300 card=0x20aa17aa chip=0x28308086 rev=0x03
hdr=0x00
 vendor = 'Intel Corporation'
 device = '82801H (ICH8 Family) USB UHCI Controller'
 class  = serial bus
 subclass   = USB
uhci3@pci0:0:29:1:  class=0x0c0300 card=0x20aa17aa chip=0x28318086 rev=0x03
hdr=0x00
 vendor = 'Intel Corporation'
 device = '82801H (ICH8 Family) USB UHCI Controller'
 class  = serial bus
 subclass   = USB
uhci4@pci0:0:29:2:  class=0x0c0300 card=0x20aa17aa chip=0x28328086 rev=0x03
  hdr=0x00
 vendor = 'Intel Corporation'
 device = '82801H (ICH8 Family) USB UHCI Controller'
 class  = serial bus
 subclass   = USB
ehci1@pci0:0:29:7:  class=0x0c0320 card=0x20ab17aa chip=0x28368086 rev=0x03
  hdr=0x00
 vendor = 'Intel Corporation'
 device = '82801H (ICH8 Family) USB2 EHCI Controller'
 class  = serial bus
 subclass   = USB
pcib4@pci0:0:30:0:  class=0x060401 card=0x20ae17aa chip=0x24488086 rev=0xf3
  hdr=0x01
 vendor = 'Intel Corporation'
 device = '82801 Mobile PCI Bridge'
 class  = bridge
 subclass   = PCI-PCI
isab0@pci0:0:31:0:  class=0x060100 card=0x20a517aa chip=0x28158086 rev=0x03
  hdr=0x00
 vendor = 'Intel Corporation'
 device = '82801HEM (I

Re: boot time error(?) involving snd_hda

[Robert Huff]

Erich Dollansky writes:

>  the kernel module sound.ko should be loaded automatically when
>  snd_hda is loaded. Can you check if this module exists on your
>  machine?

Yes, as "/boot/kernel/sound.ko".

>  sound.ko is loaded whenever snd_hda is loaded on my 8.3
>  machine. Can you do a kldstat? 

Reports "sound.ko" loaded, with a size of 877a8.

So ... it's a bogus error message?



Robert Huff

___
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 time error(?) involving snd_hda

[Erich Dollansky]

Hi,

On Friday 23 March 2012 21:18:37 Robert Huff wrote:
> 
>   On a system running:
> 
> FreeBSD 10.0-CURRENT #0: Sun Mar 11 08:20:02 EDT 2012 amd64 
> 
>   a message flashes by during boot about "Missing required module
> 'sound'."
>   loader.conf has:
> 
> snd_hda_load="YES"

the kernel module sound.ko should be loaded automatically when snd_hda is 
loaded. Can you check if this module exists on your machine?
> 
> 
>   Looking at "man snd+hda" I see this:
> 
> 
>  To compile this driver into the kernel, place the following
>  lines in your kernel configuration file:
> 
>   device sound
>   device snd_hda
> 
>  Alternatively, to load the driver as a module at boot time,
>  place the following line in loader.conf(5):
> 
>  snd_hda_load="YES"
> -
> 
>   The formatting here makes these seem (for lack of a better
> term) mutually exclusive, and so the kernel config does not have
> "device sound".
>   Have I misunderstood?
>   Is the documentation flawed?
> 
>   (In spite of the message, sound works fine.  I just want to get
> rid of the error message, and/or rectify the docuemntation.)

sound.ko is loaded whenever snd_hda is loaded on my 8.3 machine. Can you do a 
kldstat?

Erich
___
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/loader splash image

[Pan Tsu]

Fbsd8  writes:

> wayne mitchell wrote:
>> hey
>> got question/problem for /boot/loader
>>
>> system: freeBSD 8.1-RELEASE GENERIC
>>
>> trying to get a bitmap onscreen for bootup
>> 
>>
>> have read man page for all boot associated stuff (loader.conf...)
>> and followed instructions
>> using following values in /boot/loader.conf :
>>
>> bitmap_load="YES"# have tried commenting this out also
>> vesa_load="YES"
>> splash_bmp_load="YES"
>> bitmap_name="/boot/splash.bmp"
>>
>> the splash.bmp size is about 900x700
>> does not work
>> am using /boot/loader.rc as preset (includes loader.4th and beastie.4th)
>
> Try putting vesa_load="YES" first.

It's not that useful without SC_PIXEL_MODE which is not in GENERIC.
___
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/loader splash image

[Duane Hill]

Sunday, July 17, 2011, 6:07:57 PM, Fbsd8 wrote:

> wayne mitchell wrote:
>> hey
>> got question/problem for /boot/loader
>> 
>> system: freeBSD 8.1-RELEASE GENERIC
>> 
>> trying to get a bitmap onscreen for bootup
>> 
>> 
>> have read man page for all boot associated stuff (loader.conf...)
>> and followed instructions
>> using following values in /boot/loader.conf :
>> 
>> bitmap_load="YES"# have tried commenting this out also
>> vesa_load="YES"
>> splash_bmp_load="YES"
>> bitmap_name="/boot/splash.bmp"
>> 
>> the splash.bmp size is about 900x700
>> does not work
>> am using /boot/loader.rc as preset (includes loader.4th and beastie.4th)

> Try putting vesa_load="YES" first.

The image must also be 256-color.

-- 
Best regards,
 Duanemailto:du...@duanemail.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: boot/loader splash image

[Fbsd8]

wayne mitchell wrote:

hey
got question/problem for /boot/loader

system: freeBSD 8.1-RELEASE GENERIC

trying to get a bitmap onscreen for bootup


have read man page for all boot associated stuff (loader.conf...)
and followed instructions
using following values in /boot/loader.conf :

bitmap_load="YES"# have tried commenting this out also
vesa_load="YES"
splash_bmp_load="YES"
bitmap_name="/boot/splash.bmp"

the splash.bmp size is about 900x700
does not work
am using /boot/loader.rc as preset (includes loader.4th and beastie.4th)
___
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"




Try putting vesa_load="YES" first.
___
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 Environments

[krad]

On 30 June 2011 08:43, Dick Hoogendijk  wrote:

> On solaris you can have different BE's (boot environments) using ZFS.
> Is this possible with FreeBSD ZFS? I can't recall ever have seen a tool
> like BEadm (solaris).
> But maybe using ZFS manually I can get more BE's?
> __**_
> 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 "
>

 im not aware of any specific tools to do it but i have mimicked opensolaris
be's on my bsd machines. After all most of it is just monkeying around with
zfs fs cloning and setting the DESTDIR variable when you install updates
___
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 question

[Robert Simmons]

On Saturday, May 14, 2011 10:38:37 AM you wrote:
> > Date: Sat, 14 May 2011 09:44:42 -0400
> > From: Robert Simmons 
> > To: freebsd-questions@freebsd.org
> > Subject: boot question
> >
> > How do I boot from a kernel that is in a non-standard location on a disk
> > that is partitioned with the GPT scheme?
> 
> Things get a *LOT* messier if you want t relocate 'boot0' through 'boot4'
> as well as /boot/kernel.  Depending on _just_ what you want to do, you
> may have to build and install custom versions of those executables.

This is exactly what I want to do.  I want a minimum of three partitions on 
the drive.  One for swap, of course, but the other two I want to be:
/boot
/

I have gotten the kernel to boot by tricking boot2 into finding boot.config by 
locating it at /boot/boot.config rather than /boot.config and adding the 
following line to boot.config:
0:ad(0,1,a)/kernel/kernel

This gets me to the point where I have to enter the mount points manually at 
the "mountroot>" prompt.  So, this is good progress.

This skips the loader stage of booting, however, which I would like to not 
have to do.  The problem is that if I put the following line in boot.config:
0:ad(0,1,a)/loader
then the loader cannot find its config file "loader.conf"

In boot(8) there doesn't seem to be a flag that you can pass to set where to 
find loader.conf. So, how can I tell it where to find loader.conf if it is in a 
non-standard location?
___
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

[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"

Re: boot problem

[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 error

[ajtiM]

On Sunday 27 March 2011 09:26:26 Franci Nabalanci wrote:
> I boot in the single user mode and when I run /sbin fsck -y I got
> "Permission denied". The same is if I /mount -w / and I gor Permission
> Denied.
> 
> 
> On Sun, Mar 27, 2011 at 9:11 AM, Erich Dollansky <
> 
> erichfreebsdl...@ovitrap.com> wrote:
> > Hi,
> > 
> > On Sunday 27 March 2011 20:17:09 Franci Nabalanci wrote:
> > > Hi!
> > > 
> > > My system is FreeBSD releaese 8.2.
> > > I installed KDE 4.6.1 and run it. And I updated ATI drivers too.
> > > When I start KDE It freeze when I try to change a background picture..
> > 
> > After
> > 
> > > restart of computer I got an error and boot in the single mode.
> > > /dev/ad0s1a: LINK COUNT DIR I=376823 OWNER= ROOT mode 40700 SIZE=1024
> > 
> > MTIME=
> > 
> > > Mar 27 ...COUNT 18 SHOULD BE 19
> > > /dev/ad0s1a LINK COUNT INCREASING
> > > /dev/ad0s1a UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY
> > > Automatic file system check failed: help!
> > > ERROR: ABORTING BOOT
> > > (sending SIGTERM to parent)!
> > > 
> > > If I manually run fsck -p (for example) /dev/ad0s1a I got permission
> > 
> > denied.
> > 
> > you have to boot into single user mode to run fsck on the root partition.
> > 
> > Erich
 I was my mistake, gr. I wrote /sbin/ fsck -y and should nbe /sbin/fsck -y

Thanks.
Mitja

http://jpgmag.com/people/lumiwa
___
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 error

[Franci Nabalanci]

I boot in the single user mode and when I run /sbin fsck -y I got
"Permission denied". The same is if I /mount -w / and I gor Permission
Denied.


On Sun, Mar 27, 2011 at 9:11 AM, Erich Dollansky <
erichfreebsdl...@ovitrap.com> wrote:

> Hi,
>
> On Sunday 27 March 2011 20:17:09 Franci Nabalanci wrote:
> > Hi!
> >
> > My system is FreeBSD releaese 8.2.
> > I installed KDE 4.6.1 and run it. And I updated ATI drivers too.
> > When I start KDE It freeze when I try to change a background picture..
> After
> > restart of computer I got an error and boot in the single mode.
> > /dev/ad0s1a: LINK COUNT DIR I=376823 OWNER= ROOT mode 40700 SIZE=1024
> MTIME=
> > Mar 27 ...COUNT 18 SHOULD BE 19
> > /dev/ad0s1a LINK COUNT INCREASING
> > /dev/ad0s1a UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY
> > Automatic file system check failed: help!
> > ERROR: ABORTING BOOT
> > (sending SIGTERM to parent)!
> >
> > If I manually run fsck -p (for example) /dev/ad0s1a I got permission
> denied.
> >
> you have to boot into single user mode to run fsck on the root partition.
>
> Erich
>
___
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 error

[Erich Dollansky]

Hi,

On Sunday 27 March 2011 20:17:09 Franci Nabalanci wrote:
> Hi!
> 
> My system is FreeBSD releaese 8.2.
> I installed KDE 4.6.1 and run it. And I updated ATI drivers too.
> When I start KDE It freeze when I try to change a background picture.. After
> restart of computer I got an error and boot in the single mode.
> /dev/ad0s1a: LINK COUNT DIR I=376823 OWNER= ROOT mode 40700 SIZE=1024 MTIME=
> Mar 27 ...COUNT 18 SHOULD BE 19
> /dev/ad0s1a LINK COUNT INCREASING
> /dev/ad0s1a UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY
> Automatic file system check failed: help!
> ERROR: ABORTING BOOT
> (sending SIGTERM to parent)!
> 
> If I manually run fsck -p (for example) /dev/ad0s1a I got permission denied.
> 
you have to boot into single user mode to run fsck on the root partition.

Erich
___
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 linux

[Ilya Kazakevich]

You need to install boot0cfg in your MBR

man boot0cfg
http://www.freebsd.org/doc/en/books/handbook/boot-blocks.html

Honestly you
can use any MBR loader you like (grub, lilo, boot0cfg, windows). Windows
can't access boot sector on non-ntfs partitions, so you need to fetch first
block from your unix slice (boot1 or take it from /boot/boot1) and store it
as file (like freebsd.blk) on windows drive.
Grub and lilo probably can access slice their selfs.
boot0cfg definitely can.

Ilya.


On Tue, Mar 22, 2011 at 10:32 AM, xinyou yan  wrote:

>  i install freebsd last
>
> reboot ,I can find
>
> F1 windows
> F2?
> F3 freebsd
>
> where can i fix to load my linux ?
> I install grub on /devsd7
>
> Now i use windows to load grub then linux
> However I want to loader linux  directly .
> ___
> 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: boot, rc script and logs

[Ian Smith]

On Wed, 15 Dec 2010 15:42:29 +0100, Samuel Martín Moro wrote:
 > On Wed, Dec 15, 2010 at 4:57 AM, Ian Smith  wrote:
[..]
 > >  > Dec 14 13:26:47 camtrace13 kernel: ^[[m
 > >  > Dec 14 13:26:47 camtrace13 kernel: ^[[39;49m^[[=1S
 > >  > Dec 14 13:26:47 camtrace13 kernel:
 > >  >
 > > ^[[39;49m^[[m^[[H^[[J^[[17d^[[36m^[[44m^[[1m^[[J^[[H^[[K^[[B^[[K^[[B^[[K^[[B^[[K^[[B^[[K^[[B^[[K^[[B^[[K^[[B^[[K^[[B
 > > * > ^[[37m^[[**47mÿÿ**
 > > [[m^[[30m^[[47mÿÿ[[m^[[**36m^[[44m^[[1m^[[K^[[B*
 > >
 > err.. we may have a encoding problem.

Indeed.  I originally quoted yours from a digest, which are text-only, 
US-ASCII.  Your reply has your name in ISO-8859-1, but both text and 
HTML parts in UTF-8.  I expect this reply (with your i-acute correct) 
will be text-only, ISO-8859-1.  pine does its best, but gmail confuses 
it; I don't know if not also sending HTML parts to the list may help, 
as mailman drops non-plaintext attachments, including HTML, anyway.

 > but I'm quite sure it only is clearscreen, colors, and tputs stuff
 > 
 > >  > ^[[37m^[[47mÿÿ[[m^[[30m^[[47m^[[68X^[[74`ÿÿ[[m^[[30m^[[40m^[[1m
 > >  > ^[[36m^[[44m^[[K^[[B^[[37m^[[47mÿÿ[[m^[[30m^[[47m   Checking DB
 > >  > 1/2^[[20X^[[74`ÿÿ[[m^[[30m^[[40m^[[1m  ^[[36m^[[44m^[[K^[[B
 > > [..]
 > >  > Dec 14 13:26:48 camtrace13 kernel: Starting slim.
 > >  > Dec 14 13:26:48 camtrace13 kernel: Starting
 > >
 > 
 > > You'll need to rework this somehow so dialog's stdout isn't written to
 > > /dev/console, though that may seem necessary if you want it coming up on
 > > the VTY0 boot screen.  It may involve decoupling this task from running
 > > 'inline' as a boot script somehow, or else making sure that output is
 > > redirected to a log or temporary file instead of directly into dialog.
 > >
 > kay.
 > It's now fixed.
 > OUT=`/sbin/conscontrol | /usr/bin/sed -n 's;^Configured: 
 > .*\(tty[^,]*\).*$;/dev/\1;p'`
 > (is it always /dev/ttyv0? in doubt, I'll trust conscontrol)
 > [...] $DIALOG [...] >$OUT

Ah, bien.  Yes I think it'll always be ttyv0 at that time, but that's an 
elegant solution.  Thanks, we've both learned something!

cheers, Ian___
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, rc script and logs

[Samuel Martín Moro]

On Wed, Dec 15, 2010 at 4:57 AM, Ian Smith  wrote:

> In freebsd-questions Digest, Vol 341, Issue 3, Message: 17
> On Tue, 14 Dec 2010 19:02:54 +0100 Samuel Mart?n Moro 
> wrote:
>  > Hi,
>  >
>  > I'm adding some scripts to FreeBSD boot.
>  > One of this script runs a binary that checks our postgres database, its
>  > output being redirected to a dialog --gauge.
>  > But I noticed that the dialog output, while correctly displayed on the
>  > terminal, is also dumped into /var/log/console.log and
> /var/log/messages.
>  >
>  > I'm not even sure about how this is happening... I can't find about
> messages
>  > nor console.log in /etc/rc*
>
> As you indicate below, 'tty is /dev/console' while running the boot rc
> scripts, so it's normal to see these scripts logged to console.log when
> that's ebabled .. presumably /etc/syslog.conf includes something like:
> # uncomment this to log all writes to /dev/console to /var/log/console.log
> console.info/var/log/console.log
>
indeed it does.

>
>  > Is there a way to disable log output in a given rc.script?
>  >
>  > here's my script:
>  > #!/bin/sh
>  > [...]
>  > test "$1" = 'start' -o "$1" = 'faststart' || exit 0
>  > Prg=`basename $_file`
>  > exec 2>/var/log/$Prg.log
>
> You're redirecting stderr to your logfile, but not stdout, so standard
> output from the below goes to /dev/console, so also to /console.log
>
>  > test "$TERM" || export TERM=cons25
>  > DIALOG="/usr/local/bin/dialog --no-collapse --cr-wrap --colors"
>  > echo "tty is `tty`" >&2 #debug, prints: tty is /dev/console
>  > echo "= Checking DB 1/2 =" >&2
>
> The above line is also written to stdout, so to console.log below, so
> I'm not sure whether your exec usage | syntax | redirection is correct.
>
it is
dialog is used to display menus using curses
during the boot process, everything "looks" fine (except for logs), menus
are correctly displayed, while processing the DB scan.

>
>  > dbcheck -s | $DIALOG --gauge "\n  Checking DB 1/2" 7 70
> 2>/dev/null
>  > echo "= Checking DB 2/2 =" >&2
>  > dbcheck -r -s | $DIALOG --gauge "\n  Checking DB 2/2" 7 70
> 2>/dev/null
>  > [...]
>  >
>  > here is what it gives in /var/log/messages:
>  > Dec 14 13:26:46 camtrace13 dhclient: New Subnet Mask (wlan0):
> 255.255.255.0
>  > Dec 14 13:26:46 camtrace13 dhclient: New Broadcast Address (wlan0):
>  > 192.168.0.255
>  > Dec 14 13:26:46 camtrace13 dhclient: New Routers (wlan0): 192.33.160.111
>  > Dec 14 13:26:47 camtrace13 kernel: m  ^[[36m^[[44m^[[K^[[16;6H^[[1K
>  > ^[[30m^[[40m^[[70X^[[77`^[[36m^[[44m^[[K^[[13;9H^[[39;49m^[[m
>  > Dec 14 13:26:48 camtrace13 kernel: m  ^[[36m^[[44m^[[K^[[16;6H^[[1K
>  > ^[[30m^[[40m^[[70X^[[77`^[[36m^[[44m^[[K^[[13;9H^[[39;49m^[[m
>
> I don't know why those two dialog lines are sent to /var/log/messages;
> perhaps they indicate some error, only those being logged with *.notice?
>
this lines are mostly color code, used to display a grey window with a
gauge, on a blue background.

>
> [..]
>
>  > and here is what I can read in /var/log/console.log:
>  > Dec 14 13:26:43 camtrace13 kernel: Starting apache.
>  > Dec 14 13:26:46 camtrace13 kernel: Starting pgsql.
>
> If you view these scripts you'll see that they don't themselves write to
> stdout .. it's the rc system logging these.
>
indeed, I noticed yesterday that "Starting ${name}" is part of rc.subr

>
>  > Dec 14 13:26:47 camtrace13 kernel: ^[[m
>  > Dec 14 13:26:47 camtrace13 kernel: ^[[39;49m^[[=1S
>  > Dec 14 13:26:47 camtrace13 kernel:
>  >
> ^[[39;49m^[[m^[[H^[[J^[[17d^[[36m^[[44m^[[1m^[[J^[[H^[[K^[[B^[[K^[[B^[[K^[[B^[[K^[[B^[[K^[[B^[[K^[[B^[[K^[[B^[[K^[[B
> * > ^[[37m^[[**47m谀哪哪**
> 哪哪哪腲[[m^[[30m^[[47m縙[[m^[[**36m^[[44m^[[1m^[[K^[[B*
>
err.. we may have a encoding problem.
but I'm quite sure it only is clearscreen, colors, and tputs stuff

>  > ^[[37m^[[47m砠[[m^[[30m^[[47m^[[68X^[[74`砠[[m^[[30m^[[40m^[[1m
>  > ^[[36m^[[44m^[[K^[[B^[[37m^[[47m砠[[m^[[30m^[[47m   Checking DB
>  > 1/2^[[20X^[[74`砠[[m^[[30m^[[40m^[[1m  ^[[36m^[[44m^[[K^[[B
> [..]
>  > Dec 14 13:26:48 camtrace13 kernel: Starting slim.
>  > Dec 14 13:26:48 camtrace13 kernel: Starting
>

> You'll need to rework this somehow so dialog's stdout isn't written to
> /dev/console, though that may seem necessary if you want it coming up on
> the VTY0 boot screen.  It may involve decoupling this task from running
> 'inline' as a boot script somehow, or else making sure that output is
> redirected to a log or temporary file instead of directly into dialog.
>
kay.
It's now fixed.
OUT=`/sbin/conscontrol | /usr/bin/sed -n 's;^Configured: .*\(tty[^,
]*\).*$;/dev/\1;p'`
(is it always /dev/ttyv0? in doubt, I'll trust conscontrol)
[...] $DIALOG [...] >$OUT

>
>  > dhclient and oss seem to dump their output in /var/log/messages, while
>  > apache, postgresql and slim dump their one in /var/log/console.log
>  > So... How 

Re: boot, rc script and logs

[Ian Smith]

In freebsd-questions Digest, Vol 341, Issue 3, Message: 17
On Tue, 14 Dec 2010 19:02:54 +0100 Samuel Mart?n Moro  wrote:
 > Hi,
 > 
 > I'm adding some scripts to FreeBSD boot.
 > One of this script runs a binary that checks our postgres database, its
 > output being redirected to a dialog --gauge.
 > But I noticed that the dialog output, while correctly displayed on the
 > terminal, is also dumped into /var/log/console.log and /var/log/messages.
 > 
 > I'm not even sure about how this is happening... I can't find about messages
 > nor console.log in /etc/rc*

As you indicate below, 'tty is /dev/console' while running the boot rc 
scripts, so it's normal to see these scripts logged to console.log when 
that's ebabled .. presumably /etc/syslog.conf includes something like:
# uncomment this to log all writes to /dev/console to /var/log/console.log 
console.info/var/log/console.log

 > Is there a way to disable log output in a given rc.script?
 > 
 > here's my script:
 > #!/bin/sh
 > [...]
 > test "$1" = 'start' -o "$1" = 'faststart' || exit 0
 > Prg=`basename $_file`
 > exec 2>/var/log/$Prg.log

You're redirecting stderr to your logfile, but not stdout, so standard 
output from the below goes to /dev/console, so also to /console.log

 > test "$TERM" || export TERM=cons25
 > DIALOG="/usr/local/bin/dialog --no-collapse --cr-wrap --colors"
 > echo "tty is `tty`" >&2 #debug, prints: tty is /dev/console
 > echo "= Checking DB 1/2 =" >&2

The above line is also written to stdout, so to console.log below, so 
I'm not sure whether your exec usage | syntax | redirection is correct.

 > dbcheck -s | $DIALOG --gauge "\n  Checking DB 1/2" 7 70 2>/dev/null
 > echo "= Checking DB 2/2 =" >&2
 > dbcheck -r -s | $DIALOG --gauge "\n  Checking DB 2/2" 7 70 
 > 2>/dev/null
 > [...]
 > 
 > here is what it gives in /var/log/messages:
 > Dec 14 13:26:46 camtrace13 dhclient: New Subnet Mask (wlan0): 255.255.255.0
 > Dec 14 13:26:46 camtrace13 dhclient: New Broadcast Address (wlan0):
 > 192.168.0.255
 > Dec 14 13:26:46 camtrace13 dhclient: New Routers (wlan0): 192.33.160.111
 > Dec 14 13:26:47 camtrace13 kernel: m  ^[[36m^[[44m^[[K^[[16;6H^[[1K
 > ^[[30m^[[40m^[[70X^[[77`^[[36m^[[44m^[[K^[[13;9H^[[39;49m^[[m
 > Dec 14 13:26:48 camtrace13 kernel: m  ^[[36m^[[44m^[[K^[[16;6H^[[1K
 > ^[[30m^[[40m^[[70X^[[77`^[[36m^[[44m^[[K^[[13;9H^[[39;49m^[[m

I don't know why those two dialog lines are sent to /var/log/messages; 
perhaps they indicate some error, only those being logged with *.notice?

[..]

 > and here is what I can read in /var/log/console.log:
 > Dec 14 13:26:43 camtrace13 kernel: Starting apache.
 > Dec 14 13:26:46 camtrace13 kernel: Starting pgsql.

If you view these scripts you'll see that they don't themselves write to 
stdout .. it's the rc system logging these.

 > Dec 14 13:26:47 camtrace13 kernel: ^[[m
 > Dec 14 13:26:47 camtrace13 kernel: ^[[39;49m^[[=1S
 > Dec 14 13:26:47 camtrace13 kernel:
 > ^[[39;49m^[[m^[[H^[[J^[[17d^[[36m^[[44m^[[1m^[[J^[[H^[[K^[[B^[[K^[[B^[[K^[[B^[[K^[[B^[[K^[[B^[[K^[[B^[[K^[[B^[[K^[[B
 > ^[[37m^[[47mÚ^[[m^[[30m^[[47m¿^[[m^[[36m^[[44m^[[1m^[[K^[[B
 > ^[[37m^[[47m³^[[m^[[30m^[[47m^[[68X^[[74`³^[[m^[[30m^[[40m^[[1m
 > ^[[36m^[[44m^[[K^[[B^[[37m^[[47m³^[[m^[[30m^[[47m   Checking DB
 > 1/2^[[20X^[[74`³^[[m^[[30m^[[40m^[[1m  ^[[36m^[[44m^[[K^[[B
[..]
 > Dec 14 13:26:48 camtrace13 kernel: Starting slim.
 > Dec 14 13:26:48 camtrace13 kernel: Starting

You'll need to rework this somehow so dialog's stdout isn't written to 
/dev/console, though that may seem necessary if you want it coming up on 
the VTY0 boot screen.  It may involve decoupling this task from running 
'inline' as a boot script somehow, or else making sure that output is 
redirected to a log or temporary file instead of directly into dialog.

 > dhclient and oss seem to dump their output in /var/log/messages, while
 > apache, postgresql and slim dump their one in /var/log/console.log
 > So... How can my rc.script write in both console and messages logs?
 > And how can I get rid of that?

dhclient's (running) output is normally logged to messages, whereas the 
'Starting' messages are output of the rc process as it launches things.

And it's only those couple of lines to messages, the rest of them to 
console.log is unsurprising and expected if they're written to stdout.

HTH a bit, Ian___
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 loader/kernel error

[Devin Teske]

On Oct 9, 2010, at 10:58 AM, Dan Nelson wrote:

> In the last episode (Oct 08), Hac Phan said:
>> I'm having trouble with a machine that was recently rebooted and will no
>> longer boot correctly.
>> 
>> The boot process hangs with the following screen:
>> Loading /boot/defaults/loader.conf
>> -
>> 
>> The cursor does not move and no other text is displayed. After about 10
>> minutes, the boot finishes (without the splash screen) and displays the
>> login prompt.  I tried to login but it timed out after 300 seconds.
> 
> That behaviour is consistent with having a serial console setup in
> /boot/loader.conf .  As soon as the loader sees "console=comconsole", it
> will switch its output and the kernel's output to com1.  If com1 doesn't
> exist, it will take a long time to boot.  When the kernel finally finishes,
> init still start a getty on the physical console, which is when you see the
> login prompt.  If you can boot your fixit CD and get the root filessytem
> mountd read/write, try commenting out that comconsole line.
> 
> Most bad loader.conf problems can be fixed by hitting space just before the
> loader starts up the kernel and unsetting the bad variable, but "comconsole"
> is one of the commands that it runs immediately, and I don't think you can
> stop the loader from parsing loader.conf.

In `/boot/loader.rc', I'm reviewing the ANS FICL (that's `Forth Inspired 
Command Language') and I see that it does indeed parse `/boot/loader.con' 
before throwing up the menu (once the menu is up, then you can escape to the 
loader prompt by selecting the appropriate numeric option -- in the new loader, 
the old loader you simply had to press space-bar during the count-down to boot).

The bread-crumbs in `/boot/loader.rc' lead us off to `/boot/loader.4th' if you 
want to know precisely how `/boot/loader.conf' is read into the environment 
(note: real work for `comconsole=blah' is done in `/boot/support.4th' in the 
chain: include_conf_files -> load_conf -> process_conf -> process_assignment -> 
set_environment_variable; and the last part of that chain reveals that the 
internal FICL word `set' is used to set an environment variable, so comconsole 
should be visible at the interactive prompt via the `show' keyword).

So, in reality, one ought to be able to do the following to deconfigure the 
comconsole setting...

1. Boot up the machine
2. Interrupt the boot loader (older FreeBSD, hit space, newer menu-based 
loader, choose the menu option to escape to the loader prompt)
3. Enter: show
4. Verify that comconsole is set (because loader.rc shows us 
`/boot/loader.conf' is loaded before the menu is thrown up)
5. Enter: unset comconsole
6. Enter: show
7. Verify that comconsole is no longer set
8. Enter: boot
NOTE: If you prefer to boot into single-user mode, enter instead: boot -s
NOTE: Boot should no longer be dumping to serial and instead you should see a 
normal boot process on the console.
9. Login and change /boot/loader.conf to remove comconsole=...

NOTE: I do realize that in /boot/loader.4th, the FICL native `boot' keyword has 
been overridden, but it doesn't appear that anything is munged in the 
environment prior to execution of the loaded kernel, so the kernel should 
inherit the environment variables just as they appear when `show' is executed 
at the loader prompt.
--
Devin

(full sig at bottom)

> 
> -- 
>   Dan Nelson
>   dnel...@allantgroup.com
> ___
> 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"

--
Cheers,
Devin Teske

-> CONTACT INFORMATION <-
Business Solutions Consultant II
FIS - fisglobal.com
510-735-5650 Mobile
510-621-2038 Office
510-621-2020 Office Fax
909-477-4578 Home/Fax
devin.te...@fisglobal.com

-> LEGAL DISCLAIMER <-
This message  contains confidential  and proprietary  information
of the sender,  and is intended only for the person(s) to whom it
is addressed. Any use, distribution, copying or disclosure by any
other person  is strictly prohibited.  If you have  received this
message in error,  please notify  the e-mail sender  immediately,
and delete the original message without making a copy.

-> END TRANSMISSION <-

___
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 loader/kernel error

[Dan Nelson]

In the last episode (Oct 08), Hac Phan said:
> I'm having trouble with a machine that was recently rebooted and will no
> longer boot correctly.
> 
> The boot process hangs with the following screen:
> Loading /boot/defaults/loader.conf
> -
> 
> The cursor does not move and no other text is displayed. After about 10
> minutes, the boot finishes (without the splash screen) and displays the
> login prompt.  I tried to login but it timed out after 300 seconds.

That behaviour is consistent with having a serial console setup in
/boot/loader.conf .  As soon as the loader sees "console=comconsole", it
will switch its output and the kernel's output to com1.  If com1 doesn't
exist, it will take a long time to boot.  When the kernel finally finishes,
init still start a getty on the physical console, which is when you see the
login prompt.  If you can boot your fixit CD and get the root filessytem
mountd read/write, try commenting out that comconsole line.

Most bad loader.conf problems can be fixed by hitting space just before the
loader starts up the kernel and unsetting the bad variable, but "comconsole"
is one of the commands that it runs immediately, and I don't think you can
stop the loader from parsing loader.conf.
 
-- 
Dan Nelson
dnel...@allantgroup.com
___
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 loader/kernel error

[Frank Shute]

On Fri, Oct 08, 2010 at 07:09:48PM -0700, Hac Phan wrote:
>
> Hi,
> 
> I'm having trouble with a machine that was recently rebooted and will no 
> longer
> boot correctly.
> 
> The boot process hangs with the following screen:
> Loading /boot/defaults/loader.conf

It sounds like there is something in /boot/loader.conf, or another
file that is sourced by /boot/defaults/loader.conf that it doesn't like.

> -
> 
> The cursor does not move and no other text is displayed. After about 10 
> minutes,
> the boot finishes (without the splash screen) and displays the login prompt. I
> tried to login but it timed out after 300 seconds.
> 
> The server was using a custom built kernel. I tried to get the GENERIC kernel
> from the livefs ISO and restore it via FIXIT console, but I realized that I
> actually don't know how to do that...
> 
> So how do I go about fixing this? Thanks in advance.
> -- 

I'd try and boot into single user mode and edit the offending file:
maybe comment out the various lines until you find the line that's
causing the problem.

I think that as you can get to a login prompt, you should be able to
boot single user and shouldn't have to bother with the CD.

Touch wood, I've never had a problem that required booting external
media to fix, so I can't help you in that department.


Regards,

-- 

 Frank

 Contact info: http://www.shute.org.uk/misc/contact.html


___
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 Drive Nomenclature and How to Figure it out

[Adam Vande More]

On Fri, Sep 3, 2010 at 10:04 AM, Martin McCormick
wrote:

>Thank you. I have never heard of gpart before so I gave
> it a try and that helps very much if the drive is already
> formatted. Most of these drives I plan to encounter will be
> formatted so this basically solves the problem but it raises a
> new question. If one does
>
> gpart list as suggested and the disk is formatted, one gets
> exactly the information necessary. I believe it is even the
> first line of output. It doesn't get better than that. If the
> disk is not corrected formatted such as might happen with
> corruption or maybe a new drive, gpart list executes silently
> and prints nothing on the output.
>
>As I said, you answered my question so many thanks. The
> new question might best be put:
>
> Okay, if nothing is there, where did gpart look to see nothing?
>

I believe gpart checks the geom sector which the last one of a particular
geom class. The sector is written anytime the geom device is added or
updated.  This applies only to geom devices which are hardcoded.  For
example, /dev/ad0 and /dev/ad0p1 would both be seperate geom classes and
have their own meta-data sector.

FWIW, the only suitable hard disk devices I know of are:

/dev/ad{0-9}
/dev/ada{0-9}
/dev/da{0-9}

If you're writing a test, I would probably grep dmesg for the presence of
one of them.  The first device appearance is probably a prime candidate for
installation target.

-- 
Adam Vande More
___
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 Drive Nomenclature and How to Figure it out

[Martin McCormick]

Adam Vande More writes:
> Would doing something like:
> 
> gpart list
> 
> help?

Thank you. I have never heard of gpart before so I gave
it a try and that helps very much if the drive is already
formatted. Most of these drives I plan to encounter will be
formatted so this basically solves the problem but it raises a
new question. If one does

gpart list as suggested and the disk is formatted, one gets
exactly the information necessary. I believe it is even the
first line of output. It doesn't get better than that. If the
disk is not corrected formatted such as might happen with
corruption or maybe a new drive, gpart list executes silently
and prints nothing on the output.

As I said, you answered my question so many thanks. The
new question might best be put:

Okay, if nothing is there, where did gpart look to see nothing?

Martin McCormick
___
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 Drive Nomenclature and How to Figure it out

[Adam Vande More]

On Fri, Sep 3, 2010 at 9:10 AM, Martin McCormick
wrote:

>I have been writing a script to build a system from a
> mfsboot startup and it is going well but I want to revisit part
> of the script that I don't think I did a very good job with.
>
>Is there an automatic way to tell which of the devices
> shown in /dev is a likely system drive? This is before anything
> is mounted.
>
>We can usually figure it out ourselves, but is there a
> way for a script to figure out automatically which character
> device could be the one we are going to put the OS on and use as
> our boot drive?
>
>I know this sounds really obvious and you can tell
> scripts not to use /dev/acdx as they are CDROM devices, but
> system drives can actually take many different names depending
> on whether they are RAIDs SCSI IDE, etc.
>
>Any good suggestions are appreciated.
>

Would doing something like:

gpart list

help?


-- 
Adam Vande More
___
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 is full after running "make installkernel" on

[Robert Huff]

Jerry McAllister writes:

>  Things change slowly.
>  I think only a short while ago the default was 256 MB or even 128
>  MB. 

I haven't checked the logs, but I think it would have been more
than a "short" while.
Consider:

huff@>> du -s /boot/kernel
225008  /boot/kernel
huff@>> du -s /lib
24704   /lib


(This is on -CURRENT amd64, though I don't think i386 would be
that much smaller.)  Never mind the contents of /etc, /temp,
possibly /root, and anything else that gets defaulted under /; 256
mbytes just don't get it.


Robert Huff

___
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 is full after running "make installkernel" on

[Jerry McAllister]

On Tue, Jul 06, 2010 at 05:02:54PM -0700, Bill Tillman wrote:

> 
> Thanks guys.
> 
> :-)
> 
> Doesn't that seem odd that the "default" partition size for root
> (512M) isn't quite big enough?

Things change slowly.
I think only a short while ago the default was 256 MB or even 128 MB.

> 
> Should I make the partition size slightly larger (on future installs)
> to eliminate this problem?

Of course, make it whatever size you need and can afford.

jerry

> 
> Ed
> 
> 
> --
>  
> I had the same problem and since my drives are large I just started making 
> all my new builds with / set for 1G. As I understand it this is not actually 
> the solution the "in the know" folks recommend. I was advised to just delete 
> kernel.old. Of course this will work but what about when you might need 
> kernel.old to get you out of a jamb or just want to keep it for nostalgia.
>  
> I think I'm finally at the point where I will stop doing make buildworlds 
> unless absolutely needed. I've been keen on doing this regularly but I really 
> should adopt the policy of if it ain't broken don't fix it.
> 
> 
>   
> ___
> 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: /boot is full after running "make installkernel" on

[Brandon Gooch]

On Wed, Jul 7, 2010 at 7:47 AM, Bruce Cran  wrote:
> On Wed, 7 Jul 2010 07:18:18 -0400
> Jerry  wrote:
>
>> I also ran out of space. I decided that a minimum of 2GB was the
>> safest choice. It would be nice if the authors changed the default
>> settings in the soon to be released 8.1 version so as to nullify this
>> phenomena.
>
> I've just committed the fix to head/-current, but considering 8.1-RC2
> has been released I'm not even going to ask for permission to get it in
> for 8.1-RELEASE - it's just too late.
>
> --
> Bruce Cran

Thanks Bruce. This is a welcome update despite not making it in to the
8.1-RELEASE.

-Brandon
___
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 is full after running "make installkernel" on

[Bruce Cran]

On Wed, 7 Jul 2010 07:18:18 -0400
Jerry  wrote:

> I also ran out of space. I decided that a minimum of 2GB was the
> safest choice. It would be nice if the authors changed the default
> settings in the soon to be released 8.1 version so as to nullify this
> phenomena.

I've just committed the fix to head/-current, but considering 8.1-RC2
has been released I'm not even going to ask for permission to get it in
for 8.1-RELEASE - it's just too late.

-- 
Bruce Cran
___
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 is full after running "make installkernel" on

[Jerry]

On Wed, 7 Jul 2010 11:13:21 +0100
Bruce Cran  articulated:


> I'd consider that bad advice: the defaults sysinstall chooses are
> currently just wrong, and you should indeed be setting / to at least
> 1GB so you don't run out of space. The 'solution' of deleting
> kernel.old or not installing symbols is just a workaround and is
> certainly less than ideal.

I also ran out of space. I decided that a minimum of 2GB was the safest
choice. It would be nice if the authors changed the default settings in
the soon to be released 8.1 version so as to nullify this phenomena.

-- 
Jerry ✌
freebsd.u...@seibercom.net

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__

The less a statesman amounts to, the more he loves the flag.


Kin Hubbard
___
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 is full after running "make installkernel" on

[Bruce Cran]

On Tue, 6 Jul 2010 17:02:54 -0700 (PDT)
Bill Tillman  wrote:

> Doesn't that seem odd that the "default" partition size for root
> (512M) isn't quite big enough?

It's not that odd: nobody has bothered to update the default partition
sizes in sysinstall for a good few years, I suspect because most
people use a custom layout and haven't noticed that the defaults are
bad. I'm going to checkin a fix in a couple of days.

> Should I make the partition size slightly larger (on future installs)
> to eliminate this problem?

Yes, you should do. I don't usually use the default partitioning
because for years I've been creating a 1GB /, 4GB /var and 1GB /tmp and
the defaults sysinstall chooses are no good.


> As I understand it this is
> not actually the solution the "in the know" folks recommend. I was
> advised to just delete kernel.old. 

I'd consider that bad advice: the defaults sysinstall chooses are
currently just wrong, and you should indeed be setting / to at least
1GB so you don't run out of space. The 'solution' of deleting
kernel.old or not installing symbols is just a workaround and is
certainly less than ideal. 

-- 
Bruce Cran
___
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 is full after running "make installkernel" on FreeBSD 8.0

[RW]

On Fri, 02 Jul 2010 16:28:29 +0100
Arthur Chance  wrote:

> I suspect whoever you were talking to probably has more of a clue
> than I do. As a quick data point, I just ran "portsnap fetch update"
> while another process did a "df /var; sleep 1" loop and /var
> increased by about 30MB at its peak. That was a week after the last
> port update. I've no idea how much space a "portsnap fetch extract"
> would take and would rather not do one right now. 

The temporary space is likely used by the "fetch" stage for
downloaded patch files. I don't think "update" or "extract" use much
storage on /var.
___
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 is full after running "make installkernel" on

[Bill Tillman]

Thanks guys.

:-)

Doesn't that seem odd that the "default" partition size for root
(512M) isn't quite big enough?

Should I make the partition size slightly larger (on future installs)
to eliminate this problem?

Ed


--
 
I had the same problem and since my drives are large I just started making all 
my new builds with / set for 1G. As I understand it this is not actually the 
solution the "in the know" folks recommend. I was advised to just delete 
kernel.old. Of course this will work but what about when you might need 
kernel.old to get you out of a jamb or just want to keep it for nostalgia.
 
I think I'm finally at the point where I will stop doing make buildworlds 
unless absolutely needed. I've been keen on doing this regularly but I really 
should adopt the policy of if it ain't broken don't fix it.


 
___
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 is full after running "make installkernel" on FreeBSD 8.0

[Arthur Chance]

On 07/02/10 15:38, Bruce Cran wrote:

On Fri, 02 Jul 2010 15:04:10 +0100
Arthur Chance  wrote:


As a matter of idle curiosity with a bit of education thrown in, why
4GB for /var? The last time I installed a new machine I made / 1GB as
I'd found out from a previous install that 512MB wasn't really
enough, and then decided to make /var bigger than the Handbook said
as well and made it 3GB. This has turned out to be total overkill:

art...@fileserver>  df -h /var
Filesystem  SizeUsed   Avail Capacity  Mounted on
/dev/ad10s1d2.9G205M2.5G 8%/var

I'm sure my use of this machine is very simple and nowhere near as
large as other people's but a leap of 4-16 times what it currently
suggests in the Handbook seems a bit excessive, especially if people
are installing onto older kit. OTOH, playing devil's advocate with
myself, disks are huge these days so why not?



I came up with that value based on discussion on IRC. I also thought
that portsnap might take up quite a bit more than it actually does. It
perhaps doesn't need updated from its current value.


I suspect whoever you were talking to probably has more of a clue than I 
do. As a quick data point, I just ran "portsnap fetch update" while 
another process did a "df /var; sleep 1" loop and /var increased by 
about 30MB at its peak. That was a week after the last port update. I've 
no idea how much space a "portsnap fetch extract" would take and would 
rather not do one right now. Similarly I've no idea how much 
freebsd-update might take.

___
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 is full after running "make installkernel" on FreeBSD 8.0

[Bruce Cran]

On Fri, 02 Jul 2010 15:04:10 +0100
Arthur Chance  wrote:

> As a matter of idle curiosity with a bit of education thrown in, why
> 4GB for /var? The last time I installed a new machine I made / 1GB as
> I'd found out from a previous install that 512MB wasn't really
> enough, and then decided to make /var bigger than the Handbook said
> as well and made it 3GB. This has turned out to be total overkill:
> 
> art...@fileserver> df -h /var
> Filesystem  SizeUsed   Avail Capacity  Mounted on
> /dev/ad10s1d2.9G205M2.5G 8%/var
> 
> I'm sure my use of this machine is very simple and nowhere near as
> large as other people's but a leap of 4-16 times what it currently
> suggests in the Handbook seems a bit excessive, especially if people
> are installing onto older kit. OTOH, playing devil's advocate with
> myself, disks are huge these days so why not?
> 

I came up with that value based on discussion on IRC. I also thought
that portsnap might take up quite a bit more than it actually does. It
perhaps doesn't need updated from its current value.

-- 
Bruce Cran
___
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 is full after running "make installkernel" on FreeBSD 8.0

[Robert Huff]

Arthur Chance writes:

>  As a matter of idle curiosity with a bit of education thrown in,
>  why 4GB for /var? The last time I installed a new machine I made
>  / 1GB as I'd found out from a previous install that 512MB wasn't
>  really enough, and then decided to make /var bigger than the
>  Handbook said as well and made it 3GB. This has turned out to be
>  total overkill:

It is my understanding space used on /var is, well, variable.
While a generic system might only use, say, 300 mbytes 99.99 per
cent of the time, the other .01 might use 5 or 10 or 20 gbytes if
available. 


Robert Huff



___
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 is full after running "make installkernel" on FreeBSD 8.0

[Arthur Chance]

On 07/02/10 13:13, Bruce Cran wrote:

I have a task on my TODO list to increase the sizes of the partitions in
sysinstall: for example / goes to 1GB, /var to 4GB. I hope to commit
the code in the next couple of weeks.


As a matter of idle curiosity with a bit of education thrown in, why 4GB 
for /var? The last time I installed a new machine I made / 1GB as I'd 
found out from a previous install that 512MB wasn't really enough, and 
then decided to make /var bigger than the Handbook said as well and made 
it 3GB. This has turned out to be total overkill:


art...@fileserver> df -h /var
Filesystem  SizeUsed   Avail Capacity  Mounted on
/dev/ad10s1d2.9G205M2.5G 8%/var

I'm sure my use of this machine is very simple and nowhere near as large 
as other people's but a leap of 4-16 times what it currently suggests in 
the Handbook seems a bit excessive, especially if people are installing 
onto older kit. OTOH, playing devil's advocate with myself, disks are 
huge these days so why not?


___
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 is full after running "make installkernel" on FreeBSD 8.0

[Jerry McAllister]

On Thu, Jul 01, 2010 at 02:29:54PM -0700, Ed Flecko wrote:

> Henrik,
> When I FIRST installed 8.0, I did create a separate /home partition.
> When I installed the kernel and starting running out of space in / , I
> thought "O.K...I'll let FreeBSD make the partition sizes IT wants to
> and see if I have the same problem, and I did.
> 
> Apparently, 512M is just, not, quite big enough so I think I'll try 1G
> to give me plenty of room.

Apparently also 64 bit systems take more room.   I didn't notice
it was a 64 bit system when I responded yesterday.
You might want to jump to 768 MB for root.

jerry

> 
> Ed
> ___
> 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: /boot is full after running "make installkernel" on FreeBSD 8.0

[Bruce Cran]

On Fri, 02 Jul 2010 08:33:45 +0100
Matthew Seaman  wrote:

> Is it time for me to start advocating "one big partition" again?
> 
> This may not be the consensus view, but I have found that for a quiet
> life and general lack of botheration it helps to create *only two*
> partitions on your hard drive:
> 
>  b: Swap -- usually 2x RAM
>  a: Everything else

This is perfect bikeshed material: people believe FreeBSD's
partitioning scheme is superior to (for example) Linux, and that by
dumping everything in a single partition we'd be dumbing it down. I
still create separate partitions through paranoia, to avoid corrupting
the entire disk if for example /usr/obj is being written to when the
power goes out. I don't know if that would happen but I've had too many
problem over the years with various filesystems that I don't trust it.
With ZFS I've gone even further and created separate filesystems
for /usr/src, /usr/ports etc. The output of 'mount' looks somewhat like
a Solaris machine now :)

I have a task on my TODO list to increase the sizes of the partitions in
sysinstall: for example / goes to 1GB, /var to 4GB. I hope to commit
the code in the next couple of weeks.

-- 
Bruce Cran
___
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 is full after running "make installkernel" on FreeBSD 8.0

[Robert Huff]

krad writes:

>  all i can say is your a brave boy 8) A 1 TB+ / slice would take
>  ages to fsck.

For "ages" being less than ten (fifteen ?) minutes on a modern
system with reasonable memory ...
... which should be necessary very rarely.  Even on my test
system, time between involuntary reboots is measured in weeks.


Robert Huff
___
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 is full after running "make installkernel" on FreeBSD 8.0

[krad]

On 2 July 2010 08:33, Matthew Seaman wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 01/07/2010 22:29:54, Ed Flecko wrote:
> > Henrik,
> > When I FIRST installed 8.0, I did create a separate /home partition.
> > When I installed the kernel and starting running out of space in / , I
> > thought "O.K...I'll let FreeBSD make the partition sizes IT wants to
> > and see if I have the same problem, and I did.
> >
> > Apparently, 512M is just, not, quite big enough so I think I'll try 1G
> > to give me plenty of room.
>
> Is it time for me to start advocating "one big partition" again?
>
> This may not be the consensus view, but I have found that for a quiet
> life and general lack of botheration it helps to create *only two*
> partitions on your hard drive:
>
> b: Swap -- usually 2x RAM
> a: Everything else
>
> Now, I've run this setup on literally hundreds of servers without
> problems.  The usual argument against doing this is "but a run-away
> process might log so much that is fills your hard drive."  This is true.
>  You might also be killed by a lightning strike the next time you leave
> your house.  Run-away logfiles are actually pretty rare, and given that
> 80GB would be considered a pretty small hard drive nowadays, and you can
> fit a standard FreeBSD install with quite a lot of extra software inside
> 10GB, you're likely to have sufficient empty space that you'ld get days
> of warning before it caused real trouble.  In which case, newsyslog(8)
> is your friend.  Cycling logs based on size and checking that every hour
> will avoid almost all trouble.  You do monitor disk space usage on your
> servers don't you?  Cacti is in ports and its pretty easy to set up, as
> are several other alternatives.
>
> Watch this list: you'll see people having trouble with too small root
> partitions with great regularity.  I don't think I've /ever/ seen anyone
> ask about dealing with a process generating huge amounts of log data.
>
> Even if you do fill up the hard drive, it's not actually guaranteed
> disaster.  FreeBSD itself will keep running just fine.  So will most web
> applications -- although you won't get any logging.  Simply delete some
> of the excess files, and the system will spring back to normal function.
>  Filling the partition certainly will crash a database, but for serious
> RDBMS setups, I generally make an exception and put the database working
> files onto their own partition[*].
>
> Nowadays too, I much prefer using ZFS -- so I have *one* zpool from
> which is allocated all of the space for the zdevs on the system.  This
> is much the best of both worlds -- you get as many filesystems as you
> can eat, but each of them can use as much of the total available space
> as it needs to.
>
>Cheers,
>
>Matthew
>
> [*] As this usually involves hardware RAID10 with plenty of cache and a
> BBU on at least 4 x 15k RPM SAS2 drives, it would generally be on a
> separate partition in any case.
>
> - --
> 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
> -BEGIN PGP SIGNATURE-
> Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkwtllkACgkQ8Mjk52CukIyTOwCeJYhR6kY6wxmP+WlNyGF/eJte
> I0wAnRuULVWsjqxFAHaL1SFFTJd2sMMW
> =T9JF
> -END PGP SIGNATURE-
> ___
> 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"
>



all i can say is your a brave boy 8) A 1 TB+ / slice would take ages to
fsck.

Of course all these issues go away with zfs
___
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 is full after running "make installkernel" on FreeBSD 8.0

[Svein Skogen (Listmail Account)]

On 02.07.2010 09:33, Matthew Seaman wrote:
> On 01/07/2010 22:29:54, Ed Flecko wrote:
>> Henrik,
>> When I FIRST installed 8.0, I did create a separate /home partition.
>> When I installed the kernel and starting running out of space in / , I
>> thought "O.K...I'll let FreeBSD make the partition sizes IT wants to
>> and see if I have the same problem, and I did.
> 
>> Apparently, 512M is just, not, quite big enough so I think I'll try 1G
>> to give me plenty of room.
> 
> Is it time for me to start advocating "one big partition" again?
> 
> This may not be the consensus view, but I have found that for a quiet
> life and general lack of botheration it helps to create *only two*
> partitions on your hard drive:
> 
>  b: Swap -- usually 2x RAM
>  a: Everything else
> 

I usually (today) set up something similar. I sysinstall FreeBSD onto a
CF card with the "one-big-root" method, then create a zpool (on
spinning-metal-storage) where I create the usr, tmp, var fs'es, tar|tar
the originals over and fix the mountpoint info on the zfs'es. Then I add
swap on a zvol (since I don't know how to properly use a kernel dump, I
don't need swap to store it).

I use this method everywhere except on VMs inside VMWare ESXi. It's been
my painful experience that zfs inside vmware machines is a bad idea.

//Svein

-- 
+---+---
  /"\   |Svein Skogen   | sv...@d80.iso100.no
  \ /   |Solberg Østli 9| PGP Key:  0xE5E76831
   X|2020 Skedsmokorset | sv...@jernhuset.no
  / \   |Norway | PGP Key:  0xCE96CE13
|   | sv...@stillbilde.net
 ascii  |   | PGP Key:  0x58CD33B6
 ribbon |System Admin   | svein-listm...@stillbilde.net
Campaign|stillbilde.net | PGP Key:  0x22D494A4
+---+---
|msn messenger: | Mobile Phone: +47 907 03 575
|sv...@jernhuset.no | RIPE handle:SS16503-RIPE
+---+---
 If you really are in a hurry, mail me at
   svein-mob...@stillbilde.net
 This mailbox goes directly to my cellphone and is checked
even when I'm not in front of my computer.

 Picture Gallery:
  https://gallery.stillbilde.net/v/svein/




signature.asc
Description: OpenPGP digital signature

Re: /boot is full after running "make installkernel" on FreeBSD 8.0

[Matthew Seaman]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 01/07/2010 22:29:54, Ed Flecko wrote:
> Henrik,
> When I FIRST installed 8.0, I did create a separate /home partition.
> When I installed the kernel and starting running out of space in / , I
> thought "O.K...I'll let FreeBSD make the partition sizes IT wants to
> and see if I have the same problem, and I did.
> 
> Apparently, 512M is just, not, quite big enough so I think I'll try 1G
> to give me plenty of room.

Is it time for me to start advocating "one big partition" again?

This may not be the consensus view, but I have found that for a quiet
life and general lack of botheration it helps to create *only two*
partitions on your hard drive:

 b: Swap -- usually 2x RAM
 a: Everything else

Now, I've run this setup on literally hundreds of servers without
problems.  The usual argument against doing this is "but a run-away
process might log so much that is fills your hard drive."  This is true.
 You might also be killed by a lightning strike the next time you leave
your house.  Run-away logfiles are actually pretty rare, and given that
80GB would be considered a pretty small hard drive nowadays, and you can
fit a standard FreeBSD install with quite a lot of extra software inside
10GB, you're likely to have sufficient empty space that you'ld get days
of warning before it caused real trouble.  In which case, newsyslog(8)
is your friend.  Cycling logs based on size and checking that every hour
will avoid almost all trouble.  You do monitor disk space usage on your
servers don't you?  Cacti is in ports and its pretty easy to set up, as
are several other alternatives.

Watch this list: you'll see people having trouble with too small root
partitions with great regularity.  I don't think I've /ever/ seen anyone
ask about dealing with a process generating huge amounts of log data.

Even if you do fill up the hard drive, it's not actually guaranteed
disaster.  FreeBSD itself will keep running just fine.  So will most web
applications -- although you won't get any logging.  Simply delete some
of the excess files, and the system will spring back to normal function.
 Filling the partition certainly will crash a database, but for serious
RDBMS setups, I generally make an exception and put the database working
files onto their own partition[*].

Nowadays too, I much prefer using ZFS -- so I have *one* zpool from
which is allocated all of the space for the zdevs on the system.  This
is much the best of both worlds -- you get as many filesystems as you
can eat, but each of them can use as much of the total available space
as it needs to.

Cheers,

Matthew

[*] As this usually involves hardware RAID10 with plenty of cache and a
BBU on at least 4 x 15k RPM SAS2 drives, it would generally be on a
separate partition in any case.

- -- 
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
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkwtllkACgkQ8Mjk52CukIyTOwCeJYhR6kY6wxmP+WlNyGF/eJte
I0wAnRuULVWsjqxFAHaL1SFFTJd2sMMW
=T9JF
-END PGP SIGNATURE-
___
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 is full after running "make installkernel" on FreeBSD 8.0

[Chip Camden]

On Jul 01 12:29, Chip Camden wrote:
> On Jul 01 12:07, Ed Flecko wrote:
> > Thanks guys.
> > 
> > :-)
> > 
> > Doesn't that seem odd that the "default" partition size for root
> > (512M) isn't quite big enough?
> > 
> > Should I make the partition size slightly larger (on future installs)
> > to eliminate this problem?
> > 
> > Ed
> > ___
> > 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"
> 
> I know *I* will.
> 
> -- 
> Sterling (Chip) Camden
> http://camdensoftware.com | http://chipstips.com | http://chipsquips.com

I've found that if you just rm /boot/kernel.old/*.symbols, you'll have
more than enough space.  Is that safe enough?


-- 
Sterling (Chip) Camden
http://camdensoftware.com | http://chipstips.com | http://chipsquips.com


pgp8OM1K20onO.pgp
Description: PGP signature

Re: /boot is full after running "make installkernel" on FreeBSD 8.0

[Robert Huff]

Henrik Hudson writes:

>  > Or just make one large partition.  Not on a server, but I don't 
>  > see much reason for using multiple partitions on a laptop.
>  
>  Multiple partitions still isn't a bad idea if you ever have to
>  fsck and even on a desktop / laptop I usually mount /tmp as
>  noexec. (note: installworld requires exec in /tmp, so you will
>  have to remount /tmp if you use that). Also, it's easier to
>  recover if you can boot single user mode and run a quick fsck on
>  / when it's small. It doesn't happen often, but when it does it's
>  easier.

1) The preferred backup method uses dump.
2) dump works on entire partitions.
2a) It makes little sense to back up 500 gbytes when all you
need to preserve is 5 gbytes.
3) If you regularly need to dump more than a single partition,
quite a few people have scripts they will probably be willing to
share.


Robert Huff





___
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 is full after running "make installkernel" on FreeBSD 8.0

[Ed Flecko]

Henrik,
When I FIRST installed 8.0, I did create a separate /home partition.
When I installed the kernel and starting running out of space in / , I
thought "O.K...I'll let FreeBSD make the partition sizes IT wants to
and see if I have the same problem, and I did.

Apparently, 512M is just, not, quite big enough so I think I'll try 1G
to give me plenty of room.

Ed
___
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 is full after running "make installkernel" on FreeBSD 8.0

[Jerry McAllister]

On Thu, Jul 01, 2010 at 12:07:50PM -0700, Ed Flecko wrote:

> Thanks guys.
> 
> :-)
> 
> Doesn't that seem odd that the "default" partition size for root
> (512M) isn't quite big enough?
> 
> Should I make the partition size slightly larger (on future installs)
> to eliminate this problem?

Many people find the default partitions inadequate for their 
needs.  It is OK to change them.   So, sure.

jerry


> 
> Ed
> ___
> 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: /boot is full after running "make installkernel" on FreeBSD 8.0

[Jerry McAllister]

On Thu, Jul 01, 2010 at 11:24:46AM -0700, Ed Flecko wrote:

> Hi folks,
> I'm running FreeBSD 8.0, and I'm trying to simple stay current with
> all security patches. It's a clean install of FreeBSD 8.0 on a 50G
> drive, and I let sysinstall select the default partition configuration
> when I did the install.
> 
> I've taken the following steps:
> 
> 
> # csup -4 /etc/stable-supfile
> # cd /usr/src
> # make buildworld
> # make buildkernel
> # make installkernel
> 
> After the make installkernel command, the / partition shows 106%
> capacity (and it started as 500M).

> 
> Here's my before and after running "make installkernel"
> 

> Before:
> 
> Filesystem SizeUsed   Avail Capacity  Mounted on
> /dev/da0s1a496M253M203M55%/
> devfs  1.0K1.0K  0B   100%/dev
> /dev/da0s1e496M 12K456M 0%/tmp
> /dev/da0s1f 44G3.0G 37G 8%/usr
> /dev/da0s1d1.9G 10M1.8G 1%/var
> 
> After:
> 
> Filesystem SizeUsed   Avail Capacity  Mounted on
> /dev/da0s1a496M485M-29M   106%/
> devfs  1.0K1.0K  0B   100%/dev
> /dev/da0s1e496M 12K456M 0%/tmp
> /dev/da0s1f 44G3.0G 37G 8%/usr
> /dev/da0s1d1.9G 10M1.8G 1%/var
> 
> # cd /
> # du -h -d2 | grep M
> 
> 2.0K  ./tmp/.XIM-unix
>  33M  ./usr/bin
>  18M  ./usr/include
>  37M  ./usr/lib
>  20M  ./usr/libexec
> 267M ./usr/local
>  20M  ./usr/sbin
>  37M  ./usr/share
> 511M ./usr/src
> 450M ./usr/ports
>  10M  ./var/db
>  10M  ./var
> 1.7M  ./etc
> 1.1M  ./bin
> 233M ./boot/kernel
> 233M ./boot/kernel.old
> 466M ./boot
> 7.4M  ./lib
> 4.3M  ./rescue
> 4.4M  ./sbin
> 
> It looks like the both kernels are eating up the entire /
> 
> Right?

They are using up about twice the space that two kernels are
using on my machine here.

> 
> What am I doing wrong? The isn't normal, is it?

Normal is probably not a very real concept.
I get along with with 384MB for my root partition and I have a couple of
kernels there.   It is running at 92% capacity so I could probably use 
some more, but shouldn't need over 512 MB,  (Tho that isn't 8.xx so
I might have to set my sights larger when I get to that).   

jerry

> 
> Thank you,
> Ed
> ___
> 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: /boot is full after running "make installkernel" on FreeBSD 8.0

[Henrik Hudson]

On Thu, 01 Jul 2010, Lowell Gilbert wrote:

> Chip Camden  writes:
> 
> > On Jul 01 12:07, Ed Flecko wrote:
> >> Thanks guys.
> >> 
> >> :-)
> >> 
> >> Doesn't that seem odd that the "default" partition size for root
> >> (512M) isn't quite big enough?
> >> 
> >> Should I make the partition size slightly larger (on future installs)
> >> to eliminate this problem?
> >> 
> >> Ed
> >
> > I know *I* will.
> 
> *Considerably* larger, I would say.  The number of different kernel
>  modules is growing all the time, and that's where the expansion is
>  mostly coming from.
> 
> Or just make one large partition.  Not on a server, but I don't see much
> reason for using multiple partitions on a laptop.

Multiple partitions still isn't a bad idea if you ever have to fsck
and even on a desktop / laptop I usually mount /tmp as noexec. (note:
installworld requires exec in /tmp, so you will have to remount /tmp
if you use that). Also, it's easier to recover if you can boot
single user mode and run a quick fsck on / when it's small. It
doesn't happen often, but when it does it's easier.

One thing I didn't see is a /home. Is your /home under /usr or /? I
have a 8-STABLE system with both kernel and kernel.old and they only
take up 520MB or so. I normally make my / 2-4GB and then mount a
separate /var (2-10GB depending), /tmp (2-10GB depending) and
/usr (15-50gb depending) and /home (the rest)  . A separate /home is very nice
if you're rebuilding or re-installing you can just not format that
partition and all your stuff will still be there. Of course, have
backups as well :)

Henrik
-- 
Henrik Hudson
li...@rhavenn.net
-
"God, root, what is difference?" Pitr; UF 

___
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 is full after running "make installkernel" on FreeBSD 8.0

[krad]

On 1 July 2010 21:12, Ed Flecko  wrote:

> Since it would be smart to have at least one known, good kernel, why
> not make the / partition maybe 1G?
>
> I know the smaller the / partition, the better the performance (since
> it's the first partition of the drive), but I can't imagine a slightly
> larger / partition would impact performance that much, do you think?
>
> Ed
> ___
> 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"
>


On ufs installs I tend to have a single 8GB partition for /, I then hang
/tmp, /var, /home, and /usr/local off it along with any other fs i need.

When doing a zfs root install I obviously dont have to specify the size.
However I still tend to put on an 8GB reservation on it.
___
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 is full after running "make installkernel" on FreeBSD 8.0

[Ed Flecko]

Since it would be smart to have at least one known, good kernel, why
not make the / partition maybe 1G?

I know the smaller the / partition, the better the performance (since
it's the first partition of the drive), but I can't imagine a slightly
larger / partition would impact performance that much, do you think?

Ed
___
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 is full after running "make installkernel" on FreeBSD 8.0

[Anders Andersson]

>
> A healthy fear, indeed.
>
> For one thing, I'd certainly rather have someone
> do "rm /boot/kernel.old/*.ko" than "rm -r /boot/kernel.old".
>
> Being even more selective is an obvious extension...
>

Why not move the old "useless" kernel to another drive. Sure if the system
kernel fails and you need the old one, there is a little bit more work, but
nothing that I can't see be solved by:
1. booting from a livecd
2. mount the /boot and /theotherpartition
3. move the kernel back and move the faulty one away
4. reboot

That saves you from deleting the entire computer/world/Internet and save the
old kernel as well. However, I have never done this myself but the theory
sounds good.
___
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 is full after running "make installkernel" on FreeBSD 8.0

[Lowell Gilbert]

Chip Camden  writes:

> On Jul 01 12:07, Ed Flecko wrote:
>> Thanks guys.
>> 
>> :-)
>> 
>> Doesn't that seem odd that the "default" partition size for root
>> (512M) isn't quite big enough?
>> 
>> Should I make the partition size slightly larger (on future installs)
>> to eliminate this problem?
>> 
>> Ed
>
> I know *I* will.

*Considerably* larger, I would say.  The number of different kernel
 modules is growing all the time, and that's where the expansion is
 mostly coming from.

Or just make one large partition.  Not on a server, but I don't see much
reason for using multiple partitions on a laptop.

___
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 is full after running "make installkernel" on FreeBSD 8.0

[Lowell Gilbert]

Chip Camden  writes:

> On Jul 01 15:10, Lowell Gilbert wrote:
>> Chip Camden  writes:
>> 
>> > I've experienced the same thing on amd64 -- the default partition size
>> > for root is too small.  Rather than going to the trouble of correcting
>> > it, I just 'rm -r /boot/kernel.old' when it fails and then redo 'make
>> > installkernel', and all seems OK.
>> 
>> That's a little dangerous, because you're deleting your last known-good
>> kernel.  I'd feel better about recommending just removing the
>> unnecessary kernel modules (which for a lot of people, is all of them).
>
> Could you expand on that?  I'd prefer a less risky option, especially
> because I always get this paralyzing fear that I'll accidentally hit
> Enter after I've typed 'rm -r /'

A healthy fear, indeed.

For one thing, I'd certainly rather have someone 
do "rm /boot/kernel.old/*.ko" than "rm -r /boot/kernel.old".

Being even more selective is an obvious extension...
___
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 is full after running "make installkernel" on FreeBSD 8.0

[Chip Camden]

On Jul 01 12:07, Ed Flecko wrote:
> Thanks guys.
> 
> :-)
> 
> Doesn't that seem odd that the "default" partition size for root
> (512M) isn't quite big enough?
> 
> Should I make the partition size slightly larger (on future installs)
> to eliminate this problem?
> 
> Ed
> ___
> 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"

I know *I* will.

-- 
Sterling (Chip) Camden
http://camdensoftware.com | http://chipstips.com | http://chipsquips.com


pgpg29YkGipfM.pgp
Description: PGP signature

Re: /boot is full after running "make installkernel" on FreeBSD 8.0

[Chip Camden]

On Jul 01 15:10, Lowell Gilbert wrote:
> Chip Camden  writes:
> 
> > I've experienced the same thing on amd64 -- the default partition size
> > for root is too small.  Rather than going to the trouble of correcting
> > it, I just 'rm -r /boot/kernel.old' when it fails and then redo 'make
> > installkernel', and all seems OK.
> 
> That's a little dangerous, because you're deleting your last known-good
> kernel.  I'd feel better about recommending just removing the
> unnecessary kernel modules (which for a lot of people, is all of them).
> ___
> 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"

Could you expand on that?  I'd prefer a less risky option, especially
because I always get this paralyzing fear that I'll accidentally hit
Enter after I've typed 'rm -r /'

-- 
Sterling (Chip) Camden
http://camdensoftware.com | http://chipstips.com | http://chipsquips.com


pgpsdgVN3XSlj.pgp
Description: PGP signature

Re: /boot is full after running "make installkernel" on FreeBSD 8.0

[James Bailie]

Try rm -r /boot/kernel.old
I bet that's the problem.
--
James Bailie
http://www.mammothcheese.ca

-Original Message-
From: Ed Flecko 
Sender: owner-freebsd-questi...@freebsd.org
Date: Thu, 1 Jul 2010 11:24:46 
To: 
Subject: /boot is full after running "make installkernel" on FreeBSD 8.0

Hi folks,
I'm running FreeBSD 8.0, and I'm trying to simple stay current with
all security patches. It's a clean install of FreeBSD 8.0 on a 50G
drive, and I let sysinstall select the default partition configuration
when I did the install.

I've taken the following steps:


# csup -4 /etc/stable-supfile
# cd /usr/src
# make buildworld
# make buildkernel
# make installkernel

After the make installkernel command, the / partition shows 106%
capacity (and it started as 500M).

Here's my before and after running "make installkernel"

Before:

Filesystem SizeUsed   Avail Capacity  Mounted on
/dev/da0s1a496M253M203M55%/
devfs  1.0K1.0K  0B   100%/dev
/dev/da0s1e496M 12K456M 0%/tmp
/dev/da0s1f 44G3.0G 37G 8%/usr
/dev/da0s1d1.9G 10M1.8G 1%/var

After:

Filesystem SizeUsed   Avail Capacity  Mounted on
/dev/da0s1a496M485M-29M   106%/
devfs  1.0K1.0K  0B   100%/dev
/dev/da0s1e496M 12K456M 0%/tmp
/dev/da0s1f 44G3.0G 37G 8%/usr
/dev/da0s1d1.9G 10M1.8G 1%/var

# cd /
# du -h -d2 | grep M

2.0K./tmp/.XIM-unix
 33M./usr/bin
 18M./usr/include
 37M./usr/lib
 20M./usr/libexec
267M ./usr/local
 20M./usr/sbin
 37M./usr/share
511M ./usr/src
450M ./usr/ports
 10M./var/db
 10M./var
1.7M./etc
1.1M./bin
233M ./boot/kernel
233M ./boot/kernel.old
466M ./boot
7.4M./lib
4.3M./rescue
4.4M./sbin

It looks like the both kernels are eating up the entire /

Right?

What am I doing wrong? The isn't normal, is it?

Thank you,
Ed
___
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: /boot is full after running "make installkernel" on FreeBSD 8.0

[Ed Flecko]

Chip,
That sounds like a smart thing to do; can you tell me more about how
to do that (or point me to a www resource; I'm happy to read more
about that).

:-)

Ed
___
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 is full after running "make installkernel" on FreeBSD 8.0

[Lowell Gilbert]

Chip Camden  writes:

> I've experienced the same thing on amd64 -- the default partition size
> for root is too small.  Rather than going to the trouble of correcting
> it, I just 'rm -r /boot/kernel.old' when it fails and then redo 'make
> installkernel', and all seems OK.

That's a little dangerous, because you're deleting your last known-good
kernel.  I'd feel better about recommending just removing the
unnecessary kernel modules (which for a lot of people, is all of them).
___
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 is full after running "make installkernel" on FreeBSD 8.0

[Ed Flecko]

Thanks guys.

:-)

Doesn't that seem odd that the "default" partition size for root
(512M) isn't quite big enough?

Should I make the partition size slightly larger (on future installs)
to eliminate this problem?

Ed
___
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 is full after running "make installkernel" on FreeBSD 8.0

[Chip Camden]

On Jul 01 11:24, Ed Flecko wrote:
> Hi folks,
> I'm running FreeBSD 8.0, and I'm trying to simple stay current with
> all security patches. It's a clean install of FreeBSD 8.0 on a 50G
> drive, and I let sysinstall select the default partition configuration
> when I did the install.
> 
> I've taken the following steps:
> 
> 
> # csup -4 /etc/stable-supfile
> # cd /usr/src
> # make buildworld
> # make buildkernel
> # make installkernel
> 
> After the make installkernel command, the / partition shows 106%
> capacity (and it started as 500M).
> 
> Here's my before and after running "make installkernel"
> 
> Before:
> 
> Filesystem SizeUsed   Avail Capacity  Mounted on
> /dev/da0s1a496M253M203M55%/
> devfs  1.0K1.0K  0B   100%/dev
> /dev/da0s1e496M 12K456M 0%/tmp
> /dev/da0s1f 44G3.0G 37G 8%/usr
> /dev/da0s1d1.9G 10M1.8G 1%/var
> 
> After:
> 
> Filesystem SizeUsed   Avail Capacity  Mounted on
> /dev/da0s1a496M485M-29M   106%/
> devfs  1.0K1.0K  0B   100%/dev
> /dev/da0s1e496M 12K456M 0%/tmp
> /dev/da0s1f 44G3.0G 37G 8%/usr
> /dev/da0s1d1.9G 10M1.8G 1%/var
> 
> # cd /
> # du -h -d2 | grep M
> 
> 2.0K  ./tmp/.XIM-unix
>  33M  ./usr/bin
>  18M  ./usr/include
>  37M  ./usr/lib
>  20M  ./usr/libexec
> 267M ./usr/local
>  20M  ./usr/sbin
>  37M  ./usr/share
> 511M ./usr/src
> 450M ./usr/ports
>  10M  ./var/db
>  10M  ./var
> 1.7M  ./etc
> 1.1M  ./bin
> 233M ./boot/kernel
> 233M ./boot/kernel.old
> 466M ./boot
> 7.4M  ./lib
> 4.3M  ./rescue
> 4.4M  ./sbin
> 
> It looks like the both kernels are eating up the entire /
> 
> Right?
> 
> What am I doing wrong? The isn't normal, is it?
> 
> Thank you,
> Ed
> ___
> 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"

I've experienced the same thing on amd64 -- the default partition size
for root is too small.  Rather than going to the trouble of correcting
it, I just 'rm -r /boot/kernel.old' when it fails and then redo 'make
installkernel', and all seems OK.

-- 
Sterling (Chip) Camden
http://camdensoftware.com | http://chipstips.com | http://chipsquips.com


pgpj8YPHIDDdA.pgp
Description: PGP signature

Re: Boot to ZFS on FreeBSD 7.3

[Dan D Niles]

On Mon, 2010-06-28 at 19:27 -0400, Glen Barber wrote:
> > Any suggestions for getting FreeBSD 7.3 to boot to ZFS?
> >
> 
> Can you try the following at the loader prompt, where you see the 
> FreeBSD boot options?
> 
> load zfs
> load opensolaris # should not be necessary, but just to be safe
> boot

FreeBSD/i386 ZFS enabled bootstrap loader, Revision 1.1
(r...@driscoll.cse.buffalo.edu, Sun Mar 21 04:11:17 UTC 2010)
\
can't load 'kernel'

Type '?' for a list of commands, 'help' for more detailed help.
OK load zfs
can't find 'zfs'
OK load opensolaris
can't find 'opensolaris'
OK _

I says that it is a ZFS enabled bootstrap loader, but it does not appear
that the root filesystem is loaded.




___
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 to ZFS on FreeBSD 7.3

[Glen Barber]

On 6/28/10 7:27 PM, Glen Barber wrote:

On 6/28/10 5:13 PM, Dan D Niles wrote:


The release notes for FreeBSD 7.3 said that it could boot to zfs. I did
not see any options for doing that via the normal install. I followed
the instructions here:

http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot

When I reboot, I get:

can't load 'kernel'

I wiped the disk and tried again to verify I didn't miss a step. Same
result.

I saw a suggestion that zfs.cache needed to be copied. I did that
during the setup, but I tried doing it again from Fixit. Same result.


You don't need this step for 7.3.


The other suggestion I saw was to do section 2 step 7 "again." That
shouldn't be necessary for 7.3, but I tried it anyway. Still seeing
"can't load 'kernel'."


I quoted the wrong sentence - you don't need _this_ step.



Any suggestions for getting FreeBSD 7.3 to boot to ZFS?



Can you try the following at the loader prompt, where you see the
FreeBSD boot options?

load zfs
load opensolaris # should not be necessary, but just to be safe
boot

Regards,




--
Glen Barber
___
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 to ZFS on FreeBSD 7.3

[Glen Barber]

On 6/28/10 5:13 PM, Dan D Niles wrote:


The release notes for FreeBSD 7.3 said that it could boot to zfs.  I did
not see any options for doing that via the normal install.  I followed
the instructions here:

http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot

When I reboot, I get:

can't load 'kernel'

I wiped the disk and tried again to verify I didn't miss a step.  Same
result.

I saw a suggestion that zfs.cache needed to be copied.  I did that
during the setup, but I tried doing it again from Fixit.  Same result.


You don't need this step for 7.3.


The other suggestion I saw was to do section 2 step 7 "again."  That
shouldn't be necessary for 7.3, but I tried it anyway.  Still seeing
"can't load 'kernel'."

Any suggestions for getting FreeBSD 7.3 to boot to ZFS?



Can you try the following at the loader prompt, where you see the 
FreeBSD boot options?


   load zfs
   load opensolaris # should not be necessary, but just to be safe
   boot

Regards,

--
Glen Barber
___
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 Debian on a RouterStation Pro

[Polytropon]

On Mon, 3 May 2010 20:58:33 -0600, Tim Judd  wrote:
> I read the magazine article title as "to everyone who wants a
> linux/unix like system, FreeBSD is the professional choice"

While "like" indicates a similarity between Linux and FreeBSD,
which is valid because similarities do exist, the heading quoted,
"FreeBSD - the professional Linux" suggests that FreeBSD is a
Linux. The relations are "is like a" vs. "is a". There are
other relations, like "is derived from" or "is an implementation
of" when putting FreeBSD and other BSDs, Linux distributions,
Solaris, and rather generic names like UNIX into relations with
each other. This shows up in a part of your quote - FreeBSD is
considered a "UNIX like system"; FreeBSD's web page states that
is is "Based on BSD UNIX (R)", but I think it's possible to say
that it is a UNIX, too, as you commonly also say about other
commerical UNIXes that have roots in (historical) BSD.

Semiotics, dear Watson. :-)



-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
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 Debian on a RouterStation Pro

[Tim Judd]

On 5/3/10, Polytropon  wrote:
> On Mon, 3 May 2010 10:34:21 -0400, Alejandro Imass  wrote:
>> Why on earth would someone put Debian and FreeBSD and "distros" in the
>> same breath, must be a joke.
>>
>> I use Debian _and_ FreeBSD extensively but I have no confusion in tha
>> FBSD is not a Linux distro.
>
> I can assure you it's not - at least not in Germany; here, some
> years ago a computer related magazine had an article with the
> title "FreeBSD - the professional Linux". :-)
>
>

Similar to "Windows NT 4.0" as a professional Windows.  "Windows 2008" vs Vista


I read the magazine article title as "to everyone who wants a
linux/unix like system, FreeBSD is the professional choice"

It's all interpreted to the reader...  however typing "Debian" when
being sent to a FreeBSD list is completely misdirected, I would have
ignored it if it wasn't for the fact that there were so many responses
to this thread.
___
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 Debian on a RouterStation Pro

[Outback Dingo]

bad enough the original post was on the OpenWRT list, then it hit the
FreeBSD list, neither of which is debian, one of which surely isnt linux,
however fortunaltey though both OpenWRT and FreeBSD are capable of running
on the RS/RS PRO

On Mon, May 3, 2010 at 2:13 PM, Alejandro Imass  wrote:

> On Mon, May 3, 2010 at 2:07 PM, Polytropon  wrote:
> > On Mon, 3 May 2010 10:34:21 -0400, Alejandro Imass  wrote:
> >> Why on earth would someone put Debian and FreeBSD and "distros" in the
> >> same breath, must be a joke.
> >>
> >> I use Debian _and_ FreeBSD extensively but I have no confusion in tha
> >> FBSD is not a Linux distro.
> >
> > I can assure you it's not - at least not in Germany; here, some
> > years ago a computer related magazine had an article with the
> > title "FreeBSD - the professional Linux". :-)
>
>  Unbeleivable. Guess they thoght it was Debian with Slackware ports ?
>
> :-D
>
> >
> >
> >
> >
> >
> > --
> > Polytropon
> > Magdeburg, Germany
> > Happy FreeBSD user since 4.0
> > Andra moi ennepe, Mousa, ...
> >
>
___
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 Debian on a RouterStation Pro

[Alejandro Imass]

On Mon, May 3, 2010 at 2:07 PM, Polytropon  wrote:
> On Mon, 3 May 2010 10:34:21 -0400, Alejandro Imass  wrote:
>> Why on earth would someone put Debian and FreeBSD and "distros" in the
>> same breath, must be a joke.
>>
>> I use Debian _and_ FreeBSD extensively but I have no confusion in tha
>> FBSD is not a Linux distro.
>
> I can assure you it's not - at least not in Germany; here, some
> years ago a computer related magazine had an article with the
> title "FreeBSD - the professional Linux". :-)

 Unbeleivable. Guess they thoght it was Debian with Slackware ports ?

:-D

>
>
>
>
>
> --
> Polytropon
> Magdeburg, Germany
> Happy FreeBSD user since 4.0
> Andra moi ennepe, Mousa, ...
>
___
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 Debian on a RouterStation Pro

[Polytropon]

On Mon, 3 May 2010 10:34:21 -0400, Alejandro Imass  wrote:
> Why on earth would someone put Debian and FreeBSD and "distros" in the
> same breath, must be a joke.
> 
> I use Debian _and_ FreeBSD extensively but I have no confusion in tha
> FBSD is not a Linux distro.

I can assure you it's not - at least not in Germany; here, some
years ago a computer related magazine had an article with the
title "FreeBSD - the professional Linux". :-)





-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
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 Debian on a RouterStation Pro

[Alejandro Imass]

On Mon, May 3, 2010 at 9:53 AM, Outback Dingo  wrote:
> why joking, FreeBSD will run on the RS

[...]

On Mon, May 3, 2010 at 10:12 AM, Jon Radel  wrote:
>
[...]
> Or maybe he was responding to the OP asking on a FreeBSD list for somebody
> to please write him a more detailed howto for booting Debian on a device.

I was in fact replying to the OP (Jozsi Vadkan). Thanks for clarifying that Jon!

Why on earth would someone put Debian and FreeBSD and "distros" in the
same breath, must be a joke.

I use Debian _and_ FreeBSD extensively but I have no confusion in tha
FBSD is not a Linux distro.

The fact that FBSD runs on the RS is irrelevant as theOP pointed to an
openwrt link which is in fact a LInux distro.
My mail was inteded as a wake-up call to give the OP the chance to
realize he'd put his foot in his mouth and say something like "ooops,
wrong list, sorry", or clarify with something like, "well I was in
fact asking if FBSD would boot on the RS but somehow failed in
explaining it".

Cheers,
Alejandro Imass


>  Especially since he put no effort into explaining what he'd tried and what
> had gone wrong.  You know, the usual stuff to show you're not
> joking.asking in the right forum, being specific, etc., etc.
>
> --
>
> --Jon Radel
> j...@radel.com
>
>
>
___
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 Debian on a RouterStation Pro

[Jon Radel]

On Mon, May 3, 2010 at 7:55 AM, Alejandro Imass  wrote:

   

On Sun, May 2, 2010 at 4:27 PM, Jozsi Vadkan
wrote:
 

Can anyone post a howto/doc, help about booting a Debian on a
RouterStation Pro?:\

https://forum.openwrt.org/viewtopic.php?pid=108415#p108415

I still didn't manage to boot from it.

Or any other "normal distro" :\

Thank you..

p.s.: a little more detailed howto:\
   

You must be joking right?

 


On 5/3/10 9:53 AM, Outback Dingo wrote:

why joking, FreeBSD will run on the RS
Or maybe he was responding to the OP asking on a FreeBSD list for 
somebody to please write him a more detailed howto for booting Debian on 
a device.  Especially since he put no effort into explaining what he'd 
tried and what had gone wrong.  You know, the usual stuff to show you're 
not joking.asking in the right forum, being specific, etc., etc.


--

--Jon Radel
j...@radel.com

Re: boot Debian on a RouterStation Pro

[Outback Dingo]

why joking, FreeBSD will run on the RS

On Mon, May 3, 2010 at 7:55 AM, Alejandro Imass  wrote:

> On Sun, May 2, 2010 at 4:27 PM, Jozsi Vadkan 
> wrote:
> > Can anyone post a howto/doc, help about booting a Debian on a
> > RouterStation Pro?:\
> >
> > https://forum.openwrt.org/viewtopic.php?pid=108415#p108415
> >
> > I still didn't manage to boot from it.
> >
> > Or any other "normal distro" :\
> >
> > Thank you..
> >
> > p.s.: a little more detailed howto:\
>
> You must be joking right?
>
> >
> > ___
> > 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"
>
___
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 Debian on a RouterStation Pro

[Alejandro Imass]

On Sun, May 2, 2010 at 4:27 PM, Jozsi Vadkan  wrote:
> Can anyone post a howto/doc, help about booting a Debian on a
> RouterStation Pro?:\
>
> https://forum.openwrt.org/viewtopic.php?pid=108415#p108415
>
> I still didn't manage to boot from it.
>
> Or any other "normal distro" :\
>
> Thank you..
>
> p.s.: a little more detailed howto:\

You must be joking right?

>
> ___
> 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: boot loader too large

[Jason C. Wells]

Dan Naumov wrote:

Hey

A 64kb freebsd-boot partition should be more than plenty for what you
want to do, see my setup at: http://freebsd.pastebin.com/QS6MnNKc
  


Interesting.  I read somewhere that the boot partition should not be too 
large as the entire partition is loaded into memory.  I re-partitioned 
my drive to create a 64KiB freebsd-boot partition and I no longer get 
the error.  It would appear that there is an undocumented maximum size 
to the freebsd-boot partition.  In my case, a 1MiB boot partition was 
too large.


Now I need to teach gptboot in ad4p1 how to find my root partition in 
ad4p4 without manual intervention.  Is there a GPT equivalent to boot0cfg?


gptboot currently attempts to boot:

   0:ad(0p2)/boot/kernel/kernel

I'd like it to boot:

   0:ad(4p4)/boot/loader

How does the boot process discover the partition in which the gptboot 
loader resides?


And GPT is pretty damn slick.  Nice work FreeBSD hackers.


Thanks,
Jason C. Wells
___
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 loader too large

[Dan Naumov]

Hey

A 64kb freebsd-boot partition should be more than plenty for what you
want to do, see my setup at: http://freebsd.pastebin.com/QS6MnNKc

If you want to setup a ZFS boot/root configuration and make your life
easier, just use the installation script provided by the guy who wrote
ManageBE: 
http://anonsvn.h3q.com/projects/freebsd-patches/browser/manageBE/create-zfsboot-gpt_livecd.sh

- Sincerely,
Dan Naumov
___
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 loaders and USB devices

[Aiza]

Date: Thu, 25 Feb 2010 07:54:00 +0800
From: Aiza 
Subject: boot loaders and USB devices

My PC does not have the BIOS option to boot from USB.

I use an USB cabled external hard drive for taking backups. It has 
FreeBSD installed on it which I want to boot from so the motherboard 
cabled hard drive file systems are un-mounted during the dump. This USB 
drive will only be attached to do backups.


I also have a USB stick containing a Freebsd install used to clone 
itself to the motherboard cabled hard drive.


Since the BIOS will only boot from the motherboard cabled hard drive can 
I install a boot loader to gain boot access to my seldom connected USB 
devices?


I reviewed the grub port but with no joy.

What do you recommend?



Robert Bonomi wrote:
I think the standard FreeBSD loader should do this -- I haven't personally
tested, however.  You should get a menu from the boot loader asking which
partition you want to boot from.  with F5 (I think it is) being 'second disk".
hit F5, and you get the 'which boot partition' menu again.  Pick F1 for the
first partition on the USB drive, and you should be in business.   (obviously
the '2nd disk' choice is going to show up _only_ if the boot loader detects
the drive at power-up.  I don't think it relies on the BIOS for this check,
but has basic USB support built-in.

Several _other_ possible approaches:

if you can boot from CD, you could boot the 'live' cd, and then specify
that the running filesystems are on the USB device

Might be able to do the same from a carefully constructed floppy image.

A -really- 'dirty tricks'  alternative is to have an alternate /etc/fstab
on the 'motherboard-cabled' HDD.  One that specifies that '/' and everything
else are on the usb-cabled drive.  


swap the fstab files, and boot 'as normal'.  It will come up with everything
running of the USB drive.`

Do the backup, swap the fstab file back to the 'production' one, and reboot.
voila!  back to the normal drive.

One more posswibility -- build a custom kernel with the 'root' device 'hard-
wired' in as the USB drive.  Interrupt the boot sequence, and specify this
alternate kernel by name.



I had though the boot0cfg was not USB aware so never tested it. But now 
I have tested and I was right.


With the bootable USB stick flash drive plugged in I powered on the PC. 
I can see the PC bios post messages roll by and I see that the bios have 
added msg saying USB flash memory device and the pri-master ata device 
as available.


The FreeBSD boot0cfg manager comes up with only f1 and f6 options. 
Pressing f5 has no effect. To me this means that the boot0cfg manager is 
not USB aware. Have to remember that boot0cfg was written way before 
there was such a thing as USB anythings.

___
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 from FD and DR-DOS prompt comes up while installing FreeBSD?

[Fbsd1]

Paul Shi wrote:

Dear Everyone,

I am working my way t setup a FTP server on FreeBSD however I got stuck at
the very first stage - installation of FreeBSD 8.0.

I downloaded FreeBSD 8.0-RELEASE-i386-dvd1.iso from FreeBSD.org and burned
it with NERO to a DVD-RW disc. After that, I insert the DVD disc and boot
from CDROM as I have chose the CDROM to be first one in boot order. However,
system starts booting from FD, invokes some Caldera DR-DOS and goes to
command prompt [DR-DOS] A:\>

I am totally confused and cannot find any answer in FreeBSD handbook. I will
greatly appreciate your help if anyone of you has experience with this weird
problem. Thank you very much and Happy New Year!

Your sincerely,
Paul Shi
Electronic and Communication Engineering Senior
Department of Electrical and Electronic Engineering
University of Hong Kong
___
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"




You did not burn the iso file to cd correctly. Here is link to old post 
 containing details instructions for using nero to burn iso file.


http://article.gmane.org/gmane.os.freebsd.questions/100238/match=nero+iso


___
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 from FD and DR-DOS prompt comes up while installing FreeBSD?

[Chris Whitehouse]

Warren Block wrote:

On Sat, 2 Jan 2010, Paul Shi wrote:

I am working my way t setup a FTP server on FreeBSD however I got 
stuck at

the very first stage - installation of FreeBSD 8.0.

I downloaded FreeBSD 8.0-RELEASE-i386-dvd1.iso from FreeBSD.org and 
burned

it with NERO to a DVD-RW disc. After that, I insert the DVD disc and boot
from CDROM as I have chose the CDROM to be first one in boot order. 
However,

system starts booting from FD, invokes some Caldera DR-DOS and goes to
command prompt [DR-DOS] A:\>

I am totally confused and cannot find any answer in FreeBSD handbook. 
I will
greatly appreciate your help if anyone of you has experience with this 
weird

problem. Thank you very much and Happy New Year!


Nero seems to have "helped" you by making a bootable CD with a copy of 
the FreeBSD ISO file on it.  The A: disk is actually a simulated floppy 
on the CD.


That's not going to work.  Make a new CD.  Back in Windows, you might be 
able to right-click the original ISO file and get a "Burn a CD" option. 
Otherwise, you'll have to run the program and tell it to make the ISO 
into a CD, not make a CD with the ISO on it as a file.


-Warren Block * Rapid City, South Dakota USA


In Nero version 6 it's Recorder / Burn Image and just before you click 
Burn you have to select whether you are writing a CD or a DVD.


Chris



___
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"