Re0 driver or hardware problem?
Oh, and forgot to mention: - the tp-link card in another Windows PC is working nicely - booting from Ubuntu Live CD on the same machine where FreeBSD is installed - the tp-link card is working, get an IP address via DHCP Gabor ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re0 driver or hardware problem?
Hi, I have an Asus M2NPV-VM motherboard with integrated Nvidia MCP51 Gigabit Ethernet NIC and TP-Link TG-3468 PCIe network card which is basically using Realtek chip. I have several problems: 1. There is a boot time menu for tp-link card which says it is a 8111b/8111c but re driver supports RTL8139C+, RTL8169, RTL8169S, RTL8110S, RTL8168S, RTL8111S and RTL8101E. Is it correct using the re driver? 2. The Nvidia network interface is working properly but the other though it seems recognized by OS I cannot use. Sporadically it remains down and if it gets up then does not get ip address via DHCP nor help if I set static ip address. Can manipulate via ifconfig but unreachable via IP. I replaced cable, interchanged cable working with Nvidia, restarted switch/router but no luck so far. And advise please? Thanks, Gabor uname -v FreeBSD 8.1-RELEASE #0 r210200M: Wed Jul 21 14:21:18 CEST 2010 r...@neo.vx.sk:/usr/obj/usr/src/sys/GENERIC pciconf: n...@pci0:0:20:0:class=0x068000 card=0x816a1043 chip=0x026910de rev=0xa3 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'MCP51 Network Bus Enumerator' class = bridge r...@pci0:1:0:0:class=0x02 card=0x816810ec chip=0x816810ec rev=0x01 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'Gigabit Ethernet NIC(NDIS 6.0) (RTL8168/8111/8111c)' class = network subclass = ethernet rc.conf: ifconfig_nfe0=inet 192.168.0.200 netmask 255.255.255.0 defaultrouter=192.168.0.1 hostname=xxx ifconfig_re0=DHCP dmesg: nfe0: NVIDIA nForce 430 MCP13 Networking Adapter port 0xc800-0xc807 mem 0xfe02b000-0xfe02bfff irq 21 at device 20.0 on pci0 miibus1: MII bus on nfe0 e1000phy0: Marvell 88E1116 Gigabit PHY PHY 19 on miibus1 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto nfe0: Ethernet address: 00:1a:92:38:dc:95 nfe0: [FILTER] re0: RealTek 8168/8111 B/C/CP/D/DP/E PCIe Gigabit Ethernet port 0xac00-0xacff mem 0xfdbff000-0xfdbf irq 16 at device 0.0 on pci1 re0: Using 1 MSI messages re0: Chip rev. 0x3800 re0: MAC rev. 0x miibus0: MII bus on re0 rgephy0: RTL8169S/8110S/8211B media interface PHY 1 on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re0: Ethernet address: d8:5d:4c:80:b4:88 re0: [FILTER] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: freecolor: Bus error. software or hardware problem?
So, is it port trouble? -- Best regards, Antonio Kless, http://kless.spb.ru/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
freecolor: Bus error. software or hardware problem?
Strange freecolor behavior on fresh 8.0-RELEASE system. # uname -a FreeBSD alternate-1.net 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:02:08 UTC 2009 r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 # freecolor -V freecolor version 0.8.8 # freecolor Bus error I have reinstall 7.3-RELEASE on this server, and get another look of error: # freecolor Bus error: 10 Is it software or hardware problem? -- Best regards, Antonio Kless, http://kless.spb.ru/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: freecolor: Bus error. software or hardware problem?
Have you updated your ports? This was an issue on the amd64 distribution, but it was fixed. On Fri, Jul 23, 2010 at 1:21 AM, Antonio Kless antoniok@gmail.comwrote: Strange freecolor behavior on fresh 8.0-RELEASE system. # uname -a FreeBSD alternate-1.net 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:02:08 UTC 2009 r...@mason.cse.buffalo.edu: /usr/obj/usr/src/sys/GENERIC amd64 # freecolor -V freecolor version 0.8.8 # freecolor Bus error I have reinstall 7.3-RELEASE on this server, and get another look of error: # freecolor Bus error: 10 Is it software or hardware problem? -- Best regards, Antonio Kless, http://kless.spb.ru/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- - Simplicity is the ultimate sophistication. - Leonardo da Vinci - Intelligence is not defined by what you know, It's how you USE it. - People who hate Windows use Linux but people who love UNIX use BSD. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: freecolor: Bus error. software or hardware problem?
2010/7/23 Randy Belk randy.b...@gmail.com Have you updated your ports? This was an issue on the amd64 distribution, but it was fixed. On Fri, Jul 23, 2010 at 1:21 AM, Antonio Kless antoniok@gmail.comwrote: Strange freecolor behavior on fresh 8.0-RELEASE system. # uname -a FreeBSD alternate-1.net 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:02:08 UTC 2009 r...@mason.cse.buffalo.edu: /usr/obj/usr/src/sys/GENERIC amd64 # freecolor -V freecolor version 0.8.8 # freecolor Bus error I have reinstall 7.3-RELEASE on this server, and get another look of error: # freecolor Bus error: 10 Is it software or hardware problem? -- Best regards, Antonio Kless, http://kless.spb.ru/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- - Simplicity is the ultimate sophistication. - Leonardo da Vinci - Intelligence is not defined by what you know, It's how you USE it. - People who hate Windows use Linux but people who love UNIX use BSD. Yes, I run # portsnap fetch update just about 1 hour ago. -- Best regards, Antonio Kless, http://kless.spb.ru/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: freecolor: Bus error. software or hardware problem?
2010/7/23 Antonio Kless antoniok@gmail.com 2010/7/23 Randy Belk randy.b...@gmail.com Have you updated your ports? This was an issue on the amd64 distribution, but it was fixed. On Fri, Jul 23, 2010 at 1:21 AM, Antonio Kless antoniok@gmail.comwrote: Strange freecolor behavior on fresh 8.0-RELEASE system. # uname -a FreeBSD alternate-1.net 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:02:08 UTC 2009 r...@mason.cse.buffalo.edu: /usr/obj/usr/src/sys/GENERIC amd64 # freecolor -V freecolor version 0.8.8 # freecolor Bus error I have reinstall 7.3-RELEASE on this server, and get another look of error: # freecolor Bus error: 10 Is it software or hardware problem? -- Best regards, Antonio Kless, http://kless.spb.ru/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- - Simplicity is the ultimate sophistication. - Leonardo da Vinci - Intelligence is not defined by what you know, It's how you USE it. - People who hate Windows use Linux but people who love UNIX use BSD. Yes, I run # portsnap fetch update just about 1 hour ago. -- Best regards, Antonio Kless, http://kless.spb.ru/ ...run it before I install freecolor port, of course. -- Best regards, Antonio Kless, http://kless.spb.ru/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to diagnose hardware problem?
The first two utils I run if I suspect hardware issues both independant of resident os ; http://www.memtest.org/ http://www.hitachigst.com/hdd/technolo/dft/dft.htm ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
How to diagnose hardware problem?
I have what looks like a hardware problem with an Intel 1U server, which I am using mainly as a mysql database server for some of my bigger website clients. The server went down last week with a badly corrupted file system. After spending a day trying to fix the file system, we gave up and did a fresh install of FreeBSD, PF, and mysql, using our daily backups to restore the database. It all seemed to work fine until I switched the websites from the temporary database server that I had been using, onto the restored server. The database ran well for about 2 minutes, then the server crashed again. The filesystem was again corrupted so badly that we could not even log in to look at the logs. We've reinstalled FreeBSD again, just to be able to SSH into the box. It looks like there is probably a hardware problem, like a bad power supply or overheating CPU that fails when the load of the database is applied. Problem is, I have no idea how to determine which bits are failing. Can anyone suggest a favorite book or website that focuses on how to troubleshoot hardware issues? Thanks: John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to diagnose hardware problem?
First things first; if the machine is still in warranty, don't mess with it but send it back to the manufacturer and demand a replacement. It is in warranty and I am following their process. I'm hoping to short-circuit that process by finding the problem on my own, if possible. Plus, I've never really had to deal with a hardware failure before, so it's a good learning process. If the machine is out of warranty, you might consider replacing it altogether. My employer's IT department ditches PC's and servers at the first failure after the warranty runs out. Accordinf to them it's cheaper than repairing them. But if you want to have a go, this might help: http://www.daileyint.com/hmdpc/manual.htm Basically, it's just a problem of elimination. First check if your machine is the only one having problems at the hosting site. Maybe they have unstable electrical power. Then make sure that all expansion cards and RAM are well-seated, and that all connectors are OK. Also check that there is no dust build- up on e.g. fans and heatsinks. If necessary, clean carefully with (dry, oil free) compressed air. Dust can lead to short circuits or reduced cooling. Next, look for capacitors that have leaked fluid, or have bulging metal end plates on the motherboard; those are dead or dying. It's a leading cause of motherboard failure. It is possible to replace them, but you'll need the right equipment: http://www.tomshardware.com/reviews/fixing-motherboard,1606.html Install a monitoring program like mbmon or healthd, and have it log to another machine or a USB stick mounted syncronously. Monitor CPU temperature, fan speeds and the different voltages. Not all power supplies are created equally. See the articles at tom's hardware: http://www.tomshardware.com/reviews/Components,1/Power-Supplies,6/ If you've found nothing so far, it's time to start swapping out components, starting with the power supply. This is all good stuff to try. Thanks. -- John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Fwd: How to diagnose hardware problem?
On Apr 13, 2009, at 2:32 PM, Wojciech Puchar wrote: The database ran well for about 2 minutes, then the server crashed again. The filesystem was again corrupted so badly that we could not even log in to look at the logs. did memtest? it looks like it's fine until you stress your hardware I didn't, but I just installed it and am running it at the moment. So far, so good. The machine has 1G of memory, but I could not get an mlock unless I request 100 Meg or less. That is, I need to run something like: # memtest 100 Does this sound right? If I run with 125 Meg, I get the following: # memtest 125 memtester version 4.0.8 (64-bit) Copyright (C) 2007 Charles Cazabon. Licensed under the GNU General Public License version 2 (only). pagesize is 4096 pagesizemask is 0xf000 want 125MB (131072000 bytes) got 125MB (131072000 bytes), trying mlock ...failed for unknown reason. Continuing with unlocked memory; testing will be slower and less reliable. Loop 1: Stuck Address : ok Random Value: ok Compare XOR : ok Compare SUB : ok Compare MUL : ok etc... -- John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to diagnose hardware problem?
The database ran well for about 2 minutes, then the server crashed again. The filesystem was again corrupted so badly that we could not even log in to look at the logs. did memtest? it looks like it's fine until you stress your hardware We've reinstalled FreeBSD again, just to be able to SSH into the box. It looks like there is probably a hardware problem, like a bad power supply or overheating CPU that fails when the load of the database is applied. Problem is, I have no idea how to determine which bits are failing. Can anyone suggest a favorite book or website that focuses on how to troubleshoot hardware issues? Thanks: John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to diagnose hardware problem?
On Mon, Apr 13, 2009 at 12:07:25PM -0400, John Almberg wrote: I have what looks like a hardware problem with an Intel 1U server, which I am using mainly as a mysql database server for some of my bigger website clients. The server went down last week with a badly corrupted file system. After spending a day trying to fix the file system, we gave up and did a fresh install of FreeBSD, PF, and mysql, using our daily backups to restore the database. It all seemed to work fine until I switched the websites from the temporary database server that I had been using, onto the restored server. The database ran well for about 2 minutes, then the server crashed again. The filesystem was again corrupted so badly that we could not even log in to look at the logs. We've reinstalled FreeBSD again, just to be able to SSH into the box. It looks like there is probably a hardware problem, like a bad power supply or overheating CPU that fails when the load of the database is applied. Problem is, I have no idea how to determine which bits are failing. Can anyone suggest a favorite book or website that focuses on how to troubleshoot hardware issues? First things first; if the machine is still in warranty, don't mess with it but send it back to the manufacturer and demand a replacement. If the machine is out of warranty, you might consider replacing it altogether. My employer's IT department ditches PC's and servers at the first failure after the warranty runs out. Accordinf to them it's cheaper than repairing them. But if you want to have a go, this might help: http://www.daileyint.com/hmdpc/manual.htm Basically, it's just a problem of elimination. First check if your machine is the only one having problems at the hosting site. Maybe they have unstable electrical power. Then make sure that all expansion cards and RAM are well-seated, and that all connectors are OK. Also check that there is no dust build-up on e.g. fans and heatsinks. If necessary, clean carefully with (dry, oil free) compressed air. Dust can lead to short circuits or reduced cooling. Next, look for capacitors that have leaked fluid, or have bulging metal end plates on the motherboard; those are dead or dying. It's a leading cause of motherboard failure. It is possible to replace them, but you'll need the right equipment: http://www.tomshardware.com/reviews/fixing-motherboard,1606.html Install a monitoring program like mbmon or healthd, and have it log to another machine or a USB stick mounted syncronously. Monitor CPU temperature, fan speeds and the different voltages. Not all power supplies are created equally. See the articles at tom's hardware: http://www.tomshardware.com/reviews/Components,1/Power-Supplies,6/ If you've found nothing so far, it's time to start swapping out components, starting with the power supply. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpOGV68CCS4P.pgp Description: PGP signature
RE: hardware problem
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of D G Teed Sent: Wednesday, February 27, 2008 3:54 AM To: Ted Mittelstaedt Cc: DAve; FreeBSD Questions Subject: Re: hardware problem On Wed, Feb 27, 2008 at 1:58 AM, Ted Mittelstaedt [EMAIL PROTECTED] wrote: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of D G Teed Sent: Monday, February 25, 2008 7:22 AM To: DAve Cc: FreeBSD Questions Subject: Re: hardware problem Every system I've seen with his description of the problem, where the power supply can't even run it's own fan, is having a power supply problem. Power supplies are very often low quality these days and can't handle the stresses of typical electrical grid fluctuations. My experience has not been that the power supplies can't handle the electrical grid. What I've mostly seen is that the power supply FANS get dust in them, the fans slow down or stop, airflow through the supply drops, and then the supply overheats. Once it overheats, the supply will never be reliable again and must be thrown out. I've been able to routinely clean out the dust with canned air, and they still die more frequently than say motherboards. Even quality brands like Antec. I often replace the fan if it is showing signs of noise from bearing getting burned out. I'm speaking mainly of home and small office PCs. This is something that won't happen as much in a server room since the air is cleaner, but I'd guess the O.P. wasn't in that environment since he is wasting 3 days before trying another power supply. Power supplies do have a limit of life related to the quality of your electricity Not the good ones. Seriously. I run a NOC that has a 50kva natural gas fired generator. Every Tue. the generator is tested for 1/2 hour (basically we put the entire NOC on generator power for 1/2 hour) There is an automatic transfer switch that switches the entire NOC, under load, including the HVAC unit, onto generator power for 1/2 hour then switches it back to mains power. There is NO feedback circuit that syncs the sinewave from the generator with mains power. As you can imagine the switch is tremendously disruptive. All of the UPSs in the place squawk and switch into UPS power for a couple minutes. All of the UPSes in the place are cut-in types. So far we have only had 1 system lose power supplies on a regular basis, and this was a brand new, very expensive, HP server. (on UPSes of course) HP's replaced at least 8 power supplies in it under warranty. None of the others, including some of the most motley customer-owned clone equipment you might imagine, have suffered power supply failure. The HVAC unit of course heavily filters the air so there is no dust so to speak. I can pull the cover off 3 year old servers and the interior is as pristine as when they are new. And we keep the temp around 68 degrees. Please keep in mind most computer power supples nowadays are auto-switching and will run on anything from 110-220v. It is NOT dirty power that does them in. It is dust. And heat, as you said. Overloading a supply will kill it also - very few (retail) power supplies on the market will run close to their rated power output for any length of time. Today, the biggest problem I see is people demanding these minitower systems, getting these tiny small cases and stuffing them full of hard and optical drives. There's dead air spaces throughout the layout, and small, low-volume quiet fans. Hard drives also suffer as a result of this. A disk with good cooling can last many years. But few computers other than server gear provide it to the drive bays. I can recall the bad electrolyte scandle with several motherboard brands 5 years ago. The explanation of the shortened capacitor lifespan due to the electrolyte missing an ingredient was a bit of an education into what capacitors do. They do have a limited lifespan related to heat and the number of hours they are exposed to a high ripple current. Here is an excellent wikipedia entry on capacitor plague which will explain it in layman's terms. http://en.wikipedia.org/wiki/Capacitor_plague If you have not read about this before, it may be an eye opener. I know all about that. I also own several TV sets that date from late, late 60's early 70's and still work. Electrolytic capacitors have been around a long, long time. They had them during the tube days, and tube gear ran very hot. Like anything, they have a lifespan, but it is in the multiple decades, and little dependent on ripple current or heat. The issue with the self-corroding capacitors was corrected and while the equipment (like for example, Apple eMacs of 1Ghz CPU) that had those suffered, it isn't indicative of normal electrolytic capacitor lifespan. The most heat-sensitive parts are the semiconductors
Re: hardware problem
On Mon, Feb 25, 2008 at 08:38:09PM -0500, Tsu-Fan Cheng wrote: hi guys, just take every part out and dust with a brush, reseat the m-board and hook on the power supply, switch on the power and both fans spin for quite a while, seeing this, I switch it off and start to connect all the cables. After all is done, i turn on the power again, and this time it stop again after a short spin. and I looked everywhere on the board and found some silverish dust on the board, i dust it away, but this time, the fans and the LED light on the board never spin or lit up when i switch it on, i wonder if something i did kill the power this time, any idea?? thank you for your help. TFC Having been round the houses with my new build which displayed similar problems, I would say that what is most likely is that it is a power supply problem. There was a shaky attachment somewhere which loosened when you moved and finally gave up the ghost. Your best approach, is to get a new power supply or case with power supply depending on how old your case is. If that doesn't work, then it's probably your motherboard and unless your CPU is quite new and you can extract it, you'll probably be looking at new CPU and RAM also ie. expensive. If you want to get a new case, then have a look at an Antec Sonata III. It's quiet, comes with all the bits you need and has USB ports and e-SATA on the front. Cost me about 75GBP. 500W power supply which is a bit excessive for my needs though. Best of luck! -- Frank Contact info: http://www.esperance-linux.co.uk/misc/contact.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hardware problem
On Wed, Feb 27, 2008 at 1:58 AM, Ted Mittelstaedt [EMAIL PROTECTED] wrote: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of D G Teed Sent: Monday, February 25, 2008 7:22 AM To: DAve Cc: FreeBSD Questions Subject: Re: hardware problem Every system I've seen with his description of the problem, where the power supply can't even run it's own fan, is having a power supply problem. Power supplies are very often low quality these days and can't handle the stresses of typical electrical grid fluctuations. My experience has not been that the power supplies can't handle the electrical grid. What I've mostly seen is that the power supply FANS get dust in them, the fans slow down or stop, airflow through the supply drops, and then the supply overheats. Once it overheats, the supply will never be reliable again and must be thrown out. I've been able to routinely clean out the dust with canned air, and they still die more frequently than say motherboards. Even quality brands like Antec. I often replace the fan if it is showing signs of noise from bearing getting burned out. I'm speaking mainly of home and small office PCs. This is something that won't happen as much in a server room since the air is cleaner, but I'd guess the O.P. wasn't in that environment since he is wasting 3 days before trying another power supply. Power supplies do have a limit of life related to the quality of your electricity (and excessive heat). I can recall the bad electrolyte scandle with several motherboard brands 5 years ago. The explanation of the shortened capacitor lifespan due to the electrolyte missing an ingredient was a bit of an education into what capacitors do. They do have a limited lifespan related to heat and the number of hours they are exposed to a high ripple current. Here is an excellent wikipedia entry on capacitor plague which will explain it in layman's terms. http://en.wikipedia.org/wiki/Capacitor_plague If you have not read about this before, it may be an eye opener. --Donald ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hardware problem
On Mon, Feb 25, 2008 at 10:45 PM, Da Rock [EMAIL PROTECTED] wrote: On Mon, 2008-02-25 at 20:38 -0500, Tsu-Fan Cheng wrote: hi guys, just take every part out and dust with a brush, reseat the m-board and hook on the power supply, switch on the power and both fans spin for quite a while, seeing this, I switch it off and start to connect all the cables. After all is done, i turn on the power again, and this time it stop again after a short spin. and I looked everywhere on the board and found some silverish dust on the board, i dust it away, but this time, the fans and the LED light on the board never spin or lit up when i switch it on, i wonder if something i did kill the power this time, any idea?? thank you for your help. TFC Looks like that little bit of dust was making the system still seem like its alive. I'd say its well and truely dead now- what do you reckon guys? New M/B and CPU... You are suggesting to replace the MB and CPU? By the same logic, if a light bulb burns out, replace the wiring in your house. That is inappropriate. Power supplies burn out all the time. Replace the power supply. The big clue is when the power supply can't spin it's own fan. Has nothing to do with the rest of the system. --Donald ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: hardware problem
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of D G Teed Sent: Monday, February 25, 2008 7:22 AM To: DAve Cc: FreeBSD Questions Subject: Re: hardware problem Every system I've seen with his description of the problem, where the power supply can't even run it's own fan, is having a power supply problem. Power supplies are very often low quality these days and can't handle the stresses of typical electrical grid fluctuations. My experience has not been that the power supplies can't handle the electrical grid. What I've mostly seen is that the power supply FANS get dust in them, the fans slow down or stop, airflow through the supply drops, and then the supply overheats. Once it overheats, the supply will never be reliable again and must be thrown out. Turning off a computer for a while that has an overheated power supply is a surefire way to have the supply never restart again. Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
hardware problem
Hi guys, this is really not about freebsd per sa. But this is the only computer-related forum I use. so please forgive me. my desktop was relocated due to my recent moving to a new apartment. After settling down at the new place, I plug in the cables and the computer won't start up. I open the case and found out that when i switched on the power supply from the back, the power fan and cpu fan will spin for a split second then stop. I tried to debug by unplugging the cables, when doing so, sometimes the fans will spin for 10 seconds, maybe, but most of the time, it just stopped right after the power switched on. I also try to hold down the start button on the front for a while, but no good. I was told the mother board maybe short-circuit. can anyone give a second opinion?? thanks!! TFC ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hardware problem
Tsu-Fan Cheng wrote: Hi guys, this is really not about freebsd per sa. But this is the only computer-related forum I use. so please forgive me. my desktop was relocated due to my recent moving to a new apartment. After settling down at the new place, I plug in the cables and the computer won't start up. I open the case and found out that when i switched on the power supply from the back, the power fan and cpu fan will spin for a split second then stop. I tried to debug by unplugging the cables, when doing so, sometimes the fans will spin for 10 seconds, maybe, but most of the time, it just stopped right after the power switched on. I also try to hold down the start button on the front for a while, but no good. I was told the mother board maybe short-circuit. can anyone give a second opinion?? thanks!! TFC IMO, experience says the worst thing you can do to a computer is leave it sit a year running, and then move it. I would get a grounding wrist strap, open the case, remove all cards and memory, disconnect all hard drives, clean with a soft brush (never a vacuum cleaner), reseat all cards and memory, reconnect all hard drives, and then try to restart it. Even without a post code announcing a problem, I have fixed many moved PCs this way. DAve -- Google finally, after 7 years, provided a logo for veterans. Thank you Google. What to do with my signature now? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hardware problem
At 08:06 AM 2/25/2008, Tsu-Fan Cheng wrote: Hi guys, this is really not about freebsd per sa. But this is the only computer-related forum I use. so please forgive me. my desktop was relocated due to my recent moving to a new apartment. After settling down at the new place, I plug in the cables and the computer won't start up. I open the case and found out that when i switched on the power supply from the back, the power fan and cpu fan will spin for a split second then stop. I tried to debug by unplugging the cables, when doing so, sometimes the fans will spin for 10 seconds, maybe, but most of the time, it just stopped right after the power switched on. I also try to hold down the start button on the front for a while, but no good. I was told the mother board maybe short-circuit. can anyone give a second opinion?? thanks!! TFC It sounds like you have something shorting out the motherboard. I would remove everything you can, all add-on cards etc. Just leave a video card, unless video is on the motherboard. I would disconnect all the drives too. The idea is to remove everything, so you can check just the motherboard alone. If the motherboard still won't power on, remove and reseat the RAM. If it still won't power up, remove and re-seat the CPU. I would guess something inside the case was moved around enough in your move to cause the short. -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hardware problem
Every system I've seen with his description of the problem, where the power supply can't even run it's own fan, is having a power supply problem. Power supplies are very often low quality these days and can't handle the stresses of typical electrical grid fluctuations. Most people who deal with hardware have a spare power supply around just for testing as this is a very common problem. Motherboards typically do not stop power supply fans when they can't post. On Mon, Feb 25, 2008 at 10:35 AM, DAve [EMAIL PROTECTED] wrote: IMO, experience says the worst thing you can do to a computer is leave it sit a year running, and then move it. I would get a grounding wrist strap, open the case, remove all cards and memory, disconnect all hard drives, clean with a soft brush (never a vacuum cleaner), reseat all cards and memory, reconnect all hard drives, and then try to restart it. Even without a post code announcing a problem, I have fixed many moved PCs this way. DAve -- Google finally, after 7 years, provided a logo for veterans. Thank you Google. What to do with my signature now? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hardware problem
thank you all for helping. I will reinstall my main again from scratch. one thing i want to know is that if my m-board is short somewhere, does this mean my board is damaged? or it's okay if i can find out what is wrong, and so most likely i need to buy a power supply, is that right at the moment?? thans!! TFC On Mon, Feb 25, 2008 at 10:22 AM, D G Teed [EMAIL PROTECTED] wrote: Every system I've seen with his description of the problem, where the power supply can't even run it's own fan, is having a power supply problem. Power supplies are very often low quality these days and can't handle the stresses of typical electrical grid fluctuations. Most people who deal with hardware have a spare power supply around just for testing as this is a very common problem. Motherboards typically do not stop power supply fans when they can't post. On Mon, Feb 25, 2008 at 10:35 AM, DAve [EMAIL PROTECTED] wrote: IMO, experience says the worst thing you can do to a computer is leave it sit a year running, and then move it. I would get a grounding wrist strap, open the case, remove all cards and memory, disconnect all hard drives, clean with a soft brush (never a vacuum cleaner), reseat all cards and memory, reconnect all hard drives, and then try to restart it. Even without a post code announcing a problem, I have fixed many moved PCs this way. DAve -- Google finally, after 7 years, provided a logo for veterans. Thank you Google. What to do with my signature now? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hardware problem
At 09:58 AM 2/25/2008, Tsu-Fan Cheng wrote: thank you all for helping. I will reinstall my main again from scratch. one thing i want to know is that if my m-board is short somewhere, does this mean my board is damaged? or it's okay if i can find out what is wrong, and so most likely i need to buy a power supply, is that right at the moment?? thans!! TFC I would look for the short first. You may need to replace nothing. Be sure to check the Motherboard case connectors to the switchs and LEDs as well. -Derek On Mon, Feb 25, 2008 at 10:22 AM, D G Teed [EMAIL PROTECTED] wrote: Every system I've seen with his description of the problem, where the power supply can't even run it's own fan, is having a power supply problem. Power supplies are very often low quality these days and can't handle the stresses of typical electrical grid fluctuations. Most people who deal with hardware have a spare power supply around just for testing as this is a very common problem. Motherboards typically do not stop power supply fans when they can't post. On Mon, Feb 25, 2008 at 10:35 AM, DAve [EMAIL PROTECTED] wrote: IMO, experience says the worst thing you can do to a computer is leave it sit a year running, and then move it. I would get a grounding wrist strap, open the case, remove all cards and memory, disconnect all hard drives, clean with a soft brush (never a vacuum cleaner), reseat all cards and memory, reconnect all hard drives, and then try to restart it. Even without a post code announcing a problem, I have fixed many moved PCs this way. DAve -- Google finally, after 7 years, provided a logo for veterans. Thank you Google. What to do with my signature now? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. __ Information from ESET NOD32 Antivirus, version of virus signature database 2900 (20080225) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hardware problem
Derek Ragona wrote: At 08:06 AM 2/25/2008, Tsu-Fan Cheng wrote: Hi guys, this is really not about freebsd per sa. But this is the only computer-related forum I use. so please forgive me. my desktop was relocated due to my recent moving to a new apartment. After settling down at the new place, I plug in the cables and the computer won't start up. I open the case and found out that when i switched on the power supply from the back, the power fan and cpu fan will spin for a split second then stop. I tried to debug by unplugging the cables, when doing so, sometimes the fans will spin for 10 seconds, maybe, but most of the time, it just stopped right after the power switched on. I also try to hold down the start button on the front for a while, but no good. I was told the mother board maybe short-circuit. can anyone give a second opinion?? thanks!! TFC It sounds like you have something shorting out the motherboard. I would remove everything you can, all add-on cards etc. Just leave a video card, unless video is on the motherboard. I would disconnect all the drives too. The idea is to remove everything, so you can check just the motherboard alone. If the motherboard still won't power on, remove and reseat the RAM. If it still won't power up, remove and re-seat the CPU. I would guess something inside the case was moved around enough in your move to cause the short. -Derek Agree. The symptoms, fans starting and almost immediately stopping, say the power supply is starting, detecting a short and shutting down. If the video card is AGP double check it is properly seated, I've had that same result several times particularly with AGP cards lifting very slightly at the inboard end. Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hardware problem
hi guys, just take every part out and dust with a brush, reseat the m-board and hook on the power supply, switch on the power and both fans spin for quite a while, seeing this, I switch it off and start to connect all the cables. After all is done, i turn on the power again, and this time it stop again after a short spin. and I looked everywhere on the board and found some silverish dust on the board, i dust it away, but this time, the fans and the LED light on the board never spin or lit up when i switch it on, i wonder if something i did kill the power this time, any idea?? thank you for your help. TFC On Mon, Feb 25, 2008 at 7:53 PM, Chris Whitehouse [EMAIL PROTECTED] wrote: Derek Ragona wrote: At 08:06 AM 2/25/2008, Tsu-Fan Cheng wrote: Hi guys, this is really not about freebsd per sa. But this is the only computer-related forum I use. so please forgive me. my desktop was relocated due to my recent moving to a new apartment. After settling down at the new place, I plug in the cables and the computer won't start up. I open the case and found out that when i switched on the power supply from the back, the power fan and cpu fan will spin for a split second then stop. I tried to debug by unplugging the cables, when doing so, sometimes the fans will spin for 10 seconds, maybe, but most of the time, it just stopped right after the power switched on. I also try to hold down the start button on the front for a while, but no good. I was told the mother board maybe short-circuit. can anyone give a second opinion?? thanks!! TFC It sounds like you have something shorting out the motherboard. I would remove everything you can, all add-on cards etc. Just leave a video card, unless video is on the motherboard. I would disconnect all the drives too. The idea is to remove everything, so you can check just the motherboard alone. If the motherboard still won't power on, remove and reseat the RAM. If it still won't power up, remove and re-seat the CPU. I would guess something inside the case was moved around enough in your move to cause the short. -Derek Agree. The symptoms, fans starting and almost immediately stopping, say the power supply is starting, detecting a short and shutting down. If the video card is AGP double check it is properly seated, I've had that same result several times particularly with AGP cards lifting very slightly at the inboard end. Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hardware problem
On Mon, 2008-02-25 at 20:38 -0500, Tsu-Fan Cheng wrote: hi guys, just take every part out and dust with a brush, reseat the m-board and hook on the power supply, switch on the power and both fans spin for quite a while, seeing this, I switch it off and start to connect all the cables. After all is done, i turn on the power again, and this time it stop again after a short spin. and I looked everywhere on the board and found some silverish dust on the board, i dust it away, but this time, the fans and the LED light on the board never spin or lit up when i switch it on, i wonder if something i did kill the power this time, any idea?? thank you for your help. TFC Looks like that little bit of dust was making the system still seem like its alive. I'd say its well and truely dead now- what do you reckon guys? New M/B and CPU... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Hardware Problem - FreeBSD 6.2
Hi, Good morning, my name is Rômulo Lima, I had a problem when make an upgrade in my Freebsd Server from version 6.1 to 6.2. Before upgrade my SATA disc controller was working normally: atapci1: AcerLabs M5287 SATA150 controller port 0xec00-0xec0f,0xe480-0xe487,0xe400-0xe40f,0xe080-0xe087,0xe000-0xe01f mem 0xd800-0xdbff irq 21 at device 31.1 on pci0 ad4: 78167MB Maxtor 6Y080M0 YAR51HW0 at ata2-master SATA150 But after upgrade I got the following error, and my SATA disc stops, after that I proceeded with a downgrade and may Server work fine again. atapci1: AHCI controller reset failure device_attach: atapci1 attach returned 6 I search a solution on some mail lists, but I still have no solution to this problem, if anyone can help me I will thank very much! Best Regards, Rômulo Lima Tech Manager Wavenet www.wavenet.com.br (55)(71) 3177-6150 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hardware Problem - FreeBSD 6.2
On Thursday 01 March 2007 16:10, Rômulo Lima wrote: Hi, Good morning, my name is Rômulo Lima, I had a problem when make an upgrade in my Freebsd Server from version 6.1 to 6.2. Before upgrade my SATA disc controller was working normally: atapci1: AcerLabs M5287 SATA150 controller port 0xec00-0xec0f,0xe480-0xe487,0xe400-0xe40f,0xe080-0xe087,0xe000-0xe01f mem 0xd800-0xdbff irq 21 at device 31.1 on pci0 ad4: 78167MB Maxtor 6Y080M0 YAR51HW0 at ata2-master SATA150 But after upgrade I got the following error, and my SATA disc stops, after that I proceeded with a downgrade and may Server work fine again. atapci1: AHCI controller reset failure device_attach: atapci1 attach returned 6 I search a solution on some mail lists, but I still have no solution to this problem, if anyone can help me I will thank very much! Hello Romulo, Check this message and the relevant thread: http://lists.freebsd.org/pipermail/freebsd-stable/2005-January/011256.html If that's not your case, please post a message to stable@ with an appropriate subject(SATA: AHCI controller reset failure for example) to catch some attention. Nikos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Hardware Problem
I have a hardware problem with a disk drive. Last night I received millions of messages like: Oct 29 23:00:02 zook kernel: ad0: timeout waiting for write DRQ Oct 29 23:00:02 zook kernel: g_vfs_done():ad0s1e[WRITE (offset=39908835328, lengt h=8192)]error = 5 Oct 29 23:00:02 zook kernel: ad0: timeout waiting for write DRQ Oct 29 23:00:02 zook kernel: g_vfs_done():ad0s1e[WRITE (offset=39908835328, lengt h=8192)]error = 5 Oct 29 23:00:16 zook kernel: ad0: timeout waiting for write DRQ Oct 29 23:00:16 zook last message repeated 3 times Oct 29 23:00:16 zook kernel: g_vfs_done():ad0s1e[WRITE (offset=1433600, length=81 92)]error = 5 Oct 29 23:00:16 zook kernel: g_vfs_done():ad0s1e[WRITE (offset=1441792, length=81 92)]error = 5 Oct 29 23:00:16 zook kernel: g_vfs_done():ad0s1e[WRITE (offset=1449984, length=51 20)]error = 5 Oct 29 23:00:16 zook kernel: g_vfs_done():ad0s1e[WRITE(offset=8192, length=2048) ]error = 5 Oct 29 23:00:28 zook kernel: ad0: timeout waiting for write DRQ Oct 29 23:00:28 zook last message repeated 8 times They were going to messages and the console as fast as the system could log them. ad0 is not the boot disk but is used to hold large files. I have seen somewhat similar problems once before and replaced the drive. That was about a year ago. This time I am suspecting the IDE controller. Is this reasonable, or is it still likely a drive failure? Rebooting the system appears to have temporarily terminated the problem as I am no longer receiving the messages and nothing appears to have been lost on ad0. However, the bulk of data on it are the news archive and other archive files that were replaced shortly after the reboot. smartctl shows passed on the drive, but I believe I am reading that 6 sectors have been remapped. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Server compilation or hardware problem?!
[EMAIL PROTECTED] writes: I would like to ask some questions. I have the intranet system on my computer which is running freeBSD. But functionality of the system is quite slow. So I don't know what is wrong. My server contains 1GHZ procesor and 256+128RAM. Is it enough? System is used aproximately 300 users. I can define that every time maybe 5-8 users are log in. So the problem is in the compilation or in hardware? You need to be more precise about what is happening, how you are measuring slowness, what the load average is doing, and so on. If half-a-dozen users are doing number-crunching simultaneously, I wouldn't be surprised that the system is slow. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Server compilation or hardware problem?!
Hello, I would like to ask some questions. I have the intranet system on my computer which is running freeBSD. But functionality of the system is quite slow. So I don't know what is wrong. My server contains 1GHZ procesor and 256+128RAM. Is it enough? System is used aproximately 300 users. I can define that every time maybe 5-8 users are log in. So the problem is in the compilation or in hardware? Thank you very much. Yours truly. Arunas Tamulevicius IT specialist Gintarine grupe Baublio g. 2, Vilnius e-mail.: [EMAIL PROTECTED] GSM 8_620_39885 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
SCSI Hardware problem?
This looks to me like I've got a hardware problem. SCSI drive 0:4:0 -- or is this perhaps something else? I had to manually type this in ... :) copying it off the screen since I don't see this stuff in a log anywhere. FreeBSD 5.3 on a dual 450MHz Xeon with SCSI and IDE. GENERIC kernel. There was stuff above this, but it had scrolled off the screen and the console was locked up. da1 (scsi 4 on bus 0) is my boot drive. --- Dump Card State Ends (da1:ahc1:0:4:0): SCB 0x3 - timed out sg[0] - Addr 0x2574b000 (da1:ahc1:0:4:0): Queuing a BDR SCB (da1:ahc1:0:4:0): no longer in timeout, status = 24a ahc1: Timedout SCBs already complete. Interrupts may not be functioning. (da1:ahc1:0:4:0): WRITE(10). CDB: 2a, 0 0 47 49 23 0 0 4 0 (da1:ahc1:0:4:0): CAM Status: SCSI Status Error (da1:ahc1:0:4:0): SCSI Status: Check Condition (da1:ahc1:0:4:0): UNIT ATTENTION asc:29,1 (da1:ahc1:0:4:0): Power on occurred (da1:ahc1:0:4:0): Retrying Command (per sense Data) (da1:ahc1:0:4:0): WRITE(10). CDB: 2a, 0 0 47 49 23 0 0 4 0 (da1:ahc1:0:4:0): CAM Status: SCSI Status Error (da1:ahc1:0:4:0): CAM Status: Check Condition (da1:ahc1:0:4:0): UNIT ATTENTION asc:29,1 (da1:ahc1:0:4:0): Power on occurred (da1:ahc1:0:4:0): Retries Exhausted (da1:ahc1:0:4:0): lost device (da1:ahc1:0:4:0): invalidating pack panic: initiate_write_inodeblock_ufs2: already started Uptime: 3d12h50m3s --- I'm guessing I will want to copy this entire drive over to another one. What's the best way dd? Oh, one other question ... I'm used to runlevels on Linux. When I reset this machine, I'm presented with the prompt asking me for the default shell (/bin/sh). I hit enter, and I'm in sh where I can fsck the other drives and mount them. Cool. But once I have done that, how do I tell BSD to basically continue where it left off (i.e. run /etc/netstart sshd, httpd, psqld, zope, etc) without manually invoking each of those items? Thanks in advance. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SCSI Hardware problem?
On Thu, 06 Jan 2005 15:18:04 -0700, Tom Vilot wrote This looks to me like I've got a hardware problem. SCSI drive 0:4:0 - - or is this perhaps something else? I had to manually type this in ... :) copying it off the screen since I don't see this stuff in a log anywhere. FreeBSD 5.3 on a dual 450MHz Xeon with SCSI and IDE. GENERIC kernel. There was stuff above this, but it had scrolled off the screen and the console was locked up. da1 (scsi 4 on bus 0) is my boot drive. --- Dump Card State Ends (da1:ahc1:0:4:0): SCB 0x3 - timed out sg[0] - Addr 0x2574b000 (da1:ahc1:0:4:0): Queuing a BDR SCB (da1:ahc1:0:4:0): no longer in timeout, status = 24a ahc1: Timedout SCBs already complete. Interrupts may not be functioning. (da1:ahc1:0:4:0): WRITE(10). CDB: 2a, 0 0 47 49 23 0 0 4 0 (da1:ahc1:0:4:0): CAM Status: SCSI Status Error (da1:ahc1:0:4:0): SCSI Status: Check Condition (da1:ahc1:0:4:0): UNIT ATTENTION asc:29,1 (da1:ahc1:0:4:0): Power on occurred (da1:ahc1:0:4:0): Retrying Command (per sense Data) (da1:ahc1:0:4:0): WRITE(10). CDB: 2a, 0 0 47 49 23 0 0 4 0 (da1:ahc1:0:4:0): CAM Status: SCSI Status Error (da1:ahc1:0:4:0): CAM Status: Check Condition (da1:ahc1:0:4:0): UNIT ATTENTION asc:29,1 (da1:ahc1:0:4:0): Power on occurred (da1:ahc1:0:4:0): Retries Exhausted (da1:ahc1:0:4:0): lost device (da1:ahc1:0:4:0): invalidating pack panic: initiate_write_inodeblock_ufs2: already started Uptime: 3d12h50m3s Make sure your SCSI controller is supported by the driver you're using. If it is, it's probably a faulty disk. --- I'm guessing I will want to copy this entire drive over to another one. What's the best way dd? Doesn't matter too much AFAIK. As long as you can access the disk properly. Oh, one other question ... I'm used to runlevels on Linux. When I reset this machine, I'm presented with the prompt asking me for the default shell (/bin/sh). I hit enter, and I'm in sh where I can fsck the other drives and mount them. Cool. But once I have done that, how do I tell BSD to basically continue where it left off (i.e. run /etc/netstart sshd, httpd, psqld, zope, etc) without manually invoking each of those items? I assume you boot in single user mode. I would just reboot the machine again and boot normally (multi-user mode) after you're finished with fsck and stuff. Cheers, Jorn Thanks in advance. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SCSI Hardware problem?
At 02:30 PM 1/6/2005, Jorn Argelo wrote: Oh, one other question ... I'm used to runlevels on Linux. When I reset this machine, I'm presented with the prompt asking me for the default shell (/bin/sh). I hit enter, and I'm in sh where I can fsck the other drives and mount them. Cool. But once I have done that, how do I tell BSD to basically continue where it left off (i.e. run /etc/netstart sshd, httpd, psqld, zope, etc) without manually invoking each of those items? I assume you boot in single user mode. I would just reboot the machine again and boot normally (multi-user mode) after you're finished with fsck and stuff. Or you could just exit the shell and the system will continue to boot into multi-user mode. -Glenn Cheers, Jorn Thanks in advance. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SCSI Hardware problem?
Glenn Dawson wrote: Or you could just exit the shell and the system will continue to boot into multi-user mode. (( sigh )) It's always so much simpler than you think it is at first glance . Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: SCSI Hardware problem?
-Original Message- From: [EMAIL PROTECTED] [mailto:owner-freebsd- [EMAIL PROTECTED] On Behalf Of Tom Vilot Sent: Friday, January 07, 2005 3:48 To: FreeBSD Questions Subject: SCSI Hardware problem? This looks to me like I've got a hardware problem. SCSI drive 0:4:0 -- or is this perhaps something else? I had to manually type this in ... :) copying it off the screen since I don't see this stuff in a log anywhere. FreeBSD 5.3 on a dual 450MHz Xeon with SCSI and IDE. GENERIC kernel. There was stuff above this, but it had scrolled off the screen and the console was locked up. da1 (scsi 4 on bus 0) is my boot drive. --- Dump Card State Ends (da1:ahc1:0:4:0): SCB 0x3 - timed out sg[0] - Addr 0x2574b000 (da1:ahc1:0:4:0): Queuing a BDR SCB (da1:ahc1:0:4:0): no longer in timeout, status = 24a ahc1: Timedout SCBs already complete. Interrupts may not be functioning. (da1:ahc1:0:4:0): WRITE(10). CDB: 2a, 0 0 47 49 23 0 0 4 0 (da1:ahc1:0:4:0): CAM Status: SCSI Status Error (da1:ahc1:0:4:0): SCSI Status: Check Condition (da1:ahc1:0:4:0): UNIT ATTENTION asc:29,1 (da1:ahc1:0:4:0): Power on occurred (da1:ahc1:0:4:0): Retrying Command (per sense Data) (da1:ahc1:0:4:0): WRITE(10). CDB: 2a, 0 0 47 49 23 0 0 4 0 (da1:ahc1:0:4:0): CAM Status: SCSI Status Error (da1:ahc1:0:4:0): CAM Status: Check Condition (da1:ahc1:0:4:0): UNIT ATTENTION asc:29,1 (da1:ahc1:0:4:0): Power on occurred (da1:ahc1:0:4:0): Retries Exhausted (da1:ahc1:0:4:0): lost device (da1:ahc1:0:4:0): invalidating pack panic: initiate_write_inodeblock_ufs2: already started Uptime: 3d12h50m3s Is the SCSI bus terminated properly. Changing LUNs help? --- I'm guessing I will want to copy this entire drive over to another one. What's the best way dd? dd works only and only if the source drive and the target drive are *exact* clones of each other, which is not something seen very frequently. Why don't you use dump? Oh, one other question ... I'm used to runlevels on Linux. When I reset this machine, I'm presented with the prompt asking me for the default shell (/bin/sh). I hit enter, and I'm in sh where I can fsck the other drives and mount them. Cool. But once I have done that, how do I tell BSD to basically continue where it left off (i.e. run /etc/netstart sshd, httpd, psqld, zope, etc) without manually invoking each of those items? Ctrl+D Thanks in advance. Welcome :-) Regards S. Indian Institute of Information Technology Subhro Sankha Kar Block AQ-13/1, Sector V Salt Lake City PIN 700091 India smime.p7s Description: S/MIME cryptographic signature
Nasty hardware problem...
I trying to bring up a file server a system with a 1.5GHz AMD Athlon, 256MB RAM, an older AHA2940 SCSI card with an IBM DDYS-T18350N hard drive. The hard drive is connected to the second channel (the Ultra-wide channel) on the 2940. During the boot process (from the dmesg) the machine stops with a SCSI Status Error (Check Condition) saying it refuses Tagged commands. The boot system appears to then go into untagged mode and finds that the SCSI card has been RESET. There follows a dump of the card, which I have attached here. Could this be because the data rate frequency is set too high? I lowered it from 20MB/s to 16MB/s, but I could go as low as 10MB/s. On the other hand, that may have nothing to do with the problem. This is kind of a shot in the dark, I know... but someone out there in FreeBSD land might have seen something like this before. Please forgive the long message. -Lyman Dec 2 21:10:55 Cogitek-UX2 kernel: Dump Card State Begins Dec 2 21:10:55 Cogitek-UX2 kernel: ahc0: Dumping Card State in Message-in phase, at SEQADDR 0x1bf Dec 2 21:10:55 Cogitek-UX2 kernel: Card was paused Dec 2 21:10:55 Cogitek-UX2 kernel: ACCUM = 0x0, SINDEX = 0x31, DINDEX = 0xc0, ARG_2 = 0x8 Dec 2 21:10:55 Cogitek-UX2 kernel: HCNT = 0x0 SCBPTR = 0x7 Dec 2 21:10:55 Cogitek-UX2 kernel: SCSISIGI[0xe6]:(REQI|BSYI|MSGI|IOI|CDI) ERROR[0x0] Dec 2 21:10:55 Cogitek-UX2 kernel: SCSIBUSL[0x80] LASTPHASE[0xe0]:(MSGI|IOI|CDI) SCSISEQ[0x12]:(ENAUTOATNP|ENRSELI) Dec 2 21:10:55 Cogitek-UX2 kernel: SBLKCTL[0x2]:(SELWIDE) SCSIRATE[0x0] SEQCTL[0x10]:(FASTMODE) Dec 2 21:10:55 Cogitek-UX2 kernel: SEQ_FLAGS[0xc0]:(NO_CDB_SENT|NOT_IDENTIFIED) SSTAT0[0x7]:(DMADONE|SPIORDY|SDONE) Dec 2 21:10:55 Cogitek-UX2 kernel: SSTAT1[0x3]:(REQINIT|PHASECHG) SSTAT2[0x0] SSTAT3[0x0] Dec 2 21:10:55 Cogitek-UX2 kernel: SIMODE0[0x0] SIMODE1[0xac]:(ENSCSIPERR|ENBUSFREE|ENSCSIRST|ENSELTIMO) Dec 2 21:10:55 Cogitek-UX2 kernel: SXFRCTL0[0x88]:(SPIOEN|DFON) DFCNTRL[0x4]:(DIRECTION) Dec 2 21:10:55 Cogitek-UX2 kernel: DFSTATUS[0x6d]:(FIFOEMP|DFTHRESH|HDONE|FIFOQWDEMP|DFCACHETH) Dec 2 21:10:55 Cogitek-UX2 kernel: STACK: 0x144 0x0 0x191 0x199 Dec 2 21:10:55 Cogitek-UX2 kernel: SCB count = 70 Dec 2 21:10:55 Cogitek-UX2 kernel: Kernel NEXTQSCB = 69 Dec 2 21:10:55 Cogitek-UX2 kernel: Card NEXTQSCB = 69 Dec 2 21:10:55 Cogitek-UX2 kernel: QINFIFO entries: Dec 2 21:10:55 Cogitek-UX2 kernel: Waiting Queue entries: 15:32 Dec 2 21:10:55 Cogitek-UX2 kernel: Disconnected Queue entries: 8:34 11:36 5:2 3:59 13:53 6:41 0:15 10:8 1:38 12:35 9:9 2:1 4:40 14:33 Dec 2 21:10:55 Cogitek-UX2 kernel: QOUTFIFO entries: Dec 2 21:10:55 Cogitek-UX2 kernel: Sequencer Free SCB List: 7 Dec 2 21:10:55 Cogitek-UX2 kernel: Sequencer SCB Info: Dec 2 21:10:55 Cogitek-UX2 kernel: 0 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x87]:(TWIN_CHNLB) Dec 2 21:10:55 Cogitek-UX2 kernel: SCB_LUN[0x0] SCB_TAG[0xf] Dec 2 21:10:55 Cogitek-UX2 kernel: 1 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x87]:(TWIN_CHNLB) Dec 2 21:10:55 Cogitek-UX2 kernel: SCB_LUN[0x0] SCB_TAG[0x26] Dec 2 21:10:55 Cogitek-UX2 kernel: 2 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x87]:(TWIN_CHNLB) Dec 2 21:10:55 Cogitek-UX2 kernel: SCB_LUN[0x0] SCB_TAG[0x1] Dec 2 21:10:55 Cogitek-UX2 kernel: 3 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x87]:(TWIN_CHNLB) Dec 2 21:10:55 Cogitek-UX2 kernel: SCB_LUN[0x0] SCB_TAG[0x3b] Dec 2 21:10:55 Cogitek-UX2 kernel: 4 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x87]:(TWIN_CHNLB) Dec 2 21:10:55 Cogitek-UX2 kernel: SCB_LUN[0x0] SCB_TAG[0x28] Dec 2 21:10:55 Cogitek-UX2 kernel: 5 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x87]:(TWIN_CHNLB) Dec 2 21:10:56 Cogitek-UX2 kernel: SCB_LUN[0x0] SCB_TAG[0x2] Dec 2 21:10:56 Cogitek-UX2 kernel: 6 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x87]:(TWIN_CHNLB) Dec 2 21:10:56 Cogitek-UX2 kernel: SCB_LUN[0x0] SCB_TAG[0x29] Dec 2 21:10:56 Cogitek-UX2 kernel: 7 SCB_CONTROL[0x10]:(MK_MESSAGE) SCB_SCSIID[0x87]:(TWIN_CHNLB) Dec 2 21:10:56 Cogitek-UX2 kernel: SCB_LUN[0x0] SCB_TAG[0xff] Dec 2 21:10:56 Cogitek-UX2 kernel: 8 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x87]:(TWIN_CHNLB) Dec 2 21:10:56 Cogitek-UX2 kernel: SCB_LUN[0x0] SCB_TAG[0x22] Dec 2 21:10:56 Cogitek-UX2 kernel: 9 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x87]:(TWIN_CHNLB) Dec 2 21:10:56 Cogitek-UX2 kernel: SCB_LUN[0x0] SCB_TAG[0x9] Dec 2 21:10:56 Cogitek-UX2 kernel: 10 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x87]:(TWIN_CHNLB) Dec 2 21:10:56 Cogitek-UX2 kernel: SCB_LUN[0x0] SCB_TAG[0x8] Dec 2 21:10:56 Cogitek-UX2 kernel: 11 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x87]:(TWIN_CHNLB) Dec 2 21:10:56 Cogitek-UX2 kernel: SCB_LUN[0x0] SCB_TAG[0x24] Dec 2 21:10:56 Cogitek-UX2 kernel: 12
Nasty hardware problem...
Oops! Major irq head-butting is the problem. I'm amazed the system even came up far enough to complain about it. Sorry I bothered the list with this. -Lyman ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
