uname -a output does not change after kernel upgrade
freebsd-questions
freebsd-questions at it-solutions.lv
Sat May 21 23:54:22 PDT 2005
Used the default email when sending this message
and therefore it did not reached questions at freebsd.org.
-------- Original Message --------
Subject: Re: uname -a output does not change after kernel upgrade
Date: Sun, 22 May 2005 00:08:45 +0300
From: Jurgis <***@it-solutions.lv>
To: Daniel Gerzo <danger at rulez.sk>
CC: questions at freebsd.org
References: <428F80CF.1020509 at it-solutions.lv> <216446879.20050521210609 at rulez.sk>
<428F9427.90402 at it-solutions.lv> <745032946.20050521223345 at rulez.sk>
Daniel Gerzo wrote:
>>How can I now which kernel is loaded?
> sysctl -a | grep kernel
>
OK, I have new userland and old kernel.
Those command proves that.
# sysctl -a | grep kernel
kern.bootfile: /boot/kernel/kernel
kern.module_path: /boot/kernel;/boot/modules
# sysctl -a | grep kern.version
kern.version: FreeBSD 5.3-RELEASE #1: Fri Apr 29 23:04:18 EEST 2005
>
>>I remembered that I had created /boot.config file
>>with following content, but now when I checked it,
>>ir was not there.
>
>
>>--- cat /boot.config ---
>>1:ad(6,a)/boot/loader
>
>
> this doesn't have anything with kernel config I think.
> actually, I know only one way how to implicitly set the kernel boot
> file. One can do so by adding line
>
> kernel="path/to/kernel"
>
> into /boot/loader.conf
I have to sata disks ad4 and ad6 and I created /boot.config to boot from
ad6 instedad of ad4. BTW I'm not quite sure about those parameters
in that string "1:ad(6,a)/boot/loader".
>>Is it better that I start new conversation with new Subject
>>and describe how I got all this mess?
>
>
> That's up to you. Personally I don't think it is needed. You should
> firstly try to build a new kernel AND install it. If you are using
> your own kernel config file, you should add KERNCONF=CONFIGNAME to the
> make (build|install)kernel command.
I have built and installed the new kernel.
I added KERNCONF=CONFIGNAME to /etc/make.conf.
There is new kernel and modules in
# ls -la /boot/kernel/kernel
-r-xr-xr-x 1 root wheel 3328239 May 21 18:45 /boot/kernel/kernel
Here is some file information and gmirror configuration:
-----
# df
Filesystem 1K-blocks Used Avail Capacity Mounted on
/dev/mirror/gm0s1a 253734 54960 178476 24% /
devfs 1 1 0 100% /dev
/dev/mirror/gm0s1d 253678 58 233326 0% /tmp
/dev/mirror/gm0s1f 135891276 1911080 123108894 2% /usr
/dev/mirror/gm0s1e 50777034 63142 46651730 0% /var
# gmirror list
Geom name: gm0s1
State: DEGRADED
Components: 2
Balance: round-robin
Slice: 4096
Flags: NONE
SyncID: 5
ID: 4196295632
Providers:
1. Name: mirror/gm0s1
Mediasize: 200046518272 (186G)
Sectorsize: 512
Mode: r4w4e1
Consumers:
1. Name: ad6s1
Mediasize: 200046518784 (186G)
Sectorsize: 512
Mode: r4w4e2
State: ACTIVE
Priority: 0
Flags: DIRTY
SyncID: 5
ID: 3302562170
# gmirror status
Name Status Components
mirror/gm0s1 DEGRADED ad6s1
-----
--- And a bit from dmesg ---
ad4: 190782MB <ST3200826AS/3.01> [387621/16/63] at ata2-master SATA150
ad6: 190782MB <ST3200826AS/3.01> [387621/16/63] at ata3-master SATA150
GEOM_MIRROR[2]: Tasting fd0.
GEOM_MIRROR[2]: Tasting ad4.
GEOM_MIRROR[2]: Tasting ad6.
GEOM_MIRROR[2]: Tasting ad4s1.
magic: GEOM::MIRROR
version: 1
name: gm0s1
mid: 4196295632
did: 3946315095
all: 2
syncid: 3
priority: 0
slice: 4096
balance: round-robin
mediasize: 200046518272
sectorsize: 512
syncoffset: 0
mflags: NONE
dflags: NONE
hcprovider:
MD5 hash: 4efc7c98de71a4d10b891fd4bc4e2c80
GEOM_MIRROR[1]: Creating device gm0s1 (id=4196295632).
GEOM_MIRROR[0]: Device gm0s1 created (id=4196295632).
GEOM_MIRROR[1]: Adding disk ad4s1 to gm0s1.
GEOM_MIRROR[2]: Adding disk ad4s1.
GEOM_MIRROR[2]: Disk ad4s1 connected.
GEOM_MIRROR[1]: Disk ad4s1 state changed from NONE to NEW (device gm0s1).
GEOM_MIRROR[0]: Device gm0s1: provider ad4s1 detected.
GEOM_MIRROR[2]: Tasting ad6s1.
magic: GEOM::MIRROR
version: 1
name: gm0s1
mid: 4196295632
did: 3302562170
all: 2
syncid: 5
priority: 0
slice: 4096
balance: round-robin
mediasize: 200046518272
sectorsize: 512
syncoffset: 0
mflags: NONE
dflags: NONE
hcprovider:
MD5 hash: 9be4ddc54abbe5e0221f020517cac964
GEOM_MIRROR[1]: Adding disk ad6s1 to gm0s1.
GEOM_MIRROR[2]: Adding disk ad6s1.
GEOM_MIRROR[2]: Disk ad6s1 connected.
GEOM_MIRROR[1]: Disk ad6s1 state changed from NONE to NEW (device gm0s1).
GEOM_MIRROR[0]: Device gm0s1: provider ad6s1 detected.
GEOM_MIRROR[1]: Device gm0s1 state changed from STARTING to RUNNING.
GEOM_MIRROR[1]: Disk ad6s1 state changed from NEW to ACTIVE (device gm0s1).
GEOM_MIRROR[2]: Access ad6s1 r0w1e1 = 0
GEOM_MIRROR[2]: Tasting ad4s1a.
GEOM_MIRROR[2]: Access ad6s1 r0w-1e-1 = 0
GEOM_MIRROR[2]: Metadata on ad6s1 updated.
GEOM_MIRROR[0]: Device gm0s1: provider ad6s1 activated.
GEOM_MIRROR[1]: Disk ad4s1 state changed from NEW to SYNCHRONIZING (device gm0s1).
GEOM_MIRROR[0]: Device gm0s1: provider mirror/gm0s1 launched.
GEOM_MIRROR[0]: Device gm0s1: rebuilding provider ad4s1.
GEOM_MIRROR[2]: Access ad4s1 r0w1e1 = 1
GEOM_MIRROR[1]: Disk ad4s1 state changed from SYNCHRONIZING to DISCONNECTED (device gm0s1).
GEOM_MIRROR[0]: Device gm0s1: provider ad4s1 disconnected.
GEOM_MIRROR[2]: Disk ad4s1 disconnected.
GEOM_MIRROR[2]: Consumer ad4s1 destroyed.
GEOM_MIRROR[2]: Tasting ad4s1c.
GEOM_MIRROR[2]: Tasting ad4s1d.
GEOM_MIRROR[2]: Tasting ad4s1e.
GEOM_MIRROR[2]: Tasting ad4s1f.
GEOM_MIRROR[2]: Tasting ad6s1a.
GEOM_MIRROR[2]: Tasting ad6s1c.
GEOM_MIRROR[2]: Tasting ad6s1d.
GEOM_MIRROR[2]: Tasting ad6s1e.
GEOM_MIRROR[2]: Tasting ad6s1f.
GEOM_MIRROR[2]: Tasting ad6.
GEOM_MIRROR[2]: Access request for mirror/gm0s1: r1w0e0.
GEOM_MIRROR[2]: Access ad6s1 r1w0e1 = 0
GEOM_MIRROR[2]: Access request for mirror/gm0s1: r-1w0e0.
GEOM_MIRROR[2]: Access ad6s1 r-1w0e-1 = 0
GEOM_MIRROR[2]: Access request for mirror/gm0s1: r1w0e0.
GEOM_MIRROR[2]: Access ad6s1 r1w0e1 = 0
-----
The old kernel could be on ad4s1.
I first wanted to solve the gmirror problem but when I
could not I upgraded to 5.4-STABLE hoping that it
could change the picture.
What should I do now?
Thank you in advance for your time!
Jurgis
More information about the freebsd-questions
mailing list