+ Reply to Thread
Results 1 to 2 of 2

Thread: ext3_get_inode_loc unable to read inode block

  1. #1
    joseph's Avatar
    joseph is offline Website Master Achievements:
    500 Experience Points1000 Experience Points5000 Experience Points10000 Experience PointsRecommendation Second Class
    joseph has disabled reputation
    Join Date
    2008-09-08
    Posts
    412

    Default ext3_get_inode_loc unable to read inode block

    I just got this error message on a HP MSA20, It's also caused by loosed wire connection, you just need to re-plug the connecting wire between your server and the MSA20 equipment.

    EXT3-fs error (device cciss1(105,83)): ext3_get_inode_loc: unable to read inode block - inode=22298678, block=44597251
    cciss: cmd f7720000 has CHECK CONDITION, sense key = 0x5
    cciss: cmd f7720000 has CHECK CONDITION, sense key = 0x5
    EXT3-fs error (device cciss1(105,83)): ext3_get_inode_loc: unable to read inode block - inode=15810593, block=31621123
    cciss: cmd f7720000 has CHECK CONDITION, sense key = 0x5
    cciss: cmd f7720000 has CHECK CONDITION, sense key = 0x5
    EXT3-fs error (device cciss1(105,83)): ext3_get_inode_loc: unable to read inode block - inode=12042315, block=24084484
    cciss: cmd f7720000 has CHECK CONDITION, sense key = 0x5
    cciss: cmd f7720000 has CHECK CONDITION, sense key = 0x5
    EXT3-fs error (device cciss1(105,83)): ext3_get_inode_loc: unable to read inode block - inode=32964726, block=65929221
    cciss: cmd f7720000 has CHECK CONDITION, sense key = 0x5
    cciss: cmd f7720000 has CHECK CONDITION, sense key = 0x5
    cciss: cmd f7720000 has CHECK CONDITION, sense key = 0x5
    EXT3-fs error (device cciss1(105,83)): ext3_readdir: directory #55525390 contains a hole at offset 0
    cciss: cmd f7720000 has CHECK CONDITION, sense key = 0x5
    cciss: cmd f7720000 has CHECK CONDITION, sense key = 0x5
    EXT3-fs error (device cciss1(105,66)): ext3_get_inode_loc: unable to read inode block - inode=28164218, block=56328197
    cciss: cmd f7720000 has CHECK CONDITION, sense key = 0x5
    EXT3-fs error (device cciss1(105,67)): ext3_get_inode_loc: unable to read inode block - inode=983055, block=1966082
    cciss: cmd f7720000 has CHECK CONDITION, sense key = 0x5

  2. #2
    joseph's Avatar
    joseph is offline Website Master Achievements:
    500 Experience Points1000 Experience Points5000 Experience Points10000 Experience PointsRecommendation Second Class
    joseph has disabled reputation
    Join Date
    2008-09-08
    Posts
    412

    Default

    I happened to face this kind of error message again on a DELL powered storage server, the warning message is as following:

    I/O error: dev 08:2c, sector 0
    I/O error: dev 08:09, sector 102236184
    EXT3-fs error (device sd(8,9)): ext3_get_inode_loc: unable to read inode block - inode=6389804, block=12779523
    I/O error: dev 08:09, sector 0
    I/O error: dev 08:3b, sector 297271328
    EXT3-fs error (device sd(8,59)): ext3_get_inode_loc: unable to read inode block - inode=18579539, block=37158916
    I/O error: dev 08:3b, sector 0
    I/O error: dev 08:1a, sector 302514224
    EXT3-fs error (device sd(8,26)): ext3_get_inode_loc: unable to read inode block - inode=18907270, block=37814278
    I/O error: dev 08:1a, sector 0
    I/O error: dev 08:09, sector 136839192
    EXT3-fs error (device sd(8,9)): ext3_get_inode_loc: unable to read inode block - inode=8552482, block=17104899
    I/O error: dev 08:09, sector 0
    I/O error: dev 08:2c, sector 233308776
    EXT3-fs error (device sd(8,44)): ext3_get_inode_loc: unable to read inode block - inode=14584173, block=29163597
    I/O error: dev 08:2c, sector 0
    I/O error: dev 08:2a, sector 6553752
    EXT3-fs error (device sd(8,42)): ext3_get_inode_loc: unable to read inode block - inode=409688, block=819219
    I/O error: dev 08:2a, sector 0
    I/O error: dev 08:3c, sector 2883616
    EXT3-fs error (device sd(8,60)): ext3_get_inode_loc: unable to read inode block - inode=180315, block=360452
    I/O error: dev 08:3c, sector 0
    I/O error: dev 08:0c, sector 46104
    I/O error: dev 08:06, sector 68104
    I/O error: dev 08:09, sector 1048592
    EXT3-fs error (device sd(8,9)): ext3_get_inode_loc: unable to read inode block - inode=65537, block=131074
    I/O error: dev 08:09, sector 0
    I/O error: dev 08:0c, sector 244432376
    I/O error: dev 08:0c, sector 46112
    I/O error: dev 08:3c, sector 2662560
    I/O error: dev 08:3c, sector 2662560
    I/O error: dev 08:3c, sector 2662560
    I/O error: dev 08:0c, sector 244432376
    I/O error: dev 08:0c, sector 46120
    I/O error: dev 08:0b, sector 434372624
    EXT3-fs error (device sd(8,11)): ext3_get_inode_loc: unable to read inode block - inode=27148298, block=54296578
    I/O error: dev 08:0b, sector 0
    I/O error: dev 08:0c, sector 244432376
    I/O error: dev 08:0c, sector 46128
    I/O error: dev 08:2b, sector 429399280
    I/O error: dev 08:0c, sector 244432376
    I/O error: dev 08:0c, sector 46136
    I/O error: dev 08:07, sector 158938288
    I/O error: dev 08:07, sector 158938288
    I/O error: dev 08:07, sector 158938288
    I/O error: dev 08:3c, sector 129761312
    EXT3-fs error (device sd(8,60)): ext3_get_inode_loc: unable to read inode block - inode=8110168, block=16220164
    I/O error: dev 08:3c, sector 0
    I/O error: dev 08:0c, sector 244432376
    I/O error: dev 08:0c, sector 46144
    I/O error: dev 08:2a, sector 297014248
    I/O error: dev 08:15, sector 275251240
    EXT3-fs error (device sd(8,21)): ext3_get_inode_loc: unable to read inode block - inode=17203310, block=34406405
    I/O error: dev 08:15, sector 0
    I/O error: dev 08:09, sector 82346464

+ Reply to Thread

Similar Threads

  1. Replies: 0
    Last Post: 2009-12-29, 07:33 AM
  2. Fwd: Rethinking B-tree block sizes on SSDs
    By FeedReader in forum Databases
    Replies: 0
    Last Post: 2009-10-06, 05:32 PM
  3. LWN: [$] Interrupt mitigation in the block layer
    By edenCC in forum Technology News
    Replies: 0
    Last Post: 2009-08-11, 02:01 AM
  4. Delete files by inode number
    By admon.org in forum Linux System
    Replies: 0
    Last Post: 2009-03-18, 12:10 PM
  5. use an alternative supper block to start fsck
    By joseph in forum Linux System
    Replies: 0
    Last Post: 2008-09-15, 04:44 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts