From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <gentoo-embedded+bounces-4476-garchives=archives.gentoo.org@lists.gentoo.org> Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id E6E42139085 for <garchives@archives.gentoo.org>; Thu, 19 Jan 2017 21:52:19 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DBAC3234130; Thu, 19 Jan 2017 21:52:16 +0000 (UTC) Received: from mail-pf0-x231.google.com (mail-pf0-x231.google.com [IPv6:2607:f8b0:400e:c00::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 6282A23412E for <gentoo-embedded@lists.gentoo.org>; Thu, 19 Jan 2017 21:52:12 +0000 (UTC) Received: by mail-pf0-x231.google.com with SMTP id y143so16503054pfb.0 for <gentoo-embedded@lists.gentoo.org>; Thu, 19 Jan 2017 13:52:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:subject:from:to:date:in-reply-to:references:mime-version; bh=0YY3bDJcg6C7W1JpgojssSloC+qbHnVYZC3PUjQBC6Q=; b=aXeW8TBOtcjdGvL13Mnck6e9quAMCISasUyVsNK4JwfbnSvg4Ayqs5G8PRBoV4MuID 6d7jJlNdXnKfEuNW9j4ssqKTLYKKJJB5BDJnSs89A40Boinb6zE5AWxAKMYLjLd6jWfB NXNOqnBysdEUwLwqxaAWXryZycQlHXQLMj27wo84DBOQLyk2fn7Y8myJ2EeJWNU/obfO NsDsAzkb4CmFaVxDMnUfb30tACUuYxiovPFVcM7EDuO3cQjU8zCqtkQb1TrzUv9k87Qr rJqd6M5Sbj4Idp4n4gHokuqF3MLtJtgSYo2fNLAwWm2Xkn05fnxi7mmY3/s7rUfAEbrb /EFQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:mime-version; bh=0YY3bDJcg6C7W1JpgojssSloC+qbHnVYZC3PUjQBC6Q=; b=czc+b5i6C/kBX3sIm3hrOG3lInlQGaJC9vMwmDvNE7cwWpt8hmBoTV9Q6u8JVThH0c tq9Z5xaWK9Hy3lvcSkKnkInYmNrS3L6neBMFT0tbfC7NMiqy7+7DGhb8l6XMDAOKTWdw ztauG64vK+O19DwrMExhwPzZIUp6q3P2fxLOhxdB12DTPgdBAGzAizSzo5ScEWm0V4WX 8rY+M2R/P11huayJGkFrmILDkV7hgGPrkS4z5z9F0rWPQatrJHZ/wWYmbfSIHmJ7+Aa4 iS4hXSlB0wJlV/XhWPOwCdp0mE2WV+Oq+YxFGwITsHdgpthKhr265SSK0ZAATqwGPQkI 8Jbg== X-Gm-Message-State: AIkVDXLumRAktsl7eKvO14kKYnDTRF1yYSgnpYWsB8eUiK5/zGctefrQr0iEueZv41v6tA== X-Received: by 10.84.248.10 with SMTP id p10mr16144350pll.87.1484862544792; Thu, 19 Jan 2017 13:49:04 -0800 (PST) Received: from debian-gazelle.localdomain (wsip-24-249-178-180.ph.ph.cox.net. [24.249.178.180]) by smtp.gmail.com with ESMTPSA id w11sm11017811pfk.75.2017.01.19.13.49.03 for <gentoo-embedded@lists.gentoo.org> (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 19 Jan 2017 13:49:03 -0800 (PST) Message-ID: <1484862541.17180.2.camel@localhost> Subject: Re: [gentoo-embedded] glibc fails in upgrade From: herminio.hernandezjr@gmail.com To: gentoo-embedded@lists.gentoo.org Date: Thu, 19 Jan 2017 14:49:01 -0700 In-Reply-To: <984edc2d-afc3-1a29-e95b-f8b6b3f378ba@freeharbor.net> References: <CAJRA9dzuRjtyGORosRA42AoOA6epV5ChrVAEHHQj97ms5Yp9kA@mail.gmail.com> <984edc2d-afc3-1a29-e95b-f8b6b3f378ba@freeharbor.net> Content-Type: multipart/alternative; boundary="=-bpabl0v1gRLrngT64FLh" X-Mailer: Evolution 3.22.4-1 Precedence: bulk List-Post: <mailto:gentoo-embedded@lists.gentoo.org> List-Help: <mailto:gentoo-embedded+help@lists.gentoo.org> List-Unsubscribe: <mailto:gentoo-embedded+unsubscribe@lists.gentoo.org> List-Subscribe: <mailto:gentoo-embedded+subscribe@lists.gentoo.org> List-Id: Gentoo Linux mail <gentoo-embedded.gentoo.org> X-BeenThere: gentoo-embedded@lists.gentoo.org Reply-to: gentoo-embedded@lists.gentoo.org Mime-Version: 1.0 X-Archives-Salt: 99b18b65-f8a6-494c-b4c2-0cd5ac390948 X-Archives-Hash: 27d9ea2aab2a89df83f5a89b854440de --=-bpabl0v1gRLrngT64FLh Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit 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. > --=-bpabl0v1gRLrngT64FLh Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: 7bit <html><head></head><body bgcolor="#404552" text="#d3dae3" link="#a9caf1" vlink="#d3dae3"><div>I took the SD card out of the PI and ran fsck from my laptop. This fixed the partition.</div><div><br></div><div>Thanks for the advice!</div><div>Herminio</div><div><br></div><div>On Tue, 2017-01-10 at 17:51 -0500, Anthony G. Basile wrote:</div><blockquote type="cite"><pre>On 1/10/17 4:49 PM, Herminio Hernandez, Jr. wrote: <blockquote type="cite"> 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 <<a href="https://www.reddit.com/r/linuxquestions/comments/4b47r2/has_anyone_ever_gotten_structure_needs_cleaning/">https://www.reddit.com/r/linuxquestions/comments/4b47r2/has_anyone_ever_gotten_structure_needs_cleaning/</a>>*. 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 </blockquote> 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. </pre></blockquote></body></html> --=-bpabl0v1gRLrngT64FLh--