From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-user+bounces-186472-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 14DCF138334
	for <garchives@archives.gentoo.org>; Thu,  7 Mar 2019 11:32:38 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 1A53BE0951;
	Thu,  7 Mar 2019 11:32:32 +0000 (UTC)
Received: from mail-wm1-x344.google.com (mail-wm1-x344.google.com [IPv6:2a00:1450:4864:20::344])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by pigeon.gentoo.org (Postfix) with ESMTPS id 90425E0923
	for <gentoo-user@lists.gentoo.org>; Thu,  7 Mar 2019 11:32:31 +0000 (UTC)
Received: by mail-wm1-x344.google.com with SMTP id g20so8802383wmh.5
        for <gentoo-user@lists.gentoo.org>; Thu, 07 Mar 2019 03:32:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
        h=from:to:reply-to:subject:date:message-id:in-reply-to:references
         :mime-version;
        bh=rXh6NfPzMYsVFreqPwB5P8V2XgvLaKy3UzXMlyAewZc=;
        b=LAh7jkgjgyCFx2F8HvvcItMsDmEcyeJF3ik8tz0brH5kpvd0leBQOOWn/0khdNYaFC
         Jyr0mQ8CCIyWYiTSXLj8OuHdG0j7TM+Jv8HOnapD1yRuhJqyna6GfSnRjcB0RTSvb/h3
         6gUGdkj9rjTQW0ZfJ+5Rz6aeEE4aJL5/V7pFMpiIptEaqqVF2NmkxjnIfTDoh/AeFKhX
         QLFVVWOk5/4ywEBvYkLKpAf8tBt/ttP94sq/ejXz/XwhOwQdNya2C4IC5nn9VmgGC5HS
         asOIvx8EAthLOgHmQTx2Za2t6veLnq+cwB2MLTXoQUuGT0/TwqZcu7zQ1oJgVJm3bRlI
         3QSQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:from:to:reply-to:subject:date:message-id
         :in-reply-to:references:mime-version;
        bh=rXh6NfPzMYsVFreqPwB5P8V2XgvLaKy3UzXMlyAewZc=;
        b=S8DWnjiUZ0+CXCXy/3stlVhullsLm/AW4QTaXm6VN0f6aXI/KE4QKGeMs8WQ+ACaQJ
         Q1sNgg4L3D++fHNVURFCbmXdTW8F/tBWbphdgWaY/y1QjayheaBawmZrlbVbASN2Y7/k
         AimGGWB/UKrAhGwJdQo/0SFkb5ZBWye2zTnsbQWf9ulMgD+2/hqjHdKHIcI2AzRXySuO
         YUHhBGH8pqoi00X5AEsYuVwRIwxz3W5aPF7K0War8u6pGOz2FhXWOW4s75phUmMdFVoy
         Frn+kH7+t8jBwbxkU5dXL59W3VtFqHsvsMyHRIm05TM68IMmlWwNR/qum/n8hJndLQo3
         s5qw==
X-Gm-Message-State: APjAAAUB1OSfNGeamo1ObkFhSU3mHYjC6aLVixdqxxtvN406NR1348KR
	FlxBvCQr8Q2gNn8Fg7fL4QPqEiSB
X-Google-Smtp-Source: APXvYqwYk+T0AjqoTxkP3SMcIDdptWppUODFm536uEYgncKhqsUakj/jTdnT0IE3fyg7mEmCWfBHiA==
X-Received: by 2002:a1c:790b:: with SMTP id l11mr5308674wme.54.1551958349600;
        Thu, 07 Mar 2019 03:32:29 -0800 (PST)
