From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 114821] Frequent and recurring ext4 "bad header invalid magic" errors on a healthy drive
Date: Fri, 18 Mar 2016 05:17:17 +0000 [thread overview]
Message-ID: <bug-114821-13602-qUviac8L8F@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-114821-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=114821
--- Comment #2 from Lukas <dse.ssd@gmail.com> ---
I was suspecting hardware problems initially, but now I don't think that's the
case - both short and long SMART self-tests as well as vendor diagnostic tests
(including a 10 hour scan of every sector) produced no errors. All SMART
attributes that would indicate electromechanical failure are at zero raw
values.
I've also just verified that the 'clunk sound' is a head load cycle. By copying
a certain file I can trigger the error and if I check the SMART attributes
before and after, I see the 'Load Cycle Count (ID #193)' increased by 2.
Currently it is at 1823.
Unfortunately, I'm not skilled enough to quickly test with a vanilla kernel on
the same OS. Would it be useful if I'd tested using Raspbian Jessie with 4.1
kernel instead? I can exchange the SD card with the OS while keeping everything
else the same.
The stackexchange post is indeed mine and I have not posted this to the
linux-ext4 mailing list. Should I do so? I apologize if I'm doing things out of
order here, I have little experience in official linux bug reporting.
Attaching dmesg ans syslog files.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2016-03-18 5:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 5:05 [Bug 114821] New: Frequent and recurring ext4 "bad header invalid magic" errors on a healthy drive bugzilla-daemon
2016-03-17 7:38 ` [Bug 114821] " bugzilla-daemon
2016-03-18 5:17 ` bugzilla-daemon [this message]
2016-03-18 5:17 ` bugzilla-daemon
2016-03-18 5:18 ` bugzilla-daemon
2016-03-18 22:46 ` bugzilla-daemon
2016-03-20 6:46 ` bugzilla-daemon
2016-03-20 15:12 ` bugzilla-daemon
2016-03-20 20:50 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-114821-13602-qUviac8L8F@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.