|
FreeBSD General Other questions regarding FreeBSD which do not fit in any of the categories below. |
|
Thread Tools | Display Modes |
|
|
|||
According to Roland Smith's answer to http://lists.freebsd.org/pipermail/f...ry/047744.html it could be a loose IDE/SATA cable.
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump |
|
||||
Quote:
Edit: I opened the box and checked both ends of the cable; both seemed to be firmly seated, but I pushed on them just to make sure. Then closed the box back up and restarted, and will leave it running for a while and see if it freezes again. Last edited by AncientDragonfly; 30th November 2009 at 03:00 AM. Reason: update |
|
||||
I would check my drive. It looks new, but you never know. New drives can break too.
MHDD is an excellent program to do that, you can download it from: http://hddguru.com/content/en/software/2005.10.02-MHDD/ It's the best hard disk test program I know of, but with somewhat ugly graphics and not the best help, a quickstart: o Press SHIFT+F3 to detect drives if this isn't done at startup. o Select drive. o Press F8 to check SMART attributes o Press F4 twice to scan the drive. This will take a while.
__________________
UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. |
|
||||
Thanks, Carpetsmoker. That looks like it will be my next step. It stayed running for 22 hours this time, but when I ran a whereis command, the ssh session gave me "Input/output error" and I found this on the screen upstairs:
I may have time this evening to burn the disk and set it off running, and see what I have when I get home tomorrow night. I'll report back when I have something new. |
|
|||
If you google for g_vfs_done you will find quite a lot of reports of this error, without a clear solution.
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump |
|
|||
I think it might either be disk failure or an ATA controller bug, not sure what you can recommend beyond trying another OS and seeing if the problem persists.
|
|
||||
I have no news yet; I didn't get MHDD burned to a CD last night, but I have done it now, and I will start it running when I get home this evening.
Searching for g_vfs_done did indeed turn up a lot of mentions of this type of problem, and it doesn't seem to be limited to SATA, the chipset, version of FreeBSD, or any other factor in common with my particular setup. I have, however, gotten some more ideas of things to test. I would like to avoid wiping this install if I can because of the time I've spent adding and configuring the ports I need. There was a lot of compiling and disk accessing that went on before the freezing started. I would also like to avoid buying more hardware just for testing purposes. This is the only SATA drive I have, although I do have some (smaller) unused IDE drives. This thread implies it could be memory related: http://www.daemonforums.org/showthread.php?t=2363 which is interesting, and a possibility, because the memory and CD/DVD are the only parts that were in my previous system. The previous motherboard had a component burn out, literally, which left scorch marks on the back of the mb. It might be that the memory was damaged in a way that wasn't apparent until the freezing occurred. Another thread somewhere suggested it might be a power supply issue, that is, not enough power, which I guess I can test by removing the 2nd HD. The power supply is new, 460W. Other ideas my search prompted were: IRQ conflict? (Not my strong suit, does anyone see anything in dmesg?) Bad SATA cable? (I have another one that came with the HD) Bad connector on MB? (move to another connector Bios update? (there are a couple of newer versions available) Question about MHDD: if the problem is not the drive itself, but somewhere in the connection between the drive and the processor, will that be shown by the test, or will the test register that the drive is bad when it may not be? After I run the MHDD test, I'll run memtest. |
|
||||
Quote:
Quote:
Quote:
As a sidenote, the real problem are the top three lines (ata2: port not ready, ad4: device detached)...
__________________
UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. |
|
||||
Quote:
Quote:
Quote:
After that, I went ahead and started memtest, and as of this morning, 12 hours later, there were no errors. I left it running anyway, and will see if there are still no errors this evening. If not, I'll call that done, and try to work with MHDD some more, or move onto something else, like the bios update. |
|
|||
How badly do you want the sata drive as your principal drive
if you have others? I've a sata controller on pci which is unstable "to sata" and usually hoses the target filesystem upon, say, a rsync session. Here, the fix... a... gjournal setup on the target (maybe irrelevant) b... using bwlimit" parameter to rsync to make the target receive data at 1/10th the rate of the source disk (the freebsd forums has details in a post). That makes the controller, unreliable otherwise, perfect for backups ( I can merrily use the system as otherwise, rsyncing a FS at a time, as long as while it is just root, a few non-default-mounted filesystems are unmounted. ) Your post maybe (???) implies this setup is more reliable than the/a sata disk, used as the primary disk in a system with sata chipsets originally on the motherboard.
__________________
FreeBSD 13-STABLE Last edited by jb_daefo; 2nd December 2009 at 02:22 AM. Reason: to clarify last paragraph |
|
||||
Quote:
I have 3 modes in my bios: SATA, RAID, and AHCI. It is currently set to AHCI. I might try setting to SATA, although I have read that SATA really means to run in IDE mode. (I don't know for sure, though, because the mb manual is pitiful at explaining the different bios options.) I don't care what mode it runs in, just that it runs. Quote:
Quote:
Last edited by AncientDragonfly; 3rd December 2009 at 02:31 AM. Reason: changed EHCI to AHCI |
|
||||
Is that power supply from a good manufacturer, or is it just a generic tin box? While I'd be happy with a 460W name-brand PSU with 2 HDDs, a generic cheapie could easily be the problem.
__________________
The only dumb question is a question not asked. The only dumb answer is an answer not given. |
|
||||
I may be getting somewhere! MHDD didn't recognize the drive because it (MHDD) doesn't work in AHCI mode: http://forum.hddguru.com/mhdd-doesn-...v7-t13113.html
So I set it to SATA, which I (now after more research) read is there to support "1st generation SATA": http://www.hardforum.com/showthread.php?t=1407996 MHDD's checking the drive now, and estimates just over 2 hours more to go. I wonder if the freezing was a problem with AHCI mode, and might not happen in SATA? BTW, no memory errors after 26 hours of checking. |
|
||||
CoolerMaster should be good.
OH, and what is so difficult about fishing a old-style hdd connector out of your box and sticking the probes of a multimeter into it? Assuming you can [read instructions about how to] use a multimeter well enough to know volts from amps or ohms, that is.
__________________
The only dumb question is a question not asked. The only dumb answer is an answer not given. |
|
|||
Measuring a ATX power supply is not that easy. You first have to connect two pins to turn the PSU on. Some PSU's also switch off when there is no load.
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump |
|
||||
At the first screen shot is says ERROR twice, with UNC status. This means there are (at least) two bad sectors.
There are also a number of reallocated sectors, high read error rate, and a number of other smart attributes which don't look good. Conclusion: You drive is broken. You must replace it. You can check warranty status for Seagate drives online: http://www.seagate.com/www/en-us/sup..._&_submit_rma/
__________________
UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. |
|
||||
Quote:
Fortunately, it was just within the 30-day return period, and after the tech guy at the little hole-in-the-wall computer store gave me a lecture about always using the manufacturer's test program because it will give him an error code he needs for his return to the mfg, then tested it for himself with Seagate's test program, he agreed it was bad, and I walked out with another new one, hopefully not just like the old one. I have learned a valuable lesson here, which is to test even a new disk before going through the process of installing the OS and a bunch of ports. The adventure of probing my power supply can wait (oh, happy day!) until another time. If the 2nd install goes as well as the first one (until the freezing started), I will soon be using the new system without problems. Thanks, everyone, for helping me out with your suggestions and support! |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
FreeBSD 8.0-RELEASE | Nightweaver | FreeBSD Installation and Upgrading | 10 | 10th December 2009 12:12 AM |
OpenBSD OpenBSD 4.6 Release | Carpetsmoker | News | 21 | 11th November 2009 11:13 PM |
FreeBSD 7.2-RELEASE | vermaden | FreeBSD General | 6 | 12th May 2009 08:33 PM |
-Release vs. -Stable | guitarscn | OpenBSD Installation and Upgrading | 3 | 2nd October 2008 02:32 PM |
FreeBSD 6.2-RELEASE > 7.0-RELEASE Upgrade | Marci | FreeBSD Installation and Upgrading | 2 | 23rd July 2008 02:10 PM |