Hello Thomas, On Tue, 2016-02-09 at 12:53 +0100, Thomas Schmitt wrote: > > > Linux pi 4.1.16-v7+ #833 SMP Wed Jan 27 14:32:22 GMT 2016 armv7l > GNU/Linux > > The source code where i find the message text in my Sid kernel > is not depending on the CPU architecture. So it is supposed to be > in effect on your system. > But i riddle why it does not convert 0x2003 to "FAILED". > > I'm now updating my kernel to see if there are any improvements, which I doubt because there's hardly any change in the repo. But I've filed a bug to keep the RPi guy informed. https://github.com/Hexxeh/rpi-firmware/issues/103 > > > I just hope it is not another HDD failure. > > Looks like a controller and/or driver problem. > The web echo on "UNKNOWN(0x2003)" is suspiciously unhelpful. > > Lets try google > sd "FAILED Result" DID_OK DRIVER_OK > Aha. There are kernels which can translate 0x2003 and the commenters > are somewhat more qualified. But still no hands-on proposals. > > I've seen the same message again, today. but at different locations. [62711.477903] sd 0:0:0:0: [sda] UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00 [62711.485701] sd 0:0:0:0: [sda] CDB: opcode=0x28 28 00 9d 40 01 47 00 00 08 00 [62711.492910] blk_update_request: I/O error, dev sda, sector 2638217543 [84370.313684] sd 0:0:0:0: [sda] UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00 [84370.321532] sd 0:0:0:0: [sda] CDB: opcode=0x28 28 00 a1 40 01 47 00 00 08 00 [84370.328721] blk_update_request: I/O error, dev sda, sector 2705326407 And about your last question, No, apart from these, there are no other message about any sense code. > > I am hoping the fsck results are reliable. I only tried the "-c" > read- > > only option. The other was with "-cc" which would also perform a > > read/write test. > > I cannot find "-c" in man fsck of Sid. > Run the command `man fsck.ext4` Just `man fsck` takes you to the outdated/wrong util-linux manpage. > If it really does read the metadata and the content of data files, > then at least your filesystem should be ok for making a backup. > (I would not use it for heavy writing before such a backup was made.) > Yes. I guess I'll do the same. The other spare one has enough space. So I'm going to backup everything and try your verification example of dd below. Thanks again. > If you want to know whether there is a reproducible bad spot, then > try whether your disk produces any i/o errors when read flatly. > Like > > dd if=/dev/sda of=/dev/null > > If you get errors, try whether they occur again if you start reading > a few hundred blocks before that address > > dd if=/dev/sda of=/dev/null skip=...block.number... > > > But i do not really expect a reproducible pattern here. -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com "Necessity is the mother of invention."
Attachment:
signature.asc
Description: This is a digitally signed message part