All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars Michael <lh_post@yahoo.com>
To: linux-mtd@lists.infradead.org
Subject: mount ubi volume fails: No such device
Date: Mon, 7 Feb 2011 07:05:24 -0800 (PST)	[thread overview]
Message-ID: <130828.38998.qm@web30203.mail.mud.yahoo.com> (raw)

> On Mon, 2011-01-31 at 02:35 -0800, Lars Michael wrote:
> > Hi,
> >
> > I am trying to mount an UBI volume, but it fails:
> >
> > # mount -t ubifs ubi0_0 /mnt/ubi
> > mount: mounting ubi0_0 on /mnt/ubi failed: No such device
> >
> > Using mkfs.ubifs and ubinize I have prepared an image containing 
> > three volumes. On the target I have used ubiformat to flash the 
> > image and ubiattach to attach to mtd1.
> >
> > Target kernel: 2.6.29, platform m68k (mcf54418). The UBI tools on 
> > the host are built from git://git.infradead.org/mtd-utils.git.
> >
> > Everything looks fine to me, see below, but how do I mount a volume? 
> > I have tried various ways to refer to the device (like ubi0:datafs,
> > ubi0_0) without luck.
> >
> > Thanks for any help!
> 
> Do you have ubifs in /proc/filesystems?
> 

Well, no! UBIFS is included in the kernel, why doesn't it show up?
Now I changed it to a kernel object and now it appears in proc/filesystems after running insmod.

Next I try to attach again. But now other errors occur, see below:

[root@M54418TWR /]# ubiattach /dev/ubi_ctrl -m 1
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    126976 bytes
UBI: smallest flash I/O unit:    2048
UBI: VID header offset:          2048 (aligned 2048)
UBI: data offset:                4096
UBI: volume 2 ("datafs") re-sized from 133 to 821 LEBs
UBI: attached mtd1 to ubi0
UBI: MTD device name:            "ubi"
UBI: MTD device size:            255 MiB
UBI: number of good PEBs:        2036
UBI: number of bad PEBs:         4
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     3
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 2036
UBI: number of PEBs reserved for bad PEB handling: 20
UBI: max/mean erase counter: 6/2
UBI: background thread "ubi_bgt0d" started, PID 642 UBI device number 0, total 2036 LEBs (258523136 bytes, 246.5 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB) [root@M54418TWR /]# UBI: scrubbed PEB 9, data moved to PEB 2035
UBI: scrubbed PEB 10, data moved to PEB 1963
UBI: scrubbed PEB 13, data moved to PEB 1767 ...
UBI: scrubbed PEB 860, data moved to PEB 1098
UBI: scrubbed PEB 863, data moved to PEB 1097 UBI warning: ubi_eba_copy_leb: read data back from PEB 1092 and it is different UBI error: wear_leveling_worker: error -22 while moving PEB 868 to PEB 1092 UBI warning: ubi_ro_mode: switch to read-only mode UBI error: do_work: work failed with error code -22 UBI error: ubi_thread: ubi_bgt0d: work failed with error code -22

Regards,
- Lars Michael





             reply	other threads:[~2011-02-07 15:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-07 15:05 Lars Michael [this message]
2011-02-07 15:27 ` mount ubi volume fails: No such device Artem Bityutskiy
  -- 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-09  8:32 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
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=130828.38998.qm@web30203.mail.mud.yahoo.com \
    --to=lh_post@yahoo.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 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.