Sie sind nicht angemeldet.

[erledigt] Xubuntu verschlampt seine Partitionen | völlig verrückter Fehler

Lieber Besucher, herzlich willkommen bei: Ubuntu-Forum & Kubuntu-Forum | www.Ubuntu-Forum.de. Falls dies Ihr erster Besuch auf dieser Seite ist, lesen Sie sich bitte die Hilfe durch. Dort wird Ihnen die Bedienung dieser Seite näher erläutert. Darüber hinaus sollten Sie sich registrieren, um alle Funktionen dieser Seite nutzen zu können. Benutzen Sie das Registrierungsformular, um sich zu registrieren oder informieren Sie sich ausführlich über den Registrierungsvorgang. Falls Sie sich bereits zu einem früheren Zeitpunkt registriert haben, können Sie sich hier anmelden.

  • 1
  • 2

Fredl

Ubuntu-Forum-Team

Beiträge: 11 331

  • Nachricht senden

21

23.12.2016, 22:32

Der auffällige Wert hat sich in den zwei Tagen zumindest nicht weiter verschlechtert.
Daß der Test bei 90% hängt, erscheint mir merkwürdig. Daß ein aktueller Wert niedriger ist als ein WORST obwohl er das beim vorhergehenden Test auch schon war, ebenfalls.

Mehr kann ich nicht sagen. Was du mit der Platte machst, kannst nur du selbst entscheiden.
Beim Erstellen dieser Nachricht kamen keine Tiere zu Schaden.
me is all sausage
but don't call me Ferdl

ebbi97a

User

  • »ebbi97a« ist männlich
  • »ebbi97a« ist der Autor dieses Themas

Beiträge: 181

Registrierungsdatum: 28.11.2005

Derivat: Xubuntu

Version: Ubuntu 18.04 LTS - Bionic Beaver

Architektur: 64-Bit PC

Desktop: XFCE

Andere Betriebssysteme: Debian, Devuan, Mint, Manjaro, MacOS X, Android, Windows 7

  • Nachricht senden

22

31.01.2017, 12:14

Stunde der Wahrheit?

Jetzt bin ich aus Westafrika zurück und habe das heile System gestartet, welches die kritische Platte überhaupt nicht verwendet. Nach wenigen Minuten Betrieb bekam ich bereits ein Warnfenster präsentiert, welches scheinbar Klartext spricht: der Gesundheitsstatus der Platte hat sich verändert. Trotzdem findet der kurze SMART-Test weiterhin 0 Fehler. Das ganze irritiert mich sehr stark. Ich werde den Rechner mal aufschrauben und die Kabel überprüfen weil ich mich erinnere, daß ich beim Einbau mit einem kurzen Kabel Schwierigkeiten hatte und das Kabel unter leichter Spannung stand. Außerdem war es falsch gekröpft, so daß ich den Stecker kaum im Sockel befestigen konnte. Vielleich ist alles doch anders, als es scheint.
»ebbi97a« hat folgendes Bild angehängt:
  • Bildschirmfoto vom 2017-01-31 09-23-32-.png
_______________________________
Welches System hätten's denn gern?

Fredl

Ubuntu-Forum-Team

Beiträge: 11 331

  • Nachricht senden

23

31.01.2017, 14:06

"For details see syslog" ...
Leere Zeile
Beim Erstellen dieser Nachricht kamen keine Tiere zu Schaden.
me is all sausage
but don't call me Ferdl

ebbi97a

User

  • »ebbi97a« ist männlich
  • »ebbi97a« ist der Autor dieses Themas

Beiträge: 181

Registrierungsdatum: 28.11.2005

Derivat: Xubuntu

Version: Ubuntu 18.04 LTS - Bionic Beaver

Architektur: 64-Bit PC

Desktop: XFCE

Andere Betriebssysteme: Debian, Devuan, Mint, Manjaro, MacOS X, Android, Windows 7

  • Nachricht senden

24

31.01.2017, 18:54

Es werden Fehler im ext-4-Dateisystem gefunden. Hier folgt der gesamte syslog-Abschnitt vom Kaltstart bis zum Sitzungswechsel und späterem Neustart (Warmstart):

Quellcode

 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404

