SCIENTIFIC-LINUX-USERS Archives

November 2009

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV
Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
Re: RAID configuration problem
From:
Mark Whidby <[log in to unmask]>
Reply To:
Mark Whidby <[log in to unmask]>
Date:
Wed, 4 Nov 2009 11:12:32 +0000
Content-Type:
text/plain
Parts/Attachments:
text/plain (41 lines) 
John Rowe wrote:
> On Wed, 2009-11-04 at 11:01 +0000, Mark Whidby wrote:
>> John Rowe wrote:
>>>> Nov  4 10:36:31 terra kernel: sd 5:0:0:1: SCSI error: return code = 0x000b0000
>>>> Nov  4 10:36:31 terra kernel: end_request: I/O error, dev sdq, sector 5858973568
>>>> Nov  4 10:36:31 terra kernel: printk: 16 messages suppressed.
>>>> Nov  4 10:36:31 terra kernel: Buffer I/O error on device sdq, logical block 732371696
>>>> Nov  4 10:36:31 terra kernel: sd 5:0:0:1: SCSI error: return code = 0x000b0000
>>>> Nov  4 10:36:31 terra kernel: end_request: I/O error, dev sdq, sector 5858973568
>>>> Nov  4 10:36:31 terra kernel: Buffer I/O error on device sdq, logical block 732371696
>>>> Nov  4 10:36:32 terra kernel: sd 5:0:0:1: SCSI error: return code = 0x000b0000
>>>> Nov  4 10:36:32 terra kernel: end_request: I/O error, dev sdq, sector 5858973688
>>>> ...
>>>> Nov  4 10:36:33 terra kernel: sd 5:0:0:1: SCSI error: return code = 0x000b0000
>>>> Nov  4 10:36:33 terra kernel: end_request: I/O error, dev sdq, sector 5858973688
>>>> Nov  4 10:36:33 terra kernel: sd 5:0:0:1: SCSI error: return code = 0x000b0000
>>>> Nov  4 10:36:33 terra kernel: end_request: I/O error, dev sdq, sector 5858973688
>>>> Nov  4 10:36:33 terra kernel: sd 5:0:0:1: SCSI error: return code = 0x000b0000
>>>> Nov  4 10:36:33 terra kernel: end_request: I/O error, dev sdq, sector 5858973568
>>> It's looking horribly like a disk error: have you checked it?
>>> Try badblocks.
>> That's what I thought originally but no matter which combination of 4 disks
>> I try to configure I always get these errors. Unless the box has been populated
>> with a whole batch of bad disks, I suppose.
> 
> I thought that might be too easy, but it was worth a try.
> 
> Does it follow any particular disk controller? Cable?

I haven't been able to test anything like that at the moment. It just seems
very odd that with any 4 or more disks configured I get the problem. I'm going
to have to try it (and the controller) on another system to try my kernel/SL
release possibilities if the owner is amenable. Thanks for your input anyway.


-- 
Mark Whidby
Infrastructure Coordinator (Unix) - Physics/Chemistry/EAES/Mathematics Team
Information Systems
Faculty of Engineering and Physical Sciences

ATOM RSS1 RSS2