From: Lars Michael <lh_post@yahoo.com>
To: dedekind1@gmail.com
Cc: linux-mtd@lists.infradead.org
Subject: mount ubi volume fails: No such device
Date: Mon, 14 Feb 2011 04:47:36 -0800 (PST) [thread overview]
Message-ID: <269683.2447.qm@web30204.mail.mud.yahoo.com> (raw)
In-Reply-To: <1297681309.2854.16.camel@localhost>
--- On Mon, 14/2/11, Artem Bityutskiy <dedekind1@gmail.com> wrote:
> From: Artem Bityutskiy <dedekind1@gmail.com>
> Subject: Re: mount ubi volume fails: No such device
> To: "Lars Michael" <lh_post@yahoo.com>
> Cc: linux-mtd@lists.infradead.org
> Date: Monday, 14 February, 2011, 12:01
> On Mon, 2011-02-14 at 00:49 -0800,
> Lars Michael wrote:
> > Here is how i made the UBI image:
> > ./mkfs.ubifs -m 2048 -e 126976 -c 874 -v -Q -r
> ./rootfs rootfs.img
> > ./mkfs.ubifs -m 2048 -e 126976 -c 36 -v -Q -r ./progfs
> progfs.img
> > ./mkfs.ubifs -m 2048 -e 126976 -c 49 -v -Q -r ./datafs
> datafs.img
> > ubinize -o ubi.img -p 128KiB -m 2048 -v
> ubi-config.ini
>
> You also need to give this parameter to UBI:
> vid_hdr_offs=2048
>
> I.e., modprobe ubi mtd=1 vid_hdr_offs=2048
>
> Or if UBI is compiled-in, boot with the following kernel
> argument:
>
> ubi.vid_hdr_offs=2048
>
> With this option UBI will not use sub-pages at all. I think
> it makes
> sense for you to try how it works this way.
>
I believe this is the correct syntax:
[root@M54418TWR /]# insmod ubi mtd=1,2048
UBI error: ubi_init: UBI error: cannot initialize UBI, error -19
insmod: cannot insert '/lib/modules/2.6.29/kernel/drivers/mtd/ubi/ubi.ko': No such device
Unfortunately, booting Linux the NAND flash is now detected bad, so I do not have an mtd1! what is the best way to try to recover? I do not understand how the flash can suddenly become bad!
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xca (Micron NAND 256MiB 3,3V 16-bit)
Bad block table not found for chip 0
Bad block table not found for chip 0
Scanning device for bad blocks
Bad eraseblock 0 at 0x000000000000
Bad eraseblock 1 at 0x000000020000
Bad eraseblock 2 at 0x000000040000
Bad eraseblock 3 at 0x000000060000
Bad eraseblock 4 at 0x000000080000
Bad eraseblock 5 at 0x0000000a0000
Bad eraseblock 6 at 0x0000000c0000
<cut>
Bad eraseblock 2046 at 0x00000ffc0000
Bad eraseblock 2047 at 0x00000ffe0000
No space left to write bad block table
fsl_nfc: NAND Flash not found !
m25p80 spi1.1: at26df081a (1024 Kbytes)
Creating 1 MTD partitions on "Atmel at26df081a SPI Flash chip":
0x000000000000-0x000000100000 : "at26df081a"
DSPI: Coldfire master initialized
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Thanks and regards,
- Lars
next prev parent reply other threads:[~2011-02-14 12:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 8:32 mount ubi volume fails: No such device Lars Michael
2011-02-11 14:28 ` Artem Bityutskiy
2011-02-14 8:49 ` Lars Michael
2011-02-14 11:01 ` Artem Bityutskiy
2011-02-14 12:47 ` Lars Michael [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-02-18 10:57 Lars Michael
2011-02-25 10:45 ` Artem Bityutskiy
2011-02-28 8:49 ` Lars Michael
2011-02-14 10:22 Lars Michael
[not found] <9186EF1D8AB86E40B9C8009D36864D0403CA4342@dhreinsvxb03.messaging.danaherad.com>
2011-02-11 14:21 ` Lars Michael
2011-02-11 14:35 ` Artem Bityutskiy
2011-02-11 14:57 ` Artem Bityutskiy
2011-02-09 12:34 Lars Michael
2011-02-11 14:32 ` Artem Bityutskiy
2011-02-07 15:05 Lars Michael
2011-02-07 15:27 ` Artem Bityutskiy
2011-01-31 10:35 Lars Michael
2011-02-06 14:19 ` Artem Bityutskiy
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=269683.2447.qm@web30204.mail.mud.yahoo.com \
--to=lh_post@yahoo.com \
--cc=dedekind1@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).