SCIENTIFIC-LINUX-USERS Archives

November 2009

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

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

Print Reply
Sender:
Mailling list for Scientific Linux users worldwide <[log in to unmask]>
Date:
Wed, 4 Nov 2009 11:01:20 +0000
MIME-version:
1.0
Reply-To:
Mark Whidby <[log in to unmask]>
Content-type:
text/plain; format=flowed; charset=ISO-8859-1
Subject:
From:
Mark Whidby <[log in to unmask]>
In-Reply-To:
<1257332176.29272.36.camel@phobos>
Content-transfer-encoding:
7BIT
Comments:
To: John Rowe <[log in to unmask]>
Parts/Attachments:
text/plain (31 lines)
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.

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

ATOM RSS1 RSS2