• Zarejestrowany: 2014-03-30
  • Posty: 13

Temat: Potrzebny reboot po włączeniu z extroot

Witam,

Posiadam Edimax 3G-6200n.

Mam zrobiony extroot, który jest na karcie microSD w modemie Huawei e3276.

Po włączeniu zasilania w routerze extroot nie jest dobrze montowany, są błędy.

[   78.520000] scsi2 : usb-storage 1-1:1.3
[   78.530000] scsi3 : usb-storage 1-1:1.4
[   79.520000] scsi 2:0:0:0: CD-ROM            HUAWEI   Mass Storage     2.31 PQ: 0 ANSI: 2
[   79.540000] scsi 3:0:0:0: Direct-Access     HUAWEI   TF CARD Storage  2.31 PQ: 0 ANSI: 2
[   79.570000] sd 3:0:0:0: [sdb] 7744512 512-byte logical blocks: (3.96 GB/3.69 GiB)
[   79.590000] sd 3:0:0:0: [sdb] Write Protect is off
[   79.600000] sd 3:0:0:0: [sdb] Mode Sense: 0f 00 00 00
[   79.600000] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   79.640000]  sdb: sdb1
[   79.660000] sd 3:0:0:0: [sdb] Attached SCSI removable disk
[   93.350000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #12: comm dropbear: reading directory lblock 0
[   93.410000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #2: comm dropbear: reading directory lblock 0
[   93.440000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #12: comm ash: reading directory lblock 0
[   93.470000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #12: comm ash: reading directory lblock 0
[   93.510000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #232: comm ash: reading directory lblock 0
[   93.540000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #128: comm ash: reading directory lblock 0
[   93.580000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #128: comm ash: reading directory lblock 0
[   93.600000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #12: comm ash: reading directory lblock 0
[   93.620000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #128: comm ash: reading directory lblock 0
[   93.640000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #128: comm ash: reading directory lblock 0
[   93.660000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #12: comm ash: reading directory lblock 0
[   93.690000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #232: comm ash: reading directory lblock 0
[   93.910000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #232: comm sysinfo.sh: reading directory lblock 0
[   93.940000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #128: comm sysinfo.sh: reading directory lblock 0
[   94.300000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #232: comm sysinfo.sh: reading directory lblock 0
[   94.650000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #128: comm sysinfo.sh: reading directory lblock 0
[   94.670000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #232: comm sysinfo.sh: reading directory lblock 0
[   94.710000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #128: comm sysinfo.sh: reading directory lblock 0
[  111.300000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #448: comm hotplug-call: reading directory lblock 0

Dopiero po zrobieniu reboota jest dobrze:

[    9.910000] scsi0 : usb-storage 1-1:1.3
[    9.920000] scsi1 : usb-storage 1-1:1.4
[   10.920000] scsi 0:0:0:0: CD-ROM            HUAWEI   Mass Storage     2.31 PQ: 0 ANSI: 2
[   10.940000] scsi 1:0:0:0: Direct-Access     HUAWEI   TF CARD Storage  2.31 PQ: 0 ANSI: 2
[   10.960000] sd 1:0:0:0: [sda] 7744512 512-byte logical blocks: (3.96 GB/3.69 GiB)
[   10.990000] sd 1:0:0:0: [sda] Write Protect is off
[   11.000000] sd 1:0:0:0: [sda] Mode Sense: 0f 00 00 00
[   11.000000] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   11.040000]  sda: sda1
[   11.050000] sd 1:0:0:0: [sda] Attached SCSI removable disk
[   30.150000] EXT4-fs (sda1): recovery complete
[   30.160000] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)

I tak zawsze trzeba zrobić, po wznowieniu zasilania.

Co mogę zrobić by działało to od razu?
(Względnie może być skrypt który go zrestartuje...)

Pozdrawiam

Jacek D.

2 Odpowiedź przez Cezary

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

Odp: Potrzebny reboot po włączeniu z extroot

Przełączyć modem od razu w taki tryb żeby nie przełączał i nie resetował modemu a tym samym karty sd. Czy się da na e3276 - nie wiem, musisz poszukać czy wejdzie jakiś kod na niego.

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

Cezary's Strona

3 Odpowiedź przez lowermann (edytowany przez lowermann 2014-04-10 22:13:36)

  • Skąd: Lublin
  • Zarejestrowany: 2012-12-14
  • Posty: 69

Odp: Potrzebny reboot po włączeniu z extroot

Nie wiem czy ci to w czymś pomoże, ale ja miałem taki problem, że nie zawsze montowało mi extroota po włączeniu routera, i chciałem żeby router po stwierdzeniu że gdy nie ma extroota resetował router aż do zobaczenia extroota. Pomógł mi Cezary.

Zrobiłem tak:
Utworzyłem skrypt o nazwie extroot.sh poleceniem

# touch /bin/extroot.sh
 # chmod 755 /bin/extroot.sh
O następującej wartości
A=$(mount | grep "/dev/sd.*on /overlay" | wc -l)
if [ "$A" = "1" ]; then
 echo "jest extroot, nic nie rób :)"
else
 reboot
fi

Jego wywołanie dodałem do skryptu uruchamianego przy starcie systemu czyli do
/etc/rc.local,

Tam zawarłem linijkę z jego wywołaniem czyli

/bin/extroot.sh &
exit 0

I działa, tutaj więcej http://eko.one.pl/forum/viewtopic.php?pid=81344#p81344

1. Modem e3131, sieć Aero2  + Router TL-MR3420 Gargoyle 1.6.2.1
2. Modem E3372, sieć CP LTE + Router TL-MR3420 Gargoyle 1.6.2.1

lowermann's Strona

4 Odpowiedź przez jacekdob (edytowany przez jacekdob 2014-04-11 20:13:16)

  • Zarejestrowany: 2014-03-30
  • Posty: 13

Odp: Potrzebny reboot po włączeniu z extroot

Gdy extroot jest poprawnie zamontowany to tworzenie pliku nie ma sensu bo i tak będzie tylko na karcie SD a nie na routerze.

Jak extroot nie jest poprawnie zamontowany, to nie można nic zapisać, bo wszystko jest read-only.

Jak zatem zapisać plik, który by resetował router?

Czego mam szukać dla modemu by się nie przełączał?

Na razie mam:

root@OpenWrt:~# cat /etc/modules.d/60-usb-serial
usbserial vendor=0x12d1 product=0x1506
root@OpenWrt:/proc/1# cat /sys/kernel/debug/usb/devices

T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480  MxCh= 1
B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev= 3.03
S:  Manufacturer=Linux 3.3.8 dwc_otg
S:  Product=DWC OTG Controller
S:  SerialNumber=dwc_otg.0
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=480  MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=12d1 ProdID=1506 Rev= 1.02
S:  Manufacturer=HUAWEI Technology
S:  Product=HUAWEI Mobile
C:* #Ifs= 5 Cfg#= 1 Atr=80 MxPwr=500mA
I:* If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=02 Prot=10 Driver=usbserial_generic
E:  Ad=81(I) Atr=03(Int.) MxPS=  64 Ivl=2ms
E:  Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms
I:* If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=02 Prot=12 Driver=usbserial_generic
E:  Ad=83(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms
I:  If#= 2 Alt= 0 #EPs= 1 Cls=ff(vend.) Sub=02 Prot=16 Driver=huawei_ether
E:  Ad=84(I) Atr=03(Int.) MxPS=  64 Ivl=2ms
I:* If#= 2 Alt= 1 #EPs= 3 Cls=ff(vend.) Sub=02 Prot=16 Driver=huawei_ether
E:  Ad=84(I) Atr=03(Int.) MxPS=  64 Ivl=2ms
E:  Ad=85(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=03(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms
I:* If#= 3 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
E:  Ad=04(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=86(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 4 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
E:  Ad=05(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=87(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
root@OpenWrt:/proc/1# gcom -d /dev/ttyUSB1 info
##### Wireless WAN Modem Configuration #####
Product text:
====

Manufacturer: huawei
Model: E3276
Revision: 21.430.03.04.55
IMEI: xxxxxxxxxxxxxxx
+GCAP: +CGSM,+DS,+ES
OK
====
Manufacturer:           huawei
IMEI and Serial Number: xxxxxxxxxxxxxxx
Manufacturer's Revision:
21.430.03.04.
Hardware Revision:

Network Locked:         ERROR:
Customisation:

Band settings:          (
)
APN:                    0,"IP","","",0,0,0,0
##### END #####

Pozdrawiam,

Jacek D.

5 Odpowiedź przez Cezary

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

Odp: Potrzebny reboot po włączeniu z extroot

Po co w ogóle wymusiłeś usbserial_generic? option jest o tego a nie usbserial_generic.

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

Cezary's Strona

6 Odpowiedź przez jacekdob

  • Zarejestrowany: 2014-03-30
  • Posty: 13

Odp: Potrzebny reboot po włączeniu z extroot

To co mam zmienić?

Modem jest wykrywany i łączy z internetem przy takiej konfiguracji:

root@OpenWrt:/etc/modules.d# for f in *; do echo "###Filename: $f###"; cat "$f"; done
###Filename: 01-crypto-core###
crypto_algapi
###Filename: 09-crypto-aes###
aes_generic
###Filename: 09-crypto-arc4###
arc4
###Filename: 19-input-core###
input-core
###Filename: 20-cfg80211###
compat
cfg80211
###Filename: 20-eeprom-93cx6###
eeprom_93cx6
###Filename: 20-input-polldev###
input-polldev
###Filename: 20-lib-crc-ccitt###
crc-ccitt
###Filename: 20-lib-crc-itu-t###
crc-itu-t
###Filename: 20-lib-crc16###
crc16
###Filename: 20-nls-base###
nls_base
###Filename: 20-scsi-core###
scsi_mod
###Filename: 20-usb-core###
usb-common
usbcore
###Filename: 21-mac80211###
mac80211
###Filename: 24-rt2x00-lib###
rt2x00lib
###Filename: 25-nls-cp437###
nls_cp437
###Filename: 25-nls-iso8859-1###
nls_iso8859-1
###Filename: 25-rt2x00-mmio###
rt2x00mmio
###Filename: 27-rt2800-lib###
rt2800lib
###Filename: 28-rt2800-mmio###
rt2800mmio
###Filename: 29-rt2800-soc###
rt2x00soc
rt2800soc
###Filename: 30-button-hotplug###
button-hotplug
###Filename: 30-fs-ext4###
mbcache
jbd2
ext4
###Filename: 30-fs-vfat###
fat
vfat
###Filename: 30-gpio-button-hotplug###
gpio-button-hotplug
###Filename: 30-ppp###
slhc
ppp_generic
ppp_async
###Filename: 30-tun###
tun
###Filename: 40-ipt-core###
x_tables
xt_tcpudp
ip_tables
iptable_filter
iptable_mangle
xt_limit
xt_mac
xt_multiport
xt_comment
ipt_LOG
xt_TCPMSS
ipt_REJECT
###Filename: 40-pppox###
pppox
###Filename: 40-scsi-core###
sd_mod
###Filename: 40-usb2###
ehci-hcd
###Filename: 41-ipt-conntrack###
nf_conntrack
nf_defrag_ipv4
nf_conntrack_ipv4
xt_state
iptable_raw
xt_NOTRACK
xt_CT
xt_conntrack
###Filename: 41-pppoe###
pppoe
###Filename: 42-ipt-nat###
nf_nat
iptable_nat
ipt_MASQUERADE
###Filename: 45-ipt-nathelper###
nf_conntrack_ftp
nf_nat_ftp
nf_conntrack_irc
nf_nat_irc
###Filename: 50-ledtrig-usbdev###
ledtrig-usbdev
###Filename: 54-usb-rt305x-dwc_otg###
dwc_otg
###Filename: 60-huawei-hw-cdc###
hw_cdc_driver
###Filename: 60-leds-gpio###
leds-gpio
###Filename: 60-usb-net###
usbnet
###Filename: 60-usb-serial###
usbserial vendor=0x12d1 product=0x1506
###Filename: 60-usb-storage###
usb-storage
###Filename: 60-usb-wdm###
cdc-wdm
###Filename: 61-usb-net-cdc-ether###
cdc_ether
###Filename: 61-usb-serial-wwan###
usb_wwan
###Filename: 62-input-gpio-keys-polled###
gpio_keys_polled
###Filename: 62-usb-net-cdc-ncm###
cdc_ncm
###Filename: 62-usb-net-qmi-wwan###
qmi_wwan
###Filename: 65-usb-serial-option###
option

Jak zakomentuję "usbserial vendor=0x12d1 product=0x1506" to modem nie ma przypisanego sterownika i nie łączy z internetem.

7 Odpowiedź przez Cezary

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

Odp: Potrzebny reboot po włączeniu z extroot

Moduł option jest do obsługi modemów Huawei, pytanie było po co wymusiłeś usbserial generyczny na nim?

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

Cezary's Strona

8 Odpowiedź przez lowermann (edytowany przez lowermann 2014-04-12 09:04:44)

  • Skąd: Lublin
  • Zarejestrowany: 2012-12-14
  • Posty: 69

Odp: Potrzebny reboot po włączeniu z extroot

jacekdob napisał/a:

Gdy extroot jest poprawnie zamontowany to tworzenie pliku nie ma sensu bo i tak będzie tylko na karcie SD a nie na routerze.

Jak extroot nie jest poprawnie zamontowany, to nie można nic zapisać, bo wszystko jest read-only.

Jak zatem zapisać plik, który by resetował router?

Czego mam szukać dla modemu by się nie przełączał?


To proste, odpinasz modem od routera, lub wyciągasz kartę sd z modemu, tak żeby nie tworzył extroota i ten plik do resetowania zapisujesz w routerze, nie w extroocie.

No bo co ci da jak plik będzie zamontowany na extroocie jak nie zamontuje ci go poprawnie lub w ogóle i tym samym router nie będzie wiedział czy ma się resetować bo nie ma extroota, a jak jest extroot to i tak się nie zresetuje, więc byłoby to bez sensu.

Potem jak utworzysz te pliki to resetujesz router i patrzysz czy  bedzie się resetował. Powinien w kółko się resetować, gdyż nie będzie extroota. Następnie podpinasz modem i pendrive, lub modem z kartą sd i sprawdzasz czy będzie ok.

Pozdrawiam

1. Modem e3131, sieć Aero2  + Router TL-MR3420 Gargoyle 1.6.2.1
2. Modem E3372, sieć CP LTE + Router TL-MR3420 Gargoyle 1.6.2.1

lowermann's Strona

9 Odpowiedź przez jacekdob

  • Zarejestrowany: 2014-03-30
  • Posty: 13

Odp: Potrzebny reboot po włączeniu z extroot

Cezary napisał/a:

Moduł option jest do obsługi modemów Huawei, pytanie było po co wymusiłeś usbserial generyczny na nim?

A jak go odmusić?

10 Odpowiedź przez Cezary

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

Odp: Potrzebny reboot po włączeniu z extroot

Wywal te vendor=0x12d1 product=0x1506. Sam to wpisałeś to chyba wiesz po co to zrobiłeś, prawda?

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

Cezary's Strona

11 Odpowiedź przez jacekdob

  • Zarejestrowany: 2014-03-30
  • Posty: 13

Odp: Potrzebny reboot po włączeniu z extroot

Tylko jak usunę "vendor=0x12d1 product=0x1506", to

1) Po ponownym podłączeniu do prądu i tak są błędy extroota:

[    0.000000]   Normal   0x00000000 -> 0x00002000
[    0.000000] Movable zone start PFN for each node
[    0.000000] Early memory PFN ranges
[    0.000000]     0: 0x00000000 -> 0x00002000
[    0.000000] On node 0 totalpages: 8192
[    0.000000] free_area_init_node: node 0, pgdat 80258750, node_mem_map 81000000
[    0.000000]   Normal zone: 64 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 8128 pages, LIFO batch:0
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 8128
[    0.000000] Kernel command line:  board=3G-6200N console=ttyS1,57600 mtdparts=physmap-flash.0:192k(u-boot)ro,64k(u-boot-env)ro,64k(factory)ro,896k(kernel),2752k(rootfs),128k@0x3e0000(cimage)ro,3648k@0x50000(firmware) rootfstype=squashfs,jffs2
[    0.000000] PID hash table entries: 128 (order: -3, 512 bytes)
[    0.000000] Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000000] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
[    0.000000] Primary data cache 16kB, 4-way, VIPT, no aliases, linesize 32 bytes
[    0.000000] Writing ErrCtl register=0004e37a
[    0.000000] Readback ErrCtl register=0004e37a
[    0.000000] Memory: 29652k/32768k available (2059k kernel code, 3116k reserved, 343k data, 176k init, 0k highmem)
[    0.000000] SLUB: Genslabs=9, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] NR_IRQS:48
[    0.000000] console [ttyS1] enabled, bootconsole disabled
[    0.010000] Calibrating delay loop... 212.58 BogoMIPS (lpj=1062912)
[    0.090000] pid_max: default: 32768 minimum: 301
[    0.090000] Mount-cache hash table entries: 512
[    0.100000] NET: Registered protocol family 16
[    0.110000] MIPS: machine is Edimax 3g-6200n
[    0.120000] gpiochip_add: registered GPIOs 0 to 23 on device: RT305X-GPIO0
[    0.130000] gpiochip_add: registered GPIOs 24 to 39 on device: RT305X-GPIO1
[    0.140000] gpiochip_add: registered GPIOs 40 to 51 on device: RT305X-GPIO2
[    0.170000] bio: create slab <bio-0> at 0
[    0.180000] Switching to clocksource MIPS
[    0.190000] NET: Registered protocol family 2
[    0.200000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.220000] TCP established hash table entries: 1024 (order: 1, 8192 bytes)
[    0.230000] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[    0.250000] TCP: Hash tables configured (established 1024 bind 1024)
[    0.260000] TCP reno registered
[    0.260000] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.280000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.290000] NET: Registered protocol family 1
[    0.340000] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.360000] JFFS2 version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    0.380000] msgmni has been set to 57
[    0.390000] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
[    0.400000] io scheduler noop registered
[    0.410000] io scheduler deadline registered (default)
[    0.420000] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[    0.440000] serial8250: ttyS0 at MMIO 0x10000500 (irq = 13) is a 16550A
[    0.450000] serial8250: ttyS1 at MMIO 0x10000c00 (irq = 20) is a 16550A
[    0.480000] physmap platform flash device: 00800000 at bf000000
[    0.490000] physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank. Manufacturer ID 0x0000c2 Chip ID 0x0022a8
[    0.510000] physmap-flash.0: Found an alias at 0x400000 for the chip at 0x0
[    0.510000] Amd/Fujitsu Extended Query Table at 0x0040
[    0.520000]   Amd/Fujitsu Extended Query version 1.1.
[    0.530000] number of CFI chips: 1
[    0.540000] 7 cmdlinepart partitions found on MTD device physmap-flash.0
[    0.550000] Creating 7 MTD partitions on "physmap-flash.0":
[    0.570000] 0x000000000000-0x000000030000 : "u-boot"
[    0.580000] 0x000000030000-0x000000040000 : "u-boot-env"
[    0.600000] 0x000000040000-0x000000050000 : "factory"
[    0.610000] 0x000000050000-0x000000130000 : "kernel"
[    0.620000] 0x000000130000-0x0000003e0000 : "rootfs"
[    0.640000] mtd: partition "rootfs" set to be root filesystem
[    0.650000] mtd: partition "rootfs_data" created automatically, ofs=360000, len=80000
[    0.670000] 0x000000360000-0x0000003e0000 : "rootfs_data"
[    0.680000] 0x0000003e0000-0x000000400000 : "cimage"
[    0.700000] 0x000000050000-0x0000003e0000 : "firmware"
[    0.720000] ramips-wdt ramips-wdt: timeout value must be 0 < timeout <= 40, using 40
[    0.740000] TCP cubic registered
[    0.750000] NET: Registered protocol family 17
[    0.760000] Bridge firewalling registered
[    0.770000] 8021q: 802.1Q VLAN Support v1.8
[    0.780000] VFS: Mounted root (squashfs filesystem) readonly on device 31:4.
[    0.800000] Freeing unused kernel memory: 176k freed
[    3.400000] input: gpio-keys-polled as /devices/platform/gpio-keys-polled/input/input0
[    3.550000] Button Hotplug driver version 0.4.1
[    3.800000] Registered led device: edimax:green:power
[    3.800000] Registered led device: edimax:amber:wlan
[    3.800000] Registered led device: edimax:blue:3g
[    7.150000] JFFS2 notice: (395) jffs2_build_xattr_subsystem: complete building xattr subsystem, 1 of xdatum (1 unchecked, 0 orphan) and 8 of xref (0 dead, 3 orphan) found.
[    8.250000] SCSI subsystem initialized
[    8.450000] usbcore: registered new interface driver usbfs
[    8.460000] usbcore: registered new interface driver hub
[    8.470000] usbcore: registered new device driver usb
[    8.950000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    8.990000] dwc_otg: version 2.72a 24-JUN-2008
[    9.000000] dwc_otg: Core Release: 2.66a
[    9.210000] dwc_otg: Periodic Transfer Interrupt Enhancement - disabled
[    9.220000] dwc_otg: Multiprocessor Interrupt Enhancement - disabled
[    9.240000] dwc_otg: Using DMA mode
[    9.240000] dwc_otg: Device using Buffer DMA mode
[    9.250000] dwc_otg dwc_otg.0: DWC OTG Controller
[    9.260000] dwc_otg dwc_otg.0: new USB bus registered, assigned bus number 1
[    9.280000] dwc_otg dwc_otg.0: irq 26, io mem 0x101c0000
[    9.290000] dwc_otg: Init: Port Power? op_state=1
[    9.300000] dwc_otg: Init: Power Port (0)
[    9.310000] hub 1-0:1.0: USB hub found
[    9.310000] hub 1-0:1.0: 1 port detected
[    9.350000] Initializing USB Mass Storage driver...
[    9.360000] usbcore: registered new interface driver usb-storage
[    9.370000] USB Mass Storage support registered.
[    9.700000] usb 1-1: new high-speed USB device number 2 using dwc_otg
[    9.910000] scsi0 : usb-storage 1-1:1.0
[    9.930000] scsi1 : usb-storage 1-1:1.1
[   10.920000] scsi 0:0:0:0: CD-ROM            HUAWEI   Mass Storage     2.31 PQ: 0 ANSI: 2
[   10.940000] scsi 1:0:0:0: Direct-Access     HUAWEI   TF CARD Storage  2.31 PQ: 0 ANSI: 2
[   10.960000] sd 1:0:0:0: [sda] 7744512 512-byte logical blocks: (3.96 GB/3.69 GiB)
[   10.980000] sd 1:0:0:0: [sda] Write Protect is off
[   10.990000] sd 1:0:0:0: [sda] Mode Sense: 0f 00 00 00
[   11.000000] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   11.040000]  sda: sda1
[   11.050000] sd 1:0:0:0: [sda] Attached SCSI removable disk
[   30.190000] EXT4-fs (sda1): recovery complete
[   30.200000] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[   31.710000] Loading modules backported from Linux version master-2014-01-23-0-g62c147d
[   31.730000] Backport generated by backports.git backports-20140124-0-g1256d3e
[   32.000000] cfg80211: Calling CRDA to update world regulatory domain
[   32.020000] cfg80211: World regulatory domain updated:
[   32.030000] cfg80211:  DFS Master region: unset
[   32.040000] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[   32.050000] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[   32.070000] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[   32.090000] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[   32.100000] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz), (300 mBi, 2000 mBm)
[   32.120000] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (300 mBi, 2000 mBm)
[   32.130000] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm)
[   33.280000] ieee80211 phy0: rt2x00lib_request_eeprom_file: Info - Loading EEPROM data from 'RT305X.eeprom'.
[   33.480000] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 2872, rev 0200 detected
[   33.500000] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0005 detected
[   33.510000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[   33.520000] Registered led device: rt2800soc-phy0::radio
[   33.520000] Registered led device: rt2800soc-phy0::assoc
[   33.520000] Registered led device: rt2800soc-phy0::quality
[   34.040000] Error: Driver 'gpio-keys-polled' is already registered, aborting...
[   34.260000] PPP generic driver version 2.4.2
[   34.470000] tun: Universal TUN/TAP device driver, 1.6
[   34.480000] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[   34.690000] ip_tables: (C) 2000-2006 Netfilter Core Team
[   35.230000] NET: Registered protocol family 24
[   35.470000] nf_conntrack version 0.5.0 (466 buckets, 1864 max)
[   36.520000] usbcore: registered new interface driver huawei_ether
[   36.630000] usbcore: registered new interface driver usbserial
[   36.650000] USB Serial support registered for generic
[   36.660000] usbcore: registered new interface driver usbserial_generic
[   36.670000] usbserial: USB Serial Driver core
[   36.750000] usbcore: registered new interface driver cdc_wdm
[   36.800000] usbcore: registered new interface driver cdc_ether
[   36.910000] usbcore: registered new interface driver cdc_ncm
[   36.950000] usbcore: registered new interface driver qmi_wwan
[   37.010000] USB Serial support registered for GSM modem (1-port)
[   37.020000] usbcore: registered new interface driver option
[   37.030000] option: v0.7.2:USB Driver for GSM modems
[   45.060000] device eth0.1 entered promiscuous mode
[   45.070000] device eth0 entered promiscuous mode
[   45.080000] br-lan: port 1(eth0.1) entered forwarding state
[   45.090000] br-lan: port 1(eth0.1) entered forwarding state
[   47.090000] br-lan: port 1(eth0.1) entered forwarding state
[   48.390000] cfg80211: Calling CRDA for country: PL
[   48.400000] cfg80211: Regulatory domain changed to country: PL
[   48.410000] cfg80211:  DFS Master region: ETSI
[   48.420000] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[   48.430000] cfg80211:   (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
[   48.450000] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm)
[   48.460000] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz), (N/A, 2000 mBm)
[   48.480000] cfg80211:   (5490000 KHz - 5710000 KHz @ 80000 KHz), (N/A, 2700 mBm)
[   48.490000] cfg80211:   (57240000 KHz - 65880000 KHz @ 2160000 KHz), (N/A, 4000 mBm)
[   51.260000] device wlan0 entered promiscuous mode
[   61.660000] br-lan: port 2(wlan0) entered forwarding state
[   61.670000] br-lan: port 2(wlan0) entered forwarding state
[   63.670000] br-lan: port 2(wlan0) entered forwarding state
[   73.480000] ramips-wdt: timeout value 60 must be 0 < timeout <= 40, using 40
[   77.790000] hub 1-0:1.0: port 1 disabled by hub (EMI?), re-enabling...
[   77.800000] usb 1-1: USB disconnect, device number 2
[   77.820000] sd 1:0:0:0: [sda] Synchronizing SCSI cache
[   77.830000] sd 1:0:0:0: [sda]  Result: hostbyte=0x01 driverbyte=0x00
[   78.180000] usb 1-1: new high-speed USB device number 3 using dwc_otg
[   78.400000] option 1-1:1.1: GSM modem (1-port) converter detected
[   78.410000] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
[   78.430000] scsi2 : usb-storage 1-1:1.3
[   78.440000] scsi3 : usb-storage 1-1:1.4
[   79.440000] scsi 2:0:0:0: CD-ROM            HUAWEI   Mass Storage     2.31 PQ: 0 ANSI: 2
[   79.460000] scsi 3:0:0:0: Direct-Access     HUAWEI   TF CARD Storage  2.31 PQ: 0 ANSI: 2
[   79.480000] sd 3:0:0:0: [sdb] 7744512 512-byte logical blocks: (3.96 GB/3.69 GiB)
[   79.510000] sd 3:0:0:0: [sdb] Write Protect is off
[   79.520000] sd 3:0:0:0: [sdb] Mode Sense: 0f 00 00 00
[   79.520000] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   79.560000]  sdb: sdb1
[   79.570000] sd 3:0:0:0: [sdb] Attached SCSI removable disk
[  110.920000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #448: comm hotplug-call: reading directory lblock 0
[  112.860000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #448: comm hotplug-call: reading directory lblock 0
[  114.170000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #12: comm dropbear: reading directory lblock 0
[  114.260000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #12: comm ash: reading directory lblock 0
[  114.290000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #12: comm ash: reading directory lblock 0
[  114.340000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #960: comm ash: reading directory lblock 0
[  114.400000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #232: comm ash: reading directory lblock 0
[  114.430000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #128: comm ash: reading directory lblock 0
[  114.480000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #960: comm ash: reading directory lblock 0
[  114.510000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #128: comm ash: reading directory lblock 0
[  114.540000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #12: comm ash: reading directory lblock 0
[  114.580000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #128: comm ash: reading directory lblock 0
[  114.620000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #128: comm ash: reading directory lblock 0
[  114.650000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #12: comm ash: reading directory lblock 0
[  114.680000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #232: comm ash: reading directory lblock 0
[  115.000000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #960: comm sysinfo.sh: reading directory lblock 0
[  115.030000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #232: comm sysinfo.sh: reading directory lblock 0
[  115.070000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #128: comm sysinfo.sh: reading directory lblock 0
[  115.230000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #960: comm sysinfo.sh: reading directory lblock 0
[  115.310000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #829: comm df: reading directory lblock 0
[  115.340000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #829: comm df: reading directory lblock 0
[  115.370000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #829: comm df: reading directory lblock 0
[  115.400000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #829: comm df: reading directory lblock 0
[  115.440000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #829: comm df: reading directory lblock 0
[  115.860000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #829: comm uci: reading directory lblock 0
[  115.890000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #829: comm uci: reading directory lblock 0
[  115.910000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #829: comm uci: reading directory lblock 0
[  115.940000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #829: comm uci: reading directory lblock 0
[  116.020000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #960: comm sysinfo.sh: reading directory lblock 0
[  116.060000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #232: comm sysinfo.sh: reading directory lblock 0
[  116.590000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #960: comm sysinfo.sh: reading directory lblock 0
[  116.620000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #128: comm sysinfo.sh: reading directory lblock 0
[  116.750000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #829: comm ash: reading directory lblock 0
[  121.310000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #448: comm hotplug-call: reading directory lblock 0
[  121.690000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #448: comm hotplug-call: reading directory lblock 0
[  122.700000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #960: comm hotplug-call: reading directory lblock 0
[  125.160000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #960: comm hotplug-call: reading directory lblock 0
[  125.180000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #2: comm mkdir: reading directory lblock 0
[  125.200000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #232: comm hotplug-call: reading directory lblock 0
[  125.230000] EXT4-fs error (device sda1): ext4_read_inode_bitmap:161: comm mkdir: Cannot read inode bitmap - block_group = 0, inode_bitmap = 254
[  125.250000] EXT4-fs error (device sda1) in ext4_new_inode:941: IO failure
[  125.270000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #128: comm hotplug-call: reading directory lblock 0
[  128.590000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #47: comm uhttpd: reading directory lblock 0
[  131.060000] Buffer I/O error on device sda1, logical block 425984
[  131.060000] lost page write due to I/O error on sda1
[  131.080000] JBD2: I/O error detected when updating journal superblock for sda1-8.
[  131.090000] Aborting journal on device sda1-8.
[  131.100000] Buffer I/O error on device sda1, logical block 425984
[  131.100000] lost page write due to I/O error on sda1
[  131.130000] JBD2: I/O error detected when updating journal superblock for sda1-8.
[  131.490000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #960: comm ash: reading directory lblock 0

Dopiero reboot przy włączonym prądzie pomaga:

root@OpenWrt:~# dmesg
[    0.000000] Linux version 3.3.8 (cezary@eko.one.pl) (gcc version 4.6.3 20120201 (prerelease) (Linaro GCC 4.6-2012.02) ) #2 Sat Mar 15 11:29:43 CET 2014
[    0.000000] prom: fw_arg0=00000001, fw_arg1=01f57fb0, fw_arg2=01f583b0, fw_arg3=00000000
[    0.000000] env[0]: memsize=32
[    0.000000] env[1]: initrd_start=0x00000000
[    0.000000] env[2]: initrd_size=0x0
[    0.000000] env[3]: flash_start=0xBFC00000
[    0.000000] env[4]: flash_size=0x400000
[    0.000000] env[0]: memsize=32
[    0.000000] env[1]: initrd_start=0x00000000
[    0.000000] env[2]: initrd_size=0x0
[    0.000000] env[3]: flash_start=0xBFC00000
[    0.000000] env[4]: flash_size=0x400000
[    0.000000] bootconsole [early0] enabled
[    0.000000] CPU revision is: 0001964c (MIPS 24KEc)
[    0.000000] Ralink RT3052 id:1 rev:2 running at 320.00 MHz
[    0.000000] Determined physical RAM map:
[    0.000000]  memory: 02000000 @ 00000000 (usable)
[    0.000000] Initrd not found or empty - disabling initrd
[    0.000000] Zone PFN ranges:
[    0.000000]   Normal   0x00000000 -> 0x00002000
[    0.000000] Movable zone start PFN for each node
[    0.000000] Early memory PFN ranges
[    0.000000]     0: 0x00000000 -> 0x00002000
[    0.000000] On node 0 totalpages: 8192
[    0.000000] free_area_init_node: node 0, pgdat 80258750, node_mem_map 81000000
[    0.000000]   Normal zone: 64 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 8128 pages, LIFO batch:0
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 8128
[    0.000000] Kernel command line:  board=3G-6200N console=ttyS1,57600 mtdparts=physmap-flash.0:192k(u-boot)ro,64k(u-boot-env)ro,64k(factory)ro,896k(kernel),2752k(rootfs),128k@0x3e0000(cimage)ro,3648k@0x50000(firmware) rootfstype=squashfs,jffs2
[    0.000000] PID hash table entries: 128 (order: -3, 512 bytes)
[    0.000000] Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000000] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
[    0.000000] Primary data cache 16kB, 4-way, VIPT, no aliases, linesize 32 bytes
[    0.000000] Writing ErrCtl register=0004e370
[    0.000000] Readback ErrCtl register=0004e370
[    0.000000] Memory: 29652k/32768k available (2059k kernel code, 3116k reserved, 343k data, 176k init, 0k highmem)
[    0.000000] SLUB: Genslabs=9, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] NR_IRQS:48
[    0.000000] console [ttyS1] enabled, bootconsole disabled
[    0.010000] Calibrating delay loop... 212.58 BogoMIPS (lpj=1062912)
[    0.090000] pid_max: default: 32768 minimum: 301
[    0.090000] Mount-cache hash table entries: 512
[    0.100000] NET: Registered protocol family 16
[    0.110000] MIPS: machine is Edimax 3g-6200n
[    0.120000] gpiochip_add: registered GPIOs 0 to 23 on device: RT305X-GPIO0
[    0.130000] gpiochip_add: registered GPIOs 24 to 39 on device: RT305X-GPIO1
[    0.140000] gpiochip_add: registered GPIOs 40 to 51 on device: RT305X-GPIO2
[    0.170000] bio: create slab <bio-0> at 0
[    0.180000] Switching to clocksource MIPS
[    0.190000] NET: Registered protocol family 2
[    0.200000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.220000] TCP established hash table entries: 1024 (order: 1, 8192 bytes)
[    0.230000] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[    0.250000] TCP: Hash tables configured (established 1024 bind 1024)
[    0.260000] TCP reno registered
[    0.260000] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.280000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.290000] NET: Registered protocol family 1
[    0.340000] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.360000] JFFS2 version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    0.380000] msgmni has been set to 57
[    0.390000] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
[    0.400000] io scheduler noop registered
[    0.410000] io scheduler deadline registered (default)
[    0.420000] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[    0.440000] serial8250: ttyS0 at MMIO 0x10000500 (irq = 13) is a 16550A
[    0.450000] serial8250: ttyS1 at MMIO 0x10000c00 (irq = 20) is a 16550A
[    0.480000] physmap platform flash device: 00800000 at bf000000
[    0.490000] physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank. Manufacturer ID 0x0000c2 Chip ID 0x0022a8
[    0.510000] physmap-flash.0: Found an alias at 0x400000 for the chip at 0x0
[    0.510000] Amd/Fujitsu Extended Query Table at 0x0040
[    0.520000]   Amd/Fujitsu Extended Query version 1.1.
[    0.530000] number of CFI chips: 1
[    0.540000] 7 cmdlinepart partitions found on MTD device physmap-flash.0
[    0.550000] Creating 7 MTD partitions on "physmap-flash.0":
[    0.570000] 0x000000000000-0x000000030000 : "u-boot"
[    0.580000] 0x000000030000-0x000000040000 : "u-boot-env"
[    0.600000] 0x000000040000-0x000000050000 : "factory"
[    0.610000] 0x000000050000-0x000000130000 : "kernel"
[    0.620000] 0x000000130000-0x0000003e0000 : "rootfs"
[    0.640000] mtd: partition "rootfs" set to be root filesystem
[    0.650000] mtd: partition "rootfs_data" created automatically, ofs=360000, len=80000
[    0.670000] 0x000000360000-0x0000003e0000 : "rootfs_data"
[    0.680000] 0x0000003e0000-0x000000400000 : "cimage"
[    0.700000] 0x000000050000-0x0000003e0000 : "firmware"
[    0.720000] ramips-wdt ramips-wdt: timeout value must be 0 < timeout <= 40, using 40
[    0.740000] TCP cubic registered
[    0.750000] NET: Registered protocol family 17
[    0.760000] Bridge firewalling registered
[    0.770000] 8021q: 802.1Q VLAN Support v1.8
[    0.780000] VFS: Mounted root (squashfs filesystem) readonly on device 31:4.
[    0.800000] Freeing unused kernel memory: 176k freed
[    3.400000] input: gpio-keys-polled as /devices/platform/gpio-keys-polled/input/input0
[    3.550000] Button Hotplug driver version 0.4.1
[    3.800000] Registered led device: edimax:green:power
[    3.800000] Registered led device: edimax:amber:wlan
[    3.800000] Registered led device: edimax:blue:3g
[    7.150000] JFFS2 notice: (395) jffs2_build_xattr_subsystem: complete building xattr subsystem, 1 of xdatum (1 unchecked, 0 orphan) and 8 of xref (0 dead, 3 orphan) found.
[    8.250000] SCSI subsystem initialized
[    8.450000] usbcore: registered new interface driver usbfs
[    8.460000] usbcore: registered new interface driver hub
[    8.480000] usbcore: registered new device driver usb
[    8.950000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    8.990000] dwc_otg: version 2.72a 24-JUN-2008
[    9.000000] dwc_otg: Core Release: 2.66a
[    9.210000] dwc_otg: Periodic Transfer Interrupt Enhancement - disabled
[    9.220000] dwc_otg: Multiprocessor Interrupt Enhancement - disabled
[    9.240000] dwc_otg: Using DMA mode
[    9.240000] dwc_otg: Device using Buffer DMA mode
[    9.250000] dwc_otg dwc_otg.0: DWC OTG Controller
[    9.260000] dwc_otg dwc_otg.0: new USB bus registered, assigned bus number 1
[    9.280000] dwc_otg dwc_otg.0: irq 26, io mem 0x101c0000
[    9.290000] dwc_otg: Init: Port Power? op_state=1
[    9.300000] dwc_otg: Init: Power Port (0)
[    9.310000] hub 1-0:1.0: USB hub found
[    9.320000] hub 1-0:1.0: 1 port detected
[    9.350000] Initializing USB Mass Storage driver...
[    9.360000] usbcore: registered new interface driver usb-storage
[    9.370000] USB Mass Storage support registered.
[    9.700000] usb 1-1: new high-speed USB device number 2 using dwc_otg
[    9.920000] scsi0 : usb-storage 1-1:1.3
[    9.930000] scsi1 : usb-storage 1-1:1.4
[   10.920000] scsi 0:0:0:0: CD-ROM            HUAWEI   Mass Storage     2.31 PQ: 0 ANSI: 2
[   10.940000] scsi 1:0:0:0: Direct-Access     HUAWEI   TF CARD Storage  2.31 PQ: 0 ANSI: 2
[   10.960000] sd 1:0:0:0: [sda] 7744512 512-byte logical blocks: (3.96 GB/3.69 GiB)
[   10.990000] sd 1:0:0:0: [sda] Write Protect is off
[   11.000000] sd 1:0:0:0: [sda] Mode Sense: 0f 00 00 00
[   11.000000] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   11.040000]  sda: sda1
[   11.050000] sd 1:0:0:0: [sda] Attached SCSI removable disk
[   30.150000] EXT4-fs (sda1): recovery complete
[   30.160000] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[   31.710000] Loading modules backported from Linux version master-2014-01-23-0-g62c147d
[   31.730000] Backport generated by backports.git backports-20140124-0-g1256d3e
[   32.010000] cfg80211: Calling CRDA to update world regulatory domain
[   32.020000] cfg80211: World regulatory domain updated:
[   32.030000] cfg80211:  DFS Master region: unset
[   32.040000] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[   32.060000] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[   32.070000] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[   32.090000] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[   32.100000] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz), (300 mBi, 2000 mBm)
[   32.120000] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (300 mBi, 2000 mBm)
[   32.130000] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm)
[   33.280000] ieee80211 phy0: rt2x00lib_request_eeprom_file: Info - Loading EEPROM data from 'RT305X.eeprom'.
[   33.480000] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 2872, rev 0200 detected
[   33.500000] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0005 detected
[   33.510000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[   33.510000] Registered led device: rt2800soc-phy0::radio
[   33.510000] Registered led device: rt2800soc-phy0::assoc
[   33.510000] Registered led device: rt2800soc-phy0::quality
[   34.040000] Error: Driver 'gpio-keys-polled' is already registered, aborting...
[   34.250000] PPP generic driver version 2.4.2
[   34.460000] tun: Universal TUN/TAP device driver, 1.6
[   34.470000] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[   34.680000] ip_tables: (C) 2000-2006 Netfilter Core Team
[   35.230000] NET: Registered protocol family 24
[   35.470000] nf_conntrack version 0.5.0 (466 buckets, 1864 max)
[   36.520000] usbcore: registered new interface driver huawei_ether
[   36.640000] usbcore: registered new interface driver usbserial
[   36.650000] USB Serial support registered for generic
[   36.660000] usbcore: registered new interface driver usbserial_generic
[   36.680000] usbserial: USB Serial Driver core
[   36.760000] usbcore: registered new interface driver cdc_wdm
[   36.810000] usbcore: registered new interface driver cdc_ether
[   36.910000] usbcore: registered new interface driver cdc_ncm
[   36.960000] usbcore: registered new interface driver qmi_wwan
[   37.010000] USB Serial support registered for GSM modem (1-port)
[   37.030000] option 1-1:1.1: GSM modem (1-port) converter detected
[   37.040000] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
[   37.050000] usbcore: registered new interface driver option
[   37.070000] option: v0.7.2:USB Driver for GSM modems
[   45.640000] device eth0.1 entered promiscuous mode
[   45.650000] device eth0 entered promiscuous mode
[   45.670000] br-lan: port 1(eth0.1) entered forwarding state
[   45.680000] br-lan: port 1(eth0.1) entered forwarding state
[   47.680000] br-lan: port 1(eth0.1) entered forwarding state
[   49.320000] cfg80211: Calling CRDA for country: PL
[   49.330000] cfg80211: Regulatory domain changed to country: PL
[   49.340000] cfg80211:  DFS Master region: ETSI
[   49.350000] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[   49.360000] cfg80211:   (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
[   49.380000] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm)
[   49.390000] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz), (N/A, 2000 mBm)
[   49.410000] cfg80211:   (5490000 KHz - 5710000 KHz @ 80000 KHz), (N/A, 2700 mBm)
[   49.420000] cfg80211:   (57240000 KHz - 65880000 KHz @ 2160000 KHz), (N/A, 4000 mBm)
[   53.210000] device wlan0 entered promiscuous mode
[   59.930000] ramips-wdt: timeout value 60 must be 0 < timeout <= 40, using 40
[   63.610000] br-lan: port 2(wlan0) entered forwarding state
[   63.620000] br-lan: port 2(wlan0) entered forwarding state
[   65.620000] br-lan: port 2(wlan0) entered forwarding state

2) Ale i tak modem nie jest w pełni rozpoznany i nie ma internetu:

root@OpenWrt:~# cat /sys/kernel/debug/usb/devices

T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480  MxCh= 1
B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev= 3.03
S:  Manufacturer=Linux 3.3.8 dwc_otg
S:  Product=DWC OTG Controller
S:  SerialNumber=dwc_otg.0
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=480  MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=12d1 ProdID=1506 Rev= 1.02
S:  Manufacturer=HUAWEI Technology
S:  Product=HUAWEI Mobile
C:* #Ifs= 5 Cfg#= 1 Atr=80 MxPwr=500mA
I:* If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=02 Prot=10 Driver=(none)
E:  Ad=81(I) Atr=03(Int.) MxPS=  64 Ivl=2ms
E:  Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms
I:* If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=02 Prot=12 Driver=option
E:  Ad=83(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms
I:  If#= 2 Alt= 0 #EPs= 1 Cls=ff(vend.) Sub=02 Prot=16 Driver=huawei_ether
E:  Ad=84(I) Atr=03(Int.) MxPS=  64 Ivl=2ms
I:* If#= 2 Alt= 1 #EPs= 3 Cls=ff(vend.) Sub=02 Prot=16 Driver=huawei_ether
E:  Ad=84(I) Atr=03(Int.) MxPS=  64 Ivl=2ms
E:  Ad=85(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=03(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms
I:* If#= 3 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
E:  Ad=04(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=86(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 4 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
E:  Ad=05(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=87(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms

przy konfiguracji wanu:

root@OpenWrt:~# uci show network
network.loopback=interface
network.loopback.ifname=lo
network.loopback.proto=static
network.loopback.ipaddr=127.0.0.1
network.loopback.netmask=255.0.0.0
network.lan=interface
network.lan.ifname=eth0.1
network.lan.type=bridge
network.lan.proto=static
network.lan.netmask=255.255.255.0
network.lan.macaddr=00:11:22:33:44:55
network.lan.ipaddr=192.168.2.1
network.@switch[0]=switch
network.@switch[0].name=rt305x
network.@switch[0].reset=1
network.@switch[0].enable_vlan=1
network.@switch_vlan[0]=switch_vlan
network.@switch_vlan[0].device=rt305x
network.@switch_vlan[0].vlan=1
network.@switch_vlan[0].ports=0 1 2 3 5  6t
network.@switch_vlan[1]=switch_vlan
network.@switch_vlan[1].device=rt305x
network.@switch_vlan[1].vlan=2
network.@switch_vlan[1].ports=4  6t
network.wan=interface
network.wan._orig_ifname=wwan0
network.wan._orig_bridge=false
network.wan.proto=3g
network.wan.service=umts
network.wan.apn=eranet
network.wan.device=/dev/ttyUSB0

12 Odpowiedź przez Cezary

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

Odp: Potrzebny reboot po włączeniu z extroot

Przecież masz driver załadowany, czego nie ma do internetu?

I to o czym rozmawiamy nie ma nic jeszcze wspólnego z extrootem. Kod przełączający musisz sobie poszukać dla tego modemu.

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

Cezary's Strona

13 Odpowiedź przez jacekdob

  • Zarejestrowany: 2014-03-30
  • Posty: 13

Odp: Potrzebny reboot po włączeniu z extroot

A to?

If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=02 Prot=10 Driver=(none)

Przy tak załadowanych opcjach WAN się nie łączy.

Jak się nazywa ten tryb do którego go trzeba przełączyć?

14 Odpowiedź przez Cezary

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

Odp: Potrzebny reboot po włączeniu z extroot

Pusta linia bez drivera. jak widzisz siedzi na Sub=02 Prot=12, a tak w ogóle to przez ncm powinieneś się przez niego łączyć.

Przełączyć na stałe do właściwego trybu pracy. Możesz też coś takiego mojego sprawdzić: http://eko.one.pl/forum/viewtopic.php?pid=65180#p65180

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

Cezary's Strona

15 Odpowiedź przez jacekdob (edytowany przez jacekdob 2014-04-13 00:02:44)

  • Zarejestrowany: 2014-03-30
  • Posty: 13

Odp: Potrzebny reboot po włączeniu z extroot

Usunąłem vendor=0x12d1 product=0x1506 oraz wgrałem /lib/preinit/49_usb_modeswitch do pamięci w routerze.

Niestety po pierwszym uruchomienu po włączeniu zasilania są błędy extroota.

Po zrebootowaniu nie ma internetu przez modem.

Nie bardzo wiem co dalej...

Jak mam się połączyć przez ncm skoro 62-usb-net-cdc-ncm jest przed 65-usb-serial-option a i tak ładuje się dla modemu option?

Jak zakomentuję option w ogóle, to modem nie w ogóle żadnego sterownika...

16 Odpowiedź przez Cezary

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

Odp: Potrzebny reboot po włączeniu z extroot

I jeszcze wywal ten driver huawei, bo albo on, albo ncm.

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

Cezary's Strona

17 Odpowiedź przez Gruberek

  • Skąd: Piotrków Tryb.
  • Zarejestrowany: 2013-08-04
  • Posty: 712

Odp: Potrzebny reboot po włączeniu z extroot

Mam taki sam problem na routerze Linksys WRT160NL i modemie Huawei E173. W modemie jest karta micro sd na której jest extroot. Wszystko działa idealnie. Jednak po wyłączeniu routera spowodowanym brakiem zasilania extroot nie działa poprawnie po ponownym uruchomieniu. Niby wszystko jest zamontowane ale nie wczytuje się konfiguracja. Wystarczy zwykły reboot i wszystko wraca do normy.

Home: ZyXEL NBG6817 (OpenWrt)
NAS: HP ProLiant MicroServer Gen8 E3-1265L V2, 16 GB (PVE)

Gruberek's Strona

18 Odpowiedź przez Cezary

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

Odp: Potrzebny reboot po włączeniu z extroot

Modem masz przełączony? Akurat E173 można ładnie przełączyć.

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

Cezary's Strona

19 Odpowiedź przez jacekdob

  • Zarejestrowany: 2014-03-30
  • Posty: 13

Odp: Potrzebny reboot po włączeniu z extroot

No właśnie u mnie dokładnie to samo.

Okazało się, że wcześniej wgrałem /lib/preinit/49_usb_modeswitch, ale nie zainstalowałem usb-modeswitch i usb-modeswitch-data.

Po zainstalowaniu router nie uruchamia się z podłączonym modemem i kartą microSD w nim.

Jak ręcznie uruchomiłem skrypt (trochę komentując) to następuje przełączenie.

Co może być nie tak, że modem nie przełącza się przed zamontowaniem extroota?

20 Odpowiedź przez Cezary

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

Odp: Potrzebny reboot po włączeniu z extroot

Co masz w logu /tmp/usb_modeswitch.log jeżeli użyłeś mojego skryptu?

Tym bardziej że e3276 był testowany na tym skrypcie i ponoć działał.

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

Cezary's Strona

21 Odpowiedź przez jacekdob

  • Zarejestrowany: 2014-03-30
  • Posty: 13

Odp: Potrzebny reboot po włączeniu z extroot

Problem jest tylko taki, że router się nie ładuje z tym skryptem, główna lampka cały czas miga...

Czy jak zrobię i failsafe i mount_root to tak jakbym normalnie uruchomił?

Bo wtedy widać jakiś output.

22 Odpowiedź przez Cezary

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

Odp: Potrzebny reboot po włączeniu z extroot

Nie. Wtedy nic nadal się nie uruchamia bo mount_root tylko kontuje partycję, nie uruchamia usług.

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

Cezary's Strona

23 Odpowiedź przez tenobcy

  • Zarejestrowany: 2013-08-14
  • Posty: 450

Odp: Potrzebny reboot po włączeniu z extroot

Znalazł ktoś już rozwiązanie tego problemu? U mnie na modemie E3131 z kartą 32GB nawet restart nie pomaga, w /etc/config są tylko pliki konfiguracyjne dhcp, dropbear, firewall i system a w logach mam:

root@OpenWrt:~# logread
Mon Dec 29 13:58:19 2014 user.emerg syslog: setting up led USB1
Mon Dec 29 13:58:19 2014 user.emerg syslog: setting up led USB2
Mon Dec 29 13:58:19 2014 user.emerg syslog: setting up led WLAN2G
Mon Dec 29 13:58:19 2014 kern.crit kernel: [   24.820000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #262168: comm procd: reading directory lblock 0
Mon Dec 29 13:58:19 2014 user.emerg syslog: - init complete -
Mon Dec 29 13:58:19 2014 kern.info kernel: [   24.950000] usb 1-1.1: new high-speed USB device number 6 using ehci-platform
Mon Dec 29 13:58:19 2014 kern.info kernel: [   25.080000] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Mon Dec 29 13:58:19 2014 kern.warn kernel: [   25.090000] EXT4-fs warning (device sda1): __ext4_read_dirblock:908: error reading directory block (ino 131112, block 0)
Mon Dec 29 13:58:19 2014 kern.info kernel: [   25.110000] IPv6: ADDRCONF(NETDEV_UP): eth0.1: link is not ready
Mon Dec 29 13:58:19 2014 kern.info kernel: [   25.110000] device eth0.1 entered promiscuous mode
Mon Dec 29 13:58:19 2014 kern.info kernel: [   25.120000] device eth0 entered promiscuous mode
Mon Dec 29 13:58:19 2014 kern.info kernel: [   25.120000] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready
Mon Dec 29 13:58:19 2014 daemon.notice netifd: Interface 'lan' is enabled
Mon Dec 29 13:58:19 2014 daemon.notice netifd: Interface 'lan' is setting up now
Mon Dec 29 13:58:19 2014 daemon.notice netifd: Interface 'lan' is now up
Mon Dec 29 13:58:19 2014 daemon.notice netifd: Interface 'loopback' is enabled
Mon Dec 29 13:58:19 2014 daemon.notice netifd: Interface 'loopback' is setting up now
Mon Dec 29 13:58:19 2014 daemon.notice netifd: Interface 'loopback' is now up
Mon Dec 29 13:58:19 2014 kern.info kernel: [   25.140000] IPv6: ADDRCONF(NETDEV_UP): eth0.2: link is not ready
Mon Dec 29 13:58:20 2014 daemon.notice netifd: Interface 'wan' is enabled
Mon Dec 29 13:58:20 2014 daemon.notice netifd: Network device 'lo' link is up
Mon Dec 29 13:58:20 2014 daemon.notice netifd: Interface 'loopback' has link connectivity 
Mon Dec 29 13:58:20 2014 kern.info kernel: [   25.430000] option 1-1.1:1.0: GSM modem (1-port) converter detected
Mon Dec 29 13:58:20 2014 kern.info kernel: [   25.460000] usb 1-1.1: GSM modem (1-port) converter now attached to ttyUSB0
Mon Dec 29 13:58:20 2014 kern.info kernel: [   25.460000] option 1-1.1:1.2: GSM modem (1-port) converter detected
Mon Dec 29 13:58:20 2014 kern.info kernel: [   25.480000] usb 1-1.1: GSM modem (1-port) converter now attached to ttyUSB1
Mon Dec 29 13:58:20 2014 kern.info kernel: [   25.480000] option 1-1.1:1.3: GSM modem (1-port) converter detected
Mon Dec 29 13:58:20 2014 kern.warn kernel: [   25.500000] EXT4-fs warning (device sda1): __ext4_read_dirblock:908: error reading directory block (ino 131112, block 0)
Mon Dec 29 13:58:20 2014 kern.info kernel: [   25.520000] usb 1-1.1: GSM modem (1-port) converter now attached to ttyUSB2
Mon Dec 29 13:58:20 2014 kern.info kernel: [   25.520000] usb-storage 1-1.1:1.4: USB Mass Storage device detected
Mon Dec 29 13:58:20 2014 kern.crit kernel: [   25.540000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #2: comm fw3: reading directory lblock 0
Mon Dec 29 13:58:20 2014 kern.info kernel: [   25.550000] scsi2 : usb-storage 1-1.1:1.4
Mon Dec 29 13:58:20 2014 kern.info kernel: [   25.550000] usb-storage 1-1.1:1.5: USB Mass Storage device detected
Mon Dec 29 13:58:20 2014 kern.crit kernel: [   25.560000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #1048577: comm fw3: reading directory lblock 0
Mon Dec 29 13:58:20 2014 kern.info kernel: [   25.580000] scsi3 : usb-storage 1-1.1:1.5
Mon Dec 29 13:58:20 2014 kern.crit kernel: [   25.580000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #262172: comm fw3: reading directory lblock 0
Mon Dec 29 13:58:20 2014 kern.crit kernel: [   25.600000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #262168: comm fw3: reading directory lblock 0
Mon Dec 29 13:58:20 2014 kern.warn kernel: [   25.610000] EXT4-fs warning (device sda1): __ext4_read_dirblock:908: error reading directory block (ino 131127, block 0)
Mon Dec 29 13:58:20 2014 kern.info kernel: [   25.630000] eth0: link up (1000Mbps/Full duplex)
Mon Dec 29 13:58:20 2014 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Mon Dec 29 13:58:20 2014 daemon.notice netifd: Network device 'eth0' link is up
Mon Dec 29 13:58:20 2014 daemon.notice netifd: VLAN 'eth0.2' link is up
Mon Dec 29 13:58:20 2014 daemon.notice netifd: Interface 'wan' has link connectivity 
Mon Dec 29 13:58:20 2014 daemon.notice netifd: Interface 'wan' is setting up now
Mon Dec 29 13:58:20 2014 daemon.notice netifd: VLAN 'eth0.1' link is up
Mon Dec 29 13:58:20 2014 kern.info kernel: [   25.650000] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Mon Dec 29 13:58:20 2014 kern.info kernel: [   25.650000] br-lan: port 1(eth0.1) entered forwarding state
Mon Dec 29 13:58:20 2014 kern.info kernel: [   25.660000] br-lan: port 1(eth0.1) entered forwarding state
Mon Dec 29 13:58:20 2014 kern.info kernel: [   25.670000] IPv6: ADDRCONF(NETDEV_CHANGE): eth0.1: link becomes ready
Mon Dec 29 13:58:20 2014 kern.info kernel: [   25.670000] IPv6: ADDRCONF(NETDEV_CHANGE): eth0.2: link becomes ready
Mon Dec 29 13:58:20 2014 kern.crit kernel: [   25.700000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #131127: comm ls: reading directory lblock 0
Mon Dec 29 13:58:20 2014 kern.info kernel: [   25.710000] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
Mon Dec 29 13:58:20 2014 daemon.notice netifd: Bridge 'br-lan' link is up
Mon Dec 29 13:58:20 2014 daemon.notice netifd: Interface 'lan' has link connectivity 
Mon Dec 29 13:58:20 2014 kern.warn kernel: [   25.770000] EXT4-fs warning (device sda1): __ext4_read_dirblock:908: error reading directory block (ino 131127, block 0)
Mon Dec 29 13:58:20 2014 kern.crit kernel: [   25.850000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #131111: comm hotplug-call: reading directory lblock 0
Mon Dec 29 13:58:20 2014 kern.warn kernel: [   25.900000] EXT4-fs warning (device sda1): __ext4_read_dirblock:908: error reading directory block (ino 131112, block 0)
Mon Dec 29 13:58:20 2014 kern.crit kernel: [   25.920000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #1441804: comm dhcp.sh: reading directory lblock 0
Mon Dec 29 13:58:20 2014 kern.warn kernel: [   25.970000] EXT4-fs warning (device sda1): __ext4_read_dirblock:908: error reading directory block (ino 131112, block 0)
Mon Dec 29 13:58:20 2014 kern.warn kernel: [   26.040000] EXT4-fs warning (device sda1): __ext4_read_dirblock:908: error reading directory block (ino 131127, block 0)
Mon Dec 29 13:58:20 2014 kern.crit kernel: [   26.100000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #1048577: comm netifd: reading directory lblock 0
Mon Dec 29 13:58:20 2014 daemon.notice netifd: wan (1287): udhcpc (v1.22.1) started
Mon Dec 29 13:58:20 2014 kern.crit kernel: [   26.120000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #1441803: comm udhcpc: reading directory lblock 0
Mon Dec 29 13:58:20 2014 kern.warn kernel: [   26.140000] EXT4-fs warning (device sda1): __ext4_read_dirblock:908: error reading directory block (ino 131127, block 0)
Mon Dec 29 13:58:21 2014 kern.warn kernel: [   26.230000] EXT4-fs warning (device sda1): __ext4_read_dirblock:908: error reading directory block (ino 131112, block 0)
Mon Dec 29 13:58:21 2014 kern.warn kernel: [   26.290000] EXT4-fs warning (device sda1): __ext4_read_dirblock:908: error reading directory block (ino 131127, block 0)
Mon Dec 29 13:58:21 2014 kern.crit kernel: [   26.320000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #131073: comm dhcp.script: reading directory lblock 0
Mon Dec 29 13:58:21 2014 daemon.notice netifd: wan (1287): Sending discover...
Mon Dec 29 13:58:21 2014 kern.warn kernel: [   26.380000] EXT4-fs warning (device sda1): __ext4_read_dirblock:908: error reading directory block (ino 131127, block 0)
Mon Dec 29 13:58:21 2014 kern.warn kernel: [   26.440000] EXT4-fs warning (device sda1): __ext4_read_dirblock:908: error reading directory block (ino 131112, block 0)
Mon Dec 29 13:58:21 2014 kern.warn kernel: [   26.480000] EXT4-fs warning (device sda1): __ext4_read_dirblock:908: error reading directory block (ino 131112, block 0)
Mon Dec 29 13:58:21 2014 kern.notice kernel: [   26.560000] scsi 2:0:0:0: CD-ROM            HUAWEI   Mass Storage     2.31 PQ: 0 ANSI: 2
Mon Dec 29 13:58:21 2014 kern.notice kernel: [   26.580000] scsi 3:0:0:0: Direct-Access     HUAWEI   TF CARD Storage  2.31 PQ: 0 ANSI: 2
Mon Dec 29 13:58:21 2014 kern.notice kernel: [   26.590000] sd 3:0:0:0: [sdc] 61765632 512-byte logical blocks: (31.6 GB/29.4 GiB)
Mon Dec 29 13:58:21 2014 kern.notice kernel: [   26.610000] sd 3:0:0:0: [sdc] Write Protect is off
Mon Dec 29 13:58:21 2014 kern.debug kernel: [   26.610000] sd 3:0:0:0: [sdc] Mode Sense: 0f 00 00 00
Mon Dec 29 13:58:21 2014 kern.notice kernel: [   26.610000] sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Mon Dec 29 13:58:21 2014 kern.info kernel: [   26.630000]  sdc: sdc1
Mon Dec 29 13:58:21 2014 kern.notice kernel: [   26.660000] sd 3:0:0:0: [sdc] Attached SCSI removable disk
Mon Dec 29 13:58:21 2014 kern.crit kernel: [   26.690000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #1048577: comm dnsmasq: reading directory lblock 0
Mon Dec 29 13:58:21 2014 kern.crit kernel: [   26.700000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #262172: comm dnsmasq: reading directory lblock 0
Mon Dec 29 13:58:21 2014 kern.warn kernel: [   26.820000] EXT4-fs warning (device sda1): __ext4_read_dirblock:908: error reading directory block (ino 2, block 0)
Mon Dec 29 13:58:22 2014 kern.info kernel: [   27.660000] br-lan: port 1(eth0.1) entered forwarding state
Mon Dec 29 13:58:22 2014 daemon.notice netifd: wan (1287): Sending select for 192.168.1.11...
Mon Dec 29 13:58:22 2014 daemon.notice netifd: wan (1287): Lease of 192.168.1.11 obtained, lease time 86400
Mon Dec 29 13:58:23 2014 daemon.notice netifd: Interface 'wan6' is enabled
Mon Dec 29 13:58:23 2014 daemon.notice netifd: Network alias 'eth0.2' link is up
Mon Dec 29 13:58:23 2014 daemon.notice netifd: Interface 'wan6' has link connectivity 
Mon Dec 29 13:58:23 2014 daemon.notice netifd: Interface 'wan6' is setting up now
Mon Dec 29 13:58:23 2014 daemon.notice netifd: Interface 'wan' is now up
Mon Dec 29 13:58:23 2014 kern.crit kernel: [   28.280000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #1048577: comm netifd: reading directory lblock 0
Mon Dec 29 13:58:23 2014 kern.crit kernel: [   28.300000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #262172: comm netifd: reading directory lblock 0
Mon Dec 29 13:58:23 2014 kern.crit kernel: [   28.310000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #262168: comm netifd: reading directory lblock 0
Mon Dec 29 13:58:23 2014 kern.crit kernel: [   28.420000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #1441803: comm odhcp6c: reading directory lblock 0
Mon Dec 29 13:58:23 2014 kern.crit kernel: [   28.480000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #131073: comm dhcpv6.script: reading directory lblock 0
Mon Dec 29 13:58:24 2014 kern.crit kernel: [   30.120000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #262168: comm procd: reading directory lblock 0
Mon Dec 29 13:58:25 2014 daemon.info dnsmasq[1367]: started, version 2.71 cachesize 150
Mon Dec 29 13:58:25 2014 daemon.info dnsmasq[1367]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-DNSSEC
Mon Dec 29 13:58:25 2014 daemon.info dnsmasq-dhcp[1367]: DHCP, IP range 192.168.3.100 -- 192.168.3.249, lease time 12h
Mon Dec 29 13:58:25 2014 daemon.info dnsmasq[1367]: using local addresses only for domain lan
Mon Dec 29 13:58:25 2014 daemon.info dnsmasq[1367]: reading /tmp/resolv.conf.auto
Mon Dec 29 13:58:25 2014 daemon.info dnsmasq[1367]: using local addresses only for domain lan
Mon Dec 29 13:58:25 2014 daemon.info dnsmasq[1367]: using nameserver 192.168.1.254#53
Mon Dec 29 13:58:25 2014 daemon.info dnsmasq[1367]: read /etc/hosts - 1 addresses
Mon Dec 29 13:58:25 2014 daemon.info dnsmasq[1367]: read /tmp/hosts/dhcp - 1 addresses
Mon Dec 29 13:58:25 2014 daemon.info dnsmasq-dhcp[1367]: read /etc/ethers - 0 addresses
Mon Dec 29 13:58:25 2014 kern.warn kernel: [   30.680000] EXT4-fs warning (device sda1): __ext4_read_dirblock:908: error reading directory block (ino 2, block 0)
Mon Dec 29 13:58:25 2014 daemon.info dnsmasq[1367]: exiting on receipt of SIGTERM
Mon Dec 29 13:58:25 2014 daemon.info dnsmasq[1421]: started, version 2.71 cachesize 150
Mon Dec 29 13:58:25 2014 daemon.info dnsmasq[1421]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-DNSSEC
Mon Dec 29 13:58:25 2014 daemon.info dnsmasq-dhcp[1421]: DHCP, IP range 192.168.3.100 -- 192.168.3.249, lease time 12h
Mon Dec 29 13:58:25 2014 daemon.info dnsmasq[1421]: using local addresses only for domain lan
Mon Dec 29 13:58:25 2014 daemon.info dnsmasq[1421]: reading /tmp/resolv.conf.auto
Mon Dec 29 13:58:25 2014 daemon.info dnsmasq[1421]: using local addresses only for domain lan
Mon Dec 29 13:58:25 2014 daemon.info dnsmasq[1421]: using nameserver 192.168.1.254#53
Mon Dec 29 13:58:25 2014 daemon.info dnsmasq[1421]: read /etc/hosts - 1 addresses
Mon Dec 29 13:58:25 2014 daemon.info dnsmasq[1421]: read /tmp/hosts/dhcp - 1 addresses
Mon Dec 29 13:58:25 2014 daemon.info dnsmasq-dhcp[1421]: read /etc/ethers - 0 addresses
Mon Dec 29 13:58:25 2014 user.notice firewall: Reloading firewall due to ifup of wan (eth0.2)
Mon Dec 29 13:58:26 2014 kern.warn kernel: [   31.490000] EXT4-fs warning (device sda1): __ext4_read_dirblock:908: error reading directory block (ino 2, block 0)
Mon Dec 29 14:00:55 2014 kern.crit kernel: [   48.090000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #393217: comm uhttpd: reading directory lblock 0
Mon Dec 29 14:01:03 2014 authpriv.info dropbear[1482]: Child connection from 192.168.3.106:58653
Mon Dec 29 14:01:08 2014 authpriv.notice dropbear[1482]: Password auth succeeded for 'root' from 192.168.3.106:58653
Mon Dec 29 14:01:08 2014 kern.crit kernel: [   61.040000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #2: comm dropbear: reading directory lblock 0
Mon Dec 29 14:01:08 2014 kern.crit kernel: [   61.060000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #262172: comm ash: reading directory lblock 0
Mon Dec 29 14:01:08 2014 kern.crit kernel: [   61.070000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #262168: comm ash: reading directory lblock 0
Mon Dec 29 14:01:08 2014 kern.crit kernel: [   61.080000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #262172: comm ash: reading directory lblock 0
Mon Dec 29 14:01:08 2014 kern.crit kernel: [   61.100000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #262172: comm ash: reading directory lblock 0
Mon Dec 29 14:01:08 2014 kern.crit kernel: [   61.110000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #131073: comm ash: reading directory lblock 0
Mon Dec 29 14:01:08 2014 kern.crit kernel: [   61.120000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #262172: comm ash: reading directory lblock 0
Mon Dec 29 14:01:08 2014 kern.crit kernel: [   61.140000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #262172: comm ash: reading directory lblock 0
Mon Dec 29 14:01:08 2014 kern.crit kernel: [   61.150000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #1048577: comm ash: reading directory lblock 0
Mon Dec 29 14:01:08 2014 kern.crit kernel: [   61.260000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #262172: comm sysinfo.sh: reading directory lblock 0
Mon Dec 29 14:01:08 2014 kern.crit kernel: [   61.270000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #262168: comm sysinfo.sh: reading directory lblock 0
Mon Dec 29 14:01:08 2014 kern.crit kernel: [   61.290000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #262172: comm sysinfo.sh: reading directory lblock 0
Mon Dec 29 14:01:08 2014 kern.crit kernel: [   61.330000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #262172: comm sysinfo.sh: reading directory lblock 0
Mon Dec 29 14:01:08 2014 kern.crit kernel: [   61.340000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #262168: comm sysinfo.sh: reading directory lblock 0
Mon Dec 29 14:01:08 2014 kern.crit kernel: [   61.410000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #262172: comm sysinfo.sh: reading directory lblock 0
Mon Dec 29 14:01:08 2014 kern.crit kernel: [   61.430000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #262168: comm sysinfo.sh: reading directory lblock 0
Mon Dec 29 14:01:08 2014 kern.crit kernel: [   61.450000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #262172: comm sysinfo.sh: reading directory lblock 0
Mon Dec 29 14:01:08 2014 kern.crit kernel: [   61.460000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #262168: comm sysinfo.sh: reading directory lblock 0
Mon Dec 29 14:01:08 2014 kern.crit kernel: [   61.470000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #1048577: comm sysinfo.sh: reading directory lblock 0
Mon Dec 29 14:01:08 2014 kern.crit kernel: [   61.550000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #262172: comm ifstatus: reading directory lblock 0
Mon Dec 29 14:01:08 2014 kern.crit kernel: [   61.560000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #262168: comm ifstatus: reading directory lblock 0
Mon Dec 29 14:01:10 2014 kern.crit kernel: [   63.560000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #262172: comm ash: reading directory lblock 0
Mon Dec 29 14:01:10 2014 kern.crit kernel: [   63.570000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #262168: comm ash: reading directory lblock 0
Mon Dec 29 14:01:10 2014 kern.crit kernel: [   63.580000] EXT4-fs error (device sda1): ext4_find_entry:1309: inode #1048577: comm ash: reading directory lblock 0

24 Odpowiedź przez Cezary

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

Odp: Potrzebny reboot po włączeniu z extroot

Od początku go masz tylko błędami sieje. Uruchom go bez extroota i sprawdź system plików.

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

Cezary's Strona

25 Odpowiedź przez tenobcy (edytowany przez tenobcy 2014-12-29 14:41:07)

  • Zarejestrowany: 2013-08-14
  • Posty: 450

Odp: Potrzebny reboot po włączeniu z extroot

Bez extroota wszystko jest ok, po uruchomieniu extrrota tą metodą http://eko.one.pl/forum/viewtopic.php?p … 14#p124114 na ext4 też wszystko jest ok do pierwszego ponownego uruchomienia. Robiłem już to kilkanaście razy z trzema różnymi kartami i za każdym razem jest to samo.