Re: drive / IDE controller questions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Guys, Thanks for the tips. I don't think the problem is with the drive itself overheating for the following reasons: First, I tried the touch-test you suggested and the drive seems warm, but definitely not hot. Second, I think the front case fan is doing a pretty good job. When I put my hand on the drive there was a pretty good breeze blowing right around the drive itself. Finally, when I start running into problems and the drive gets really bad (restarting constantly), I can't even run the WD diagnostic tool, but I can immediately swap the drive out into another system and run the diagnostic tool without any problems. Oh, and Mark, to answer your question, the WD diagnostic tool states that it allows you to test the drive, print results for last drive tested, repair errors found during the Test Drive option and write zeros to the drive. But, they obviously do something more than that because when I'm having problems and fsck won't mark the filesystem as clean, I can run WD's diagnostic tool, it will report there were no errors found, but fsck will be able to complete now. Here are potential problems that I haven't ruled out: - - general M/B problem requiring a replacement M/B - - a problem with the on-board IDE controller whether it's overheating or some other problem - - a problem with the power supply (this is stab in the dark, but I've seen rare VCore spikes with xmbon but I have no idea if this would only affect the drive) I replaced the side panel on my case for the first time in about a year. The CPU and memory temperatures are up a few degrees, but I'll leave it on for awhile anyway. I also did my best to position cables out of the way to allow good air flow. I also might try to buy a cheap IDE controller and see if that helps. Again, thanks for your suggestions. If I find a solution I'll make sure to pass it on. Joey On March 19, 2004 22:11, Mark Terribile wrote: [Jerry McAllister] [Joey Mingone] [Jerry McAllister] Another early guess might also be overheating problems. I am not sure how you would check other than trying to make it cooler. Could be.. although I have almost always had the case open and I have two case fans. The CPU temp is usually in the 40s or 50s C (not too bad for a 1.6GHz Athlon) and the memory is usually around 25C. ..but maybe I'll try pointing a fan at it. The case fans won't help much with the case open. Actually, I mean the disk overheating. They do that and they get worse at it as they age too. Also, some cases are designed to aid in the cooling and so with the case open, the airflow is either not properly directed or it doesn't get enough of a Bernouli or hydraulic effect... Of course, if it is a generic case that is probably not a consideration. Well, my tower box doesn't have any special baffles (yet) but if I operate it with both side panels off and push the CPU hard it will reset, and if I check the CPU heat sink I find it unusually warm. Without the forced circulation from either the exhaust fans above and to the rear or the inlet fan that I have on my disk drives, the CPU fan appears to draw back too much of the warm air it ejects below, hence the trend toward putting a side inlet vent on the machine -- a very bad idea, since it means that you can't place the machine up against another one. (The new BTX spec addresses this, but it looks like it introduces other problems.) I suggest that Joey check the temperature of the drive as he usually runs it, then again after running with the box closed. Mark Terribile __ Do you Yahoo!? Yahoo! Mail - More reliable, more storage, less spam http://mail.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAYGTZ0NQPEWppBZsRArKTAKDcMq+if6cDOj5/Npum1Z0V5In+sACgm8JA PQqA+I4MrAtPaxHhf2ppeqA= =dDvQ -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: drive / IDE controller questions
[Joey Mingrone] I don't think the problem is with the drive itself overheating ... ... I tried the touch-test ... and the drive seems warm, but ... not hot. ... the front case fan is doing a pretty good job. ... there was a pretty good breeze blowing right around the drive itself. Two long shots: First, have you tried a new cable to the driver? It's possible the old one is marginal. (And make sure the driver jumpers are not loose.) Second, have you checked that the drive has a good ground connection to the power supply (not just the case mounting)? It's possible to have just enough resistance that the signals will be affected. You might try another connector; if the connectors are daisy-chained, you might try the one nearest the power supply. (I had a car that came from the factory with a marginal ground on the fuel-injection computer.) Of course, if you have a scope, you can check for stray ground voltages on the case. As I recall, you already made sure that the power supply is adequate on both the +5 and +12? Mark Terribile __ Do you Yahoo!? Yahoo! Finance Tax Center - File online. File on time. http://taxes.yahoo.com/filing.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
drive / IDE controller questions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I've been having problems with my western digital drive (http://www.wdc.com/en/products/products.asp?DriveID=24) for about a year. I've posted messages about this before, but I have some new information that may be relevant. The problem started out when I would randomly hear the drive restarting. It would make a high pitch sound that would increase in pitch and last a second or two (The same sound the drive makes when you power on the system). Messages similar to the ones below would also appear in /var/log/messages: ad0: WRITE command timeout tag=0 serv=0 - resetting /kernel: ata0: resetting devices .. ata0-slave: ATA identify retries exceeded ad0: READ command timeout tag=0 serv=0 - resetting At first, these drive resets would only happen once or twice and everything would go back to normal. Eventually they would happen over and over until the system became unusable and wouldn't boot up even after running fsck in singal user mode with all the partitions unmount or mounted read only. I found a temporary solution was to run the western digital diagnostic tools and then run fsck. I would usually have a small amount of data corruption/loss but the system would be usable again. Things would be fine for a week or longer, but the problem would eventually reappear. Finally I contacted WD and they sent me a replacement drive (It was the same model, but a refurbished drive that I'm guessing was sent back by someone else). After a few tries I managed to get dd to copy the contents of the old drive to the new drive and for quite some time everything was great. But, the other day the new drive began to have the same problem as the old one. So now, I'm guessing the problem may lie with the controller on the main board (http://usa.asus.com/mb/socketa/a7v266-e/overview.htm). My main board has the optional raid controller. Would it be possible to use that controller with my current drive, or would the secondary controller be a better solution? Other notes: I've tried a few different IDE cables. I don't think it has anything to do with the OS since the resets have happened before the OS starts to boot and in the BIOS. I've included a uname -a, dmesg output and my kernel config file below. Any tips would be much appreciated. Thanks, Joey uname -a: FreeBSD *hostname* 4.9-RELEASE-p2 FreeBSD 4.9-RELEASE-p2 #0: Mon Feb 9 03:08:50 AST 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/KERNEL_CONFIG_2004-02-09 i386 dmesg: Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.9-RELEASE-p2 #0: Mon Feb 9 03:08:50 AST 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/2004-02-09 Timecounter i8254 frequency 1193182 Hz CPU: AMD Athlon(TM) XP1600+ (1410.21-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x662 Stepping = 2 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE AMD Features=0xc048MP,AMIE,DSP,3DNow! real memory = 536788992 (524208K bytes) avail memory = 518852608 (506692K bytes) Preloaded elf kernel kernel at 0xc0364000. Preloaded userconfig_script /boot/kernel.conf at 0xc036409c. Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 10 entries at 0xc00f1480 apm0: APM BIOS on motherboard apm0: found APM BIOS v1.2, connected at v1.2 npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge on motherboard pci0: PCI bus on pcib0 agp0: VIA Generic host to PCI bridge mem 0xf800-0xfbff at device 0.0 on pci0 pcib1: PCI to PCI bridge (vendor=1106 device=b099) at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: NVidia Riva Ultra Vanta TNT2 graphics accelerator at 0.0 irq 11 atapci0: Promise ATA100 controller port 0xb400-0xb43f,0xb800-0xb803,0xd000-0xd007,0xd400-0xd403,0xd800-0xd807 mem 0xf380-0xf381 irq 5 at device 6.0 on pci0 ata2: at 0xd800 on atapci0 ata3: at 0xd000 on atapci0 pcm0: Creative EMU10K1 port 0xb000-0xb01f irq 10 at device 15.0 on pci0 pcm0: SigmaTel STAC9721/23 AC97 Codec rl0: RealTek 8139 10/100BaseTX port 0xa400-0xa4ff mem 0xf300-0xf3ff irq 5 at device 16.0 on pci0 rl0: Ethernet address: 00:e0:4c:00:30:22 miibus0: MII bus on rl0 rlphy0: RealTek internal media interface on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: PCI to ISA bridge (vendor=1106 device=3074) at device 17.0 on pci0 isa0: ISA bus on isab0 atapci1: VIA 8233 ATA100 controller port 0xa000-0xa00f irq 0 at device 17.1 on pci0 ata0: at 0x1f0 irq 14 on atapci1 ata1: at 0x170 irq 15 on atapci1 uhci0: VIA 83C572 USB controller port 0x9800-0x981f irq 5 at device 17.2 on pci0 usb0: VIA 83C572 USB controller on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: VIA
Re: drive / IDE controller questions
Hi, I've been having problems with my western digital drive (http://www.wdc.com/en/products/products.asp?DriveID=24) for about a year. I've posted messages about this before, but I have some new information that may be relevant. The problem started out when I would randomly hear the drive restarting. It would make a high pitch sound that would increase in pitch and last a second or two (The same sound the drive makes when you power on the system). Messages similar to the ones below would also appear in /var/log/messages: ad0: WRITE command timeout tag=0 serv=0 - resetting /kernel: ata0: resetting devices .. ata0-slave: ATA identify retries exceeded ad0: READ command timeout tag=0 serv=0 - resetting At first, these drive resets would only happen once or twice and everything would go back to normal. Eventually they would happen over and over until the system became unusable and wouldn't boot up even after running fsck in singal user mode with all the partitions unmount or mounted read only. I found a temporary solution was to run the western digital diagnostic tools and then run fsck. I would usually have a small amount of data corruption/loss but the system would be usable again. Things would be fine for a week or longer, but the problem would eventually reappear. Finally I contacted WD and they sent me a replacement drive (It was the same model, but a refurbished drive that I'm guessing was sent back by someone else). After a few tries I managed to get dd to copy the contents of the old drive to the new drive and for quite some time everything was great. But, the other day the new drive began to have the same problem as the old one. So now, I'm guessing the problem may lie with the controller on the main board (http://usa.asus.com/mb/socketa/a7v266-e/overview.htm). Another early guess might also be overheating problems. I am not sure how you would check other than trying to make it cooler. jerry My main board has the optional raid controller. Would it be possible to use that controller with my current drive, or would the secondary controller be a better solution? Other notes: I've tried a few different IDE cables. I don't think it has anything to do with the OS since the resets have happened before the OS starts to boot and in the BIOS. I've included a uname -a, dmesg output and my kernel config file below. Any tips would be much appreciated. Thanks, Joey uname -a: FreeBSD *hostname* 4.9-RELEASE-p2 FreeBSD 4.9-RELEASE-p2 #0: Mon Feb 9 03:08:50 AST 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/KERNEL_CONFIG_2004-02-09 i386 dmesg: Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.9-RELEASE-p2 #0: Mon Feb 9 03:08:50 AST 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/2004-02-09 Timecounter i8254 frequency 1193182 Hz CPU: AMD Athlon(TM) XP1600+ (1410.21-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x662 Stepping = 2 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE AMD Features=0xc048MP,AMIE,DSP,3DNow! real memory = 536788992 (524208K bytes) avail memory = 518852608 (506692K bytes) Preloaded elf kernel kernel at 0xc0364000. Preloaded userconfig_script /boot/kernel.conf at 0xc036409c. Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 10 entries at 0xc00f1480 apm0: APM BIOS on motherboard apm0: found APM BIOS v1.2, connected at v1.2 npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge on motherboard pci0: PCI bus on pcib0 agp0: VIA Generic host to PCI bridge mem 0xf800-0xfbff at device 0.0 on pci0 pcib1: PCI to PCI bridge (vendor=1106 device=b099) at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: NVidia Riva Ultra Vanta TNT2 graphics accelerator at 0.0 irq 11 atapci0: Promise ATA100 controller port 0xb400-0xb43f,0xb800-0xb803,0xd000-0xd007,0xd400-0xd403,0xd800-0xd807 mem 0xf380-0xf381 irq 5 at device 6.0 on pci0 ata2: at 0xd800 on atapci0 ata3: at 0xd000 on atapci0 pcm0: Creative EMU10K1 port 0xb000-0xb01f irq 10 at device 15.0 on pci0 pcm0: SigmaTel STAC9721/23 AC97 Codec rl0: RealTek 8139 10/100BaseTX port 0xa400-0xa4ff mem 0xf300-0xf3ff irq 5 at device 16.0 on pci0 rl0: Ethernet address: 00:e0:4c:00:30:22 miibus0: MII bus on rl0 rlphy0: RealTek internal media interface on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: PCI to ISA bridge (vendor=1106 device=3074) at device 17.0 on pci0 isa0: ISA bus on isab0 atapci1: VIA 8233 ATA100 controller port 0xa000-0xa00f irq 0 at device 17.1 on pci0 ata0: at 0x1f0 irq 14 on atapci1 ata1: at 0x170 irq 15 on atapci1 uhci0: VIA 83C572 USB controller port 0x9800-0x981f irq 5 at
Re: drive / IDE controller questions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 snip Another early guess might also be overheating problems. I am not sure how you would check other than trying to make it cooler. jerry snip Could be.. although I have almost always had the case open and I have two case fans. The CPU temp is usually in the 40s or 50s C (not too bad for a 1.6GHz Athlon) and the memory is usually around 25C. ..but maybe I'll try pointing a fan at it. Thanks, joey -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAW1P90NQPEWppBZsRAjA1AKDECIaip9NIehDE3Gm0P6aeXV1SSQCgtp8+ J1F13XmVghOIiEkvQTuHn0Q= =Uogh -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: drive / IDE controller questions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 snip Another early guess might also be overheating problems. I am not sure how you would check other than trying to make it cooler. jerry snip Could be.. although I have almost always had the case open and I have two case fans. The CPU temp is usually in the 40s or 50s C (not too bad for a 1.6GHz Athlon) and the memory is usually around 25C. ..but maybe I'll try pointing a fan at it. Actually, I mean the disk overheating. They do that and they get worse at it as they age too. Also, some cases are designed to aid in the cooling and so with the case open, the airflow is either not properly directed or it doesn't get enough of a Bernouli or hydraulic effect, either of which is used to increase the air flow speed in critical areas. Of course, if it is a generic case that is probably not a consideration. jerry Thanks, joey -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAW1P90NQPEWppBZsRAjA1AKDECIaip9NIehDE3Gm0P6aeXV1SSQCgtp8+ J1F13XmVghOIiEkvQTuHn0Q= =Uogh -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: drive / IDE controller questions
in message [EMAIL PROTECTED], wrote Joey Mingrone thusly... I've been having problems with my western digital drive (http://www.wdc.com/en/products/products.asp?DriveID=24) for about a year. What that has to do w/ the thread discussing wget proxy problem? Above message was a *reply* to one of the messages in that thread. It was quite a rude surprise. People, kindly do not hijack a thread; start a new one. Thanks for your cooperation in future. - Parv -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
drive / IDE controller questions
[Jerry McAllister writes]
{Joey Mingrone writes]
I've been having problems with my western digital drive ...
The problem started out when I would randomly hear the drive restarting. It
would make a high pitch sound... (The same sound the drive makes when you
power on the system). ... Eventually they would happen over and over ...
So now, I'm guessing the problem may lie with the controller on the main
board
Another early guess might also be overheating problems. I am not sure how
you would check other than trying to make it cooler.
One way to check heating is to take the cover off and put your hand on the
drive. If it's too hot for your comfort, it's probably too hot for the drive's
comfort. You want to let the machine run and then remove the cover and check
it quickly; airflow changes when you take the cover(s) off. If that's the
problem, an extra fan in the right place can work wonders.
Don't exonorate cables too quickly; they can block airflow, especially if they
sag over time, or get pulled about by airflow.
I'm not familiar with the WD utilities; do they do surface scans? If not,
is it possible that there are problems that either the controllers or FreeBSD
cannot handle, and that these are occurring as certain blocks are put into
service? (But that wouldn't explain the failure on two drives?)
Mark Terribile
__
Do you Yahoo!?
Yahoo! Mail - More reliable, more storage, less spam
http://mail.yahoo.com
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: drive / IDE controller questions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On March 19, 2004 18:37, Parv wrote: in message [EMAIL PROTECTED], wrote Joey Mingrone thusly... I've been having problems with my western digital drive (http://www.wdc.com/en/products/products.asp?DriveID=24) for about a year. What that has to do w/ the thread discussing wget proxy problem? Above message was a *reply* to one of the messages in that thread. It was quite a rude surprise. People, kindly do not hijack a thread; start a new one. Thanks for your cooperation in future. - Parv Sorry about that. I think I got lazy and just replied to a message and changed the subject instead of typing [EMAIL PROTECTED] in the To: field. ..didn't realize the messages were threaded on the list. joey -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAW5zt0NQPEWppBZsRAsAeAJ9SVB3feilyU3ApA7L3iIHEOFU6fgCffb2l bJK7AOxrjQJIxrFNH13blGc= =6i3f -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: drive / IDE controller questions
[Jerry McAllister] [Joey Mingone] [Jerry McAllister] Another early guess might also be overheating problems. I am not sure how you would check other than trying to make it cooler. Could be.. although I have almost always had the case open and I have two case fans. The CPU temp is usually in the 40s or 50s C (not too bad for a 1.6GHz Athlon) and the memory is usually around 25C. ..but maybe I'll try pointing a fan at it. The case fans won't help much with the case open. Actually, I mean the disk overheating. They do that and they get worse at it as they age too. Also, some cases are designed to aid in the cooling and so with the case open, the airflow is either not properly directed or it doesn't get enough of a Bernouli or hydraulic effect... Of course, if it is a generic case that is probably not a consideration. Well, my tower box doesn't have any special baffles (yet) but if I operate it with both side panels off and push the CPU hard it will reset, and if I check the CPU heat sink I find it unusually warm. Without the forced circulation from either the exhaust fans above and to the rear or the inlet fan that I have on my disk drives, the CPU fan appears to draw back too much of the warm air it ejects below, hence the trend toward putting a side inlet vent on the machine -- a very bad idea, since it means that you can't place the machine up against another one. (The new BTX spec addresses this, but it looks like it introduces other problems.) I suggest that Joey check the temperature of the drive as he usually runs it, then again after running with the box closed. Mark Terribile __ Do you Yahoo!? Yahoo! Mail - More reliable, more storage, less spam http://mail.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Starting a new thread (was Re: drive / IDE controller questions)
in message [EMAIL PROTECTED], wrote Joey Mingrone thusly... On March 19, 2004 18:37, Parv wrote: in message [EMAIL PROTECTED], wrote Joey Mingrone thusly... I've been having problems with my western digital drive What that has to do w/ the thread discussing wget proxy problem? ... People, kindly do not hijack a thread; start a new one. Thanks for your cooperation in future. Sorry about that. I think I got lazy and just replied to a message and changed the subject Appreciate the acknowledgment. instead of typing [EMAIL PROTECTED] in the To: field. ..didn't realize the messages were threaded on the list. It is not the 'list' where the messages are threaded per se. 'References:' and/or 'In-Reply-To:' headers[0] contained in a message posses the information that allows for threading of messages by a mail reader, mutt in my case. Ergo, just a change in the 'To:' header will not make any difference, unless you also /remove/ the 'References:' and 'In-Reply-To:' headers. That assumes that you want to create a new separate thread by replying to another message, which is more time consuming than starting a new thread from scratch, no? [0] RFC 2822, 3.6.4 Identification fields... http://www.cis.ohio-state.edu/cgi-bin/rfc/rfc2822.html#sec-3.6.4 - Parv -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
