Gigabyte GA-MA74GM-S2H - FreeBSD - 2010 archive
back to main FreeBSD page for this machine.
2010 archive.
2010-10-29: I upgraded to FreeBSD 8.1-stable, using csup. dmesg output: normal, verbose. Before rebooting I tried to upgrade the boot blocks:
gpart bootcode -p /boot/gptzfsboot -i 1 ad4 gpart bootcode -p /boot/gptzfsboot -i 1 ad4
no feedback from the commands, not sure if they had any effect. After booting, I upgraded the root pool:
root@kg-f2# zpool upgrade zroot This system is currently running ZFS pool version 15. Successfully upgraded 'zroot' from version 14 to version 15 If you boot from pool 'zroot', don't forget to update boot code. Assuming you use GPT partitioning and da0 is your boot disk the following command will do it: gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 da0 Aha, now lets see if the updating the boot blocks works: root@kg-f2# gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ad4 bootcode written to ad4 root@kg-f2# gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ad6 bootcode written to ad6 Yep, there it is. Upgrading the second pool now: root@kg-f2# zpool upgrade storage This system is currently running ZFS pool version 15. Successfully upgraded 'storage' from version 14 to version 15
Ok. Now a reboot to see if the boot blocks work. Yes, it does work. Relief. Now, the file systems needs to be upgraded:
root@kg-f2# zfs upgrade This system is currently running ZFS filesystem version 4. The following filesystems are out of date, and can be upgraded. After being upgraded, these filesystems (and any 'zfs send' streams generated from subsequent snapshots) will no longer be accessible by older software versions. VER FILESYSTEM --- ------------ 3 storage 3 zroot 3 zroot/tmp 3 zroot/usr 3 zroot/usr/home 3 zroot/usr/ports 3 zroot/usr/ports/distfiles 3 zroot/usr/ports/packages 3 zroot/usr/src 3 zroot/var 3 zroot/var/crash 3 zroot/var/db 3 zroot/var/db/pkg 3 zroot/var/empty 3 zroot/var/log 3 zroot/var/mail 3 zroot/var/run 3 zroot/var/tmp root@kg-f2#
Ok, let's see.
root@kg-f2# zfs upgrade -r zroot 17 filesystems upgraded
That was zroot, and it leaves storage behind:
root@kg-f2# zfs upgrade This system is currently running ZFS filesystem version 4. The following filesystems are out of date, and can be upgraded. After being upgraded, these filesystems (and any 'zfs send' streams generated from subsequent snapshots) will no longer be accessible by older software versions. VER FILESYSTEM --- ------------ 3 storage Better upgrade that too: root@kg-f2# zfs upgrade storage 1 filesystems upgraded And now everything is up to date: root@kg-f2# zfs upgrade This system is currently running ZFS filesystem version 4. All filesystems are formatted with the current version.
Nice.
2010-03-13: the Slim USB 2.0 to PS/2 Adapter Dongle (sku 1440) is detected but doesn't seem to work on this machine:
ugen0.2: <GASIA> at usbus0 ukbd0: <GASIA PS2toUSB Adapter, class 0/0, rev 1.10/2.80, addr 2> on usbus0 kbd2 at ukbd0 ums0: <GASIA PS2toUSB Adapter, class 0/0, rev 1.10/2.80, addr 2> on usbus0 ums0: 5 buttons and [XYZ] coordinates ID=1
Strange.
2010-03-05: I upgrade to latest FreeBSD 8.0-stable, using csup. dmesg output: normal, verbose.
2010-02-21: ntpd - the previous change wasn't enough to fix ntpd. Here is what worked (found after a long, helpful thread on the -stable mailinglist):
root@kg-f2# sysctl machdep.acpi_timer_freq=3570847 machdep.acpi_timer_freq: 3577045 -> 3570847 root@kg-f2# /etc/rc.d/ntpd stop Stopping ntpd. root@kg-f2# rm /var/db/ntpd.drift root@kg-f2# /etc/rc.d/ntpd start Starting ntpd.
And also putting the change to machdep.acpi_timer_freq into /etc/sysctl.conf.
2010-02-12: ntpd - I am trying this suggestion from the freebsd-stable mailing list:
root@kg-f2# /etc/rc.d/ntpd stop root@kg-f2# rm /var/db/ntpd.drift root@kg-f2# sysctl kern.timecounter.hardware=ACPI-safe kern.timecounter.hardware: HPET -> ACPI-safe root@kg-f2# /etc/rc.d/ntpd start
Hopefully that helps.
2010-02-11: the machine has trouble keeping time (or ntpd has). I see lines like this in /var/log/messages:
Feb 7 12:05:54 kg-f2 ntpd[909]: ntpd 4.2.4p5-a (1) Feb 7 12:11:16 kg-f2 ntpd[910]: time reset +1.020413 s Feb 7 12:11:16 kg-f2 ntpd[910]: kernel time sync status change 2001 Feb 7 12:26:26 kg-f2 ntpd[910]: time reset +2.277793 s Feb 7 12:41:29 kg-f2 ntpd[910]: time reset +2.260229 s Feb 7 12:57:02 kg-f2 ntpd[910]: time reset +2.332972 s Feb 7 13:21:24 kg-f2 ntpd[910]: time reset +3.659869 s Feb 7 13:37:01 kg-f2 ntpd[910]: time reset +2.343230 s Feb 7 13:52:24 kg-f2 ntpd[910]: time reset +2.310659 s Feb 7 14:07:29 kg-f2 ntpd[910]: time reset +2.265705 s Feb 7 14:23:03 kg-f2 ntpd[910]: time reset +2.335868 s Feb 7 14:39:06 kg-f2 ntpd[910]: time reset +2.411116 s Feb 7 14:54:32 kg-f2 ntpd[910]: time reset +2.318222 s Feb 7 15:09:55 kg-f2 ntpd[910]: time reset +2.308120 s Feb 7 15:25:49 kg-f2 ntpd[910]: time reset +2.388391 s Feb 7 15:40:54 kg-f2 ntpd[910]: time reset +2.265464 s Feb 7 15:55:57 kg-f2 ntpd[910]: time reset +2.257952 s Feb 7 16:11:45 kg-f2 ntpd[910]: time reset +2.373325 s
Further investigation shows this:
root@kg-f2# sysctl kern.timecounter kern.timecounter.tick: 1 kern.timecounter.choice: TSC(-100) HPET(900) ACPI-safe(850) i8254(0) dummy(-1000000) kern.timecounter.hardware: HPET kern.timecounter.stepwarnings: 0 kern.timecounter.tc.i8254.mask: 65535 kern.timecounter.tc.i8254.counter: 52444 kern.timecounter.tc.i8254.frequency: 1193182 kern.timecounter.tc.i8254.quality: 0 kern.timecounter.tc.ACPI-safe.mask: 4294967295 kern.timecounter.tc.ACPI-safe.counter: 3252982815 kern.timecounter.tc.ACPI-safe.frequency: 3579545 kern.timecounter.tc.ACPI-safe.quality: 850 kern.timecounter.tc.HPET.mask: 4294967295 kern.timecounter.tc.HPET.counter: 3443625641 kern.timecounter.tc.HPET.frequency: 14318180 kern.timecounter.tc.HPET.quality: 900 kern.timecounter.tc.TSC.mask: 4294967295 kern.timecounter.tc.TSC.counter: 1276479615 kern.timecounter.tc.TSC.frequency: 2819782573 kern.timecounter.tc.TSC.quality: -100 kern.timecounter.smp_tsc: 0 kern.timecounter.invariant_tsc: 1
for some reason, the HPET timecounter isn't very accurate.
2010-01-31: I upgraded to latest FreeBSD 8.0-stable, using csup. dmesg output: normal, verbose (part 1, part 2).
2010-01-31: Today the server panic'ed - twice.I could ping it, but the server was unresponsive both on console and via ssh. The messages on the console was:
"Sleeping thread (tid 10014, pid 0) owns a non-sleepable lock" "panic: sleeping thread" "cpuid = 1"
I didn't record the message for the second panic, so I don't remember if tid and pid where the same. Otherwise, the message was the same.
2010-01-30: after the upgrade, dmesg shows this on boot:
root@kg-f2# dmesg | grep ZFS ZFS NOTICE: Prefetch is disabled by default if less than 4GB of RAM is present; ZFS filesystem version 14 ZFS storage pool version 14
and zpool status zroot shows this:
root@kg-f2# zpool status zroot pool: zroot state: ONLINE status: The pool is formatted using an older on-disk format. The pool can still be used, but some features are unavailable. action: Upgrade the pool using 'zpool upgrade'. Once this is done, the pool will no longer be accessible on older software versions. scrub: none requested config: NAME STATE READ WRITE CKSUM zroot ONLINE 0 0 0 mirror ONLINE 0 0 0 gpt/disk0 ONLINE 0 0 0 gpt/disk1 ONLINE 0 0 0 errors: No known data errors
More interesting output:
root@kg-f2# zpool upgrade This system is currently running ZFS pool version 14. The following pools are out of date, and can be upgraded. After being upgraded, these pools will no longer be accessible by older software versions. VER POOL --- ------------ 13 storage 13 zroot Use 'zpool upgrade -v' for a list of available versions and their associated features.
Time to upgrade boot code and zpool. First I upgrade to boot code:
root@kg-f2# gpart bootcode -p /boot/gptzfsboot -i 1 ad4 root@kg-f2# gpart bootcode -p /boot/gptzfsboot -i 1 ad6
Then I do an zpool upgrade:
root@kg-f2# zpool upgrade zroot This system is currently running ZFS pool version 14. Successfully upgraded 'zroot' from version 13 to version 14
That's all. Now to see if the server still boots. It does, all is well. Finally, I upgrade the last pool:
root@kg-f2# zpool upgrade storage This system is currently running ZFS pool version 14. Successfully upgraded 'storage' from version 13 to version 14
And I am finished.
2010-01-15: I upgraded to latest FreeBSD 8.0-stable, using csup. No issues so far. dmesg output: normal, verbose (part 1, part 2).