LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
User Name
Password
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices

Reply
 
Search this Thread
Old 06-17-2007, 09:35 AM   #1
ElmPie
LQ Newbie
 
Registered: Aug 2003
Distribution: Debian
Posts: 12

Rep: Reputation: 0
Raid disk problem : Attempt to read block from filesystem resulted in short read


I have a Debian server with kernel 2.4.27-1-386 installed.

Once in a wile I get mails from mdadm monitoring telling me that :

A Fail event had been detected on md device /dev/md0.
It could be related to component device /dev/hdb1

When I remove the disk from the array and add it again the problems seem to be gone for a while. But now I want to get to the bottom of this.

I removed the disk from the array :
mdadm /dev/md0 -r /dev/hdb1

And checked the disk :
fsck /dev/hdb1
/dev/hdb1: recovering journal
/dev/hdb1: Attempt to read block from filesystem resulted in short read while reading block 8005
JBD: Failed to read block at offset 7483
fsck.ext2: Input/output error while recovering ext3 journal of /dev/hdb1

I'm not sure what I should do next. Can anyone point me in a direction?

Thanks!
 
Old 06-17-2007, 02:50 PM   #2
rtspitz
Member
 
Registered: Jan 2005
Location: germany
Distribution: suse, opensuse, debian, others for testing
Posts: 307

Rep: Reputation: 32
make a backup.

if suggest to run badblocks on the failed ext3 disk.
 
Old 06-18-2007, 04:57 PM   #3
ElmPie
LQ Newbie
 
Registered: Aug 2003
Distribution: Debian
Posts: 12

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by rtspitz
make a backup.

if suggest to run badblocks on the failed ext3 disk.
Thanks for the reply!

I did run badblocks and then tried to :

fsck -t ext2 -l badblocks /dev/hdb1
But then I got a whole bunch of :
Bad block 2766258 out of range; ignored.
Bad block 2766259 out of range; ignored.
Bad block 2767756 out of range; ignored.
Bad block 2767757 out of range; ignored.
Bad block 2767758 out of range; ignored.
....

What is interesting is this :

dmesg | grep hdb
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x40 { UncorrectableError }, LBAsect=1835966, sector=1835903
end_request: I/O error, dev 03:41 (hdb), sector 1835903
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x40 { UncorrectableError }, LBAsect=3148990, sector=3148927
end_request: I/O error, dev 03:41 (hdb), sector 3148927
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x40 { UncorrectableError }, LBAsect=3932571, sector=3932508
end_request: I/O error, dev 03:41 (hdb), sector 3932508

I guess the disk really isn't looking good at all but is there anything I can still try?

Thanks!
 
Old 06-18-2007, 05:03 PM   #4
Quakeboy02
Senior Member
 
Registered: Nov 2006
Distribution: Debian Squeeze 2.6.32.9 SMP AMD64
Posts: 3,238

Rep: Reputation: 121Reputation: 121
Quote:
I guess the disk really isn't looking good at all but is there anything I can still try?
Your system is giving you fair warning that a drive is failing. It's probably a good idea to replace it while you still can.
 
Old 06-18-2007, 05:14 PM   #5
ElmPie
LQ Newbie
 
Registered: Aug 2003
Distribution: Debian
Posts: 12

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by Quakeboy02
Your system is giving you fair warning that a drive is failing. It's probably a good idea to replace it while you still can.

Yes I'm going to do that but I was wondering how disk errors can be handled in Debian. I want to give that a try first.


Thanks.
 
Old 08-26-2008, 05:21 AM   #6
yusufu
LQ Newbie
 
Registered: Aug 2008
Posts: 1

Rep: Reputation: 0
Unhappy Msa 1000

I have an HP MSA 1000. I had one of the hard disk crash and after replacing it, I still can't get the data out of it.
I ran dmesg | grep sda and this is what I got:


Buffer I/O error on device sda, logical block 0
Buffer I/O error on device sda, logical block 1
Buffer I/O error on device sda, logical block 2
Buffer I/O error on device sda, logical block 3
Buffer I/O error on device sda, logical block 4
Buffer I/O error on device sda, logical block 5
Buffer I/O error on device sda, logical block 6
Buffer I/O error on device sda, logical block 7
sda: Current: sense key: Hardware Error
end_request: I/O error, dev sda, sector 0
Buffer I/O error on device sda, logical block 0
sda: Current: sense key: Hardware Error
end_request: I/O error, dev sda, sector 1
Buffer I/O error on device sda, logical block 1
sda: Current: sense key: Hardware Error
end_request: I/O error, dev sda, sector 0
sda: Current: sense key: Hardware Error
end_request: I/O error, dev sda, sector 0
sda: Current: sense key: Hardware Error
end_request: I/O error, dev sda, sector 1
sda: Current: sense key: Hardware Error
end_request: I/O error, dev sda, sector 2
sda: Current: sense key: Hardware Error
end_request: I/O error, dev sda, sector 3
sda: Current: sense key: Hardware Error
end_request: I/O error, dev sda, sector 4
sda: Current: sense key: Hardware Error
end_request: I/O error, dev sda, sector 5
sda: Current: sense key: Hardware Error
end_request: I/O error, dev sda, sector 6
sda: Current: sense key: Hardware Error
end_request: I/O error, dev sda, sector 7
sda: Current: sense key: Hardware Error
end_request: I/O error, dev sda, sector 8
sda: Current: sense key: Hardware Error
end_request: I/O error, dev sda, sector 9
sda: Current: sense key: Hardware Error
end_request: I/O error, dev sda, sector 10
sda: Current: sense key: Hardware Error
end_request: I/O error, dev sda, sector 11
sda: Current: sense key: Hardware Error
end_request: I/O error, dev sda, sector 12
sda: Current: sense key: Hardware Error
end_request: I/O error, dev sda, sector 13
sda: Current: sense key: Hardware Error
end_request: I/O error, dev sda, sector 14
sda: Current: sense key: Hardware Error
end_request: I/O error, dev sda, sector 15


What do I do?
 
  


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 On
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
fsck.ext3: Attempt to read block from filesystem trouble dolphans1 Mandriva 12 10-07-2009 04:30 AM
How can I have: Root has Read-Write, user has read only for the boot filesystem? xmrkite Linux - Software 6 10-16-2008 04:31 AM
Error reading block ... resulted in short read shadowrise Linux - Hardware 1 12-29-2006 08:15 AM
fsck error (read from fs resulted in short read) NeoKaiserSigma Linux - General 0 04-05-2005 06:24 PM
..."short read while reading block 516" mohapi Fedora 7 10-22-2004 01:37 PM


All times are GMT -5. The time now is 12:42 AM.

Main Menu
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