Re: File system corruption with ATA RAID-1 on 6-STABLE
Seán C. Farley schrieb: On Wed, 21 Dec 2005, Brian Fundakowski Feldman wrote: On Sat, Nov 19, 2005 at 12:06:00PM -0600, Seán C. Farley wrote: I installed 6.0 on a system with two SATA drives in RAID-1. 5.4 is installed on a standard IDE channel. All appeared to work well until sometime after updating the system to 6-STABLE, installing the Nvidia driver and copying a lot of data (mainly ogg files) from my old hard drive onto it. I started seeing a multitude of READ_DMA (or maybe WRITE_DMA) errors in /var/log/messages. The system was beginning to slow down a lot, so I rebooted. Since then I have been unable to keep it up without a panic after an fsck in single-user mode. I realize this does not tell much, but just when ld.so.hints is being removed due to being corrupt the follow panic appears: Panic: ffs_valloc: dup alloc The panic may just be from a system that is too corrupted. I am amazed it still boots. That's how it appears, yeah. What does the drive health look like? Seems most like a chipset bug or nvidia driver bug, but could be things are just coinciding with drive or drive controller failure. I have since reinstalled and have been unable to reproduce the problem. 6-STABLE as of November 28 works without any obvious problems. I have also used the Nvidia driver v8174 and v8178. I do see this in messages (only one): Dec 16 02:31:46 thor kernel: ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=195511730 I am also attaching the information about my SATA drives (from smartctl). The first drive (ad4) has three errors logged. Seán smartctl version 5.33 [i386-portbld-freebsd6.0] Copyright (C) 2002-4 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: ST3160827AS Serial Number:4MT0L7EY Firmware Version: 3.42 User Capacity:160,041,885,696 bytes Device is:Not in smartctl database [for details use: -P showall] ATA Version is: 6 ATA Standard is: ATA/ATAPI-6 T13 1410D revision 2 Local Time is:Thu Dec 29 15:08:26 2005 CST 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: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 430) seconds. Offline data collection capabilities:(0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities:(0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability:(0x01) Error logging supported. No General Purpose Logging support. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time:( 94) minutes. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 057 046 006Pre-fail Always - 66158687 3 Spin_Up_Time0x0003 099 099 000Pre-fail Always - 0 4 Start_Stop_Count0x0032 100 100 020Old_age Always - 3 5 Reallocated_Sector_Ct 0x0033 099 099 036Pre-fail Always - 46 7 Seek_Error_Rate 0x000f 083 060 030Pre-fail Always - 210711557 9 Power_On_Hours 0x0032 096 096 000Old_age Always - 3673 10 Spin_Retry_Count0x0013 100 100 097Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020Old_age Always - 3 194 Temperature_Celsius 0x0022 030 040 000Old_age Always - 30 (Lifetime Min/Max 0/21) 195 Hardware_ECC_Recovered 0x001a 057 046 000Old_age Always -
Re: File system corruption with ATA RAID-1 on 6-STABLE
On Wed, 21 Dec 2005, Brian Fundakowski Feldman wrote: On Sat, Nov 19, 2005 at 12:06:00PM -0600, Seán C. Farley wrote: I installed 6.0 on a system with two SATA drives in RAID-1. 5.4 is installed on a standard IDE channel. All appeared to work well until sometime after updating the system to 6-STABLE, installing the Nvidia driver and copying a lot of data (mainly ogg files) from my old hard drive onto it. I started seeing a multitude of READ_DMA (or maybe WRITE_DMA) errors in /var/log/messages. The system was beginning to slow down a lot, so I rebooted. Since then I have been unable to keep it up without a panic after an fsck in single-user mode. I realize this does not tell much, but just when ld.so.hints is being removed due to being corrupt the follow panic appears: Panic: ffs_valloc: dup alloc The panic may just be from a system that is too corrupted. I am amazed it still boots. That's how it appears, yeah. What does the drive health look like? Seems most like a chipset bug or nvidia driver bug, but could be things are just coinciding with drive or drive controller failure. I have since reinstalled and have been unable to reproduce the problem. 6-STABLE as of November 28 works without any obvious problems. I have also used the Nvidia driver v8174 and v8178. I do see this in messages (only one): Dec 16 02:31:46 thor kernel: ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=195511730 I am also attaching the information about my SATA drives (from smartctl). The first drive (ad4) has three errors logged. Seán -- [EMAIL PROTECTED]smartctl version 5.33 [i386-portbld-freebsd6.0] Copyright (C) 2002-4 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: ST3160827AS Serial Number:4MT0L7EY Firmware Version: 3.42 User Capacity:160,041,885,696 bytes Device is:Not in smartctl database [for details use: -P showall] ATA Version is: 6 ATA Standard is: ATA/ATAPI-6 T13 1410D revision 2 Local Time is:Thu Dec 29 15:08:26 2005 CST 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: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 430) seconds. Offline data collection capabilities:(0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities:(0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability:(0x01) Error logging supported. No General Purpose Logging support. Short self-test routine recommended polling time:( 1) minutes. Extended self-test routine recommended polling time:( 94) minutes. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 057 046 006Pre-fail Always - 66158687 3 Spin_Up_Time0x0003 099 099 000Pre-fail Always - 0 4 Start_Stop_Count0x0032 100 100 020Old_age Always - 3 5 Reallocated_Sector_Ct 0x0033 099 099 036Pre-fail Always - 46 7 Seek_Error_Rate 0x000f 083 060 030Pre-fail Always - 210711557 9 Power_On_Hours 0x0032 096 096 000Old_age Always - 3673 10 Spin_Retry_Count0x0013 100 100 097Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020Old_age Always - 3 194 Temperature_Celsius 0x0022 030 040 000Old_age Always - 30 (Lifetime Min/Max 0/21) 195 Hardware_ECC_Recovered 0x001a 057 046 000Old_age Always
Re: File system corruption with ATA RAID-1 on 6-STABLE
On Sat, Nov 19, 2005 at 12:06:00PM -0600, Seán C. Farley wrote: I installed 6.0 on a system with two SATA drives in RAID-1. 5.4 is installed on a standard IDE channel. All appeared to work well until sometime after updating the system to 6-STABLE, installing the Nvidia driver and copying a lot of data (mainly ogg files) from my old hard drive onto it. I started seeing a multitude of READ_DMA (or maybe WRITE_DMA) errors in /var/log/messages. The system was beginning to slow down a lot, so I rebooted. Since then I have been unable to keep it up without a panic after an fsck in single-user mode. I realize this does not tell much, but just when ld.so.hints is being removed due to being corrupt the follow panic appears: Panic: ffs_valloc: dup alloc The panic may just be from a system that is too corrupted. I am amazed it still boots. That's how it appears, yeah. What does the drive health look like? Seems most like a chipset bug or nvidia driver bug, but could be things are just coinciding with drive or drive controller failure. -- Brian Fundakowski Feldman \'[ FreeBSD ]''\ [EMAIL PROTECTED] \ The Power to Serve! \ Opinions expressed are my own. \,,\ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
File system corruption with ATA RAID-1 on 6-STABLE
I installed 6.0 on a system with two SATA drives in RAID-1. 5.4 is installed on a standard IDE channel. All appeared to work well until sometime after updating the system to 6-STABLE, installing the Nvidia driver and copying a lot of data (mainly ogg files) from my old hard drive onto it. I started seeing a multitude of READ_DMA (or maybe WRITE_DMA) errors in /var/log/messages. The system was beginning to slow down a lot, so I rebooted. Since then I have been unable to keep it up without a panic after an fsck in single-user mode. I realize this does not tell much, but just when ld.so.hints is being removed due to being corrupt the follow panic appears: Panic: ffs_valloc: dup alloc The panic may just be from a system that is too corrupted. I am amazed it still boots. I am not sure if it is -STABLE or -RELEASE where the problem really started since I did not copy anything over until everything look good. I did not lose anything important, so I do not need to save anything. How should I proceed or does anyone know if this is a known problem? I am able to mount the partitions within the 5.4 system without issue. Possible related PR's: i386/75531 (http://www.freebsd.org/cgi/query-pr.cgi?pr=i386/75531) kern/89069 (http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/89069) Other oddities: 1. /var/log/messages showed some messages from my 5.4 system at first. Are those stored in the BIOS? 2. While copying the data over, I noticed the system running slower and slower. This may have been from all the messages being saved into messages about READ_DMA. Configuration: ASUS A7V880 atapci0: VIA 6420 SATA150 controller port 0xeff0-0xeff7,0xefe4-0xefe7,0xefa8-0xefaf,0xefe0-0xefe3,0xef90-0xef9f, 0xe800-0xe8ff irq 20 at device 15.0 on pci0 ad4: 152627MB Seagate ST3160827AS 3.42 at ata2-master SATA150 ad6: 152627MB Seagate ST3160827AS 3.42 at ata3-master SATA150 ar0: 152627MB VIA Tech V-RAID RAID1 status: READY ar0: disk0 READY (master) using ad4 at ata2-master ar0: disk1 READY (mirror) using ad6 at ata3-master Seán -- [EMAIL PROTECTED]___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
