LinuxQuestions.org
Register a domain and help support LQ
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices



Reply
 
Search this Thread
Old 07-31-2006, 11:55 PM   #1
conquest
LQ Newbie
 
Registered: Jul 2006
Posts: 2

Rep: Reputation: 0
raid + nasty clicking drive (Fedora Core 4)


So my AMD64 with a DFI Lan Party board has been humming along for about a year now. I've got 2 drives setup as raid.

The kernel I'm running is: 2.6.14-1.1653_FC4smp

I just started hearing this NASTY clicking sound, pretty loud. I looked in /var/log/messages and there are TONS of errors. What can I do to fix this? Is it possible just to disable raid for now, get a new drive and let it re-sync? Of course I don't want to bring this server down if possible.


Jul 31 21:50:33 fencechat kernel: ata4: status=0x71 { DriveReady DeviceFault SeekComplete Error }
Jul 31 21:50:33 fencechat kernel: ata4: error=0x04 { DriveStatusError }
Jul 31 21:50:33 fencechat kernel: ata4: status=0x71 { DriveReady DeviceFault SeekComplete Error }
Jul 31 21:50:33 fencechat kernel: ata4: error=0x04 { DriveStatusError }
Jul 31 21:50:33 fencechat kernel: ata4: status=0x71 { DriveReady DeviceFault SeekComplete Error }
Jul 31 21:50:33 fencechat kernel: ata4: error=0x04 { DriveStatusError }
Jul 31 21:50:33 fencechat kernel: ata4: status=0x71 { DriveReady DeviceFault SeekComplete Error }
Jul 31 21:50:33 fencechat kernel: ata4: error=0x04 { DriveStatusError }
Jul 31 21:50:33 fencechat kernel: ata4: status=0x71 { DriveReady DeviceFault SeekComplete Error }
Jul 31 21:50:33 fencechat kernel: ata4: error=0x04 { DriveStatusError }
Jul 31 21:50:33 fencechat kernel: sd 3:0:0:0: SCSI error: return code = 0x8000002

