Re: [gentoo-user] systemd, libgudev and bug 552036

[Adam Carter]

Still blocked - anything else i should try?

tnx.


# emerge -a1 =sys-apps/systemd-226-r2 dev-libs/libgudev virtual/libgudev

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild  N ] dev-libs/libgudev-230  USE="introspection -debug
(-static-libs)" ABI_X86="(64) -32 (-x32)"
[ebuild U  ] virtual/libgudev-230 [215-r3]
[ebuild U  ] sys-apps/systemd-226-r2 [218-r5] USE="kdbus* -gnuefi%
-importd% -nat%"
[blocks B  ] sys-apps/systemd[gudev(-)] ("sys-apps/systemd[gudev(-)]"
is blocking dev-libs/libgudev-230)

!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:

sys-apps/systemd:0

  (sys-apps/systemd-226-r2:0/2::gentoo, ebuild scheduled for merge) pulled
in by
=sys-apps/systemd-226-r2 (Argument)

  (sys-apps/systemd-218-r5:0/2::gentoo, installed) pulled in by

sys-apps/systemd[python(-),python_targets_python2_7(-)?,python_single_target_python2_7(+)?,python_targets_python3_3(-)?,python_single_target_python3_3(+)?,python_targets_python3_4(-)?,python_single_target_python3_4(+)?]
required by (net-analyzer/fail2ban-0.9.2:0/0::gentoo, installed)




It may be possible to solve this problem by using package.mask to
prevent one of those packages from being selected. However, it is also
possible that conflicting dependencies exist such that they are
impossible to satisfy simultaneously.  If such a conflict exists in
the dependencies of two different packages, then those packages can
not be installed simultaneously. You may want to try a larger value of
the --backtrack option, such as --backtrack=30, in order to see if
that will solve this conflict automatically.

For more information, see MASKED PACKAGES section in the emerge man
page or refer to the Gentoo Handbook.


 * Error: The above package list contains packages which cannot be
 * installed at the same time on the same system.

  (dev-libs/libgudev-230:0/0::gentoo, ebuild scheduled for merge) pulled in
by

dev-libs/libgudev:0/0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?,introspection?,static-libs?]
(dev-libs/libgudev:0/0[abi_x86_64(-),introspection]) required by
(virtual/libgudev-230:0/0::gentoo, ebuild scheduled for merge)
dev-libs/libgudev


On Fri, Dec 18, 2015 at 2:35 PM, Mike Gilbert  wrote:

> On Dec 17, 2015 9:37 PM, "Adam Carter"  wrote:
> >
> > The gudev USE flag is deprecated from systemd, and the functionality is
> now provided by libgudev (see bug 552036). However, i get the following
> block;
> >
> > # emerge -a1 =sys-apps/systemd-226-r2 dev-libs/libgudev
> >
> > These are the packages that would be merged, in order:
> >
> > Calculating dependencies... done!
> > [ebuild  N ] dev-libs/libgudev-230  USE="introspection -debug
> (-static-libs)" ABI_X86="(64) -32 (-x32)"
> > [ebuild U  ] sys-apps/systemd-226-r2 [218-r5] USE="kdbus* -gnuefi%
> -importd% -nat%"
> > [blocks B  ] sys-apps/systemd[gudev(-)]
> ("sys-apps/systemd[gudev(-)]" is blocking dev-libs/libgudev-230)
> >
> > So i plan to emerge libgudev with nodeps (to avoid the blocker), then
> upgrade systemd which will of course build without the gudev flag and I
> think I should be ok. Do I understand correctly?
>
> Add virtual/libgudev to your emerge line and it should auto-resolve the
> blocker.
>

Re: [gentoo-user] systemd, libgudev and bug 552036

[Neil Bothwick]

On Fri, 18 Dec 2015 21:00:02 +1100, Adam Carter wrote:

> Still blocked - anything else i should try?
> 
> tnx.
> 
> 
> # emerge -a1 =sys-apps/systemd-226-r2 dev-libs/libgudev virtual/libgudev

Why are you including libgudev in the merge list? If it's a dependency
of systemd, let portage take care of it.
 
> These are the packages that would be merged, in order:
> 
> Calculating dependencies... done!
> [ebuild  N ] dev-libs/libgudev-230  USE="introspection -debug
> (-static-libs)" ABI_X86="(64) -32 (-x32)"
> [ebuild U  ] virtual/libgudev-230 [215-r3]
> [ebuild U  ] sys-apps/systemd-226-r2 [218-r5] USE="kdbus* -gnuefi%
> -importd% -nat%"
> [blocks B  ] sys-apps/systemd[gudev(-)]
> ("sys-apps/systemd[gudev(-)]" is blocking dev-libs/libgudev-230)

Try "emerge -1avt systemd" for more information about what portage really
wants.


-- 
Neil Bothwick

Top Oxymorons Number 26: Software documentation


pgpSQWiHZmwEY.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] Unknown problem causing incorrect mounting and daemons not starting

[Thomas Sigurdsen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

The problems/strange state persists with mtab being a symlink and then
rebooting. Mtab stays a symlink through reboots too.

> I wouldn't expect the symlink to fix anything without a reboot (since
> the main problem is at startup time). I'm not sure if the dbus issue
> is separate or not - if it is the same it seems odd that it won't
> start even after getting everything mounted by hand, anyway.
> 
> -John Sent from my phone
> 
> Thomas Sigurdsen  wrote:
> 
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>> 
>>> It seems to me the root of your problems is fsck failing because
>>> (it thinks) the partitions are already mounted.
>>> 
>>> Is your mtab a symlink to /proc/mounts as it "should" be?
>> 
>> Just checked, and mtab is not a symlink. It is a plain text file.
>> 
>> Just tried takinga backup of mtab and symlinking /proc/mounts onto 
>> /etc/mtab yields no different results when trying
>> `/etc/init.d/dbus start`. Is this something I fix somewhere else or
>> maybe I just need to reboot the system after symlinking.
>> 
>> -BEGIN PGP SIGNATURE- Version: GnuPG v2
>> 
>> iQEcBAEBCAAGBQJWbIDrAAoJEMUjE08Xv1s5xiMH/RHhiWklaZiMes7h5PSVLP7M 
>> JLJJ14jpqytxPfDujZfUznT+Yed/QxvwNSG2lK7YidxKxrTwB/F8cslFKHulDMc/ 
>> Sp4knftRAdHu9f21lkt+LWgfryu6ZxOu4lzCjGev/47yFU7nOb/5BWfBVinGm8vo 
>> lZVweuEQJOmqs1k7cl5EpYMbKzx6YYuQpkGddV5VK9Gq99r6zSCThpc/XkS49gLF 
>> DTblOWBXcJcmw3vWwsYHwdGz2eIAdCN5LJ0brRCwocWneZUXRouDuITBhGCtWL1W 
>> gnSp6W/WWY9khINvZmiJUxxP0Oe+YQ+88MBLly2f4ptn4NUVJFA+gRm6XOlw/50= 
>> =Wsr+ -END PGP SIGNATURE-
>> 

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJWc+axAAoJEMUjE08Xv1s5y+oH/0lrOLDp7bNWQWgvIW2JN8as
y+qxKPvW4WCXg0677qB/PCVcwPwdhQlKeSp2D1Qbip7pJTqoNYnTmpuIW41BQjNZ
o4/8HV4LuWNUJBIVT45h7RODkLnRy1ewgd1z4PbQjAORLuCElGR3/XXa/G28Pi5j
QTz9yvauPyZEAxrOARTDRLj3Q9ZVTMBR3cOXJ3vnemBmxkE8Di+9EO6ev5N2i4U7
kbIyXU6DmFgco5XPWtNn84biNrlEue3O4vz/VL9j62yuJ/B2l+YK02ocuTXhJfZY
pAvYfDF6FzeWcNmfO4PW6TPP4EV4WVT8amTiMUdlzQXW7eMdb2S0RlAtYYTEbvg=
=lb1j
-END PGP SIGNATURE-

Re: [gentoo-user] Unknown problem causing incorrect mounting and daemons not starting

[Alan Mackenzie]

Hello, Thomas.

On Fri, Dec 18, 2015 at 10:57:53AM +, Thomas Sigurdsen wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256

> The problems/strange state persists with mtab being a symlink and then
> rebooting. Mtab stays a symlink through reboots too.

This is a stab in the dark, but recently when an emerge upgraded udev, I
got a warning message that CONFIG_FHANDLE wasn't set in my kernel config.
(This is in General setup, prompt "open by fhandle syscalls".)

Without this setting, I got errors on booting, and indeed my ethernet
connection didn't come up.  After setting CONFIG_FHANDLE and rebuilding
my kernel, the problem went away.

Might you have this same problem?

-- 
Alan Mackenzie (Nuremberg, Germany).

Re: [gentoo-user] systemd, libgudev and bug 552036

[Mike Gilbert]

On Fri, Dec 18, 2015 at 5:00 AM, Adam Carter  wrote:
> Still blocked - anything else i should try?

Perhaps your ABI_X86 flags are mismatched.

You keep truncating/editing the emerge output, so we have to make
guesses. Stop doing that please.

[gentoo-user] Hard drive noise

[Dale]

Howdy,

I finally got a new 3TB hard drive.  I got one on sale for under $100. 
Anyway, I put it in, did the LVM thing and set up my backup script, very
basic as it is.  A little bit ago, I noticed a sound.  It's not a click
or a metallic type sound.  It sounds like the heads are doing random
reads/writes and the heads are moving but doing so noisily.  Thing is,
there is no drive activity according to gkrellm or iotop.  All the
drives should be basically idle.  I even went to single user mode to be
sure nothing in KDE was doing some index thingy or something.  Still,
nothing showed that there should be any drive activity, including the
hard drive light on the case. 

Also, I do not know WHICH drive is making this noise yet.  I have four
in there running and they are physically mounted close together.  I'm
not sure I would know which one it is even if I take the side off the
case.  I just know that it is making this odd noise.  Here is some info
from hdparm:


root@fireball / # hdparm -i /dev/sdd

/dev/sdd:

 Model=ST3000DM001-1ER166, FwRev=CC25, SerialNo=Z501R198
 Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
 RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
 BuffType=unknown, BuffSize=unknown, MaxMultSect=16, MultSect=off
 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=5860533168
 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes:  pio0 pio1 pio2 pio3 pio4
 DMA modes:  mdma0 mdma1 mdma2
 UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6
 AdvancedPM=yes: unknown setting WriteCache=enabled
 Drive conforms to: Reserved:  ATA/ATAPI-4,5,6,7

 * signifies the current active mode

root@fireball / #
 

That's the new drive up above.  Old drive that is basically the same
drive, different batch I would assume, is below.


root@fireball / # hdparm -i /dev/sdc

/dev/sdc:

 Model=ST3000DM001-1CH166, FwRev=CC29, SerialNo=W1F4C31Q
 Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
 RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
 BuffType=unknown, BuffSize=unknown, MaxMultSect=16, MultSect=16
 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=5860533168
 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes:  pio0 pio1 pio2 pio3 pio4
 DMA modes:  mdma0 mdma1 mdma2
 UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6
 AdvancedPM=yes: unknown setting WriteCache=enabled
 Drive conforms to: Reserved:  ATA/ATAPI-4,5,6,7

 * signifies the current active mode

root@fireball / #


The last SMART test I ran showed no problems but I have a fresh one
running as I type on all drives.  Will update if it shows anything. 

Thoughts? 

Dale

:-)  :-) 

Re: [gentoo-user] Hard drive noise

[Dale]

Ian Bloss wrote:
>
> Is it a seagate?
>
>

It would be a Seagate, yes.  From SMART:

=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.14 (AF)
Device Model: ST3000DM001-1ER166
 

You know some history on this thing?

Dale

:-)  :-) 

Re: [gentoo-user] Hard drive noise

[Bill Kenworthy]

On 19/12/15 08:01, Dale wrote:
> Howdy,
> 
> I finally got a new 3TB hard drive.  I got one on sale for under $100. 
> Anyway, I put it in, did the LVM thing and set up my backup script, very
> basic as it is.  A little bit ago, I noticed a sound.  It's not a click
> or a metallic type sound.  It sounds like the heads are doing random
> reads/writes and the heads are moving but doing so noisily.  Thing is,
> there is no drive activity according to gkrellm or iotop.  All the
> drives should be basically idle.  I even went to single user mode to be
> sure nothing in KDE was doing some index thingy or something.  Still,
> nothing showed that there should be any drive activity, including the
> hard drive light on the case. 
> 
> Also, I do not know WHICH drive is making this noise yet.  I have four
> in there running and they are physically mounted close together.  I'm
> not sure I would know which one it is even if I take the side off the
> case.  I just know that it is making this odd noise.  Here is some info
> from hdparm:
> 
> 
> root@fireball / # hdparm -i /dev/sdd
> 
> /dev/sdd:
> 
>  Model=ST3000DM001-1ER166, FwRev=CC25, SerialNo=Z501R198
>  Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
>  RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
>  BuffType=unknown, BuffSize=unknown, MaxMultSect=16, MultSect=off
>  CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=5860533168
>  IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
>  PIO modes:  pio0 pio1 pio2 pio3 pio4
>  DMA modes:  mdma0 mdma1 mdma2
>  UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6
>  AdvancedPM=yes: unknown setting WriteCache=enabled
>  Drive conforms to: Reserved:  ATA/ATAPI-4,5,6,7
> 
>  * signifies the current active mode
> 
> root@fireball / #
>  
> 
> That's the new drive up above.  Old drive that is basically the same
> drive, different batch I would assume, is below.
> 
> 
> root@fireball / # hdparm -i /dev/sdc
> 
> /dev/sdc:
> 
>  Model=ST3000DM001-1CH166, FwRev=CC29, SerialNo=W1F4C31Q
>  Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
>  RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
>  BuffType=unknown, BuffSize=unknown, MaxMultSect=16, MultSect=16
>  CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=5860533168
>  IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
>  PIO modes:  pio0 pio1 pio2 pio3 pio4
>  DMA modes:  mdma0 mdma1 mdma2
>  UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6
>  AdvancedPM=yes: unknown setting WriteCache=enabled
>  Drive conforms to: Reserved:  ATA/ATAPI-4,5,6,7
> 
>  * signifies the current active mode
> 
> root@fireball / #
> 
> 
> The last SMART test I ran showed no problems but I have a fresh one
> running as I type on all drives.  Will update if it shows anything. 
> 
> Thoughts? 
> 
> Dale
> 
> :-)  :-) 
> 
> 

Mechanics trick - place a largish screwdriver end on each hard drive
case in turn and the handle end to your ear.  You can hear difference in
sound quite clearly.

BillK

Re: [gentoo-user] systemd, libgudev and bug 552036

[Adam Carter]

>
> On Fri, Dec 18, 2015 at 5:00 AM, Adam Carter 
> wrote:
> > Still blocked - anything else i should try?
>
> Perhaps your ABI_X86 flags are mismatched.
>
> You keep truncating/editing the emerge output, so we have to make
> guesses. Stop doing that please.
>
> Sorry - here's the full output;

# emerge -a1 =sys-apps/systemd-226-r2 dev-libs/libgudev virtual/libgudev

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild  N ] dev-libs/libgudev-230  USE="introspection -debug
(-static-libs)" ABI_X86="(64) -32 (-x32)"
[ebuild U  ] virtual/libgudev-230 [215-r3]
[ebuild U  ] sys-apps/systemd-226-r2 [218-r5] USE="kdbus* -gnuefi%
-importd% -nat%"
[blocks B  ] sys-apps/systemd[gudev(-)] ("sys-apps/systemd[gudev(-)]"
is blocking dev-libs/libgudev-230)

!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:

sys-apps/systemd:0

  (sys-apps/systemd-226-r2:0/2::gentoo, ebuild scheduled for merge) pulled
in by
=sys-apps/systemd-226-r2 (Argument)

  (sys-apps/systemd-218-r5:0/2::gentoo, installed) pulled in by

sys-apps/systemd[python(-),python_targets_python2_7(-)?,python_single_target_python2_7(+)?,python_targets_python3_3(-)?,python_single_target_python3_3(+)?,python_targets_python3_4(-)?,python_single_target_python3_4(+)?]
required by (net-analyzer/fail2ban-0.9.2:0/0::gentoo, installed)




It may be possible to solve this problem by using package.mask to
prevent one of those packages from being selected. However, it is also
possible that conflicting dependencies exist such that they are
impossible to satisfy simultaneously.  If such a conflict exists in
the dependencies of two different packages, then those packages can
not be installed simultaneously. You may want to try a larger value of
the --backtrack option, such as --backtrack=30, in order to see if
that will solve this conflict automatically.

For more information, see MASKED PACKAGES section in the emerge man
page or refer to the Gentoo Handbook.


 * Error: The above package list contains packages which cannot be
 * installed at the same time on the same system.

  (dev-libs/libgudev-230:0/0::gentoo, ebuild scheduled for merge) pulled in
by

dev-libs/libgudev:0/0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?,introspection?,static-libs?]
(dev-libs/libgudev:0/0[abi_x86_64(-),introspection]) required by
(virtual/libgudev-230:0/0::gentoo, ebuild scheduled for merge)
dev-libs/libgudev

Re: [gentoo-user] Hard drive noise

[Dale]

cov...@ccs.covici.com wrote:
> Dale  wrote:
>
>>
>> That would likely work.  I've also used a water hose to do that on
>> cars.  I'm not sure how well that will work since the drives are only
>> like a inch apart.  With the screwdriver I might even be able to feel
>> it.  It's not very loud but I can hear it.  One reason I can hear it so
>> well, the fans on my case are very quiet.  In a quiet room, I can't hear
>> the fans.  I can hear this drive noise even with the TV at a reasonable
>> level.  With no TV, I can hear it pretty well.  My water hose trick
>> wouldn't likely work but your screwdriver idea might work in more than
>> one way. 
>>
>> I also found this after the reply from Ian.
>>
>> https://www.backblaze.com/blog/3tb-hard-drive-failure/ 
>>
>> No wonder they had it on sale.  Heck, why didn't they just say it was a
>> good door stop instead of a hard drive??? 
> I always try to get something a bit better than consumer drives, at
> least the equivalent of Western Digital Red which now has a longer
> warranty -- notice that a lot of drives have only ONE year warranties
> now?  Doesn't that make you feel warm and fuzzy?
>


I'm feeling something but I don't think warm and fuzzy would be it.  :-@@ 

Dale

:-)  :-) 

Re: [gentoo-user] Hard drive noise

[Dale]

Adam Carter wrote:
> See if SMART knows anything - run this against each drive (change $DRV
> to sda etc each time)
>
> smartctl -a /dev/$DRV | egrep
> '(^ID|Reallocated_Sector_C|Reported_Uncorrectable_Er|Command_Timeout|Current_Pending_Sect|Offline_Uncorre)'


It's currently running the test on most of these.  The sdd drive is the
new one.  The sdc drive is the same model but a couple years old, which
is why I bought this one since the last one was working fine.  The sda/b
drives are WD of different sizes.  sda has the OS on it and I think it
is the black type.  Sdb is a small backup drive that I copy things like
family photos and such too.  Yea, I also have DVD backups that are not
here at the house.  Here is the output:


root@fireball / # smartctl -a /dev/sdd  | egrep
'(^ID|Reallocated_Sector_C|Reported_Uncorrectable_Er|Command_Timeout|Current_Pending_Sect|Offline_Uncorre)'
ID# ATTRIBUTE_NAME  FLAG VALUE WORST THRESH TYPE 
UPDATED  WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct   0x0033   100   100   010Pre-fail 
Always   -   0
188 Command_Timeout 0x0032   100   100   000Old_age  
Always   -   0 0 0
197 Current_Pending_Sector  0x0012   100   100   000Old_age  
Always   -   0
198 Offline_Uncorrectable   0x0010   100   100   000Old_age  
Offline  -   0
root@fireball / # smartctl -a /dev/sdc | egrep
'(^ID|Reallocated_Sector_C|Reported_Uncorrectable_Er|Command_Timeout|Current_Pending_Sect|Offline_Uncorre)'
ID# ATTRIBUTE_NAME  FLAG VALUE WORST THRESH TYPE 
UPDATED  WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct   0x0033   100   100   010Pre-fail 
Always   -   0
188 Command_Timeout 0x0032   100   100   000Old_age  
Always   -   0 0 0
197 Current_Pending_Sector  0x0012   100   100   000Old_age  
Always   -   0
198 Offline_Uncorrectable   0x0010   100   100   000Old_age  
Offline  -   0
root@fireball / # smartctl -a /dev/sdb | egrep
'(^ID|Reallocated_Sector_C|Reported_Uncorrectable_Er|Command_Timeout|Current_Pending_Sect|Offline_Uncorre)'
ID# ATTRIBUTE_NAME  FLAG VALUE WORST THRESH TYPE 
UPDATED  WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct   0x0033   100   100   010Pre-fail 
Always   -   0
188 Command_Timeout 0x0032   100   100   000Old_age  
Always   -   0
197 Current_Pending_Sector  0x0012   100   100   000Old_age  
Always   -   0
198 Offline_Uncorrectable   0x0030   100   100   000Old_age  
Offline  -   0
root@fireball / # smartctl -a /dev/sda | egrep
'(^ID|Reallocated_Sector_C|Reported_Uncorrectable_Er|Command_Timeout|Current_Pending_Sect|Offline_Uncorre)'
ID# ATTRIBUTE_NAME  FLAG VALUE WORST THRESH TYPE 
UPDATED  WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct   0x0033   200   200   140Pre-fail 
Always   -   0
197 Current_Pending_Sector  0x0032   200   200   000Old_age  
Always   -   0
198 Offline_Uncorrectable   0x0030   200   200   000Old_age  
Offline  -   0
root@fireball / #



That looks OK to me BUT it is currently running the test.  What I may do
is redo the file system and copy a new set of backups over to it.  Sort
of give it a bit of a workout and see if that spots anything.  I bet as
it is, they won't let me return it or anything.  It is working, just
making that noise. 

Dale

:-)  :-) 

Re: [gentoo-user] Hard drive noise

[Dale]

Dale wrote:
> Howdy,
>
> I finally got a new 3TB hard drive.  I got one on sale for under $100. 
> Anyway, I put it in, did the LVM thing and set up my backup script, very
> basic as it is.  A little bit ago, I noticed a sound.  It's not a click
> or a metallic type sound.  It sounds like the heads are doing random
> reads/writes and the heads are moving but doing so noisily.  Thing is,
> there is no drive activity according to gkrellm or iotop.  All the
> drives should be basically idle.  I even went to single user mode to be
> sure nothing in KDE was doing some index thingy or something.  Still,
> nothing showed that there should be any drive activity, including the
> hard drive light on the case. 
>
> <<<  SNIP  >>>
>
> Thoughts? 
>
> Dale
>
> :-)  :-) 
>
>


Well ain't this interesting.  I was about to pull the side off that
monster Cooler Master HAF-932 when I moved my router, which sits on top
of the case over the top fan.  When I moved it, the sound stopped.  When
I sat it back down, it made that noise again but slightly different. 
So, I moved the router a little further back.  Now all is quiet.  No
weird noises for the last several minutes now. 

After finding out about this drive, now I'm nervous about depending on
it for a backup.  Bad thing is, I've got two of these drives now. 
Different batches but still.  Since firmware seems to have some affect
on this, is this a good version to have?

Firmware Version: CC25 

That's on the new drive.  The old drive is:

Firmware Version: CC29 

Weird, my new drive seems to have older firmware than my old drive. 
How's that work I wonder?  My old drive is a couple years old at least. 

I think I'm leery of all drives now.  I've had WDs fail, Seagate and
some other brand.  I just keep buying bad stuff.  :-(   I'm glad I don't
have to buy pacemakers.   :/ 

Dale

:-)  :-) 

Re: [gentoo-user] Hard drive noise

[Ian Bloss]

Is it a seagate?

On Fri, Dec 18, 2015, 19:02 Dale  wrote:

> Howdy,
>
> I finally got a new 3TB hard drive.  I got one on sale for under $100.
> Anyway, I put it in, did the LVM thing and set up my backup script, very
> basic as it is.  A little bit ago, I noticed a sound.  It's not a click
> or a metallic type sound.  It sounds like the heads are doing random
> reads/writes and the heads are moving but doing so noisily.  Thing is,
> there is no drive activity according to gkrellm or iotop.  All the
> drives should be basically idle.  I even went to single user mode to be
> sure nothing in KDE was doing some index thingy or something.  Still,
> nothing showed that there should be any drive activity, including the
> hard drive light on the case.
>
> Also, I do not know WHICH drive is making this noise yet.  I have four
> in there running and they are physically mounted close together.  I'm
> not sure I would know which one it is even if I take the side off the
> case.  I just know that it is making this odd noise.  Here is some info
> from hdparm:
>
>
> root@fireball / # hdparm -i /dev/sdd
>
> /dev/sdd:
>
>  Model=ST3000DM001-1ER166, FwRev=CC25, SerialNo=Z501R198
>  Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
>  RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
>  BuffType=unknown, BuffSize=unknown, MaxMultSect=16, MultSect=off
>  CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=5860533168
>  IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
>  PIO modes:  pio0 pio1 pio2 pio3 pio4
>  DMA modes:  mdma0 mdma1 mdma2
>  UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6
>  AdvancedPM=yes: unknown setting WriteCache=enabled
>  Drive conforms to: Reserved:  ATA/ATAPI-4,5,6,7
>
>  * signifies the current active mode
>
> root@fireball / #
>
>
> That's the new drive up above.  Old drive that is basically the same
> drive, different batch I would assume, is below.
>
>
> root@fireball / # hdparm -i /dev/sdc
>
> /dev/sdc:
>
>  Model=ST3000DM001-1CH166, FwRev=CC29, SerialNo=W1F4C31Q
>  Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
>  RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
>  BuffType=unknown, BuffSize=unknown, MaxMultSect=16, MultSect=16
>  CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=5860533168
>  IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
>  PIO modes:  pio0 pio1 pio2 pio3 pio4
>  DMA modes:  mdma0 mdma1 mdma2
>  UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6
>  AdvancedPM=yes: unknown setting WriteCache=enabled
>  Drive conforms to: Reserved:  ATA/ATAPI-4,5,6,7
>
>  * signifies the current active mode
>
> root@fireball / #
>
>
> The last SMART test I ran showed no problems but I have a fresh one
> running as I type on all drives.  Will update if it shows anything.
>
> Thoughts?
>
> Dale
>
> :-)  :-)
>
>
>

Re: [gentoo-user] systemd, libgudev and bug 552036

[Adam Carter]

 emerge -1avt systemd

These are the packages that would be merged, in reverse order:

Calculating dependencies... done!
[ebuild   R] sys-apps/systemd-218-r5:0/2::gentoo  USE="acl gudev
introspection kmod lz4 pam policykit python seccomp ssl (-apparmor) -audit
-cryptsetup -curl -doc -elfutils -gcrypt -http -idn -kdbus -lzma -qrcode
(-selinux) -sysv-utils -terminal {-test} -vanilla -xkb" ABI_X86="(64) -32
(-x32)" PYTHON_SINGLE_TARGET="python2_7 -python3_3 -python3_4"
PYTHON_TARGETS="python2_7 python3_4 -python3_3" 0 KiB

Total: 1 package (1 reinstall), Size of downloads: 0 KiB

WARNING: One or more updates/rebuilds have been skipped due to a dependency
conflict:

sys-apps/systemd:0

  (sys-apps/systemd-226-r2:0/2::gentoo, ebuild scheduled for merge)
conflicts with
>=sys-apps/systemd-212-r5:0/2[abi_x86_64(-),gudev(-),introspection(-)]
required by (virtual/libgudev-215-r3:0/0::gentoo, installed)


sys-apps/systemd[python(-),python_targets_python2_7(-),python_single_target_python2_7(+),python_targets_python3_4(-)]
required by (net-analyzer/fail2ban-0.9.2:0/0::gentoo, installed)




Would you like to merge these packages? [Yes/No]

Re: [gentoo-user] Hard drive noise

[Dale]

Bill Kenworthy wrote:
> On 19/12/15 08:01, Dale wrote:
>> Howdy,
>>
>> I finally got a new 3TB hard drive.  I got one on sale for under $100. 
>> Anyway, I put it in, did the LVM thing and set up my backup script, very
>> basic as it is.  A little bit ago, I noticed a sound.  It's not a click
>> or a metallic type sound.  It sounds like the heads are doing random
>> reads/writes and the heads are moving but doing so noisily.  Thing is,
>> there is no drive activity according to gkrellm or iotop.  All the
>> drives should be basically idle.  I even went to single user mode to be
>> sure nothing in KDE was doing some index thingy or something.  Still,
>> nothing showed that there should be any drive activity, including the
>> hard drive light on the case. 
>>
>>  SNIP 
>> The last SMART test I ran showed no problems but I have a fresh one
>> running as I type on all drives.  Will update if it shows anything. 
>>
>> Thoughts? 
>>
>> Dale
>>
>> :-)  :-) 
>>
>>
> Mechanics trick - place a largish screwdriver end on each hard drive
> case in turn and the handle end to your ear.  You can hear difference in
> sound quite clearly.
>
> BillK
>
>
>
>

That would likely work.  I've also used a water hose to do that on
cars.  I'm not sure how well that will work since the drives are only
like a inch apart.  With the screwdriver I might even be able to feel
it.  It's not very loud but I can hear it.  One reason I can hear it so
well, the fans on my case are very quiet.  In a quiet room, I can't hear
the fans.  I can hear this drive noise even with the TV at a reasonable
level.  With no TV, I can hear it pretty well.  My water hose trick
wouldn't likely work but your screwdriver idea might work in more than
one way. 

I also found this after the reply from Ian.

https://www.backblaze.com/blog/3tb-hard-drive-failure/ 

No wonder they had it on sale.  Heck, why didn't they just say it was a
good door stop instead of a hard drive??? 

Dale

:-)  :-) 

Re: [gentoo-user] Hard drive noise

[Adam Carter]

See if SMART knows anything - run this against each drive (change $DRV to
sda etc each time)

smartctl -a /dev/$DRV | egrep
'(^ID|Reallocated_Sector_C|Reported_Uncorrectable_Er|Command_Timeout|Current_Pending_Sect|Offline_Uncorre)'

Re: [gentoo-user] Hard drive noise

[Ian Bloss]

If it's under warranty you can return it because it's clicking. You just
have to be "persuasive"...

On Fri, Dec 18, 2015, 20:16 Dale  wrote:

> Adam Carter wrote:
> > See if SMART knows anything - run this against each drive (change $DRV
> > to sda etc each time)
> >
> > smartctl -a /dev/$DRV | egrep
> >
> '(^ID|Reallocated_Sector_C|Reported_Uncorrectable_Er|Command_Timeout|Current_Pending_Sect|Offline_Uncorre)'
>
>
> It's currently running the test on most of these.  The sdd drive is the
> new one.  The sdc drive is the same model but a couple years old, which
> is why I bought this one since the last one was working fine.  The sda/b
> drives are WD of different sizes.  sda has the OS on it and I think it
> is the black type.  Sdb is a small backup drive that I copy things like
> family photos and such too.  Yea, I also have DVD backups that are not
> here at the house.  Here is the output:
>
>
> root@fireball / # smartctl -a /dev/sdd  | egrep
>
> '(^ID|Reallocated_Sector_C|Reported_Uncorrectable_Er|Command_Timeout|Current_Pending_Sect|Offline_Uncorre)'
> ID# ATTRIBUTE_NAME  FLAG VALUE WORST THRESH TYPE
> UPDATED  WHEN_FAILED RAW_VALUE
>   5 Reallocated_Sector_Ct   0x0033   100   100   010Pre-fail
> Always   -   0
> 188 Command_Timeout 0x0032   100   100   000Old_age
> Always   -   0 0 0
> 197 Current_Pending_Sector  0x0012   100   100   000Old_age
> Always   -   0
> 198 Offline_Uncorrectable   0x0010   100   100   000Old_age
> Offline  -   0
> root@fireball / # smartctl -a /dev/sdc | egrep
>
> '(^ID|Reallocated_Sector_C|Reported_Uncorrectable_Er|Command_Timeout|Current_Pending_Sect|Offline_Uncorre)'
> ID# ATTRIBUTE_NAME  FLAG VALUE WORST THRESH TYPE
> UPDATED  WHEN_FAILED RAW_VALUE
>   5 Reallocated_Sector_Ct   0x0033   100   100   010Pre-fail
> Always   -   0
> 188 Command_Timeout 0x0032   100   100   000Old_age
> Always   -   0 0 0
> 197 Current_Pending_Sector  0x0012   100   100   000Old_age
> Always   -   0
> 198 Offline_Uncorrectable   0x0010   100   100   000Old_age
> Offline  -   0
> root@fireball / # smartctl -a /dev/sdb | egrep
>
> '(^ID|Reallocated_Sector_C|Reported_Uncorrectable_Er|Command_Timeout|Current_Pending_Sect|Offline_Uncorre)'
> ID# ATTRIBUTE_NAME  FLAG VALUE WORST THRESH TYPE
> UPDATED  WHEN_FAILED RAW_VALUE
>   5 Reallocated_Sector_Ct   0x0033   100   100   010Pre-fail
> Always   -   0
> 188 Command_Timeout 0x0032   100   100   000Old_age
> Always   -   0
> 197 Current_Pending_Sector  0x0012   100   100   000Old_age
> Always   -   0
> 198 Offline_Uncorrectable   0x0030   100   100   000Old_age
> Offline  -   0
> root@fireball / # smartctl -a /dev/sda | egrep
>
> '(^ID|Reallocated_Sector_C|Reported_Uncorrectable_Er|Command_Timeout|Current_Pending_Sect|Offline_Uncorre)'
> ID# ATTRIBUTE_NAME  FLAG VALUE WORST THRESH TYPE
> UPDATED  WHEN_FAILED RAW_VALUE
>   5 Reallocated_Sector_Ct   0x0033   200   200   140Pre-fail
> Always   -   0
> 197 Current_Pending_Sector  0x0032   200   200   000Old_age
> Always   -   0
> 198 Offline_Uncorrectable   0x0030   200   200   000Old_age
> Offline  -   0
> root@fireball / #
>
>
>
> That looks OK to me BUT it is currently running the test.  What I may do
> is redo the file system and copy a new set of backups over to it.  Sort
> of give it a bit of a workout and see if that spots anything.  I bet as
> it is, they won't let me return it or anything.  It is working, just
> making that noise.
>
> Dale
>
> :-)  :-)
>
>
>

Re: [gentoo-user] Hard drive noise

[Ian Bloss]

I've had more Seagates die over time than any other brand, I would
recommend getting your money back asap and finding another brand.

I work IT at a school and we no longer purchase seagate drives for their
failure rate.

On Fri, Dec 18, 2015, 19:41 Bill Kenworthy  wrote:

> On 19/12/15 08:01, Dale wrote:
> > Howdy,
> >
> > I finally got a new 3TB hard drive.  I got one on sale for under $100.
> > Anyway, I put it in, did the LVM thing and set up my backup script, very
> > basic as it is.  A little bit ago, I noticed a sound.  It's not a click
> > or a metallic type sound.  It sounds like the heads are doing random
> > reads/writes and the heads are moving but doing so noisily.  Thing is,
> > there is no drive activity according to gkrellm or iotop.  All the
> > drives should be basically idle.  I even went to single user mode to be
> > sure nothing in KDE was doing some index thingy or something.  Still,
> > nothing showed that there should be any drive activity, including the
> > hard drive light on the case.
> >
> > Also, I do not know WHICH drive is making this noise yet.  I have four
> > in there running and they are physically mounted close together.  I'm
> > not sure I would know which one it is even if I take the side off the
> > case.  I just know that it is making this odd noise.  Here is some info
> > from hdparm:
> >
> >
> > root@fireball / # hdparm -i /dev/sdd
> >
> > /dev/sdd:
> >
> >  Model=ST3000DM001-1ER166, FwRev=CC25, SerialNo=Z501R198
> >  Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
> >  RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
> >  BuffType=unknown, BuffSize=unknown, MaxMultSect=16, MultSect=off
> >  CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=5860533168
> >  IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
> >  PIO modes:  pio0 pio1 pio2 pio3 pio4
> >  DMA modes:  mdma0 mdma1 mdma2
> >  UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6
> >  AdvancedPM=yes: unknown setting WriteCache=enabled
> >  Drive conforms to: Reserved:  ATA/ATAPI-4,5,6,7
> >
> >  * signifies the current active mode
> >
> > root@fireball / #
> >
> >
> > That's the new drive up above.  Old drive that is basically the same
> > drive, different batch I would assume, is below.
> >
> >
> > root@fireball / # hdparm -i /dev/sdc
> >
> > /dev/sdc:
> >
> >  Model=ST3000DM001-1CH166, FwRev=CC29, SerialNo=W1F4C31Q
> >  Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
> >  RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
> >  BuffType=unknown, BuffSize=unknown, MaxMultSect=16, MultSect=16
> >  CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=5860533168
> >  IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
> >  PIO modes:  pio0 pio1 pio2 pio3 pio4
> >  DMA modes:  mdma0 mdma1 mdma2
> >  UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6
> >  AdvancedPM=yes: unknown setting WriteCache=enabled
> >  Drive conforms to: Reserved:  ATA/ATAPI-4,5,6,7
> >
> >  * signifies the current active mode
> >
> > root@fireball / #
> >
> >
> > The last SMART test I ran showed no problems but I have a fresh one
> > running as I type on all drives.  Will update if it shows anything.
> >
> > Thoughts?
> >
> > Dale
> >
> > :-)  :-)
> >
> >
>
> Mechanics trick - place a largish screwdriver end on each hard drive
> case in turn and the handle end to your ear.  You can hear difference in
> sound quite clearly.
>
> BillK
>
>
>
>

Re: [gentoo-user] Hard drive noise

[covici]

Dale  wrote:

> Bill Kenworthy wrote:
> > On 19/12/15 08:01, Dale wrote:
> >> Howdy,
> >>
> >> I finally got a new 3TB hard drive.  I got one on sale for under $100. 
> >> Anyway, I put it in, did the LVM thing and set up my backup script, very
> >> basic as it is.  A little bit ago, I noticed a sound.  It's not a click
> >> or a metallic type sound.  It sounds like the heads are doing random
> >> reads/writes and the heads are moving but doing so noisily.  Thing is,
> >> there is no drive activity according to gkrellm or iotop.  All the
> >> drives should be basically idle.  I even went to single user mode to be
> >> sure nothing in KDE was doing some index thingy or something.  Still,
> >> nothing showed that there should be any drive activity, including the
> >> hard drive light on the case. 
> >>
> >>  SNIP 
> >> The last SMART test I ran showed no problems but I have a fresh one
> >> running as I type on all drives.  Will update if it shows anything. 
> >>
> >> Thoughts? 
> >>
> >> Dale
> >>
> >> :-)  :-) 
> >>
> >>
> > Mechanics trick - place a largish screwdriver end on each hard drive
> > case in turn and the handle end to your ear.  You can hear difference in
> > sound quite clearly.
> >
> > BillK
> >
> >
> >
> >
> 
> That would likely work.  I've also used a water hose to do that on
> cars.  I'm not sure how well that will work since the drives are only
> like a inch apart.  With the screwdriver I might even be able to feel
> it.  It's not very loud but I can hear it.  One reason I can hear it so
> well, the fans on my case are very quiet.  In a quiet room, I can't hear
> the fans.  I can hear this drive noise even with the TV at a reasonable
> level.  With no TV, I can hear it pretty well.  My water hose trick
> wouldn't likely work but your screwdriver idea might work in more than
> one way. 
> 
> I also found this after the reply from Ian.
> 
> https://www.backblaze.com/blog/3tb-hard-drive-failure/ 
> 
> No wonder they had it on sale.  Heck, why didn't they just say it was a
> good door stop instead of a hard drive??? 

I always try to get something a bit better than consumer drives, at
least the equivalent of Western Digital Red which now has a longer
warranty -- notice that a lot of drives have only ONE year warranties
now?  Doesn't that make you feel warm and fuzzy?

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

 John Covici
 cov...@ccs.covici.com

[gentoo-user] anyone tried amdgpu (kernel module)

[Tsukasa Mcp_Reznor]

I have a Bonaire gpu, which has legacy support using the amdgpu kernel module.  
I currently use the Radeon dri module with radeonsi mesa drivers and am quite 
happy.  But gentoo being gentoo I thought I'd give the amdgpu a go for the fun 
of it.
Tried a few variations and keep coming up with a black screen on boot and it's 
hard locked.  I'm using the same Firmware includes that the radeon driver 
requires, and from reading it looks like that's fine with amdgpu, so I'm not 
sure what else could be the issue.
Has anyone here tried and had success with it?  I've tried Kernels 4.2 4.2.4 
4.3 and 4.3.2.  So I believe I'm missing something simple and it's not a kernel 
bug. 

Re: [gentoo-user] Hard drive noise

[wabenbau]

Ian Bloss  wrote:

> I've had more Seagates die over time than any other brand, I would
> recommend getting your money back asap and finding another brand.
> 
> I work IT at a school and we no longer purchase seagate drives for
> their failure rate.

A friend of mine is using Seagate ES drives since many years in his 
servers. He replaces all his drives after the five years warranty time
is up and as far as I can remember he told me, that he never had a 
failure with all of his drives. He gave me two of his old drives and 
I used them for some years in a RAID-1 array in one of my machines 
till I replaced them with SSDs recently. They are still ok. The only 
bad  thing about these drives is their high noise level. Server drives
are usually located in a server room and not in an office and so they 
are not designed to be silent. :-)

--
Regards
wabe

Re: [gentoo-user] Hard drive noise

[wabenbau]

Dale  wrote:

> I think I'm leery of all drives now.  I've had WDs fail, Seagate and
> some other brand.  I just keep buying bad stuff.  :-(   I'm glad I
> don't have to buy pacemakers.   :/ 

It seems that many many years ago HDs were more reliable then today. 
I have five 4GB IBM SCSI HDs and one 40GB Seagate IDE HD in my cupboard 
that I've used 24/7 for about 8 years. They were still intact when I 
replaced  them.
But its hardly surprising that a drive with a capacity of some TB has 
a higher risk of failure than a drive with a capacity of 4GB or 40GB.

Since about three years I'm using four 3TB WD red HDs as storage drives 
and I bought two more some months ago. No failures with all of these 
drives so far.

--
Regards
wabe

[gentoo-user] Re: systemd, libgudev and bug 552036

[Jonathan Callen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 12/18/2015 07:43 PM, Adam Carter wrote:
> emerge -1avt systemd
> 
> These are the packages that would be merged, in reverse order:
> 
> Calculating dependencies... done! [ebuild   R]
> sys-apps/systemd-218-r5:0/2::gentoo  USE="acl gudev introspection
> kmod lz4 pam policykit python seccomp ssl (-apparmor) -audit 
> -cryptsetup -curl -doc -elfutils -gcrypt -http -idn -kdbus -lzma
> -qrcode (-selinux) -sysv-utils -terminal {-test} -vanilla -xkb"
> ABI_X86="(64) -32 (-x32)" PYTHON_SINGLE_TARGET="python2_7
> -python3_3 -python3_4" PYTHON_TARGETS="python2_7 python3_4
> -python3_3" 0 KiB
> 
> Total: 1 package (1 reinstall), Size of downloads: 0 KiB
> 
> WARNING: One or more updates/rebuilds have been skipped due to a
> dependency conflict:
> 
> sys-apps/systemd:0
> 
> (sys-apps/systemd-226-r2:0/2::gentoo, ebuild scheduled for merge) 
> conflicts with
>> =sys-apps/systemd-212-r5:0/2[abi_x86_64(-),gudev(-),introspection(-)]
>
>> 
required by (virtual/libgudev-215-r3:0/0::gentoo, installed)
> 
> 
> sys-apps/systemd[python(-),python_targets_python2_7(-),python_single_t
arget_python2_7(+),python_targets_python3_4(-)]
>
> 
required by (net-analyzer/fail2ban-0.9.2:0/0::gentoo, installed)
> 
> 
> 
> 
> Would you like to merge these packages? [Yes/No]
> 

There are a couple of issues here, which appear to be caused by some
mismatched keywords in the tree. Your issue is that
net-analyzer/fail2ban[python] requires either sys-apps/systemd[python]
or dev-python/python-systemd. The python USE flag has been removed
from newer stable versions of sys-apps/systemd (in favor of
dev-python/python-systemd), but dev-python/python-systemd is not yet
stable. Therefore, portage is keeping the older version of systemd
installed, as that is the only way it could find to keep all deps
satisfied. If you want to keep fail2ban, the easiest method may be to
keyword dev-python/python-systemd-230 locally, and file a bug
requesting its stabilization.

- -- 
Jonathan Callen
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCgAGBQJWdNRQAAoJEEIQbvYRB3mgy4MP/0iX59YRMQgC0su8YwLeCiBF
vbypMwDxhmJ3ZYYLcAcUzY2oGleiRZyShtyym8JB5MdG8z5G5qMkwTdaVByqOFa0
muC6qHL4nNNumNA5h2kqZoswCqLPqYclDj3P++oFlaDM0SiDzU5VrEz6CXTKn6bB
/FjmwuRq1SWAGH+ecloypOEZsy4UFaVM66MvydN+XRTS3R7ybhB+dHFUcsGjokTJ
GP9BsmxBanOgV79r90XwK4/+Zt/b6r4JvN7xuT81MOHTzeParD9fjmMVl68AX7YB
k1roVJPJLTQHnwurzwjjxAz6/8BwgzofADIw/FKqcuiIdRWc8KxgvsVl7ykdNuF4
kW1T2EMoCHbi5iQABTPzZsobrtolHhqZ0qn4mCw4VOuQ8zTgFUkg1rUUOmDurxrD
n3OEphcZRoTs4NJRicJs5omxWIFHpH571X3xI3MOM9W5n4mqTw6yYAlVWV730zU+
wIMl60SMHRnidJO7uCG/8JkAulw4/lkC6jWWFcY5HM2sXzy7W7hrKDZqPMMZ7WjA
gNd4hnUpUvJZsDe+hfAgehz3zh3pq0/GdI/sR9VUYC04NZESdS+LVe17V/RTVjJb
e0vpyR4HbwmrArVx1/m7DZuK19cdmOAT54aCV0LEbE+PK+4nflXwVjFpJiw5zdXV
+rUd4D8a3sY/eTe9cCnJ
=LYWj
-END PGP SIGNATURE-

Re: [gentoo-user] Hard drive noise

[Rich Freeman]

On Fri, Dec 18, 2015 at 7:49 PM, Dale  wrote:
>
> I also found this after the reply from Ian.
>
> https://www.backblaze.com/blog/3tb-hard-drive-failure/
>
> No wonder they had it on sale.  Heck, why didn't they just say it was a
> good door stop instead of a hard drive???
>

Yeah, the only reason I'd want to use that model drive is if I had a
raid5 composed of entirely different drives and for some reason the
discount on the Seagate 3TB drive let me bump it up to a raid6 (and to
be sure I'd never put more than one of those in an array).  It is
basically a doorstop.

I had two of those go in the span of a year.  One was replaced under
warranty.  The next was the warranty replacement.  That one was no
longer under warranty, but after a scathing Amazon review Seagate
actually commented on the review asking me to contact them about a
replacement.  I didn't bother - I really was tired of swapping out
drives at that pace and didn't consider the considerably-higher risk
of a double failure worth it.

i'd have to check - I think I picked a 4TB Seagate NAS drive to replace it.

Somebody suggested not buying Seagate.  The thing is, EVERY
manufacturer has had drives like these.  Well, the Hitachi drives
Backblaze goes on about would be an exception, but they're
SIGNIFICANTLY more expensive and I don't think it is worth the premium
in a RAID.  For a single-drive system I'd strongly consider them.  I
think I heard they were bought out at some point, so we'll see if
their reputation holds.

And that's the thing with brand reputations.  These days MBAs milk
reputations.  Some finance guy realizes that people will buy this
year's drives based on last year's reputation and cuts some corners
and collects a huge bonus.  Three years later everybody is dealing
with drive failures.  Every vendor does it.  That one Seagate model
was about the worst I've personally seen, but who knows what model is
being sold today that in three years will turn out to be just as bad,
and it could come from any of the vendors.

I do try to look at the Backblaze stats for what they're worth, but I
think the general advice applies well.  Make sure you have an
appropriate level of redundancy and backup strategy.  Make sure to mix
models of drives in your RAIDs.  The whole point of a RAID is to keep
the price down by increasing your tolerance of failures.

And the whole NAS drive firmware thing really bugs me because they
charge a premium for a few bits in flash memory that should be
user-configurable anyway.  Some of those drives have better vibration
resistance, which bugs me less.  However, the bottom line is that they
probably will improve your RAID performance in the event of a failure,
and they probably do tend to cut the corners less on them.  But who
knows, maybe the drive that fails next year will be the super-premium
edition.

All of this goes to one of my drivers for using btrfs (and in this
regard zfs will do just as well).  The checksumming means that I'm not
really trusting the drive or its firmware at all, and I scrub my
arrays weekly.

Sorry you ended up with a bad drive...  That model IS considerably
cheaper than most of the others...

-- 
Rich

Re: [gentoo-user] Hard drive noise

[Ian Bloss]

When I get a chance next time I'm at work I'll attach a link to the piles
of dead seagates I've been collecting for target practice.

On Fri, Dec 18, 2015, 22:09   wrote:

> Ian Bloss  wrote:
>
> > I've had more Seagates die over time than any other brand, I would
> > recommend getting your money back asap and finding another brand.
> >
> > I work IT at a school and we no longer purchase seagate drives for
> > their failure rate.
>
> A friend of mine is using Seagate ES drives since many years in his
> servers. He replaces all his drives after the five years warranty time
> is up and as far as I can remember he told me, that he never had a
> failure with all of his drives. He gave me two of his old drives and
> I used them for some years in a RAID-1 array in one of my machines
> till I replaced them with SSDs recently. They are still ok. The only
> bad  thing about these drives is their high noise level. Server drives
> are usually located in a server room and not in an office and so they
> are not designed to be silent. :-)
>
> --
> Regards
> wabe
>
>

Re: [gentoo-user] Hard drive noise

[John Runyon]

> The thing is, EVERY
manufacturer has had drives like these.  Well, the Hitachi drives
Backblaze goes on about would be an exception

you've clearly never heard of DeathStars if you think Hitachi is an exception...

-John
Sent from my phone

Rich Freeman  wrote:

>On Fri, Dec 18, 2015 at 7:49 PM, Dale  wrote:
>>
>> I also found this after the reply from Ian.
>>
>> https://www.backblaze.com/blog/3tb-hard-drive-failure/
>>
>> No wonder they had it on sale.  Heck, why didn't they just say it was a
>> good door stop instead of a hard drive???
>>
>
>Yeah, the only reason I'd want to use that model drive is if I had a
>raid5 composed of entirely different drives and for some reason the
>discount on the Seagate 3TB drive let me bump it up to a raid6 (and to
>be sure I'd never put more than one of those in an array).  It is
>basically a doorstop.
>
>I had two of those go in the span of a year.  One was replaced under
>warranty.  The next was the warranty replacement.  That one was no
>longer under warranty, but after a scathing Amazon review Seagate
>actually commented on the review asking me to contact them about a
>replacement.  I didn't bother - I really was tired of swapping out
>drives at that pace and didn't consider the considerably-higher risk
>of a double failure worth it.
>
>i'd have to check - I think I picked a 4TB Seagate NAS drive to replace it.
>
>Somebody suggested not buying Seagate.  The thing is, EVERY
>manufacturer has had drives like these.  Well, the Hitachi drives
>Backblaze goes on about would be an exception, but they're
>SIGNIFICANTLY more expensive and I don't think it is worth the premium
>in a RAID.  For a single-drive system I'd strongly consider them.  I
>think I heard they were bought out at some point, so we'll see if
>their reputation holds.
>
>And that's the thing with brand reputations.  These days MBAs milk
>reputations.  Some finance guy realizes that people will buy this
>year's drives based on last year's reputation and cuts some corners
>and collects a huge bonus.  Three years later everybody is dealing
>with drive failures.  Every vendor does it.  That one Seagate model
>was about the worst I've personally seen, but who knows what model is
>being sold today that in three years will turn out to be just as bad,
>and it could come from any of the vendors.
>
>I do try to look at the Backblaze stats for what they're worth, but I
>think the general advice applies well.  Make sure you have an
>appropriate level of redundancy and backup strategy.  Make sure to mix
>models of drives in your RAIDs.  The whole point of a RAID is to keep
>the price down by increasing your tolerance of failures.
>
>And the whole NAS drive firmware thing really bugs me because they
>charge a premium for a few bits in flash memory that should be
>user-configurable anyway.  Some of those drives have better vibration
>resistance, which bugs me less.  However, the bottom line is that they
>probably will improve your RAID performance in the event of a failure,
>and they probably do tend to cut the corners less on them.  But who
>knows, maybe the drive that fails next year will be the super-premium
>edition.
>
>All of this goes to one of my drivers for using btrfs (and in this
>regard zfs will do just as well).  The checksumming means that I'm not
>really trusting the drive or its firmware at all, and I scrub my
>arrays weekly.
>
>Sorry you ended up with a bad drive...  That model IS considerably
>cheaper than most of the others...
>
>-- 
>Rich
>

Re: [gentoo-user] anyone tried amdgpu (kernel module)

[Alexander Kapshuk]

On Fri, Dec 18, 2015 at 11:07 PM, Tsukasa Mcp_Reznor  wrote:

> I have a Bonaire gpu, which has legacy support using the amdgpu kernel
> module.  I currently use the Radeon dri module with radeonsi mesa drivers
> and am quite happy.  But gentoo being gentoo I thought I'd give the amdgpu
> a go for the fun of it.
>
> Tried a few variations and keep coming up with a black screen on boot and
> it's hard locked.  I'm using the same Firmware includes that the radeon
> driver requires, and from reading it looks like that's fine with amdgpu, so
> I'm not sure what else could be the issue.
>
> Has anyone here tried and had success with it?  I've tried Kernels 4.2
> 4.2.4 4.3 and 4.3.2.  So I believe I'm missing something simple and it's
> not a kernel bug.
>

Did you consult the wiki article shown below when configuring your system
to use admgpu?

https://wiki.gentoo.org/wiki/Amdgpu

Re: [gentoo-user] Hard drive noise

[covici]

Rich Freeman  wrote:

> On Fri, Dec 18, 2015 at 7:49 PM, Dale  wrote:
> >
> > I also found this after the reply from Ian.
> >
> > https://www.backblaze.com/blog/3tb-hard-drive-failure/
> >
> > No wonder they had it on sale.  Heck, why didn't they just say it was a
> > good door stop instead of a hard drive???
> >
> 
> Yeah, the only reason I'd want to use that model drive is if I had a
> raid5 composed of entirely different drives and for some reason the
> discount on the Seagate 3TB drive let me bump it up to a raid6 (and to
> be sure I'd never put more than one of those in an array).  It is
> basically a doorstop.
> 
> I had two of those go in the span of a year.  One was replaced under
> warranty.  The next was the warranty replacement.  That one was no
> longer under warranty, but after a scathing Amazon review Seagate
> actually commented on the review asking me to contact them about a
> replacement.  I didn't bother - I really was tired of swapping out
> drives at that pace and didn't consider the considerably-higher risk
> of a double failure worth it.
> 
> i'd have to check - I think I picked a 4TB Seagate NAS drive to replace it.
> 
> Somebody suggested not buying Seagate.  The thing is, EVERY
> manufacturer has had drives like these.  Well, the Hitachi drives
> Backblaze goes on about would be an exception, but they're
> SIGNIFICANTLY more expensive and I don't think it is worth the premium
> in a RAID.  For a single-drive system I'd strongly consider them.  I
> think I heard they were bought out at some point, so we'll see if
> their reputation holds.
> 
> And that's the thing with brand reputations.  These days MBAs milk
> reputations.  Some finance guy realizes that people will buy this
> year's drives based on last year's reputation and cuts some corners
> and collects a huge bonus.  Three years later everybody is dealing
> with drive failures.  Every vendor does it.  That one Seagate model
> was about the worst I've personally seen, but who knows what model is
> being sold today that in three years will turn out to be just as bad,
> and it could come from any of the vendors.
> 
> I do try to look at the Backblaze stats for what they're worth, but I
> think the general advice applies well.  Make sure you have an
> appropriate level of redundancy and backup strategy.  Make sure to mix
> models of drives in your RAIDs.  The whole point of a RAID is to keep
> the price down by increasing your tolerance of failures.
> 
> And the whole NAS drive firmware thing really bugs me because they
> charge a premium for a few bits in flash memory that should be
> user-configurable anyway.  Some of those drives have better vibration
> resistance, which bugs me less.  However, the bottom line is that they
> probably will improve your RAID performance in the event of a failure,
> and they probably do tend to cut the corners less on them.  But who
> knows, maybe the drive that fails next year will be the super-premium
> edition.
> 
> All of this goes to one of my drivers for using btrfs (and in this
> regard zfs will do just as well).  The checksumming means that I'm not
> really trusting the drive or its firmware at all, and I scrub my
> arrays weekly.
> 
> Sorry you ended up with a bad drive...  That model IS considerably
> cheaper than most of the others...

I was never able to get either zfs or btrfs to work correctly, zfs was
very vulnerable -- I forgot to export a zfs on a usb drive and got an
enless loop of processes untill I rebooted.  Btrfs never did work for
me, I created a pool,  copied my root file system, usr and var into
ssubvolumes, and copied my files, but when I would boot into it,
everything was messed up, processes thought files were missing, very
strange.  So, how did you set up either one of those -- I would love to
use it because I have ssds and I don't want to rely on their firmware
either.


-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

 John Covici
 cov...@ccs.covici.com