Ext3-fs Error Device Sdb1 Ext3_find_entry
I/O Error Installing, Configuring, Troubleshooting server daemons such as Web and Mail Locked Print view Search Advanced search 2 posts • Page ext3 fs error ext3_get_inode_loc unable to read inode block 1 of 1 mashkoorqadir Posts: 50 Joined: 2012/06/27 07:55:01 Centos server linux ext3_get_inode_loc unable to read inode block 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, dev sdb, sector 17414208end_request: I/O error, dev sdb, sector 17414440end_request: I/O error, dev sdb, sector 1028160end_request: I/O error, dev sdb, sector 1028168end_request: I/O error, dev sdb, sector 1028160end_request: I/O error, dev sdb, sector 625137212end_request: I/O error, dev sdb, sector 625137324end_request: I/O error, dev sdb, sector 17414460end_request: I/O error, dev sdb, sector 17414468end_request:
Help Here Hardware Testing hard disk. Failure or not? Welcome! If this is your first visit, be sure to check out the FAQ. You will have to register before you can post in the forums. (Be aware the forums do not accept user names with a dash "-") Also, logging in lets you avoid the CAPTCHA verification when searching . Select Articles, Forum, or Blog. Posting in the Forums implies acceptance of the Terms and Conditions. Page 1 of 2 12 Last Jump to page: Results 1 to 10 of 15 Thread: Testing hard disk. Failure or not? Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to http://www.centos.org/forums/viewtopic.php?t=46551 Hybrid Mode Switch to Threaded Mode 12-Nov-2012,03:46 #1 fperal View Profile View Forum Posts View Blog Entries View Articles Busy Penguin Join Date Nov 2009 Posts 256 Testing hard disk. Failure or not? Hi! I have a opensuse server running 24/7. Some times it unmount filesystems on sdb. sdb disk is a sata one connected to the motherboard through a pci card (delock 70156 PCI-> SATA + eSATA + IDE) because the motherboard https://forums.opensuse.org/showthread.php/480458-Testing-hard-disk-Failure-or-not is old and does not have sata. Whe the disk is unmounted it "dissapears". Executing fdisk -l reports no sdb disk. But rebooting the computer mount the disk again. This are some errors in /var/log/messages: Code: Nov 11 20:41:47 aldebaran kernel: sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Nov 11 20:42:18 aldebaran kernel: sd 2:0:0:0: [sdb] 488397168 512-byte hardware sectors: (250 GB/232 GiB) Nov 11 20:42:49 aldebaran kernel: sd 2:0:0:0: [sdb] Write Protect is off Nov 11 20:42:49 aldebaran kernel: sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00 ......... Nov 11 21:03:03 aldebaran smartd[3311]: Device: /dev/sdb [SAT], SMART Usage Attribute: 195 Hardware_ECC_Recovered changed from 42 to 41 Nov 11 23:03:02 aldebaran smartd[3311]: Device: /dev/sdb [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 78 to 79 Nov 11 23:03:02 aldebaran smartd[3311]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 22 to 21 ..... Nov 11 23:43:37 aldebaran kernel: sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Nov 11 23:44:49 aldebaran kernel: sd 2:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK Nov 11 23:44:49 aldebaran kernel: sd 2:0:0:0: [sdb] Sense Key : Aborted Command [current] [descriptor] Nov 11 23:44:49 aldebaran kernel: sd 2:0:0:0: [sdb] Add. Sense: No additional sense information Nov 11 23:44:49 aldebaran kernel: end_
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 http://forum.doozan.com/read.php?2,4998,6481 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 the Dockstar, hooked the usb hard fs error 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 07, 2011 05:51PM Registered: 6 years ago Posts: 58 ext3_get_inode_loc unable to > 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] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [77163.943051] usb 1-1.2: Product: USB 2.0 Storage Device [