1 Temat przez Graffy

  • Graffy
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2013-04-23
  • Posty: 310

Temat: Extroot problem z pendrive

Przez przypadek zauważyłem, że coś nawala pendrive od extroot.
Router działa jak i wszystkie uruchomione usługi.
System plików to ext4 z wyłączonym księgowaniem.
Jakoś specjalnie go nie obciążam, logi staram się zapisywać do /tmp.
Działał bez problemów jakieś pół roku.
Można się jakoś ustrzec przed tym ?
Fragmenty z logread:

Sep 18 13:47:31 wdr4300 kern.crit kernel: [781645.500000] EXT4-fs error (device sda2): ext4_find_entry:935: inode #159: comm find: reading directory lblock 0
Sep 18 13:47:31 wdr4300 kern.crit kernel: [781645.510000] EXT4-fs error (device sda2): ext4_find_entry:935: inode #8227: comm find: reading directory lblock 0
Sep 18 13:47:31 wdr4300 kern.crit kernel: [781645.520000] EXT4-fs error (device sda2): ext4_find_entry:935: inode #8227: comm find: reading directory lblock 0
Sep 18 13:47:31 wdr4300 kern.crit kernel: [781645.530000] EXT4-fs error (device sda2): ext4_find_entry:935: inode #8227: comm find: reading directory lblock 0
Sep 18 13:47:31 wdr4300 kern.crit kernel: [781645.540000] EXT4-fs error (device sda2): ext4_find_entry:935: inode #8227: comm find: reading directory lblock 0
Sep 18 13:47:31 wdr4300 kern.crit kernel: [781645.550000] EXT4-fs error (device sda2): ext4_find_entry:935: inode #8227: comm find: reading directory lblock 0
Sep 18 13:47:31 wdr4300 kern.crit kernel: [781645.570000] EXT4-fs error (device sda2): ext4_find_entry:935: inode #8227: comm find: reading directory lblock 0
Sep 18 13:47:31 wdr4300 kern.crit kernel: [781645.580000] EXT4-fs error (device sda2): ext4_find_entry:935: inode #8227: comm find: reading directory lblock 0
Sep 18 13:47:31 wdr4300 kern.crit kernel: [781645.590000] EXT4-fs error (device sda2): ext4_find_entry:935: inode #8227: comm find: reading directory lblock 0
Sep 18 13:47:31 wdr4300 kern.crit kernel: [781645.600000] EXT4-fs error (device sda2): ext4_find_entry:935: inode #8227: comm find: reading directory lblock 0
Sep 18 13:47:31 wdr4300 kern.crit kernel: [781645.610000] EXT4-fs error (device sda2): ext4_find_entry:935: inode #8227: comm find: reading directory lblock 0
Sep 18 13:47:31 wdr4300 kern.crit kernel: [781645.620000] EXT4-fs error (device sda2): ext4_find_entry:935: inode #8227: comm find: reading directory lblock 0
Sep 18 13:47:31 wdr4300 kern.crit kernel: [781645.640000] EXT4-fs error (device sda2): ext4_find_entry:935: inode #8227: comm find: reading directory lblock 0
Sep 18 13:47:31 wdr4300 kern.crit kernel: [781645.650000] EXT4-fs error (device sda2): ext4_find_entry:935: inode #8227: comm find: reading directory lblock 0
Sep 18 13:47:31 wdr4300 kern.crit kernel: [781645.660000] EXT4-fs error (device sda2): ext4_find_entry:935: inode #8227: comm find: reading directory lblock 0
Sep 18 13:47:31 wdr4300 kern.crit kernel: [781645.670000] EXT4-fs error (device sda2): ext4_find_entry:935: inode #8227: comm find: reading directory lblock 0
Sep 18 13:47:31 wdr4300 kern.crit kernel: [781645.680000] EXT4-fs error (device sda2): ext4_find_entry:935: inode #8227: comm find: reading directory lblock 0
Sep 18 13:47:31 wdr4300 kern.crit kernel: [781645.690000] EXT4-fs error (device sda2): ext4_find_entry:935: inode #8227: comm find: reading directory lblock 0
Sep 18 13:47:31 wdr4300 kern.crit kernel: [781645.710000] EXT4-fs error (device sda2): ext4_find_entry:935: inode #8227: comm find: reading directory lblock 0
Sep 18 13:47:31 wdr4300 kern.crit kernel: [781645.720000] EXT4-fs error (device sda2): ext4_find_entry:935: inode #8227: comm find: reading directory lblock 0
...............
Sep 18 13:52:40 wdr4300 kern.crit kernel: [781955.110000] EXT4-fs error (device sda2): ext4_read_inode_bitmap:161: comm mc: Cannot read inode bitmap - block_group = 0, inode_bitmap = 49
Sep 18 13:52:40 wdr4300 kern.crit kernel: [781955.130000] EXT4-fs error (device sda2) in ext4_new_inode:941: IO failure
Sep 18 13:52:41 wdr4300 kern.crit kernel: [781955.130000] EXT4-fs error (device sda2): ext4_read_block_bitmap:396: comm mc: Cannot read block bitmap - block_group = 1, block_bitmap = 34
Sep 18 13:52:41 wdr4300 kern.crit kernel: [781955.150000] EXT4-fs (sda2): delayed block allocation failed for inode 141 at logical offset 0 with max blocks 1 with error -5
Sep 18 13:52:41 wdr4300 kern.crit kernel: [781955.160000] EXT4-fs (sda2): This should not happen!! Data will be lost
Sep 18 13:52:41 wdr4300 kern.crit kernel: [781955.160000]
Sep 18 13:52:41 wdr4300 kern.crit kernel: [781955.180000] EXT4-fs error (device sda2): ext4_read_inode_bitmap:161: comm mc: Cannot read inode bitmap - block_group = 0, inode_bitmap = 49
Sep 18 13:52:41 wdr4300 kern.crit kernel: [781955.190000] EXT4-fs error (device sda2) in ext4_new_inode:941: IO failure
Sep 18 13:52:41 wdr4300 kern.crit kernel: [781955.200000] EXT4-fs error (device sda2): ext4_read_block_bitmap:396: comm mc: Cannot read block bitmap - block_group = 1, block_bitmap = 34
Sep 18 13:52:41 wdr4300 kern.crit kernel: [781955.210000] EXT4-fs (sda2): delayed block allocation failed for inode 142 at logical offset 0 with max blocks 1 with error -5
Sep 18 13:52:41 wdr4300 kern.crit kernel: [781955.220000] EXT4-fs (sda2): This should not happen!! Data will be lost
Sep 18 13:52:41 wdr4300 kern.crit kernel: [781955.220000]
Sep 18 13:52:41 wdr4300 kern.crit kernel: [781955.240000] EXT4-fs error (device sda2): ext4_read_inode_bitmap:161: comm mc: Cannot read inode bitmap - block_group = 0, inode_bitmap = 49
Sep 18 13:52:41 wdr4300 kern.crit kernel: [781955.250000] EXT4-fs error (device sda2) in ext4_new_inode:941: IO failure
Sep 18 13:52:41 wdr4300 kern.crit kernel: [781955.260000] EXT4-fs error (device sda2): ext4_read_block_bitmap:396: comm mc: Cannot read block bitmap - block_group = 1, block_bitmap = 34
Sep 18 13:52:41 wdr4300 kern.crit kernel: [781955.280000] EXT4-fs (sda2): delayed block allocation failed for inode 143 at logical offset 0 with max blocks 1 with error -5
Sep 18 13:52:41 wdr4300 kern.crit kernel: [781955.290000] EXT4-fs (sda2): This should not happen!! Data will be lost
Sep 18 13:52:41 wdr4300 kern.crit kernel: [781955.290000]
Sep 18 13:52:41 wdr4300 kern.crit kernel: [781955.300000] EXT4-fs error (device sda2): ext4_read_inode_bitmap:161: comm mc: Cannot read inode bitmap - block_group = 0, inode_bitmap = 49
Sep 18 13:52:41 wdr4300 kern.crit kernel: [781955.310000] EXT4-fs error (device sda2) in ext4_new_inode:941: IO failure
Sep 18 13:52:41 wdr4300 kern.crit kernel: [781955.320000] EXT4-fs error (device sda2): ext4_read_block_bitmap:396: comm mc: Cannot read block bitmap - block_group = 1, block_bitmap = 34
Sep 18 13:52:41 wdr4300 kern.crit kernel: [781955.330000] EXT4-fs (sda2): delayed block allocation failed for inode 143 at logical offset 0 with max blocks 1 with error -5
Sep 18 13:52:41 wdr4300 kern.crit kernel: [781955.350000] EXT4-fs (sda2): This should not happen!! Data will be lost
Sep 18 13:52:41 wdr4300 kern.crit kernel: [781955.350000]
Sep 18 13:52:41 wdr4300 kern.crit kernel: [781955.360000] EXT4-fs error (device sda2): ext4_read_inode_bitmap:161: comm mc: Cannot read inode bitmap - block_group = 0, inode_bitmap = 49
Sep 18 13:52:41 wdr4300 kern.crit kernel: [781955.370000] EXT4-fs error (device sda2) in ext4_new_inode:941: IO failure
Sep 18 13:52:41 wdr4300 kern.crit kernel: [781955.380000] EXT4-fs error (device sda2): ext4_read_block_bitmap:396: comm mc: Cannot read block bitmap - block_group = 1, block_bitmap = 34
Sep 18 13:52:41 wdr4300 kern.crit kernel: [781955.390000] EXT4-fs (sda2): delayed block allocation failed for inode 143 at logical offset 0 with max blocks 1 with error -5
Sep 18 13:52:41 wdr4300 kern.crit kernel: [781955.410000] EXT4-fs (sda2): This should not happen!! Data will be lost
Sep 18 13:52:41 wdr4300 kern.crit kernel: [781955.410000]

Ciekaw jestem czy wstanie jak go zrestartuje po powrocie do domu ...

APU2 @ OpenWrt 18.06-SNAPSHOT, r7852-7ac6044632

2 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 115,838

Odp: Extroot problem z pendrive

Odłącz, uruchom, podłącz, napraw system plików.

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

3 Odpowiedź przez Graffy

  • Graffy
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2013-04-23
  • Posty: 310

Odp: Extroot problem z pendrive

Wyłączyłem router, zrobiłem kopię dd na wszelki wypadek.
Sprawdziłem system plików na PC z Linux-em i nie znalazł żadnych błędów.
Uruchomiłem router - wszystko działa jak trzeba.

APU2 @ OpenWrt 18.06-SNAPSHOT, r7852-7ac6044632

4 Odpowiedź przez oneiro

  • oneiro
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2011-04-26
  • Posty: 483

Odp: Extroot problem z pendrive

Chciałbym odświeżyć temat, mam takie coś:

Dec 16 20:48:49 OpenWrt kern.crit kernel: [87381.110000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #117: comm ash: reading directory lblock 0
Dec 16 20:48:50 OpenWrt kern.crit kernel: [87381.200000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #120: comm df: reading directory lblock 0
Dec 16 20:48:50 OpenWrt kern.crit kernel: [87381.210000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #120: comm df: reading directory lblock 0
Dec 16 20:48:50 OpenWrt kern.crit kernel: [87381.220000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #120: comm df: reading directory lblock 0
Dec 16 20:49:17 OpenWrt kern.crit kernel: [87408.200000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #130: comm ash: reading directory lblock 0
Dec 16 20:49:17 OpenWrt kern.crit kernel: [87408.590000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #126: comm ash: reading directory lblock 0

Zrobiony extroot na /dev/sda1 i w związku z tym mam pytanie, bo nie wiem gdzie leży problem.

Pendrive podłączony bezpośrednio do portu USB w TP-LINK 1043ND v1 - 2 dni działa bez zarzutu
Pendrive podłączony przez aktywny hub (z podłączonym i nie zasilaczem ) 1 dzień i w/w log
Pendrive podłączony przez aktywny hub + USB_HDD (z podłączonym zasilaczem ) 1 dzień i w/w log

Czy może to być wina huba? Nie wiem czy hub (sterownik/mod) jest jakoś konfigurowalny w linuxie, jeśli tak czy można coś zmienić?

5 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 115,838

Odp: Extroot problem z pendrive

Zły hub. A tak na prawdę to może być również problem np. z kablami i luźnymi wtyczkami.

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona