From: Maciej Borzecki <maciej.borzecki@open-rnd.pl>
To: Philip Balister <philip@balister.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: wic debug suggestions
Date: Wed, 22 Oct 2014 10:16:57 +0200 [thread overview]
Message-ID: <1674569.uPgRA3xl4g@comp-006-thk> (raw)
In-Reply-To: <2808693.YK3zlpjAPq@comp-006-thk>
On Wednesday 22 of October 2014 09:03:03 Maciej Borzecki wrote:
> On Monday 20 of October 2014 13:45:37 Philip Balister wrote:
> > I'm trying to make an sd card using the sdimage-bootpart.wks file. I've
> > made an image and dd'ed it to a card. The card has a good vfat
> > partition, but the ext4 partition won't mount. Looks like bad
> > superblock. I can format the partition manually, so partitions seem OK
> > and card works.
> >
> > Does anyone have any suggestions for debugging this?
>
> In default wks, the vfat partition is /boot, ext4 is /. If I understood you
> correctly / fails to mount, is that right?
>
> I've rebuilt an image with poky rev
> 8ac8eca2e3bd8c78e2b31ea974930ed0243258a3. Loading via loopback and mounting
> partition 2 (/ in this case) works fine.
Verified with current master 924da20c6f2f183fa7e930e4c3c6b14c090acbe5, works
fine. The image works both as loopback and in BeagleBone Black.
>
> Can you post the output this command?
> wic create -D -e core-image-minimal sdimage-bootpart
>
> Ext4 image is built by image.bbclass (Tom, please correct me if I'm wrong on
> this). It should be possible to do the loopback/mount thing with the image
> file as well. Can you check if you can mount it this way?
Disregard this statement as it is incorrect. I forgot that wic builds all
images separately from bitbake. The temp ext4 appears only if you have run wic
at this location: /var/tmp/wic/build/rootfs_root.ext4. Try to mount that.
Also try running tune2fs -l /var/tmp/wic/build/rootfs_root.ext4 to see if that
produces any reasonable output.
--
Maciej Borzęcki
Senior Software Engineer Open-RnD Sp. z o.o.
www.open-rnd.pl, Facebook, Twitter
mobile: +48 telefon, fax: +48 42 657 9079
Niniejsza wiadomość wraz z załącznikami może zawierać chronione prawem lub
poufne informacje i została wysłana wyłącznie do wiadomości i użytku osób, do
których została zaadresowana. Jeśli wiadomość została otrzymana przypadkowo
zabrania się jej kopiowania lub rozsyłania do osób trzecich. W takim przypadku
uprasza się o natychmiastowe zniszczenie wiadomości oraz poinformowanie
nadawcy o zaistniałej sytuacji za pomocą wiadomości zwrotnej. Dziękujemy.
This message, including any attachments hereto, may contain privileged or
confidential information and is sent solely for the attention and use of the
intended addressee(s). If you are not an intended addressee, you may neither
use this message nor copy or deliver it to anyone. In such case, you should
immediately destroy this message and kindly notify the sender by reply email.
Thank you.
next prev parent reply other threads:[~2014-10-22 8:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 17:45 wic debug suggestions Philip Balister
2014-10-21 15:09 ` Tom Zanussi
2014-10-21 17:19 ` Tom Zanussi
2014-10-22 7:03 ` Maciej Borzecki
2014-10-22 8:16 ` Maciej Borzecki [this message]
2014-10-22 12:40 ` Tom Zanussi
2014-10-22 12:48 ` Maciej Borzecki
2014-10-22 13:26 ` Tom Zanussi
2014-10-22 13:26 ` Philip Balister
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=1674569.uPgRA3xl4g@comp-006-thk \
--to=maciej.borzecki@open-rnd.pl \
--cc=openembedded-core@lists.openembedded.org \
--cc=philip@balister.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