Find the answer to your Linux question:
Results 1 to 3 of 3
Hello i'm newbie on linux ... i had some problem .. with my linux server ... i have one partition cannot access file again .. the error like this ..... ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Feb 2012
    Posts
    2

    ls: cannot access /1: Input/output error


    Hello i'm newbie on linux ...

    i had some problem .. with my linux server ...

    i have one partition cannot access file again ..

    the error like this ..... :
    ls: cannot access /1: Input/output error

    and the partition be come read-only.

    But now i try again for ls -la .. not appear like above again ... :
    total 0
    only that appear but still read-only....

    little log error at /var/log/messages:

    Feb 23 15:16:11 xxx kernel: I/O error: dev 08:21, sector 4192
    Feb 23 15:16:11 xxx kernel: EXT3-fs error (device sd(8,33)): ext3_readdir: directory #2 contains a hole at offset 0
    Feb 23 15:16:26 xxx kernel: I/O error: dev 08:21, sector 4192
    Feb 23 15:16:26 xxx kernel: EXT3-fs error (device sd(8,33)): ext3_readdir: directory #2 contains a hole at offset 0
    Feb 23 15:16:36 xxx su(pam_unix)[21622]: session closed for user root
    Feb 23 15:16:39 xxx kernel: I/O error: dev 08:21, sector 4192
    Feb 23 15:16:39 xxx kernel: EXT3-fs error (device sd(8,33)): ext3_readdir: directory #2 contains a hole at offset 0
    Feb 23 15:16:53 xxx kernel: I/O error: dev 08:21, sector 4192
    Feb 23 15:16:53 xxx kernel: EXT3-fs error (device sd(8,33)): ext3_readdir: directory #2 contains a hole at offset 0
    Feb 23 15:17:07 xxx su(pam_unix)[23410]: session opened for user root by agusdev(uid=507)
    Feb 23 15:17:57 xxx kernel: I/O error: dev 08:21, sector 4192
    Feb 23 15:17:57 xxx kernel: EXT3-fs error (device sd(8,33)): ext3_readdir: directory #2 contains a hole at offset 0
    Feb 23 15:18:31 xxx kernel: I/O error: dev 08:21, sector 4192
    Feb 23 15:18:31 xxx kernel: EXT3-fs error (device sd(8,33)): ext3_readdir: directory #2 contains a hole at offset 0
    Feb 23 15:20:20 xxx kernel: I/O error: dev 08:21, sector 4192
    Feb 23 15:20:20 xxx kernel: EXT3-fs error (device sd(8,33)): ext3_readdir: directory #2 contains a hole at offset 0
    Feb 23 15:20:24 xxx kernel: I/O error: dev 08:21, sector 4192
    Feb 23 15:21:17 xxx kernel: I/O error: dev 08:21, sector 4192
    Feb 23 15:21:17 xxx kernel: EXT3-fs error (device sd(8,33)): ext3_readdir: directory #2 contains a hole at offset 0

    and on dmesg :

    oc: unable to read inode block - inode=1703937, block=3407874
    I/O error: dev 08:21, sector 0
    EXT3-fs error (device sd(8,33)) in ext3_reserve_inode_write: IO failure
    I/O error: dev 08:21, sector 0
    I/O error: dev 08:21, sector 45048
    I/O error: dev 08:21, sector 27262992
    EXT3-fs error (device sd(8,33)): ext3_get_inode_loc: unable to read inode block - inode=1703937, block=3407874
    I/O error: dev 08:21, sector 0
    EXT3-fs error (device sd(8,33)) in ext3_reserve_inode_write: IO failure
    I/O error: dev 08:21, sector 0
    I/O error: dev 08:21, sector 45056
    I/O error: dev 08:21, sector 27262992
    EXT3-fs error (device sd(8,33)): ext3_get_inode_loc: unable to read inode block - inode=1703937, block=3407874
    I/O error: dev 08:21, sector 0
    EXT3-fs error (device sd(8,33)) in ext3_reserve_inode_write: IO failure


    may you help me recovery my partition ... plz...

    thx for attention n help before

  2. #2
    Linux Enthusiast scathefire's Avatar
    Join Date
    Jan 2010
    Location
    Western Kentucky
    Posts
    626
    i'd suggest running fsck against the partition in question. if you can unmount the partition without having to bring the system offline first, go that route.
    linux user # 503963

  3. #3
    Just Joined!
    Join Date
    Feb 2012
    Posts
    2
    Quote Originally Posted by scathefire View Post
    i'd suggest running fsck against the partition in question. if you can unmount the partition without having to bring the system offline first, go that route.
    thanks before for answer me... but i trauma for do fsck.. i'm already did it for 2 server and the result my server be come unstable and some command cannot run ..

    Maybe you can give suggestion for run fsck ?

    this is which is i did for fsck:
    i use e2fsck /dev/sda2 ... on process it suggest me check for bad sector and i answer yes
    on process mark bad sector have any question for fix (delete) and i answer yes .. any wrong ??

    and i want ask about unmount first,what for i do that??


    O ya how about some relation or effect to RAID system ?? if my system use RAID...
    and i want know my system use RAID or no from where ??

    thanks again for answer me ..

Posting Permissions

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