Jan 31 09:47:46 i5tuxedo anacron[1098]: Job `cron.daily' terminated (mailing output)
Jan 31 09:47:46 i5tuxedo anacron[1098]: Can't find sendmail at /usr/sbin/sendmail, not mailing output
Jan 31 09:47:46 i5tuxedo anacron[1098]: anacron: Can't find sendmail at /usr/sbin/sendmail, not mailing output
Jan 31 09:48:18 i5tuxedo ntpd[1628]: Soliciting pool server 2001:67c:1560:8003::c7
Jan 31 09:48:25 i5tuxedo kernel: [  361.881439] ata4: limiting SATA link speed to 3.0 Gbps
Jan 31 09:48:25 i5tuxedo kernel: [  361.881449] ata4.00: exception Emask 0x10 SAct 0x1fe0000 SErr 0x400100 action 0x6 frozen
Jan 31 09:48:25 i5tuxedo kernel: [  361.881453] ata4.00: irq_stat 0x08000000, interface fatal error
Jan 31 09:48:25 i5tuxedo kernel: [  361.881458] ata4: SError: { UnrecovData Handshk }
Jan 31 09:48:25 i5tuxedo kernel: [  361.881463] ata4.00: failed command: WRITE FPDMA QUEUED
Jan 31 09:48:25 i5tuxedo kernel: [  361.881472] ata4.00: cmd 61/10:88:40:30:64/01:00:29:00:00/40 tag 17 ncq 139264 out
Jan 31 09:48:25 i5tuxedo kernel: [  361.881472]          res 40/00:c4:00:fe:65/00:00:29:00:00/40 Emask 0x10 (ATA bus error)
Jan 31 09:48:25 i5tuxedo kernel: [  361.881477] ata4.00: status: { DRDY }
Jan 31 09:48:25 i5tuxedo kernel: [  361.881480] ata4.00: failed command: WRITE FPDMA QUEUED
Jan 31 09:48:25 i5tuxedo kernel: [  361.881488] ata4.00: cmd 61/28:90:10:3d:64/03:00:29:00:00/40 tag 18 ncq 413696 out
Jan 31 09:48:25 i5tuxedo kernel: [  361.881488]          res 40/00:c4:00:fe:65/00:00:29:00:00/40 Emask 0x10 (ATA bus error)
Jan 31 09:48:25 i5tuxedo kernel: [  361.881491] ata4.00: status: { DRDY }
Jan 31 09:48:25 i5tuxedo kernel: [  361.881495] ata4.00: failed command: WRITE FPDMA QUEUED
Jan 31 09:48:25 i5tuxedo kernel: [  361.881502] ata4.00: cmd 61/40:98:40:40:64/00:00:29:00:00/40 tag 19 ncq 32768 out
Jan 31 09:48:25 i5tuxedo kernel: [  361.881502]          res 40/00:c4:00:fe:65/00:00:29:00:00/40 Emask 0x10 (ATA bus error)
Jan 31 09:48:25 i5tuxedo kernel: [  361.881505] ata4.00: status: { DRDY }
Jan 31 09:48:25 i5tuxedo kernel: [  361.881508] ata4.00: failed command: WRITE FPDMA QUEUED
Jan 31 09:48:25 i5tuxedo kernel: [  361.881515] ata4.00: cmd 61/40:a0:00:e1:65/00:00:29:00:00/40 tag 20 ncq 32768 out
Jan 31 09:48:25 i5tuxedo kernel: [  361.881515]          res 40/00:c4:00:fe:65/00:00:29:00:00/40 Emask 0x10 (ATA bus error)
Jan 31 09:48:25 i5tuxedo kernel: [  361.881519] ata4.00: status: { DRDY }
Jan 31 09:48:25 i5tuxedo kernel: [  361.881522] ata4.00: failed command: WRITE FPDMA QUEUED
Jan 31 09:48:25 i5tuxedo kernel: [  361.881529] ata4.00: cmd 61/40:a8:00:e7:65/00:00:29:00:00/40 tag 21 ncq 32768 out
Jan 31 09:48:25 i5tuxedo kernel: [  361.881529]          res 40/00:c4:00:fe:65/00:00:29:00:00/40 Emask 0x10 (ATA bus error)
Jan 31 09:48:25 i5tuxedo kernel: [  361.881532] ata4.00: status: { DRDY }
Jan 31 09:48:25 i5tuxedo kernel: [  361.881535] ata4.00: failed command: WRITE FPDMA QUEUED
Jan 31 09:48:25 i5tuxedo kernel: [  361.881542] ata4.00: cmd 61/40:b0:c0:f6:65/00:00:29:00:00/40 tag 22 ncq 32768 out
Jan 31 09:48:25 i5tuxedo kernel: [  361.881542]          res 40/00:c4:00:fe:65/00:00:29:00:00/40 Emask 0x10 (ATA bus error)
Jan 31 09:48:25 i5tuxedo kernel: [  361.881546] ata4.00: status: { DRDY }
Jan 31 09:48:25 i5tuxedo kernel: [  361.881548] ata4.00: failed command: WRITE FPDMA QUEUED
Jan 31 09:48:25 i5tuxedo kernel: [  361.881555] ata4.00: cmd 61/40:b8:80:fc:65/00:00:29:00:00/40 tag 23 ncq 32768 out
Jan 31 09:48:25 i5tuxedo kernel: [  361.881555]          res 40/00:c4:00:fe:65/00:00:29:00:00/40 Emask 0x10 (ATA bus error)
Jan 31 09:48:25 i5tuxedo kernel: [  361.881559] ata4.00: status: { DRDY }
Jan 31 09:48:25 i5tuxedo kernel: [  361.881562] ata4.00: failed command: WRITE FPDMA QUEUED
Jan 31 09:48:25 i5tuxedo kernel: [  361.881569] ata4.00: cmd 61/40:c0:00:fe:65/00:00:29:00:00/40 tag 24 ncq 32768 out
Jan 31 09:48:25 i5tuxedo kernel: [  361.881569]          res 40/00:c4:00:fe:65/00:00:29:00:00/40 Emask 0x10 (ATA bus error)
Jan 31 09:48:25 i5tuxedo kernel: [  361.881572] ata4.00: status: { DRDY }
Jan 31 09:48:25 i5tuxedo kernel: [  361.881578] ata4: hard resetting link
Jan 31 09:48:25 i5tuxedo kernel: [  362.201337] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
Jan 31 09:48:25 i5tuxedo kernel: [  362.202939] ata4.00: configured for UDMA/133
Jan 31 09:48:25 i5tuxedo kernel: [  362.202956] ata4: EH complete
Jan 31 09:48:25 i5tuxedo kernel: [  362.209378] ata4.00: exception Emask 0x10 SAct 0x70000007 SErr 0x400100 action 0x6 frozen
Jan 31 09:48:25 i5tuxedo kernel: [  362.209382] ata4.00: irq_stat 0x08000000, interface fatal error
Jan 31 09:48:25 i5tuxedo kernel: [  362.209385] ata4: SError: { UnrecovData Handshk }
Jan 31 09:48:25 i5tuxedo kernel: [  362.209388] ata4.00: failed command: WRITE FPDMA QUEUED
Jan 31 09:48:25 i5tuxedo kernel: [  362.209393] ata4.00: cmd 61/40:00:40:40:64/00:00:29:00:00/40 tag 0 ncq 32768 out
Jan 31 09:48:25 i5tuxedo kernel: [  362.209393]          res 40/00:14:40:30:64/00:00:29:00:00/40 Emask 0x10 (ATA bus error)
Jan 31 09:48:25 i5tuxedo kernel: [  362.209396] ata4.00: status: { DRDY }
Jan 31 09:48:25 i5tuxedo kernel: [  362.209398] ata4.00: failed command: WRITE FPDMA QUEUED
Jan 31 09:48:25 i5tuxedo kernel: [  362.209402] ata4.00: cmd 61/28:08:10:3d:64/03:00:29:00:00/40 tag 1 ncq 413696 out
Jan 31 09:48:25 i5tuxedo kernel: [  362.209402]          res 40/00:14:40:30:64/00:00:29:00:00/40 Emask 0x10 (ATA bus error)
Jan 31 09:48:25 i5tuxedo kernel: [  362.209405] ata4.00: status: { DRDY }
Jan 31 09:48:25 i5tuxedo kernel: [  362.209406] ata4.00: failed command: WRITE FPDMA QUEUED
Jan 31 09:48:25 i5tuxedo kernel: [  362.209411] ata4.00: cmd 61/10:10:40:30:64/01:00:29:00:00/40 tag 2 ncq 139264 out
Jan 31 09:48:25 i5tuxedo kernel: [  362.209411]          res 40/00:14:40:30:64/00:00:29:00:00/40 Emask 0x10 (ATA bus error)
Jan 31 09:48:25 i5tuxedo kernel: [  362.209413] ata4.00: status: { DRDY }
Jan 31 09:48:25 i5tuxedo kernel: [  362.209415] ata4.00: failed command: WRITE FPDMA QUEUED
Jan 31 09:48:25 i5tuxedo kernel: [  362.209420] ata4.00: cmd 61/40:e0:c0:f6:65/00:00:29:00:00/40 tag 28 ncq 32768 out
Jan 31 09:48:25 i5tuxedo kernel: [  362.209420]          res 40/00:14:40:30:64/00:00:29:00:00/40 Emask 0x10 (ATA bus error)
Jan 31 09:48:25 i5tuxedo kernel: [  362.209422] ata4.00: status: { DRDY }
Jan 31 09:48:25 i5tuxedo kernel: [  362.209424] ata4.00: failed command: WRITE FPDMA QUEUED
Jan 31 09:48:25 i5tuxedo kernel: [  362.209428] ata4.00: cmd 61/40:e8:00:e7:65/00:00:29:00:00/40 tag 29 ncq 32768 out
Jan 31 09:48:25 i5tuxedo kernel: [  362.209428]          res 40/00:14:40:30:64/00:00:29:00:00/40 Emask 0x10 (ATA bus error)
Jan 31 09:48:25 i5tuxedo kernel: [  362.209430] ata4.00: status: { DRDY }
Jan 31 09:48:25 i5tuxedo kernel: [  362.209432] ata4.00: failed command: WRITE FPDMA QUEUED
Jan 31 09:48:25 i5tuxedo kernel: [  362.209436] ata4.00: cmd 61/40:f0:00:e1:65/00:00:29:00:00/40 tag 30 ncq 32768 out
Jan 31 09:48:25 i5tuxedo kernel: [  362.209436]          res 40/00:14:40:30:64/00:00:29:00:00/40 Emask 0x10 (ATA bus error)
Jan 31 09:48:25 i5tuxedo kernel: [  362.209438] ata4.00: status: { DRDY }
Jan 31 09:48:25 i5tuxedo kernel: [  362.209441] ata4: hard resetting link
Jan 31 09:48:26 i5tuxedo kernel: [  362.529341] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
Jan 31 09:48:26 i5tuxedo kernel: [  362.530749] ata4.00: configured for UDMA/133
Jan 31 09:48:26 i5tuxedo kernel: [  362.530785] ata4: EH complete
Jan 31 09:48:26 i5tuxedo kernel: [  362.537407] ata4.00: exception Emask 0x10 SAct 0x70000 SErr 0x400100 action 0x6 frozen
Jan 31 09:48:26 i5tuxedo kernel: [  362.537409] ata4.00: irq_stat 0x08000000, interface fatal error
Jan 31 09:48:26 i5tuxedo kernel: [  362.537410] ata4: SError: { UnrecovData Handshk }
Jan 31 09:48:26 i5tuxedo kernel: [  362.537411] ata4.00: failed command: WRITE FPDMA QUEUED
Jan 31 09:48:26 i5tuxedo kernel: [  362.537414] ata4.00: cmd 61/10:80:40:30:64/01:00:29:00:00/40 tag 16 ncq 139264 out
Jan 31 09:48:26 i5tuxedo kernel: [  362.537414]          res 40/00:94:40:40:64/00:00:29:00:00/40 Emask 0x10 (ATA bus error)
Jan 31 09:48:26 i5tuxedo kernel: [  362.537415] ata4.00: status: { DRDY }
Jan 31 09:48:26 i5tuxedo kernel: [  362.537416] ata4.00: failed command: WRITE FPDMA QUEUED
Jan 31 09:48:26 i5tuxedo kernel: [  362.537418] ata4.00: cmd 61/28:88:10:3d:64/03:00:29:00:00/40 tag 17 ncq 413696 out
Jan 31 09:48:26 i5tuxedo kernel: [  362.537418]          res 40/00:94:40:40:64/00:00:29:00:00/40 Emask 0x10 (ATA bus error)
Jan 31 09:48:26 i5tuxedo kernel: [  362.537419] ata4.00: status: { DRDY }
Jan 31 09:48:26 i5tuxedo kernel: [  362.537420] ata4.00: failed command: WRITE FPDMA QUEUED
Jan 31 09:48:26 i5tuxedo kernel: [  362.537422] ata4.00: cmd 61/40:90:40:40:64/00:00:29:00:00/40 tag 18 ncq 32768 out
Jan 31 09:48:26 i5tuxedo kernel: [  362.537422]          res 40/00:94:40:40:64/00:00:29:00:00/40 Emask 0x10 (ATA bus error)
Jan 31 09:48:26 i5tuxedo kernel: [  362.537423] ata4.00: status: { DRDY }
Jan 31 09:48:26 i5tuxedo kernel: [  362.537425] ata4: hard resetting link
Jan 31 09:48:26 i5tuxedo kernel: [  362.857325] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
Jan 31 09:48:26 i5tuxedo kernel: [  362.858665] ata4.00: configured for UDMA/133
Jan 31 09:48:26 i5tuxedo kernel: [  362.858671] ata4: EH complete
Jan 31 09:48:26 i5tuxedo kernel: [  362.865334] ata4.00: exception Emask 0x10 SAct 0x40000001 SErr 0x400100 action 0x6 frozen
Jan 31 09:48:26 i5tuxedo kernel: [  362.865346] ata4.00: irq_stat 0x08000000, interface fatal error
Jan 31 09:48:26 i5tuxedo kernel: [  362.865347] ata4: SError: { UnrecovData Handshk }
Jan 31 09:48:26 i5tuxedo kernel: [  362.865348] ata4.00: failed command: WRITE FPDMA QUEUED
Jan 31 09:48:26 i5tuxedo kernel: [  362.865351] ata4.00: cmd 61/10:00:40:30:64/01:00:29:00:00/40 tag 0 ncq 139264 out
Jan 31 09:48:26 i5tuxedo kernel: [  362.865351]          res 40/00:04:40:30:64/00:00:29:00:00/40 Emask 0x10 (ATA bus error)
Jan 31 09:48:26 i5tuxedo kernel: [  362.865352] ata4.00: status: { DRDY }
Jan 31 09:48:26 i5tuxedo kernel: [  362.865353] ata4.00: failed command: WRITE FPDMA QUEUED
Jan 31 09:48:26 i5tuxedo kernel: [  362.865365] ata4.00: cmd 61/28:f0:10:3d:64/03:00:29:00:00/40 tag 30 ncq 413696 out
Jan 31 09:48:26 i5tuxedo kernel: [  362.865365]          res 40/00:04:40:30:64/00:00:29:00:00/40 Emask 0x10 (ATA bus error)
Jan 31 09:48:26 i5tuxedo kernel: [  362.865366] ata4.00: status: { DRDY }
Jan 31 09:48:26 i5tuxedo kernel: [  362.865367] ata4: hard resetting link
Jan 31 09:48:26 i5tuxedo kernel: [  363.185358] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
Jan 31 09:48:26 i5tuxedo kernel: [  363.186755] ata4.00: configured for UDMA/133
Jan 31 09:48:26 i5tuxedo kernel: [  363.186768] ata4: EH complete
Jan 31 09:48:26 i5tuxedo kernel: [  363.193400] ata4: limiting SATA link speed to 1.5 Gbps
Jan 31 09:48:26 i5tuxedo kernel: [  363.193406] ata4.00: exception Emask 0x10 SAct 0x1800 SErr 0x400100 action 0x6 frozen
Jan 31 09:48:26 i5tuxedo kernel: [  363.193409] ata4.00: irq_stat 0x08000000, interface fatal error
Jan 31 09:48:26 i5tuxedo kernel: [  363.193412] ata4: SError: { UnrecovData Handshk }
Jan 31 09:48:26 i5tuxedo kernel: [  363.193416] ata4.00: failed command: WRITE FPDMA QUEUED
Jan 31 09:48:26 i5tuxedo kernel: [  363.193422] ata4.00: cmd 61/28:58:10:3d:64/03:00:29:00:00/40 tag 11 ncq 413696 out
Jan 31 09:48:26 i5tuxedo kernel: [  363.193422]          res 40/00:64:40:30:64/00:00:29:00:00/40 Emask 0x10 (ATA bus error)
Jan 31 09:48:26 i5tuxedo kernel: [  363.193425] ata4.00: status: { DRDY }
Jan 31 09:48:26 i5tuxedo kernel: [  363.193427] ata4.00: failed command: WRITE FPDMA QUEUED
Jan 31 09:48:26 i5tuxedo kernel: [  363.193432] ata4.00: cmd 61/10:60:40:30:64/01:00:29:00:00/40 tag 12 ncq 139264 out
Jan 31 09:48:26 i5tuxedo kernel: [  363.193432]          res 40/00:64:40:30:64/00:00:29:00:00/40 Emask 0x10 (ATA bus error)
Jan 31 09:48:26 i5tuxedo kernel: [  363.193435] ata4.00: status: { DRDY }
Jan 31 09:48:26 i5tuxedo kernel: [  363.193439] ata4: hard resetting link
Jan 31 09:48:29 i5tuxedo kernel: [  365.409357] ata4: SATA link down (SStatus 1 SControl 310)
Jan 31 09:48:29 i5tuxedo kernel: [  365.414173] ata4: hard resetting link
Jan 31 09:48:31 i5tuxedo kernel: [  367.629364] ata4: SATA link down (SStatus 1 SControl 310)
Jan 31 09:48:31 i5tuxedo kernel: [  367.634186] ata4: hard resetting link
Jan 31 09:48:33 i5tuxedo kernel: [  369.849385] ata4: SATA link down (SStatus 1 SControl 310)
Jan 31 09:48:33 i5tuxedo kernel: [  369.849389] ata4.00: disabled
Jan 31 09:48:33 i5tuxedo kernel: [  369.849402] sd 3:0:0:0: [sdb] tag#11 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 31 09:48:33 i5tuxedo kernel: [  369.849403] sd 3:0:0:0: [sdb] tag#11 Sense Key : Illegal Request [current] [descriptor] 
Jan 31 09:48:33 i5tuxedo kernel: [  369.849405] sd 3:0:0:0: [sdb] tag#11 Add. Sense: Unaligned write command
Jan 31 09:48:33 i5tuxedo kernel: [  369.849407] sd 3:0:0:0: [sdb] tag#11 CDB: Write(16) 8a 00 00 00 00 00 29 64 3d 10 00 00 03 28 00 00
Jan 31 09:48:33 i5tuxedo kernel: [  369.849408] blk_update_request: I/O error, dev sdb, sector 694435088
Jan 31 09:48:33 i5tuxedo kernel: [  369.849410] EXT4-fs warning (device sdb1): ext4_end_bio:329: I/O error -5 writing to inode 21648147 (offset 0 size 24576 starting block 86804392)
Jan 31 09:48:33 i5tuxedo kernel: [  369.849412] Buffer I/O error on device sdb1, logical block 86804130
Jan 31 09:48:33 i5tuxedo kernel: [  369.849414] Buffer I/O error on device sdb1, logical block 86804131
Jan 31 09:48:33 i5tuxedo kernel: [  369.849415] Buffer I/O error on device sdb1, logical block 86804132
Jan 31 09:48:33 i5tuxedo kernel: [  369.849416] Buffer I/O error on device sdb1, logical block 86804133
Jan 31 09:48:33 i5tuxedo kernel: [  369.849417] Buffer I/O error on device sdb1, logical block 86804134
Jan 31 09:48:33 i5tuxedo kernel: [  369.849417] Buffer I/O error on device sdb1, logical block 86804135
Jan 31 09:48:33 i5tuxedo kernel: [  369.849420] EXT4-fs warning (device sdb1): ext4_end_bio:329: I/O error -5 writing to inode 21648148 (offset 0 size 24576 starting block 86804398)
Jan 31 09:48:33 i5tuxedo kernel: [  369.849421] Buffer I/O error on device sdb1, logical block 86804136
Jan 31 09:48:33 i5tuxedo kernel: [  369.849422] Buffer I/O error on device sdb1, logical block 86804137
Jan 31 09:48:33 i5tuxedo kernel: [  369.849422] Buffer I/O error on device sdb1, logical block 86804138
Jan 31 09:48:33 i5tuxedo kernel: [  369.849423] Buffer I/O error on device sdb1, logical block 86804139
Jan 31 09:48:33 i5tuxedo kernel: [  369.849425] EXT4-fs warning (device sdb1): ext4_end_bio:329: I/O error -5 writing to inode 21648149 (offset 0 size 20480 starting block 86804403)
Jan 31 09:48:33 i5tuxedo kernel: [  369.849427] EXT4-fs warning (device sdb1): ext4_end_bio:329: I/O error -5 writing to inode 21648150 (offset 0 size 24576 starting block 86804409)
Jan 31 09:48:33 i5tuxedo kernel: [  369.849430] EXT4-fs warning (device sdb1): ext4_end_bio:329: I/O error -5 writing to inode 21648151 (offset 0 size 24576 starting block 86804415)
Jan 31 09:48:33 i5tuxedo kernel: [  369.849433] EXT4-fs warning (device sdb1): ext4_end_bio:329: I/O error -5 writing to inode 21648152 (offset 0 size 24576 starting block 86804421)
Jan 31 09:48:33 i5tuxedo kernel: [  369.849435] EXT4-fs warning (device sdb1): ext4_end_bio:329: I/O error -5 writing to inode 21648153 (offset 0 size 24576 starting block 86804427)
Jan 31 09:48:33 i5tuxedo kernel: [  369.849438] EXT4-fs warning (device sdb1): ext4_end_bio:329: I/O error -5 writing to inode 21648154 (offset 0 size 28672 starting block 86804434)
Jan 31 09:48:33 i5tuxedo kernel: [  369.849441] EXT4-fs warning (device sdb1): ext4_end_bio:329: I/O error -5 writing to inode 21648155 (offset 0 size 28672 starting block 86804441)
Jan 31 09:48:33 i5tuxedo kernel: [  369.849444] EXT4-fs warning (device sdb1): ext4_end_bio:329: I/O error -5 writing to inode 21648157 (offset 0 size 24576 starting block 86804447)
Jan 31 09:48:33 i5tuxedo kernel: [  369.849462] sd 3:0:0:0: rejecting I/O to offline device
Jan 31 09:48:33 i5tuxedo kernel: [  369.849463] sd 3:0:0:0: [sdb] killing request
Jan 31 09:48:33 i5tuxedo kernel: [  369.849465] sd 3:0:0:0: rejecting I/O to offline device
Jan 31 09:48:33 i5tuxedo kernel: [  369.849469] sd 3:0:0:0: [sdb] tag#12 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 31 09:48:33 i5tuxedo kernel: [  369.849470] sd 3:0:0:0: [sdb] tag#12 Sense Key : Illegal Request [current] [descriptor] 
Jan 31 09:48:33 i5tuxedo kernel: [  369.849471] sd 3:0:0:0: [sdb] tag#12 Add. Sense: Unaligned write command
Jan 31 09:48:33 i5tuxedo kernel: [  369.849473] sd 3:0:0:0: [sdb] tag#12 CDB: Write(16) 8a 00 00 00 00 00 29 64 30 40 00 00 01 10 00 00
Jan 31 09:48:33 i5tuxedo kernel: [  369.849473] blk_update_request: I/O error, dev sdb, sector 694431808
Jan 31 09:48:33 i5tuxedo kernel: [  369.849486] sd 3:0:0:0: rejecting I/O to offline device
Jan 31 09:48:33 i5tuxedo kernel: [  369.849491] ata4: EH complete
Jan 31 09:48:33 i5tuxedo kernel: [  369.849495] sd 3:0:0:0: [sdb] FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Jan 31 09:48:33 i5tuxedo kernel: [  369.849496] sd 3:0:0:0: [sdb] CDB: Write(16) 8a 00 00 00 00 00 36 04 29 88 00 00 00 30 00 00
Jan 31 09:48:33 i5tuxedo kernel: [  369.849497] blk_update_request: I/O error, dev sdb, sector 906242440
Jan 31 09:48:33 i5tuxedo kernel: [  369.849502] ata4.00: detaching (SCSI 3:0:0:0)
Jan 31 09:48:33 i5tuxedo kernel: [  369.849520] Aborting journal on device sdb1-8.
Jan 31 09:48:33 i5tuxedo kernel: [  369.849526] JBD2: Error -5 detected when updating journal superblock for sdb1-8.
Jan 31 09:48:33 i5tuxedo kernel: [  369.852178] blk_update_request: I/O error, dev sdb, sector 0
Jan 31 09:48:33 i5tuxedo systemd[1]: Stopped target Swap.
Jan 31 09:48:33 i5tuxedo kernel: [  369.853530] ata4: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen
Jan 31 09:48:33 i5tuxedo kernel: [  369.853532] ata4: irq_stat 0x00000040, connection status changed
Jan 31 09:48:33 i5tuxedo kernel: [  369.853533] ata4: SError: { CommWake DevExch }
Jan 31 09:48:33 i5tuxedo kernel: [  369.853536] ata4: hard resetting link
Jan 31 09:48:33 i5tuxedo kernel: [  369.854647] sd 3:0:0:0: [sdb] Synchronizing SCSI cache
Jan 31 09:48:33 i5tuxedo systemd[1]: Deactivating swap /dev/disk/by-uuid/a40c36ec-d0b9-4888-be30-bacb69741931...
Jan 31 09:48:33 i5tuxedo systemd[1]: Stopped target Local File Systems.
Jan 31 09:48:33 i5tuxedo systemd[1]: Unmounting /home...
Jan 31 09:48:33 i5tuxedo umount[2613]: umount: /home: target is busy
Jan 31 09:48:33 i5tuxedo umount[2613]:         (In some cases useful info about processes that
Jan 31 09:48:33 i5tuxedo umount[2613]:          use the device is found by lsof(8) or fuser(1).)
Jan 31 09:48:33 i5tuxedo systemd[1]: home.mount: Mount process exited, code=exited status=32
Jan 31 09:48:33 i5tuxedo swapoff[2610]: swapoff: /dev/disk/by-uuid/a40c36ec-d0b9-4888-be30-bacb69741931: swapoff fehlgeschlagen: Datei oder Verzeichnis nicht gefunden
Jan 31 09:48:33 i5tuxedo systemd[1]: Failed unmounting /home.
Jan 31 09:48:33 i5tuxedo systemd[1]: home.mount: Unit is bound to inactive unit dev-disk-by\x2duuid-948157c2\x2d855b\x2d47b4\x2db084\x2d5eca13d5861e.device. Stopping, too.
Jan 31 09:48:33 i5tuxedo systemd[1]: dev-disk-by\x2duuid-a40c36ec\x2dd0b9\x2d4888\x2dbe30\x2dbacb69741931.swap: Swap process exited, code=exited status=255
Jan 31 09:48:33 i5tuxedo systemd[1]: Deactivated swap /dev/disk/by-uuid/a40c36ec-d0b9-4888-be30-bacb69741931.
Jan 31 09:48:33 i5tuxedo systemd[1]: dev-disk-by\x2duuid-a40c36ec\x2dd0b9\x2d4888\x2dbe30\x2dbacb69741931.swap: Unit entered failed state.
Jan 31 09:48:33 i5tuxedo systemd[1]: Unmounting /home...
Jan 31 09:48:33 i5tuxedo umount[2617]: umount: /home: target is busy
Jan 31 09:48:33 i5tuxedo umount[2617]:         (In some cases useful info about processes that
Jan 31 09:48:33 i5tuxedo umount[2617]:          use the device is found by lsof(8) or fuser(1).)
Jan 31 09:48:33 i5tuxedo systemd[1]: home.mount: Mount process exited, code=exited status=32
Jan 31 09:48:33 i5tuxedo systemd[1]: Failed unmounting /home.
Jan 31 09:48:33 i5tuxedo systemd[1]: home.mount: Unit is bound to inactive unit dev-disk-by\x2duuid-948157c2\x2d855b\x2d47b4\x2db084\x2d5eca13d5861e.device. Stopping, too.
Jan 31 09:48:33 i5tuxedo systemd[1]: Unmounting /home...
Jan 31 09:48:33 i5tuxedo umount[2622]: umount: /home: target is busy
Jan 31 09:48:33 i5tuxedo umount[2622]:         (In some cases useful info about processes that
Jan 31 09:48:33 i5tuxedo umount[2622]:          use the device is found by lsof(8) or fuser(1).)
Jan 31 09:48:33 i5tuxedo systemd[1]: home.mount: Mount process exited, code=exited status=32
Jan 31 09:48:33 i5tuxedo systemd[1]: Failed unmounting /home.
Jan 31 09:48:33 i5tuxedo systemd[1]: home.mount: Unit is bound to inactive unit dev-disk-by\x2duuid-948157c2\x2d855b\x2d47b4\x2db084\x2d5eca13d5861e.device. Stopping, too.
Jan 31 09:48:33 i5tuxedo systemd[1]: Unmounting /home...
Jan 31 09:48:33 i5tuxedo umount[2625]: umount: /home: target is busy
Jan 31 09:48:33 i5tuxedo umount[2625]:         (In some cases useful info about processes that
Jan 31 09:48:33 i5tuxedo umount[2625]:          use the device is found by lsof(8) or fuser(1).)
Jan 31 09:48:33 i5tuxedo systemd[1]: home.mount: Mount process exited, code=exited status=32
Jan 31 09:48:33 i5tuxedo systemd[1]: Failed unmounting /home.
Jan 31 09:48:33 i5tuxedo systemd[1]: home.mount: Unit is bound to inactive unit dev-disk-by\x2duuid-948157c2\x2d855b\x2d47b4\x2db084\x2d5eca13d5861e.device. Stopping, too.
Jan 31 09:48:33 i5tuxedo systemd[1]: Unmounting /home...
Jan 31 09:48:33 i5tuxedo umount[2627]: umount: /home: target is busy
Jan 31 09:48:33 i5tuxedo umount[2627]:         (In some cases useful info about processes that
Jan 31 09:48:33 i5tuxedo umount[2627]:          use the device is found by lsof(8) or fuser(1).)
Jan 31 09:48:33 i5tuxedo systemd[1]: home.mount: Mount process exited, code=exited status=32
Jan 31 09:48:33 i5tuxedo systemd[1]: Failed unmounting /home.
Jan 31 09:48:33 i5tuxedo systemd[1]: home.mount: Unit is bound to inactive unit dev-disk-by\x2duuid-948157c2\x2d855b\x2d47b4\x2db084\x2d5eca13d5861e.device. Stopping, too.
Jan 31 09:48:33 i5tuxedo systemd[1]: Unmounting /home...
Jan 31 09:48:33 i5tuxedo umount[2630]: umount: /home: target is busy
Jan 31 09:48:33 i5tuxedo umount[2630]:         (In some cases useful info about processes that
Jan 31 09:48:33 i5tuxedo umount[2630]:          use the device is found by lsof(8) or fuser(1).)
Jan 31 09:48:33 i5tuxedo systemd[1]: home.mount: Mount process exited, code=exited status=32
Jan 31 09:48:33 i5tuxedo systemd[1]: Failed unmounting /home.
Jan 31 09:48:33 i5tuxedo systemd[1]: home.mount: Unit is bound to inactive unit dev-disk-by\x2duuid-948157c2\x2d855b\x2d47b4\x2db084\x2d5eca13d5861e.device. Stopping, too.
Jan 31 09:48:33 i5tuxedo systemd[1]: Unmounting /home...
Jan 31 09:48:33 i5tuxedo umount[2634]: umount: /home: target is busy
Jan 31 09:48:33 i5tuxedo umount[2634]:         (In some cases useful info about processes that
Jan 31 09:48:33 i5tuxedo umount[2634]:          use the device is found by lsof(8) or fuser(1).)
Jan 31 09:48:33 i5tuxedo systemd[1]: home.mount: Mount process exited, code=exited status=32
Jan 31 09:48:33 i5tuxedo systemd[1]: Failed unmounting /home.
Jan 31 09:48:33 i5tuxedo systemd[1]: home.mount: Unit is bound to inactive unit dev-disk-by\x2duuid-948157c2\x2d855b\x2d47b4\x2db084\x2d5eca13d5861e.device. Stopping, too.
Jan 31 09:48:33 i5tuxedo systemd[1]: Unmounting /home...
Jan 31 09:48:33 i5tuxedo umount[2637]: umount: /home: target is busy
Jan 31 09:48:33 i5tuxedo umount[2637]:         (In some cases useful info about processes that
Jan 31 09:48:33 i5tuxedo umount[2637]:          use the device is found by lsof(8) or fuser(1).)
Jan 31 09:48:33 i5tuxedo systemd[1]: home.mount: Mount process exited, code=exited status=32
Jan 31 09:48:33 i5tuxedo systemd[1]: Failed unmounting /home.
Jan 31 09:48:33 i5tuxedo systemd[1]: home.mount: Unit is bound to inactive unit dev-disk-by\x2duuid-948157c2\x2d855b\x2d47b4\x2db084\x2d5eca13d5861e.device. Stopping, too.
Jan 31 09:48:33 i5tuxedo systemd[1]: Unmounting /home...
Jan 31 09:48:33 i5tuxedo umount[2639]: umount: /home: target is busy
Jan 31 09:48:33 i5tuxedo umount[2639]:         (In some cases useful info about processes that
Jan 31 09:48:33 i5tuxedo umount[2639]:          use the device is found by lsof(8) or fuser(1).)
Jan 31 09:48:33 i5tuxedo systemd[1]: home.mount: Mount process exited, code=exited status=32
Jan 31 09:48:33 i5tuxedo systemd[1]: Failed unmounting /home.
Jan 31 09:48:33 i5tuxedo systemd[1]: home.mount: Unit is bound to inactive unit dev-disk-by\x2duuid-948157c2\x2d855b\x2d47b4\x2db084\x2d5eca13d5861e.device. Stopping, too.
Jan 31 09:48:33 i5tuxedo systemd[1]: Unmounting /home...
Jan 31 09:48:33 i5tuxedo umount[2642]: umount: /home: target is busy
Jan 31 09:48:33 i5tuxedo umount[2642]:         (In some cases useful info about processes that
Jan 31 09:48:33 i5tuxedo umount[2642]:          use the device is found by lsof(8) or fuser(1).)
Jan 31 09:48:33 i5tuxedo systemd[1]: home.mount: Mount process exited, code=exited status=32
Jan 31 09:48:33 i5tuxedo systemd[1]: Failed unmounting /home.
Jan 31 09:48:33 i5tuxedo systemd[1]: home.mount: Unit is bound to inactive unit dev-disk-by\x2duuid-948157c2\x2d855b\x2d47b4\x2db084\x2d5eca13d5861e.device. Stopping, too.
Jan 31 09:48:33 i5tuxedo systemd[1]: Unmounting /home...
Jan 31 09:48:33 i5tuxedo umount[2645]: umount: /home: target is busy
Jan 31 09:48:33 i5tuxedo umount[2645]:         (In some cases useful info about processes that
Jan 31 09:48:33 i5tuxedo umount[2645]:          use the device is found by lsof(8) or fuser(1).)
Jan 31 09:48:33 i5tuxedo systemd[1]: home.mount: Mount process exited, code=exited status=32
Jan 31 09:48:33 i5tuxedo systemd[1]: Failed unmounting /home.
Jan 31 09:48:33 i5tuxedo systemd[1]: home.mount: Unit is bound to inactive unit dev-disk-by\x2duuid-948157c2\x2d855b\x2d47b4\x2db084\x2d5eca13d5861e.device. Stopping, too.
Jan 31 09:48:33 i5tuxedo systemd[1]: Unmounting /home...
Jan 31 09:48:33 i5tuxedo umount[2649]: umount: /home: target is busy
Jan 31 09:48:33 i5tuxedo umount[2649]:         (In some cases useful info about processes that
Jan 31 09:48:33 i5tuxedo umount[2649]:          use the device is found by lsof(8) or fuser(1).)
Jan 31 09:48:33 i5tuxedo systemd[1]: home.mount: Mount process exited, code=exited status=32
Jan 31 09:48:33 i5tuxedo systemd[1]: Failed unmounting /home.
Jan 31 09:48:33 i5tuxedo systemd[1]: home.mount: Unit is bound to inactive unit dev-disk-by\x2duuid-948157c2\x2d855b\x2d47b4\x2db084\x2d5eca13d5861e.device. Stopping, too.
Jan 31 09:48:33 i5tuxedo systemd[1]: Unmounting /home...
Jan 31 09:48:33 i5tuxedo umount[2653]: umount: /home: target is busy
Jan 31 09:48:33 i5tuxedo umount[2653]:         (In some cases useful info about processes that
Jan 31 09:48:33 i5tuxedo umount[2653]:          use the device is found by lsof(8) or fuser(1).)
Jan 31 09:48:33 i5tuxedo systemd[1]: home.mount: Mount process exited, code=exited status=32
Jan 31 09:48:33 i5tuxedo systemd[1]: Failed unmounting /home.
Jan 31 09:48:33 i5tuxedo systemd[1]: home.mount: Unit is bound to inactive unit dev-disk-by\x2duuid-948157c2\x2d855b\x2d47b4\x2db084\x2d5eca13d5861e.device. Stopping, too.
Jan 31 09:48:33 i5tuxedo systemd[1]: Unmounting /home...
Jan 31 09:48:33 i5tuxedo umount[2657]: umount: /home: target is busy
Jan 31 09:48:33 i5tuxedo umount[2657]:         (In some cases useful info about processes that
Jan 31 09:48:33 i5tuxedo umount[2657]:          use the device is found by lsof(8) or fuser(1).)
Jan 31 09:48:33 i5tuxedo systemd[1]: home.mount: Mount process exited, code=exited status=32
Jan 31 09:48:33 i5tuxedo systemd[1]: Failed unmounting /home.
Jan 31 09:48:33 i5tuxedo systemd[1]: home.mount: Unit is bound to inactive unit dev-disk-by\x2duuid-948157c2\x2d855b\x2d47b4\x2db084\x2d5eca13d5861e.device. Stopping, too.
Jan 31 09:48:33 i5tuxedo systemd[1]: Unmounting /home...
Jan 31 09:48:33 i5tuxedo umount[2660]: umount: /home: target is busy
Jan 31 09:48:33 i5tuxedo umount[2660]:         (In some cases useful info about processes that
Jan 31 09:48:33 i5tuxedo umount[2660]:          use the device is found by lsof(8) or fuser(1).)
Jan 31 09:48:33 i5tuxedo systemd[1]: home.mount: Mount process exited, code=exited status=32
Jan 31 09:48:33 i5tuxedo systemd[1]: Failed unmounting /home.
Jan 31 09:48:33 i5tuxedo systemd[1]: home.mount: Unit is bound to inactive unit dev-disk-by\x2duuid-948157c2\x2d855b\x2d47b4\x2db084\x2d5eca13d5861e.device. Stopping, too.
Jan 31 09:48:33 i5tuxedo systemd[1]: Unmounting /home...
Jan 31 09:48:33 i5tuxedo umount[2663]: umount: /home: target is busy
Jan 31 09:48:33 i5tuxedo umount[2663]:         (In some cases useful info about processes that
Jan 31 09:48:33 i5tuxedo umount[2663]:          use the device is found by lsof(8) or fuser(1).)
Jan 31 09:48:33 i5tuxedo systemd[1]: home.mount: Mount process exited, code=exited status=32
Jan 31 09:48:33 i5tuxedo systemd[1]: Failed unmounting /home.
Jan 31 09:48:33 i5tuxedo systemd[1]: home.mount: Unit is bound to inactive unit dev-disk-by\x2duuid-948157c2\x2d855b\x2d47b4\x2db084\x2d5eca13d5861e.device. Stopping, too.
Jan 31 09:48:33 i5tuxedo systemd[1]: Unmounting /home...
Jan 31 09:48:33 i5tuxedo umount[2666]: umount: /home: target is busy
Jan 31 09:48:33 i5tuxedo umount[2666]:         (In some cases useful info about processes that
Jan 31 09:48:33 i5tuxedo umount[2666]:          use the device is found by lsof(8) or fuser(1).)
Jan 31 09:48:33 i5tuxedo systemd[1]: home.mount: Mount process exited, code=exited status=32
Jan 31 09:48:33 i5tuxedo systemd[1]: Failed unmounting /home.
Jan 31 09:48:33 i5tuxedo systemd[1]: home.mount: Unit is bound to inactive unit dev-disk-by\x2duuid-948157c2\x2d855b\x2d47b4\x2db084\x2d5eca13d5861e.device, but not stopping since we tried this too often recently.
Jan 31 09:48:33 i5tuxedo systemd[1]: Stopped File System Check on /dev/disk/by-uuid/948157c2-855b-47b4-b084-5eca13d5861e.
Jan 31 09:48:34 i5tuxedo kernel: [  370.577398] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan 31 09:48:34 i5tuxedo kernel: [  370.578032] ata4.00: ATA-9: WDC WD40EZRZ-00WN9B0, 80.00A80, max UDMA/133
Jan 31 09:48:34 i5tuxedo kernel: [  370.578034] ata4.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Jan 31 09:48:34 i5tuxedo kernel: [  370.578730] ata4.00: configured for UDMA/133
Jan 31 09:48:34 i5tuxedo kernel: [  370.578734] ata4: EH complete
Jan 31 09:48:34 i5tuxedo kernel: [  370.581438] EXT4-fs error (device sdb1): ext4_find_entry:1450: inode #21626913: comm Thunar: reading directory lblock 0
Jan 31 09:48:34 i5tuxedo kernel: [  370.581489] EXT4-fs error (device sdb1): ext4_find_entry:1450: inode #21626881: comm Thunar: reading directory lblock 0
Jan 31 09:48:34 i5tuxedo kernel: [  370.581491] EXT4-fs (sdb1): previous I/O error to superblock detected
Jan 31 09:48:34 i5tuxedo kernel: [  370.581506] EXT4-fs error (device sdb1): ext4_find_entry:1450: inode #21626913: comm gmain: reading directory lblock 0
Jan 31 09:48:34 i5tuxedo kernel: [  370.581508] sd 3:0:0:0: [sdb] Stopping disk
Jan 31 09:48:34 i5tuxedo kernel: [  370.581509] EXT4-fs (sdb1): previous I/O error to superblock detected
Jan 31 09:48:35 i5tuxedo kernel: [  371.637826] scsi 3:0:0:0: Direct-Access     ATA      WDC WD40EZRZ-00W 0A80 PQ: 0 ANSI: 5
Jan 31 09:48:35 i5tuxedo kernel: [  371.638198] sd 3:0:0:0: [sdh] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
Jan 31 09:48:35 i5tuxedo kernel: [  371.638203] sd 3:0:0:0: [sdh] 4096-byte physical blocks
Jan 31 09:48:35 i5tuxedo kernel: [  371.638239] sd 3:0:0:0: Attached scsi generic sg2 type 0
Jan 31 09:48:35 i5tuxedo kernel: [  371.638306] sd 3:0:0:0: [sdh] Write Protect is off
Jan 31 09:48:35 i5tuxedo kernel: [  371.638316] sd 3:0:0:0: [sdh] Mode Sense: 00 3a 00 00
Jan 31 09:48:35 i5tuxedo kernel: [  371.638342] sd 3:0:0:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jan 31 09:48:36 i5tuxedo kernel: [  372.923421] EXT4-fs error (device sdb1): ext4_find_entry:1450: inode #21626913: comm gmain: reading directory lblock 0
Jan 31 09:48:37 i5tuxedo kernel: [  373.492159]  sdh: sdh1 sdh2 sdh3
Jan 31 09:48:37 i5tuxedo kernel: [  373.492690] sd 3:0:0:0: [sdh] Attached SCSI disk
Jan 31 09:48:37 i5tuxedo kernel: [  373.529590] EXT4-fs error (device sdb1): ext4_find_entry:1450: inode #21626883: comm gmain: reading directory lblock 0
Jan 31 09:48:37 i5tuxedo systemd-udevd[2677]: Process '/lib/udev/hdparm' failed with exit code 5.
Jan 31 09:48:37 i5tuxedo kernel: [  373.590657] EXT4-fs error (device sdb1): ext4_find_entry:1450: inode #21626883: comm systemd: reading directory lblock 0
Jan 31 09:48:37 i5tuxedo kernel: [  373.590678] EXT4-fs error (device sdb1): ext4_find_entry:1450: inode #21626913: comm systemd: reading directory lblock 0
Jan 31 09:48:37 i5tuxedo kernel: [  373.592824] EXT4-fs error (device sdb1): ext4_find_entry:1450: inode #21626881: comm Thunar: reading directory lblock 0
Jan 31 09:48:37 i5tuxedo kernel: [  373.592834] EXT4-fs error (device sdb1): ext4_find_entry:1450: inode #21626912: comm Thunar: reading directory lblock 0
Jan 31 09:48:37 i5tuxedo kernel: [  373.597262] EXT4-fs error (device sdb1): ext4_find_entry:1450: inode #21626881: comm thunar-volman: reading directory lblock 0
Jan 31 09:48:37 i5tuxedo kernel: [  373.613638] EXT4-fs error (device sdb1): ext4_journal_check_start:56: Detected aborted journal
Jan 31 09:48:37 i5tuxedo kernel: [  373.613642] EXT4-fs (sdb1): Remounting filesystem read-only
Jan 31 09:48:37 i5tuxedo systemd[1]: Activating swap /dev/disk/by-uuid/a40c36ec-d0b9-4888-be30-bacb69741931...
Jan 31 09:48:37 i5tuxedo udisksd[2130]: Error statting /dev/sdb2\040(deleted): No such file or directory
Jan 31 09:48:37 i5tuxedo systemd[1775]: Swap dev-disk-by\x2did-ata\x2dWDC_WD40EZRZ\x2d00WN9B0_WD\x2dWCC4E4TT41J2\x2dpart2.swap appeared twice with different device paths /dev/sdb2 and /dev/sdh2
Jan 31 09:48:37 i5tuxedo systemd[1775]: Swap dev-disk-by\x2did-wwn\x2d0x50014ee20c97724d\x2dpart2.swap appeared twice with different device paths /dev/sdb2 and /dev/sdh2
Jan 31 09:48:37 i5tuxedo systemd[1775]: Swap dev-disk-by\x2dpartuuid-1098fb85\x2db98b\x2d45e7\x2d9971\x2d62c395146239.swap appeared twice with different device paths /dev/sdb2 and /dev/sdh2
Jan 31 09:48:37 i5tuxedo systemd[1775]: Swap dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d4\x2dpart2.swap appeared twice with different device paths /dev/sdb2 and /dev/sdh2
Jan 31 09:48:37 i5tuxedo systemd[1775]: Swap dev-disk-by\x2duuid-a40c36ec\x2dd0b9\x2d4888\x2dbe30\x2dbacb69741931.swap appeared twice with different device paths /dev/sdb2 and /dev/sdh2
Jan 31 09:48:37 i5tuxedo systemd[1]: Swap dev-disk-by\x2did-ata\x2dWDC_WD40EZRZ\x2d00WN9B0_WD\x2dWCC4E4TT41J2\x2dpart2.swap appeared twice with different device paths /dev/sdb2 and /dev/sdh2
Jan 31 09:48:37 i5tuxedo systemd[1]: Swap dev-disk-by\x2did-wwn\x2d0x50014ee20c97724d\x2dpart2.swap appeared twice with different device paths /dev/sdb2 and /dev/sdh2
Jan 31 09:48:37 i5tuxedo systemd[1]: Swap dev-disk-by\x2dpartuuid-1098fb85\x2db98b\x2d45e7\x2d9971\x2d62c395146239.swap appeared twice with different device paths /dev/sdb2 and /dev/sdh2
Jan 31 09:48:37 i5tuxedo systemd[1]: Swap dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d4\x2dpart2.swap appeared twice with different device paths /dev/sdb2 and /dev/sdh2
Jan 31 09:48:37 i5tuxedo systemd[1]: Swap dev-disk-by\x2duuid-a40c36ec\x2dd0b9\x2d4888\x2dbe30\x2dbacb69741931.swap appeared twice with different device paths /dev/sdb2 and /dev/sdh2
Jan 31 09:48:37 i5tuxedo kernel: [  374.127587] Adding 34435068k swap on /dev/sdh2.  Priority:-3 extents:1 across:34435068k FS
Jan 31 09:48:37 i5tuxedo systemd[1]: Activated swap /dev/disk/by-uuid/a40c36ec-d0b9-4888-be30-bacb69741931.
Jan 31 09:48:40 i5tuxedo kernel: [  376.767611] EXT4-fs error: 4 callbacks suppressed
Jan 31 09:48:40 i5tuxedo kernel: [  376.767621] EXT4-fs error (device sdb1): ext4_find_entry:1450: inode #21626883: comm panel-9-places: reading directory lblock 0
Jan 31 09:48:40 i5tuxedo kernel: [  376.775251] EXT4-fs error (device sdb1): ext4_find_entry:1450: inode #21626881: comm panel-9-places: reading directory lblock 0
Jan 31 09:48:43 i5tuxedo kernel: [  379.533849] EXT4-fs warning: 13 callbacks suppressed
Jan 31 09:48:43 i5tuxedo kernel: [  379.533860] EXT4-fs warning (device sdb1): dx_probe:739: inode #21626907: lblock 0: comm upstart: error -5 reading directory block
Jan 31 09:48:45 i5tuxedo kernel: [  381.913351] EXT4-fs error (device sdb1): ext4_find_entry:1450: inode #21626881: comm Thunar: reading directory lblock 0
Jan 31 09:48:48 i5tuxedo kernel: [  384.573643] BTRFS info (device sdh3): disk space caching is enabled
Jan 31 09:48:48 i5tuxedo kernel: [  384.573645] BTRFS: has skinny extents
Jan 31 09:48:48 i5tuxedo kernel: [  384.587362] EXT4-fs error (device sdb1): ext4_find_entry:1450: inode #21626883: comm update-notifier: reading directory lblock 0
Jan 31 09:48:48 i5tuxedo kernel: [  384.587376] EXT4-fs error (device sdb1): ext4_find_entry:1450: inode #21626881: comm update-notifier: reading directory lblock 0
Jan 31 09:48:48 i5tuxedo kernel: [  384.587380] EXT4-fs error (device sdb1): ext4_find_entry:1450: inode #21626881: comm update-notifier: reading directory lblock 0
Jan 31 09:48:48 i5tuxedo kernel: [  384.588814] EXT4-fs error (device sdb1): ext4_find_entry:1450: inode #21626913: comm update-notifier: reading directory lblock 0
Jan 31 09:48:48 i5tuxedo kernel: [  384.588818] EXT4-fs error (device sdb1): ext4_find_entry:1450: inode #21626881: comm update-notifier: reading directory lblock 0
Jan 31 09:48:48 i5tuxedo kernel: [  384.606560] EXT4-fs warning (device sdb1): dx_probe:739: inode #21626907: lblock 0: comm upstart: error -5 reading directory block
Jan 31 09:48:48 i5tuxedo udisksd[2130]: Error statting /dev/sdb2\040(deleted): No such file or directory
Jan 31 09:48:48 i5tuxedo udisksd[2130]: Mounted /dev/sdh3 at /media/spittler/e29062e9-3de1-4d73-a8e7-1ff82f96b5f9 on behalf of uid 1000
Jan 31 09:48:48 i5tuxedo kernel: [  385.255824] EXT4-fs error (device sdb1): ext4_find_entry:1450: inode #21626881: comm xfce4-notifyd: reading directory lblock 0
Jan 31 09:48:48 i5tuxedo kernel: [  385.255830] EXT4-fs error (device sdb1): ext4_find_entry:1450: inode #21626881: comm xfce4-notifyd: reading directory lblock 0
Jan 31 09:48:48 i5tuxedo kernel: [  385.255832] EXT4-fs error (device sdb1): ext4_find_entry:1450: inode #21626881: comm xfce4-notifyd: reading directory lblock 0
Jan 31 09:48:48 i5tuxedo kernel: [  385.255836] EXT4-fs error (device sdb1): ext4_find_entry:1450: inode #21626906: comm xfce4-notifyd: reading directory lblock 0
Jan 31 09:48:54 i5tuxedo kernel: [  390.533874] EXT4-fs warning (device sdb1): dx_probe:739: inode #21626907: lblock 0: comm upstart: error -5 reading directory block
Jan 31 09:48:57 i5tuxedo kernel: [  393.378390] EXT4-fs error: 6 callbacks suppressed
Jan 31 09:48:57 i5tuxedo kernel: [  393.378399] EXT4-fs error (device sdb1): ext4_find_entry:1450: inode #21626883: comm update-notifier: reading directory lblock 0
Jan 31 09:48:57 i5tuxedo kernel: [  393.378590] EXT4-fs warning (device sdb1): dx_probe:739: inode #21626907: lblock 0: comm upstart: error -5 reading directory block
Jan 31 09:48:59 i5tuxedo kernel: [  395.977541] EXT4-fs warning (device sdb1): dx_probe:739: inode #21626907: lblock 0: comm upstart: error -5 reading directory block
Jan 31 09:49:01 i5tuxedo kernel: [  397.611196] EXT4-fs error (device sdb1): ext4_find_entry:1450: inode #21626913: comm panel-1-whisker: reading directory lblock 0
Jan 31 09:49:01 i5tuxedo kernel: [  397.611221] EXT4-fs error (device sdb1): ext4_find_entry:1450: inode #21626913: comm panel-1-whisker: reading directory lblock 0
Jan 31 09:49:01 i5tuxedo kernel: [  397.611388] EXT4-fs error (device sdb1): ext4_find_entry:1450: inode #21626913: comm panel-1-whisker: reading directory lblock 0
Jan 31 09:49:01 i5tuxedo kernel: [  397.611522] EXT4-fs error (device sdb1): ext4_find_entry:1450: inode #21626913: comm panel-1-whisker: reading directory lblock 0
Jan 31 09:49:01 i5tuxedo kernel: [  397.611653] EXT4-fs error (device sdb1): ext4_find_entry:1450: inode #21626913: comm panel-1-whisker: reading directory lblock 0
Jan 31 09:49:01 i5tuxedo kernel: [  397.611785] EXT4-fs error (device sdb1): ext4_find_entry:1450: inode #21626913: comm panel-1-whisker: reading directory lblock 0
Jan 31 09:49:01 i5tuxedo kernel: [  397.611914] EXT4-fs error (device sdb1): ext4_find_entry:1450: inode #21626913: comm panel-1-whisker: reading directory lblock 0
Jan 31 09:49:01 i5tuxedo kernel: [  397.612044] EXT4-fs error (device sdb1): ext4_find_entry:1450: inode #21626913: comm panel-1-whisker: reading directory lblock 0
Jan 31 09:49:01 i5tuxedo kernel: [  397.612172] EXT4-fs error (device sdb1): ext4_find_entry:1450: inode #21626913: comm panel-1-whisker: reading directory lblock 0
Jan 31 09:49:03 i5tuxedo kernel: [  399.695039] EXT4-fs warning (device sdb1): dx_probe:739: inode #21626907: lblock 0: comm upstart: error -5 reading directory block
Jan 31 09:49:07 i5tuxedo kernel: [  403.430438] EXT4-fs error: 21 callbacks suppressed
Jan 31 09:49:07 i5tuxedo kernel: [  403.430445] EXT4-fs error (device sdb1): ext4_find_entry:1450: inode #21626906: comm xfce4-session: reading directory lblock 0
Jan 31 09:49:07 i5tuxedo kernel: [  403.430613] EXT4-fs warning (device sdb1): dx_probe:739: inode #21626907: lblock 0: comm upstart: error -5 reading directory block
Jan 31 09:49:07 i5tuxedo kernel: [  403.433820] EXT4-fs warning (device sdb1): dx_probe:739: inode #21626907: lblock 0: comm upstart: error -5 reading directory block
Jan 31 09:49:07 i5tuxedo kernel: [  403.452899] EXT4-fs error (device sdb1): ext4_find_entry:1450: inode #21626913: comm panel-9-places: reading directory lblock 0
Jan 31 09:49:07 i5tuxedo kernel: [  403.452950] EXT4-fs error (device sdb1): ext4_find_entry:1450: inode #21626913: comm panel-9-places: reading directory lblock 0
Jan 31 09:49:07 i5tuxedo kernel: [  403.452980] EXT4-fs warning (device sdb1): dx_probe:739: inode #21626907: lblock 0: comm upstart: error -5 reading directory block
Jan 31 09:49:07 i5tuxedo kernel: [  403.469076] EXT4-fs warning (device sdb1): dx_probe:739: inode #21626907: lblock 0: comm upstart: error -5 reading directory block
Jan 31 09:49:07 i5tuxedo kernel: [  403.469104] EXT4-fs warning (device sdb1): dx_probe:739: inode #21626907: lblock 0: comm upstart: error -5 reading directory block
Jan 31 09:49:07 i5tuxedo kernel: [  403.469119] EXT4-fs warning (device sdb1): dx_probe:739: inode #21626907: lblock 0: comm upstart: error -5 reading directory block
Jan 31 09:49:07 i5tuxedo kernel: [  403.469141] EXT4-fs warning (device sdb1): dx_probe:739: inode #21626907: lblock 0: comm upstart: error -5 reading directory block
Jan 31 09:49:07 i5tuxedo kernel: [  403.469155] EXT4-fs warning (device sdb1): dx_probe:739: inode #21626907: lblock 0: comm upstart: error -5 reading directory block
Jan 31 09:49:07 i5tuxedo kernel: [  403.469168] EXT4-fs warning (device sdb1): dx_probe:739: inode #21626907: lblock 0: comm upstart: error -5 reading directory block
Jan 31 09:49:07 i5tuxedo kernel: [  403.470012] EXT4-fs error (device sdb1): ext4_find_entry:1450: inode #21626913: comm nm-applet: reading directory lblock 0
Jan 31 09:49:07 i5tuxedo kernel: [  403.492565] EXT4-fs error (device sdb1): ext4_find_entry:1450: inode #21626881: comm iceauth: reading directory lblock 0
Jan 31 09:49:07 i5tuxedo obexd[2221]: Terminating
Jan 31 09:49:07 i5tuxedo kernel: [  403.532172] EXT4-fs error (device sdb1): ext4_find_entry:1450: inode #21626917: comm gpg-agent: reading directory lblock 0
Jan 31 09:49:07 i5tuxedo kernel: [  403.534242] EXT4-fs error (device sdb1): ext4_find_entry:1450: inode #21626883: comm upstart: reading directory lblock 0
Jan 31 09:49:07 i5tuxedo kernel: [  403.534257] EXT4-fs error (device sdb1): ext4_find_entry:1450: inode #21626881: comm upstart: reading directory lblock 0
Jan 31 09:47:30 i5tuxedo rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="1161" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
Jan 31 09:49:07 i5tuxedo rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="1161" x-info="http://www.rsyslog.com"] exiting on signal 15.
Jan 31 13:25:39 i5tuxedo rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="1093" x-info="http://www.rsyslog.com"] start
Jan 31 13:25:39 i5tuxedo rsyslogd-2222: command 'KLogPermitNonKernelFacility' is currently not permitted - did you already set it via a RainerScript command (v6+ config)? [v8.16.0 try http://www.rsyslog.com/e/2222 ]


Neuformatieren kann nicht des Rätsels Lösung sein; das habe ich ja schon bei der Neuinstalltion gemacht.
_______________________________
Welches System hätten's denn gern?

ebbi97a

User

  • »ebbi97a« ist männlich
  • »ebbi97a« ist der Autor dieses Themas

Beiträge: 181

Registrierungsdatum: 28.11.2005

Derivat: Xubuntu

Version: Ubuntu 18.04 LTS - Bionic Beaver

Architektur: 64-Bit PC

Desktop: XFCE

Andere Betriebssysteme: Debian, Devuan, Mint, Manjaro, MacOS X, Android, Windows 7

  • Nachricht senden

25

03.02.2017, 14:00

  1. Nochmals einen ausführlichen SMART-Test von 9 Stunden Dauer laufen gelassen: wieder 0 Fehler.
  2. Ein besseres Kabel habe ich noch nicht gefunden.
_______________________________
Welches System hätten's denn gern?

Fredl

Ubuntu-Forum-Team

Beiträge: 11 331

  • Nachricht senden

26

03.02.2017, 14:36

Ich wiederhole den Hinweis, daß es auch am Controller oder den elektrischen Verbindungen liegen könnte.
Ich würde erstmal irgendwo hingreifen als fortlaufend Tests mit unklaren Ergebnissen auszuführen. I/O-errors sind eine klare Aussage.
Beim Erstellen dieser Nachricht kamen keine Tiere zu Schaden.
me is all sausage
but don't call me Ferdl

ebbi97a

User

  • »ebbi97a« ist männlich
  • »ebbi97a« ist der Autor dieses Themas

Beiträge: 181

Registrierungsdatum: 28.11.2005

Derivat: Xubuntu

Version: Ubuntu 18.04 LTS - Bionic Beaver

Architektur: 64-Bit PC

Desktop: XFCE

Andere Betriebssysteme: Debian, Devuan, Mint, Manjaro, MacOS X, Android, Windows 7

  • Nachricht senden

27

10.02.2017, 15:21

Darf ich hoffen?

Zitat von »Fredl«

Ich wiederhole den Hinweis, daß es auch am Controller oder den elektrischen Verbindungen liegen könnte.

Habe ein neues SATA-Kabel mit einem gekröpften Ende eingezogen - allerdings an einem anderen Controller-Stecker als vorher (das alte wäre recht mühsam zu entfernen gewesen). Dann habe ich alle Partitionen auf /dev/sdb mit fsck bzw. dem Pendant für BTRFS geprüft: keine Fehler.
Danach habe ich den kurzen SAMRT-Test für /dev/sdb wiederholt: 0 Fehler = passed.

Danach habe ich mit Timeshift eine Sicherung der beiden noch lauffähigen Systeme auf dem Rechner (zur Erinnerung: das waren die beiden Systeme, welche /dev/sdb nicht fest eingebunden hatten und es ausschließlich für Timeshift als /dev/sdb3 verwendet haben). Die Versuche waren während des Fehlerzustands ausnahmslos alle abgestürzt; jetzt sind sie durchgelaufen.

Das kaputte System startet auch noch, allerdings habe ich vorauseilender Panik selbst eine Menge wichtiger Daten und Konfigurationen vernichtet.
_______________________________
Welches System hätten's denn gern?

Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von »ebbi97a« (10.02.2017, 15:26)

ebbi97a

User

  • »ebbi97a« ist männlich
  • »ebbi97a« ist der Autor dieses Themas

Beiträge: 181

Registrierungsdatum: 28.11.2005

Derivat: Xubuntu

Version: Ubuntu 18.04 LTS - Bionic Beaver

Architektur: 64-Bit PC

Desktop: XFCE

Andere Betriebssysteme: Debian, Devuan, Mint, Manjaro, MacOS X, Android, Windows 7

  • Nachricht senden

28

17.02.2017, 12:12

Es geht schon wieder los ― da muß ich wohl doch Geld in die Hand nehmen und eine neue Platte kaufen.

______________________________________________________________________________________


Halt! Alles zurück! {12:16:27}
Das ist ja eine ganz andere Platte, die nur als Wechselplatte angeschlossen ist. Die wurde allerdings kaum verwendet und auch nicht mißhandelt; die kann unmöglich kaputt sein. Irgendwas ist an der Kiste oberfaul X(
»ebbi97a« hat folgendes Bild angehängt:
  • Bildschirmfoto_2017-02-17_11-57-22.png
_______________________________
Welches System hätten's denn gern?

Fredl

Ubuntu-Forum-Team

Beiträge: 11 331

  • Nachricht senden

29

17.02.2017, 13:58

Zitat von »Fredl«

"For details see syslog" ...

Und bitte keine Screenshots. Man kann auch Texte aus Dialogboxen kopieren.
Beim Erstellen dieser Nachricht kamen keine Tiere zu Schaden.
me is all sausage
but don't call me Ferdl

ebbi97a

User

  • »ebbi97a« ist männlich
  • »ebbi97a« ist der Autor dieses Themas

Beiträge: 181

Registrierungsdatum: 28.11.2005

Derivat: Xubuntu

Version: Ubuntu 18.04 LTS - Bionic Beaver

Architektur: 64-Bit PC

Desktop: XFCE

Andere Betriebssysteme: Debian, Devuan, Mint, Manjaro, MacOS X, Android, Windows 7

  • Nachricht senden

30

19.02.2017, 06:52

Fehler verschwunden

Ich bedanke mich bei allen, die soviel Geduld mit mir und meinem Problem gehabt haben ― besonders Fredl.

Der Fehler ist seit 1 Woche nicht mehr aufgetreten, obwohl ich fleißig am Wiederaufbau bin und große Datenmengen bewege. Ein neues System war ziemlich leicht und schnell installiert und die reinen Benutzerdaten (Bilder, Texte usw.) waren auch schnell wieder aus der Sicherung zurückkopiert. Bei den aufwendigen Konfigurationsdaten einer großen Menge von Anwendungsprogrammen kam mir ein Zufall zuhilfe: in meiner Verzweiflung nach dem Unfall hatte ich mangels genialer Einfälle u.a. eine über 80 GB große Sicherung mit tar von einem anderen System aus auf einer externen Platte, die eigentlich nur zum Sichern von in Arbeit befindlichen Photos und Videos gedacht war, angelegt. Sie scheint fehlerfrei zu sein, aber das Wiedergewinnen einer Datei dauert etwa eine halbe Stunde pro Suchvorgang; gestern Abend konnte ich auch diese Weise meine vollständige Buchhaltung vom Unfalltag wiedergewinnen. :)

Der Rest wird auch noch werden. Lehre daraus:
  1. Die Systemsicherung mit Timeshift war gut und praxistauglich. Hätte ich sie durch vorauseilende Panik nicht selbst vernichtet, hätte ich schlimmstenfalls ein paar Stunden verloren.
  2. Bei der Sicherung der Nutzerdaten ― insbesondere den Konfigurationsdaten von Anwendungsprogrammen ― besteht noch erheblicher Verbesserungsbedarf. :whistling:
_______________________________
Welches System hätten's denn gern?

Dieser Beitrag wurde bereits 3 mal editiert, zuletzt von »ebbi97a« (19.02.2017, 07:02)

  • 1
  • 2

Zurzeit sind neben Ihnen 2 Benutzer in diesem Thema unterwegs:

2 Besucher

Ähnliche Themen

Verwendete Tags

Btrfs, ext4, partition, Timeshift, xubuntu