I searched here on the forum to see why my cache drive goes to read only after a while.  Most people ran a check on the drive to check for corruptions.  So I stopped the array and ran reiserfsck -check /dev/sdb1

 

Replaying journal: Done.

Reiserfs journal '/dev/sdb1' in blocks [18..8211]: 662 transactions replayed

Checking internal tree..  finished

Comparing bitmaps..finished

Checking Semantic tree:

finished

No corruptions found

There are on the filesystem:

        Leaves 63511

        Internal nodes 417

        Directories 309746

        Other files 184359

        Data block pointers 31617135 (969150 of them are zero)

        Safe links 0

###########

reiserfsck finished at Mon Aug 29 10:23:45 2016

###########

 

It reports no issues.  Any other suggestions on why my cache drive started acting up all of a sudden?

 

When I try to create a file I get:

 

/mnt/cache# touch test

touch: cannot touch âtestâ: Read-only file system

 

And in the log file I get the following error/warning:

Aug 29 10:32:22 tower kernel: blk_update_request: critical medium error, dev sdb, sector 1426375255

Aug 29 10:32:22 tower kernel: Buffer I/O error on dev sdb1, logical block 178296899, async page read

Aug 29 10:32:25 tower shfs/user: shfs_read: read: (5) Input/output error

Aug 29 10:32:25 tower kernel: mpt2sas0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)

Aug 29 10:32:25 tower kernel: sd 3:0:0:0: [sdb] UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08

Aug 29 10:32:25 tower kernel: sd 3:0:0:0: [sdb] Sense Key : 0x3 [current]

Aug 29 10:32:25 tower kernel: sd 3:0:0:0: [sdb] ASC=0x11 ASCQ=0x0

Aug 29 10:32:25 tower kernel: sd 3:0:0:0: [sdb] CDB: opcode=0x28 28 00 55 04 c2 5f 00 00 08 00

Aug 29 10:32:25 tower kernel: blk_update_request: critical medium error, dev sdb, sector 1426375263

Aug 29 10:32:25 tower kernel: Buffer I/O error on dev sdb1, logical block 178296900, async page read

Aug 29 10:32:28 tower kernel: mpt2sas0: log_info(0x31110630): originator(PL), code(0x11), sub_code(0x0630)

Aug 29 10:32:28 tower kernel: mpt2sas0: log_info(0x31110630): originator(PL), code(0x11), sub_code(0x0630)

Aug 29 10:32:28 tower kernel: mpt2sas0: log_info(0x31110630): originator(PL), code(0x11), sub_code(0x0630)

Aug 29 10:32:28 tower kernel: mpt2sas0: log_info(0x31110630): originator(PL), code(0x11), sub_code(0x0630)

Aug 29 10:32:28 tower kernel: mpt2sas0: log_info(0x31110630): originator(PL), code(0x11), sub_code(0x0630)

Aug 29 10:32:32 tower kernel: sd 3:0:0:0: [sdb] UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08

Aug 29 10:32:32 tower kernel: sd 3:0:0:0: [sdb] Sense Key : 0x3 [current]

Aug 29 10:32:32 tower kernel: sd 3:0:0:0: [sdb] ASC=0x11 ASCQ=0x0

Aug 29 10:32:32 tower kernel: sd 3:0:0:0: [sdb] CDB: opcode=0x28 28 00 55 04 c3 c7 00 00 08 00

Aug 29 10:32:32 tower kernel: blk_update_request: critical medium error, dev sdb, sector 1426375623

Aug 29 10:32:32 tower kernel: Buffer I/O error on dev sdb1, logical block 178296945, async page read

 

It seems to me as if the drive is failing?

 

thanks

david

You forgot to post your complete diagnostics zip.

here you go.

 

thanks

david

tower-diagnostics-20160829-1107.zip

Your cache disk is a goner, replace it.

That is what I was afraid of.

 

thanks,

david

what tipped you off to that Johnnie.black?

I'm experiencing the same issue with my cache drive.

what tipped you off to that Johnnie.black?

I'm experiencing the same issue with my cache drive.

Post your diagnostics, same problem doesn't always mean the same reason.

 

IIRC he had a cache disk with several pending sectors.