From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id B5990ED93 for ; Tue, 13 Dec 2022 11:52:16 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 96EEF1E3DA for ; Tue, 13 Dec 2022 11:51:46 +0100 (CET) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for ; Tue, 13 Dec 2022 11:51:45 +0100 (CET) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 729C244E01 for ; Tue, 13 Dec 2022 11:51:45 +0100 (CET) Message-ID: Date: Tue, 13 Dec 2022 11:51:44 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.5.0 Content-Language: en-US To: pve-user@lists.proxmox.com References: <20221128174156.gal7tmxds22tjreq@cloud0> <360k6j-u5c1.ln1@hermione.lilliput.linux.it> From: Stefan Hanreich In-Reply-To: <360k6j-u5c1.ln1@hermione.lilliput.linux.it> X-SPAM-LEVEL: Spam detection results: 0 AWL 0.524 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% HTML_MESSAGE 0.001 HTML included in message KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment NICE_REPLY_A -0.001 Looks like a legit reply (A) PLING_QUERY 0.1 Subject has exclamation mark and question mark SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [die.net] Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: Re: [PVE-User] OfflineUncorrectableSector, and now?! X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2022 10:52:16 -0000 These warnings get governed by the configuration in /etc/smartd.conf The only line in the default configuration line looks like this: DEVICESCAN -d removable -n standby -m root -M exec /usr/share/smartmontools/smartd-runner You can change this to the following line to only get email notifications when the value of SMART attribute 198 increases: |DEVICESCAN -U 198+ -d removable -n standby -m root -M exec /usr/share/smartmontools/smartd-runner | You can find the documentation for this file in the respective man page [1]. Kind Regards Stefan || [1] https://linux.die.net/man/5/smartd.conf || On 12/12/22 17:07, Marco Gaiarin wrote: > Mandi! Yannick Palanque > In chel di` si favelave... > >> I see that it is a Dell SSD. Do you have any contract support? You >> could ask to their support what they think of it. > DELL support say that disk is good. > > > Thre's some way to disable daily SMART email, eg defining that '8 bad sector > is good'? Clearly without disabling SMART at all... > > > If i've understood well, 'smartd' send notification using scripts in > '/etc/smartmontools/run.d/', and particulary: > > /etc/smartmontools/run.d/10mail > > I've to code a custom script? > > > I've used to have smartd signal disk trouble once, and reading manpages > seems that this is still the default behaviour... > >From s.hanreich@proxmox.com Tue Dec 13 11:56:58 2022 Return-Path: X-Original-To: pve-user@lists.proxmox.com Delivered-To: pve-user@lists.proxmox.com Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 3E361EE1F for ; Tue, 13 Dec 2022 11:56:58 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 19B8A1E495 for ; Tue, 13 Dec 2022 11:56:28 +0100 (CET) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for ; Tue, 13 Dec 2022 11:56:26 +0100 (CET) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 202B144D8C for ; Tue, 13 Dec 2022 11:56:26 +0100 (CET) Message-ID: Date: Tue, 13 Dec 2022 11:56:24 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.5.0 Content-Language: en-US To: pve-user@lists.proxmox.com References: <20221128174156.gal7tmxds22tjreq@cloud0> <360k6j-u5c1.ln1@hermione.lilliput.linux.it> From: Stefan Hanreich In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.518 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment NICE_REPLY_A -0.001 Looks like a legit reply (A) PLING_QUERY 0.1 Subject has exclamation mark and question mark SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [die.net, proxmox.com] Subject: Re: [PVE-User] OfflineUncorrectableSector, and now?! X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2022 10:56:58 -0000 Seems like there were some issues with the formatting of my last mail, so I am writing again: The default config looks like this: DEVICESCAN -d removable -n standby -m root -M exec /usr/share/smartmontools/smartd-runner This would need to be adapted like this: DEVICESCAN -U 198+ -d removable -n standby -m root -M exec /usr/share/smartmontools/smartd-runner Kind Regards On 12/13/22 11:51, Stefan Hanreich wrote: > These warnings get governed by the configuration in /etc/smartd.conf > > The only line in the default configuration line looks like this: > > DEVICESCAN -d removable -n standby -m root -M exec > /usr/share/smartmontools/smartd-runner > > You can change this to the following line to only get email > notifications when the value of SMART attribute 198 increases: > > |DEVICESCAN -U 198+ -d removable -n standby -m root -M exec > /usr/share/smartmontools/smartd-runner | > > You can find the documentation for this file in the respective man page > [1]. > > Kind Regards > Stefan > > > || > > [1] https://linux.die.net/man/5/smartd.conf > > || > > On 12/12/22 17:07, Marco Gaiarin wrote: >> Mandi! Yannick Palanque >>    In chel di` si favelave... >> >>> I see that it is a Dell SSD. Do you have any contract support? You >>> could ask to their support what they think of it. >> DELL support say that disk is good. >> >> >> Thre's some way to disable daily SMART email, eg defining that '8 bad >> sector >> is good'? Clearly without disabling SMART at all... >> >> >> If i've understood well, 'smartd' send notification using scripts in >> '/etc/smartmontools/run.d/', and particulary: >> >>     /etc/smartmontools/run.d/10mail >> >> I've to code a custom script? >> >> >> I've used to have smartd signal disk trouble once, and reading manpages >> seems that this is still the default behaviour... >> > _______________________________________________ > pve-user mailing list > pve-user@lists.proxmox.com > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user > >