[SOLVED] Raid drives randomly unmount and remount at a new device location
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Raid drives randomly unmount and remount at a new device location
Running a file server that I added 2 sata drives in soft raid1 via a dedicated sata card.
About every 7-10 days the server loses track of the drives and remounts them to new device location... higher up. AKA: sdg would be come sdi and sdh would become sdj. In the process the server fails one of the drives in the raid set.
When I reboot the server the drives go back to there original locations. And I can re-add the failed drive to the raid set. I have not had any data lose and the drives checkout clean with no errors.
I have a raid5 array on the same system that is rock solid and never glitches during all of this.
Has anyone else had a similar issue?
Below is the system event log:
Code:
Feb 9 08:15:31 hostserver kernel: ata8: hard resetting link
Feb 9 08:15:38 hostserver kernel: ata8: link is slow to respond, please be patient (ready=0)
Feb 9 08:15:41 hostserver kernel: ata8: softreset failed (device not ready)
Feb 9 08:15:41 hostserver kernel: ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Feb 9 08:15:46 hostserver kernel: ata8.00: qc timeout (cmd 0xec)
Feb 9 08:15:46 hostserver kernel: ata8.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Feb 9 08:15:46 hostserver kernel: ata8.00: revalidation failed (errno=-5)
Feb 9 08:15:46 hostserver kernel: ata8: hard resetting link
Feb 9 08:15:53 hostserver kernel: ata8: link is slow to respond, please be patient (ready=0)
Feb 9 08:15:56 hostserver kernel: ata8: softreset failed (device not ready)
Feb 9 08:15:56 hostserver kernel: ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Feb 9 08:16:06 hostserver kernel: ata8.00: qc timeout (cmd 0xec)
Feb 9 08:16:06 hostserver kernel: ata8.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Feb 9 08:16:06 hostserver kernel: ata8.00: revalidation failed (errno=-5)
Feb 9 08:16:06 hostserver kernel: ata8: limiting SATA link speed to 1.5 Gbps
Feb 9 08:16:06 hostserver kernel: ata8: hard resetting link
Feb 9 08:16:13 hostserver kernel: ata8: link is slow to respond, please be patient (ready=0)
Feb 9 08:16:16 hostserver kernel: ata8: softreset failed (device not ready)
Feb 9 08:16:16 hostserver kernel: ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Feb 9 08:16:26 hostserver kernel: ata8.00: failed to IDENTIFY (I/O error, err_mask=0x100)
Feb 9 08:16:26 hostserver kernel: ata8.00: revalidation failed (errno=-5)
Feb 9 08:16:26 hostserver kernel: ata8.00: disabled
Feb 9 08:16:26 hostserver kernel: ata8.00: device reported invalid CHS sector 0
Feb 9 08:16:26 hostserver kernel: ata8: exception Emask 0x10 SAct 0x0 SErr 0x990000 action 0xe frozen t4
Feb 9 08:16:26 hostserver kernel: ata8: irq_stat 0x00400000, PHY RDY changed
Feb 9 08:16:26 hostserver kernel: ata8: SError: { PHYRdyChg 10B8B Dispar LinkSeq }
Feb 9 08:16:26 hostserver kernel: ata8: hard resetting link
Feb 9 08:16:33 hostserver kernel: ata8: link is slow to respond, please be patient (ready=0)
Feb 9 08:16:34 hostserver kernel: ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Feb 9 08:16:34 hostserver kernel: ata8.00: ATA-8: WDC WD1001FALS-00J7B0, 05.00K05, max UDMA/133
Feb 9 08:16:34 hostserver kernel: ata8.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
Feb 9 08:16:34 hostserver kernel: ata8.00: configured for UDMA/133
Feb 9 08:16:34 hostserver kernel: end_request: I/O error, dev sdh, sector 1776355031
Feb 9 08:16:34 hostserver kernel: md: super_written gets error=-5, uptodate=0
Feb 9 08:16:34 hostserver kernel: raid1: Disk failure on sdh5, disabling device.
Feb 9 08:16:34 hostserver kernel: raid1: Operation continuing on 1 devices.
Feb 9 08:16:34 hostserver kernel: sd 7:0:0:0: rejecting I/O to offline device
Feb 9 08:16:34 hostserver kernel: sd 7:0:0:0: rejecting I/O to offline device
Feb 9 08:16:34 hostserver kernel: sd 7:0:0:0: rejecting I/O to offline device
Feb 9 08:16:34 hostserver kernel: end_request: I/O error, dev sdh, sector 1619030464
Feb 9 08:16:34 hostserver kernel: md: super_written gets error=-5, uptodate=0
Feb 9 08:16:34 hostserver kernel: raid1: Disk failure on sdh2, disabling device.
Feb 9 08:16:34 hostserver kernel: raid1: Operation continuing on 1 devices.
Feb 9 08:16:34 hostserver kernel: sd 7:0:0:0: rejecting I/O to offline device
Feb 9 08:16:34 hostserver kernel: raid1: sdh3: rescheduling sector 6273856
Feb 9 08:16:34 hostserver kernel: sd 7:0:0:0: rejecting I/O to offline device
Feb 9 08:16:34 hostserver kernel: raid1: sdh2: rescheduling sector 7047760
Feb 9 08:16:34 hostserver kernel: ata8: EH complete
Feb 9 08:16:34 hostserver kernel: ata8.00: detaching (SCSI 7:0:0:0)
Feb 9 08:16:34 hostserver kernel: sd 7:0:0:0: [sdh] Synchronizing SCSI cache
Feb 9 08:16:34 hostserver kernel: sd 7:0:0:0: [sdh] Stopping disk
Feb 9 08:16:34 hostserver kernel: scsi 7:0:0:0: Direct-Access ATA WDC WD1001FALS-0 05.0 PQ: 0 ANSI: 5
Feb 9 08:16:34 hostserver kernel: sd 7:0:0:0: [sdi] 1953525168 512-byte hardware sectors (1000205 MB)
Feb 9 08:16:34 hostserver kernel: sd 7:0:0:0: [sdi] Write Protect is off
Feb 9 08:16:34 hostserver kernel: sd 7:0:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 9 08:16:34 hostserver kernel: sd 7:0:0:0: [sdi] 1953525168 512-byte hardware sectors (1000205 MB)
Feb 9 08:16:34 hostserver kernel: sd 7:0:0:0: [sdi] Write Protect is off
Feb 9 08:16:34 hostserver kernel: sd 7:0:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 9 08:16:36 hostserver kernel: sdi: sdi1 sdi2 sdi3 sdi4 < sdi5 sdi6 sdi7 >
Feb 9 08:16:36 hostserver kernel: sd 7:0:0:0: [sdi] Attached SCSI disk
Feb 9 08:16:36 hostserver kernel: sd 7:0:0:0: Attached scsi generic sg7 type 0
Feb 9 08:17:04 hostserver kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Feb 9 08:17:04 hostserver kernel: ata7.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Feb 9 08:17:04 hostserver kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 9 08:17:04 hostserver kernel: ata7.00: status: { DRDY }
Feb 9 08:17:04 hostserver kernel: ata7: hard resetting link
Feb 9 08:17:10 hostserver kernel: ata7: link is slow to respond, please be patient (ready=0)
Feb 9 08:17:14 hostserver kernel: ata7: softreset failed (device not ready)
Feb 9 08:17:14 hostserver kernel: ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Feb 9 08:17:19 hostserver kernel: ata7.00: qc timeout (cmd 0xec)
Feb 9 08:17:19 hostserver kernel: ata7.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Feb 9 08:17:19 hostserver kernel: ata7.00: revalidation failed (errno=-5)
Feb 9 08:17:19 hostserver kernel: ata7: hard resetting link
Feb 9 08:17:25 hostserver kernel: ata7: link is slow to respond, please be patient (ready=0)
Feb 9 08:17:29 hostserver kernel: ata7: softreset failed (device not ready)
Feb 9 08:17:29 hostserver kernel: ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Feb 9 08:17:39 hostserver kernel: ata7.00: qc timeout (cmd 0xec)
Feb 9 08:17:39 hostserver kernel: ata7.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Feb 9 08:17:39 hostserver kernel: ata7.00: revalidation failed (errno=-5)
Feb 9 08:17:39 hostserver kernel: ata7: limiting SATA link speed to 1.5 Gbps
Feb 9 08:17:39 hostserver kernel: ata7: hard resetting link
Feb 9 08:17:45 hostserver kernel: ata7: link is slow to respond, please be patient (ready=0)
Feb 9 08:17:49 hostserver kernel: ata7: softreset failed (device not ready)
Feb 9 08:17:49 hostserver kernel: ata7: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Feb 9 08:17:59 hostserver kernel: ata7.00: failed to IDENTIFY (I/O error, err_mask=0x100)
Feb 9 08:17:59 hostserver kernel: ata7.00: revalidation failed (errno=-5)
Feb 9 08:17:59 hostserver kernel: ata7.00: disabled
Feb 9 08:17:59 hostserver kernel: ata7.00: device reported invalid CHS sector 0
Feb 9 08:17:59 hostserver kernel: ata7: exception Emask 0x10 SAct 0x0 SErr 0x990000 action 0xe frozen t4
Feb 9 08:17:59 hostserver kernel: ata7: irq_stat 0x00400000, PHY RDY changed
Feb 9 08:17:59 hostserver kernel: ata7: SError: { PHYRdyChg 10B8B Dispar LinkSeq }
Feb 9 08:17:59 hostserver kernel: ata7: hard resetting link
Feb 9 08:18:05 hostserver kernel: ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Feb 9 08:18:06 hostserver kernel: ata7.00: ATA-8: WDC WD1001FALS-00J7B0, 05.00K05, max UDMA/133
Feb 9 08:18:06 hostserver kernel: ata7.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
Feb 9 08:18:06 hostserver kernel: ata7.00: configured for UDMA/133
Feb 9 08:18:06 hostserver kernel: end_request: I/O error, dev sdg, sector 1776355031
Feb 9 08:18:06 hostserver kernel: md: super_written gets error=-5, uptodate=0
Feb 9 08:18:06 hostserver kernel: sd 6:0:0:0: rejecting I/O to offline device
Feb 9 08:18:06 hostserver kernel: sd 6:0:0:0: rejecting I/O to offline device
Feb 9 08:18:06 hostserver kernel: sd 6:0:0:0: rejecting I/O to offline device
Feb 9 08:18:06 hostserver kernel: sd 6:0:0:0: rejecting I/O to offline device
Feb 9 08:18:06 hostserver kernel: end_request: I/O error, dev sdg, sector 1619030464
Feb 9 08:18:06 hostserver kernel: md: super_written gets error=-5, uptodate=0
Feb 9 08:18:06 hostserver kernel: ata7: EH complete
Feb 9 08:18:06 hostserver kernel: RAID1 conf printout:
Feb 9 08:18:06 hostserver kernel: ata7.00: detaching (SCSI 6:0:0:0)
Feb 9 08:18:06 hostserver kernel: --- wd:1 rd:2
Feb 9 08:18:06 hostserver kernel: disk 0, wo:0, o:1, dev:sdg2
Feb 9 08:18:06 hostserver kernel: disk 1, wo:1, o:0, dev:sdh2
Feb 9 08:18:06 hostserver kernel: raid1: Disk failure on sdh3, disabling device.
Feb 9 08:18:06 hostserver kernel: raid1: Operation continuing on 1 devices.
Feb 9 08:18:06 hostserver kernel: raid1: sdg3: redirecting sector 6273856 to another mirror
Feb 9 08:18:06 hostserver kernel: end_request: I/O error, dev sdg, sector 1707130924
Feb 9 08:18:06 hostserver kernel: md: super_written gets error=-5, uptodate=0
Feb 9 08:18:06 hostserver kernel: RAID1 conf printout:
Feb 9 08:18:06 hostserver kernel: --- wd:1 rd:2
Feb 9 08:18:06 hostserver kernel: disk 0, wo:0, o:1, dev:sdg3
Feb 9 08:18:06 hostserver kernel: disk 1, wo:1, o:0, dev:sdh3
Feb 9 08:18:06 hostserver kernel: sd 6:0:0:0: [sdg] Synchronizing SCSI cache
Feb 9 08:18:06 hostserver kernel: sd 6:0:0:0: [sdg] Stopping disk
Feb 9 08:18:06 hostserver kernel: RAID1 conf printout:
Feb 9 08:18:06 hostserver kernel: --- wd:1 rd:2
Feb 9 08:18:06 hostserver kernel: disk 0, wo:0, o:1, dev:sdg3
Feb 9 08:18:06 hostserver kernel: end_request: I/O error, dev sdg, sector 88100224
Feb 9 08:18:06 hostserver kernel: md: super_written gets error=-5, uptodate=0
Feb 9 08:18:06 hostserver kernel: RAID1 conf printout:
Feb 9 08:18:06 hostserver kernel: --- wd:1 rd:2
Feb 9 08:18:06 hostserver kernel: disk 0, wo:0, o:1, dev:sdg2
Feb 9 08:18:06 hostserver kernel: Buffer I/O error on device md4, logical block 784231
Feb 9 08:18:06 hostserver kernel: lost page write due to I/O error on md4
Feb 9 08:18:06 hostserver kernel: Buffer I/O error on device md4, logical block 1890184
Feb 9 08:18:06 hostserver kernel: lost page write due to I/O error on md4
Feb 9 08:18:06 hostserver kernel: Buffer I/O error on device md4, logical block 1890185
Feb 9 08:18:06 hostserver kernel: lost page write due to I/O error on md4
Feb 9 08:18:06 hostserver kernel: Buffer I/O error on device md4, logical block 1890186
Feb 9 08:18:06 hostserver kernel: lost page write due to I/O error on md4
Feb 9 08:18:06 hostserver kernel: Buffer I/O error on device md4, logical block 1890187
Feb 9 08:18:06 hostserver kernel: lost page write due to I/O error on md4
Feb 9 08:18:06 hostserver kernel: Buffer I/O error on device md4, logical block 1890188
Feb 9 08:18:06 hostserver kernel: lost page write due to I/O error on md4
Feb 9 08:18:06 hostserver kernel: Buffer I/O error on device md4, logical block 1890189
Feb 9 08:18:06 hostserver kernel: lost page write due to I/O error on md4
Feb 9 08:18:06 hostserver kernel: Buffer I/O error on device md4, logical block 1890190
Feb 9 08:18:06 hostserver kernel: lost page write due to I/O error on md4
Feb 9 08:18:06 hostserver kernel: Buffer I/O error on device md4, logical block 1890191
Feb 9 08:18:06 hostserver kernel: lost page write due to I/O error on md4
Feb 9 08:18:06 hostserver kernel: end_request: I/O error, dev sdg, sector 69223808
Feb 9 08:18:06 hostserver kernel: md: super_written gets error=-5, uptodate=0
Feb 9 08:18:06 hostserver kernel: RAID1 conf printout:
Feb 9 08:18:06 hostserver kernel: --- wd:1 rd:2
Feb 9 08:18:06 hostserver kernel: disk 0, wo:0, o:1, dev:sdg5
Feb 9 08:18:06 hostserver kernel: disk 1, wo:1, o:0, dev:sdh5
Feb 9 08:18:06 hostserver kernel: RAID1 conf printout:
Feb 9 08:18:06 hostserver kernel: --- wd:1 rd:2
Feb 9 08:18:06 hostserver kernel: disk 0, wo:0, o:1, dev:sdg5
Feb 9 08:18:06 hostserver kernel: end_request: I/O error, dev sdg, sector 69223808
Feb 9 08:18:06 hostserver kernel: md: super_written gets error=-5, uptodate=0
Feb 9 08:18:06 hostserver kernel: raid1: Disk failure on sdg6, disabling device.
Feb 9 08:18:06 hostserver kernel: raid1: Operation continuing on 1 devices.
Feb 9 08:18:06 hostserver kernel: scsi 7:0:0:0: rejecting I/O to dead device
Feb 9 08:18:06 hostserver kernel: scsi 7:0:0:0: rejecting I/O to dead device
Feb 9 08:18:06 hostserver kernel: end_request: I/O error, dev sdh, sector 69223808
Feb 9 08:18:06 hostserver kernel: md: super_written gets error=-5, uptodate=0
Feb 9 08:18:06 hostserver kernel: scsi 7:0:0:0: rejecting I/O to dead device
Feb 9 08:18:06 hostserver kernel: scsi 7:0:0:0: rejecting I/O to dead device
Feb 9 08:18:06 hostserver kernel: end_request: I/O error, dev sdh, sector 69223808
Feb 9 08:18:06 hostserver kernel: md: super_written gets error=-5, uptodate=0
Feb 9 08:18:06 hostserver kernel: scsi 7:0:0:0: rejecting I/O to dead device
Feb 9 08:18:06 hostserver kernel: scsi 7:0:0:0: rejecting I/O to dead device
Feb 9 08:18:06 hostserver kernel: end_request: I/O error, dev sdh, sector 69223808
Feb 9 08:18:06 hostserver kernel: md: super_written gets error=-5, uptodate=0
Feb 9 08:18:06 hostserver kernel: RAID1 conf printout:
Feb 9 08:18:06 hostserver kernel: --- wd:1 rd:2
Feb 9 08:18:06 hostserver kernel: disk 0, wo:1, o:0, dev:sdg6
Feb 9 08:18:06 hostserver kernel: disk 1, wo:0, o:1, dev:sdh6
Feb 9 08:18:06 hostserver kernel: RAID1 conf printout:
Feb 9 08:18:06 hostserver kernel: --- wd:1 rd:2
Feb 9 08:18:06 hostserver kernel: disk 1, wo:0, o:1, dev:sdh6
Feb 9 08:18:06 hostserver kernel: end_request: I/O error, dev sdg, sector 88100224
Feb 9 08:18:06 hostserver kernel: md: super_written gets error=-5, uptodate=0
Feb 9 08:18:06 hostserver kernel: end_request: I/O error, dev sdg, sector 88100224
Feb 9 08:18:06 hostserver kernel: md: super_written gets error=-5, uptodate=0
Feb 9 08:18:06 hostserver kernel: end_request: I/O error, dev sdg, sector 107940480
Feb 9 08:18:06 hostserver kernel: md: super_written gets error=-5, uptodate=0
Feb 9 08:18:06 hostserver kernel: raid1: Disk failure on sdg7, disabling device.
Feb 9 08:18:06 hostserver kernel: raid1: Operation continuing on 1 devices.
Feb 9 08:18:06 hostserver kernel: scsi 7:0:0:0: rejecting I/O to dead device
Feb 9 08:18:06 hostserver kernel: scsi 7:0:0:0: rejecting I/O to dead device
Feb 9 08:18:06 hostserver kernel: end_request: I/O error, dev sdh, sector 107940480
Feb 9 08:18:06 hostserver kernel: md: super_written gets error=-5, uptodate=0
Feb 9 08:18:06 hostserver kernel: scsi 7:0:0:0: rejecting I/O to dead device
Feb 9 08:18:06 hostserver kernel: scsi 7:0:0:0: rejecting I/O to dead device
Feb 9 08:18:06 hostserver kernel: end_request: I/O error, dev sdh, sector 107940480
Feb 9 08:18:06 hostserver kernel: md: super_written gets error=-5, uptodate=0
Feb 9 08:18:06 hostserver kernel: scsi 7:0:0:0: rejecting I/O to dead device
Feb 9 08:18:06 hostserver kernel: scsi 7:0:0:0: rejecting I/O to dead device
Feb 9 08:18:06 hostserver kernel: end_request: I/O error, dev sdh, sector 107940480
Feb 9 08:18:06 hostserver kernel: md: super_written gets error=-5, uptodate=0
Feb 9 08:18:06 hostserver kernel: RAID1 conf printout:
Feb 9 08:18:06 hostserver kernel: --- wd:1 rd:2
Feb 9 08:18:06 hostserver kernel: disk 0, wo:1, o:0, dev:sdg7
Feb 9 08:18:06 hostserver kernel: disk 1, wo:0, o:1, dev:sdh7
Feb 9 08:18:06 hostserver kernel: RAID1 conf printout:
Feb 9 08:18:06 hostserver kernel: --- wd:1 rd:2
Feb 9 08:18:06 hostserver kernel: disk 1, wo:0, o:1, dev:sdh7
Feb 9 08:18:06 hostserver kernel: scsi 6:0:0:0: Direct-Access ATA WDC WD1001FALS-0 05.0 PQ: 0 ANSI: 5
Feb 9 08:18:06 hostserver kernel: sd 6:0:0:0: [sdj] 1953525168 512-byte hardware sectors (1000205 MB)
Feb 9 08:18:06 hostserver kernel: sd 6:0:0:0: [sdj] Write Protect is off
Feb 9 08:18:06 hostserver kernel: sd 6:0:0:0: [sdj] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 9 08:18:06 hostserver kernel: sd 6:0:0:0: [sdj] 1953525168 512-byte hardware sectors (1000205 MB)
Feb 9 08:18:06 hostserver kernel: sd 6:0:0:0: [sdj] Write Protect is off
Feb 9 08:18:06 hostserver kernel: sd 6:0:0:0: [sdj] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
System and drive config info:
Code:
My System Information Snap Shot: 02.09.2012
Linux hostserver 2.6.27.41-170.2.117.fc10.x86_64 #1 SMP Thu Dec 10 10:36:29 EST 2009 x86_64 x86_64 x86_64 GNU/Linux
The current run level is: N 5
This system has 4 cores on 1 cpu
00:00.0 RAM memory: nVidia Corporation MCP78S [GeForce 8200] Memory Controller (rev a2)
00:01.0 ISA bridge: nVidia Corporation MCP78S [GeForce 8200] LPC Bridge (rev a2)
00:01.1 SMBus: nVidia Corporation MCP78S [GeForce 8200] SMBus (rev a1)
00:01.2 RAM memory: nVidia Corporation MCP78S [GeForce 8200] Memory Controller (rev a1)
00:01.3 Co-processor: nVidia Corporation MCP78S [GeForce 8200] Co-Processor (rev a2)
00:01.4 RAM memory: nVidia Corporation MCP78S [GeForce 8200] Memory Controller (rev a1)
00:02.0 USB Controller: nVidia Corporation MCP78S [GeForce 8200] OHCI USB 1.1 Controller (rev a1)
00:02.1 USB Controller: nVidia Corporation MCP78S [GeForce 8200] EHCI USB 2.0 Controller (rev a1)
00:04.0 USB Controller: nVidia Corporation MCP78S [GeForce 8200] OHCI USB 1.1 Controller (rev a1)
00:04.1 USB Controller: nVidia Corporation MCP78S [GeForce 8200] EHCI USB 2.0 Controller (rev a1)
00:06.0 IDE interface: nVidia Corporation MCP78S [GeForce 8200] IDE (rev a1)
00:07.0 Audio device: nVidia Corporation MCP78S [GeForce 8200] High Definition Audio (rev a1)
00:08.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Bridge (rev a1)
00:09.0 SATA controller: nVidia Corporation Device 0584 (rev a2)
00:0b.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Express Bridge (rev a1)
00:10.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Express Bridge (rev a1)
00:12.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Express Bridge (rev a1)
00:13.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Bridge (rev a1)
00:14.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Bridge (rev a1)
00:18.0 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] HyperTransport Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] Miscellaneous Control
00:18.4 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] Link Control
01:08.0 Ethernet controller: Davicom Semiconductor, Inc. Ethernet 100/10 MBit (rev 31)
02:00.0 VGA compatible controller: nVidia Corporation GeForce 8200 (rev a2)
04:00.0 SATA controller: JMicron Technologies, Inc. JMB366 AHCI/IDE (rev 02)
04:00.1 IDE interface: JMicron Technologies, Inc. JMB366 AHCI/IDE (rev 02)
05:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 14)
PROCESSOR USAGE
Linux 2.6.27.41-170.2.117.fc10.x86_64 (hostserver) 02/09/2012
12:47:27 PM CPU %user %nice %sys %iowait %irq %soft %steal %idle intr/s
12:47:27 PM all 2.66 0.01 2.11 1.97 0.04 0.11 0.00 93.10 13806.22
MEMORY USAGE
total used free shared buffers cached
Mem: 7753 5195 2557 0 963 990
-/+ buffers/cache: 3242 4511
Swap: 4988 0 4988
MemTotal: 7939648 kB
MemFree: 2619148 kB
Buffers: 986120 kB
Cached: 1014236 kB
SwapCached: 0 kB
Active: 3384528 kB
Inactive: 1615192 kB
SwapTotal: 5108616 kB
SwapFree: 5108616 kB
Dirty: 588 kB
Writeback: 0 kB
AnonPages: 2999464 kB
Mapped: 183188 kB
Slab: 153364 kB
SReclaimable: 119296 kB
SUnreclaim: 34068 kB
PageTables: 40940 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 9078440 kB
Committed_AS: 7259380 kB
VmallocTotal: 34359738367 kB
VmallocUsed: 329184 kB
VmallocChunk: 34359408807 kB
HugePages_Total: 0
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 2048 kB
DirectMap4k: 24192 kB
DirectMap2M: 2859008 kB
DirectMap1G: 5242880 kB
POWER AND TEMP USAGE
w83627ehf-isa-0a10
Adapter: ISA adapter
VCore: +1.23 V (min = +1.20 V, max = +1.33 V)
+12V: +11.99 V (min = +11.93 V, max = +12.09 V)
+3.3v AVCC: +3.33 V (min = +3.28 V, max = +3.36 V)
+3.3v VCC: +3.33 V (min = +3.28 V, max = +3.36 V)
in4: +0.95 V (min = +0.93 V, max = +1.01 V)
-5V: +1.14 V (min = +1.13 V, max = +1.25 V)
+5V: +5.09 V (min = +5.04 V, max = +5.09 V)
VSB: +3.31 V (min = +3.14 V, max = +3.47 V)
VBAT: +3.06 V (min = +3.01 V, max = +3.47 V)
+1.25V: +1.18 V (min = +1.16 V, max = +1.31 V)
Case Fan: 0 RPM (min = 0 RPM, div = 32)
CPU Fan: 2678 RPM (min = 1430 RPM, div = 8)
Aux Fan: 0 RPM (min = 0 RPM, div = 32)
Sys Temp: +73.4°F (high = +140.0°F, hyst = +136.4°F) sensor = thermistor
CPU Temp: +98.6°F (high = +179.6°F, hyst = +176.0°F) sensor = diode
AUX Temp: +117.5°F (high = +179.6°F, hyst = +176.0°F) sensor = thermistor
cpu0_vid: +1.250 V
/dev/sdg: WDC WD1001FALS-00J7B0: 91°F
/dev/sdh: WDC WD1001FALS-00J7B0: 93°F
HARD DRIVE HARDWARE INFO
/dev/sdg:
Model=WDC WD1001FALS-00J7B0 , FwRev=05.00K05, SerialNo= WD-WMATV5035240
Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=50
BuffType=unknown, BuffSize=32767kB, MaxMultSect=16, MultSect=?0?
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=1953525168
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6
AdvancedPM=no WriteCache=enabled
Drive conforms to: Unspecified: ATA/ATAPI-1,2,3,4,5,6,7
* signifies the current active mode
/dev/sdh:
Model=WDC WD1001FALS-00J7B0 , FwRev=05.00K05, SerialNo= WD-WMATV5063113
Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=50
BuffType=unknown, BuffSize=32767kB, MaxMultSect=16, MultSect=?0?
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=1953525168
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6
AdvancedPM=no WriteCache=enabled
Drive conforms to: Unspecified: ATA/ATAPI-1,2,3,4,5,6,7
* signifies the current active mode
Partitioned:
Disk /dev/sdg: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdg1 1 95296 765465088+ fd Linux raid autodetect
/dev/sdg2 95297 100780 44050230 fd Linux raid autodetect
/dev/sdg3 100781 106264 44050230 fd Linux raid autodetect
/dev/sdg4 106265 121601 123194452+ 5 Extended
/dev/sdg5 106265 110573 34612011 fd Linux raid autodetect
/dev/sdg6 110574 114882 34612011 fd Linux raid autodetect
/dev/sdg7 114883 121601 53970336 fd Linux raid autodetect
Disk /dev/sdh: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdh1 1 95296 765465088+ fd Linux raid autodetect
/dev/sdh2 95297 100780 44050230 fd Linux raid autodetect
/dev/sdh3 100781 106264 44050230 fd Linux raid autodetect
/dev/sdh4 106265 121601 123194452+ 5 Extended
/dev/sdh5 106265 110573 34612011 fd Linux raid autodetect
/dev/sdh6 110574 114882 34612011 fd Linux raid autodetect
/dev/sdh7 114883 121601 53970336 fd Linux raid autodetect
cat /etc/mdadm.conf
ARRAY /dev/md3 level=raid5 num-devices=3 UUID=c2efe398:421bff8a:7f390ee3:00f99222
spares=1 devices=/dev/sde1,/dev/sdd1,/dev/sdc1,/dev/sdb1
ARRAY /dev/md0 level=raid5 num-devices=3 UUID=1c9cb177:369b13f9:3f2980bf:cca6d225
spares=1 devices=/dev/sde2,/dev/sdd2,/dev/sdc2,/dev/sdb2
ARRAY /dev/md4 level=raid1 num-devices=2 UUID=00995434:87aa912a:0c865975:ac14234a
devices=/dev/sdh,/dev/sdg
ARRAY /dev/md1 level=raid1 num-devices=2 UUID=7f36ab75:5993f410:5d9ccd73:74a6b5fb
devices=/dev/sdh1,/dev/sdg1
ARRAY /dev/md2 level=raid1 num-devices=2 UUID=7f9c6861:867fe59e:70d30e30:71f63d61
devices=/dev/sdh2,/dev/sdg2
ARRAY /dev/md4 level=raid1 num-devices=2 UUID=d9fde136:2db4d862:080bc19a:bfcc2251
devices=/dev/sdh3,/dev/sdg3
ARRAY /dev/md5 level=raid1 num-devices=2 UUID=e160ab5c:83abe20d:f7e97c12:31ecf36a
devices=/dev/sdh5,/dev/sdg5
ARRAY /dev/md6 level=raid1 num-devices=2 UUID=8f30c212:7a0e1236:a7e20b5f:ac8931bd
devices=/dev/sdh6,/dev/sdg6
ARRAY /dev/md7 level=raid1 num-devices=2 UUID=dac1ac2a:35be7add:8b2c4b2c:cc1e7d26
devices=/dev/sdh7,/dev/sdg7
Distribution: CentOS, RHEL, Solaris 10, AIX, HP-UX
Posts: 731
Rep:
As reported in the logs the drives response to slow. Can be a firmware issue on the drive or the controller. Also possibly the driver for the card has poor quality, but i have no experience with addon sata cards.
This is the second sata card I have tried in this system. ... I purchase an Adaptec card that had its own issues. Adaptec claimed there was a known issue with their card and this drive model WD1001FALS-00J7B0. I replace with this generic card and all seemed fine accept for the remount issue.
I guess this is my answer.... never heard of this before,
Difference between Desktop edition and RAID (Enterprise) edition drives
Answer ID 1397 | Last Updated 01/19/2012
Share
Print
Email this page
Notify Me
<-- -->
Western Digital manufactures desktop edition hard drives and RAID Edition (RE) hard drives. Each type of hard drive is designed to work specifically as a stand-alone drive, or in a multi-drive RAID environment.
If you install and use a desktop edition hard drive connected to a RAID controller, the drive may not work correctly. This is caused by the normal error recovery procedure that a desktop edition hard drive uses.
NOTE Note: There are a few cases where the manufacturer of the RAID controller have designed their cards to work with specific model Desktop drives. If this is the case you would need to contact the manufacturer of that controller for any support on that drive while it is used in a RAID environment. Desktop Class Hard Drives are tested and recommended for use in consumer-type RAID applications (RAID-0 / RAID-1). For more information about using a Desktop hard drive in a RAID please see Answer ID 996: Support for WD desktop drives in a RAID 0 or RAID 1 configuration.
When an error is found on a desktop edition hard drive, the drive will enter into a deep recovery cycle to attempt to repair the error, recover the data from the problematic area, and then reallocate a dedicated area to replace the problematic area. This process can take up to 2 minutes depending on the severity of the issue. Most RAID controllers allow a very short amount of time for a hard drive to recover from an error. If a hard drive takes too long to complete this process, the drive will be dropped from the RAID array. Most RAID controllers allow from 7 to 15 seconds for error recovery before dropping a hard drive from an array. Western Digital does not recommend installing desktop edition hard drives in an enterprise environment (on a RAID controller).
Western Digital RAID edition hard drives have a feature called TLER (Time Limited Error Recovery) which stops the hard drive from entering into a deep recovery cycle. The hard drive will only spend 7 seconds to attempt to recover. This means that the hard drive will not be dropped from a RAID array. While TLER is designed for RAID environments, a drive with TLER enabled will work with no performance decrease when used in non-RAID environments.
STOP Critical: WD Caviar Black, Caviar Green, and Caviar Blue hard drives are not recommended for and are not warranted for use in RAID environments utilizing Enterprise HBAs and/or expanders and in multi-bay chassis, as they are not designed for, nor tested in, these specific types of RAID applications. For all Business Critical RAID applications, please consider WD’s Enterprise Hard Drives that are specifically designed with RAID-specific, time-limited error recovery (TLER), are tested extensively in 24x7 RAID applications, and include features like enhanced RAFF technology and thermal extended burn-in testing.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
