Ext3-fs Error Device Sda In Start_transaction Journal Has Aborted
Contents |
md0) in start_transaction: Journal has aborted General support questions including new installations Post Reply Print view Search Advanced search 5 posts • Page 1 of 1 pilot12 Posts:
Ext3-fs Error In Ext3_reserve_inode_write Journal Has Aborted
9 Joined: 2006/09/29 19:06:41 EXT3-fs error (device md0) in start_transaction: Journal has aborted ext3-fs error fortigate Quote Postby pilot12 » 2006/11/07 09:29:33 EXT3-fs error (device md0) in start_transaction: Journal has abortedI get this spitting out over
Ext3-fs Error Unable To Read Inode Block
and over again, only redress is a reboot.There seem to be no other errors and the server works normally afterwards. This error mostly happens overnight, there is no data lost.I have no ext3-fs error (device dm-0) idea what is causing this and have searched Google and found several other instances of this error without a successful conclusion. there is some articles here:http://lkml.org/lkml/2003/8/6/24http://comments.gmane.org/gmane.linux.kernel/78181http://forums.techguy.org/unix-linux...device-dm.htmlI have so far reloaded all the software (Distribution: CentOs version 4 X86_64 Dell PowerEdge 2900 2 gig Ram. Raid array 5) and this is still happening every night. Is this a Kernal Bug ?Can anyone give me a ext3-fs error (device dm-0) ext3_journal_start_sb detected aborted journal lead on what to do next ? This is the first time using Linux on our servers, and I really need to get over this problem so any help will be greatly appreciated. Top matt_garman Posts: 37 Joined: 2006/10/18 14:14:21 Re: EXT3-fs error (device md0) in start_transaction: Journal has aborted Quote Postby matt_garman » 2006/11/13 23:29:28 Bump.I just experienced the same thing on a Dell Poweredge 1950. I have two 140GB hard drives in a RAID-1 (mirror) array.My guess is that the problem lies in one of three areas: (1) one or both hard drives are dying, (2) the RAID controller is buggy/dying and/or (3) there is a software problem (e.g. RAID driver).Any ideas?Thanks,Mattp.s. This machine has the Dell PERC 5/i integrated RAID card. Relevant part of dmesg:megasas: 00.00.02.00 Sat Oct 15 19:03:34 EDT 2005megasas: 0x1028:0x0015:0x1028:0x1f03: bus 2:slot 14:func 0ACPI: PCI interrupt 0000:02:0e.0[A] -> GSI 78 (level, low) -> IRQ 193scsi0 : LSI Logic SAS based MegaRAID driver Vendor: DP Model: BACKPLANE Rev: 1.00 Type: Enclosure ANSI SCSI revision: 05 Vendor: DELL Model: PERC 5/i Rev: 1.00 Type: Direct-Access ANSI SCSI revision: 05SCSI device sda: 285474816 512-byte hdwr sectors (146163 MB)sda: ask
Assigned to Milestone kernel-package (Ubuntu) Edit Invalid Medium Ben Collins Edit You need to log in to change this bug's status. Affecting: kernel-package (Ubuntu) Filed here by: Paul McGarry When:
Ext3-fs Error (device Sda1)
2005-12-14 Assigned: 2006-01-13 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex ext3-fs error deleted inode referenced Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) Project
Ext3 Fs Error Ext3_journal_start_sb Detected Aborted Journal
(Find…) Status Importance Invalid Medium Assigned to Me Ben Collins (ben-collins) Comment on this change (optional) Email me about changes to this bug report Also affects project (?) Also affects distribution/package http://www.centos.org/forums/viewtopic.php?t=34807 Nominate for series Bug Description I have a development server running Ubuntu 5.04 HWDB ID: f7759e4f272e325092d2736243ee163c uname -a: Linux dev 2.6.10-5-686-smp #1 SMP Mon Oct 10 11:40:56 UTC 2005 i686 GNU/Linux Overnight there appears to have been a filesystem problem of some sort and the console was spewing: EXT3-fs error (device sda1) in start_transaction: Journal has aborted If I hit ctrl-alt-del then it https://bugs.launchpad.net/bugs/27056 also says: scsi0 (0:0): rejecting I/O to offline device * cannot execute /sbin/shutdown scsi0 (0:0): rejecting I/O to offline device scsi0 (0:0): rejecting I/O to offline device so a hard reboot was necessary. If there is any more info I can provide, or something I should do to obtain more info if it happens again, please let me know. I don't think there's anything logged about the occurance because with the disk gone there was nowhere to log it.... Add tags Tag help Ben Collins (ben-collins) wrote on 2005-12-14: #1 This is a hardware issue in either the scsi host controller or the driver itself. Check the cables, reseat the host controller in the PCI slot, etc. The ext3 error you were seeing is a consequence of the scsi controller making the drive off-line (you probably didn't see this portion of the error because it had been scolled off the screen). If it continues to happen, then I suspect one of the two is failing. See full activity log To post a comment you must log in. Report a bug This report contains Public information Edit Ever
EXT3-fs error (device sda1) in start_transaction: Journal has aborted Publikacja 13 listopada 2012 przez c0m4r — Brak komentarzy ↓ If your system abruptly loses power, or http://c0m4r.lamarr.pl/blog/?p=28 if a RAID card is beginning to fail, you might see https://www.redhat.com/archives/ext3-users/2005-March/msg00029.html an ominous message like this within your logs: EXT3-fs error (device sda1) in start_transaction: Journal has aborted Basically, the system is telling you that it's detected a filesystem/journal mismatch, and it can't utilize the journal any longer. When this situation pops up, the filesystem gets mounted read-only fs error almost immediately. To fix the situation, you can remount the partition as ext2 (if it isn't your active root partition), or you can commence the repair operations. If you're working with an active root partition, you will need to boot into some rescue media and perform these operations there. If this error occurs with an additional partition besides the ext3-fs error (device root partition, simply unmount the broken filesystem and proceed with these operations. Remove the journal from the filesystem (effectively turning it into ext2): # tune2fs -O ^has_journal /dev/sda1 Now, you will need to fsck it to correct any possible problems (throw in a -y flag to say yes to all repairs, -C for a progress bar): # e2fsck /dev/sda1 Once that's finished, make a new journal which effectively makes the partition an ext3 filesystem again: # tune2fs -j /dev/sda1 You should be able to mount the partition as an ext3 partition at this time: # mount -t ext3 /dev/sda1 /mnt/fixed Be sure to check your dmesg output for any additional errors after you're finished! ‹ top (Linux) Top - VIRT, RES i SHR › Napisano w Sysadmin Dodaj komentarz Anuluj pisanie odpowiedzi Musisz się zalogować, aby móc dodać komentarz. Najnowsze wpisy Top - VIRT, RES i SHR EXT3-fs error (device sda1) in start_transaction: Journal has aborted top (Linux) Odzyskiwanie root-a w Debianie Zmiana kodowania systemu i plików z ISO-8859-2 (latin2) na UTF-8 Archiwa Lis
on hitachi deskstars Date: Sat, 19 Mar 2005 05:44:48 -0500 On Wed, Feb 09, 2005 at 01:17:48AM +0100, Christian wrote: > > maybe you can elaborate a bit more on the "corrupted journals": what does > "fsck" say, what's in the kernel log (during mount). if we know the > symptoms, perhaps someone can find the root of the problem... > I'm seeing the same behavior, but after only a few hours under heavy load and also with two new Hitachi SATA drives, showing as sda and sdb. System is Fedora Core 3 running 2.6.10-1.770_FC3. I had to use the "irqpoll" kernel option to not lock hard when the sata driver loads. >From /var/log/dmesg: SCSI subsystem initialized libata version 1.10 loaded. sata_sil version 0.8 ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11 PCI: setting IRQ 11 as level-triggered ACPI: PCI interrupt 0000:00:11.0[A] -> GSI 11 (level, low) -> IRQ 11 ata1: SATA max UDMA/100 cmd 0xE083A080 ctl 0xE083A08A bmdma 0xE083A000 irq 11 ata2: SATA max UDMA/100 cmd 0xE083A0C0 ctl 0xE083A0CA bmdma 0xE083A008 irq 11 irq 11: nobody cared (try booting with the "irqpoll" option. [