Jul 31 21:50:33 fencechat kernel: ata4: error=0x04 { DriveStatusError }
Jul 31 21:50:33 fencechat kernel: sd 3:0:0:0: SCSI error: return code = 0x8000002
Jul 31 21:50:33 fencechat kernel: sdb: Current: sense key: Aborted Command
Jul 31 21:50:33 fencechat kernel: Additional sense: No additional sense information
Jul 31 21:50:33 fencechat kernel: end_request: I/O error, dev sdb, sector 164858863
Jul 31 21:50:33 fencechat kernel: raid1: Disk failure on sdb10, disabling device.
Jul 31 21:50:33 fencechat kernel: Operation continuing on 1 devices
Jul 31 21:50:33 fencechat kernel: RAID1 conf printout:
Jul 31 21:50:33 fencechat kernel: --- wd:1 rd:2
Jul 31 21:50:33 fencechat kernel: disk 0, wo:0, o:1, dev:sda2
Jul 31 21:50:33 fencechat kernel: disk 1, wo:1, o:0, dev:sdb10
Jul 31 21:50:33 fencechat kernel: ata4: status=0x71 { DriveReady DeviceFault SeekComplete Error }
Jul 31 21:50:33 fencechat kernel: ata4: error=0x04 { DriveStatusError }
Jul 31 21:50:33 fencechat kernel: ata4: status=0x71 { DriveReady DeviceFault SeekComplete Error }
Jul 31 21:50:33 fencechat kernel: ata4: error=0x04 { DriveStatusError }
Jul 31 21:50:33 fencechat kernel: ata4: status=0x71 { DriveReady DeviceFault SeekComplete Error }
Jul 31 21:50:33 fencechat kernel: ata4: error=0x04 { DriveStatusError }
Jul 31 21:50:33 fencechat kernel: ata4: status=0x71 { DriveReady DeviceFault SeekComplete Error }
Jul 31 21:50:33 fencechat kernel: ata4: error=0x04 { DriveStatusError }
Jul 31 21:50:33 fencechat kernel: ata4: status=0x71 { DriveReady DeviceFault SeekComplete Error }
Jul 31 21:50:33 fencechat kernel: ata4: error=0x04 { DriveStatusError }
Jul 31 21:50:33 fencechat kernel: sd 3:0:0:0: SCSI error: return code = 0x8000002
Jul 31 21:50:33 fencechat kernel: sd 3:0:0:0: SCSI error: return code = 0x8000002
Jul 31 21:50:33 fencechat kernel: sdb: Current: sense key: Aborted Command
Jul 31 21:50:33 fencechat kernel: Additional sense: No additional sense information
Jul 31 21:50:33 fencechat kernel: end_request: I/O error, dev sdb, sector 29703931
Jul 31 21:50:33 fencechat kernel: raid1: Disk failure on sdb6, disabling device.
Jul 31 21:50:33 fencechat kernel: Operation continuing on 1 devices
Jul 31 21:50:33 fencechat kernel: RAID1 conf printout:
Jul 31 21:50:33 fencechat kernel: --- wd:1 rd:2
Jul 31 21:50:33 fencechat kernel: disk 0, wo:0, o:1, dev:sda6
Jul 31 21:50:33 fencechat kernel: disk 1, wo:1, o:0, dev:sdb6
Jul 31 21:50:33 fencechat kernel: RAID1 conf printout:
Jul 31 21:50:33 fencechat kernel: --- wd:1 rd:2
Jul 31 21:50:33 fencechat kernel: disk 0, wo:0, o:1, dev:sda2
Jul 31 21:50:33 fencechat kernel: RAID1 conf printout:
Jul 31 21:50:33 fencechat kernel: --- wd:1 rd:2
Jul 31 21:50:33 fencechat kernel: disk 0, wo:0, o:1, dev:sda6
Jul 31 21:50:40 fencechat kernel: ata4: status=0x71 { DriveReady DeviceFault SeekComplete Error }
Jul 31 21:50:40 fencechat kernel: ata4: error=0x04 { DriveStatusError }
Jul 31 21:50:40 fencechat kernel: sd 3:0:0:0: SCSI error: return code = 0x8000002
Jul 31 21:50:40 fencechat kernel: sdb: Current: sense key: Aborted Command
Jul 31 21:50:40 fencechat kernel: Additional sense: No additional sense information
Jul 31 21:50:40 fencechat kernel: end_request: I/O error, dev sdb, sector 62460466
Jul 31 21:50:40 fencechat kernel: raid1: Disk failure on sdb9, disabling device.
Jul 31 21:50:40 fencechat kernel: Operation continuing on 1 devices
Jul 31 21:50:40 fencechat kernel: RAID1 conf printout:
Jul 31 21:50:40 fencechat kernel: --- wd:1 rd:2
Jul 31 21:50:40 fencechat kernel: disk 0, wo:0, o:1, dev:sda3
Jul 31 21:50:40 fencechat kernel: disk 1, wo:1, o:0, dev:sdb9
Jul 31 21:50:40 fencechat kernel: RAID1 conf printout:
Jul 31 21:50:40 fencechat kernel: --- wd:1 rd:2
Jul 31 21:50:40 fencechat kernel: disk 0, wo:0, o:1, dev:sda3
Jul 31 21:50:50 fencechat kernel: ata4: status=0x71 { DriveReady DeviceFault SeekComplete Error }
Jul 31 21:50:50 fencechat kernel: ata4: error=0x04 { DriveStatusError }
Jul 31 21:50:50 fencechat kernel: sd 3:0:0:0: SCSI error: return code = 0x8000002
Jul 31 21:50:50 fencechat kernel: sdb: Current: sense key: Aborted Command
Jul 31 21:50:50 fencechat kernel: Additional sense: No additional sense information
Jul 31 21:50:50 fencechat kernel: end_request: I/O error, dev sdb, sector 5140609
Jul 31 21:50:50 fencechat kernel: raid1: Disk failure on sdb2, disabling device.
Jul 31 21:50:50 fencechat kernel: Operation continuing on 1 devices
Jul 31 21:50:50 fencechat kernel: RAID1 conf printout:
Jul 31 21:50:50 fencechat kernel: --- wd:1 rd:2
Jul 31 21:50:50 fencechat kernel: disk 0, wo:0, o:1, dev:sda9
Jul 31 21:50:50 fencechat kernel: disk 1, wo:1, o:0, dev:sdb2
Jul 31 21:50:50 fencechat kernel: RAID1 conf printout:
Jul 31 21:50:50 fencechat kernel: --- wd:1 rd:2
Jul 31 21:50:50 fencechat kernel: disk 0, wo:0, o:1, dev:sda9
ul 31 22:16:56 fencechat kernel: ata4: error=0x04 { DriveStatusError }
Jul 31 22:16:56 fencechat kernel: ata4: status=0x71 { DriveReady DeviceFault SeekComplete Error }
Jul 31 22:16:56 fencechat kernel: ata4: error=0x04 { DriveStatusError }
Jul 31 22:16:56 fencechat kernel: sd 3:0:0:0: SCSI error: return code = 0x8000002
Jul 31 22:16:56 fencechat kernel: sdb: Current: sense key: Aborted Command
Jul 31 22:16:56 fencechat kernel: Additional sense: No additional sense information
Jul 31 22:16:56 fencechat kernel: end_request: I/O error, dev sdb, sector 16
Jul 31 22:16:56 fencechat kernel: Buffer I/O error on device sdb, logical block 2
Jul 31 22:16:56 fencechat kernel: ata4: status=0x71 { DriveReady DeviceFault SeekComplete Error }
Jul 31 22:16:56 fencechat kernel: ata4: error=0x04 { DriveStatusError }
Jul 31 22:16:56 fencechat kernel: ata4: status=0x71 { DriveReady DeviceFault Jul 31 22:16:56 fencechat kernel: ata4: error=0x04 { DriveStatusError }
Jul 31 22:16:56 fencechat kernel: ata4: status=0x71 { DriveReady DeviceFault SeekComplete Error }
Jul 31 22:16:56 fencechat kernel: ata4: error=0x04 { DriveStatusError }
Jul 31 22:16:56 fencechat kernel: sd 3:0:0:0: SCSI error: return code = 0x8000002
Jul 31 22:16:56 fencechat kernel: sdb: Current: sense key: Aborted Command
Jul 31 22:16:56 fencechat kernel: Additional sense: No additional sense information
Jul 31 22:16:56 fencechat kernel: end_request: I/O error, dev sdb, sector 24
Jul 31 22:16:56 fencechat kernel: Buffer I/O error on device sdb, logical block 3
ul 31 22:16:56 fencechat kernel: end_request: I/O error, dev sdb, sector 24
Jul 31 22:16:56 fencechat kernel: Buffer I/O error on device sdb, logical block 3
Jul 31 22:16:56 fencechat kernel: ata4: status=0x71 { DriveReady DeviceFault SeekComplete Error }
Jul 31 22:16:56 fencechat kernel: ata4: error=0x04 { DriveStatusError }
Jul 31 22:16:56 fencechat kernel: ata4: status=0x71 { DriveReady DeviceFault SeekComplete Error }
Jul 31 22:16:56 fencechat kernel: ata4: error=0x04 { DriveStatusError }
Jul 31 22:16:56 fencechat kernel: ata4: status=0x71 { DriveReady DeviceFault SeekComplete Error }
Jul 31 22:16:56 fencechat kernel: ata4: error=0x04 { DriveStatusError }
Jul 31 22:16:56 fencechat kernel: ata4: status=0x71 { DriveReady DeviceFault SeekComplete Error }
Jul 31 22:16:56 fencechat kernel: ata4: error=0x04 { DriveStatusError }
Jul 31 22:16:56 fencechat kernel: ata4: status=0x71 { DriveReady DeviceFault SeekComplete Error }
Jul 31 22:16:56 fencechat kernel: ata4: error=0x04 { DriveStatusError }
Jul 31 22:16:56 fencechat kernel: sd 3:0:0:0: SCSI error: return code = 0x8000002
Jul 31 22:16:56 fencechat kernel: sdb: Current: sense key: Aborted Command
Jul 31 22:16:56 fencechat kernel: Additional sense: No additional sense information
Jul 31 22:16:56 fencechat kernel: end_request: I/O error, dev sdb, sector 32
Jul 31 22:16:56 fencechat kernel: Buffer I/O error on device sdb, logical block 4
Jul 31 22:16:56 fencechat kernel: ata4: status=0x71 { DriveReady DeviceFault SeekComplete Error }
Jul 31 22:16:56 fencechat kernel: ata4: error=0x04 { DriveStatusError }
Jul 31 22:16:56 fencechat kernel: ata4: status=0x71 { DriveReady DeviceFault SeekComplete Error }
Jul 31 22:16:56 fencechat kernel: ata4: error=0x04 { DriveStatusError }
Jul 31 22:16:56 fencechat kernel: ata4: status=0x71 { DriveReady DeviceFault SeekComplete Error }
Jul 31 22:16:57 fencechat kernel: ata4: error=0x04 { DriveStatusError }
 
Old 07-31-2006, 11:56 PM   #2
conquest
LQ Newbie
 
Registered: Jul 2006
Posts: 2

Original Poster
Rep: Reputation: 0
I've tried using dmraid to disable raid using this command which failed:

dmraid -an
ERROR: hpt45x: reading /dev/sdb[Input/output error]
ERROR: isw: reading /dev/sdb[Input/output error]
ERROR: lsi: reading /dev/sdb[Input/output error]
ERROR: nvidia: reading /dev/sdb[Input/output error]
ERROR: pdc: reading /dev/sdb[Input/output error]
ERROR: pdc: reading /dev/sdb[Input/output error]
ERROR: pdc: reading /dev/sdb[Input/output error]
ERROR: pdc: reading /dev/sdb[Input/output error]
ERROR: pdc: reading /dev/sdb[Input/output error]
ERROR: sil: reading /dev/sdb[Input/output error]
ERROR: via: reading /dev/sdb[Input/output error]
RAID set "nvidia_bcfgcgjh" is not active


I've also tried using mdadm for each device:

mdadm --set-faulty /dev/md1 /dev/sdb2


cat /proc/mdstat shows this:

Personalities : [raid1]
md1 : active raid1 sdb2[2](F) sda9[0]
2048192 blocks [2/1] [U_]

md8 : active raid1 sdb3[2](F) sda10[0]
2048192 blocks [2/1] [U_]

md2 : active raid1 sdb5[2](F) sda5[0]
5116544 blocks [2/1] [U_]

md4 : active raid1 sdb6[2](F) sda6[0]
5116544 blocks [2/1] [U_]

md5 : active raid1 sdb7[2](F) sda7[0]
5116544 blocks [2/1] [U_]

md6 : active raid1 sdb8[2](F) sda8[0]
5116544 blocks [2/1] [U_]

md3 : active raid1 sdb9[2](F) sda3[0]
6144704 blocks [2/1] [U_]

md7 : active raid1 sdb10[2](F) sda2[0]
51199040 blocks [2/1] [U_]

md9 : active raid1 sdb11[2](F) sda11[0]
2048192 blocks [2/1] [U_]

md0 : active raid1 sdb1[2](F) sda1[0]
521984 blocks [2/1] [U_]

unused devices: <none>

Also trying to stop using mdadm yields this:

mdadm -S /dev/md1
mdadm: fail to stop array /dev/md1: Device or resource busy


Would unplugging this device (on the fly) be a bad thing?
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Raid Problem Fedora Core 3, RAID LOST DISKS ALWAYS icatalan Linux - Hardware 1 09-17-2005 04:14 AM
Fedora Core 4 wont "see" my Promise Fastrak 378 IDE-RAID array as one drive. Justinr999 Linux - Hardware 0 07-19-2005 02:30 AM
Fedora Core 3 and RAID 1 cbriscoejr Fedora 11 04-01-2005 02:07 PM
Raid 1 on Fedora core 2 mouse46 Linux - Hardware 16 09-22-2004 02:36 PM


All times are GMT -5. The time now is 03:31 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration