Forum Discussion
Nimbostratusext3_abort called detected aborted journal
Hi guys, I need some help here. Recently we upgraded one of our F5 LTM from (I think it was 9.4.2 to 10.2.4) Both switches were working fine for a few weeks and after a while, one started acting little bit. Active switch becomes inactive and throws an error to the console
I found some answers on other sites, but since its F5 switch I guess it will be better if I ask here...
[admin@NIMZMMU-BIGIP1:Active] ~ ext3_abort called. EXT3-fs error (device dm-1): ext3_journal_start_sb: Detected aborted journal<6>ata4.00: configured for UDMA /133 (device error ignored) Remounting filesystem read-only ext3_abort called. EXT3-fs error (device dm-0): ext3_journal_start_sb: Detected aborted journal Remounting filesystem read-only EXT3-fs error (device dm-0): ext3_find_entry: reading directory 2539521 offset 0 EXT3-fs error (device dm-0): ext3_find_entry: <6>ata4: EH complete EXT3-fs error (device dm-6): ext3_find_entry: <6>ata4: EH complete EXT3-fs error (device dm-6): ext3_find_entry: reading directory 49687 offset 0<5>SCSI device sda: drive ca
5 Replies
What_Lies_Bene1Cirrostratus
Looks like a file system or disk error. You could try booting to another partition and see if it goes away, if it does perhaps zap and rebuild the dodgy one. If that's no help its more likely to be an underlying disk issue.
If you can, I'd call F5 support anyway, looks pretty serious.
electromecca_15thanks, What Lies Beneath I will log this issue with F5 support (I can't even do switchboot -l or ls -l or sbin/reboot :) ).
- What_Lies_Bene1Cool, you're welcome. Let us know if there's anything to be learnt. Cheers
- electromecca_15
Hello Folks,
Just a quick update, I was in contact with F5 support and they're saying it's a defective hdd.
- What_Lies_Bene1OK, cool, thanks for letting us know.
