From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 111961] ext4 umount - invalid opcode with PLEXTOR PX-128M6G-2242
Date: Fri, 05 Feb 2016 23:09:52 +0000 [thread overview]
Message-ID: <bug-111961-13602-n9cW1R47KG@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-111961-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=111961
--- Comment #3 from Sebastian <info@dynpages.de> ---
Thank you very much for the fast response! dmesg output from current boot
doesn't include any ext4 message. I don't have a syslog daemon running, but I
grepped for fsck and ext4 on journald, hoping that helps.
The problem just occurred once - after manual recovering from systemd recovery
shell the system boots fine again . I'll check on the logs and will provide
more information in case anything fails again. If you miss something or if I
can help you there get back to me anytime.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2016-02-05 23:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 16:16 [Bug 111961] New: ext4 umount - invalid opcode with PLEXTOR PX-128M6G-2242 bugzilla-daemon
2016-02-05 16:19 ` [Bug 111961] " bugzilla-daemon
2016-02-05 21:02 ` bugzilla-daemon
2016-02-05 23:09 ` bugzilla-daemon [this message]
2016-02-05 23:11 ` bugzilla-daemon
2016-02-05 23:11 ` bugzilla-daemon
2016-02-07 3:50 ` bugzilla-daemon
2016-02-07 9:14 ` bugzilla-daemon
2016-02-07 9:15 ` bugzilla-daemon
2016-02-10 17:33 ` bugzilla-daemon
2017-03-06 20:29 ` bugzilla-daemon
2017-03-08 10:48 ` 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-111961-13602-n9cW1R47KG@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.