Re: Problems installing FreeBSD 7.0

On 2008-Dec-24 17:29:05 +0100, Jack Raats wrote: >Main problem is: >ad0: FreeBSD check1 failed This is produced when the ATA subsystem is trying to read RAID metadata off the disk and just means it failed to find any. It's not an error. Can you post more context please. -- Peter Jeremy Please

Re: Problems installing FreeBSD 7.0

On 2008-Dec-23 20:32:38 +0100, Jack Raats wrote: >> Can you try to paste exactly what was on the screen before the "freeze" >> for >> both 6.4 and 7.0? > >How can I do this if the systeem freezes??? Take a photo and put it up somewhere (http://imagebin.ca/ if nowhere else). If scroll lock still

Re: process stuck in vmopar

2008/12/24 pluknet : > 2008/12/24 pluknet : >> 2008/12/24 pluknet : >>> Server version: Apache/2.2.11 (Unix) built from sources. >>> >>> After issuing kill -9 process stuck in vmopar state forever. >>> aaa301 2313 0.0 0.0 0 8 ?? DE3:10PM 0:00.01 >>> /home/aaa301/myb vmopar >>

Re: Problems installing FreeBSD 7.0

From: "SDH Admin" How can I do this if the systeem freezes??? Good old fashioned pen + paper (as long as it's not too long). Never fails. Main problem is: ad0: FreeBSD check1 failed I googled but didn't find any solution. Does anyone have a clue where to find the solution? Jack __

Re: process stuck in vmopar

2008/12/24 pluknet : > 2008/12/24 pluknet : >> Server version: Apache/2.2.11 (Unix) built from sources. >> >> After issuing kill -9 process stuck in vmopar state forever. >> aaa301 2313 0.0 0.0 0 8 ?? DE3:10PM 0:00.01 >> /home/aaa301/myb vmopar >> >> System: FreeBSD 6.2 i386.

can't disable hyperthreading on 7.1

Hi I have several computers with 2 xeon processors with hyperthreading under FreeBSD 7.1-RC2 and in any case can not turn off hyperthreading: [...@vmat ~]$ cat /boot/loader.conf machdep.hyperthreading_allowed="0" machdep.hlt_logical_cpus="1" [...@vmat ~]$ sysctl machdep.hyperthreading_allowed m

Re: process stuck in vmopar

2008/12/24 pluknet : > Server version: Apache/2.2.11 (Unix) built from sources. > > After issuing kill -9 process stuck in vmopar state forever. > aaa301 2313 0.0 0.0 0 8 ?? DE3:10PM 0:00.01 > /home/aaa301/myb vmopar > > System: FreeBSD 6.2 i386. > One important note. Kernel

process stuck in vmopar

Server version: Apache/2.2.11 (Unix) built from sources. After issuing kill -9 process stuck in vmopar state forever. aaa301 2313 0.0 0.0 0 8 ?? DE3:10PM 0:00.01 /home/aaa301/myb vmopar System: FreeBSD 6.2 i386. Any hints? -- wbr, pluknet