Displaying 20 results from an estimated 200 matches similar to: "strange deadlock and magic resurrection with RELENG_6"
2007 Apr 04
1
sun x2100 gmirror problem
Hi,
We're using gmirror on our sun fire x2100 and FreeBSD 6.1-p10. Some days
ago I found this in the logs:
Apr 1 02:12:05 x2100 kernel: ad6: WARNING - WRITE_DMA48 UDMA ICRC error
(retrying request) LBA=612960533
Apr 1 02:12:05 x2100 kernel: ad6: FAILURE - WRITE_DMA48
status=51<READY,DSC,ERROR> error=10<NID_NOT_FOUND> LBA=612960533
Apr 1 02:12:05 x2100 kernel: GEOM_MIRROR:
2006 Mar 06
6
gmirror(8) and graid3(8) changes.
Hi.
Here you can find patches with changes to gmirror(8) and graid3(8):
http://people.freebsd.org/~pjd/patches/gmirror.7.patch
http://people.freebsd.org/~pjd/patches/graid3.patch
The patches does the following:
- Significant synchronization speed improvement. Now many parallel
synchronization I/O requests can be used instead of only one before.
Many people requested this.
- Close race
2008 Aug 27
1
Finding which GEOM provider is generating errors in a graid3
I have a FreeBSD 6.2-based server running a 1.2TB graid3 volume, which
consists of 5x 320gb SATA hard drives. I've been getting errors in
/var/log/messages from the graid3 volume, which I suspect means an
underlying fault with one of the disks, but is there any way to decipher
which one of these drives is throwing errors?
I've checked smartctl -a /dev/adXX but nothing shows up there..
2003 May 24
3
UDMA ICRC error
Hi there.
OS version: FreeBSD 4.7-Stable FreeBSD #3
I just added a disk to my box and after playing with
fdisk and disklabel with this configuration:
fdisk:
****************************************************************
g c16383 h16 s63
p 1 165 0 39102336
****************************************************************
disklabel
2004 Nov 30
1
FAILURE - WRITE_DMA timed out
When I use SATA disks heavily on a 5.3-R machine (Athlon) with the
SiI3512 disk controller, I get frequent (sometimes one every 1-5
minutes) WRITE_DMA timed out messages (with different blocks and both
disks).
It also panics with more than one kind of panic, and sometimes doesn't
even get to finish the background fsck from the previous panic before
dying again.
Given that both disks get the
2006 Apr 05
1
GEOM_RAID3: Device datos is broken, too few valid components
Hello list,
Last night one disk of my desktop machine dead causing a hard lock of the
computer. It was a component of a mirror volume so it wasn't as serious as
it initially looked.
Unfortunately, the metadata structure of my data partition (a geom raid3
array with tree components ) seems to be corrupted by this hard lock,
the following message is scrolled constantly on the screen:
2006 Mar 22
0
"TIMEOUT - WRITE_DMA" with SiI 3512 SATA on IBM eServer 326
Hi,
I have a problem, probably with the SiI 3512 SATA150 controller in a
dual-Opteron IBM eServer 326:
Every once a while the kernel issues a message like:
ad4: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=150190687
The system waits a few seconds and continues to work normally.
It typically occurs several times a day most likely depending on the
load of the (SATA connected) hard drive.
2013 Feb 01
1
stable/9: Force ada1 to UDMA-33
Hello,
I've got a (P)ATA disk in a special frame. The disk itself
supports UDMA-100 (and has an 80-ribbon cable), but the
frame isn't compatible with that. By default, FreeBSD
negotiates UDMA-100, and the console starts to fill with
ICRC errors.
In the past, I used a patch to ata-all.c that enabled the
following entry in loader.conf to force the disk to UDMA-33,
so it worked fine:
2006 Dec 05
0
The amazing smartctl -a /dev/hda
I finally fixed my drive error problem. This has been going on quite a
while. I've posted before with no success on getting this fixed.
I was getting these errors.
Dec 4 04:03:10 bikesn4x4s kernel: hda: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Dec 4 04:03:10 bikesn4x4s kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }
And now for the amazing smartctl -a
2006 Mar 24
1
ad4: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - on FreeBSD 6-STABLE
Hi
After my previous email about the SETFEATURES SET TRANSFER MODE timeout
on (msgid 441AA807.5090100@wfeet.za.net , 17 March 14:18 GMT + 2 on
freebsd-stable), I installed FreeBSD 6.1 BETA 4 and upgraded to a
6-STABLE kernel, running the box in 'safe' mode to do so. I now,
however, get a slightly different error message:
ad4: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout
2004 Sep 10
0
flac123 resurrection
flac123 is back! Version 0.0.3 is now available at
http://flac-tools.sourceforge.net . flac123 now supports FLAC 1.1.0, and
its remote mode mimics mpg123's. Please test it for bugs and report them to
the flac-tools sourceforge forum.
_________________________________________________________________
Share holiday photos without swamping your Inbox. Get MSN Extra Storage
now!
2009 Nov 06
2
SMART errors
I dumpster dived an older low end Dell (actually, found it in a field in
a fresh dump pile). Case looked good, only flaws appeared to be missing
cdrom bezel and the heat sink clamp was off (but not broken).
After cleaning cpu/heat sink and fresh thermal paste, I found out why it
was dumped - the internal hard drive was bad, and the optical drive is
going bad.
I had an old 80 GB Seagate and
2006 Mar 11
4
Problem with 16-in-1 card reader
My new PC has an internal 16-in-1 card reader connected via USB 2.0. The
device is the Techsolo TCR-1640
(http://www.techsolo.de/product/cardreader/tcr_1640/index.php).
I boot from a compact flash inserted in it and I can mount and unmount
the same CF once the system has booted and has mounted the root
partition from my graid3 array.
The problem arise when I replace the inserted CF with another
2004 Apr 08
4
recommended SSL-friendly crypto accelerator
Hi,
I'm pondering building my own SSL accelerator out of a multi-CPU
FreeBSD system and a crypto accelerator.
What's the recommended hardware crypto accelerator card these
days?
Thanks,
==ml
--
Michael Lucas mwlucas@FreeBSD.org, mwlucas@BlackHelicopters.org
Today's chance of throwing it all away to start a goat farm: 49.1%
http://www.BlackHelicopters.org/~mwlucas/
2008 Aug 05
1
Stuck in geli
Rarely, a geli partition I have freezes a process in bufwait state. It
occurs after an ATA timeout message:
Aug 5 03:47:13 thor kernel: ad10: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=219028637
The geli partition resides on an Intel MatrixRAID RAID1 mirror using the
ICH9R chipset (Asus P5K-E/WIFI). Killing (even -9) the process does not
work. Rebooting is the only solution, yet the
2006 Sep 20
2
Status of MFC security event audit support in RELENG_6?
A few weeks back Robert Watson announced the merge of these features from 7
back into 6-STABLE. I hadn't seen any updates and was curious as to the
status. Us 6-STABLE users are curious to test it out.
Thanks.
--A
2012 Dec 17
1
WRITE_FPDMA_QUEUED CAM status: ATA Status Error
Hi,
Is there a way to tell / narrow down if an issue with errors like below
are due to a bad cable or bad port multiplier ? The disks in a
particular cage are throwing errors like these below. (RELENG9 from today)
siis0 at pci0:5:0:0: class=0x010400 card=0x71241095 chip=0x31241095
rev=0x02 hdr=0x00
vendor = 'Silicon Image, Inc.'
device = 'SiI 3124 PCI-X Serial
2006 Aug 16
1
Warning: MFC of security event audit support RELENG_6 in the next 2-3 weeks
Dear 6-STABLE users,
In the next 2-3 weeks, I plan to MFC support for CAPP security eventing
auditing from 7-CURRENT to 6-STABLE. The implementation has been running
quite nicely in -CURRENT for several months. Right now, I'm just waiting on a
confirmation from Sun regarding formal allocation of a BSM header version
number so as to avoid accidental version number conflicts in the
2006 Aug 16
1
Warning: MFC of security event audit support RELENG_6 in the next 2-3 weeks
Dear 6-STABLE users,
In the next 2-3 weeks, I plan to MFC support for CAPP security eventing
auditing from 7-CURRENT to 6-STABLE. The implementation has been running
quite nicely in -CURRENT for several months. Right now, I'm just waiting on a
confirmation from Sun regarding formal allocation of a BSM header version
number so as to avoid accidental version number conflicts in the
2008 Jun 03
0
[releng_6 tinderbox] failure on sparc64/sparc64
TB --- 2008-06-03 09:06:24 - tinderbox 2.3 running on freebsd-legacy.sentex.ca
TB --- 2008-06-03 09:06:24 - starting RELENG_6 tinderbox run for sparc64/sparc64
TB --- 2008-06-03 09:06:24 - cleaning the object tree
TB --- 2008-06-03 09:06:55 - cvsupping the source tree
TB --- 2008-06-03 09:06:55 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_6/sparc64/sparc64/supfile
TB ---