Twitter iPhone pliant OnePlus 11 PS5 Disney+ Orange Livebox Windows 11

Machine plantée aide lecture log

1 réponse
Avatar
Droopy191
Salut,

Mon Thecus N2100 est planté suite à une coupure de courant brutale.
J'ai accès aux messages du noyau par une console série.

Voila ce que ca donne après la détection matériel.
Mais je ne sais pas vraiment interpréter ce que cela signifie.
Problème de fs ou c'est le disque qui a pris un coup ?
Merci pour votre aide.



[42949393.430000] EXT3-fs: mounted filesystem with ordered data mode.
Begin: Running /scripts/local-bottom ... done.
done.
Begin: Running /scripts/init-bottom ... done.
INIT: version 2.86 booting
[42949936.750000] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[42949936.760000] ata1.00: BMDMA2 stat 0x80c2209
[42949936.760000] ata1.00: cmd c8/00:08:3d:79:a1/00:00:00:00:00/eb tag 0
dma 40n
[42949936.760000] res 51/40:00:3d:79:a1/00:00:00:00:00/eb Emask
0x9 (m)
[42949936.780000] ata1.00: status: { DRDY ERR }
[42949936.780000] ata1.00: error: { UNC }
[42949936.850000] ata1.00: configured for UDMA/100
[42949936.850000] ata1: EH complete
[42949937.950000] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[42949937.960000] ata1.00: BMDMA2 stat 0x80c2209
[42949937.960000] ata1.00: cmd c8/00:08:3d:79:a1/00:00:00:00:00/eb tag 0
dma 40n
[42949937.960000] res 51/40:00:3d:79:a1/00:00:00:00:00/eb Emask
0x9 (m)
[42949937.980000] ata1.00: status: { DRDY ERR }
[42949937.980000] ata1.00: error: { UNC }
[42949938.050000] ata1.00: configured for UDMA/100
[42949938.050000] ata1: EH complete
[42949939.380000] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[42949939.380000] ata1.00: BMDMA2 stat 0x80c2209
[42949939.390000] ata1.00: cmd c8/00:08:3d:79:a1/00:00:00:00:00/eb tag 0
dma 40n
[42949939.390000] res 51/40:00:3d:79:a1/00:00:00:00:00/eb Emask
0x9 (m)
[42949939.410000] ata1.00: status: { DRDY ERR }
[42949939.410000] ata1.00: error: { UNC }
[42949939.470000] ata1.00: configured for UDMA/100
[42949939.470000] ata1: EH complete
[42949941.990000] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[42949942.010000] ata1.00: BMDMA2 stat 0x80c2209
[42949942.010000] ata1.00: cmd c8/00:08:3d:79:a1/00:00:00:00:00/eb tag 0
dma 40n
[42949942.010000] res 51/40:00:3d:79:a1/00:00:00:00:00/eb Emask
0x9 (m)
[42949942.030000] ata1.00: status: { DRDY ERR }
[42949942.030000] ata1.00: error: { UNC }
[42949942.090000] ata1.00: configured for UDMA/100
[42949942.090000] ata1: EH complete
[42949943.320000] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[42949943.320000] ata1.00: BMDMA2 stat 0x80c2209
[42949943.340000] ata1.00: cmd c8/00:08:3d:79:a1/00:00:00:00:00/eb tag 0
dma 40n
[42949943.340000] res 51/40:00:3d:79:a1/00:00:00:00:00/eb Emask
0x9 (m)
[42949943.350000] ata1.00: status: { DRDY ERR }
[42949943.350000] ata1.00: error: { UNC }
[42949943.410000] ata1.00: configured for UDMA/100
[42949943.410000] ata1: EH complete
[42949944.730000] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[42949944.750000] ata1.00: BMDMA2 stat 0x80c2209
[42949944.750000] ata1.00: cmd c8/00:08:3d:79:a1/00:00:00:00:00/eb tag 0
dma 40n
[42949944.750000] res 51/40:00:3d:79:a1/00:00:00:00:00/eb Emask
0x9 (m)
[42949944.770000] ata1.00: status: { DRDY ERR }
[42949944.770000] ata1.00: error: { UNC }
[42949944.840000] ata1.00: configured for UDMA/100
[42949944.840000] sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
[42949944.850000] sd 0:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor]
[42949944.850000] Descriptor sense data with sense descriptors (in hex):
[42949944.870000] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[42949944.870000] 0b a1 79 3d
[42949944.870000] sd 0:0:0:0: [sda] ASC=0x11 ASCQ=0x4
[42949944.880000] end_request: I/O error, dev sda, sector 195131709
[42949944.880000] ata1: EH complete
[42949944.890000] sd 0:0:0:0: [sda] Write Protect is off
[42949944.890000] EXT3-fs error (device sda3): ext3_get_inode_loc:
unable to re8



--
DR

1 réponse

Avatar
droopy191
Droopy191 wrote:
Salut,

Mon Thecus N2100 est planté suite à une coupure de courant brutale.
J'ai accès aux messages du noyau par une console série.

Voila ce que ca donne après la détection matériel.
Mais je ne sais pas vraiment interpréter ce que cela signifie.
Problème de fs ou c'est le disque qui a pris un coup ?



Bon, rien a faire avec badblocks ou fsck
un formatage par outil constructeur semble avoir résolu le pb.


--
DR