Re: [gentoo-user] emerge --depclean does not remove due to link level dependencies
2009/11/4 Alex Schuster : > Hi there! > > Again, this is just something I am curious about, not a real problem. > emerge -p --depclean gives me this output: > > [...] > Calculating dependencies... done! >>>> Checking for lib consumers... >>>> Assigning files to packages... > * In order to avoid breakage of link level dependencies, one or more > * packages will not be removed. This can be solved by rebuilding the > * packages that pulled them in. > * > * dev-libs/elfutils-0.131-r2 pulled in by: > * dev-util/ddd-3.3.12-r1 needs libelf.so.1 Newer versions of portage print this message if a package is about to be removed because there is no ebuild dependency from all other installed packages, but it is still needed because other packages link to it automagically. This seems to be the case here, ddd automagically links to elfutils depending on whether it is available or not, instead of being controlled by the ebuild via use flag. So ddd links against elfutils and portage does not know about it. In this case the suggestion of rebuilding the packages does not work. With older portage versions elfutils is removed and the dependency is ignored. Revdep-rebuild will complain about ddd linking against elfutils which is not available anymore and then rebuild ddd which will result in ddd not linking against elfutils anymore. > [...] > And some more of that involving media-libs/libcddb-1.3.2, media- > sound/esound-0.2.41, sys-libs/db-4.5.20_p2-r1 and sys-libs/db-4.6.21_p4. > > Okay, ddd needs libelf.so.1, provided by elfutils. Still the same when I > rebuild ddd. So, why does this output appear at all? ddd needs > libelf.so.1, this is in elfutils, so of course elfutils is needed just > like any other package. > > Oh, wait I think I got it. emerge -pe ddd dos NOT list elfutils. So is > this a bug in the ddd ebuild, not having elfutils as a dependency? And the > same would be true for the other packages? Should I file some bugs? > > H. Now I got it. ddd does indeed not need elfutils. But it uses it > when it is available. After removing elfutils, ddd still builds. Starting > the ddd configure script in by hand with the --help option does not show > options like --without-elf, so it's not the ebuild's fault that ddd makes > use of the libelf library when it is available. > [snip] > Should some bugs be filed? And if so, should they go: > - To the ebuild maintainers? But they probably cannot do much about it, > apart from patching the package's autoconf stuff. > - To upstream? Well, would they consider this this a bug at all, or a mere > problem with Gentoo's special build system, that wants to know all the > dependencies? If ddd really links automagically against elfutils, you should file a Gentoo bug about ddd which needs it's autotools fixed. To save the Gentoo developers some time you can also file an upstream bug and add a reference to it in the Gentoo bug report. If upstream cares about automagic dependencies is another story, in Gentoo it is considered a bug. -- Daniel Pielmeier
[gentoo-user] emerge --depclean does not remove due to link level dependencies
Hi there! Again, this is just something I am curious about, not a real problem. emerge -p --depclean gives me this output: [...] Calculating dependencies... done! >>> Checking for lib consumers... >>> Assigning files to packages... * In order to avoid breakage of link level dependencies, one or more * packages will not be removed. This can be solved by rebuilding the * packages that pulled them in. * * dev-libs/elfutils-0.131-r2 pulled in by: * dev-util/ddd-3.3.12-r1 needs libelf.so.1 [...] And some more of that involving media-libs/libcddb-1.3.2, media- sound/esound-0.2.41, sys-libs/db-4.5.20_p2-r1 and sys-libs/db-4.6.21_p4. Okay, ddd needs libelf.so.1, provided by elfutils. Still the same when I rebuild ddd. So, why does this output appear at all? ddd needs libelf.so.1, this is in elfutils, so of course elfutils is needed just like any other package. Oh, wait I think I got it. emerge -pe ddd dos NOT list elfutils. So is this a bug in the ddd ebuild, not having elfutils as a dependency? And the same would be true for the other packages? Should I file some bugs? Hmmmm. Now I got it. ddd does indeed not need elfutils. But it uses it when it is available. After removing elfutils, ddd still builds. Starting the ddd configure script in by hand with the --help option does not show options like --without-elf, so it's not the ebuild's fault that ddd makes use of the libelf library when it is available. Still, this is ugly I think. Another part of the emerge --depclean output is: * media-sound/esound-0.2.41 pulled in by: * app-office/gnucash-2.2.9-r1 needs libesd.so.0 * gnome-extra/gnome-media-2.26.0-r1 needs libesd.so.0 * gnome-extra/nautilus-cd-burner-2.24.0 needs libesd.so.0 * gnome-extra/yelp-2.26.0 needs libesd.so.0 * media-libs/smpeg-0.4.4-r9 needs libesd.so.0 * media-sound/amarok-1.4.10_p20090130-r3 needs libesd.so.0 * media-sound/rhythmbox-0.11.6-r1 needs libesd.so.0 * media-sound/synaesthesia-2.4 needs libesd.so.0 * media-video/transcode-1.0.7 needs libesd.so.0 I do not have esd in my USE flags. Looks like all those packages use it anyway when it is available. Should some bugs be filed? And if so, should they go: - To the ebuild maintainers? But they probably cannot do much about it, apart from patching the package's autoconf stuff. - To upstream? Well, would they consider this this a bug at all, or a mere problem with Gentoo's special build system, that wants to know all the dependencies? - To the doc team? Suggesting that the emerge --depclean output should change from: * In order to avoid breakage of link level dependencies, one or more * packages will not be removed. This can be solved by rebuilding the * packages that pulled them in. to something like: * In order to avoid breakage of link level dependencies, one or more * packages will not be removed. If you like them to be removed, do so * manually, and run revdep-rebuild afterwards to rebuild the packages * without the libraries. We are sorry, this is an upstream problem with * bad configure files and we cannot do much about it. Use quickpkg * before removing the packages, so if anything breaks you can get them * back quickly. Good luck. Wonko
[gentoo-user] ddd not working right
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, today I recompiled my ddd and now I'm getting this messages a lot [tcsetpgrp failed in terminal_inferior: Inappropriate ioctl for device] the only important thing that I have change in my system since last time I builded ddd is that I now have glibc with nptl and nptl-only flags set up. That's the reason why I'm getting that messages? What could I do? BTW, I recompiled gdb later and no changes - -- Rodrigo Lazo (rlazo) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDPv0AcSM2/etFWtgRAh61AJ4oVSbGE8oJM0dhURS8CR2BV8KAugCaAyOe A44Qe1hAcMHi3l4Xr8qAmOc= =cwZc -END PGP SIGNATURE- -- gentoo-user@gentoo.org mailing list
[gentoo-user] Re: which package contains latex stmaryrd.sty
Willie Wong: >On Fri, Apr 10, 2009 at 05:49:27PM +0200, Penguin Lover Hartmut Figge squawked: >> Why should i have searched for this migration guide, when texlive was >> pulled in automatically yesterday and i had never noticed something of >> tetex in my system? But there exists emerge.log. Looking for tetex i found 1188510596: Started emerge on: Aug 30, 2007 23:49:56 1188510596: *** emerge a2ps [...] 1188510887: >>> emerge (5 of 6) app-text/tetex-3.0_p1-r3 to / So there was indeed tetex installed pulled in by a2ps. And this emerge.log is a fine thing. It reminded me on previous trouble with texlive not long ago. 1238911367: Started emerge on: Apr 05, 2009 08:02:47 1238911367: *** emerge --newuse --deep --update world [...] 1238915281: >>> emerge (16 of 20) dev-texlive/texlive-basic-2008 to / [...] 1238915289: *** exiting unsuccessfully with status '1'. 1238915293: *** terminating. I was not very happy about this and had to do something. emerge.log shows what had happened. 1238916325: *** emerge unmerge tetex :) Didn't help, though. Then somehow i noticed that unmerging ddd could be useful. And so it was. 1238916481: Started emerge on: Apr 05, 2009 09:28:01 1238916481: *** emerge unmerge ddd 1238916487: === Unmerging... (dev-util/ddd-3.3.11) 1238916487: >>> unmerge success: dev-util/ddd-3.3.11 1238916487: *** exiting successfully. 1238916490: *** terminating. 1238916494: Started emerge on: Apr 05, 2009 09:28:14 1238916494: *** emerge --newuse --deep --update world 1238916499: *** Finished. Cleaning up... 1238916499: *** exiting successfully. 1238916499: *** terminating. 'emerge -uDN world' had finished successfully. A following new emerge of ddd also. Fine. Until yesterday. *g* >No, you shouldn't have. But I am confused about the file collision >message, especially since you didn't show the exact list of files that >collided! No problem because summary.log exists. >>> Messages generated by process 32095 on 2009-04-09 23:04:40 CEST for package dev-texlive/texlive-basic-2008: [...] Detected file collision(s): /var/lib/texmf/web2c/tex/tex.fmt /var/lib/texmf/web2c/tex/tex.log /var/lib/texmf/web2c/metafont/mf.base /var/lib/texmf/web2c/metafont/mf.log >>> Messages generated by process 32095 on 2009-04-09 23:07:02 CEST for package dev-texlive/texlive-latex-2008-r1: [...] Detected file collision(s): /usr/bin/pdflatex /usr/bin/latex By the way, thanks for the link to http://www.gentoo.org/proj/en/tex/texlive-migration-guide.xml which is now in my bookmarks. Should i have trouble with texlive in the future i know what to do. Hartmut
[gentoo-user] failure on booting Gentoo Linux 2007 amd64 Live CD
Dear Sirs After I had downloaded and burned on K3B the forementioned CD I don't get it booted on my machine amd64 +3000. I've already its manual and doc, I upgraded my K8VXSE motherboard BIOS...nothing! I don't know what else to do... ___ Para fazer uma ligação DDD pra perto ou pra longe, faz um 21. A Embratel tem tarifas muito baratas esperando por você. Aproveite! -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] SSHd: Permission denied (publickey,keyboard-interactive).
Michael Sullivan wrote: I hooked up my old server box today so that I could update the software, only to find that I could not ssh over to it: [EMAIL PROTECTED] ~ $ ssh bullet Permission denied (publickey,keyboard-interactive). There were no 'official' logs, but a website I found on google suggested running /usr/sbin/sshd -ddd -p 2202 and then trying to shell over with ssh -p 2202 Here's the output. I piped it to a file: [snip] I tried upgrading PAM and rebooting, but it didn't solve the problem. I'm running pam-1.0.1, if that matters... what problem? you haven't actually said what is / isn't working! What's the output from the client when you try and ssh in with the command "ssh -p 2202 "? -- Iain Buchanan Don't go easy on each other just because you're brother and sister. I want to see you both fighting for your parents' love. -- Homer Simpson Lisa on Ice
Re: [gentoo-user] SSHd: Permission denied (publickey,keyboard-interactive).
On Fri, 2008-09-12 at 15:27 +0930, Iain Buchanan wrote: > Michael Sullivan wrote: > > I hooked up my old server box today so that I could update the software, > > only to find that I could not ssh over to it: > > > > [EMAIL PROTECTED] ~ $ ssh bullet > > Permission denied (publickey,keyboard-interactive). > > > > There were no 'official' logs, but a website I found on google suggested > > running > > > > /usr/sbin/sshd -ddd -p 2202 > > > > and then trying to shell over with > > > > ssh -p 2202 > > > > Here's the output. I piped it to a file: > > [snip] > > > I tried upgrading PAM and rebooting, but it didn't solve the problem. > > I'm running pam-1.0.1, if that matters... > > what problem? you haven't actually said what is / isn't working! What's > the output from the client when you try and ssh in with the command "ssh > -p 2202 "? > I thought I was pretty clear on that, but here it is again: [EMAIL PROTECTED] ~ $ ssh -p 2202 bullet Permission denied (publickey,keyboard-interactive). As you can see, I'm still locked out.
Re: [gentoo-user] [~amd64] Confusing behavior from gdb
On Saturday, April 25, 2015 7:42:30 PM cov...@ccs.covici.com wrote:
> > (gdb) list mount.c:123
> > 118 else
> > 119 fputc(*p, stdout);
> > 120 }
> > 121 }
> > 122
> > 123 static void print_all(struct libmnt_context *cxt, char *pattern, int
show_label)
> > 124 {
> > 125 struct libmnt_table *tb;
> > 126 struct libmnt_iter *itr = NULL;
> > 127 struct libmnt_fs *fs;
> > (gdb)
> >
> >
> > This seems to me to be very buggy behavior, but I'd like to get opinions
from
> > people who really know gdb, which I don't.
>
> I think it wants to put you on the first real statement of the function.
>
Yes. Also, if you compiled with any optimizations compile again with none.
That way the compiler will try to generate code that matches the order of your
C statements. It doesn't guarantees that this won't happen but with
optimizations if you try to step through the source it'll definitely be jumping
back and forth. The first statement here is line 126 but it may be optimized
away or out of order. Also for source code debugging it'll be much easier to
use a graphical frontend (ddd,kdbg,kdevelop,etc).
--
Fernando Rodriguez
Re: [gentoo-user] Re: failure on booting Gentoo Linux 2007 amd64 Live CD
Citando Dan Farrell <[EMAIL PROTECTED]>: > On Mon, 3 Sep 2007 00:41:43 + (UTC) > James <[EMAIL PROTECTED]> wrote: > > > LUIZ AFONSO BELLO DE CAMPOS click21.com.br> writes: > > > > > > > > > > >Dear Sirs > > > > > > After I had downloaded and burned on K3B the forementioned > > > CD I don't get it booted on my machine amd64 +3000. I've already > > > its manual and doc, I upgraded my K8VXSE motherboard > > > BIOS...nothing! I don't know what else to do... > > > > > > try to boot the system on knoppix or another (linux) boot cd... > > and if you have problems booting all linux cds, try adding 'noapic > noacpi' to the kernel boot parameters. > > -- Dan > -- > [EMAIL PROTECTED] mailing list > > >> I found out K3B is not fully qualified to write bootable CDs on FreeBSD-6.1-R amd64, that's my case. Xcdroast is far better. The matter is that I burned such program by using 32bit Slackware Linux. So it's not on FreeBSD amd64 but on Linux32bit K3B fails as well. >> Regards ___ Para fazer uma ligação DDD pra perto ou pra longe, faz um 21. A Embratel tem tarifas muito baratas esperando por você. Aproveite! -- [EMAIL PROTECTED] mailing list
[gentoo-user] high priority task as user (nice/ionice)
Hi, with guvcview I capture video streams of some birds, which sometime arrive on the roof. When they do I press the record button of the guvcview application. The webcam I use is able to deliver 30fps at 640x320 pixel with audio via usb. Unfortunately while recording nothing else should use the CPU/the IO system heavily otherwise I will get an vi-vi-ddd-dd-deooo-o--o-o (stuttering performance). In this list I read about ionice and nice, which latter I know before. Form the manpages of both I read, that only root is allowed to give process higher priority than normal. I want to give guvcview high IO- and CPU-priority without the hassle to pickup PIDs and lunch nice/ionice by root-hand after the start of guvcview (user-process). And I am iusing icewm (no KDE/GNOME as desktop) Is there any chance to start guvcview with user rights AND to give the application higer priorities so that whatever guvcview wants from the system will be served as soon as possible to avoid stuttering videos? Thank you very much in advance for any help! Have a nice sunday! mcc -- Please don't send me any Word- or Powerpoint-Attachments unless it's absolutely neccessary. - Send simply Text. See http://www.gnu.org/philosophy/no-word-attachments.html In a world without fences and walls nobody needs gates and windows.
Re: [gentoo-user] SSHd: Permission denied (publickey,keyboard-interactive).
Michael Sullivan wrote: > On Fri, 2008-09-12 at 15:27 +0930, Iain Buchanan wrote: >> Michael Sullivan wrote: >>> I hooked up my old server box today so that I could update the software, >>> only to find that I could not ssh over to it: >>> >>> [EMAIL PROTECTED] ~ $ ssh bullet >>> Permission denied (publickey,keyboard-interactive). >>> >>> There were no 'official' logs, but a website I found on google suggested >>> running >>> >>> /usr/sbin/sshd -ddd -p 2202 >>> >>> and then trying to shell over with >>> >>> ssh -p 2202 >>> >>> Here's the output. I piped it to a file: >> [snip] >> >>> I tried upgrading PAM and rebooting, but it didn't solve the problem. >>> I'm running pam-1.0.1, if that matters... >> what problem? you haven't actually said what is / isn't working! What's >> the output from the client when you try and ssh in with the command "ssh >> -p 2202 "? >> > > I thought I was pretty clear on that, but here it is again: > > [EMAIL PROTECTED] ~ $ ssh -p 2202 bullet > Permission denied (publickey,keyboard-interactive). > > As you can see, I'm still locked out. > > try # ssh -p 2202 -vv bullet or #ssh -vv bullet as that will give you debug info from the client side of the connection. Is it safe to assume that you logged into it via the console to start SSHd on 2202? Also, does your user exist on the box? It sounds like 'no', especially when btmp is involved. -- Eric Martin Key fingerprint = D1C4 086E DBB5 C18E 6FDA B215 6A25 7174 A941 3B9F signature.asc Description: OpenPGP digital signature
Re: SPAM: Re: [gentoo-user] failure on booting Gentoo Linux 2007 amd64 Live CD
Citando Alan McKinnon <[EMAIL PROTECTED]>: > On Monday 03 September 2007, LUIZ AFONSO BELLO DE CAMPOS wrote: > >Dear Sirs > > > > > > After I had downloaded and burned on K3B the forementioned CD > > I don't get it booted on my machine amd64 +3000. I've already its > > manual and doc, I upgraded my K8VXSE motherboard BIOS...nothing! I > > don't know what else to do... > > How did you burn the CD using K3B? As a data project, or as a disk > image? > > A quick check is to pop the CD into a machine that works, mount the CD > and see what's on it. If you see one file called .iso, then > you burned it wrong and need to burn another one as a full disk image. > > If that check is OK, then make sure that the .iso you downloaded is not > corrupt by checking it's MD5 sum by following the instructions on the > downlaod site. > > Next time you ask for help on a mailing list, it's a good idea to > describe exactly what problem you are having. You didn't say, so we > donlt know, and I just guessed at what is the most common problem. > > So, does the CD boot at all? What's on the screen? If it boots and tries > to run, where does it stop and what error messages do you get when it > does? > > alan > > > Thanks, Alan. I will try cdrecord command line. > > > -- > Optimists say the glass is half full, > Pessimists say the glass is half empty, > Developers say wtf is the glass twice as big as it needs to be? > > Alan McKinnon > alan at linuxholdings dot co dot za > +27 82, double three seven, one nine three five > -- > [EMAIL PROTECTED] mailing list > > ___ Para fazer uma ligação DDD pra perto ou pra longe, faz um 21. A Embratel tem tarifas muito baratas esperando por você. Aproveite! -- [EMAIL PROTECTED] mailing list
Re: SPAM: Re: [gentoo-user] failure on booting Gentoo Linux 2007 amd64 Live CD
Cara, tem que gravar como imagem, senão não boota. In english: You must record the CD in image mode to make a bootable CD. 2007/9/3, LUIZ AFONSO BELLO DE CAMPOS <[EMAIL PROTECTED]>: > > Citando Alan McKinnon <[EMAIL PROTECTED]>: > > > On Monday 03 September 2007, LUIZ AFONSO BELLO DE CAMPOS wrote: > > >Dear Sirs > > > > > > > > > After I had downloaded and burned on K3B the forementioned CD > > > I don't get it booted on my machine amd64 +3000. I've already its > > > manual and doc, I upgraded my K8VXSE motherboard BIOS...nothing! I > > > don't know what else to do... > > > > How did you burn the CD using K3B? As a data project, or as a disk > > image? > > > > A quick check is to pop the CD into a machine that works, mount the CD > > and see what's on it. If you see one file called .iso, then > > you burned it wrong and need to burn another one as a full disk image. > > > > If that check is OK, then make sure that the .iso you downloaded is not > > corrupt by checking it's MD5 sum by following the instructions on the > > downlaod site. > > > > Next time you ask for help on a mailing list, it's a good idea to > > describe exactly what problem you are having. You didn't say, so we > > donlt know, and I just guessed at what is the most common problem. > > > > So, does the CD boot at all? What's on the screen? If it boots and tries > > to run, where does it stop and what error messages do you get when it > > does? > > > > alan > > > > > Thanks, Alan. I will try cdrecord command line. > > > > > > -- > > Optimists say the glass is half full, > > Pessimists say the glass is half empty, > > Developers say wtf is the glass twice as big as it needs to be? > > > > Alan McKinnon > > alan at linuxholdings dot co dot za > > +27 82, double three seven, one nine three five > > -- > > [EMAIL PROTECTED] mailing list > > > > > > > > > ___ > Para fazer uma ligação DDD pra perto ou pra longe, faz um 21. A Embratel > tem > tarifas muito baratas esperando por você. Aproveite! > > -- > [EMAIL PROTECTED] mailing list > >
Re: [gentoo-user] Hard Drive Crash - Please Help
] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 868 occurred at disk power-on lifetime: 12653 hours (527 days + 5 hours) When the command that caused the error occurred, the device was active or idle. - Grant -- gentoo-user@gentoo.org mailing list
[gentoo-user] SSHd: Permission denied (publickey,keyboard-interactive).
I hooked up my old server box today so that I could update the software, only to find that I could not ssh over to it: [EMAIL PROTECTED] ~ $ ssh bullet Permission denied (publickey,keyboard-interactive). There were no 'official' logs, but a website I found on google suggested running /usr/sbin/sshd -ddd -p 2202 and then trying to shell over with ssh -p 2202 Here's the output. I piped it to a file: [EMAIL PROTECTED] ~ $ cat sshd.log debug2: load_server_config: filename /etc/ssh/sshd_config debug2: load_server_config: done config len = 237 debug2: parse_server_config: config /etc/ssh/sshd_config len 237 debug3: /etc/ssh/sshd_config:21 setting Protocol 2 debug3: /etc/ssh/sshd_config:60 setting PasswordAuthentication no debug3: /etc/ssh/sshd_config:87 setting UsePAM yes debug3: /etc/ssh/sshd_config:91 setting X11Forwarding yes debug3: /etc/ssh/sshd_config:127 setting Subsystem sftp/usr/lib/misc/sftp-server debug1: sshd version OpenSSH_4.7p1 debug3: Not a RSA1 key file /etc/ssh/ssh_host_rsa_key. debug1: read PEM private key done: type RSA debug1: private host key: #0 type 1 RSA debug3: Not a RSA1 key file /etc/ssh/ssh_host_dsa_key. debug1: read PEM private key done: type DSA debug1: private host key: #1 type 2 DSA debug1: rexec_argv[0]='/usr/sbin/sshd' debug1: rexec_argv[1]='-ddd' debug1: rexec_argv[2]='-p' debug1: rexec_argv[3]='2202' debug2: fd 3 setting O_NONBLOCK debug1: Bind to port 2202 on 0.0.0.0. Server listening on 0.0.0.0 port 2202. socket: Address family not supported by protocol debug3: fd 4 is not O_NONBLOCK debug1: Server will not fork when running in debugging mode. debug3: send_rexec_state: entering fd = 7 config len 237 debug3: ssh_msg_send: type 0 debug3: send_rexec_state: done debug1: rexec start in 4 out 4 newsock 4 pipe -1 sock 7 debug1: inetd sockets after dupping: 3, 3 Connection from 192.168.1.2 port 57643 debug1: Client protocol version 2.0; client software version OpenSSH_4.7 debug1: match: OpenSSH_4.7 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_4.7 debug2: fd 3 setting O_NONBLOCK debug3: privsep user:group 22:22 debug1: permanently_set_uid: 22/22 debug1: list_hostkey_types: ssh-rsa,ssh-dss debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,[EMAIL PROTECTED],aes128-ctr,aes192-ctr,aes256-ctr debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,[EMAIL PROTECTED],aes128-ctr,aes192-ctr,aes256-ctr debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,[EMAIL PROTECTED],hmac-ripemd160,[EMAIL PROTECTED],hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,[EMAIL PROTECTED],hmac-ripemd160,[EMAIL PROTECTED],hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,[EMAIL PROTECTED] debug2: kex_parse_kexinit: none,[EMAIL PROTECTED] debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,[EMAIL PROTECTED],aes128-ctr,aes192-ctr,aes256-ctr debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,[EMAIL PROTECTED],aes128-ctr,aes192-ctr,aes256-ctr debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,[EMAIL PROTECTED],hmac-ripemd160,[EMAIL PROTECTED],hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,[EMAIL PROTECTED],hmac-ripemd160,[EMAIL PROTECTED],hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: [EMAIL PROTECTED],zlib,none debug2: kex_parse_kexinit: [EMAIL PROTECTED],zlib,none debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: mac_setup: found hmac-md5 debug1: kex: client->server aes128-cbc hmac-md5 [EMAIL PROTECTED] debug2: mac_setup: found hmac-md5 debug1: kex: server->client aes128-cbc hmac-md5 [EMAIL PROTECTED] debug1: SSH2_MSG_KEX_DH_GEX_REQUEST received debug3: mm_request_send entering: type 0 debug3: mm_choose_dh: waiting for MONITOR_ANS_MODULI debug3: mm_request_receive_expect entering: type 1 debug3: mm_request_receive entering debug2: Network child is on pid 8390 debug3: preauth child monitor started debug3: mm_request_receive entering debug3: m
[gentoo-user] hotplug permissions xsane
Hello all,
My scanner was working OK till I did a 'emerge -uDv world'. xsane now
picks up my logitech webcam instead of my scanner and does not see my
scanner.
In root xsane sees both devices, asks me which one to use and all is OK,
so its a permissions problem.
vanda_comp dave # lsusb
Bus 002 Device 001: ID :
Bus 001 Device 006: ID 046d:08b2 Logitech, Inc. QuickCam Pro 4000
Bus 001 Device 005: ID 055f:0008 Mustek Systems, Inc. ScanExpress 1200
CU Plus
Bus 001 Device 004: ID 056a:0011 Wacom Co., Ltd Graphire 2
Bus 001 Device 003: ID 04b8:0005 Seiko Epson Corp. Stylus Printer
Bus 001 Device 002: ID 0409:0050 NEC Corp.
Bus 001 Device 001: ID :
vanda_comp dave #
[EMAIL PROTECTED] /proc/bus/usb/001 $ ls -al
total 0
dr-xr-xr-x 2 root root 0 Jul 17 13:15 .
drwxr-xr-x 4 root root 0 Jul 17 13:15 ..
-rw-r--r-- 1 root root 43 Jul 17 13:15 001
-rw-r--r-- 1 root root 43 Jul 17 13:15 002
-rw-r--r-- 1 root root 50 Jul 17 13:15 003
-rw-r--r-- 1 root root 52 Jul 17 13:15 004
-rw-r--r-- 1 root root 57 Jul 17 13:15 005
-rw-r--r-- 1 root root 508 Jul 17 13:15 006
[EMAIL PROTECTED] /proc/bus/usb/001 $
Looking in hotplug I have stripped down the usermap to just my scanners
entry to make sure it is seen - it matches 055f 0008.
[EMAIL PROTECTED] /etc/hotplug/usb $ cat libsane.usermap
# This file is part of sane-backends.
#
# The entries below are used to detect a USB scanner when it's plugged in
# and then run the libusbscanner script to change the ownership and
# permissions on the "device node" used by libusb.
#
.
#
#
# The following list already contains a lot of scanners. If your scanner
# isn't mentioned there, add it as explained above and mail the entry to
# the sane-devel mailing list.
#
# Hewlett-Packard|ScanJet 4100C
# Mustek Systems Inc.|ScanExpress 1200 CU Plus
libusbscanner 0x0003 0x055f 0x00080x
0x 0x00 0x000x00
0x000x00 0x00 0x
[EMAIL PROTECTED] /etc/hotplug/usb $
[EMAIL PROTECTED] /etc/hotplug/usb $ cat libusbscanner
#!/bin/sh
# This file is part of sane-backends.
#
# This script changes the permissions and ownership of a USB device under
# /proc/bus/usb to grant access to this device to users in the scanner
group.
#
# Ownership is set to root:scanner, permissions are set to 0660.
#
# Arguments :
# ---
# ACTION=[add|remove]
# DEVICE=/proc/bus/usb/BBB/DDD
# TYPE=usb
# latest hotplug doesn't set DEVICE on 2.6.x kernels
if [ -z "$DEVICE" ] ; then
IF=`echo $DEVPATH | sed 's/\(bus\/usb\/devices\/\)\(.*\)-\(.*\)/\2/'`
DEV=`echo $DEVPATH | sed 's/\(bus\/usb\/devices\/\)\(.*\)-\(.*\)/\3/'`
DEV=`expr $DEV + 1`
DEVICE=`printf '/proc/bus/usb/%.03d/%.03d' $IF $DEV`
fi
if [ -z "${DEVICE}" ] ; then
IF=$(echo ${DEVPATH} | sed
's:\(bus/usb/devices/\)\(.*\)-\(.*\):\2:')
if [ -r /sys/${DEVPATH}/devnum ]; then
DEV=$(cat /sys/${DEVPATH}/devnum)
else
DEV=1 # you'll have to adjust this manually for kernel < 2.6.6
fi
DEVICE=$(printf '/proc/bus/usb/%.03d/%.03d' ${IF} ${DEV})
fi
if [ "$ACTION" = "add" -a "$TYPE" = "usb" ]; then
chown root:scanner "$DEVICE"
chmod 0660 "$DEVICE"
fi
# That's an insecure but simple alternative
# Everyone has access to the scanner
# if [ "$ACTION" = "add" -a "$TYPE" = "usb" ]; then
# chmod 0666 "$DEVICE"
# fi
[EMAIL PROTECTED] /etc/hotplug/usb $
Should set my scanner to the scanner group but does not. If I unplug my
scanner & re-plug it in I get ...
vanda_comp dave # lsusb
Bus 002 Device 001: ID :
Bus 001 Device 007: ID 055f:0008 Mustek Systems, Inc. ScanExpress 1200
CU Plus
Bus 001 Device 006: ID 046d:08b2 Logitech, Inc. QuickCam Pro 4000
Bus 001 Device 004: ID 056a:0011 Wacom Co., Ltd Graphire 2
Bus 001 Device 003: ID 04b8:0005 Seiko Epson Corp. Stylus Printer
Bus 001 Device 002: ID 0409:0050 NEC Corp.
Bus 001 Device 001: ID :
vanda_comp dave #
[EMAIL PROTECTED] /proc/bus/usb/001 $ ls -al
total 0
dr-xr-xr-x 2 root root 0 Jul 17 13:15 .
drwxr-xr-x 4 root root 0 Jul 17 13:15 ..
-rw-r--r-- 1 root root 43 Jul 17 13:15 001
-rw-r--r-- 1 root root 43 Jul 17 13:15 002
-rw-r--r-- 1 root root 50 Jul 17 13:15 003
-rw-r--r-- 1 root root 52 Jul 17 13:15 004
-rw-r--r-- 1 root root508 Jul 17 13:15 006
-rw-rw 1 root scanner 57 Jul 17 13:55 007
[EMAIL PROTECTED] /proc/bus/usb/001 $
Everything works AOK and I can scan. However unplugging & plugging in
scanners every time the machine starts is a pain.
Hotplug is started on bootup ...
vanda_comp 001 # rc-update add hotplug default
* hotplug already installed in runlevel default; skippin
Re: [gentoo-user][SOLVED] hotplug permissions xsane
Dave S wrote:
>Hello all,
>
>My scanner was working OK till I did a 'emerge -uDv world'. xsane now
>picks up my logitech webcam instead of my scanner and does not see my
>scanner.
>
>In root xsane sees both devices, asks me which one to use and all is OK,
>so its a permissions problem.
>
>
>
>
>vanda_comp dave # lsusb
>Bus 002 Device 001: ID :
>Bus 001 Device 006: ID 046d:08b2 Logitech, Inc. QuickCam Pro 4000
>Bus 001 Device 005: ID 055f:0008 Mustek Systems, Inc. ScanExpress 1200
>CU Plus
>Bus 001 Device 004: ID 056a:0011 Wacom Co., Ltd Graphire 2
>Bus 001 Device 003: ID 04b8:0005 Seiko Epson Corp. Stylus Printer
>Bus 001 Device 002: ID 0409:0050 NEC Corp.
>Bus 001 Device 001: ID :
>vanda_comp dave #
>
>[EMAIL PROTECTED] /proc/bus/usb/001 $ ls -al
>total 0
>dr-xr-xr-x 2 root root 0 Jul 17 13:15 .
>drwxr-xr-x 4 root root 0 Jul 17 13:15 ..
>-rw-r--r-- 1 root root 43 Jul 17 13:15 001
>-rw-r--r-- 1 root root 43 Jul 17 13:15 002
>-rw-r--r-- 1 root root 50 Jul 17 13:15 003
>-rw-r--r-- 1 root root 52 Jul 17 13:15 004
>-rw-r--r-- 1 root root 57 Jul 17 13:15 005
>-rw-r--r-- 1 root root 508 Jul 17 13:15 006
>[EMAIL PROTECTED] /proc/bus/usb/001 $
>
>
>
>
>
>Looking in hotplug I have stripped down the usermap to just my scanners
>entry to make sure it is seen - it matches 055f 0008.
>
>
>
>
>
>[EMAIL PROTECTED] /etc/hotplug/usb $ cat libsane.usermap
># This file is part of sane-backends.
>#
># The entries below are used to detect a USB scanner when it's plugged in
># and then run the libusbscanner script to change the ownership and
># permissions on the "device node" used by libusb.
>#
>
>.
>
>#
>#
># The following list already contains a lot of scanners. If your scanner
># isn't mentioned there, add it as explained above and mail the entry to
># the sane-devel mailing list.
>#
># Hewlett-Packard|ScanJet 4100C
># Mustek Systems Inc.|ScanExpress 1200 CU Plus
>libusbscanner 0x0003 0x055f 0x00080x
>0x 0x00 0x000x00
>0x000x00 0x00 0x
>[EMAIL PROTECTED] /etc/hotplug/usb $
>
>
>
>
>
>[EMAIL PROTECTED] /etc/hotplug/usb $ cat libusbscanner
>#!/bin/sh
>
># This file is part of sane-backends.
>#
># This script changes the permissions and ownership of a USB device under
># /proc/bus/usb to grant access to this device to users in the scanner
>group.
>#
># Ownership is set to root:scanner, permissions are set to 0660.
>#
># Arguments :
># ---
># ACTION=[add|remove]
># DEVICE=/proc/bus/usb/BBB/DDD
># TYPE=usb
>
># latest hotplug doesn't set DEVICE on 2.6.x kernels
>if [ -z "$DEVICE" ] ; then
> IF=`echo $DEVPATH | sed 's/\(bus\/usb\/devices\/\)\(.*\)-\(.*\)/\2/'`
> DEV=`echo $DEVPATH | sed 's/\(bus\/usb\/devices\/\)\(.*\)-\(.*\)/\3/'`
> DEV=`expr $DEV + 1`
> DEVICE=`printf '/proc/bus/usb/%.03d/%.03d' $IF $DEV`
>fi
>
>
>if [ -z "${DEVICE}" ] ; then
>IF=$(echo ${DEVPATH} | sed
>'s:\(bus/usb/devices/\)\(.*\)-\(.*\):\2:')
>if [ -r /sys/${DEVPATH}/devnum ]; then
> DEV=$(cat /sys/${DEVPATH}/devnum)
>else
> DEV=1 # you'll have to adjust this manually for kernel < 2.6.6
>fi
>DEVICE=$(printf '/proc/bus/usb/%.03d/%.03d' ${IF} ${DEV})
>fi
>
>if [ "$ACTION" = "add" -a "$TYPE" = "usb" ]; then
> chown root:scanner "$DEVICE"
> chmod 0660 "$DEVICE"
>fi
>
>
># That's an insecure but simple alternative
># Everyone has access to the scanner
>
># if [ "$ACTION" = "add" -a "$TYPE" = "usb" ]; then
># chmod 0666 "$DEVICE"
># fi
>[EMAIL PROTECTED] /etc/hotplug/usb $
>
>
>
>
>Should set my scanner to the scanner group but does not. If I unplug my
>scanner & re-plug it in I get ...
>
>
>
>
>
>vanda_comp dave # lsusb
>Bus 002 Device 001: ID :
>Bus 001 Device 007: ID 055f:0008 Mustek Systems, Inc. ScanExpress 1200
>CU Plus
>Bus 001 Device 006: ID 046d:08b2 Logitech, Inc. QuickCam Pro 4000
>Bus 001 Device 004: ID 056a:0011 Wacom Co., Ltd Graphire 2
>Bus 001 Device 003: ID 04b8:0005 Seiko Epson Corp. Stylus Printer
>Bus 001 Device 002: ID 0409:0050 NEC Corp.
>Bus 001 Device 001: ID :
>vanda_comp dave #
>
>[EMAIL PROTECTED] /proc/bus/usb/001 $ ls -al
>total 0
>dr-xr-xr-x 2 root root 0 Jul 17 13:15 .
>drwxr-xr-x 4 root root 0 Jul
Re: [gentoo-user] SSHd: Permission denied (publickey,keyboard-interactive).
On Fri, 2008-09-12 at 06:58 -0400, Eric Martin wrote: > Michael Sullivan wrote: > > On Fri, 2008-09-12 at 15:27 +0930, Iain Buchanan wrote: > >> Michael Sullivan wrote: > >>> I hooked up my old server box today so that I could update the software, > >>> only to find that I could not ssh over to it: > >>> > >>> [EMAIL PROTECTED] ~ $ ssh bullet > >>> Permission denied (publickey,keyboard-interactive). > >>> > >>> There were no 'official' logs, but a website I found on google suggested > >>> running > >>> > >>> /usr/sbin/sshd -ddd -p 2202 > >>> > >>> and then trying to shell over with > >>> > >>> ssh -p 2202 > >>> > >>> Here's the output. I piped it to a file: > >> [snip] > >> > >>> I tried upgrading PAM and rebooting, but it didn't solve the problem. > >>> I'm running pam-1.0.1, if that matters... > >> what problem? you haven't actually said what is / isn't working! What's > >> the output from the client when you try and ssh in with the command "ssh > >> -p 2202 "? > >> > > > > I thought I was pretty clear on that, but here it is again: > > > > [EMAIL PROTECTED] ~ $ ssh -p 2202 bullet > > Permission denied (publickey,keyboard-interactive). > > > > As you can see, I'm still locked out. > > > > > try > > # ssh -p 2202 -vv bullet > > or > > #ssh -vv bullet > > as that will give you debug info from the client side of the connection. >Is it safe to assume that you logged into it via the console to start > SSHd on 2202? Also, does your user exist on the box? It sounds like > 'no', especially when btmp is involved. > Yes I logged onto the console. I also logged on with michael on bullet and it let me in, but I could not ssh to 127.0.0.1 Here's some more logging from unsuccessful attempts. [EMAIL PROTECTED] ~ $ cat sshd.log debug2: load_server_config: filename /etc/ssh/sshd_config debug2: load_server_config: done config len = 237 debug2: parse_server_config: config /etc/ssh/sshd_config len 237 debug3: /etc/ssh/sshd_config:21 setting Protocol 2 debug3: /etc/ssh/sshd_config:60 setting PasswordAuthentication no debug3: /etc/ssh/sshd_config:87 setting UsePAM yes debug3: /etc/ssh/sshd_config:91 setting X11Forwarding yes debug3: /etc/ssh/sshd_config:127 setting Subsystem sftp/usr/lib/misc/sftp-server debug1: sshd version OpenSSH_4.7p1 debug3: Not a RSA1 key file /etc/ssh/ssh_host_rsa_key. debug1: read PEM private key done: type RSA debug1: private host key: #0 type 1 RSA debug3: Not a RSA1 key file /etc/ssh/ssh_host_dsa_key. debug1: read PEM private key done: type DSA debug1: private host key: #1 type 2 DSA debug1: rexec_argv[0]='/usr/sbin/sshd' debug1: rexec_argv[1]='-ddd' debug1: rexec_argv[2]='-p' debug1: rexec_argv[3]='2202' debug2: fd 3 setting O_NONBLOCK debug1: Bind to port 2202 on 0.0.0.0. Server listening on 0.0.0.0 port 2202. socket: Address family not supported by protocol debug3: fd 4 is not O_NONBLOCK debug1: Server will not fork when running in debugging mode. debug3: send_rexec_state: entering fd = 7 config len 237 debug3: ssh_msg_send: type 0 debug3: send_rexec_state: done debug1: rexec start in 4 out 4 newsock 4 pipe -1 sock 7 debug1: inetd sockets after dupping: 3, 3 Connection from 192.168.1.2 port 43258 debug1: Client protocol version 2.0; client software version OpenSSH_4.7 debug1: match: OpenSSH_4.7 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_4.7 debug2: fd 3 setting O_NONBLOCK debug3: privsep user:group 22:22 debug1: permanently_set_uid: 22/22 debug1: list_hostkey_types: ssh-rsa,ssh-dss debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,[EMAIL PROTECTED],aes128-ctr,aes192-ctr,aes256-ctr debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,[EMAIL PROTECTED],aes128-ctr,aes192-ctr,aes256-ctr debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,[EMAIL PROTECTED],hmac-ripemd160,[EMAIL PROTECTED],hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,[EMAIL PROTECTED],hmac-ripemd160,[EMAIL PROTECTED],hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,[EMAIL PROTECTED] debug2: kex_parse_kexinit: none,[EMAIL P
[gentoo-user] smartctl contradicting itself?
Hello everybody, As a follow up to the thread subj: is harddrive kaput? the cable is fine. All the smartctl selftests return w/ no error. But #smartctl -l error /dev/hdb Home page is http://smartmontools.sourceforge.net/ === START OF READ SMART DATA SECTION === SMART Error Log Version: 1 Warning: ATA error count 94 inconsistent with error log pointer 5 ATA Error Count: 94 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 94 occurred at disk power-on lifetime: 1425 hours (59 days + 9 hours) When the command that caused the error occurred, the device was in an unknown$ After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 00 00 00 00 f0 Error: ICRC, ABRT at LBA = 0x = 0 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- c8 00 08 00 00 00 f0 08 00:05:07.920 READ DMA c8 00 08 00 00 00 f0 08 00:05:07.840 READ DMA 10 00 3f 00 00 00 f0 08 00:05:07.824 RECALIBRATE [OBS-4] c8 00 08 00 00 00 f0 08 00:05:07.760 READ DMA c8 00 08 00 00 00 f0 08 00:05:07.696 READ DMA Error 93 occurred at disk power-on lifetime: 1425 hours (59 days + 9 hours) When the command that caused the error occurred, the device was in an unknown$ After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 00 00 00 00 f0 Error: ICRC, ABRT at LBA = 0x = 0 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- c8 00 08 00 00 00 f0 08 00:05:07.840 READ DMA 10 00 3f 00 00 00 f0 08 00:05:07.824 RECALIBRATE [OBS-4] c8 00 08 00 00 00 f0 08 00:05:07.760 READ DMA c8 00 08 00 00 00 f0 08 00:05:07.696 READ DMA c8 00 08 00 00 00 f0 08 00:05:07.616 READ DMA Error 92 occurred at disk power-on lifetime: 1425 hours (59 days + 9 hours) When the command that caused the error occurred, the device was in an unknown$ After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 00 00 00 00 f0 Error: ICRC, ABRT at LBA = 0x = 0 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- c8 00 08 00 00 00 f0 08 00:05:07.760 READ DMA c8 00 08 00 00 00 f0 08 00:05:07.696 READ DMA c8 00 08 00 00 00 f0 08 00:05:07.616 READ DMA 10 00 3f 00 00 00 f0 08 00:05:07.584 RECALIBRATE [OBS-4] 91 00 3f 3f ff 3f ff 08 00:05:07.584 INITIALIZE DEVICE PARAMETERS [OBS-$ Error 91 occurred at disk power-on lifetime: 1425 hours (59 days + 9 hours) When the command that caused the error occurred, the device was in an unknown$ After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 00 00 00 00 f0 Error: ICRC, ABRT at LBA = 0x = 0 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- c8 00 08 00 00 00 f0 08 00:05:07.696 READ DMA c8 00 08 00 00 00 f0 08 00:05:07.616 READ DMA 10 00 3f 00 00 00 f0 08 00:05:07.584 RECALIBRATE [OBS-4] 91 00 3f 3f ff 3f ff 08 00:05:07.584 INITIALIZE DEVICE PARAMETERS [OBS-$ ef 03 44 00 00 00 f0 0e 00:05:07.552 SET FEATURES [Set transfer mode] Error 90 occurred at disk power-on lifetime: 1425 hours (59 days + 9 hours) When the command that caused the error occurred, the device was in an unknown$ After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 00 00 00 00 f0 Error: ICRC, ABRT at LBA = 0x = 0 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- c8 00 08 00 00 00 f0 08 00:05:07.616 READ DMA 10 00 3f 00 00 00 f0 08 00:05:07.584 RECALIBRATE [OBS-4] 91 00 3f 3f ff 3f ff 08 00:05:07.584 INITIALIZE DEVICE PARAMETERS [
Re: [gentoo-user] Long boot time after kernel update
On Mon, Dec 27, 2021 at 8:46 AM Wols Lists wrote:
>
> On 27/12/2021 13:40, Michael wrote:
> > On Monday, 27 December 2021 11:32:39 GMT Wols Lists wrote:
> >> On 27/12/2021 11:07, Jacques Montier wrote:
> >>> Well, i don't know if my partitions are aligned or mis-aligned... How
> >>> could i get it ?
> >>
> >> fdisk would have spewed a bunch of warnings. So you're okay.
> >>
> >> I'm not sure of the details, but it's the classic "off by one" problem -
> >> if there's a mismatch between the kernel block size and the disk block
> >> size any writes required doing a read-update-write cycle which of course
> >> knackered performance. I had that hit a while back.
> >>
> >> But seeing as fdisk isn't moaning, that isn't the problem ...
> >>
> >> Cheers,
> >> Wol
> >
> > I also thought of misaligned boundaries when I first saw the error, but the
> > mention of Seagate by the OP pointed me to another edge case which crept up
> > with zstd compression on ZFS. I'm mentioning it here in case it is
> > relevant:
> >
> > https://livelace.ru/posts/2021/Jul/19/unaligned-write-command/
> >
> that might be of interest to me ... I'm getting system lockups but it's
> not an SSD. I've got two IronWolves and a Barracuda.
>
> But I notice the OP has a Barra*C*uda. Note the different spelling.
> That's a shingled drive I believe, which shouldn't make a lot of
> difference in light usage, but you don't want to hammer it!
I've run into this issue and I've seen rare reports of it online, but
no sign of resolution. I'm pretty sure it is some sort of bug in the
kernel. I've tended to see it under load, and mostly when using zfs.
I do not use zstd compression and do not have any zvols on the pools
that had this issue. So, either there are multiple problems, or that
linked post did not correctly identify the root cause (which seems
likely). I'm guessing it is triggered under load and perhaps using
zstd compression helps create that load.
I haven't seen it much lately - probably because I've shifted a lot of
my load to lizardfs and also I'm using USB3 hard drives for the bulk
of my storage and since these seem to be ATA errors the removal of the
SATA host and associated drivers may bypass the problem.
I doubt this has anything to do with physical/logical sector size and
partition alignment. The disks should still work correctly if the
physical sectors aren't aligned - they should just have performance
degradation. In any case, all my drives are aligned on physical
sector boundaries. I'm not familiar enough with ATA to understand
what the actual errors are referring to.
Here is an example of one of the errors I've had in the past from one
of these situations. A zpool scrub usually clears up any damage and
then the drive works normally until the issue happens again (which
hasn't happened in quite a while for me now). I have a dump of the
SMART logs and the kernel ring buffer:
ATA Error Count: 1
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 1 occurred at disk power-on lifetime: 12838 hours (534 days + 22 hours)
When the command that caused the error occurred, the device was
active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 e0 88 cc c3 06 Error: ICRC, ABRT at LBA = 0x06c3cc88 = 113495176
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- --
61 00 c0 68 cb c3 40 08 2d+00:45:18.962 WRITE FPDMA QUEUED
60 00 b8 98 67 00 40 08 2d+00:45:18.917 READ FPDMA QUEUED
60 00 b0 98 65 00 40 08 2d+00:45:18.916 READ FPDMA QUEUED
60 00 a8 98 66 00 40 08 2d+00:45:18.916 READ FPDMA QUEUED
61 00 a0 68 ca c3 40 08 2d+00:45:18.879 WRITE FPDMA QUEUED
[354064.268896] ata6.00: exception Emask 0x11 SAct 0x100 SErr
0x48 action 0x6 frozen
[354064.268907] ata6.00: irq_stat 0x4808, interface fatal error
[354064.268910] ata6: SError: { 10B8B Handshk }
[354064.268915] ata6.00: failed command: WRITE FPDMA QUEUED
[354064.268919] a
[gentoo-user] dying hard drive?
ted_Event_Count 0x0012 100 100 000Old_age Always - 2 197 Current_Pending_Sector 0x0033 253 253 010Pre-fail Always - 0 198 Offline_Uncorrectable 0x0031 100 100 010Pre-fail Offline - 2 199 UDMA_CRC_Error_Count0x000b 100 100 051Pre-fail Always - 0 200 Multi_Zone_Error_Rate 0x000b 100 100 051Pre-fail Always - 0 201 Soft_Read_Error_Rate0x000b 100 100 051Pre-fail Always - 0 SMART Error Log Version: 1 ATA Error Count: 1 CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 1 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 51 00 01 00 00 a0 Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- b1 c0 00 01 00 00 a0 00 00:00:07.688 DEVICE CONFIGURATION RESTORE ec 00 03 01 00 00 a0 00 00:00:07.688 IDENTIFY DEVICE 91 00 3f 01 00 00 af 00 00:00:07.688 INITIALIZE DEVICE PARAMETERS [OBS-6] 10 00 00 01 00 00 a0 00 00:00:07.688 RECALIBRATE [OBS-4] ec 00 01 01 00 00 a0 00 00:00:07.688 IDENTIFY DEVICE SMART Self-test log structure revision number 1 Num Test_DescriptionStatus Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offlineCompleted: read failure 00% 11486 262886799 # 2 Short offline Completed without error 00% 11483 - Device does not support Selective Self Tests/Logging smartctl version 5.33 [i686-pc-linux-gnu] Copyright (C) 2002-4 Bruce Allen Home page is http://smartmontools.sourceforge.net/ # smartctl -l selftest /dev/hda === START OF READ SMART DATA SECTION === SMART Self-test log structure revision number 1 Num Test_DescriptionStatus Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offlineCompleted: read failure 00% 11486 262886799 # 2 Short offline Completed without error 00% 11483 - -- Matt Garman email at: http://raw-sewage.net/index.php?file=email -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] dying hard drive?
ways - 11505h+32m 10 Spin_Retry_Count0x0013 253 253 049Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000Old_age Always - 50 194 Temperature_Celsius 0x0022 163 127 000Old_age Always - 25 195 Hardware_ECC_Recovered 0x000a 100 100 000Old_age Always - 265460048 196 Reallocated_Event_Count 0x0012 100 100 000Old_age Always - 2 197 Current_Pending_Sector 0x0033 253 253 010Pre-fail Always - 0 198 Offline_Uncorrectable 0x0031 100 100 010Pre-fail Offline - 2 199 UDMA_CRC_Error_Count0x000b 100 100 051Pre-fail Always - 0 200 Multi_Zone_Error_Rate 0x000b 100 100 051Pre-fail Always - 0 201 Soft_Read_Error_Rate0x000b 100 100 051Pre-fail Always - 0 SMART Error Log Version: 1 ATA Error Count: 1 CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 1 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 51 00 01 00 00 a0 Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- b1 c0 00 01 00 00 a0 00 00:00:07.688 DEVICE CONFIGURATION RESTORE ec 00 03 01 00 00 a0 00 00:00:07.688 IDENTIFY DEVICE 91 00 3f 01 00 00 af 00 00:00:07.688 INITIALIZE DEVICE PARAMETERS [OBS-6] 10 00 00 01 00 00 a0 00 00:00:07.688 RECALIBRATE [OBS-4] ec 00 01 01 00 00 a0 00 00:00:07.688 IDENTIFY DEVICE SMART Self-test log structure revision number 1 Num Test_DescriptionStatus Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offlineCompleted: read failure 00% 11486 262886799 # 2 Short offline Completed without error 00% 11483 - Device does not support Selective Self Tests/Logging smartctl version 5.33 [i686-pc-linux-gnu] Copyright (C) 2002-4 Bruce Allen Home page is http://smartmontools.sourceforge.net/ # smartctl -l selftest /dev/hda === START OF READ SMART DATA SECTION === SMART Self-test log structure revision number 1 Num Test_DescriptionStatus Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offlineCompleted: read failure 00% 11486 262886799 # 2 Short offline Completed without error 00% 11483 - Tim -- gentoo-user@gentoo.org mailing list
[gentoo-user] Circular block (mozilla V. Seamonkey)
Hi, I couldn't find anything in the archives so I hope that I am not wasting everybody's time... I updated to xorg-x11 7.0 today, following the modular-x-howto. The X11 update in itself was flawless, but now seamonkey and mozilla are blocking one another. How do I solve this one? Thanks a lot in advance, jules omc-2 X11 # emerge -vauDNt world These are the packages that would be merged, in reverse order: Calculating world dependencies - !!! Packages for the following atoms are either all !!! masked or don't exist: dev-util/valgrind ... done! [blocks B ] www-client/mozilla (is blocking www-client/seamonkey-1.0.2) [blocks B ] www-client/seamonkey (is blocking www-client/mozilla-1.7.13) [nomerge ] gnome-base/gnome-2.12.3 USE="cdr dvdr hal -accessibility" [ebuild N] www-client/epiphany-1.8.4.1-r1 USE="python -dbus -debug -doc -firefox" 0 kB [ebuild U ] media-video/totem-1.2.1-r1 [1.2.1] USE="dvd gnome mpeg nsplugin ogg theora vorbis xine xv -a52 -debug -firefox% -flac -lirc -mad" 0 kB [nomerge ] gnome-extra/yelp-2.12.2-r1 USE="-debug -firefox" [nomerge ] www-client/seamonkey-1.0.2 USE="crypt gnome ipv6 -debug -java -ldap -mozcalendar -mozdevelop -moznocompose -moznoirc -moznomail -moznoroaming -postgres -xinerama -xprint" [nomerge ] dev-util/devhelp-0.10 USE="zlib -debug -firefox" [ebuild N] www-client/mozilla-1.7.13 USE="crypt gnome ipv6 ssl -debug -java -ldap -mozcalendar -mozdevelop -moznocompose -moznoirc -moznomail -moznoxft -mozsvg -postgres -truetype -xinerama -xprint" 0 kB [ebuild U ] sys-apps/busybox-1.1.3 [1.1.0] USE="-debug -floppyboot -make-symlinks -netboot -savedconfig -static" 1,402 kB [nomerge ] dev-util/ddd-3.3.10 [ebuild N] virtual/x11-7.0-r2 USE="dri" 0 kB [ebuild N] x11-misc/gccmakedep-1.0.2 USE="-debug" 68 kB [ebuild N] x11-libs/liboldX-1.0.1 USE="-debug" 210 kB [ebuild N] x11-libs/libXTrap-1.0.0 USE="-debug" 214 kB [ebuild N] x11-libs/libXevie-1.0.1 USE="-debug" 219 kB [ebuild N] x11-libs/libFS-1.0.0 USE="ipv6 -debug" 231 kB [ebuild N] x11-themes/xcursor-themes-1.0.1 USE="-debug" 2,204 kB [ebuild N]x11-apps/xcursorgen-1.0.1 USE="-debug" 80 kB [ebuild N] x11-apps/xsetroot-1.0.1 USE="-debug" 75 kB [ebuild N] x11-libs/libXprintAppUtil-1.0.1 USE="-debug" 203 kB [ebuild N]x11-libs/libXprintUtil-1.0.1 USE="-debug" 218 kB [ebuild N] x11-libs/libXvMC-1.0.2 USE="-debug" 224 kB [ebuild N] x11-apps/xdm-1.0.5 USE="ipv6 pam -debug -xprint" 355 kB [ebuild N] x11-apps/xdriinfo-1.0.1 USE="-debug" 79 kB [ebuild N] x11-themes/gentoo-xcursors-0.3.1 0 kB [ebuild N] x11-misc/imake-1.0.2 USE="-debug" 110 kB [ebuild N]x11-misc/xorg-cf-files-1.0.2 USE="-debug" 258 kB [ebuild N] app-text/rman-3.2 77 kB [ebuild N] dev-perl/extutils-parsexs-2.15 USE="-minimal" 23 kB [ebuild N] dev-perl/ExtUtils-CBuilder-0.18 USE="-minimal" 17 kB [nomerge ] app-portage/profuse-0.25.4 USE="gtk ncurses" [nomerge ] dev-perl/gtk2-fu-0.10 USE="-minimal" [ebuild U ] dev-perl/module-build-0.28 [0.26.11] USE="-minimal" 175 kB [ebuild U ] dev-perl/gtk2-perl-1.102 [1.062] USE="-minimal" 591 kB [ebuild U ]dev-perl/glib-perl-1.105 [1.101] USE="-minimal -xml" 222 kB [nomerge ] x11-misc/xscreensaver-4.24 USE="gnome jpeg nls opengl pam -insecure-savers -kerberos -krb4 -new-login -offensive -xinerama" [ebuild N] x11-apps/appres-1.0.0 USE="-debug" 72 kB [ebuild N] x11-apps/xwininfo-1.0.2 USE="-debug" 89 kB [nomerge ] app-misc/ca-certificates-20050804 [ebuild U ] media-libs/libpng-1.2.12 [1.2.8-r1] USE="-doc" 0 kB Total size of downloads: 7,429 kB !!! Error: The above package list contains packages which cannot be installed !!!at the same time on the same system. # ## emerge --info ## omc-2 X11 # emerge --info Portage 2.1-r1 (default-linux/amd64/2006.0, gcc-3.4.6, glibc-2.3.6-r4, 2.6.16-gentoo-r9 x86_64) = System uname: 2.6.16-gentoo-r9 x86_64 AMD Opteron(tm) Processor 252 Gentoo Base System version 1.6.15 dev-lang/python: 2.3.5-r2, 2.4.2 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: [Not Present] dev-util/confcache: [Not Present] sys-apps/sandbox:1.2.17 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2 sys-devel/binutils: 2.16.1-r3 sys-devel/gcc-c
[gentoo-user] Does this drive need a funeral?
Hi, For the first time in my life, I think I have a drive failing on me. Here is the info: root@smoker / # smartctl -a /dev/sdc smartctl 5.40 2010-10-16 r3189 [i686-pc-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Western Digital Caviar family Device Model: WDC WD800BB-00DKA0 Serial Number:WD-WCAHL2497094 Firmware Version: 77.07W77 User Capacity:80,026,361,856 bytes Device is:In smartctl database [for details use: -P show] ATA Version is: 6 ATA Standard is: Exact ATA specification draft version not indicated Local Time is:Tue Nov 1 13:52:49 2011 CDT SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: FAILED! Drive failure expected in less than 24 hours. SAVE ALL DATA. See vendor-specific Attribute list for failed Attributes. General SMART Values: Offline data collection status: (0x85) Offline data collection activity was aborted by an interrupting command from host. Auto Offline Data Collection: Enabled. Self-test execution status: ( 73) The previous self-test completed having a test element that failed and the test element that failed is not known. Total time to complete Offline data collection: (2478) seconds. Offline data collection capabilities:(0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities:(0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability:(0x01) Error logging supported. No General Purpose Logging support. Short self-test routine recommended polling time:( 2) minutes. Extended self-test routine recommended polling time:( 38) minutes. Conveyance self-test routine recommended polling time:( 5) minutes. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 018 001 051Pre-fail Always FAILING_NOW 1904 3 Spin_Up_Time0x0007 087 084 021Pre-fail Always - 2166 4 Start_Stop_Count0x0032 099 099 040Old_age Always - 1288 5 Reallocated_Sector_Ct 0x0033 199 199 140Pre-fail Always - 1 7 Seek_Error_Rate 0x000b 200 200 051Pre-fail Always - 0 9 Power_On_Hours 0x0032 023 023 000Old_age Always - 56466 10 Spin_Retry_Count0x0013 100 100 051Pre-fail Always - 0 11 Calibration_Retry_Count 0x0013 100 100 051Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 099 099 000Old_age Always - 1039 194 Temperature_Celsius 0x0022 110 253 000Old_age Always - 33 196 Reallocated_Event_Count 0x0032 199 199 000Old_age Always - 1 197 Current_Pending_Sector 0x0012 199 199 000Old_age Always - 17 198 Offline_Uncorrectable 0x0012 200 200 000Old_age Always - 10 199 UDMA_CRC_Error_Count0x000a 200 253 000Old_age Always - 1155 200 Multi_Zone_Error_Rate 0x0009 195 085 051Pre-fail Offline - 191 SMART Error Log Version: 1 ATA Error Count: 4449 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Re: [gentoo-user] [OT] HD running temperatures
8 Seek_Time_Performance 0x0005 100 100 020Pre-fail Offline - 0 9 Power_On_Hours 0x0012 099 099 000Old_age Always - 13573 10 Spin_Retry_Count0x0013 100 100 060Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000Old_age Always - 891 192 Power-Off_Retract_Count 0x0032 098 098 050Old_age Always - 2800 193 Load_Cycle_Count0x0012 098 098 050Old_age Always - 2800 194 Temperature_Celsius 0x0002 107 107 000Old_age Always - 51 (Lifetime Min/Max 11/62) 196 Reallocated_Event_Count 0x0032 100 100 000Old_age Always - 1 197 Current_Pending_Sector 0x0022 100 100 000Old_age Always - 0 198 Offline_Uncorrectable 0x0008 100 100 000Old_age Offline - 0 199 UDMA_CRC_Error_Count0x000a 200 200 000Old_age Always - 0 SMART Error Log Version: 1 ATA Error Count: 31 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 31 occurred at disk power-on lifetime: 3448 hours (143 days + 16 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 01 d2 27 93 f1 Error: UNC 1 sectors at LBA = 0x019327d2 = 26421202 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- c8 00 01 d2 27 93 f1 00 01:45:54.100 READ DMA ca 00 01 1f 30 00 f0 00 01:45:54.100 WRITE DMA ca 00 01 5f 00 00 f0 00 01:45:54.100 WRITE DMA ca 00 01 3f 00 00 f0 00 01:45:54.100 WRITE DMA c8 00 01 00 00 00 f0 00 01:45:54.100 READ DMA Error 30 occurred at disk power-on lifetime: 3448 hours (143 days + 16 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 01 d2 27 93 f1 Error: UNC 1 sectors at LBA = 0x019327d2 = 26421202 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- c8 00 01 d2 27 93 f1 00 01:45:49.100 READ DMA ca 00 01 1f 30 00 f0 00 01:45:49.100 WRITE DMA ca 00 01 5f 00 00 f0 00 01:45:49.100 WRITE DMA c8 00 01 00 00 00 f0 00 01:45:49.100 READ DMA ca 00 01 3f 00 00 f0 00 01:45:49.100 WRITE DMA Error 29 occurred at disk power-on lifetime: 3448 hours (143 days + 16 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 01 d2 27 93 f1 Error: UNC 1 sectors at LBA = 0x019327d2 = 26421202 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- c8 00 01 d2 27 93 f1 00 01:45:44.100 READ DMA ca 00 01 1f 30 00 f0 00 01:45:44.100 WRITE DMA ca 00 01 5f 00 00 f0 00 01:45:44.100 WRITE DMA ca 00 01 3f 00 00 f0 00 01:45:44.100 WRITE DMA c8 00 01 00 00 00 f0 00 01:45:44.100 READ DMA Error 28 occurred at disk power-on lifetime: 3448 hours (143 days + 16 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 01 d2 27 93 f1 Error: UNC 1 sectors at LBA = 0x019327d2 = 26421202 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- c8 00 01 d2 27 93 f1 00 01:45:39.100 READ DMA ca 00 01 1f 30 00 f0 00 01:45:39.100 WRITE DMA ca 00 01 5f 00 00 f0 00 01:45:39.100 WRITE DMA c8 00 01 00 00 00 f0 00 01:45:39.100 READ DMA ca 00 01 3f 00 00 f0 00 01:45:39.100 WRITE DMA Error 27 occurred at disk power-on lifetime: 3448 hours (143 days + 16 hours) When the command that
Re: [gentoo-user] Re: System freezes during compiles
7 Seek_Error_Rate 0x000f 252 252 051Pre-fail Always - 0 8 Seek_Time_Performance 0x0025 252 252 015Pre-fail Offline - 0 9 Power_On_Hours 0x0032 087 087 000Old_age Always - 7095 10 Spin_Retry_Count0x0033 252 252 051Pre-fail Always - 0 11 Calibration_Retry_Count 0x0032 099 099 000Old_age Always - 1151 12 Power_Cycle_Count 0x0032 099 099 000Old_age Always - 1112 184 End-to-End_Error0x0033 252 252 070Pre-fail Always - 0 187 Reported_Uncorrect 0x0032 100 100 000Old_age Always - 34 188 Command_Timeout 0x0032 100 100 000Old_age Always - 57 190 Airflow_Temperature_Cel 0x0022 069 040 040Old_age Always In_the_past 31 (Min/Max 8/60) 191 G-Sense_Error_Rate 0x0032 090 090 000Old_age Always - 103348 192 Power-Off_Retract_Count 0x0032 100 100 000Old_age Always - 332 193 Load_Cycle_Count0x0032 100 100 000Old_age Always - 9937 194 Temperature_Celsius 0x0022 064 040 000Old_age Always - 31 (Min/Max 8/60) 195 Hardware_ECC_Recovered 0x001a 001 001 000Old_age Always - 241822 196 Reallocated_Event_Count 0x0032 252 252 000Old_age Always - 0 197 Current_Pending_Sector 0x0012 252 252 000Old_age Always - 0 198 Offline_Uncorrectable 0x0030 252 252 000Old_age Offline - 0 199 UDMA_CRC_Error_Count0x0036 200 200 000Old_age Always - 27 200 Multi_Zone_Error_Rate 0x000a 100 100 000Old_age Always - 2 201 Soft_Read_Error_Rate0x0032 252 252 000Old_age Always - 0 SMART Error Log Version: 1 ATA Error Count: 26 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 26 occurred at disk power-on lifetime: 6959 hours (289 days + 23 hours) When the command that caused the error occurred, the device was in an unknown state. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 08 08 a8 4a e0 Error: UNC 8 sectors at LBA = 0x004aa808 = 4892680 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- c8 00 08 08 a8 4a e0 00 00:02:31.687 READ DMA c8 00 10 68 40 6b e0 00 00:02:24.250 READ DMA ef 05 fe 00 00 00 40 00 00:02:24.187 SET FEATURES [Enable APM] c8 00 10 e0 a7 4a e0 00 00:02:24.187 READ DMA c8 00 00 48 99 c7 e0 00 00:02:24.187 READ DMA Error 25 occurred at disk power-on lifetime: 5683 hours (236 days + 19 hours) When the command that caused the error occurred, the device was in an unknown state. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 20 40 9e 04 e1 Error: UNC 32 sectors at LBA = 0x01049e40 = 17079872 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- c8 00 20 40 9e 04 e1 00 00:15:33.812 READ DMA c8 00 10 28 c3 94 e0 00 00:15:26.375 READ DMA ef 05 fe 00 00 00 40 00 00:15:26.312 SET FEATURES [Enable APM] c8 00 20 20 9e 04 e1 00 00:15:26.312 READ DMA c8 00 08 e0 a9 73 e0 00 00:15:26.312 READ DMA Error 24 occurred at disk power-on lifetime: 5534 hours (230 days + 14 hours) When the command that caused the error occurred, the device was in an unknown state. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 08 a0 c6 54 e0 Error: UNC 8 sectors at LBA = 0x0054c6a0 = 872 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- c8 00 08 a0 c6 54 e0 00 00:10:28.500 READ DMA c8 00 68 d8 2b cc e0 00 00:10:21.062 READ DMA ef c2 00 00 00 00 40 00 00:10:21.062 SET FEATURES [Disable AAM] c8 00 10
Re: [gentoo-user] Catch all mailbox
# # The debug_peer_level parameter specifies the increment in verbose # logging level when an SMTP client or server host name or address # matches a pattern in the debug_peer_list parameter. # debug_peer_level = 2 # The debug_peer_list parameter specifies an optional list of domain # or network patterns, /file/name patterns or type:name tables. When # an SMTP client or server host name or address matches a pattern, # increase the verbose logging level by the amount specified in the # debug_peer_level parameter. # #debug_peer_list = 127.0.0.1 #debug_peer_list = some.domain # The debugger_command specifies the external command that is executed # when a Postfix daemon program is run with the -D option. # # Use "command .. & sleep 5" so that the debugger can attach before # the process marches on. If you use an X-based debugger, be sure to # set up your XAUTHORITY environment variable before starting Postfix. # debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin ddd $daemon_directory/$process_name $process_id & sleep 5 # If you can't use X, use this to capture the call stack when a # daemon crashes. The result is in a file in the configuration # directory, and is named after the process name and the process ID. # # debugger_command = # PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont; # echo where) | gdb $daemon_directory/$process_name $process_id 2>&1 # >$config_directory/$process_name.$process_id.log & sleep 5 # # Another possibility is to run gdb under a detached screen session. # To attach to the screen sesssion, su root and run "screen -r # " where uniquely matches one of the detached # sessions (from "screen -list"). # # debugger_command = # PATH=/bin:/usr/bin:/sbin:/usr/sbin; export PATH; screen # -dmS $process_name gdb $daemon_directory/$process_name # $process_id & sleep 1 # INSTALL-TIME CONFIGURATION INFORMATION # # The following parameters are used when installing a new Postfix version. # # sendmail_path: The full pathname of the Postfix sendmail command. # This is the Sendmail-compatible mail posting interface. # sendmail_path = /usr/sbin/sendmail # newaliases_path: The full pathname of the Postfix newaliases command. # This is the Sendmail-compatible command to build alias databases. # newaliases_path = /usr/bin/newaliases # mailq_path: The full pathname of the Postfix mailq command. This # is the Sendmail-compatible mail queue listing command. # mailq_path = /usr/bin/mailq # setgid_group: The group for mail submission and queue management # commands. This must be a group name with a numerical group ID that # is not shared with other accounts, not even with the Postfix account. # setgid_group = postdrop # html_directory: The location of the Postfix HTML documentation. # html_directory = /usr/share/doc/postfix-2.5.5/html # manpage_directory: The location of the Postfix on-line manual pages. # manpage_directory = /usr/share/man # sample_directory: The location of the Postfix sample configuration files. # This parameter is obsolete as of Postfix 2.1. # sample_directory = /etc/postfix # readme_directory: The location of the Postfix README files. # readme_directory = /usr/share/doc/postfix-2.5.5/readme home_mailbox = .maildir/ content_filter = smtp-amavis:[127.0.0.1]:10024 message_size_limit = 2048 # smtp auth smtpd_tls_auth_only = no smtp_use_tls = yes smtpd_sasl_auth_enable = yes smtpd_sasl_type = cyrus local_recipient_maps = smtpd_use_tls = yes smtp_tls_note_starttls_offer = yes smtpd_tls_key_file = /etc/ssl/cyrus/server.key smtpd_tls_cert_file = /etc/ssl/cyrus/server.crt smtpd_tls_CAfile = /etc/ssl/cacert.pem smtpd_tls_loglevel = 1 smtpd_tls_received_header = yes smtpd_tls_session_cache_timeout = 3600s tls_random_source = dev:/dev/urandom notify_classes = bounce, delay, policy, protocol, resource, software bounce_notice_recipient = shared+admin.HoshiDomains.data.mail.Fetchmail 2bounce_notice_recipient = shared+admin.HoshiDomains.data.mail.Fetchmail delay_notice_recipient = shared+admin.HoshiDomains.data.mail.Fetchmail error_notice_recipient = shared+admin.HoshiDomains.data.mail.Fetchmail #luser_relay = shared+admin.HoshiDomains.data.mail.Fetchmail
