Re: Multiple hard disk failures - coincidence ?
On Sat, 2004-Dec-18 02:03:09 -0500, Gary Corcoran wrote: >I've just had *THREE* Maxtor 250GB hard disk failures on my >FreeBSD 4.10 server within a matter of days. One I could >attribute to actual failure. Two made me suspicious. Three >has me wondering if this is some software problem... (or >a conspiracy (just kidding) ;-) ) Seems unlikely that faulty server software could cause a disk failure. One possibility is that your power supply is a but stressed and the supply rails are out of tolerance. The other possibility is that the drives are overheating. Higher density drives will be more sensitive to both heat and dirty power. > I suppose it >is possible these errors may have shown up more than a week or >two ago, because my windows machines, reaching them via samba, >haven't shown any problems until today, and of course with almost >750GB of data, it's not all accessed over a short time span. My approach to this is to add a line similar to dd if=/dev/ad0 of=/dev/null bs=32k for each disk into /etc/daily.local (or /etc/weekly.local or whatever). This ensures that the disks are readable on a regular basis. >P.S. I *can't* be the first person to run into this problem: >When one gets a "hard error" reported for a certain block number, >how does one find out exactly *which* file or directory is now >unreadable? With hundreds of thousands of megabytes on one disk, >a manual search is not practical - somebody must have written a >program to 'backtrack' a block number to a particular file name >- no? I know I've done this in the past but I don't recall exactly how. About all you can do is search through the inode list for the relevant blocks and then map the inode numbers to file names. -- Peter Jeremy ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Multiple hard disk failures - coincidence ?
On Sat, 18 Dec 2004, Peter Jeremy wrote: > Seems unlikely that faulty server software could cause a disk failure. > One possibility is that your power supply is a but stressed and the > supply rails are out of tolerance. The other possibility is that the > drives are overheating. Higher density drives will be more sensitive > to both heat and dirty power. A third possibility is that all disks came from the same batch (and I've been bitten by that). After all, there's a reason why 250Gb can be squeezed into such a piddly package... -- Dave ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Multiple hard disk failures - coincidence ?
On Sat, 18 Dec 2004, Gary Corcoran wrote: I've just had *THREE* Maxtor 250GB hard disk failures on my FreeBSD 4.10 server within a matter of days. One I could attribute to actual failure. Two made me suspicious. Three has me wondering if this is some software problem... (or a conspiracy (just kidding) ;-) ) Are the errors occuring at around the same block numbers? I recall a thread on -current talking about how some drives reported failures around the 133GB mark. Soren recently committed a patch to -current changing the point at which 48bit addressing is used to work around this. It may be worth investigating. Mike "Silby" Silbersack ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Multiple hard disk failures - coincidence ?
> > I've just had *THREE* Maxtor 250GB hard disk failures on my > > FreeBSD 4.10 server within a matter of days. One I could > > attribute to actual failure. Two made me suspicious. Three > > has me wondering if this is some software problem... (or > > a conspiracy (just kidding) ;-) ) > Are the errors occuring at around the same block numbers? I recall a > thread on -current talking about how some drives reported failures around > the 133GB mark. Soren recently committed a patch to -current changing the > point at which 48bit addressing is used to work around this. It may be > worth investigating. that would be different kind of error: ad0: FAILURE - READ_DMA status=51 error=10 LBA=268435455 Timestamp: 0x41C40644 [SorAlx] http://cydem.org.ua/ ridin' VN1500-B2 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Virtual CPU or not?
Hello, I would like to find a method which determines the current number of active CPUs. The problem is that neither hw.ncpu nor kern.smp.cpus contain the right value if machdep.hlt_logical_cpus is 1. Is there a better method than checking that sysctl and divide the hw.ncpu by two if set? Thanks, -- Attila Nagy e-mail: [EMAIL PROTECTED] Adopt a directory on our free software phone @work: +361 371 3536 server! http://www.fsn.hu/?f=brick cell.: +3630 306 6758 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Developing device-drivers without rebuilding the hole kernel
Hello, i want to edit the syscons driver for additional vesa-support. but i don't want to rebuild the whole kernel every time i add a few new lines or a function. is there a way to just build the syscons object file and maby a few dependencies every time and then just link it together with the rest of the kernel, which i've builded once? i hope someone can help me. thanks in advance. -- NEU +++ DSL Komplett von GMX +++ http://www.gmx.net/de/go/dsl GMX DSL-Netzanschluss + Tarif zum supergünstigen Komplett-Preis! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Developing device-drivers without rebuilding the hole kernel
On Sat, Dec 18, 2004 at 02:09:05PM +0100, "Anton Wöllert" wrote: > Hello, > > i want to edit the syscons driver for additional vesa-support. but i don't > want to rebuild the whole kernel every time i add a few new lines or a > function. is there a way to just build the syscons object file and maby a > few dependencies every time and then just link it together with the rest of > the kernel, which i've builded once? > > > i hope someone can help me. thanks in advance. make -DNOCLEAN buildkernel KERNCONF=YOURKERNEL should do the trick. -- Erik Trulsson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Strange command histories in hacked shell server
You should have a script that creates a new user when people login with 'new'. Have you forbid that script from overwriting your wheel account and re-creating root? > Hi, > > Sorry for cross posting. > > I have with FreeBSD 5.3-stable server which serves as a public shell > server. > > FreeBSD public.ub.mng.net 5.3-STABLE FreeBSD 5.3-STABLE #6: Wed Nov 24 > 15:55:36 ULAT 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PSH > i386 > > It has ssh and proftp-1.2.10 daemons. > > However it was hacked and I'm trying to analyze it and having some > difficulties. > > Machine is configured in such way that everyone can create an account > itself. > Some user dir permissions: > ... > drwxr-xr-x 2 root wheel 512 Mar 29 2004 new > drwx-- 3 tamiraad unix 512 Apr 9 2004 tamiraad > drwxr-xr-x 6 tsgan tsgan1024 Dec 16 17:51 tsgan > drwx-- 4 tugstugi unix 512 Dec 13 20:34 tugstugi > drwxr-xr-x 5 unix unix 512 Dec 13 12:37 unix > ... > User should log on as new with password new to create an account. > > Accounting is enabled and kern.securelevel is set to 2. > Only one account 'tsgan' is in wheel group and only tsgan gan become root > using su. > > Following is the some strange output from grave-robber (coroner toolkit): > ... > Dec 13 04 20:18:405 m.c -rw-rw tugstugi > smmsp/var/spool/clientmqueue/dfiBDCIeD0001529 > Dec 13 04 20:34:58 512 m.. drwx-- tugstugi unix > /home/tugstugi > Dec 13 04 20:35:57 512 ..c drwx-- tugstugi unix > /home/tugstugi > Dec 14 04 00:19:560 m.c -rw-rw-rw- tugstugi > unix /home/tugstugi/.myrc > > Dec 14 04 00:20:50 9665 m.. -rw-r--r-- tugstugi > unix /home/tsgan/.tmp/known_hosts > 9665 m.c -rw-r--r-- tugstugi > unix /home/tugstugi/.ssh/known_hosts > > Dec 15 04 19:12:21 1002 m.c -rw--- tugstugi > unix /home/tugstugi/.shrc > ... > Somehow he seems like copied /home/tugstugi/.ssh/known_hosts to > home/tsgan/.tmp/known_hosts. > I don't know why. > > > Following is lastcomm output: > ... > sshd -F tugstugi __ 0.16 secs Tue Dec 14 > 23:01 > sh - tugstugi #C:5:0x1 0.03 secs Tue Dec 14 > 23:02 > su - tugstugi #C:5:0x1 0.02 secs Tue Dec 14 > 23:38 > ... > sshd -F tugstugi __ 0.08 secs Tue Dec 14 > 22:41 > sh - tugstugi #C:5:0x1 0.02 secs Tue Dec 14 > 22:41 > who - tugstugi #C:5:0x1 0.00 secs Tue Dec 14 > 22:52 > su - tugstugi #C:5:0x1 0.02 secs Tue Dec 14 > 22:48 > sh - tsgan#C:5:0x1 0.00 secs Tue Dec 14 > 22:48 > ls - tsgan#C:5:0x1 0.00 secs Tue Dec 14 > 22:52 > su - tsgan#C:5:0x1 0.02 secs Tue Dec 14 > 22:49 > csh - root #C:5:0x1 0.03 secs Tue Dec 14 > 22:49 > ... > > In above I think he already hijacked my account and root password so he > used su to > become root. > > sshd -F tsgan__ 0.02 secs Tue Dec 14 > 00:27 > sh - tsganttyp0 0.02 secs Tue Dec 14 > 00:27 > cat - tsganttyp0 0.00 secs Tue Dec 14 > 00:28 > su - tsganttyp0 0.00 secs Tue Dec 14 > 00:28 > sleep- tsganttyp0 0.00 secs Tue Dec 14 > 00:27 > ^^ > stty - tsganttyp0 0.00 secs Tue Dec 14 > 00:27 > stty - tsganttyp0 0.00 secs Tue Dec 14 > 00:27 > ^^ > fortune - tsganttyp0 0.00 secs Tue Dec 14 > 00:27 > ... > > I don't quite understand why he used sleep and stty commands in above. > My suspect is tty hijacking. Am I right? Correct me if I'm wrong. > > sleep- tugstugi #C:5:0x2 0.00 secs Tue Dec 14 > 00:24 > stty - tugstugi #C:5:0x2 0.00 secs Tue Dec 14 > 00:24 > stty - tugstugi #C:5:0x2 0.00 secs Tue Dec 14 > 00:24 > ... > id - tugstugi #C:5:0x2 0.00 secs Tue Dec 14 > 00:24 > sleep- tugstugi #C:5:0x2 0.00 secs Tue Dec 14 > 00:24 > stty - tugstugi #C:5:0x2 0.00 secs Tue Dec 14 > 00:24 > stty - tugstugi #C:5:0x2 0.00 secs Tue Dec 14 > 00:24 > id - tugstugi #C:5:0x2 0.00 secs Tue Dec 14 > 00:24 > cat - tsgan#C:5:0x2 0.00 secs Tue Dec 14 > 00:24 > ls - tsgan#C:5:0x2 0.00 secs Tue Dec 14 > 00:24 > su - tsgan#C:5:0x2 0.02 secs Tue Dec 14 > 00:23 > sh - tugstugi #C:5:0x2 0.00 secs Tue Dec 14 > 00:23
Re: Multiple hard disk failures - coincidence ? (fwd)
Oops! Sent it to the wrong list. -- Gary Jennejohn / garyj[at]jennejohn.org gj[at]freebsd.org garyj[at]denx.de --- Forwarded Message Peter Jeremy writes: > On Sat, 2004-Dec-18 02:03:09 -0500, Gary Corcoran wrote: > >I've just had *THREE* Maxtor 250GB hard disk failures on my > >FreeBSD 4.10 server within a matter of days. One I could > >attribute to actual failure. Two made me suspicious. Three > >has me wondering if this is some software problem... (or > >a conspiracy (just kidding) ;-) ) > > Seems unlikely that faulty server software could cause a disk failure. > One possibility is that your power supply is a but stressed and the > supply rails are out of tolerance. The other possibility is that the > drives are overheating. Higher density drives will be more sensitive > to both heat and dirty power. > I'd argue for overheating. A guy I know recently had mysterious crashes on a brand-new box with a large drive, in fact, I think it was a 250Gb MAXTOR. The machine would run for a few minutes and then just spontaneously reboot. I told him it sounded like an overheating drive. After swapping out practically every bit of hardware he finally got smart and put the HD into a tray with a cooling fan. After that, all problems disappeared. And he only had *two* of these monsters in his machine! --- End of Forwarded Message ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: freebsd-hackers Digest, Vol 91, Issue 7
how did you CHANGED the limit to (800pkt/sec). this would be around 12Mb/sec traffic. On Fri, 17 Dec 2004 12:01:06 + (GMT), freebsd-hackers-request wrote > Send freebsd-hackers mailing list submissions to > [EMAIL PROTECTED] > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > or, via email, send a message with subject or body 'help' to > [EMAIL PROTECTED] > > You can reach the person managing the list at > [EMAIL PROTECTED] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of freebsd-hackers digest..." > > Today's Topics: > >1. -CURRENT problems with WCCP/high load (Gaspar Chilingarov) >2. Strange command histories in hacked shell server (Ganbold) >3. Re: -CURRENT problems with WCCP/high load (Andre Oppermann) >4. Re: brute3.tar.gz (John Von Essen) >5. Re: Multi-volume compressed dumps on DVDs (Dag-Erling Sm?rgrav) > >6. Re: duplicate CVS modules in merged CVSROOT (Dag-Erling > Sm?rgrav) >7. Re: using two keyboards at the same time (Dag-Erling Sm?rgrav) >8. Re: duplicate CVS modules in merged CVSROOT (Dmitry Morozovsky) >9. Re: duplicate CVS modules in merged CVSROOT (Roman Kurakin) > 10. Re: nfs within jail (Matt) > 11. USB video? (David Gilbert) > 12. Re: nfs within jail (David Scheidt) > > -- > > Message: 1 > Date: Thu, 16 Dec 2004 00:46:05 +0400 (AMT) > From: "Gaspar Chilingarov" <[EMAIL PROTECTED]> > Subject: -CURRENT problems with WCCP/high load > To: [EMAIL PROTECTED] > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain;charset=utf-8 > > Hello! > > machine panics under load (800pkt/sec, 600-800 kByte/sec traffik) > > I got a dual pIII 1Ghz machine with todays -current, > ipfirewall_forward option enabled, several Intel Express cards > inside. kernel is GENERIC with some stripped drivers, witness, > invariants, debugging etc disabled. compiled with -O2 -pipe, no arch > flags. > > running squid with wccp2 patch, loaded modules -- acpi, ipfw, if_gre. > > on another side is a cisco router which redirects traffic to freebsd > box using wccp2. > > after running several seconds under the load -- 7-10 seconds > computer panics with in process swi:net. > > kernel world compilation run without any failures or crashes -- so > i'm sure, that this is a software problem. > > anyone interested in kernel corefile or not ? I can provide any additional > information if anyone interested. > > please reply directly to my mail address, i'm not on list ) > > with best regards , Gaspar Chilingarov > > -- > > Message: 2 > Date: Thu, 16 Dec 2004 20:31:05 +0800 > From: Ganbold <[EMAIL PROTECTED]> > Subject: Strange command histories in hacked shell server > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="us-ascii"; format=flowed > > Hi, > > Sorry for cross posting. > > I have with FreeBSD 5.3-stable server which serves as a public shell > server. > > FreeBSD public.ub.mng.net 5.3-STABLE FreeBSD 5.3-STABLE #6: Wed Nov > 24 > 15:55:36 ULAT 2004 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PSH i386 > > It has ssh and proftp-1.2.10 daemons. > > However it was hacked and I'm trying to analyze it and having some > difficulties. > > Machine is configured in such way that everyone can create an > account itself. Some user dir permissions: ... drwxr-xr-x 2 root >wheel 512 Mar 29 2004 new drwx-- 3 tamiraad unix > 512 Apr 9 2004 tamiraad drwxr-xr-x 6 tsgan tsgan >1024 Dec 16 17:51 tsgan drwx-- 4 tugstugi unix > 512 Dec 13 20:34 tugstugi drwxr-xr-x 5 unix unix > 512 Dec 13 12:37 unix ... User should log on as new with password > new to create an account. > > Accounting is enabled and kern.securelevel is set to 2. > Only one account 'tsgan' is in wheel group and only tsgan gan become > root using su. > > Following is the some strange output from grave-robber (coroner > toolkit): ... > Dec 13 04 20:18:405 m.c -rw-rw tugstugi smmsp /var/spool/clientmqueue/dfiBDCIeD0001529 > > Dec 13 04 20:34:58 512 m.. drwx-- tugstugi unix /home/tugstugi > > Dec 13 04 20:35:57 512 ..c drwx-- tugstugi unix /home/tugstugi > Dec 14 04 00:19:560 m.c -rw-rw-rw- tugstugi > unix /home/tugstugi/.myrc > > Dec 14 04 00:20:50 9665 m.. -rw-r--r-- tugstugi > unix /home/tsgan/.tmp/known_hosts > 9665 m.c -rw-r--r-- tugstugi > unix /home/tugstugi/.ssh/known_hosts > > Dec 15 04 19:12:21 1002 m.c -rw--- tugstugi > unix /home/tugstugi/.shrc > ... > Somehow he seems like copied /home/tugstugi/.ssh/known_hosts to > home/tsgan/.tmp/known_hosts. > I don't know why. > > Following is l
Re: Developing device-drivers without rebuilding the hole kernel
> want to rebuild the whole kernel every time i add a few new lines or a If you use config(8) to configure your kernel in the "traditional way", this should come for free. See: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-building.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Multiple hard disk failures - coincidence ?
Peter Jeremy wrote: On Sat, 2004-Dec-18 02:03:09 -0500, Gary Corcoran wrote: I've just had *THREE* Maxtor 250GB hard disk failures on my FreeBSD 4.10 server within a matter of days. One I could attribute to actual failure. Two made me suspicious. Three has me wondering if this is some software problem... (or a conspiracy (just kidding) ;-) ) Seems unlikely that faulty server software could cause a disk failure. One possibility is that your power supply is a but stressed and the supply rails are out of tolerance. The other possibility is that the drives are overheating. Higher density drives will be more sensitive to both heat and dirty power. I suppose it is possible these errors may have shown up more than a week or two ago, because my windows machines, reaching them via samba, haven't shown any problems until today, and of course with almost 750GB of data, it's not all accessed over a short time span. My approach to this is to add a line similar to dd if=/dev/ad0 of=/dev/null bs=32k for each disk into /etc/daily.local (or /etc/weekly.local or whatever). This ensures that the disks are readable on a regular basis. P.S. I *can't* be the first person to run into this problem: When one gets a "hard error" reported for a certain block number, how does one find out exactly *which* file or directory is now unreadable? With hundreds of thousands of megabytes on one disk, a manual search is not practical - somebody must have written a program to 'backtrack' a block number to a particular file name - no? I generally do a tar cf /dev/lubb /mountpoint We have some tools that do teh reverse.. tell you what blocks are in a file.. It should be possible to modify fsck to do the inverse.. fsck -n --findblocks 234234,56546,2342342 I know I've done this in the past but I don't recall exactly how. About all you can do is search through the inode list for the relevant blocks and then map the inode numbers to file names. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: My freebsd dream
I swear in the name of Holy testicles of Giant panda that one day I will make my dream come true .. Men are generally idle, and ready to satisfy themselves, and intimidate the industry of others, by calling that impossible which is only difficult. Samuel Johnson (1709 - 1784) --- Chris McDermott <[EMAIL PROTECTED]> wrote: > I'm very sorry if you took this the wrong way. I > didn't mean to > trivialize your post, but when I was reading your > email I couldn't > help thinking "If I had a dream...". I thought > everyone would enjoy > the parody, so I posted it as a reply. I wasn't > trying to comment on > "your dream". > > Please accept my apologies. > > Chris McDermott > > On Thu, 2 Dec 2004 10:21:28 -0800 (PST), freeBsd > Romeo > <[EMAIL PROTECTED]> wrote: > > thanks sir, > > Mr Chris McDerMott has written a great parody, > worth > > candidate for freebsd funnies ...i am happy if I > was > > his inspiration :-)..I think now freebsd is > more > > suitable for stable production system I have > > decided to align myself to Redhat Stateless linux > > > project(http://fedora.redhat.com/projects/stateless/) > > and KDE ...My free bsd dream has died young I > > rather stick with Linux for now > > > > regards, > > gaurav > > > > > > > > --- Ivan Voras <[EMAIL PROTECTED]> wrote: > > > > > Chris McDermott wrote: > > > > I have a dream that one day this [OS] will > rise up > > > and live out the > > > > true meaning of its creed: "We hold these > truths > > > to be self-evident: > > > > > > I think this is a candidate for > > > > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/funnies.html > > > > > > :) > > > ___ > > > [EMAIL PROTECTED] mailing list > > > > > > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > > To unsubscribe, send any mail to > > > "[EMAIL PROTECTED]" > > > > > > > > > __ > > Do you Yahoo!? > > The all-new My Yahoo! - What will yours do? > > http://my.yahoo.com > > > > > > ___ > > [EMAIL PROTECTED] mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" > > > __ Do you Yahoo!? Yahoo! Mail - Helps protect you from nasty viruses. http://promotions.yahoo.com/new_mail ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
5.3 Release and Realtek
I'm running 5.3-Release amd64 on an Asus AV8 motherboard which includes
Realtek ALC850 audio chipset. I'm unable to get the system to recognize
the chipset. From the archives/man pages/manual I've :
# kldload snd_driver
kldload: can't load snd_driver: No such file or directory
Modified /boot/loader.conf to use :
sound_load="YES"
snd_driver_load="YES"
Recompiled the kernel with :
device sound
The last one resulted in /dev/sndstat showing up, but the contents show
no devices :
# cat /dev/sndstat
FreeBSD Audio Driver (newpcm)
Installed devices:
However I don't see any snd_* modules in /boot/kernel/*ko
I also noted that sys/dev/sound/pcm/ac97.c contains the following :
static const struct ac97_vendorid ac97vendorid[] = {
{ 0x414c4300, "Realtek" },
static struct ac97_codecid ac97codecid[] = {
{ 0x414c4790, 0x0f, 0, "ALC850",0 },
At this point I'm at a loss as to where to go from here, or which kernel
module would support this chipset.
Other than that this system is a screamer. This is my first experience
with 5.3, AMD, and with the 64 bit port, so far I'm really impressed. I
saw reports that the Marvell Gig Ethernet wasn't working for some folks,
but it worked fine for me. I chose this motherboard as it was the only one
of about three that supported socket 939 and had the Via K8T800 chipset, I
was concerned about the reports of problems with the nVidia nForce
chipset. I would have liked to have had PCI-X, but that's only available
today with nVidia. The Promise SATA raid controller (one of two different
brand controllers onboard) worked just fine.
http://www.asus.com/products/mb/socket939/a8v-d/overview.htm
Chris
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Developing device-drivers without rebuilding the hole kernel
"Anton Wöllert" <[EMAIL PROTECTED]> writes: > i want to edit the syscons driver for additional vesa-support. but i don't > want to rebuild the whole kernel every time i add a few new lines or a > function. is there a way to just build the syscons object file and maby a > few dependencies every time and then just link it together with the rest of > the kernel, which i've builded once? Define NO_KERNELCLEAN in /etc/make.conf. DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Multiple hard disk failures - coincidence ?
On Sat, Dec 18, 2004 at 08:17:39PM +1100, Peter Jeremy wrote: > On Sat, 2004-Dec-18 02:03:09 -0500, Gary Corcoran wrote: > > I suppose it > >is possible these errors may have shown up more than a week or > >two ago, because my windows machines, reaching them via samba, > >haven't shown any problems until today, and of course with almost > >750GB of data, it's not all accessed over a short time span. > > My approach to this is to add a line similar to > dd if=/dev/ad0 of=/dev/null bs=32k > for each disk into /etc/daily.local (or /etc/weekly.local or whatever). > This ensures that the disks are readable on a regular basis. Regular reading of every file is part of what I call backup. -- B.Walter BWCThttp://www.bwct.de [EMAIL PROTECTED] [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.3 Release and Realtek
I think I found the answer, more testing will be required, but for now I see the sound "card". The answer : # cd /usr/src/sys/modules/sound # make install # kldload snd_driver # cat /dev/sndstat FreeBSD Audio Driver (newpcm) Installed devices: pcm1: at io 0xd800 irq 22 kld snd_via8233 (5p/1r/0v channels duplex) Chris ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Multiple hard disk failures - coincidence ?
On Sat, 2004-Dec-18 20:59:11 +0100, Bernd Walter wrote: >On Sat, Dec 18, 2004 at 08:17:39PM +1100, Peter Jeremy wrote: >> My approach to this is to add a line similar to >> dd if=/dev/ad0 of=/dev/null bs=32k >> for each disk into /etc/daily.local (or /etc/weekly.local or whatever). >> This ensures that the disks are readable on a regular basis. > >Regular reading of every file is part of what I call backup. That only verifies the used part of the disk. Reading the unused parts of the disk as well helps reduce surprises. Also, in a mirrored environment, the backup does not ensure that the data can be read off both disks. (Or the parity area for RAID-5). -- Peter Jeremy ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Multiple hard disk failures - coincidence ?
On Sun, Dec 19, 2004 at 08:07:20AM +1100, Peter Jeremy wrote: > On Sat, 2004-Dec-18 20:59:11 +0100, Bernd Walter wrote: > >On Sat, Dec 18, 2004 at 08:17:39PM +1100, Peter Jeremy wrote: > >> My approach to this is to add a line similar to > >> dd if=/dev/ad0 of=/dev/null bs=32k > >> for each disk into /etc/daily.local (or /etc/weekly.local or whatever). > >> This ensures that the disks are readable on a regular basis. > > > >Regular reading of every file is part of what I call backup. > > That only verifies the used part of the disk. Reading the unused parts That's true - used parts are the only I'm interested in reading. If blocks fail that aren't used write reallocation has to do it's job. > of the disk as well helps reduce surprises. Also, in a mirrored environment, > the backup does not ensure that the data can be read off both disks. > (Or the parity area for RAID-5). Raid is another story. Just dd'ing the disks wouldn't check redundance integrity, but if you check the integrity why would you still want to check via dd too? -- B.Walter BWCThttp://www.bwct.de [EMAIL PROTECTED] [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Multiple hard disk failures - coincidence ?
Have you run the low level disk tools from Maxtor on your failed drives? One day out of the blue my 80Gig maxtors started giving out hard error failures, so I downloaded a floppy image from maxtor and used it to scan and repair my drives. I rebooted in single user mode and fscked my drives and rescued the data from lostnfound. and everything has been Aok ever since. On Sat, 2004-12-18 at 22:17 +0100, Bernd Walter wrote: > On Sun, Dec 19, 2004 at 08:07:20AM +1100, Peter Jeremy wrote: > > On Sat, 2004-Dec-18 20:59:11 +0100, Bernd Walter wrote: > > >On Sat, Dec 18, 2004 at 08:17:39PM +1100, Peter Jeremy wrote: > > >> My approach to this is to add a line similar to > > >> dd if=/dev/ad0 of=/dev/null bs=32k > > >> for each disk into /etc/daily.local (or /etc/weekly.local or whatever). > > >> This ensures that the disks are readable on a regular basis. > > > > > >Regular reading of every file is part of what I call backup. > > > > That only verifies the used part of the disk. Reading the unused parts > > That's true - used parts are the only I'm interested in reading. > If blocks fail that aren't used write reallocation has to do it's > job. > > > of the disk as well helps reduce surprises. Also, in a mirrored > > environment, > > the backup does not ensure that the data can be read off both disks. > > (Or the parity area for RAID-5). > > Raid is another story. > Just dd'ing the disks wouldn't check redundance integrity, but if you > check the integrity why would you still want to check via dd too? > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Multiple hard disk failures - coincidence ?
Ed Stover wrote: Have you run the low level disk tools from Maxtor on your failed drives? One day out of the blue my 80Gig maxtors started giving out hard error failures, so I downloaded a floppy image from maxtor and used it to scan and repair my drives. I rebooted in single user mode and fscked my drives and rescued the data from lostnfound. and everything has been Aok ever since. Thanks to everyone who responded. While I was doubtful of there being a heating problem, since my case is well cooled and there are fans blowing directly over (most of) the drives, I opened the case today and was surprised. One of the two fans in the front of the case that blow directly over five of the disks had completely *stopped*! And yes, the disks behind the one that stopped were the disks that were giving me errors, and they were extra warm (but not as toasty as my old SCSI drives in my firewall!). I don't know why/how it stopped. I nudged the fan to see if it had seized up, and it moved easily and started spinning! I moved the front panel fan control up to 'high' (from 'medium') and it started putting out a nice flow of air over the disks. It's been cooling the drives now for a few hours, and they seem back to 'normal' temp, but they are stilling showing exactly the same "hard error" sectors. Unfortunately one of the drives is having errors in sectors 96-103 (fsbn 255), so I can't even 'ls' the root directory. Are those sectors likely to be part of the superblock (which hopefully has a backup on disk?), or they probably part of the root directory? Thanks for reminding me about the Maxtor disk tools. I downloaded the latest version and am running it now to analyze the worst (no ls) drive first. Gary ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
snapshots and innds
I'm getting a strong hunch that snapshots and inn don't get along
well, presumably having something to do with inn's extensive use
of mmap().
Just for an example, my system panic()ed earlier today (different
problem) and during the reboot, I'm stuck with an fsck_ufs on wchan
"ufs" and innd on wchan "suspfs", and neither of them responding
in any way.
Unfortunately, my attempts to figure out *where* exactly everyone's
hung is being hampered by my not having any idea how to cause kgdb
to attach to the desired thread, or how to determine what thread
number (100xx) is related to what entry in ps -H.
For that matter, when I try to do a "print *(struct proc *)0x{blah}"
in kgdb for an address I got out of ps -o pid,uprocp,wchan,command,
it doesn't seem to believe that there is a struct proc.
Is there an up-to-date (i.e. covers 5.3) place that talks about
kernel debugging?
--
Steve Watt KD6GGD PP-ASEL-IA ICBM: 121W 56' 57.8" / 37N 20' 14.9"
Internet: steve @ Watt.COM Whois: SW32
Free time? There's no such thing. It just comes in varying prices...
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Virtual CPU or not?
> I would like to find a method which determines the current number of > active CPUs. > Is there a better method than checking that sysctl and divide the > hw.ncpu by two if set? You are probably looking for: min(number of '0' bits in machdep.hlt_cpus, hw.ncpu) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
