On Thu, Oct 3, 2019 at 1:14 PM JH <jupiter.hce@xxxxxxxxx> 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/
Re: How the bad blocks occured in despite MTD manages the bad blocks
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: How the bad blocks occured in despite MTD manages the bad blocks
- From: Richard Weinberger <richard.weinberger@xxxxxxxxx>
- Date: Thu, 3 Oct 2019 15:28:04 +0200
- Cc: linux-mtd <linux-mtd@xxxxxxxxxxxxxxxxxxx>
- In-reply-to: <CAA=hcWTzAMU5GvGzcG2Ha5RH_=QUTEAa3gZkMoe=cgtZGG+h+Q@mail.gmail.com>
- References: <CAA=hcWSR52BJB4+k2k4CwLTQUVmvJvR=bjRx6kqe2aar-PH21w@mail.gmail.com> <CAFLxGvxg3dYoiiTy7=vNwC75s529akqx0DO3ozLrP_TbhATr_g@mail.gmail.com> <CAA=hcWTzAMU5GvGzcG2Ha5RH_=QUTEAa3gZkMoe=cgtZGG+h+Q@mail.gmail.com>
- Follow-Ups:
- References:
- Prev by Date: Re: How the bad blocks occured in despite MTD manages the bad blocks
- Next by Date: [PATCH 4.4 06/99] mtd: cfi_cmdset_0002: Use chip_good() to retry in do_write_oneword()
- Previous by thread: Re: How the bad blocks occured in despite MTD manages the bad blocks
- Next by thread: Re: How the bad blocks occured in despite MTD manages the bad blocks
- Index(es):
 |