public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: herminio.hernandezjr@gmail.com
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] glibc fails in upgrade
Date: Thu, 19 Jan 2017 14:49:01 -0700	[thread overview]
Message-ID: <1484862541.17180.2.camel@localhost> (raw)
In-Reply-To: <984edc2d-afc3-1a29-e95b-f8b6b3f378ba@freeharbor.net>

[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]

I took the SD card out of the PI and ran fsck from my laptop. This
fixed the partition.
Thanks for the advice!Herminio
On Tue, 2017-01-10 at 17:51 -0500, Anthony G. Basile wrote:
> On 1/10/17 4:49 PM, Herminio Hernandez, Jr. wrote:
> > I just ran emerge -avuND @world my RPI3 and my build crashed when
> > it tried
> > to merge glibc with this error "structure needs cleaning".I found
> > some
> > instructions on how to fix it *here
> > <https://www.reddit.com/r/linuxquestions/comments/4b47r2/has_anyone
> > _ever_gotten_structure_needs_cleaning/>*.
> > However, when I got to the part where I needed to fsck I received
> > an error
> > that the filesystem is mounted. Do I need to turn off the pi and
> > place the
> > SD card on my laptop to fix?
> > 
> > Thanks
> > Herminio
> > 
> 
> 1. The error has nothing to do with the glibc upgrade.
> 
> 2. You can't run fsck on a mounted filesystem.  You can force an fsck
> on
> reboot with ` touch /forcefsck` but its probably safer to do it via
> your
> laptop as you can control just how you run fsck.
> 

[-- Attachment #2: Type: text/html, Size: 1357 bytes --]

      parent reply	other threads:[~2017-01-19 21:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-10 21:49 [gentoo-embedded] glibc fails in upgrade Herminio Hernandez, Jr.
2017-01-10 22:51 ` Anthony G. Basile
2017-01-10 22:59   ` Herminio Hernandez, Jr.
2017-01-19 21:49   ` herminio.hernandezjr [this message]

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=1484862541.17180.2.camel@localhost \
    --to=herminio.hernandezjr@gmail.com \
    --cc=gentoo-embedded@lists.gentoo.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