Re: kernel panic on SATA drive
You may wish to check and see if your firmware is up-to-date on all of your disk drives, and your controller. On Mon, Dec 21, 2009 at 10:40:10PM +0200, Alex thus spake: Dear John, Any progress for bellow? I have the same problem with PCI SATA Controller ST-Lab A-173 Sil3512 It's not RAID, but when copying to HDD: LOG--- ad6:FAILURE - device detached g_vfs_done():ad6s1f[WRITE(offset=38007275520, length=131072)]error = 6 /usr: got error 6 while accessing filesystem panic: softdep_deallocate_dependencies: unrecovered I/O error cpuid = 0 Uptime: 2m18s Physical memory: 243 MB Dumping 58 MB:unknown: timeout waiting to issue command unknown: error issuing WRITE_DMA command ** DUMP FAILED (ERROR 5) ** Automatic reboot in 15 seconds - press any key on the console to abort ---END LOG- Brgrds, Alex I've been having an intermittent problem, wonder if someone on the list has any ideas. First my setup: FreeBSD 7.2-RELEASE (amd64) quad-core Phenom processor mobo: MSI K9N2G Neo chipset: NVIDIA GeForce 8200, which FreeBSD recognizes as nForce (not sure how that works) I have a 3ware RAID card (RAID 1), which is the boot device. A seagate drive connected via SATA A WD external drive via USB I will have the system running fine, then the seagate will apparently fall off the bus, resulting in a panic. The dump fails as well, presumably due to the 3ware driver not being able to handle the panic? not sure... If anyone knows a way I can get the dump to succeed, I'd appreciate that info, too. See below output for details. ___ 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: kernel panic on SATA drive
On Tue, Dec 22, 2009 at 11:52 AM, Jason jhelf...@e-e.com wrote: = Any progress for bellow? I have the same problem with PCI SATA Controller ST-Lab A-173 Sil3512 It's not RAID, but when copying to HDD: LOG--- ad6:FAILURE - device detached g_vfs_done():ad6s1f[WRITE(offset=38007275520, length=131072)]error = 6 /usr: got error 6 while accessing filesystem panic: softdep_deallocate_dependencies: unrecovered I/O error cpuid = 0 Uptime: 2m18s Physical memory: 243 MB Dumping 58 MB:unknown: timeout waiting to issue command unknown: error issuing WRITE_DMA command ** DUMP FAILED (ERROR 5) ** Automatic reboot in 15 seconds - press any key on the console to abort ---END LOG- Brgrds, Alex I just had a drive do the same, it was dying. -- Adam Vande More ___ 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
kernel panic on SATA drive
Dear John, Any progress for bellow? I have the same problem with PCI SATA Controller ST-Lab A-173 Sil3512 It's not RAID, but when copying to HDD: LOG--- ad6:FAILURE - device detached g_vfs_done():ad6s1f[WRITE(offset=38007275520, length=131072)]error = 6 /usr: got error 6 while accessing filesystem panic: softdep_deallocate_dependencies: unrecovered I/O error cpuid = 0 Uptime: 2m18s Physical memory: 243 MB Dumping 58 MB:unknown: timeout waiting to issue command unknown: error issuing WRITE_DMA command ** DUMP FAILED (ERROR 5) ** Automatic reboot in 15 seconds - press any key on the console to abort ---END LOG- Brgrds, Alex I've been having an intermittent problem, wonder if someone on the list has any ideas. First my setup: FreeBSD 7.2-RELEASE (amd64) quad-core Phenom processor mobo: MSI K9N2G Neo chipset: NVIDIA GeForce 8200, which FreeBSD recognizes as nForce (not sure how that works) I have a 3ware RAID card (RAID 1), which is the boot device. A seagate drive connected via SATA A WD external drive via USB I will have the system running fine, then the seagate will apparently fall off the bus, resulting in a panic. The dump fails as well, presumably due to the 3ware driver not being able to handle the panic? not sure... If anyone knows a way I can get the dump to succeed, I'd appreciate that info, too. See below output for details. ___ 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
kernel panic on SATA drive
The FreeBSD Developers' Handbook describes how to get panic information (and dig out further details). http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html#KERNELDEBUG-OBTAIN Was there any output before ad7: FAILURE - device detached? Losing the drive in the bios makes me think hardware, but I'd check for any firmware problems/updates if they exist. I have not tried yet, but FreeBSD8 is supposed to finally handle the anxiety of losing a drive. http://freebsdfoundation.org/press/2008Dec-newsletter.shtml#Project1 I would try smartctl from ports; run a long scan and read the full output to see if it passes or if you get a response like: # 1 Extended offlineCompleted: read failure 20% 32490 308342849 Also look above that output to see if there any metioned 'Error ## occured at disk power-on lifetime' type of messages. to scan, run: smartctl -t long /dev/ad7 after the scan, read output with: smartctl -a long /dev/ad7 What motherboard is it? GeForce 8200 sounds like a graphics chipset to me. For hardware analysis, try to isolate it to a particular drive (sounds like it is only the seagate), cable (data or power), motherboard sata port. When the drive is not recognized, does a coldboot redetect it? Does the drive start any audible clicking? What model of drive is it? Make sure the drive is dusted off, increase the cooling, and try again; I have a drive that flakes out if the three speed antec fan in front of it is only on low but stabilizes when kept cooler; its a great hint to me that the drive is near life's end. ___ 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
kernel panic on SATA drive
I've been having an intermittent problem, wonder if someone on the list has any ideas. First my setup: FreeBSD 7.2-RELEASE (amd64) quad-core Phenom processor mobo: MSI K9N2G Neo chipset: NVIDIA GeForce 8200, which FreeBSD recognizes as nForce (not sure how that works) I have a 3ware RAID card (RAID 1), which is the boot device. A seagate drive connected via SATA A WD external drive via USB I will have the system running fine, then the seagate will apparently fall off the bus, resulting in a panic. The dump fails as well, presumably due to the 3ware driver not being able to handle the panic? not sure... If anyone knows a way I can get the dump to succeed, I'd appreciate that info, too. See below output for details. The first time I had the problem, it would regularly happen when I tried to install a particular port (sudo). Then I changed where the SATA cable was plugged in and tried un/re-plugging the USB external drive and rebooting and managed to get it working (so I thought). One weird aspect of that process is that the BIOS would not even list the SATA drive until I switched it to a different plug... freaked me out a bit. Also during POST it would hang for many seconds, when I had the USB drive plugged in, until I went through my random plugging/unplugging/replugging shenanigans. But now it has happened again, this time while copying lots of files from the USB external drive to the SATA one. Both drives are recognized by BIOS (and FreeBSD) on reboot this time, at least. But I'm hesitant to just 'call it good' - I'd like this to be a stable server (: I manually transcribed the bulk of the output - is there a nicer way to get the output of a kernel panic so I can copy/paste? I didn't find an obvious command, though I'm no FreeBSD guru. If someone could tell me how to get that output, I'd be greatful. output below ad7: FAILURE - device detached g_vfs_done():ad7s1d[WRITE(offset=340978335744, length=16384)]error = 6 g_vfs_done():ad7s1d[WRITE(offset=340978352128, length=16384)]error = 6 /dev: got error 6 while accessing filesystem panic: softdep_deallocate_dependencies: unrecovered I/O error cpuid=2 Uptime: 15h23m39s Physical memory: 7923MB Dumping 733MB: 718 702 686 670 654 638twe0:completion event for nonbusy command twe0: completion event for nonbusy command twe0: completion event for nonbusy command twe0: completion event for nonbusy command twe0: completion event for nonbusy command twe0: completion event for nonbusy command twe0: FATAL STATUS BIT(S) 20MCERR twe0: status 13207fd2CQEMPTY,UCREADY,RQEMPTY,MCERR, ### At this point in the log a bunch of output starts getting interleaved, character-by-character even. ### Maybe due to multi-cpus dumping output simultaneously? I don't know... ### eventually... twe0: can't drain AEN queue twe0: controller reset in progress twe0: reset 1 failed ### snip more failing messages twe0: can't reset controller, giving up #Then some more stuff that I haven't written down end log --- So any thoughts? Maybe it's just a mobo / chipset compatibility issue? I should have known with a mobo that says GeForce 8200 for chipset. I thought NVIDIA support was pretty good in FreeBSD though... Do you think recompiling my own kernel would help? Do you think installing a different version of FreeBSD would help? (My main experience is with 6.2) It was quite odd to me that even the BIOS stopped recognizing the SATA drive the first time. Any thoughts on that? Thanks for any feedback -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
