Ext3-fs Error Device Sdb1 Ext3_find_entry Reading Directory
Contents |
I/O Error Installing, Configuring, Troubleshooting server daemons such as Web and Mail Locked
Ext3 Fs Error Ext3_get_inode_loc Unable To Read Inode Block
Print view Search Advanced search 2 posts • Page 1 linux ext3_get_inode_loc unable to read inode block of 1 mashkoorqadir Posts: 50 Joined: 2012/06/27 07:55:01 Centos server giving I/O Error Postby mashkoorqadir » 2014/06/05 08:22:24 Hi guys,My CentOS 5.4 server is running since 2009 working fine since yesterday. it suddenly stop responding. its very critical server for the company. I saw repeated following line and was unable to stop that./etc/rc.d/rc.sysinit: line 947: /bin/usleep: Input/Output errorThis line just repeats over and over and I cant stop it with control-c it.when i reboot the machine it failed mount local partitions and stuck. one more time i rebooted the message on the screen was,setting host name xyzsetting up logical volume mangment:/1: superblock has an invalid ext3 journal (inode 8)clear*** ext3 journal has been deleted - file system in ext2 only ***Error reading block 2056 (attempt to read block from filesystem resulted in short read). Remounting root file system inread-write mode. okMounting local filesystems FailedEnabling local filesystem quotas: FailedEnabling /etc/fstab swaps: Failedand hang at this stage. Again i rebooted this time server started and loaded most of the process at login stage it gave following messages.end_request: I/O error, dev sdb, sector 247392428EXT3-fs error (device sda3): ext3_find_entry: reading directory 528278814 offset 0end_request: I/O error, dev sdb, sector 247392428EXT3-fs error (device sda3): ext3_find_entry: reading directory 528278814 offset 0end_request: I/O error, dev sdb, sector 247392428EXT3-fs error (device sda3): ext3_find_entry: reading directory 528278814 offset 0end_request: I/O error, dev sdb, sector 71end_request: I/O error, dev sdb, sector 63end_request: I/O error,
2011 08:44AM Registered: 6 years ago Posts: 58 Greetings I have had a Dockstar running Debian squeeze since last September. It runs rtorrent 24/7, and has worked well so far. It has a 1 TB usb hard disk with ext3 file system hooked to it. Yesterday, I got this error when trying to do ls on a directory on that usb hard disk: $ ls ls: reading directory .: Input/output error $ Huh? That sounds like a possible hardware failure, but the hard disk is only a few months old. I shut the Dockstar down, hooked the usb hard disk to another linux box, and ran fsck on it. fsck found no problems, and so I restarted http://www.centos.org/forums/viewtopic.php?t=46551 the Dockstar, hooked the usb hard disk back up, and it works fine now. Any ideas what might have happened here? This is unexpected, flaky, "un-Debian-like" behavior, and has never happened before on any of my various linux machines. Reply Quote dpffan Re: Getting "reading directory .: Input/output error" June 07, 2011 09:43AM Run smartctl from the linux box and see what SMART says, ie http://en.wikipedia.org/wiki/S.M.A.R.T. Reply Quote hanker Re: Getting "reading directory .: Input/output error" June http://forum.doozan.com/read.php?2,4998,6481 07, 2011 05:51PM Registered: 6 years ago Posts: 58 > Run smartctl from the linux box and see what SMART > says, ie > http://en.wikipedia.org/wiki/S.M.A.R.T. Thank you for your reply :) I installed smartmontools. I ran smartctl on the drive and got this: $ sudo smartctl -i /dev/sdc smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ Device: WDC WD10 EVDS-63U8B0 Version: 01.0 Serial number: WD-WCAV5F916494 Device type: disk Local Time is: Tue Jun 7 16:28:19 2011 CDT Device does not support SMART $ This is a several-month-old 1 TB Western Digital SATA drive mounted in an Icydock usb 2.0 enclosure. Hmmm... Anyway, after working fine all day, I came home and tried to mount the drive on my Mac with nfs. Like yesterday, I did the mount by double-clicking an alias to the drive. That's when it failed again. This has always worked before. I rebooted the Dockstar and it's OK again. I can mount the drive on the Mac with cmd-K and it works fine. Here's what showed up in dmesg when it failed. The first line is from the end of boot. [ 114.998173] EXT3-fs: mounted filesystem with ordered data mode. [77163.494929] usb 1-1.2: USB disconnect, address 4 [77163.815158] usb 1-1.2: new high speed USB device using orion-ehci and address 6 [77163.928740] usb 1-1.2: New USB device found, idVendor=0928, idProduct=0003 [77163.935672] us
more detail about the error # dmesg . . EXT3-fs error (device sdb1): ext3_lookup: unlinked inode 142214653 in dir #142213149 Aborting journal on device sdb1. ext3_abort called. [code].... View 3 Replies Similar Messages: Debian http://linux.bigresource.com/CentOS-5-Hardware-EXT3-fs-error-device-sdb1-ext3_lookup-unlinked-inode-142214653-in-dir-142213149-FbFDq4Gzz.html :: Error (device Hde1): Ext3_get_inode_loc: Unable To Read Inode Block - Inode=2375715 Red Hat / Fedora :: Unlinked Inode, Aborted Journal And Read Only File System? General :: EXT3 FS Error - Unable To Read Inode http://serverfault.com/questions/111985/usb-drive-becomes-read-only-after-a-while Block Hardware :: Buffer I/O Error On Device Sdb1? General :: External Hard Drive Is No Longer Recognized - Buffer I/O Error On Device Sdb1, Logical Block 6160408 Server :: Run Fsck.ext3 -y /dev/sdb1 And fs error It Shows As Clean Ubuntu :: Mdadm: Cannot Open Device /dev/sdb1: Device Or Resource Busy General :: Where Is Inode Table In Ext3 OpenSUSE Install :: 11.1 Hanging Frequently - Maxserver Kernel: EXT3-fs Error (device Sda3) Hardware :: Raid6: Disk Failure On Sdb1, Disabling Device? Hardware :: "failed To Set Xfermode," / Getting Ext3 Errors About Failing To Read An Inode Block? Software :: EXT3-fserror: Inode Bitmap For Group 4 Not ext3_get_inode_loc unable to In Group CentOS 5 Hardware :: EXT3 - End Request I / O Error On Server OpenSUSE Hardware :: No Application That Can Open Type Block Device (inode/blockdevice)? Ubuntu Servers :: Delete The Sdb1 Partition Fine, But Get The Same Error When Try To Create It Again? CentOS 5 :: Booting 5.4 - Error "EXT3-fs: Can't Read Group Descriptor 3" CentOS 5 :: Mount Error: Can't Mount An Encrypted Volume With An Overlaying Ext3 FS CentOS 5 Hardware :: Booting Time Error "ext3.0 And Jbd.0 Not Installed / Loaded" Fedora :: Error - Ext3_get_inode_block: Bad Inode Number Programming :: Getting Error While Accessing Inode Structure Member / Why Is This? Ubuntu :: Resize2fs: "inode Is From A Bad Block In The Inode Table"? Ubuntu :: Error - Superblock Has An Invalid Journal (inode Clear?
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top USB Drive becomes read-only after a while up vote 1 down vote favorite Our backup "solution" includes hooking up a USB drive to the backup server, and running a custom script that rsyncs the data on to the USB drive. However, after a while, the drive becomes read-only. Here's the output of dmesg: [2502923.708171] sdb: sdb1 [2502923.742767] sd 36:0:0:0: [sdb] Attached SCSI disk [2502980.368020] kjournald starting. Commit interval 5 seconds [2502980.482705] EXT3 FS on sdb1, internal journal [2502980.482705] EXT3-fs: recovery complete. [2502980.488709] EXT3-fs: mounted filesystem with ordered data mode. [2590744.432168] usb 1-2: USB disconnect, address 36 [2590744.432655] sd 36:0:0:0: [sdb] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK [2590744.432784] end_request: I/O error, dev sdb, sector 795108447 [2590744.432857] Buffer I/O error on device sdb1, logical block 99388548 [2590744.432925] lost page write due to I/O error on sdb1 [2590744.433002] Buffer I/O error on device sdb1, logical block 99388549 [2590744.433070] lost page write due to I/O error on sdb1 [2590744.433139] Buffer I/O error on device sdb1, logical block 99388550 [2590744.433207] lost page write due to I/O error on sdb1 [2590744.433275] Buffer I/O error on device sdb1, logical block 99388551 [2590744.433343] lost page write due to I/O error on sdb1 [2590744.433410] Buffer I/O error on device sdb1, logical block 99388552 [2590744.433478] lost page write due to I/O error on sdb1 [2590744.433545] Buffer I/O error on device sdb1, logical block 99388553 [2590744.433613] lost page write due to I/O error on sdb1 [2590744.433681] Buffer I/O error on device sdb1, logical block 99388554 [2590744.433749] lost page write due to I/O error on sdb1 [2590744.433817] Buffer I/O error on device sdb1, logical block 99388555 [2590744.433884] lost page w