Contenu | Rechercher | Menus

Annonce

Si vous avez des soucis pour rester connecté, déconnectez-vous puis reconnectez-vous depuis ce lien en cochant la case
Me connecter automatiquement lors de mes prochaines visites.

À propos de l'équipe du forum.

Pages : 1 2

#26 Le 29/09/2021, à 12:48

Coeur Noir

Re : Erreurs dans dmesg : de quoi dois-je m'inquiéter ?

Suite à un redémarrage hier, après des mises à jour, le boot a pris dans les 40 secondes ( au lieu des 10 habituelles ) avec ces erreurs dans le dmesg :

django@ASGARD:~$ dmesg | grep -Ei "error|warning"
[    0.488819] RAS: Correctable Errors collector initialized.
(…) quelques lignes concernant ACPI (…)
[   12.332957] EXT4-fs (sdb1): re-mounted. Opts: errors=remount-ro. Quota mode: none.
                        res 61/04:00:00:80:98/00:00:ff:00:00/a0 Emask 0x1 (device error)
[   17.088191] ata5.00: error: { ABRT }
                        res 61/04:00:00:80:98/00:00:ff:00:00/a0 Emask 0x1 (device error)
[   21.364186] ata5.00: error: { ABRT }
                        res 61/04:00:00:80:98/00:00:ff:00:00/a0 Emask 0x1 (device error)
[   25.720178] ata5.00: error: { ABRT }
[   29.992089] ata5.00: NCQ disabled due to excessive errors
                        res 61/04:00:00:80:98/00:00:ff:00:00/a0 Emask 0x1 (device error)
[   29.992221] ata5.00: error: { ABRT }
                        res 61/04:00:00:80:98/00:00:ff:00:00/a0 Emask 0x1 (device error)
[   36.352554] ata5.00: error: { ABRT }
                        res 61/04:00:00:80:98/00:00:ff:00:00/a0 Emask 0x1 (device error)
[   42.692553] ata5.00: error: { ABRT }
[   44.814891] blk_update_request: I/O error, dev sda, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
django@ASGARD:~$

Mais au démarrage d'aujourd'hui, rien à signaler, aucune erreur sur ata5.00…

Débuter ⋅ Doc ⋅ Bien rédiger ⋅ Retour commande ⋅ Insérer image | illustrations & captures d'écran < ⋅ >

Hors ligne

#27 Le 07/10/2021, à 00:01

Coeur Noir

Re : Erreurs dans dmesg : de quoi dois-je m'inquiéter ?

Quelques jours plus tard…

django@ASGARD:~$ dmesg | grep -Ei "error|warning"
[    0.623448] RAS: Correctable Errors collector initialized.
[    0.827057] ACPI Warning: SystemIO range 0x0000000000001828-0x000000000000182F conflicts with OpRegion 0x0000000000001800-0x000000000000187F (\PMIO) (20201113/utaddress-204)
[    0.827083] ACPI Warning: SystemIO range 0x0000000000001C40-0x0000000000001C4F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20201113/utaddress-204)
[    0.827199] ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) (20201113/utaddress-204)
[    0.827205] ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20201113/utaddress-204)
[    0.827473] ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) (20201113/utaddress-204)
[    0.827479] ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20201113/utaddress-204)
[    1.169998] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20201113/psargs-330)
[    1.170010] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20201113/psparse-529)
[    1.171395] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20201113/psargs-330)
[    1.171406] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20201113/psparse-529)
[   11.376549] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20201113/psargs-330)
[   11.376598] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20201113/psparse-529)
[   11.488812] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20201113/psargs-330)
[   11.488859] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20201113/psparse-529)
[   12.482080] EXT4-fs (sdb1): re-mounted. Opts: errors=remount-ro. Quota mode: none.
                        res 61/04:00:00:80:98/00:00:ff:00:00/a0 Emask 0x1 (device error)
[   17.270846] ata5.00: error: { ABRT }
                        res 61/04:00:00:80:98/00:00:ff:00:00/a0 Emask 0x1 (device error)
[   21.527220] ata5.00: error: { ABRT }
                        res 61/04:00:00:80:98/00:00:ff:00:00/a0 Emask 0x1 (device error)
[   25.867214] ata5.00: error: { ABRT }
[   30.134789] ata5.00: NCQ disabled due to excessive errors
                        res 61/04:00:00:80:98/00:00:ff:00:00/a0 Emask 0x1 (device error)
[   30.134850] ata5.00: error: { ABRT }
                        res 61/04:00:00:80:98/00:00:ff:00:00/a0 Emask 0x1 (device error)
[   36.478846] ata5.00: error: { ABRT }
                        res 61/04:00:00:80:98/00:00:ff:00:00/a0 Emask 0x1 (device error)
[   42.826843] ata5.00: error: { ABRT }
[   44.944005] blk_update_request: I/O error, dev sda, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
django@ASGARD:~$

Débuter ⋅ Doc ⋅ Bien rédiger ⋅ Retour commande ⋅ Insérer image | illustrations & captures d'écran < ⋅ >

Hors ligne

#28 Le 07/10/2021, à 10:19

geole

Re : Erreurs dans dmesg : de quoi dois-je m'inquiéter ?

Bonjour
Redonne 

sudo smartctl -s on -a /dev/sda
sudo smartctl -s on -a /dev/sdb

Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit,  utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir  https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248

Hors ligne

#29 Le 07/10/2021, à 10:37

Coeur Noir

Re : Erreurs dans dmesg : de quoi dois-je m'inquiéter ?

Et aujourd'hui, démarrage nickel…

django@ASGARD:~$ sudo smartctl -s on -a /dev/sda
[sudo] Mot de passe de django : 
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.11.0-37-generic] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Blue
Device Model:     WDC WD10EZEX-00BN5A0
Serial Number:    WD-WCC3F0348707
LU WWN Device Id: 5 0014ee 20959e582
Firmware Version: 01.01A01
User Capacity:    1000204886016 bytes [1,00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Thu Oct  7 11:34:14 2021 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Enabled.

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x82)	Offline data collection activity
					was completed without error.
					Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		(11400) 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.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 118) minutes.
Conveyance self-test routine
recommended polling time: 	 (   5) minutes.
SCT capabilities: 	       (0x3035)	SCT Status supported.
					SCT Feature Control supported.
					SCT Data Table supported.

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     0x002f   200   200   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   167   166   021    Pre-fail  Always       -       2608
  4 Start_Stop_Count        0x0032   096   096   000    Old_age   Always       -       4205
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   059   059   000    Old_age   Always       -       30304
 10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   096   096   000    Old_age   Always       -       4205
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       157
193 Load_Cycle_Count        0x0032   199   199   000    Old_age   Always       -       4048
194 Temperature_Celsius     0x0022   120   096   000    Old_age   Always       -       23
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%     23105         -
# 2  Short offline       Completed without error       00%      7908         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

django@ASGARD:~$ sudo smartctl -s on -a /dev/sdb
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.11.0-37-generic] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Samsung based SSDs
Device Model:     Samsung SSD 840 EVO 120GB
Serial Number:    S1D5NSADB89673F
LU WWN Device Id: 5 002538 8a00e26fd
Firmware Version: EXT0BB6Q
User Capacity:    120034123776 bytes [120 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2, ATA8-ACS T13/1699-D revision 4c
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Thu Oct  7 11:35:16 2021 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Enabled.

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		( 4200) seconds.
Offline data collection
capabilities: 			 (0x53) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					No Offline surface scan supported.
					Self-test supported.
					No 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.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 (  70) minutes.
SCT capabilities: 	       (0x003d)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  9 Power_On_Hours          0x0032   094   094   000    Old_age   Always       -       30067
 12 Power_Cycle_Count       0x0032   095   095   000    Old_age   Always       -       4439
177 Wear_Leveling_Count     0x0013   096   096   000    Pre-fail  Always       -       39
179 Used_Rsvd_Blk_Cnt_Tot   0x0013   100   100   010    Pre-fail  Always       -       0
181 Program_Fail_Cnt_Total  0x0032   100   100   010    Old_age   Always       -       0
182 Erase_Fail_Count_Total  0x0032   100   100   010    Old_age   Always       -       0
183 Runtime_Bad_Block       0x0013   100   100   010    Pre-fail  Always       -       0
187 Uncorrectable_Error_Cnt 0x0032   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0032   077   054   000    Old_age   Always       -       23
195 ECC_Error_Rate          0x001a   200   200   000    Old_age   Always       -       0
199 CRC_Error_Count         0x003e   100   100   000    Old_age   Always       -       0
235 POR_Recovery_Count      0x0012   099   099   000    Old_age   Always       -       390
241 Total_LBAs_Written      0x0032   099   099   000    Old_age   Always       -       11049893530

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%         9         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

django@ASGARD:~$

Débuter ⋅ Doc ⋅ Bien rédiger ⋅ Retour commande ⋅ Insérer image | illustrations & captures d'écran < ⋅ >

Hors ligne

#30 Le 07/10/2021, à 10:55

geole

Re : Erreurs dans dmesg : de quoi dois-je m'inquiéter ?

Il n'y a rien d'indiqué pour les deux disques.
Peut-être regarder s'il n'y a pas de faux contact au niveau du branchement des câbles

Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit,  utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir  https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248

Hors ligne

#31 Le 07/10/2021, à 17:59

Coeur Noir

Re : Erreurs dans dmesg : de quoi dois-je m'inquiéter ?

…câbles neufs, depuis quelques semaines.

Aujourd'hui encore r. à s.

Débuter ⋅ Doc ⋅ Bien rédiger ⋅ Retour commande ⋅ Insérer image | illustrations & captures d'écran < ⋅ >

Hors ligne

#32 Le 22/10/2021, à 21:07

Coeur Noir

Re : Erreurs dans dmesg : de quoi dois-je m'inquiéter ?

Tiens big_smile

django@ASGARD:~$ dmesg | grep -Ei "error|warning"
[    0.632062] RAS: Correctable Errors collector initialized.
[    0.810819] ACPI Warning: SystemIO range 0x0000000000001828-0x000000000000182F conflicts with OpRegion 0x0000000000001800-0x000000000000187F (\PMIO) (20201113/utaddress-204)
[    0.810836] ACPI Warning: SystemIO range 0x0000000000001C40-0x0000000000001C4F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20201113/utaddress-204)
[    0.810870] ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) (20201113/utaddress-204)
[    0.810875] ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20201113/utaddress-204)
[    0.810886] ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) (20201113/utaddress-204)
[    0.810891] ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20201113/utaddress-204)
[    1.162595] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20201113/psargs-330)
[    1.162608] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20201113/psparse-529)
[    1.163986] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20201113/psargs-330)
[    1.163997] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20201113/psparse-529)
[    9.267995] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20201113/psargs-330)
[    9.268044] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20201113/psparse-529)
[    9.380668] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20201113/psargs-330)
[    9.380715] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20201113/psparse-529)
[   10.369883] EXT4-fs (sdb1): re-mounted. Opts: errors=remount-ro. Quota mode: none.
                        res 61/04:00:00:80:98/00:00:ff:00:00/a0 Emask 0x1 (device error)
[   16.760442] ata5.00: error: { ABRT }
                        res 61/04:00:00:80:98/00:00:ff:00:00/a0 Emask 0x1 (device error)
[   21.024498] ata5.00: error: { ABRT }
                        res 61/04:00:00:80:98/00:00:ff:00:00/a0 Emask 0x1 (device error)
[   25.372875] ata5.00: error: { ABRT }
[   29.648442] ata5.00: NCQ disabled due to excessive errors
                        res 61/04:00:00:80:98/00:00:ff:00:00/a0 Emask 0x1 (device error)
[   29.648882] ata5.00: error: { ABRT }
                        res 61/04:00:00:80:98/00:00:ff:00:00/a0 Emask 0x1 (device error)
[   35.996497] ata5.00: error: { ABRT }
                        res 61/04:00:00:80:98/00:00:ff:00:00/a0 Emask 0x1 (device error)
[   42.348496] ata5.00: error: { ABRT }
[   44.468764] blk_update_request: I/O error, dev sda, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
django@ASGARD:~$

…3 semaines plus tard, et il me semble bien qu'il y a eu nouveau m.à.j noyau récemment…

Débuter ⋅ Doc ⋅ Bien rédiger ⋅ Retour commande ⋅ Insérer image | illustrations & captures d'écran < ⋅ >

Hors ligne

#33 Le 08/11/2021, à 21:28

Coeur Noir

Re : Erreurs dans dmesg : de quoi dois-je m'inquiéter ?

Bon ça a l'air de coïncider, je viens de voir passer une m.à.j noyau ( 5.11.0-40-generic ) et au démarrage suivant :

django@ASGARD:~$ dmesg | grep -Ei "error|warning"
[    0.630436] RAS: Correctable Errors collector initialized.
[    0.802622] ACPI Warning: SystemIO range 0x0000000000001828-0x000000000000182F conflicts with OpRegion 0x0000000000001800-0x000000000000187F (\PMIO) (20201113/utaddress-204)
[    0.802635] ACPI Warning: SystemIO range 0x0000000000001C40-0x0000000000001C4F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20201113/utaddress-204)
[    0.802641] ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) (20201113/utaddress-204)
[    0.802646] ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20201113/utaddress-204)
[    0.802652] ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) (20201113/utaddress-204)
[    0.802656] ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20201113/utaddress-204)
[    1.149659] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20201113/psargs-330)
[    1.149674] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20201113/psparse-529)
[    1.150538] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20201113/psargs-330)
[    1.150546] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20201113/psparse-529)
[   11.364133] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20201113/psargs-330)
[   11.364182] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20201113/psparse-529)
[   11.474203] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20201113/psargs-330)
[   11.474251] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20201113/psparse-529)
[   12.508597] EXT4-fs (sdb1): re-mounted. Opts: errors=remount-ro. Quota mode: none.
                        res 61/04:00:00:80:98/00:00:ff:00:00/a0 Emask 0x1 (device error)
[   22.206835] ata5.00: error: { ABRT }
                        res 61/04:00:00:80:98/00:00:ff:00:00/a0 Emask 0x1 (device error)
[   26.470859] ata5.00: error: { ABRT }
                        res 61/04:00:00:80:98/00:00:ff:00:00/a0 Emask 0x1 (device error)
[   30.810860] ata5.00: error: { ABRT }
[   35.078805] ata5.00: NCQ disabled due to excessive errors
                        res 61/04:00:00:80:98/00:00:ff:00:00/a0 Emask 0x1 (device error)
[   35.078862] ata5.00: error: { ABRT }
                        res 61/04:00:00:80:98/00:00:ff:00:00/a0 Emask 0x1 (device error)
[   41.426860] ata5.00: error: { ABRT }
                        res 61/04:00:00:80:98/00:00:ff:00:00/a0 Emask 0x1 (device error)
[   47.778860] ata5.00: error: { ABRT }
[   49.889190] blk_update_request: I/O error, dev sda, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
django@ASGARD:~$

Débuter ⋅ Doc ⋅ Bien rédiger ⋅ Retour commande ⋅ Insérer image | illustrations & captures d'écran < ⋅ >

Hors ligne

#34 Le 18/12/2021, à 18:31

Coeur Noir

Re : Erreurs dans dmesg : de quoi dois-je m'inquiéter ?

Bon… y'a environ 2 semaines j'ai encore eu le même genre de ralentissement, les mêmes messages d'erreurs, puis ça s'est « aggravé » avec plus d'accès au DD - le système finit par démarrer sans les documents des utilisateurs, ce qui est pas top utile.

J'ai donc viré ce disque et mis celui de « sauvegarde » à la place. Depuis pas le moindre incident - si ce n'est que ce disque ( hitachi ) est relativement bruyant.

Donc y'avait bien un problème sur le disque Western Digital.

Débuter ⋅ Doc ⋅ Bien rédiger ⋅ Retour commande ⋅ Insérer image | illustrations & captures d'écran < ⋅ >

Hors ligne

#35 Le 18/12/2021, à 19:46

geole

Re : Erreurs dans dmesg : de quoi dois-je m'inquiéter ?

geole a écrit :
Coeur Noir a écrit :

Hello,

[   43.101753] blk_update_request: I/O error, dev sda, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0

Bonjour
Cela se passe en phase de démarrage  et te fait perdre pas loin de 18 secondes.
Soit il y a un problème "chauffe"....
Soit le secteur zéro est vraiment illisible  et ton disque a une table de partition gpt. La duplication est alors utilisée.
Soit le secteur 0 finit par être lu et tu peux enfin accéder aux partitions..... Attention pour le jour où la réparation n'aura plus lieu.

Cela a fini par arriver.
Attention pour le jour où la réparation n'aura plus lieu.

Dernière modification par geole (Le 18/12/2021, à 21:44)

Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit,  utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir  https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248

Hors ligne

#36 Le 18/12/2021, à 20:26

Coeur Noir

Re : Erreurs dans dmesg : de quoi dois-je m'inquiéter ?

Tables de partitions mbr/msdos sur mes disques, ici.

Donc là t'es en train de me dire que le secteur 0 de ce disque est proche de la mort, c'est ça ?

Y'a moyen de « réparer » ou il est bon à détruire ?

Débuter ⋅ Doc ⋅ Bien rédiger ⋅ Retour commande ⋅ Insérer image | illustrations & captures d'écran < ⋅ >

Hors ligne

#37 Le 18/12/2021, à 21:35

geole

Re : Erreurs dans dmesg : de quoi dois-je m'inquiéter ?

A tenter.
Ecrire des zéros dans le secteur zéro.

sudo dd if=/dev/zero  of=/dev/sda count=1

En espérant qu'il remplace le secteur zero par un autre.
Sinon on utilisera les grands moyens. 

sudo hdparm --yes-i-know-what-i-am-doing --write-sector 0 /dev/sda

Puis lancer testdisk afin qu'il recherche les partitions et refabrique la table de partition

Dernière modification par geole (Le 18/12/2021, à 21:41)

Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit,  utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir  https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248

Hors ligne

Pages : 1 2