Ext3-fs Error Device Sda3 Ext3_find_entry Reading Directory
Contents |
Edit You need to log in to change this bug's status. Affecting: Debian Filed here by: Jos van Hees
Ext3 Fs Error Ext3_get_inode_loc Unable To Read Inode Block
When: 2008-03-11 Completed: 2008-10-11 Target Distribution Baltix BOSS Juju Charms linux ext3_get_inode_loc unable to read inode block Collection Debian Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) Project (Find…) Status Importance Invalid Undecided Assigned to Nobody Me Remote Watch None, the status of the bug is updated manually. None, the status of the bug is updated manually. URL: The information about this bug in Launchpad is automatically pulled daily from the remote bug. Comment on this change (optional) Email me about changes to this bug report linux (Ubuntu) Edit Invalid Undecided Unassigned Edit You need to log in to change this bug's status. Affecting: linux (Ubuntu) Filed here by: Fred When: 2008-03-10 Completed: 2008-10-29 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) Project (Find…) Status Importance Invalid Undecided Assigned to Nobody Me Comment on this change (optional) Email me about changes to this bug report Also affects project (?) Also affects distribution/package Nominate for series Bug Description I am running Ubuntu 8.04 "Hardy Heron" (alpha). MSI P35 Neo Samsung SpinPoint T166 500 gb (7200 rpm, SATA-2, 16 mb cache) Samsung SpinPoint T166 250 gb (7200 rpm, SATA-2, 16 mb cache) sda1 = Windows XP sdb1 = Linux So I am listening to MP3 music in Rhythmbox 0.11.4, and surfing with Mozilla Firefox 3.0b3 and perhaps doing some other stuff, like maybe running apt-update && upgrade && clean && autoclean && autoremove or something in a Term
redhat com> Subject: Re: EXT3 errors and / filesystem readonly. Date: Mon, 31 Aug 2009 15:27:00 -0400 Hello, I have a production RHEL ES 4U6 server encountered EXT3 filesystem errors. Subsequently local / Root (/dev/cciss/c0d0p2) and one emcpower device went readonly. I had to reboot the server and FSCK and then remount both the filesystems back to normal. I have both Linux running in local hdd and https://bugs.launchpad.net/bugs/200747 other filesystems mounted from EMC clariion. I see the below errors in the /var/log/messages. Aug 26 20:45:41 zmcs kernel: Error:Mpx:Path Bus 0 Tgt 1 Lun 6 to APM00083500788 is dead. Aug 26 20:45:41 zmcs kernel: Error:Mpx:Path Bus 0 Tgt 1 Lun 6 to 600601607D0122005484F535FE81DE11 is marked as dead; volume ID has https://www.redhat.com/archives/redhat-list/2009-August/msg00211.html changed. Aug 26 20:45:43 zmcs kernel: Error:Mpx:Path Bus 0 Tgt 0 Lun 6 to APM00083500788 is dead. Aug 26 20:45:43 zmcs kernel: Error:Mpx:Path Bus 0 Tgt 0 Lun 6 to 600601607D0122005484F535FE81DE11 is marked as dead; volume ID has changed. Aug 26 20:46:43 zmcs kernel: Error:Mpx:All paths to 600601607D0122005484F535FE81DE11 are dead. Aug 26 20:46:43 zmcs kernel: Error:Mpx:600601607D0122005484F535FE81DE11 is dead. .... ....... ......... Aug 27 02:12:04 zmcs kernel: EXT3-fs error (device dm-2): ext3_find_entry: reading directory #55511780 offset 1 Aug 27 02:12:04 zmcs kernel: Aborting journal on device dm-2. Aug 27 02:12:04 zmcs kernel: EXT3-fs error (device dm-2): ext3_find_entry: reading directory #55511780 offset 2 Aug 27 02:12:04 zmcs kernel: EXT3-fs error (device dm-2): ext3_find_entry: reading directory #55511780 offset 3 Aug 27 02:13:06 zmcs kernel: EXT3-fs error (device dm-2): ext3_get_inode_loc: unable to read inode block - inode=130155080, block=260309012 Aug 27 02:13:42 zmcs kernel: EXT3-fs error (device dm-2): ext3_readdir: directory #123682826 contains a hole at o
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 https://forums.opensuse.org/showthread.php/480458-Testing-hard-disk-Failure-or-not forums do not accept user names with a dash "-") Also, logging in lets https://ubuntuforums.org/archive/index.php/t-1502877.html 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 fs error Switch to 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) ext3_get_inode_loc unable to because the motherboard 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
external USB harddrive. I havn't had any problems with the previous Ubuntu version but I don't know if it's related to that. When I leave my PC on at night I usually find the OS have forgotten about the device. It's not in Gparted. I have mounted the harddrive to a folder but when I click on it it shows an empty folder. The mount is done via /etc/fstab If I reboot it says the device is not yet ready and asks if I want to wait, continue or do something manually. I've found out that I turn off the harddrive and on again it becomes available (under a new device name, /sdd instead og /sdc). And I can access the files and folders on the drive. If I reboot and turn off the device and on again before the boot is complete everything is back to normal. Any idea on what's going on? dileepmJune 6th, 2010, 12:53 PMHi, I am not sure if your problem is for any specific reason. But try this procedure in general http://starksolutions.blogspot.com/2010/05/linux-auto-mount-partitions.html I assume that external hard drives are considered removable drives (like flash/pen drives) tbressonJune 10th, 2010, 10:48 AMI'm not sure that's the issue. But thanks for the reply and the link :) It's there some kind of system log that explains why the connection to the harddrive was dropped or something like that? tbressonJune 15th, 2010, 08:34 AMLet's say I loose the connection to the drive. Is there any commands or anything like that I can write to check out some sort of logs that'll help find out what happend? tbressonJune 22nd, 2010, 06:23 AMdmesg said this: (added to main topic) [32243.112055] usb 1-1: reset high speed USB device using ehci_hcd and address 2 [32258.224041] usb 1-1: device descriptor read/64, error -110 [32273.440026] usb 1-1: device descriptor read/64, error -110 [32273.656030] usb 1-1: reset high speed USB device using ehci_hcd and address 2 [32288.768027] usb 1-1: device descriptor read/64, error -110 [32303.984042] usb 1-1: