Re: ad8: TIMEOUT - WRITE_DMA errors UFS 7.0-RC1
On Sun, Mar 09, 2008 at 12:50:49AM +0100, Eilko Bos wrote: > >From the keyboard of Michael Haro, written on Sun, Jan 27, 2008 at > >12:01:03AM -0800: > > > Can anyone else using 7.0 who hasn't already (especially those using ZFS) > > > check his/her /var/log/messages for disk TIMEOUTs or other disk error > > > messages? If this is widespread, I think the chances re slim that it is a > > > hardware problem in every case. > > > > I've had this problem with Hitachi sata drives using a promise sata > > controller. > > I am using 2 160Gb Maxtor disks in geom_mirror. With 6.3 it runs fine. I > upgraded to 7.0-RELEASE and after install problems started. Disk TIMEOUTs > freezed the box as soon as I initiated a lot of disk activity (e.g. make > buildworld of building a kernel). > > I 'downgraded' the box to 6.3 again (had to rebuild the mirror because it was > touched by a newer gmirror) and now the problems have gone again. I have the > strong impression it is not hardware bot rather 7.0-RELEASE related. > Actually I want to get rid of the box at home (want to carry it to a > datacenter) > but if it can be helpfull I am willing to have it for another week or two at > home to upgrade/downgrade/etc. with it. You should consider posting the SMART stats for both /dev/ad0 and /dev/ad1 (because you didn't disclose which disk is showing problems; I assume ad0 though). You can get these by installing ports/sysutils/smartmontools and using "smartctl -a ad0" (same for ad1). This can help narrow down the problem. Confirming it's *not* a disk issue is helpful. More importantly: if the problem is easily reproducable for you under RELENG_7, you should contact Scott Long, who has offered to help track this problem down. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ad8: TIMEOUT - WRITE_DMA errors UFS 7.0-RC1
>From the keyboard of Michael Haro, written on Sun, Jan 27, 2008 at 12:01:03AM >-0800: > > Can anyone else using 7.0 who hasn't already (especially those using ZFS) > > check his/her /var/log/messages for disk TIMEOUTs or other disk error > > messages? If this is widespread, I think the chances re slim that it is a > > hardware problem in every case. > > I've had this problem with Hitachi sata drives using a promise sata > controller. I am using 2 160Gb Maxtor disks in geom_mirror. With 6.3 it runs fine. I upgraded to 7.0-RELEASE and after install problems started. Disk TIMEOUTs freezed the box as soon as I initiated a lot of disk activity (e.g. make buildworld of building a kernel). I 'downgraded' the box to 6.3 again (had to rebuild the mirror because it was touched by a newer gmirror) and now the problems have gone again. I have the strong impression it is not hardware bot rather 7.0-RELEASE related. Actually I want to get rid of the box at home (want to carry it to a datacenter) but if it can be helpfull I am willing to have it for another week or two at home to upgrade/downgrade/etc. with it. My dmesg (6.3 again): -- Copyright (c) 1992-2008 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 6.3-RELEASE #0: Wed Jan 16 04:45:45 UTC 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel Pentium III (1000.04-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x68a Stepping = 10 Features=0x383fbff real memory = 1610592256 (1535 MB) avail memory = 1564733440 (1492 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 3 cpu1 (AP): APIC ID: 0 ioapic0 irqs 0-15 on motherboard ioapic1 irqs 16-31 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) hptrr: HPT RocketRAID controller driver v1.1 (Jan 16 2008 04:43:12) acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <32-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0 cpu0: on acpi0 cpu1: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 fxp0: port 0xd800-0xd83f mem 0xfe00-0xfe000fff,0xfd80-0xfd8f at device 2.0 on pci0 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:e0:18:47:01:35 em0: port 0xd400-0xd43f mem 0xfd00-0xfd01,0xfc80-0xfc81 irq 17 at device 4.0 on pci0 em0: Ethernet address: 00:07:e9:3e:e7:90 pci0: at device 7.0 (no driver attached) isab0: port 0xe800-0xe80f at device 15.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xb800-0xb80f at device 15.1 on pci0 ata0: on atapci0 ata1: on atapci0 ohci0: mem 0xfa00-0xfa000fff irq 9 at device 15.2 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered pcib1: on acpi0 pci1: on pcib1 sym0: <1010-33> port 0xb400-0xb4ff mem 0xf980-0xf98003ff,0xf900-0xf9001fff irq 24 at device 5.0 on pci1 sym0: Symbios NVRAM, ID 7, Fast-80, LVD, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: using LOAD/STORE-based firmware. sym0: handling phase mismatch from SCRIPTS. sym0: [GIANT-LOCKED] sym1: <1010-33> port 0xb000-0xb0ff mem 0xf880-0xf88003ff,0xf800-0xf8001fff irq 25 at device 5.1 on pci1 sym1: Symbios NVRAM, ID 7, Fast-80, LVD, parity checking sym1: open drain IRQ line driver, using on-chip SRAM sym1: using LOAD/STORE-based firmware. sym1: handling phase mismatch from SCRIPTS. sym1: [GIANT-LOCKED] atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0: port 0x378-0x37f,0x778-0x77a irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 pmtimer0 on isa0 orm0: at iomem 0xc-0xc7fff,0xc8000-0xc97ff,0xcc000-0xcc7ff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounters tick every 1.000 msec hptrr: no controller detecte
Re: ad8: TIMEOUT - WRITE_DMA errors UFS 7.0-RC1
Well the problem is that things *sometimes* work... sometimes not But my backup is on a system running FreeBSD 6.3 with a promise sata controller and that one has crashed too while backing up. So I'm kind of cautious with testing. First I need some reliable storage to try to recover my data. Remco On Sun, Jan 27, 2008 at 10:27:38AM -0700, Joe Peterson wrote: > Remco van Bekkum wrote: > > Well it looks like in my case it is hardware related after all. It failed > > to read the boot > > block several times now. 2nd sort of DOA of this disk... > > Have you tried reading the block in another OS or using SeaTools? That would > at least verify that it's hardware. > > -Joe > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ad8: TIMEOUT - WRITE_DMA errors UFS 7.0-RC1
Remco van Bekkum wrote: > Well it looks like in my case it is hardware related after all. It failed to > read the boot > block several times now. 2nd sort of DOA of this disk... Have you tried reading the block in another OS or using SeaTools? That would at least verify that it's hardware. -Joe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ad8: TIMEOUT - WRITE_DMA errors UFS 7.0-RC1
Well it looks like in my case it is hardware related after all. It failed to read the boot block several times now. 2nd sort of DOA of this disk... Remco On Sat, Jan 26, 2008 at 04:28:29PM -0700, Joe Peterson wrote: > Remco van Bekkum wrote: > > Same here. On an amd64 system with 1x sata disk (Western Digital Caviar > > Green Power) on an amd690G chipset, with UFS and intensive disk activity > > the system hangs and in the end it may panic. I've csupped today and > > rebuild world & generic kernel but still it's very unstable, sometimes it > > even hangs when activating geom volumes at boot time... > > I must add that this is a new system so I'm not 100% sure the hardware is > > sane. > > Using ZFS it also crashed when doing intensive I/O. > > This is very interesting. It seems to there are several of us who are > experiencing something that *looks* like hardware (disk) issues when using > 7.0. > > Could this be related to the mouse freeze issue? Could some process be > locking/grabbing the CPU at inopportune times and causing not only the > freezing symptoms but also reads/writes problems? > > Can anyone else using 7.0 who hasn't already (especially those using ZFS) > check his/her /var/log/messages for disk TIMEOUTs or other disk error > messages? If this is widespread, I think the chances re slim that it is a > hardware problem in every case. > > -Joe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ad8: TIMEOUT - WRITE_DMA errors UFS 7.0-RC1
On Jan 26, 2008 3:28 PM, Joe Peterson <[EMAIL PROTECTED]> wrote: > Remco van Bekkum wrote: > > Same here. On an amd64 system with 1x sata disk (Western Digital Caviar > > Green Power) on an amd690G chipset, with UFS and intensive disk activity > > the system hangs and in the end it may panic. I've csupped today and > > rebuild world & generic kernel but still it's very unstable, sometimes it > > even hangs when activating geom volumes at boot time... > > I must add that this is a new system so I'm not 100% sure the hardware is > > sane. > > Using ZFS it also crashed when doing intensive I/O. > > This is very interesting. It seems to there are several of us who are > experiencing something that *looks* like hardware (disk) issues when using > 7.0. > > Could this be related to the mouse freeze issue? Could some process be > locking/grabbing the CPU at inopportune times and causing not only the > freezing symptoms but also reads/writes problems? > > Can anyone else using 7.0 who hasn't already (especially those using ZFS) > check his/her /var/log/messages for disk TIMEOUTs or other disk error > messages? If this is widespread, I think the chances re slim that it is a > hardware problem in every case. I've had this problem with Hitachi sata drives using a promise sata controller. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ad8: TIMEOUT - WRITE_DMA errors UFS 7.0-RC1
Jeremy Chadwick wrote: >> If this is widespread, I think the chances re slim that it is a >> hardware problem in every case. > > I'm in definite agreement here. I think it might be worthwhile to note > what hardware we're all using, in case there's something similar between > our systems (chipset, disk vendor, etc.). > > My system is as follows; timeouts were reported during an rsync of data > from the ZFS stripe (ad8+ad10) to a UFS2 filesystem on ad6. System > eventually panic'd after remaining deadlocked (while kernel messages > about timeouts kept printing on the console for ad6 only) for 10-15 > minutes. > > * MB: Supermicro PDSMI+ (Intel ICH7-based) > * CPU: Intel Core 2 Duo E6600 > * RAM: Corsair CM2X1024-6400 DDR2, 2GB > * ad4: WD Caviar SE WD2000JD (boot/OS) > * ad6: Seagate Barracuda 7200.10 ST3500630AS > * ad8: WD Caviar SE16 WD5000AAKS (ZFS stripe) > * ad10: WD Caviar SE16 WD5000AAKS (ZFS stripe) > * All drives are hooked up to the ICH7. > * SMART stats showed no problems on any of the drives before or after. > * RELENG_7, i386, ULE scheduler. Mine is as follows: * MB: Tyan Trinity S2099 * CPU: Pentium 4, 2.4GHz * RAM: Crucial DDR, ECC, CL2.5, Unbuffered 2GB (1/2 PC2100, 1/2 PC2700) * ad0: Seagate ST3500630A 3.AAE (1 UFS2 boot, 1 ZFS pool) * ad1: Seagate ST3160812A 3.AAH (not used by FreeBSD) * Intel ICH4 UDMA100 controller * ATI Radeon RV280 9250 * Intel PRO/1000 NIC * 7.0-RC1, i386, ULE scheduler -Joe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ad8: TIMEOUT - WRITE_DMA errors UFS 7.0-RC1
On Sat, Jan 26, 2008 at 04:28:29PM -0700, Joe Peterson wrote: > Remco van Bekkum wrote: > > Same here. On an amd64 system with 1x sata disk (Western Digital Caviar > > Green Power) on an amd690G chipset, with UFS and intensive disk activity > > the system hangs and in the end it may panic. I've csupped today and > > rebuild world & generic kernel but still it's very unstable, sometimes it > > even hangs when activating geom volumes at boot time... > > I must add that this is a new system so I'm not 100% sure the hardware is > > sane. > > Using ZFS it also crashed when doing intensive I/O. > > This is very interesting. It seems to there are several of us who are > experiencing something that *looks* like hardware (disk) issues when using > 7.0. We need Soren Schmidt and/or Xin Li to help with this situation. I really don't know what we can provide (other than hardware, which I am more than happy to donate). In my case, I was able to let the machine remain broken for 15 minutes or so, and it eventually panic'd. Of course due to PR 118255, it's becoming difficult to get a coredump. > Could this be related to the mouse freeze issue? Could some process be > locking/grabbing the CPU at inopportune times and causing not only the > freezing symptoms but also reads/writes problems? I don't use a mouse on my systems, but what you've described is possible. I'm guessing some sort of loop in the kernel (or a driver) which holds the system down for too long. > If this is widespread, I think the chances re slim that it is a > hardware problem in every case. I'm in definite agreement here. I think it might be worthwhile to note what hardware we're all using, in case there's something similar between our systems (chipset, disk vendor, etc.). My system is as follows; timeouts were reported during an rsync of data from the ZFS stripe (ad8+ad10) to a UFS2 filesystem on ad6. System eventually panic'd after remaining deadlocked (while kernel messages about timeouts kept printing on the console for ad6 only) for 10-15 minutes. * MB: Supermicro PDSMI+ (Intel ICH7-based) * CPU: Intel Core 2 Duo E6600 * RAM: Corsair CM2X1024-6400 DDR2, 2GB * ad4: WD Caviar SE WD2000JD (boot/OS) * ad6: Seagate Barracuda 7200.10 ST3500630AS * ad8: WD Caviar SE16 WD5000AAKS (ZFS stripe) * ad10: WD Caviar SE16 WD5000AAKS (ZFS stripe) * All drives are hooked up to the ICH7. * SMART stats showed no problems on any of the drives before or after. * RELENG_7, i386, ULE scheduler. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ad8: TIMEOUT - WRITE_DMA errors UFS 7.0-RC1
> Can anyone else using 7.0 who hasn't already (especially those using ZFS) > check his/her /var/log/messages for disk TIMEOUTs or other disk error > messages? If this is widespread, I think the chances re slim that it is a > hardware problem in every case. I noticed this week that I was getting DMA WRITE timeouts on two of my disks on my 7.0-RC1 box. The strange thing in my case was that only 2 of my 3 drives were exhibiting the behavior. The two having the problem were both SATA300 drives, while the third was SATA150. I jumpered the two "bad" drives to SATA150, and the timeouts went away. I replaced the motherboard, set the two drives back to SATA300 and have not had a timeout since. I was thinking maybe it was related, but in my case it was truly a hardware failure. Here were the messages, for what it's worth: Jan 23 10:05:01 pflog kernel: ad10: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=1525567 Jan 23 10:05:09 pflog kernel: ad10: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=3828159 Jan 23 10:07:27 pflog kernel: ad10: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=3450111 Jan 23 10:07:33 pflog kernel: ad10: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=4561983 Jan 23 11:30:27 pflog kernel: ad10: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=4178303 Jan 23 11:30:33 pflog kernel: ad10: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=5660287 Jan 23 11:30:39 pflog kernel: ad10: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=6805951 Jan 23 11:30:48 pflog kernel: ad10: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=9856959 Josh ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ad8: TIMEOUT - WRITE_DMA errors UFS 7.0-RC1
Remco van Bekkum wrote: > Same here. On an amd64 system with 1x sata disk (Western Digital Caviar > Green Power) on an amd690G chipset, with UFS and intensive disk activity > the system hangs and in the end it may panic. I've csupped today and > rebuild world & generic kernel but still it's very unstable, sometimes it > even hangs when activating geom volumes at boot time... > I must add that this is a new system so I'm not 100% sure the hardware is > sane. > Using ZFS it also crashed when doing intensive I/O. This is very interesting. It seems to there are several of us who are experiencing something that *looks* like hardware (disk) issues when using 7.0. Could this be related to the mouse freeze issue? Could some process be locking/grabbing the CPU at inopportune times and causing not only the freezing symptoms but also reads/writes problems? Can anyone else using 7.0 who hasn't already (especially those using ZFS) check his/her /var/log/messages for disk TIMEOUTs or other disk error messages? If this is widespread, I think the chances re slim that it is a hardware problem in every case. -Joe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ad8: TIMEOUT - WRITE_DMA errors UFS 7.0-RC1
Same here. On an amd64 system with 1x sata disk (Western Digital Caviar Green Power) on an amd690G chipset, with UFS and intensive disk activity the system hangs and in the end it may panic. I've csupped today and rebuild world & generic kernel but still it's very unstable, sometimes it even hangs when activating geom volumes at boot time... I must add that this is a new system so I'm not 100% sure the hardware is sane. Using ZFS it also crashed when doing intensive I/O. I can supply additional info later if that may help. Cheers, Remco On Sat, Jan 26, 2008 at 10:54:17PM +0100, Nikolaj Farrell wrote: > After upgrading from RELENG_6_2 to 7.0-RC1 I am experiencing system > becoming unresponsive during intensive disk operations. Only solution is > a power off. These hangs occured pretty much within a few hours of first > running 7.0-RC1. 6.2R was fine. I am not running ZFS. > > The hangs are easy to reproduce by an unrar of an archive ~4.4GB. The > system will not hang during "normal" operations. > > Below are the errors I get, output from dmesg, atacontrol cap and > smartctl tests. (The long test is aborted below, but as indicated > previously completed without errors) > > These are the errors: > --- > Jan 26 19:55:36 athlon kernel: ad8: WARNING - SETFEATURES SET TRANSFER > MODE taskqueue timeout - completing request directly > Jan 26 19:55:36 athlon kernel: ad8: WARNING - SETFEATURES ENABLE RCACHE > taskqueue timeout - completing request directly > Jan 26 19:55:36 athlon kernel: ad8: WARNING - SETFEATURES ENABLE WCACHE > taskqueue timeout - completing request directly > Jan 26 19:55:36 athlon kernel: ad8: WARNING - SET_MULTI taskqueue > timeout - completing request directly > Jan 26 19:55:36 athlon kernel: ad8: TIMEOUT - WRITE_DMA retrying (1 > retry left) LBA=2415 > Jan 26 19:55:36 athlon kernel: ad8: WARNING - SETFEATURES SET TRANSFER > MODE taskqueue timeout - completing request directly > Jan 26 19:55:36 athlon kernel: ad8: WARNING - SETFEATURES SET TRANSFER > MODE taskqueue timeout - completing request directly > Jan 26 19:55:36 athlon kernel: ad8: WARNING - SETFEATURES ENABLE RCACHE > taskqueue timeout - completing request directly > Jan 26 19:55:36 athlon kernel: ad8: WARNING - SETFEATURES ENABLE WCACHE > taskqueue timeout - completing request directly > Jan 26 19:55:36 athlon kernel: ad8: WARNING - SET_MULTI taskqueue > timeout - completing request directly > Jan 26 19:55:36 athlon kernel: ad8: TIMEOUT - WRITE_DMA retrying (1 > retry left) LBA=2543 > --- > and so on... > > This computer has only the one SATA hard drive. > dmesg info: > atapci1: port > 0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc807,0xc480-0xc483,0xc400-0xc40f,0xc000-0xc0ff > > irq 21 at device 15.0 on pci0 > atapci1: [ITHREAD] > ata4: on atapci1 > ad8: 238475MB at ata4-master SATA150 > > --- > > atacontrol cap ad8 > > Protocol Serial ATA II > device model SAMSUNG SP2504C > serial number S09QJ1CP201268 > firmware revision VT100-50 > cylinders 16383 > heads 16 > sectors/track 63 > lba supported 268435455 sectors > lba48 supported 488397168 sectors > dma supported > overlap not supported > > Feature Support EnableValue Vendor > write cacheyes yes > read ahead yes yes > Native Command Queuing (NCQ) yes - 31/0x1F > Tagged Command Queuing (TCQ) no no 31/0x1F > SMART yes yes > microcode download yes yes > security yes no > power management yes yes > advanced power management no no 0/0x00 > automatic acoustic management yes no 0/0x00 254/0xFE > > --- > smartctl -a /dev/ad8: > > === START OF INFORMATION SECTION === > Model Family: SAMSUNG SpinPoint P120 series > Device Model: SAMSUNG SP2504C > Serial Number:S09QJ1CP201268 > Firmware Version: VT100-50 > User Capacity:250 059 350 016 bytes > Device is:In smartctl database [for details use: -P show] > ATA Version is: 7 > ATA Standard is: ATA/ATAPI-7 T13 1532D revision 4a > Local Time is:Sat Jan 26 22:44:43 2008 CET > SMART support is: Available - device has SMART capability. > SMART support is: Enabled > > === START OF READ SMART DATA SECTION === > SMART overall-health self-assessment test result: PASSED > > General SMART Values: > Offline data collection status: (0x02) Offline data collection activity > was completed without error. > Auto Offline Data Collection: > Disabled. > Self-test execution status: ( 25) The self-test routine was aborted by > the host. > Total time to complete Offline > data collection: (5028) seconds. > Offline data collection > capabilities:
