mam tylko External root jest na partycji /dev/sda1 odmontować z poziomu interfejsu graficznego gargole i w konsoli wpisać e2fsck /dev/sda1 i utwożyć od nowa extemala???

a ak naprawidz system plikow

Thu Dec 20 12:51:16 2018 kern.warn kernel: [  587.380000] EXT4-fs warning (device sda1): __ext4_read_dirblock:884: error -5 reading directory block (ino 393323, block 0)
Thu Dec 20 12:51:16 2018 daemon.err uhttpd[1723]:  * Running script '/etc/openvpn.firewall'
Thu Dec 20 12:51:16 2018 daemon.err uhttpd[1723]: touch: /etc/crontabs/root: Read-only file system
Thu Dec 20 12:51:17 2018 daemon.err uhttpd[1723]: touch: /etc/crontabs/root: Read-only file system
Thu Dec 20 12:51:46 2018 kern.warn kernel: [  617.630000] EXT4-fs warning (device sda1): __ext4_read_dirblock:884: error -5 reading directory block (ino 393280, block 0)
Thu Dec 20 12:51:46 2018 daemon.err uhttpd[1723]: uci: Entry not found
Thu Dec 20 12:51:46 2018 kern.warn kernel: [  617.700000] EXT4-fs warning (device sda1): __ext4_read_dirblock:884: error -5 reading directory block (ino 393223, block 0)
Thu Dec 20 12:51:46 2018 kern.warn kernel: [  617.720000] EXT4-fs warning (device sda1): __ext4_read_dirblock:884: error -5 reading directory block (ino 393223, block 0)
Thu Dec 20 12:51:46 2018 daemon.err uhttpd[1723]: ln: /etc/rc.d/S50mjpg-streamer: File exists
Thu Dec 20 12:51:48 2018 user.info MJPG-streamer [4823]: starting application
Thu Dec 20 12:51:48 2018 user.info MJPG-streamer [4823]: MJPG Streamer Version: svn rev: Unversioned directory
Thu Dec 20 12:51:48 2018 user.info MJPG-streamer [4823]: Using V4L2 device.: /dev/video0
Thu Dec 20 12:51:48 2018 user.info MJPG-streamer [4823]: Desired Resolution: 640 x 480
Thu Dec 20 12:51:48 2018 user.info MJPG-streamer [4823]: Frames Per Second.: 5
Thu Dec 20 12:51:48 2018 user.info MJPG-streamer [4823]: Format............: YUV
Thu Dec 20 12:51:48 2018 user.info MJPG-streamer [4823]: JPEG Quality......: 80
Thu Dec 20 12:51:49 2018 kern.err kernel: [  619.920000] uvcvideo: Failed to query (GET_DEF) UVC control 11 on unit 3: -32 (exp. 1).
Thu Dec 20 12:51:49 2018 user.info MJPG-streamer [4823]: www-folder-path...: /usr/lib/mjpg-streamer/www/
Thu Dec 20 12:51:49 2018 user.info MJPG-streamer [4823]: HTTP TCP port.....: 8080
Thu Dec 20 12:51:49 2018 user.info MJPG-streamer [4823]: username:password.: admin:
Thu Dec 20 12:51:49 2018 user.info MJPG-streamer [4823]: commands..........: enabled
Thu Dec 20 12:51:49 2018 user.info MJPG-streamer [4823]: starting input plugin input_uvc.so
Thu Dec 20 12:51:49 2018 user.info MJPG-streamer [4823]: starting output plugin: output_http.so (ID: 00)
Thu Dec 20 12:51:49 2018 daemon.err uhttpd[1723]: Warning: Unable to locate ipset utility, disabling ipset support
Thu Dec 20 12:51:49 2018 daemon.err uhttpd[1723]: Warning: Option @defaults[0].force_router_dns is unknown
Thu Dec 20 12:51:49 2018 daemon.err uhttpd[1723]: Warning: Section @zone[1] (wan) cannot resolve device of network 'wan'
Thu Dec 20 12:51:49 2018 daemon.err uhttpd[1723]:  * Flushing IPv4 filter table
Thu Dec 20 12:51:49 2018 daemon.err uhttpd[1723]:  * Flushing IPv4 nat table
Thu Dec 20 12:51:49 2018 daemon.err uhttpd[1723]:  * Flushing IPv4 mangle table
Thu Dec 20 12:51:49 2018 daemon.err uhttpd[1723]:  * Flushing IPv4 raw table
Thu Dec 20 12:51:49 2018 daemon.err uhttpd[1723]:  * Flushing conntrack table ...
Thu Dec 20 12:51:49 2018 daemon.err uhttpd[1723]:  * Populating IPv4 filter table
Thu Dec 20 12:51:49 2018 daemon.err uhttpd[1723]:    * Zone 'lan'
Thu Dec 20 12:51:49 2018 daemon.err uhttpd[1723]:    * Zone 'wan'
Thu Dec 20 12:51:49 2018 daemon.err uhttpd[1723]:    * Rule 'Allow-DHCP-Renew'
Thu Dec 20 12:51:49 2018 daemon.err uhttpd[1723]:    * Rule 'Allow-Ping'
Thu Dec 20 12:51:49 2018 daemon.err uhttpd[1723]:    * Rule 'Allow-IGMP'
Thu Dec 20 12:51:49 2018 daemon.err uhttpd[1723]:    * Rule #7
Thu Dec 20 12:51:49 2018 daemon.err uhttpd[1723]:    * Rule #8
Thu Dec 20 12:51:49 2018 daemon.err uhttpd[1723]:    * Forward 'lan' -> 'wan'
Thu Dec 20 12:51:49 2018 daemon.err uhttpd[1723]:  * Populating IPv4 nat table
Thu Dec 20 12:51:49 2018 daemon.err uhttpd[1723]:    * Zone 'lan'
Thu Dec 20 12:51:49 2018 daemon.err uhttpd[1723]:    * Zone 'wan'
Thu Dec 20 12:51:49 2018 daemon.err uhttpd[1723]:  * Populating IPv4 mangle table
Thu Dec 20 12:51:49 2018 daemon.err uhttpd[1723]:    * Zone 'lan'
Thu Dec 20 12:51:49 2018 daemon.err uhttpd[1723]:    * Zone 'wan'
Thu Dec 20 12:51:49 2018 daemon.err uhttpd[1723]:  * Populating IPv4 raw table
Thu Dec 20 12:51:49 2018 daemon.err uhttpd[1723]:    * Zone 'lan'
Thu Dec 20 12:51:49 2018 daemon.err uhttpd[1723]:    * Zone 'wan'
Thu Dec 20 12:51:49 2018 daemon.err uhttpd[1723]:  * Set tcp_ecn to off
Thu Dec 20 12:51:49 2018 daemon.err uhttpd[1723]:  * Set tcp_syncookies to on
Thu Dec 20 12:51:49 2018 daemon.err uhttpd[1723]:  * Set tcp_window_scaling to on
Thu Dec 20 12:51:49 2018 daemon.err uhttpd[1723]:  * Running script '/etc/firewall.user'
Thu Dec 20 12:51:49 2018 daemon.err uhttpd[1723]:  * Running script '/usr/lib/gargoyle_firewall_util/gargoyle_additions.firewall'
Thu Dec 20 12:51:49 2018 kern.warn kernel: [  620.130000] EXT4-fs warning (device sda1): __ext4_read_dirblock:884: error -5 reading directory block (ino 393323, block 0)
Thu Dec 20 12:51:49 2018 kern.warn kernel: [  620.150000] EXT4-fs warning (device sda1): __ext4_read_dirblock:884: error -5 reading directory block (ino 393323, block 0)
Thu Dec 20 12:51:49 2018 kern.warn kernel: [  620.840000] EXT4-fs warning (device sda1): __ext4_read_dirblock:884: error -5 reading directory block (ino 393223, block 0)
Thu Dec 20 12:51:49 2018 kern.warn kernel: [  620.880000] EXT4-fs warning (device sda1): __ext4_read_dirblock:884: error -5 reading directory block (ino 393323, block 0)
Thu Dec 20 12:51:50 2018 kern.warn kernel: [  621.100000] EXT4-fs warning (device sda1): __ext4_read_dirblock:884: error -5 reading directory block (ino 393323, block 0)
Thu Dec 20 12:51:50 2018 daemon.err uhttpd[1723]:  * Running script '/etc/openvpn.firewall'
Thu Dec 20 12:51:50 2018 daemon.err uhttpd[1723]: touch: /etc/crontabs/root: Read-only file system
Thu Dec 20 12:51:50 2018 daemon.err uhttpd[1723]: touch: /etc/crontabs/root: Read-only file system
Thu Dec 20 12:53:47 2018 daemon.info hostapd: wlan0: STA 00:0a:f5:15:82:fc IEEE 802.11: authenticated
Thu Dec 20 12:53:47 2018 daemon.info hostapd: wlan0: STA 00:0a:f5:15:82:fc IEEE 802.11: associated (aid 1)
Thu Dec 20 12:53:48 2018 daemon.info hostapd: wlan0: STA 00:0a:f5:15:82:fc WPA: pairwise key handshake completed (RSN)
Thu Dec 20 12:58:10 2018 kern.crit kernel: [ 1001.340000] EXT4-fs error (device sda1): ext4_find_entry:1289: inode #393323: comm uhttpd: reading directory lblock 0
Thu Dec 20 12:58:10 2018 kern.crit kernel: [ 1001.570000] EXT4-fs error (device sda1): ext4_find_entry:1289: inode #262186: comm gargoyle_header: reading directory lblock 0
Thu Dec 20 12:58:10 2018 kern.crit kernel: [ 1001.590000] EXT4-fs error (device sda1): ext4_find_entry:1289: inode #393218: comm sh: reading directory lblock 0
Thu Dec 20 12:58:10 2018 kern.crit kernel: [ 1001.630000] EXT4-fs error (device sda1): ext4_find_entry:1289: inode #262160: comm sh: reading directory lblock 0
Thu Dec 20 12:58:10 2018 kern.warn kernel: [ 1001.780000] EXT4-fs warning (device sda1): __ext4_read_dirblock:884: error -5 reading directory block (ino 393323, block 0)
Thu Dec 20 12:58:10 2018 kern.crit kernel: [ 1001.830000] EXT4-fs error (device sda1): ext4_find_entry:1289: inode #393218: comm sh: reading directory lblock 0
Thu Dec 20 12:58:11 2018 kern.warn kernel: [ 1001.980000] EXT4-fs warning (device sda1): __ext4_read_dirblock:884: error -5 reading directory block (ino 393323, block 0)
Thu Dec 20 13:02:02 2018 daemon.info hostapd: wlan0: STA 00:0a:f5:15:82:fc WPA: group key handshake completed (RSN)
Thu Dec 20 13:02:46 2018 kern.crit kernel: [ 1277.640000] EXT4-fs error (device sda1): ext4_find_entry:1289: inode #393217: comm uhttpd: reading directory lblock 0
Thu Dec 20 13:02:47 2018 kern.warn kernel: [ 1277.910000] EXT4-fs warning (device sda1): __ext4_read_dirblock:884: error -5 reading directory block (ino 393323, block 0)
Thu Dec 20 13:02:47 2018 kern.warn kernel: [ 1278.030000] EXT4-fs warning (device sda1): __ext4_read_dirblock:884: error -5 reading directory block (ino 393323, block 0)
Thu Dec 20 13:12:02 2018 daemon.info hostapd: wlan0: STA 00:0a:f5:15:82:fc WPA: group key handshake completed (RSN)
Thu Dec 20 13:17:35 2018 daemon.info hostapd: wlan0: STA 00:0a:f5:15:82:fc IEEE 802.11: authenticated
Thu Dec 20 13:17:35 2018 daemon.info hostapd: wlan0: STA 00:0a:f5:15:82:fc IEEE 802.11: associated (aid 1)
Thu Dec 20 13:17:35 2018 daemon.info hostapd: wlan0: STA 00:0a:f5:15:82:fc WPA: pairwise key handshake completed (RSN)
Thu Dec 20 13:22:02 2018 daemon.info hostapd: wlan0: STA 00:0a:f5:15:82:fc WPA: group key handshake completed (RSN)
Thu Dec 20 13:26:16 2018 kern.warn kernel: [ 2687.490000] EXT4-fs warning (device sda1): __ext4_read_dirblock:884: error -5 reading directory block (ino 393323, block 0)
Thu Dec 20 13:26:16 2018 kern.warn kernel: [ 2687.610000] EXT4-fs warning (device sda1): __ext4_read_dirblock:884: error -5 reading directory block (ino 393323, block 0)
Thu Dec 20 13:27:01 2018 kern.warn kernel: [ 2732.510000] EXT4-fs warning (device sda1): __ext4_read_dirblock:884: error -5 reading directory block (ino 393323, block 0)
Thu Dec 20 13:27:01 2018 kern.warn kernel: [ 2732.620000] EXT4-fs warning (device sda1): __ext4_read_dirblock:884: error -5 reading directory block (ino 393323, block 0)
Thu Dec 20 13:32:02 2018 daemon.info hostapd: wlan0: STA 00:0a:f5:15:82:fc WPA: group key handshake completed (RSN)
Thu Dec 20 13:36:00 2018 kern.warn kernel: [ 3271.450000] EXT4-fs warning (device sda1): __ext4_read_dirblock:884: error -5 reading directory block (ino 393267, block 0)
Thu Dec 20 13:42:02 2018 daemon.info hostapd: wlan0: STA 00:0a:f5:15:82:fc WPA: group key handshake completed (RSN)
Thu Dec 20 13:48:01 2018 kern.warn kernel: [ 3992.280000] EXT4-fs warning (device sda1): __ext4_read_dirblock:884: error -5 reading directory block (ino 393323, block 0)
Thu Dec 20 13:48:01 2018 kern.warn kernel: [ 3992.390000] EXT4-fs warning (device sda1): __ext4_read_dirblock:884: error -5 reading directory block (ino 393323, block 0)
Thu Dec 20 13:49:10 2018 kern.warn kernel: [ 4061.380000] EXT4-fs warning (device sda1): __ext4_read_dirblock:884: error -5 reading directory block (ino 393323, block 0)
Thu Dec 20 13:49:10 2018 kern.warn kernel: [ 4061.490000] EXT4-fs warning (device sda1): __ext4_read_dirblock:884: error -5 reading directory block (ino 393323, block 0)
Thu Dec 20 13:52:02 2018 daemon.info hostapd: wlan0: STA 00:0a:f5:15:82:fc WPA: group key handshake completed (RSN)
Thu Dec 20 14:02:02 2018 daemon.info hostapd: wlan0: STA 00:0a:f5:15:82:fc WPA: group key handshake completed (RSN)
Thu Dec 20 14:07:24 2018 authpriv.info dropbear[5295]: Child connection from 192.168.100.7:52918
Thu Dec 20 14:07:39 2018 authpriv.warn dropbear[5295]: Login attempt for nonexistent user from 192.168.100.7:52918
Thu Dec 20 14:07:52 2018 authpriv.warn dropbear[5295]: Login attempt for nonexistent user from 192.168.100.7:52918
Thu Dec 20 14:08:04 2018 authpriv.warn dropbear[5295]: Login attempt for nonexistent user from 192.168.100.7:52918
Thu Dec 20 14:08:17 2018 authpriv.warn dropbear[5295]: Login attempt for nonexistent user from 192.168.100.7:52918
Thu Dec 20 14:08:19 2018 authpriv.warn dropbear[5295]: Login attempt for nonexistent user from 192.168.100.7:52918
Thu Dec 20 14:08:37 2018 authpriv.warn dropbear[5295]: Login attempt for nonexistent user from 192.168.100.7:52918
Thu Dec 20 14:09:00 2018 authpriv.warn dropbear[5295]: Login attempt for nonexistent user from 192.168.100.7:52918
Thu Dec 20 14:10:43 2018 kern.warn kernel: [ 5354.080000] EXT4-fs warning (device sda1): __ext4_read_dirblock:884: error -5 reading directory block (ino 393323, block 0)
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 kern.warn kernel: [ 5354.480000] EXT4-fs warning (device sda1): __ext4_read_dirblock:884: error -5 reading directory block (ino 393323, block 0)
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:43 2018 daemon.err uhttpd[1723]: sh: write error: Broken pipe
Thu Dec 20 14:10:47 2018 kern.crit kernel: [ 5358.640000] EXT4-fs error (device sda1): ext4_find_entry:1289: inode #262160: comm sh: reading directory lblock 0
Success

zmienilem huba wyglada ze jest dobrze ale jest on bez swojego zasilania czy router to uciagnie

czyli wychodzi ze to hub  dzieki

Thu Dec 20 07:02:31 2018 kern.info kernel: [ 6826.330000] br-lan: port 2(wlan0) entered forwarding state
Thu Dec 20 07:02:31 2018 kern.warn kernel: [ 6826.400000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 154, block 0)
Thu Dec 20 07:02:31 2018 kern.warn kernel: [ 6826.430000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 154, block 0)
Thu Dec 20 07:02:31 2018 daemon.err block: /dev/sdb2040(deleted) is not a block device or file
Thu Dec 20 07:02:32 2018 daemon.err block: /dev/sdb2040(deleted) is not a block device or file
Thu Dec 20 07:02:32 2018 daemon.err block: /dev/sdb2040(deleted) is not a block device or file
Thu Dec 20 07:02:33 2018 kern.warn kernel: [ 6828.240000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 154, block 0)
Thu Dec 20 07:02:33 2018 kern.warn kernel: [ 6828.270000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 154, block 0)
Thu Dec 20 07:02:33 2018 kern.warn kernel: [ 6828.300000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 154, block 0)
Thu Dec 20 07:02:33 2018 kern.warn kernel: [ 6828.330000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 154, block 0)
Thu Dec 20 07:02:46 2018 kern.warn kernel: [ 6841.250000] EXT4-fs warning: 5 callbacks suppressed
Thu Dec 20 07:02:46 2018 kern.warn kernel: [ 6841.250000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 21, block 0)
Thu Dec 20 07:02:47 2018 kern.warn kernel: [ 6842.280000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 15, block 0)
Thu Dec 20 07:02:47 2018 kern.warn kernel: [ 6842.480000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 15, block 0)
Thu Dec 20 07:02:49 2018 kern.crit kernel: [ 6844.580000] EXT4-fs error (device sdb1): ext4_find_entry:1289: inode #121: comm uhttpd: reading directory lblock 0
Thu Dec 20 07:02:49 2018 kern.crit kernel: [ 6844.740000] EXT4-fs error (device sdb1): ext4_find_entry:1289: inode #78: comm gargoyle_header: reading directory lblock 0
Thu Dec 20 07:02:49 2018 kern.crit kernel: [ 6844.760000] EXT4-fs error (device sdb1): ext4_find_entry:1289: inode #21: comm sh: reading directory lblock 0
Thu Dec 20 07:02:50 2018 kern.crit kernel: [ 6844.990000] EXT4-fs error (device sdb1): ext4_find_entry:1289: inode #283: comm uhttpd: reading directory lblock 0
Thu Dec 20 07:03:17 2018 kern.warn kernel: [ 6872.580000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 15, block 0)
Thu Dec 20 07:03:17 2018 kern.warn kernel: [ 6872.590000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 15, block 0)
Thu Dec 20 07:03:17 2018 kern.warn kernel: [ 6872.600000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 15, block 0)
Thu Dec 20 07:03:17 2018 kern.warn kernel: [ 6872.610000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 15, block 0)
Thu Dec 20 07:03:17 2018 kern.warn kernel: [ 6872.690000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 15, block 0)
Thu Dec 20 07:03:17 2018 kern.warn kernel: [ 6872.710000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 15, block 0)
Thu Dec 20 07:03:18 2018 kern.warn kernel: [ 6873.330000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 15, block 0)
Thu Dec 20 07:03:18 2018 user.notice firewall: Reloading firewall due to ifup of wan6 (eth0)
Thu Dec 20 07:03:18 2018 kern.warn kernel: [ 6873.800000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 15, block 0)
Thu Dec 20 07:03:18 2018 kern.warn kernel: [ 6873.820000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 15, block 0)
Thu Dec 20 07:03:19 2018 kern.warn kernel: [ 6874.220000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 21, block 0)
Thu Dec 20 07:05:14 2018 kern.crit kernel: [ 6989.000000] EXT4-fs error (device sdb1): ext4_find_entry:1289: inode #121: comm uhttpd: reading directory lblock 0
Thu Dec 20 07:05:14 2018 kern.crit kernel: [ 6989.500000] EXT4-fs error (device sdb1): ext4_find_entry:1289: inode #283: comm uhttpd: reading directory lblock 0
Thu Dec 20 07:05:18 2018 kern.crit kernel: [ 6993.910000] EXT4-fs error (device sdb1): ext4_find_entry:1289: inode #121: comm uhttpd: reading directory lblock 0
Thu Dec 20 07:05:19 2018 daemon.err uhttpd[1907]: cat: can't open '/plugin_root/adblock/block.hosts': No such file or directory
Thu Dec 20 07:05:19 2018 kern.crit kernel: [ 6994.050000] EXT4-fs error (device sdb1): ext4_find_entry:1289: inode #126: comm cat: reading directory lblock 0
Thu Dec 20 07:05:19 2018 kern.crit kernel: [ 6994.070000] EXT4-fs error (device sdb1): ext4_find_entry:1289: inode #142: comm cat: reading directory lblock 0
Thu Dec 20 07:05:19 2018 kern.crit kernel: [ 6994.510000] EXT4-fs error (device sdb1): ext4_find_entry:1289: inode #283: comm uhttpd: reading directory lblock 0
Thu Dec 20 07:05:42 2018 kern.warn kernel: [ 7017.210000] EXT4-fs warning: 3 callbacks suppressed
Thu Dec 20 07:05:42 2018 kern.warn kernel: [ 7017.210000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 78, block 0)
Thu Dec 20 07:05:42 2018 daemon.err uhttpd[1907]: uci: Entry not found
Thu Dec 20 07:05:42 2018 kern.crit kernel: [ 7017.260000] EXT4-fs error (device sdb1): ext4_find_entry:1289: inode #78: comm uci: reading directory lblock 0
Thu Dec 20 07:05:42 2018 daemon.err uhttpd[1907]: uci: Entry not found
Thu Dec 20 07:05:42 2018 user.notice ADBLOCK: Enabling adblock plugin
Thu Dec 20 07:05:42 2018 user.notice ADBLOCK: Removing hosts file from dnsmasq
Thu Dec 20 07:05:42 2018 kern.warn kernel: [ 7017.290000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 121, block 0)
Thu Dec 20 07:05:42 2018 daemon.err uhttpd[1907]: uci: Entry not found
Thu Dec 20 07:05:42 2018 kern.warn kernel: [ 7017.310000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 78, block 0)
Thu Dec 20 07:05:42 2018 user.notice ADBLOCK: Removing cron entry
Thu Dec 20 07:05:42 2018 daemon.err uhttpd[1907]: sed: can't create temp file '/etc/crontabs/rootJpoNfS': Read-only file system
Thu Dec 20 07:05:42 2018 user.notice ADBLOCK: Removing firewall rules
Thu Dec 20 07:05:42 2018 kern.crit kernel: [ 7017.340000] EXT4-fs error (device sdb1): ext4_find_entry:1289: inode #65: comm sed: reading directory lblock 0
Thu Dec 20 07:05:42 2018 daemon.err uhttpd[1907]: sed: can't create temp file '/etc/firewall.userS2PXkk': Read-only file system
Thu Dec 20 07:05:42 2018 user.notice ADBLOCK: Reverting uHTTPd error page
Thu Dec 20 07:05:42 2018 kern.crit kernel: [ 7017.360000] EXT4-fs error (device sdb1): ext4_find_entry:1289: inode #18: comm sed: reading directory lblock 0
Thu Dec 20 07:05:42 2018 daemon.err uhttpd[1907]: uci: Entry not found
Thu Dec 20 07:05:42 2018 kern.warn kernel: [ 7017.380000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 78, block 0)
Thu Dec 20 07:05:42 2018 daemon.err uhttpd[1907]: mkdir: can't create directory '/plugin_root/adblock': Read-only file system
Thu Dec 20 07:05:42 2018 user.notice ADBLOCK: Unable to create folder to store ad list. Attempting to exit gracefully...
Thu Dec 20 07:05:42 2018 daemon.err uhttpd[1907]: cat: can't open '/plugin_root/adblock/block.hosts': No such file or directory
Thu Dec 20 07:05:43 2018 kern.crit kernel: [ 7017.990000] EXT4-fs error (device sdb1): ext4_find_entry:1289: inode #283: comm uhttpd: reading directory lblock 0
Thu Dec 20 07:05:46 2018 user.notice ADBLOCK: Modifying black/white lists from GUI
Thu Dec 20 07:05:46 2018 daemon.err uhttpd[1907]: /tmp/tmp.sh: line 6: can't create /plugin_root/usr/lib/adblock/black.list: nonexistent directory
Thu Dec 20 07:05:46 2018 daemon.err uhttpd[1907]: /tmp/tmp.sh: line 7: can't create /plugin_root/usr/lib/adblock/white.list: nonexistent directory
Thu Dec 20 07:05:46 2018 kern.crit kernel: [ 7021.930000] EXT4-fs error (device sdb1): ext4_find_entry:1289: inode #131: comm sh: reading directory lblock 0
Thu Dec 20 07:05:47 2018 daemon.err uhttpd[1907]: uci: Entry not found
Thu Dec 20 07:05:47 2018 user.notice ADBLOCK: Removing old hosts file
Thu Dec 20 07:05:47 2018 user.notice ADBLOCK: Retrieving ad lists from remote source
Thu Dec 20 07:05:47 2018 kern.crit kernel: [ 7022.010000] EXT4-fs error (device sdb1): ext4_find_entry:1289: inode #16: comm sh: reading directory lblock 0
Thu Dec 20 07:05:47 2018 kern.crit kernel: [ 7022.020000] EXT4-fs error (device sdb1): ext4_find_entry:1289: inode #169: comm sh: reading directory lblock 0
Thu Dec 20 07:05:49 2018 kern.crit kernel: [ 7024.730000] EXT4-fs error (device sdb1): ext4_find_entry:1289: inode #16: comm wget: reading directory lblock 0
Thu Dec 20 07:05:50 2018 daemon.err uhttpd[1907]: wget: error getting response: Connection reset by peer
Thu Dec 20 07:05:50 2018 user.notice ADBLOCK: Successfully retrieved ad list
Thu Dec 20 07:05:50 2018 user.notice ADBLOCK: Adding entries from black.list
Thu Dec 20 07:05:51 2018 user.notice ADBLOCK: Removing entries from white.list
Thu Dec 20 07:05:51 2018 daemon.err uhttpd[1907]: /usr/lib/adblock/runadblock.sh: line 196: can't create /plugin_root/adblock/block.hosts: nonexistent directory
Thu Dec 20 07:05:51 2018 kern.warn kernel: [ 7026.080000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 121, block 0)
Thu Dec 20 07:05:51 2018 daemon.err uhttpd[1907]: uci: Entry not found
Thu Dec 20 07:05:51 2018 user.notice ADBLOCK: Reloading hosts list
Thu Dec 20 07:05:51 2018 kern.warn kernel: [ 7026.120000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 78, block 0)
Thu Dec 20 07:05:51 2018 daemon.info dnsmasq[8116]: read /etc/hosts - 2 addresses
Thu Dec 20 07:05:51 2018 daemon.info dnsmasq[8116]: read /tmp/hosts/dhcp - 1 addresses
Thu Dec 20 07:05:51 2018 daemon.err uhttpd[1907]: cat: can't open '/plugin_root/adblock/block.hosts': No such file or directory
Thu Dec 20 07:06:50 2018 kern.crit kernel: [ 7085.430000] EXT4-fs error (device sdb1): ext4_find_entry:1289: inode #283: comm uhttpd: reading directory lblock 0
Thu Dec 20 07:07:34 2018 daemon.err uhttpd[1907]: uci: Entry not found
Thu Dec 20 07:07:34 2018 kern.warn kernel: [ 7129.190000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 78, block 0)
Thu Dec 20 07:07:34 2018 daemon.err uhttpd[1907]: rm: can't remove '/etc/dropbear/authorized_keys': Read-only file system
Thu Dec 20 07:07:34 2018 daemon.err uhttpd[1907]: /tmp/tmp.sh: line 23: can't create /etc/dropbear/authorized_keys: Read-only file system
Thu Dec 20 07:07:34 2018 kern.crit kernel: [ 7129.500000] EXT4-fs error (device sdb1): ext4_find_entry:1289: inode #18: comm iptables: reading directory lblock 0
Thu Dec 20 07:07:34 2018 kern.warn kernel: [ 7129.760000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 65, block 0)
Thu Dec 20 07:07:35 2018 kern.warn kernel: [ 7130.430000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 121, block 0)
Thu Dec 20 07:07:35 2018 kern.warn kernel: [ 7130.440000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 121, block 0)
Thu Dec 20 07:07:35 2018 kern.warn kernel: [ 7130.800000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 21, block 0)
Thu Dec 20 07:07:35 2018 kern.warn kernel: [ 7130.830000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 121, block 0)
Thu Dec 20 07:07:36 2018 kern.warn kernel: [ 7130.950000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 121, block 0)
Thu Dec 20 07:07:59 2018 kern.crit kernel: [ 7154.910000] EXT4-fs error (device sdb1): ext4_find_entry:1289: inode #121: comm uhttpd: reading directory lblock 0
Thu Dec 20 07:08:00 2018 kern.crit kernel: [ 7155.400000] EXT4-fs error (device sdb1): ext4_find_entry:1289: inode #283: comm uhttpd: reading directory lblock 0
Thu Dec 20 07:08:22 2018 daemon.err uhttpd[1907]: Error: There is no such init script like 'miniupnpd'.
Thu Dec 20 07:08:37 2018 daemon.err uhttpd[1907]: Bad argument `CONNMARK'
Thu Dec 20 07:08:37 2018 daemon.err uhttpd[1907]: Try `iptables -h' or 'iptables --help' for more information.
Thu Dec 20 07:08:37 2018 daemon.err uhttpd[1907]: Bad argument `CONNMARK'
Thu Dec 20 07:08:37 2018 daemon.err uhttpd[1907]: Try `iptables -h' or 'iptables --help' for more information.
Thu Dec 20 07:08:38 2018 kern.warn kernel: [ 7192.960000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 21, block 0)
Thu Dec 20 07:08:38 2018 daemon.err uhttpd[1907]: touch: /etc/crontabs/root: Read-only file system
Thu Dec 20 07:08:38 2018 kern.crit kernel: [ 7193.020000] EXT4-fs error (device sdb1): ext4_find_entry:1289: inode #16: comm bwmon_gargoyle: reading directory lblock 0
Thu Dec 20 07:08:38 2018 kern.warn kernel: [ 7193.730000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 121, block 0)
Thu Dec 20 07:19:54 2018 kern.warn kernel: [ 7869.770000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 121, block 0)
Thu Dec 20 07:26:51 2018 kern.crit kernel: [ 8286.590000] EXT4-fs error (device sdb1): ext4_find_entry:1289: inode #121: comm uhttpd: reading directory lblock 0
Thu Dec 20 07:29:57 2018 kern.warn kernel: [ 8472.410000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 121, block 0)
Thu Dec 20 07:29:57 2018 kern.warn kernel: [ 8472.470000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 121, block 0)
Thu Dec 20 08:53:21 2018 kern.warn kernel: [13476.190000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 121, block 0)
Thu Dec 20 08:53:21 2018 kern.warn kernel: [13476.250000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 121, block 0)
Thu Dec 20 09:04:25 2018 kern.warn kernel: [14140.780000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 121, block 0)
Thu Dec 20 09:04:25 2018 kern.warn kernel: [14140.840000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 121, block 0)
Thu Dec 20 09:37:35 2018 kern.warn kernel: [16130.460000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 121, block 0)
Thu Dec 20 09:37:35 2018 kern.warn kernel: [16130.520000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 121, block 0)
Thu Dec 20 09:42:59 2018 kern.warn kernel: [16454.370000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 121, block 0)
Thu Dec 20 09:42:59 2018 kern.warn kernel: [16454.430000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 121, block 0)
Thu Dec 20 11:16:28 2018 kern.warn kernel: [22063.240000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 121, block 0)
Thu Dec 20 11:16:28 2018 kern.warn kernel: [22063.300000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 121, block 0)
Thu Dec 20 11:54:24 2018 kern.warn kernel: [24339.160000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 121, block 0)
Thu Dec 20 11:54:24 2018 kern.warn kernel: [24339.220000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 121, block 0)
Thu Dec 20 11:54:25 2018 kern.warn kernel: [24340.180000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 121, block 0)
Thu Dec 20 11:54:25 2018 kern.warn kernel: [24340.270000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 121, block 0)
Thu Dec 20 11:54:25 2018 kern.warn kernel: [24340.300000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 121, block 0)
Thu Dec 20 11:54:25 2018 kern.warn kernel: [24340.410000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 121, block 0)
Thu Dec 20 11:54:31 2018 kern.warn kernel: [24346.670000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 121, block 0)
Thu Dec 20 11:54:38 2018 kern.crit kernel: [24353.740000] EXT4-fs error (device sdb1): ext4_find_entry:1289: inode #283: comm uhttpd: reading directory lblock 0
Thu Dec 20 11:54:39 2018 kern.warn kernel: [24354.070000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 121, block 0)
Thu Dec 20 11:54:54 2018 kern.crit kernel: [24369.620000] EXT4-fs error (device sdb1): ext4_find_entry:1289: inode #283: comm uhttpd: reading directory lblock 0
Thu Dec 20 11:55:00 2018 kern.warn kernel: [24375.310000] EXT4-fs warning (device sdb1): __ext4_read_dirblock:884: error -5 reading directory block (ino 121, block 0)
Success

witam mam problem z  wykrywaniem nosnika  usb i kamerki tylko pomaga restart [1043] i jest wszystko ok ale po  jakims czasie problem powraca teraz mam 1.9.2.3 (r49483) wgrywalem inne ver bez skutku  uzywam huba aktywnego z zsilaczem

33

(8 odpowiedzi, napisanych Oprogramowanie / Software)

Dzięki udało się

34

(8 odpowiedzi, napisanych Oprogramowanie / Software)

Failsafe działa dostałem się do routera i mam wgrany najnowszy gargole ale jak zmieniam w nim ipz 192.168.1.1 na 192.168.100.250 i w karcie sieciowej pc teź zmieniłem to nie ma już połączenia czy trzeba wgrac soft  przez serwer http

35

(8 odpowiedzi, napisanych Oprogramowanie / Software)

Failsafe robi sie trzymać reset i załącz?i co dalej

36

(8 odpowiedzi, napisanych Oprogramowanie / Software)

Wciskam reset ale nic się nie dzieje soft wgrałe dobry ale pdczas instalacij cały czas mielił

37

(8 odpowiedzi, napisanych Oprogramowanie / Software)

Witam po wgraniu najnowszego gargulca nie można dostać się do routera ani po nowym ip 192.168.1.1 ani po starym wfi działa jest po starym ip tylko zmieniło nazwe sieci na gargole  i co teraz

38

(233 odpowiedzi, napisanych Oprogramowanie / Software)

gdzei znajde o mjpeg-streamer

39

(233 odpowiedzi, napisanych Oprogramowanie / Software)

Witam czy da sie podpiac 2 kamerki pod rurer zeby byl podglad z obydwoch na najnowszym gargolu

40

(233 odpowiedzi, napisanych Oprogramowanie / Software)

a sterowniki  w gargolcu są zainstalowane

41

(233 odpowiedzi, napisanych Oprogramowanie / Software)

witam czy kamerka medi tech mt 4040 pójdzie na gargole

42

(10 odpowiedzi, napisanych Oprogramowanie / Software)

po 2 resecie poszło dzięki

43

(10 odpowiedzi, napisanych Oprogramowanie / Software)

niestety nie czy ktoś to sprawdzał na tej wer

44

(10 odpowiedzi, napisanych Oprogramowanie / Software)

nie mogę dodać zaznaczam ptaszkiem Włącz serwer DHCP na LAN wpisuje zakres dhcp dalej ptaszek Wymuszanie przydziałów DHCP wpisuje adres mac i ip dodaje jest dodane ale w wake on lan go nie ma co jest nie tak? a i w zakładce dhcp Statyczne adresy IP na dole w dodanych też go nie ma

45

(10 odpowiedzi, napisanych Oprogramowanie / Software)

Witam mam zainstalowanego  Gargoyle1.9.2.4 i nie wiem jak dodać adres mac pc do wake on lan aby wybudzić kompa

46

(2 odpowiedzi, napisanych Oprogramowanie / Software)

firsboot nic nie daje dalej nie mogę się zalogować czyli pozostaje mi wgrać nowy obraz przez ssh

47

(2 odpowiedzi, napisanych Oprogramowanie / Software)

witam ten router pracował jako most bezprzewodowy/przekaźnik ale po zmianie internetu musiałem go zresetować [jest w nim wgrany gargole]i teraz nie mogę się z nim połączyć po wpisaniu ip routera 192.168.1.1 wyskakuje mi cos takigo [haserl CGI Error

Translate error: '/www/i18n/English-EN/strings.js' No UTF-8 BOM co teraz zrobić

48

(249 odpowiedzi, napisanych Oprogramowanie / Software)

racja dzięki

49

(249 odpowiedzi, napisanych Oprogramowanie / Software)

ta czy  warto zinstalować  nowe gargoyle 1.9 jest jakaś różnica

50

(249 odpowiedzi, napisanych Oprogramowanie / Software)

czyli pluginy są takie same jak w starej 1.6.2.2