From: Sid Boyce <sboyce-QgLWrMLu8clzjhtm8Ag3mw@public.gmane.org>
To: Beagle Board
<beagleboard-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>,
"linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Beagleboard -XM and 32GB microSD card oddities
Date: Thu, 30 Jun 2011 10:50:59 +0100 [thread overview]
Message-ID: <4E0C4703.9000207@blueyonder.co.uk> (raw)
I'm not really looking for a solution, just supplying some information
in case anyone is contemplating a >16GB card.
Using Ubuntu 11.04 ARM or x86_64, I cannot create an ext4 partition that
will mount. Doing fsck.ext4 appears to fix the filesystem, but rerunning
fsck.ext4 a second time gives the same errors.
Only BTRFS works.
A BTRFS partition can be created without a problem. I then use rsync to
copy across all the data from the 16GB (ext4) partition and it mounts
without errors. After the rsync I create the excluded directories proc,
sys, tmp, media.
I get a kernel oops (2.6.39-x1) on boot up of the 32GB card.
I'm still trying to figure why I'm getting the oops that I don't have on
the original 16GB card.
Regards
Sid.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Senior Staff Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks
--
You received this message because you are subscribed to the Google Groups "Beagle Board" group.
To post to this group, send email to beagleboard-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to beagleboard+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit this group at http://groups.google.com/group/beagleboard?hl=en.
next reply other threads:[~2011-06-30 9:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 9:50 Sid Boyce [this message]
2011-06-30 14:43 ` Beagleboard -XM and 32GB microSD card oddities Gregoire Gentil
2011-06-30 15:49 ` Sid Boyce
2011-06-30 15:52 ` Sid Boyce
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=4E0C4703.9000207@blueyonder.co.uk \
--to=sboyce-qglwrmlu8clzjhtm8ag3mw@public.gmane.org \
--cc=beagleboard-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.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