Re: TIMEOUT - WRITE_DMA errors
Run diagnostics from Dell and from the hard drive manufacturer. -Derek At 07:32 AM 8/25/2006, [EMAIL PROTECTED] wrote: Hi: I just installed FreeBSD 6.1 on a new Dell desktop that's going to act as a temporary server while I migrate two older servers (4.10-STABLE) over to all new software, the reconfigure it to act as a remote amanda server when that's complete. I've noticed a bunch of these errors in the syslog: Aug 25 11:15:15 testbed kernel: ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=29736031 Aug 25 11:27:09 testbed kernel: ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=12168863 Aug 25 11:30:15 testbed kernel: ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=8026047 Aug 25 11:50:24 testbed kernel: ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=29736031 I did some googling, and found some seem to think it could be a problem with the disk, whereas others think it's nothing. Before I put this thing into production, even if it's only going to be there for a couple of days, I'd like to make sure. Please reply directly, as I am not subscribed. Thanks! James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am = ___ 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. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: TIMEOUT - WRITE_DMA errors
[EMAIL PROTECTED] wrote: Hi: I just installed FreeBSD 6.1 on a new Dell desktop that's going to act as a temporary server while I migrate two older servers (4.10-STABLE) over to all new software, the reconfigure it to act as a remote amanda server when that's complete. I've noticed a bunch of these errors in the syslog: Aug 25 11:15:15 testbed kernel: ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=29736031 Aug 25 11:27:09 testbed kernel: ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=12168863 Aug 25 11:30:15 testbed kernel: ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=8026047 Aug 25 11:50:24 testbed kernel: ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=29736031 I did some googling, and found some seem to think it could be a problem with the disk, whereas others think it's nothing. Before I put this thing into production, even if it's only going to be there for a couple of days, I'd like to make sure. Please reply directly, as I am not subscribed. I have a stack of SATA drives that all exhibited that behavior just prior to barfing on three mail toasters and a web server. I think I changed 8 drives in 10 months (all new servers). We went back to only ordering SCSI now for production servers. SATA might be nice for gamers and desktops, but I would not use them for heavy activity production such as mail queues. Yes, we went back and forth with the supplier, cables, connections, vibration, NOC temperature, etc. The replacements would still fail within a few months. We since replaced the Maxtor and Fitzy drives with a specific model Seagate which seems to survive. Just one guys 2cents worth. DAve -- Three years now I've asked Google why they don't have a logo change for Memorial Day. Why do they choose to do logos for other non-international holidays, but nothing for Veterans? Maybe they forgot who made that choice possible. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: AARRRGGHHH! (was Re: TIMEOUT - WRITE_DMA errors in security output)
On 09/03/04 09:53 PM, Louis LeBlanc sat at the `puter and typed: > On 09/02/04 08:56 PM, Louis LeBlanc sat at the `puter and typed: > > Just for the record, that was definitely the wrong command. > > Had to boot to another kernel again. Lots of corruption on the root > partition. Non-recoverable. Starting from scratch. Anyone have any pointers for 5.2.1 on a Dell Dimension 8300? Thanks Lou -- Louis LeBlanc [EMAIL PROTECTED] Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://www.keyslapper.org ԿԬ Law of the Perversity of Nature: You cannot determine beforehand which side of the bread to butter. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: AARRRGGHHH! (was Re: TIMEOUT - WRITE_DMA errors in security output)
On 09/02/04 08:56 PM, Louis LeBlanc sat at the `puter and typed: > > The ata controller(s) are, from the /var/run/dmesg.boot: > > atapci0: port > 0xffa0-0xffaf,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 mem > 0xfebffc00-0xfebf irq 18 at device 31.1 on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata0: [MPSAFE] > ata1: at 0x170 irq 15 on atapci0 > ata1: [MPSAFE] > atapci1: port > 0xfea0-0xfeaf,0xfe30-0xfe33,0xfe20-0xfe27,0xfe10-0xfe13,0xfe00-0xfe07 irq 18 at > device 31.2 on pci0 > atapci1: [MPSAFE] > ata2: at 0xfe00 on atapci1 > ata2: [MPSAFE] > ata3: at 0xfe20 on atapci1 > ata3: [MPSAFE] > > I *think* it's an Intel MB, but I don't know which one. The machine > is a Dell Dimension 8300 if that helps, and the drive is 160 Gig. > > atacontrol gives the following info: > # atacontrol info 0 > Master: no device present > Slave: no device present > # atacontrol info 1 > Master: acd0 ATA/ATAPI rev 5 > Slave: acd1 ATA/ATAPI rev 0 > # atacontrol info 2 > Master: ad4 ATA/ATAPI rev 6 > Slave: no device present > # atacontrol info 3 > Master: no device present > Slave: no device present > > Looks like I only have to hit channel 2 for now. > > More detail on the disk: > # atacontrol cap 2 0 > ATA channel 2, Master, device ad4: > > ATA/ATAPI revision6 > device model WDC WD1600JD-75HBB0 > serial number WD-WMAL91191824 > firmware revision 08.02D08 > cylinders 16383 > heads 16 > sectors/track 63 > lba supported 268435455 sectors > lba48 supported 31250 sectors > dma supported > overlap not supported > > Feature Support EnableValue Vendor > write cacheyes yes > read ahead yes yes > dma queued no no 0/0x00 > SMART yes yes > microcode download yes yes > security no no > power management yes yes > advanced power management no no 0/0x00 > automatic acoustic management yes no 128/0x80 128/0x80 > > Should I restart with this script, or just try the change without > rebooting? As I interpret this, the command I should use is > > /sbin/atacontrol mode 2 pio4 xxx Just for the record, that was definitely the wrong command. Had to boot to another kernel again. Lots of corruption on the root partition. Lou -- Louis LeBlanc [EMAIL PROTECTED] Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://www.keyslapper.org ԿԬ Green's Law of Debate: Anything is possible if you don't know what you're talking about. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: AARRRGGHHH! (was Re: TIMEOUT - WRITE_DMA errors in security output)
On 09/02/04 01:23 PM, Kendall Gifford sat at the `puter and typed: > On Mon, 30 Aug 2004 08:40:00 -0400, Louis LeBlanc > <[EMAIL PROTECTED]> wrote: > > Well, it's probably not an old BOIS, since the machine is less than 3 > > months old. I checked the BIOS after the system locked up, and it was > > enabled. I disabled it, and still couldn't boot until I used the > > generic kernel. > > > > Right now, the BIOS DMA is off, but the ata_dma sysctl variable is > > still setting to 1. I'll check this out for a while, and see if it > > works. If not, I'll call Dell for a new HD and cable. > > > > Well, I read part of this thread a few days ago but haven't had time > to respond until now -- sorry. Hey, I'm just glad you responded :) > I had a problem that seems to be similar if not identical to this > one about three months ago -- I emailed both freebsd-questions and > freebsd-hardware in that order and never got a response, though I've > worked around the problem. > > I had been running 4.9 in a system with a new motherboard and two > 120 GB Maxtor ATA133 drives that were also pretty new. I had also > purchased new, custom UDMA133 round cables for the drives and > everything worked just peachy under 4.9. When I upgraded to 5.2.1, > however, I had problems just like what you mentioned -- WRITE_DMA > warnings and failures whenever there was significant disk activity. > Eventually this caused one of my vinum raid plexes to go down. > > Anyhow, from researching old mailings and such I noticed that I > wasn't alone in this seemingly inexplicable problem under 5.1 and > newer. It seems some of us with drives (someone mentioned that it > seemed to be ones larger than or equal to 80 or 120 GB or something > like that) on an ATA controller like the VIA 8235 have this problem > unless you put the drive(s) into PIO mode. > > I did this (using a custom script in /usr/local/etc/rc.d that > executes the atacontrol command: /sbin/atacontrol mode 0 pio4 xxx) > for both of my ATA controllers and everything works fine. I wonder > if the ata driver just has an incompatability with my specific VIA > 8235 ata controller or something like that. > > Anyhow, what kind of motheboard/ata-controller do you have? The ata controller(s) are, from the /var/run/dmesg.boot: atapci0: port 0xffa0-0xffaf,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 mem 0xfebffc00-0xfebf irq 18 at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] atapci1: port 0xfea0-0xfeaf,0xfe30-0xfe33,0xfe20-0xfe27,0xfe10-0xfe13,0xfe00-0xfe07 irq 18 at device 31.2 on pci0 atapci1: [MPSAFE] ata2: at 0xfe00 on atapci1 ata2: [MPSAFE] ata3: at 0xfe20 on atapci1 ata3: [MPSAFE] I *think* it's an Intel MB, but I don't know which one. The machine is a Dell Dimension 8300 if that helps, and the drive is 160 Gig. atacontrol gives the following info: # atacontrol info 0 Master: no device present Slave: no device present # atacontrol info 1 Master: acd0 ATA/ATAPI rev 5 Slave: acd1 ATA/ATAPI rev 0 # atacontrol info 2 Master: ad4 ATA/ATAPI rev 6 Slave: no device present # atacontrol info 3 Master: no device present Slave: no device present Looks like I only have to hit channel 2 for now. More detail on the disk: # atacontrol cap 2 0 ATA channel 2, Master, device ad4: ATA/ATAPI revision6 device model WDC WD1600JD-75HBB0 serial number WD-WMAL91191824 firmware revision 08.02D08 cylinders 16383 heads 16 sectors/track 63 lba supported 268435455 sectors lba48 supported 31250 sectors dma supported overlap not supported Feature Support EnableValue Vendor write cacheyes yes read ahead yes yes dma queued no no 0/0x00 SMART yes yes microcode download yes yes security no no power management yes yes advanced power management no no 0/0x00 automatic acoustic management yes no 128/0x80 128/0x80 > Also, I noticed that others also recommended turning DMA mode off in > /boot/loader.conf and that you tried it and it didn't work. I also remember > reading somewhere a reason why this won't/doesn't work and that is why > I do it in a /usr/local/etc/rc.d script -- there never seems to be a problem > booting in DMA mode. Here's my pretty standard script: I did turn off DMA in the BIOS. I still saw a couple of the timeouts yesterday, but nothing so major it locked the system up. Another thing that I just remembered; when I initially installed 5.2.1-R on this machine, softupdates was on by default. I had a few incidents while building the kernel and world from updated source that caused the system to lock up even worse, and each time resulted in lost data in the /usr partition
Re: AARRRGGHHH! (was Re: TIMEOUT - WRITE_DMA errors in security output)
On Mon, 30 Aug 2004 08:40:00 -0400, Louis LeBlanc <[EMAIL PROTECTED]> wrote: > Well, it's probably not an old BOIS, since the machine is less than 3 > months old. I checked the BIOS after the system locked up, and it was > enabled. I disabled it, and still couldn't boot until I used the > generic kernel. > > Right now, the BIOS DMA is off, but the ata_dma sysctl variable is > still setting to 1. I'll check this out for a while, and see if it > works. If not, I'll call Dell for a new HD and cable. > Well, I read part of this thread a few days ago but haven't had time to respond until now -- sorry. I had a problem that seems to be similar if not identical to this one about three months ago -- I emailed both freebsd-questions and freebsd-hardware in that order and never got a response, though I've worked around the problem. I had been running 4.9 in a system with a new motherboard and two 120 GB Maxtor ATA133 drives that were also pretty new. I had also purchased new, custom UDMA133 round cables for the drives and everything worked just peachy under 4.9. When I upgraded to 5.2.1, however, I had problems just like what you mentioned -- WRITE_DMA warnings and failures whenever there was significant disk activity. Eventually this caused one of my vinum raid plexes to go down. Anyhow, from researching old mailings and such I noticed that I wasn't alone in this seemingly inexplicable problem under 5.1 and newer. It seems some of us with drives (someone mentioned that it seemed to be ones larger than or equal to 80 or 120 GB or something like that) on an ATA controller like the VIA 8235 have this problem unless you put the drive(s) into PIO mode. I did this (using a custom script in /usr/local/etc/rc.d that executes the atacontrol command: /sbin/atacontrol mode 0 pio4 xxx) for both of my ATA controllers and everything works fine. I wonder if the ata driver just has an incompatability with my specific VIA 8235 ata controller or something like that. Anyhow, what kind of motheboard/ata-controller do you have? Also, I noticed that others also recommended turning DMA mode off in /boot/loader.conf and that you tried it and it didn't work. I also remember reading somewhere a reason why this won't/doesn't work and that is why I do it in a /usr/local/etc/rc.d script -- there never seems to be a problem booting in DMA mode. Here's my pretty standard script: #!/bin/sh # case "$1" in start|restart) if [ -f /sbin/atacontrol ] && [ -x /sbin/atacontrol ]; then /sbin/atacontrol mode 0 pio4 xxx /sbin/atacontrol mode 1 pio4 xxx fi ;; stop) ;; esac P.S. Let us know what ata controller you have. O.T. Also, does anyone know why disabling DMA in /bool/loader.conf doesn't work? -- Kendall Gifford [EMAIL PROTECTED] http://www.kendallgifford.com/ +++ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: AARRRGGHHH! (was Re: TIMEOUT - WRITE_DMA errors in security output)
Although highly unlikely, but could you check your BIOS and enable DMA if there is any setting for it? Alternatively, old BIOSses are really messy about handling New hard drives. So reflashing the BIOS is also a good option if your mo'bo manufacturer offers something new. Also you did not indicate what type of cable you are using, ie 40 conductor or 80 conductor. Regards S. On Sun, 29 Aug 2004 23:16:13 -0400, Louis LeBlanc <[EMAIL PROTECTED]> wrote: > On 08/28/04 09:04 AM, Subhro sat at the `puter and typed: > > Well it is really unfortunate that hard disks don't need a reason to > > die. Maybe you are right. Are you using a 40 conductor or a 80 > > conductor cable? You can also try disabling DMA by setting the values > > displayed by sysctl -a | grep dma to 0 in /boot/loader.conf > > > > Regards > > S. > > Somehow I don't think that's going to solve my problem. After adding > the following line to loader.conf: > hw.ata.ata_dma=0 > the machine just freezes up while trying to mount the root partition. > > I managed to boot to an old kernel and fix that problem. > > Lou > -- > Louis LeBlanc [EMAIL PROTECTED] > Fully Funded Hobbyist, KeySlapper Extrordinaire :) > http://www.keyslapper.org ԿԬ > > Grief can take care of itself; but to get the full value of a joy you > must have somebody to divide it with. >-- Mark Twain > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > -- Subhro Sankha Kar School of Information Technology Block AQ-13/1 Sector V ZIP 700091 India ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
AARRRGGHHH! (was Re: TIMEOUT - WRITE_DMA errors in security output)
On 08/28/04 09:04 AM, Subhro sat at the `puter and typed: > Well it is really unfortunate that hard disks don't need a reason to > die. Maybe you are right. Are you using a 40 conductor or a 80 > conductor cable? You can also try disabling DMA by setting the values > displayed by sysctl -a | grep dma to 0 in /boot/loader.conf > > Regards > S. Somehow I don't think that's going to solve my problem. After adding the following line to loader.conf: hw.ata.ata_dma=0 the machine just freezes up while trying to mount the root partition. I managed to boot to an old kernel and fix that problem. Lou -- Louis LeBlanc [EMAIL PROTECTED] Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://www.keyslapper.org ԿԬ Grief can take care of itself; but to get the full value of a joy you must have somebody to divide it with. -- Mark Twain ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: TIMEOUT - WRITE_DMA errors in security output
Well it is really unfortunate that hard disks don't need a reason to die. Maybe you are right. Are you using a 40 conductor or a 80 conductor cable? You can also try disabling DMA by setting the values displayed by sysctl -a | grep dma to 0 in /boot/loader.conf Regards S. On Fri, 27 Aug 2004 18:47:13 -0400, Louis LeBlanc <[EMAIL PROTECTED]> wrote: > I doubt this is the problem. The disk is only a couple months old and > hasn't seen any abuse so far. > > It is also unlikely to be "goofy data cables" as suggested by another > poster. The cable is no older than the drive, and no more abused. > > Thanks all the same. > Lou > > On 08/27/04 06:18 PM, Sopov Alexey sat at the `puter and typed: > > Backup your data imediatly! > > I think your ad4 dies... > > > > > > > > LL> Hey all. I'm seeing some things I'm not comfortable with in the > > LL> security output from one of my systems - a new Dell Dimension 8300. > > > > LL> This is what I'm seeing: > > > > LL> key2.keyslapper.org kernel log messages: > > >> ad4: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=31672255 > > >> ad4: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=31672383 > > > > LL> The ad4 timeouts have happened before. They usually coincide with a > > LL> moderate to large port build. If I'm building some huge package like > > LL> OpenOffice or xorg when this happens, the whole system hangs. No > > LL> mouse, keyboard, nothing. Last time I just left it to see if things > > LL> resolved, and next morning I found it freshly rebooted. (I did > > LL> eventually get both OpenOffice and xorg built though) > > > > LL> Ad4 is a 160G hard drive with the following partitioning: > > LL> $ df -k > > LL> Filesystem 1K-blocksUsedAvail Capacity Mounted on > > LL> /dev/ad4s1a 1012974 57462 874476 6%/ > > LL> devfs 1 10 100%/dev > > LL> /dev/ad4s1h 57896520 4 53264796 0%/export > > LL> /dev/ad4s1g 60931274 2371112 53685662 4%/home > > LL> /dev/ad4s1e 10129747882 924056 1%/tmp > > LL> /dev/ad4s1f 20308398 450 1468367821%/usr > > LL> /dev/ad4s1d 8122126 85068 7387288 1%/var > > > > LL> fdisk output is: > > LL> # fdisk > > LL> *** Working on device /dev/ad4 *** > > LL> parameters extracted from in-core disklabel are: > > LL> cylinders=310019 heads=16 sectors/track=63 (1008 blks/cyl) > > > > LL> Figures below won't work with BIOS for partitions not in cyl 1 > > LL> parameters to be used for BIOS calculations are: > > LL> cylinders=310019 heads=16 sectors/track=63 (1008 blks/cyl) > > > > LL> Media sector size is 512 > > LL> Warning: BIOS sector numbering starts with sector 1 > > LL> Information from DOS bootblock is: > > LL> The data for partition 1 is: > > LL> sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) > > LL> start 63, size 312496317 (152586 Meg), flag 80 (active) > > LL> beg: cyl 0/ head 1/ sector 1; > > LL> end: cyl 1023/ head 254/ sector 63 > > LL> The data for partition 2 is: > > LL> > > LL> The data for partition 3 is: > > LL> > > LL> The data for partition 4 is: > > LL> > > > > > > LL> Any other info that would help, please let me know, but I'd like to > > LL> know what the cause could be and how to fix it. > > > > LL> TIA > > LL> Lou > > > > > > > > -- > > [ /Iexa ] mailto:[EMAIL PROTECTED] > > > > ___ > > [EMAIL PROTECTED] mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > > > > > -- > Louis LeBlanc [EMAIL PROTECTED] > Fully Funded Hobbyist, KeySlapper Extrordinaire :) > http://www.keyslapper.org ԿԬ > > I object to intellect without discipline; I object to power without > constructive purpose. >-- Spock, "The Squire of Gothos", stardate 2124.5 > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > -- Subhro Sankha Kar School of Information Technology Block AQ-13/1 Sector V ZIP 700091 India ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: TIMEOUT - WRITE_DMA errors in security output
I doubt this is the problem. The disk is only a couple months old and hasn't seen any abuse so far. It is also unlikely to be "goofy data cables" as suggested by another poster. The cable is no older than the drive, and no more abused. Thanks all the same. Lou On 08/27/04 06:18 PM, Sopov Alexey sat at the `puter and typed: > Backup your data imediatly! > I think your ad4 dies... > > > > LL> Hey all. I'm seeing some things I'm not comfortable with in the > LL> security output from one of my systems - a new Dell Dimension 8300. > > LL> This is what I'm seeing: > > LL> key2.keyslapper.org kernel log messages: > >> ad4: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=31672255 > >> ad4: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=31672383 > > LL> The ad4 timeouts have happened before. They usually coincide with a > LL> moderate to large port build. If I'm building some huge package like > LL> OpenOffice or xorg when this happens, the whole system hangs. No > LL> mouse, keyboard, nothing. Last time I just left it to see if things > LL> resolved, and next morning I found it freshly rebooted. (I did > LL> eventually get both OpenOffice and xorg built though) > > LL> Ad4 is a 160G hard drive with the following partitioning: > LL> $ df -k > LL> Filesystem 1K-blocksUsedAvail Capacity Mounted on > LL> /dev/ad4s1a 1012974 57462 874476 6%/ > LL> devfs 1 10 100%/dev > LL> /dev/ad4s1h 57896520 4 53264796 0%/export > LL> /dev/ad4s1g 60931274 2371112 53685662 4%/home > LL> /dev/ad4s1e 10129747882 924056 1%/tmp > LL> /dev/ad4s1f 20308398 450 1468367821%/usr > LL> /dev/ad4s1d 8122126 85068 7387288 1%/var > > LL> fdisk output is: > LL> # fdisk > LL> *** Working on device /dev/ad4 *** > LL> parameters extracted from in-core disklabel are: > LL> cylinders=310019 heads=16 sectors/track=63 (1008 blks/cyl) > > LL> Figures below won't work with BIOS for partitions not in cyl 1 > LL> parameters to be used for BIOS calculations are: > LL> cylinders=310019 heads=16 sectors/track=63 (1008 blks/cyl) > > LL> Media sector size is 512 > LL> Warning: BIOS sector numbering starts with sector 1 > LL> Information from DOS bootblock is: > LL> The data for partition 1 is: > LL> sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) > LL> start 63, size 312496317 (152586 Meg), flag 80 (active) > LL> beg: cyl 0/ head 1/ sector 1; > LL> end: cyl 1023/ head 254/ sector 63 > LL> The data for partition 2 is: > LL> > LL> The data for partition 3 is: > LL> > LL> The data for partition 4 is: > LL> > > > LL> Any other info that would help, please let me know, but I'd like to > LL> know what the cause could be and how to fix it. > > LL> TIA > LL> Lou > > > > -- > [ /Iexa ] mailto:[EMAIL PROTECTED] > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > -- Louis LeBlanc [EMAIL PROTECTED] Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://www.keyslapper.org ԿԬ I object to intellect without discipline; I object to power without constructive purpose. -- Spock, "The Squire of Gothos", stardate 2124.5 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: TIMEOUT - WRITE_DMA errors in security output
Backup your data imediatly! I think your ad4 dies... LL> Hey all. I'm seeing some things I'm not comfortable with in the LL> security output from one of my systems - a new Dell Dimension 8300. LL> This is what I'm seeing: LL> key2.keyslapper.org kernel log messages: >> ad4: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=31672255 >> ad4: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=31672383 LL> The ad4 timeouts have happened before. They usually coincide with a LL> moderate to large port build. If I'm building some huge package like LL> OpenOffice or xorg when this happens, the whole system hangs. No LL> mouse, keyboard, nothing. Last time I just left it to see if things LL> resolved, and next morning I found it freshly rebooted. (I did LL> eventually get both OpenOffice and xorg built though) LL> Ad4 is a 160G hard drive with the following partitioning: LL> $ df -k LL> Filesystem 1K-blocksUsedAvail Capacity Mounted on LL> /dev/ad4s1a 1012974 57462 874476 6%/ LL> devfs 1 10 100%/dev LL> /dev/ad4s1h 57896520 4 53264796 0%/export LL> /dev/ad4s1g 60931274 2371112 53685662 4%/home LL> /dev/ad4s1e 10129747882 924056 1%/tmp LL> /dev/ad4s1f 20308398 450 1468367821%/usr LL> /dev/ad4s1d 8122126 85068 7387288 1%/var LL> fdisk output is: LL> # fdisk LL> *** Working on device /dev/ad4 *** LL> parameters extracted from in-core disklabel are: LL> cylinders=310019 heads=16 sectors/track=63 (1008 blks/cyl) LL> Figures below won't work with BIOS for partitions not in cyl 1 LL> parameters to be used for BIOS calculations are: LL> cylinders=310019 heads=16 sectors/track=63 (1008 blks/cyl) LL> Media sector size is 512 LL> Warning: BIOS sector numbering starts with sector 1 LL> Information from DOS bootblock is: LL> The data for partition 1 is: LL> sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) LL> start 63, size 312496317 (152586 Meg), flag 80 (active) LL> beg: cyl 0/ head 1/ sector 1; LL> end: cyl 1023/ head 254/ sector 63 LL> The data for partition 2 is: LL> LL> The data for partition 3 is: LL> LL> The data for partition 4 is: LL> LL> Any other info that would help, please let me know, but I'd like to LL> know what the cause could be and how to fix it. LL> TIA LL> Lou -- [ /Iexa ] mailto:[EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: TIMEOUT - WRITE_DMA errors in security output
Goofy drive data cables? Regards S. On Fri, 27 Aug 2004 09:13:01 -0400, Louis LeBlanc <[EMAIL PROTECTED]> wrote: > Hey all. I'm seeing some things I'm not comfortable with in the > security output from one of my systems - a new Dell Dimension 8300. > > This is what I'm seeing: > > key2.keyslapper.org kernel log messages: > > ad4: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=31672255 > > ad4: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=31672383 > > The ad4 timeouts have happened before. They usually coincide with a > moderate to large port build. If I'm building some huge package like > OpenOffice or xorg when this happens, the whole system hangs. No > mouse, keyboard, nothing. Last time I just left it to see if things > resolved, and next morning I found it freshly rebooted. (I did > eventually get both OpenOffice and xorg built though) > > Ad4 is a 160G hard drive with the following partitioning: > $ df -k > Filesystem 1K-blocksUsedAvail Capacity Mounted on > /dev/ad4s1a 1012974 57462 874476 6%/ > devfs 1 10 100%/dev > /dev/ad4s1h 57896520 4 53264796 0%/export > /dev/ad4s1g 60931274 2371112 53685662 4%/home > /dev/ad4s1e 10129747882 924056 1%/tmp > /dev/ad4s1f 20308398 450 1468367821%/usr > /dev/ad4s1d 8122126 85068 7387288 1%/var > > fdisk output is: > # fdisk > *** Working on device /dev/ad4 *** > parameters extracted from in-core disklabel are: > cylinders=310019 heads=16 sectors/track=63 (1008 blks/cyl) > > Figures below won't work with BIOS for partitions not in cyl 1 > parameters to be used for BIOS calculations are: > cylinders=310019 heads=16 sectors/track=63 (1008 blks/cyl) > > Media sector size is 512 > Warning: BIOS sector numbering starts with sector 1 > Information from DOS bootblock is: > The data for partition 1 is: > sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) >start 63, size 312496317 (152586 Meg), flag 80 (active) >beg: cyl 0/ head 1/ sector 1; >end: cyl 1023/ head 254/ sector 63 > The data for partition 2 is: > > The data for partition 3 is: > > The data for partition 4 is: > > > Any other info that would help, please let me know, but I'd like to > know what the cause could be and how to fix it. > > TIA > Lou > -- > Louis LeBlanc [EMAIL PROTECTED] > Fully Funded Hobbyist, KeySlapper Extrordinaire :) > http://www.keyslapper.org ԿԬ > > Pudder's Law: > Anything that begins well will end badly. > (Note: The converse of Pudder's law is not true.) > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > -- Subhro Sankha Kar School of Information Technology Block AQ-13/1 Sector V ZIP 700091 India ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
