From: Matt Dunnington <m@dunnington.eu>
To: linux-fsdevel@vger.kernel.org
Subject: jfs_fsck fails at boot, after upgrade to recent kernel
Date: Sun, 01 May 2011 14:03:17 +0100 [thread overview]
Message-ID: <4DBD5A15.4080700@dunnington.eu> (raw)
Hi
I'd appreciate some help with an issue that I'm experiencing with my
root jfs partition being mounted read only at boot, due to jfs_fsck
returning code 11. Below is a log of what is shown on screen after
jfs_fsck has been run on the rootfs:
Could not locate device by label or uuid
warning... fsck.jfs for device /dev/md1 exiteds with signal 11
operational error
remounting root filesystem read/write
mount: / not mounted already, or bad option
root filesystem could not be mounted read/write
The issue arose when I upgraded my kernel from 2.6.28-gentoo-r2 to
2.6.38-gentoo-r3. If I boot my original kernel the system still boots
fine, but booting the new kernel results in the errors above. Is this a
bug, or perhaps I have missed something in my kernel configuration?
Many thanks in advance for your kind assistance. Please let me know if
you need any further information.
Best Regards
Matt Dunnington
next reply other threads:[~2011-05-01 13:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-01 13:03 Matt Dunnington [this message]
2011-05-04 15:09 ` jfs_fsck fails at boot, after upgrade to recent kernel Dave Kleikamp
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=4DBD5A15.4080700@dunnington.eu \
--to=m@dunnington.eu \
--cc=linux-fsdevel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).