Received: from dell_xps.localnet (230.3.169.217.in-addr.arpa. [217.169.3.230])
        by smtp.gmail.com with ESMTPSA id 62sm3181590wra.46.2019.03.07.03.32.28
        for <gentoo-user@lists.gentoo.org>
        (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Thu, 07 Mar 2019 03:32:28 -0800 (PST)
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Emerge --sync source
Date: Thu, 07 Mar 2019 11:32:07 +0000
Message-ID: <2248135.JMcyjGid6S@dell_xps>
In-Reply-To: <25870333.8ERAaanbrm@peak>
References: <2837719.MWtaJtHztM@peak> <1551889882.229992.29.camel@openeye.net> <25870333.8ERAaanbrm@peak>
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart2119805.487jdFcWpF"; micalg="pgp-sha256"; protocol="application/pgp-signature"
X-Archives-Salt: 8a6688e2-c978-4cd8-aee2-ee1904d2cc19
X-Archives-Hash: 70b4ce454badbbc8a1f872e189c3be01

--nextPart2119805.487jdFcWpF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="UTF-8"

On Thursday, 7 March 2019 10:10:53 GMT Peter Humphrey wrote:
> On Wednesday, 6 March 2019 16:31:27 GMT Laurence Perkins wrote:
> > On Fri, 2019-03-01 at 10:12 +0000, Peter Humphrey wrote:
> > > [OT]
> > > Evidence is mounting that the Atom box is in terminal decline. I get
> > > things like batches of files in the portage tree changing owner, and
> > > then
> > > when I correct that, long lists of supposedly locally changed ebuilds
> > > preventing syncing. And when I boot weekly into its little rescue sys=
tem
> > > to backup the main system, the root filesystem remounts itself read-o=
nly
> > > while tar is running. Smartd recognises the SSD and runs daily tests,
> > > but
> > > reports no errors. No amount of wiping and reinstalling has helped so
> > > far.
> >=20
> > What filesystem are you running and how old is the SSD?  That sounds
> > like some of the symptoms EXT4 had on early generation flash media
> > where its assumptions about what order writes would physically make it
> > to the disk in were wrong, leading to corruption.
>=20
> The disk is a 64GB SanDisk SDSSDP device, which I bought five years ago to
> replace a failed spinning disk. All partitions are ext4 except /boot, whi=
ch
> is ext2.
>=20
> > So unless it was working correctly at some point in the past, try a
> > different filesystem.  EXT3 or BTRFS didn't have the same problems.
>=20
> It was working just fine until recently.
>=20
> > If it's just that the SSD is failing, then get a new one before
> > something important gets damaged and you have to redo the whole thing.
>=20
> Everything on it is disposable.
>=20
> The box is getting a bit long in the tooth: I bought it in November 2010.
> It's a single-core, 32-bit Atom N270 (not N2700). It doesn't owe me
> anything now, in spite of having cost =C2=A3450 at the time. I don't know
> whether it's worth throwing any more money at it. On the other hand, I see
> Amazon are only asking for =C2=A320 for a small SSD.
>=20
> The repeatability of some of the errors it throws makes me question wheth=
er
> the disk or something else is at fault. (What would cause a file system to
> be remounted read-only in the middle of its work?)

I can think of 3 things, but more learned M/L contributors may add to these:

1. The SATA connection has come loose.  With time and movement it can come=
=20
(slightly) adrift.  Pushing it back in fully fixes this problem - also see =
No.
2 below.

2. The physical connector's contacts are beginning to oxidise.  Reseat the=
=20
SATA cable connectors both on the drive and any ribbons on the MoBo.  This=
=20
usualy cleans any oxidisation.

3. The AHCI driver is deploying energy saving measures (aka. Aggressive Lin=
k=20
Power Management - ALPM).  Check the output of:

 cat /sys/class/scsi_host/host*/link_power_management_policy

If it doesn't say 'max_performance' you'll need to revisit your BIOS settin=
gs=20
and also PCIEASPM settings in the kernel.

4. Finally, there is a chance the PSU is playing up.


1 & 2 above are more noticeable on spinning disks, but it is a matter of sc=
ale=20
before SSDs are affected too.  If BIOS, kernel settings and drivers were no=
t=20
altered recently, then 1 & 2 merit attention in the first instance.


> I have a spare four-core, 64-bit Celeron box (I bought it for a purpose
> that's gone away). I've been wondering what to do with it, so maybe it can
> replace the Atom box. It's powerful enough to compile its own software,
> whereas the Atom needs help. Whichever I use, its job will be as a server
> of DNS, LAN mail, time and git. Maybe print too. Also it will fetch my
> ISP's POP mail and serve it over IMAP to this box.
>=20
> > The self-test capability of storage media is almost universally
> > horrible and you generally don't get a failure report until your data
> > has already been lost.  If your SMART output gives you the raw
> > statistics on the device instead of just pass/fail then analyzing that
> > usually gives a better indication of whether something is about to go
> > wrong.
>=20
> It seems to report only pass/fail, so that's not much help.
>=20
> Decisions, decisions...

Do short/long smartctl tests report no errors, assuming the disk comes with=
=20
S.M.A.R.T. capability?

=2D-=20
Regards,
Mick
--nextPart2119805.487jdFcWpF
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEt7MNaGaS6HvTUrEz6WnU8jC95dcFAlyBATcACgkQ6WnU8jC9
5dea0BAAlypBfdiVs+KHgsOAqo8mpvTzBkBBg9g1WFEfnenNhkFYcQ70qby2jtNg
G+gf3XJVWsa+p6S91id/+j2F9mNZlp04Lwqv6Q4tWfhTHidds3SBQ3CCoDMVNuqY
cR5gYTb2xCi6s+od+8lfIwY+bZOU8yfWIzCwTyQtxiqY8M1xkGqLavUj7xFR8BUk
0+FkTZcUYJBrxJcbCCu6Qkas2XSxXGE0rRzLOlSF80Jx9kHsvW3Oz6MBJ0QAYVb3
jolOdyhlemjnn70exmzjkX556vsy3BILCGtbZKv2m0Q3glmhxhnKkwg6rqX0QbFb
7+Z8WNPTqLLucfhSvzGLjHpVO0A8pemlvLeOGPpto6G4CerR1v0XsAdM1li47OQW
/q88ZhVRYdyTkyy3CH86X3jyMQMiLUFgN/N3eBrgbtNds7dNpERKIHVW3LWXwtY4
pcVqZdRV/iwhVy3OwTb9UoLWWjvA+55my2Vu5Uk1AQttAn8Wgkn+QOBAMwfYwB/q
znU/VnWqSFtgVbLH2/CN4C/pu/HJKeKG1EuvYPUcbRyl9vCu7klDEN3W2PgMMKm1
9RPyLjUclH26yLTyqGrE6i10gVl1Pc6mgDuzpOjS45JX9CRnWe1aDE/Ann/brBKI
KdmOkkxiU1mhbizIt3MHZIW1jWkXumBoYaFOmHca5mUH7jF5nXA=
=IgNT
-----END PGP SIGNATURE-----

--nextPart2119805.487jdFcWpF--