From: Richard Weinberger <richard.weinberger@gmail.com>
To: JH <jupiter.hce@gmail.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: How the bad blocks occured in despite MTD manages the bad blocks
Date: Thu, 3 Oct 2019 15:28:04 +0200 [thread overview]
Message-ID: <CAFLxGvwUK=hb6b_hX8HSTVzAZW7djBL_3bRWvTXcVUw+FuBTmw@mail.gmail.com> (raw)
In-Reply-To: <CAA=hcWTzAMU5GvGzcG2Ha5RH_=QUTEAa3gZkMoe=cgtZGG+h+Q@mail.gmail.com>
On Thu, Oct 3, 2019 at 1:14 PM JH <jupiter.hce@gmail.com> wrote:
> I was told by hardware engineer, it was broken by bad block problem.
Did he inspect the filesystem in detail?
If he said so based on the same information you shared with us, it was
pure guesswork.
> After those lines, the boot stopped in an emergent mode in a prompt to
> suggest to log in by Ctl-D, but that could not work, I was not able to
> log into the file system, nor can I get kernel log. From your
> experience, what could be likely the causes, hardware or software?
Without logs I cannot say anything, sorry.
--
Thanks,
//richard
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-10-03 13:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 10:35 How the bad blocks occured in despite MTD manages the bad blocks JH
2019-10-02 16:09 ` Steve deRosier
2019-10-02 16:13 ` Richard Weinberger
2019-10-03 11:14 ` JH
2019-10-03 13:28 ` Richard Weinberger [this message]
2019-10-03 21:26 ` JH
2019-10-03 23:44 ` Steve deRosier
2019-10-04 6:36 ` JH
2019-10-05 8:38 ` Richard Weinberger
2019-10-05 21:56 ` JH
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='CAFLxGvwUK=hb6b_hX8HSTVzAZW7djBL_3bRWvTXcVUw+FuBTmw@mail.gmail.com' \
--to=richard.weinberger@gmail.com \
--cc=jupiter.hce@gmail.com \
--cc=linux-mtd@lists.infradead.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).