LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 08-05-2009, 01:49 PM   #1
rjo98
Senior Member
 
Registered: Jun 2009
Location: US
Distribution: RHEL, CentOS
Posts: 1,685

Rep: Reputation: 48
Bad drive in array?


I think i have a failed or failing drive in an array. Is there a way to tell without rebooting and going into the RAID setup utility?

Last edited by rjo98; 08-05-2009 at 02:02 PM.
 
Old 08-05-2009, 01:53 PM   #2
rjo98
Senior Member
 
Registered: Jun 2009
Location: US
Distribution: RHEL, CentOS
Posts: 1,685

Original Poster
Rep: Reputation: 48
I found this but I can't tell if that means a drive is dead, or just has some bad sectors, or if it resolved itself.

Jul 30 00:04:20 server1 kernel: megaraid: aborting-567509220 cmd=2a <c=2 t=0 l=0>
Jul 30 00:04:20 server1 kernel: megaraid abort: 567509220:89[255:128], fw owner
Jul 30 00:04:20 server1 kernel: megaraid: aborting-567509221 cmd=2a <c=2 t=0 l=0>
Jul 30 00:04:20 server1 kernel: megaraid abort: 567509221:33[255:128], fw owner
Jul 30 00:04:20 server1 kernel: megaraid: aborting-567509222 cmd=2a <c=2 t=0 l=0>
Jul 30 00:04:20 server1 kernel: megaraid abort: 567509222:28[255:128], fw owner
Jul 30 00:04:20 server1 kernel: megaraid: resetting the host...
Jul 30 00:04:20 server1 kernel: megaraid: 3 outstanding commands. Max wait 180 sec
Jul 30 00:04:20 server1 kernel: megaraid mbox: Wait for 3 commands to complete:180
Jul 30 00:09:29 server1 kernel: megaraid mbox: reset sequence completed successfully
Jul 30 08:45:41 server1 kernel: megaraid: aborting-567512252 cmd=2a <c=2 t=0 l=0>
Jul 30 08:45:41 server1 kernel: megaraid abort: 567512252:121[255:128], fw owner
Jul 30 08:45:41 server1 kernel: megaraid: aborting-567512253 cmd=2a <c=2 t=0 l=0>
Jul 30 08:45:41 server1 kernel: megaraid abort: 567512253:66[255:128], fw owner
Jul 30 08:45:41 server1 kernel: megaraid: aborting-567512254 cmd=2a <c=2 t=0 l=0>
Jul 30 08:45:41 server1 kernel: megaraid abort: 567512254:113[255:128], fw owner
Jul 30 08:45:41 server1 kernel: megaraid: aborting-567512356 cmd=30 <c=2 t=0 l=0>
Jul 30 08:45:41 server1 kernel: megaraid abort: 567512356:27[255:128], fw owner
Jul 30 08:45:41 server1 kernel: megaraid: resetting the host...
Jul 30 08:45:41 server1 kernel: megaraid: 4 outstanding commands. Max wait 180 sec
Jul 30 08:45:41 server1 kernel: megaraid mbox: Wait for 4 commands to complete:180
Jul 30 08:45:46 server1 kernel: megaraid mbox: Wait for 4 commands to complete:175
Jul 30 08:45:51 server1 kernel: megaraid mbox: Wait for 4 commands to complete:170
Jul 30 08:45:56 server1 kernel: megaraid mbox: Wait for 4 commands to complete:165
Jul 31 03:16:01 server1 kernel: megaraid mbox: Wait for 3 commands to complete:160
Jul 31 03:16:06 server1 kernel: megaraid mbox: Wait for 3 commands to complete:155
Jul 31 03:16:11 server1 kernel: megaraid mbox: Wait for 3 commands to complete:150
Jul 31 03:16:16 server1 kernel: megaraid mbox: Wait for 3 commands to complete:145
Jul 31 03:16:21 server1 kernel: megaraid mbox: Wait for 3 commands to complete:140
Jul 31 03:16:26 server1 kernel: megaraid mbox: Wait for 3 commands to complete:135
Jul 31 03:16:31 server1 kernel: megaraid mbox: Wait for 3 commands to complete:130
Jul 31 03:16:36 server1 kernel: megaraid mbox: Wait for 3 commands to complete:125
Jul 31 03:16:41 server1 kernel: megaraid mbox: Wait for 3 commands to complete:120
Jul 31 03:16:44 server1 kernel: megaraid mbox: reset sequence completed successfully

Last edited by rjo98; 08-05-2009 at 03:15 PM.
 
Old 08-05-2009, 11:49 PM   #3
chrism01
LQ Guru
 
Registered: Aug 2004
Location: Sydney
Distribution: Centos 6.9, Centos 7.3
Posts: 17,357

Rep: Reputation: 2367Reputation: 2367Reputation: 2367Reputation: 2367Reputation: 2367Reputation: 2367Reputation: 2367Reputation: 2367Reputation: 2367Reputation: 2367Reputation: 2367
mdadm --detail

http://linux.die.net/man/8/mdadm
 
Old 08-06-2009, 07:51 AM   #4
rjo98
Senior Member
 
Registered: Jun 2009
Location: US
Distribution: RHEL, CentOS
Posts: 1,685

Original Poster
Rep: Reputation: 48
Thanks. looks like i must have hardware raid, so i'll have to restart and go into the bios. thanks though.
 
  


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
Removed bad hard drive from computer, now flash drive won't mount. checkmate3001 Linux - Hardware 6 08-15-2008 12:03 AM
RAID1 array down to one disk with bad blocks, clone to good disk with dd noerror? ewolf Linux - Server 2 05-10-2008 12:40 AM
usb drive won't mount - error: wrong fs type, bad option, bad superblock on /dev/sda1 bluecog6 Linux - Hardware 4 01-27-2007 09:07 AM
Problem with bad inodes on Raid 1 Array abefroman Linux - Hardware 1 08-13-2006 06:08 AM
Compaq SCSI Drive Array scottpioso Linux - Hardware 8 04-08-2003 09:56 PM


All times are GMT -5. The time now is 04:38 PM.

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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration