Logo GNT
Actualités Tests & Guides Bons Plans
Twitter iPhone pliant OnePlus 11 PS5 Disney+ Orange Livebox Windows 11
Entraide Linux Autres OS Linux Debian Smartd disque HS?

Smartd disque HS?

4 réponses
Avatar
Georges Roux
Bonjour,

Smartd le daemon qui controle le disque viens de me mailer ceci:

-----------------------------------------------------------

This email was generated by the smartd daemon running on:

host name: mimosa
DNS domain: [Unknown]
NIS domain: (none)

The following warning/error was logged by the smartd daemon:

Device: /dev/hda, ATA error count increased from 1215 to 1216

For details see host's SYSLOG (default: /var/log/messages).

You can also use the smartctl utility for further investigation.
No additional email messages about this problem will be sent.

-------------------------------------------------------------

et dans syslog j'ai ça:

Apr 29 10:37:28 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 10:37:28 mimosa smartd[3719]: Sending warning via mail to root ...
Apr 29 10:37:28 mimosa smartd[3719]: Warning via mail to root: successful
Apr 29 10:37:28 mimosa smartd[3719]: Device: /dev/hda, SMART Usage Attribute: 197 Current_Pending_Sector changed from 253 to 252
Apr 29 10:37:28 mimosa smartd[3719]: Device: /dev/hda, ATA error count increased from 1215 to 1216
Apr 29 10:37:28 mimosa smartd[3719]: Sending warning via mail to root ...
Apr 29 10:37:28 mimosa smartd[3719]: Warning via mail to root: successful
Apr 29 11:07:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 11:37:28 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 12:07:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 12:37:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 13:07:28 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 13:37:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 14:07:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 14:37:28 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 15:07:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 15:37:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 16:07:28 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 16:37:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 17:07:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 17:37:28 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 18:07:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 18:37:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 19:07:28 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 19:37:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 20:07:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 20:37:28 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 21:07:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 21:37:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 22:07:28 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 22:37:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 23:07:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 23:37:28 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 30 00:07:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 30 00:37:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 30 01:07:28 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 30 01:07:28 mimosa smartd[3719]: Device: /dev/hda, starting scheduled Short Self-Test.
Apr 30 01:37:27 mimosa smartd[3719]: Device: /dev/hda, SMART Usage Attribute: 196 Reallocated_Event_Count changed from 253 to 252
Apr 30 01:37:27 mimosa smartd[3719]: Device: /dev/hda, SMART Usage Attribute: 197 Current_Pending_Sector changed from 252 to 253
Apr 30 03:07:28 mimosa smartd[3719]: Device: /dev/hda, starting scheduled Long Self-Test.

Cela veut il dire que mon disque vas me lacher?

Georges


--
Pensez à lire la FAQ de la liste avant de poser une question :
http://wiki.debian.net/?DebianFrench

Pensez à rajouter le mot ``spam'' dans vos champs "From" et "Reply-To:"

To UNSUBSCRIBE, email to debian-user-french-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Signaler un problème avec ce contenu

4 réponses

Supprimer
Cette action est irreversible, confirmez la suppression du commentaire ?
Signaler le commentaire

Veuillez sélectionner un problème

Nudité
Violence
Harcèlement
Fraude
Vente illégale
Discours haineux
Terrorisme
Autre
Avatar
deny
Georges Roux a écrit :

Bonjour,

Smartd le daemon qui controle le disque viens de me mailer ceci:

-----------------------------------------------------------

This email was generated by the smartd daemon running on:

host name: mimosa
DNS domain: [Unknown]
NIS domain: (none)

The following warning/error was logged by the smartd daemon:

Device: /dev/hda, ATA error count increased from 1215 to 1216

For details see host's SYSLOG (default: /var/log/messages).

You can also use the smartctl utility for further investigation.
No additional email messages about this problem will be sent.

-------------------------------------------------------------

et dans syslog j'ai ça:

Apr 29 10:37:28 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 10:37:28 mimosa smartd[3719]: Sending warning via mail to root ...
Apr 29 10:37:28 mimosa smartd[3719]: Warning via mail to root: successful
Apr 29 10:37:28 mimosa smartd[3719]: Device: /dev/hda, SMART Usage Attribute: 197 Current_Pending_Sector changed from 253 to 252
Apr 29 10:37:28 mimosa smartd[3719]: Device: /dev/hda, ATA error count increased from 1215 to 1216
Apr 29 10:37:28 mimosa smartd[3719]: Sending warning via mail to root ...
Apr 29 10:37:28 mimosa smartd[3719]: Warning via mail to root: successful
Apr 29 11:07:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 11:37:28 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 12:07:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 12:37:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 13:07:28 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 13:37:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 14:07:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 14:37:28 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 15:07:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 15:37:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 16:07:28 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 16:37:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 17:07:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 17:37:28 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 18:07:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 18:37:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 19:07:28 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 19:37:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 20:07:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 20:37:28 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 21:07:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 21:37:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 22:07:28 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 22:37:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 23:07:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 23:37:28 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 30 00:07:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 30 00:37:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 30 01:07:28 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 30 01:07:28 mimosa smartd[3719]: Device: /dev/hda, starting scheduled Short Self-Test.
Apr 30 01:37:27 mimosa smartd[3719]: Device: /dev/hda, SMART Usage Attribute: 196 Reallocated_Event_Count changed from 253 to 252
Apr 30 01:37:27 mimosa smartd[3719]: Device: /dev/hda, SMART Usage Attribute: 197 Current_Pending_Sector changed from 252 to 253
Apr 30 03:07:28 mimosa smartd[3719]: Device: /dev/hda, starting scheduled Long Self-Test.

Cela veut il dire que mon disque vas me lacher?

Georges






salut
lance un :

smartctl -t short /dev/hdx (remplace x par le disque a controler)
puis :
smartctl -l selftest /dev/hdx

tu auras des infos sur l"etat general de ton disque et la durée tres theorique
du temps qu'il lui resta à vivre
il y a de multiples paramètres pour établir la bonne santé de ton disque dur ,
et s'inquieter d'un seul message d'avertissement peut apparaitre un peu prematuré
(en voici la liste : http://lea-linux.org/hardware/hard_plus/smart.html)
dans tous les cas : sauvegardons !


--
http://www.linux-pour-lesnuls.com


--
Pensez à lire la FAQ de la liste avant de poser une question :
http://wiki.debian.net/?DebianFrench

Pensez à rajouter le mot ``spam'' dans vos champs "From" et "Reply-To:"

To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact
Avatar
Jean-Luc Coulon (f5ibh)
--=-DKCqwwUVbBhXEdUPqQaW
Content-Type: text/plain; charset=iso-8859-15; DelSp=Yes; Format=Flowed
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Le 01.05.2005 11:01:36, Basile STARYNKEVITCH a écrit :
Le Sat, Apr 30, 2005 at 11:45:49PM +0200, Georges Roux écrivait/wrote:



[ .. ]
>
> Cela veut il dire que mon disque vas me lacher?

Je n'ai pas une grande experience en ce domaine, mais les 2 fois où
j'ai eu une erreur disque comme ça, le disque suspect est mort en
quelques jours au plus.

Donc, essayez si possible de sauvegarder votre disque, et envisagez de
le remplacer.

Mon point de vue actuel est que les disques sont quasiment des
"consommables" - à leur première défaillance, il faut les remplacer .



Je vote pour : sauvegarde, poubell, remplacement, restauration


Bon courage


--
Basile STARYNKEVITCH http://starynkevitch.net/Basile/



J-L

--=-DKCqwwUVbBhXEdUPqQaW
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQBCdJvvUdGGXzzGnNARAp1TAKCsXyTLh8LWsAKdIKSQfIxXvKAIdACgkawS
E36nlckVWLmCxzLQiRU9uKY Ø1/
-----END PGP SIGNATURE-----

--=-DKCqwwUVbBhXEdUPqQaW--



--
Pensez à lire la FAQ de la liste avant de poser une question :
http://wiki.debian.net/?DebianFrench

Pensez à rajouter le mot ``spam'' dans vos champs "From" et "Reply-To:"

To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact
Avatar
Basile STARYNKEVITCH
Le Sat, Apr 30, 2005 at 11:45:49PM +0200, Georges Roux écrivait/wrote:
Bonjour,

Smartd le daemon qui controle le disque viens de me mailer ceci:

-----------------------------------------------------------

This email was generated by the smartd daemon running on:

host name: mimosa
DNS domain: [Unknown]
NIS domain: (none)

The following warning/error was logged by the smartd daemon:

Device: /dev/hda, ATA error count increased from 1215 to 1216



[...]


et dans syslog j'ai ça:

Apr 29 10:37:28 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 10:37:28 mimosa smartd[3719]: Sending warning via mail to root ...
Apr 29 10:37:28 mimosa smartd[3719]: Warning via mail to root: successful
Apr 29 10:37:28 mimosa smartd[3719]: Device: /dev/hda, SMART Usage Attribute: 197 Current_Pending_Sector changed from 253 to 252
Apr 29 10:37:28 mimosa smartd[3719]: Device: /dev/hda, ATA error count increased from 1215 to 1216
Apr 29 10:37:28 mimosa smartd[3719]: Sending warning via mail to root ...
Apr 29 10:37:28 mimosa smartd[3719]: Warning via mail to root: successful
Apr 29 11:07:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 11:37:28 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 12:07:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 12:37:27 mimosa smartd[3719]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Apr 29 13:07:28 mimosa smartd[3719]: Device: /dev/hda, 1 Currently
unreadable (pending) sectors


[...]

Apr 30 01:07:28 mimosa smartd[3719]: Device: /dev/hda, starting scheduled Short Self-Test.
Apr 30 01:37:27 mimosa smartd[3719]: Device: /dev/hda, SMART Usage Attribute: 196 Reallocated_Event_Count changed from 253 to 252
Apr 30 01:37:27 mimosa smartd[3719]: Device: /dev/hda, SMART Usage Attribute: 197 Current_Pending_Sector changed from 252 to 253
Apr 30 03:07:28 mimosa smartd[3719]: Device: /dev/hda, starting scheduled Long Self-Test.

Cela veut il dire que mon disque vas me lacher?



Je n'ai pas une grande experience en ce domaine, mais les 2 fois où
j'ai eu une erreur disque comme ça, le disque suspect est mort en
quelques jours au plus.

Donc, essayez si possible de sauvegarder votre disque, et envisagez de
le remplacer.

Mon point de vue actuel est que les disques sont quasiment des
"consommables" - à leur première défaillance, il faut les remplacer.

Bon courage


--
Basile STARYNKEVITCH http://starynkevitch.net/Basile/
email: basile<at>starynkevitch<dot>net
aliases: basile<at>tunes<dot>org = bstarynk<at>nerim<dot>net
8, rue de la Faïencerie, 92340 Bourg La Reine, France


--
Pensez à lire la FAQ de la liste avant de poser une question :
http://wiki.debian.net/?DebianFrench

Pensez à rajouter le mot ``spam'' dans vos champs "From" et "Reply-To:"

To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact
Avatar
DominiX
Basile STARYNKEVITCH wrote:
Le Sat, Apr 30, 2005 at 11:45:49PM +0200, Georges Roux écrivait/wrote:

Bonjour,

Smartd le daemon qui controle le disque viens de me mailer ceci:

-----------------------------------------------------------

This email was generated by the smartd daemon running on:

host name: mimosa
DNS domain: [Unknown]
NIS domain: (none)

The following warning/error was logged by the smartd daemon:

Device: /dev/hda, ATA error count increased from 1215 to 1216






[...]


Mon point de vue actuel est que les disques sont quasiment des
"consommables" - à leur première défaillance, il faut les remplacer.




je vote pour aussi.

Bon courage




--
dominix


--
Pensez à lire la FAQ de la liste avant de poser une question :
http://wiki.debian.net/?DebianFrench

Pensez à rajouter le mot ``spam'' dans vos champs "From" et "Reply-To:"

To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact