dziękuje za podpowiedź... jednak na finiszu error i to świadczący chyba o tym, że nie został zamontowany nośnik i brak udziału :
root@Gargoyle:~# /etc/init.d/vsftpd start
ERROR: No drives attached, no directories to share!

co za tym idzie ftp nie odpowiada... walczę nadal i proszę o sugestie z Waszej strony.
pozdrawiam i dziękuje za wszelkie podpowiedzi

Cezary, a dotyczy to także wersji na 4MB, bo w poradniku na instalację Gargoyla jest:
cytat
Brak jest pakietów fdisk/e2fsprogs/samba/nfs/ftp (oraz pluginów). Ponieważ jest już także domyślnie pakiet block-mount, to można doinstalować następne pakiety po zrobieniu extroota

bo ja u siebie np nie mam w opcjach GUI konfiguracji serwera FTP (3420 Gargoyle 1.5.9.6 z extrootem)

czyli zrobić to:
Usuwamy plugin:

opkg remove plugin-gargoyle-usb-storage
Sprzątamy po pluginie:

uci del gargoyle.display.system_usb_storage
uci del gargoyle.scripts.system_usb_storage
uci del gargoyle.system.usb_storage
uci commit gargoyle
rm /etc/rc.d/S56usb_storage
Instalujemy pakiety block-mount i block-hotplug

opkg update
opkg install block-mount block-hotplug

a później wg poradnika:
http://eko.one.pl/?p=openwrt-ftp

czyli stąd
http://downloads.openwrt.org/attitude_a … c/packages

lub
http://ecco.selfip.net/attitude_adjustm … x/packages

a nie stąd
http://ecco.selfip.net/gargoyle-pl/atti … x/packages
czyli najlepiej usunąć ten link z menu dodatków i instalować

skorzystałem z Waszych sugestii jednak nadal nie udało mi się postawić ftp'a:

Mar 20 22:50:18 Gargoyle authpriv.notice dropbear[3772]: Password auth succeeded for 'root' from 192.168.1.152:33398
Mar 20 22:52:27 Gargoyle daemon.info hostapd: wlan0: STA 00:25:d3:6c:f5:28 WPA: group key handshake completed (RSN)
Mar 20 23:02:27 Gargoyle daemon.info hostapd: wlan0: STA 00:25:d3:6c:f5:28 WPA: group key handshake completed (RSN)
Mar 20 23:03:12 Gargoyle auth.err passwd: unknown user pikolodoro102071983
Mar 20 23:07:36 Gargoyle user.notice root: vsftpd init: mounted = 0
Success

mój plik konf.: /etc/vsftpd.conf
background=yes
listen=yes
local_umask=022
check_shell=no
session_support=no
user_config_dir=/etc/vsftpd_users
chroot_local_user=yes
anonymous_enable=yes
local_enable=yes

zawartość vi /etc/vsftpd_users/ftp:
dirlist_enable=yes
download_enable=yes
write_enable=yes
anon_upload_enable=yes
anon_other_write_enable=yes
anon_mkdir_write_enable=yes

Dostęp dla określonego użytkownika:
echo "toka:x:1000:65534:toka:/mnt/sda1:/bin/false" >> /etc/passwd
echo "toka:x:0:0:99999:7:::" >> /etc/shadow
passwd pikolodoro102071983

mój plik dla toka /etc/vsftpd_users/toka:
dirlist_enable=yes
download_enable=yes
write_enable=yes

w /mnt/sda1/ mam podkatalog upload

po wydanu w trerminalu komendy /etc/init.d/vsftpd start
nadal informacja "/ etc / vsftpd_users / ftp" nie ma takiego pliku lub katalogu

moje dodatki:
   
attitude_adjustment
http://downloads.openwrt.org/attitude_a … c/packages    Systemowe
eko1
http://ecco.selfip.net/attitude_adjustm … x/packages   
ftp
http://ecco.selfip.net/gargoyle-pl/atti … x/packages

nie posiadam zainstalowanego pluginu:
USB Storage Support for Gargoyle

proszę o wskazówki, pozdrawiam i dobrej nocy

kurcze nie usunąłem http://ecco.selfip.net/gargoyle-pl/atti … x/packages zapewne to jest znów przyczyną

proszę o analizę moich wypocin

nie myśle już trzeźwo ->kima ...jutro kolejny dzień zmagań

dziś po pracy zacznę konfigurację od nowa.

chciałem aby hasłem do użytkownika toka było pikolodoro102071983 widać zrobiłem to źle, ustawię tak jak jest w poradniku , konfigurację dostępu do ftp chciałbym mieć zarówno dla określonego użytkownika jak i dla klientów anonimowych.

po powrocie i ponownej konfiguracji dam znać co i jak.

Ustawiłem hasło i uruchomiłem ftp'a...error...przeprowadziłem wszystko od nowa, sysupg-> usunąłem dodatek-> konf.połączenia z internetem oraz wykonałem exroot-> instalacja ftp'a z poradnika wraz ze wskazówkami, które otrzymałem od Cezarego oraz KMY-> SUKCES . Wszystko działa jak należy, teraz zainstaluje transmissionbt i podejmę próbę z minidlna. Bardzo dziękuje za wskazówki.

Pozdrawiam.

jeszcze nie wszystko po uruchomieniu ftp'a nastąpił brak łącza z internetem, wyłączyłem router i podłaczyłem ponownie, po zalogowaniu znów nie mogę się zalogować na serwer, ponizej log już po wyłączeniu i ponownym połaczeniu routera do zasilania:

Jan  1 01:01:54 Gargoyle local2.info chat[2674]: ^M
Jan  1 01:01:54 Gargoyle local2.info chat[2674]: AT+CGDCONT=1,"IP","internet"^M^M
Jan  1 01:01:54 Gargoyle local2.info chat[2674]: OK
Jan  1 01:01:54 Gargoyle local2.info chat[2674]:  -- got it
Jan  1 01:01:54 Gargoyle local2.info chat[2674]: send (ATD*99***1#^M)
Jan  1 01:01:54 Gargoyle local2.info chat[2674]: expect (CONNECT)
Jan  1 01:01:54 Gargoyle local2.info chat[2674]: ^M
Jan  1 01:01:54 Gargoyle local2.info chat[2674]: ATD*99***1#^M^M
Jan  1 01:01:54 Gargoyle local2.info chat[2674]: CONNECT
Jan  1 01:01:54 Gargoyle local2.info chat[2674]:  -- got it
Jan  1 01:01:54 Gargoyle local2.info chat[2674]: send ( ^M)
Jan  1 01:01:54 Gargoyle daemon.info pppd[2650]: Serial connection established.
Jan  1 01:01:54 Gargoyle daemon.info pppd[2650]: Using interface 3g-wan
Jan  1 01:01:54 Gargoyle daemon.notice pppd[2650]: Connect: 3g-wan <--> /dev/ttyUSB0
Jan  1 01:01:57 Gargoyle daemon.warn pppd[2650]: Could not determine remote IP address: defaulting to 10.64.64.64
Jan  1 01:01:57 Gargoyle daemon.notice pppd[2650]: local  IP address 31.174.212.12
Jan  1 01:01:57 Gargoyle daemon.notice pppd[2650]: remote IP address 10.64.64.64
Jan  1 01:01:57 Gargoyle daemon.notice pppd[2650]: primary   DNS address 89.108.195.20
Jan  1 01:01:57 Gargoyle daemon.notice pppd[2650]: secondary DNS address 89.108.202.20
Jan  1 01:01:57 Gargoyle daemon.notice netifd: Interface 'wan' is now up
Jan  1 01:01:59 Gargoyle user.notice ifup: Enabling Router Solicitations on wan (3g-wan)
Jan  1 01:01:59 Gargoyle daemon.info dnsmasq[1119]: reading /tmp/resolv.conf.auto
Jan  1 01:01:59 Gargoyle daemon.info dnsmasq[1119]: using nameserver 89.108.195.20#53
Jan  1 01:01:59 Gargoyle daemon.info dnsmasq[1119]: using nameserver 89.108.202.20#53
Jan  1 01:01:59 Gargoyle daemon.warn dnsmasq[1119]: ignoring nameserver 192.168.1.1 - local interface
Jan  1 01:01:59 Gargoyle daemon.info dnsmasq[1119]: using local addresses only for domain lan
Jan  1 01:02:00 Gargoyle user.info firewall: adding wan (3g-wan) to zone wan
Jan  1 01:02:03 Gargoyle kern.crit kernel: [  123.450000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #1261569: comm iptables: reading directory lblock 0
Jan  1 01:02:03 Gargoyle kern.crit kernel: [  123.460000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #753666: comm iptables: reading directory lblock 0
Jan  1 01:02:03 Gargoyle kern.crit kernel: [  123.480000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #1261569: comm iptables: reading directory lblock 0
Jan  1 01:02:03 Gargoyle kern.crit kernel: [  123.490000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #753666: comm iptables: reading directory lblock 0
Jan  1 01:02:03 Gargoyle kern.crit kernel: [  123.510000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #1261569: comm iptables: reading directory lblock 0
Jan  1 01:02:03 Gargoyle kern.crit kernel: [  123.520000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #753666: comm iptables: reading directory lblock 0
Jan  1 01:02:03 Gargoyle kern.crit kernel: [  123.530000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #1261569: comm iptables: reading directory lblock 0
Jan  1 01:02:03 Gargoyle kern.crit kernel: [  123.540000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #753666: comm iptables: reading directory lblock 0
Jan  1 01:02:03 Gargoyle kern.crit kernel: [  123.560000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #1261569: comm iptables: reading directory lblock 0
Jan  1 01:02:03 Gargoyle kern.crit kernel: [  123.570000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #753666: comm iptables: reading directory lblock 0
Jan  1 01:02:03 Gargoyle kern.crit kernel: [  123.590000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #1261569: comm iptables: reading directory lblock 0
Jan  1 01:02:03 Gargoyle kern.crit kernel: [  123.600000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #753666: comm iptables: reading directory lblock 0
Jan  1 01:02:03 Gargoyle kern.crit kernel: [  123.620000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #1261569: comm iptables: reading directory lblock 0
Jan  1 01:02:03 Gargoyle kern.crit kernel: [  123.630000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #753666: comm iptables: reading directory lblock 0
Jan  1 01:02:03 Gargoyle kern.crit kernel: [  123.640000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #1261569: comm iptables: reading directory lblock 0
Jan  1 01:02:03 Gargoyle kern.crit kernel: [  123.650000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #753666: comm iptables: reading directory lblock 0
Jan  1 01:02:04 Gargoyle kern.crit kernel: [  124.240000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #753694: comm hotplug-call: reading directory lblock 0
Jan  1 01:02:04 Gargoyle kern.crit kernel: [  124.370000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #753666: comm tc: reading directory lblock 0
Jan  1 01:02:04 Gargoyle kern.crit kernel: [  124.380000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #1261569: comm tc: reading directory lblock 0
Jan  1 01:02:04 Gargoyle kern.crit kernel: [  124.390000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #753666: comm tc: reading directory lblock 0
Jan  1 01:02:04 Gargoyle kern.crit kernel: [  124.400000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #1261569: comm tc: reading directory lblock 0
Jan  1 01:02:04 Gargoyle kern.crit kernel: [  124.410000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #753666: comm tc: reading directory lblock 0
Jan  1 01:02:04 Gargoyle kern.crit kernel: [  124.500000] EXT4-fs error (device sda1): ext4_read_inode_bitmap:161: comm rm: Cannot read inode bitmap - block_group = 218, inode_bitmap = 7143425
Jan  1 01:02:04 Gargoyle kern.crit kernel: [  124.510000] EXT4-fs error (device sda1) in ext4_new_inode:941: IO failure
Jan  1 01:02:04 Gargoyle kern.err kernel: [  124.520000] overlayfs: ERROR - failed to whiteout 'S50cron'
Jan  1 01:02:04 Gargoyle kern.crit kernel: [  124.780000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #1785857: comm iptables: reading directory lblock 0
Jan  1 01:02:04 Gargoyle kern.crit kernel: [  124.930000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #1261569: comm iptables: reading directory lblock 0
Jan  1 01:02:04 Gargoyle kern.crit kernel: [  124.940000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #753666: comm iptables: reading directory lblock 0
Jan  1 01:02:04 Gargoyle kern.crit kernel: [  124.950000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #1261569: comm iptables: reading directory lblock 0
Jan  1 01:02:04 Gargoyle kern.crit kernel: [  124.960000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #753666: comm iptables: reading directory lblock 0
Jan  1 01:02:04 Gargoyle kern.crit kernel: [  124.980000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #1261569: comm iptables: reading directory lblock 0
Jan  1 01:02:04 Gargoyle kern.crit kernel: [  124.990000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #753666: comm iptables: reading directory lblock 0
Jan  1 01:02:05 Gargoyle kern.crit kernel: [  125.000000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #1261569: comm iptables: reading directory lblock 0
Jan  1 01:02:05 Gargoyle kern.crit kernel: [  125.020000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #753666: comm iptables: reading directory lblock 0
Jan  1 01:02:05 Gargoyle kern.crit kernel: [  125.040000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #1261569: comm iptables: reading directory lblock 0
Jan  1 01:02:05 Gargoyle kern.crit kernel: [  125.050000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #753666: comm iptables: reading directory lblock 0
Jan  1 01:02:05 Gargoyle kern.crit kernel: [  125.060000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #1261569: comm iptables: reading directory lblock 0
Jan  1 01:02:05 Gargoyle kern.crit kernel: [  125.070000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #753666: comm iptables: reading directory lblock 0
Jan  1 01:02:05 Gargoyle kern.crit kernel: [  125.400000] EXT4-fs error (device sda1): ext4_read_inode_bitmap:161: comm mkdir: Cannot read inode bitmap - block_group = 92, inode_bitmap = 3014657
Jan  1 01:02:05 Gargoyle kern.crit kernel: [  125.410000] EXT4-fs error (device sda1) in ext4_new_inode:941: IO failure
Jan  1 01:02:05 Gargoyle kern.crit kernel: [  125.500000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #1261569: comm iptables: reading directory lblock 0
Jan  1 01:02:05 Gargoyle kern.crit kernel: [  125.510000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #753666: comm iptables: reading directory lblock 0
Jan  1 01:02:05 Gargoyle kern.crit kernel: [  125.520000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #1261569: comm iptables: reading directory lblock 0
Jan  1 01:02:05 Gargoyle kern.crit kernel: [  125.530000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #753666: comm iptables: reading directory lblock 0
Jan  1 01:02:05 Gargoyle kern.crit kernel: [  125.650000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #1261569: comm iptables: reading directory lblock 0
Jan  1 01:02:05 Gargoyle kern.crit kernel: [  125.650000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #753666: comm iptables: reading directory lblock 0
Jan  1 01:02:05 Gargoyle kern.crit kernel: [  125.670000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #1261569: comm iptables: reading directory lblock 0
Jan  1 01:02:05 Gargoyle kern.crit kernel: [  125.680000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #753666: comm iptables: reading directory lblock 0
Jan  1 01:02:05 Gargoyle kern.crit kernel: [  125.740000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #753694: comm bwmon_gargoyle: reading directory lblock 0
Jan  1 01:02:05 Gargoyle kern.crit kernel: [  125.850000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #1261569: comm ipset: reading directory lblock 0
Jan  1 01:02:05 Gargoyle kern.crit kernel: [  125.870000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #753666: comm ipset: reading directory lblock 0
Jan  1 01:02:05 Gargoyle kern.crit kernel: [  125.880000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #753666: comm ipset: reading directory lblock 0
Jan  1 01:02:06 Gargoyle kern.crit kernel: [  126.060000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #1261569: comm iptables: reading directory lblock 0
Jan  1 01:02:06 Gargoyle kern.crit kernel: [  126.070000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #753666: comm iptables: reading directory lblock 0
Jan  1 01:02:06 Gargoyle kern.warn kernel: [  126.160000] ipt_bandwidth: timezone shift of 60 minutes detected, adjusting
Jan  1 01:02:06 Gargoyle kern.warn kernel: [  126.170000]                old minutes west=0, new minutes west=-60
Jan  1 01:02:06 Gargoyle kern.crit kernel: [  126.530000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #1785857: comm bwmon_gargoyle: reading directory lblock 0
Jan  1 01:02:06 Gargoyle kern.crit kernel: [  126.550000] EXT4-fs error (device sda1): ext4_read_inode_bitmap:161: comm touch: Cannot read inode bitmap - block_group = 218, inode_bitmap = 7143425
Jan  1 01:02:06 Gargoyle kern.crit kernel: [  126.570000] EXT4-fs error (device sda1) in ext4_new_inode:941: IO failure
Jan  1 01:02:07 Gargoyle kern.crit kernel: [  127.360000] EXT4-fs error (device sda1): ext4_read_inode_bitmap:161: comm mv: Cannot read inode bitmap - block_group = 218, inode_bitmap = 7143425
Jan  1 01:02:07 Gargoyle kern.crit kernel: [  127.370000] EXT4-fs error (device sda1) in ext4_new_inode:941: IO failure
Mar 21 19:32:25 Gargoyle kern.info kernel: [  134.200000] IMQ driver unloaded successfully.
Mar 21 19:32:25 Gargoyle kern.info kernel: [  134.240000]     Hooked IMQ after mangle on INPUT
Mar 21 19:32:25 Gargoyle kern.info kernel: [  134.240000]     Hooked IMQ after mangle on FORWARD
Mar 21 19:32:25 Gargoyle kern.info kernel: [  134.250000] IMQ driver loaded successfully. (numdevs = 1, numqueues = 1)
Mar 21 19:32:25 Gargoyle kern.crit kernel: [  134.260000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #753694: comm qos_gargoyle: reading directory lblock 0
Mar 21 19:32:46 Gargoyle daemon.info hostapd: wlan0: STA 00:25:d3:6c:f5:28 IEEE 802.11: authenticated
Mar 21 19:32:46 Gargoyle daemon.info hostapd: wlan0: STA 00:25:d3:6c:f5:28 IEEE 802.11: associated (aid 1)
Mar 21 19:32:46 Gargoyle daemon.info hostapd: wlan0: STA 00:25:d3:6c:f5:28 WPA: pairwise key handshake completed (RSN)
Mar 21 19:32:46 Gargoyle daemon.info dnsmasq-dhcp[1119]: DHCPREQUEST(br-lan) 192.168.1.152 00:25:d3:6c:f5:28
Mar 21 19:32:46 Gargoyle daemon.info dnsmasq-dhcp[1119]: DHCPACK(br-lan) 192.168.1.152 00:25:d3:6c:f5:28 k70
Mar 21 19:33:22 Gargoyle daemon.info hostapd: wlan0: STA f8:0c:f3:18:86:e3 IEEE 802.11: authenticated
Mar 21 19:33:22 Gargoyle daemon.info hostapd: wlan0: STA f8:0c:f3:18:86:e3 IEEE 802.11: associated (aid 2)
Mar 21 19:33:22 Gargoyle daemon.info hostapd: wlan0: STA f8:0c:f3:18:86:e3 WPA: pairwise key handshake completed (RSN)
Mar 21 19:33:23 Gargoyle daemon.info dnsmasq-dhcp[1119]: DHCPREQUEST(br-lan) 192.168.2.101 f8:0c:f3:18:86:e3
Mar 21 19:33:23 Gargoyle daemon.info dnsmasq-dhcp[1119]: DHCPNAK(br-lan) 192.168.2.101 f8:0c:f3:18:86:e3 wrong network
Mar 21 19:33:27 Gargoyle daemon.info dnsmasq-dhcp[1119]: DHCPDISCOVER(br-lan) f8:0c:f3:18:86:e3
Mar 21 19:33:27 Gargoyle daemon.info dnsmasq-dhcp[1119]: DHCPOFFER(br-lan) 192.168.1.211 f8:0c:f3:18:86:e3
Mar 21 19:33:27 Gargoyle daemon.info dnsmasq-dhcp[1119]: DHCPREQUEST(br-lan) 192.168.1.211 f8:0c:f3:18:86:e3
Mar 21 19:33:27 Gargoyle daemon.info dnsmasq-dhcp[1119]: DHCPACK(br-lan) 192.168.1.211 f8:0c:f3:18:86:e3 android-89abc95b91988274
Mar 21 19:33:33 Gargoyle daemon.info hostapd: wlan0: STA f8:0c:f3:18:86:e3 IEEE 802.11: disassociated
Mar 21 19:33:34 Gargoyle daemon.info hostapd: wlan0: STA f8:0c:f3:18:86:e3 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Mar 21 19:35:51 Gargoyle kern.crit kernel: [  340.000000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #753665: comm overview.sh: reading directory lblock 0
Mar 21 19:35:51 Gargoyle kern.crit kernel: [  340.010000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #753666: comm overview.sh: reading directory lblock 0
Mar 21 19:35:51 Gargoyle kern.crit kernel: [  340.020000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #753666: comm overview.sh: reading directory lblock 0
Mar 21 19:35:51 Gargoyle kern.crit kernel: [  340.040000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #753666: comm sh: reading directory lblock 0
Mar 21 19:35:51 Gargoyle kern.crit kernel: [  340.040000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #753666: comm sh: reading directory lblock 0
Mar 21 19:35:51 Gargoyle kern.crit kernel: [  340.060000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #753665: comm sh: reading directory lblock 0
Mar 21 19:35:51 Gargoyle kern.crit kernel: [  340.070000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #753666: comm uci: reading directory lblock 0
Mar 21 19:35:51 Gargoyle kern.crit kernel: [  340.080000] EXT4-fs error (device sda1): ext4_find_entry:935: inode #753666: comm uci: reading directory lblock 0
Mar 21 19:36:17 Gargoyle kern.crit kernel: [  366.350000] EXT4-fs error (device sda1): ext4_read_inode_bitmap:161: comm gargoyle_header: Cannot read inode bitmap - block_group = 218, inode_bitmap = 7143425
Mar 21 19:36:17 Gargoyle kern.crit kernel: [  366.370000] EXT4-fs error (device sda1) in ext4_new_inode:941: IO failure
Mar 21 19:37:32 Gargoyle kern.crit kernel: [  441.770000] EXT4-fs error (device sda1): ext4_read_inode_bitmap:161: comm gargoyle_header: Cannot read inode bitmap - block_group = 218, inode_bitmap = 7143425
Mar 21 19:37:32 Gargoyle kern.crit kernel: [  441.790000] EXT4-fs error (device sda1) in ext4_new_inode:941: IO failure
Success

Cezary, możesz zerknąć na to:
root@Gargoyle:~# mount | grep /dev/sd
/dev/sda1 on /overlay type ext2 (rw,noatime,user_xattr,barrier=1)
root@Gargoyle:~# opkg remove plugin-gargoyle-usb-storage
No packages removed.
root@Gargoyle:~# uci del gargoyle.display.system_usb_storage
uci: Entry not found
root@Gargoyle:~# uci del gargoyle.scripts.system_usb_storage
uci: Entry not found
root@Gargoyle:~# uci del gargoyle.system.usb_storage
uci: Entry not found
root@Gargoyle:~# uci commit gargoyle
root@Gargoyle:~# rm /etc/rc.d/S56usb_storage
rm: can't remove '/etc/rc.d/S56usb_storage': No such file or directory
root@Gargoyle:~# opkg update
Downloading http://downloads.openwrt.org/attitude_a … ackages.gz.
Updated list of available packages in /var/opkg-lists/attitude_adjustment.
Downloading http://ecco.selfip.net/attitude_adjustm … ackages.gz.
Updated list of available packages in /var/opkg-lists/eko1.
root@Gargoyle:~# df -h
Filesystem                Size      Used Available Use% Mounted on
rootfs                  966.9M      8.9M    958.0M   1% /
/dev/root                 2.8M      2.8M         0 100% /rom
tmpfs                    14.3M    552.0K     13.7M   4% /tmp
tmpfs                   512.0K         0    512.0K   0% /dev
/dev/sda1               966.9M      8.9M    958.0M   1% /overlay
overlayfs:/overlay      966.9M      8.9M    958.0M   1% /
/dev/mtdblock3          320.0K    252.0K     68.0K  79% /tmp/jffs2
root@Gargoyle:~# mount
rootfs on / type rootfs (rw)
/dev/root on /rom type squashfs (ro,relatime)
proc on /proc type proc (rw,noatime)
sysfs on /sys type sysfs (rw,noatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime)
tmpfs on /dev type tmpfs (rw,noatime,size=512k,mode=755)
devpts on /dev/pts type devpts (rw,noatime,mode=600)
/dev/sda1 on /overlay type ext2 (rw,noatime,user_xattr,barrier=1)
overlayfs:/overlay on / type overlayfs (rw,relatime,lowerdir=/,upperdir=/overlay)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
none on /proc/bus/usb type usbfs (rw,relatime)
/dev/mtdblock3 on /tmp/jffs2 type jffs2 (rw,relatime)
root@Gargoyle:~#

chciałem usunąć to vsftpd ale go nie było
od którego kroku teraz zacząć, abym miał w GUI konfigurowanie FTP, samby

a serwer ftp konfigurowany ręcznie przez putty

albo inaczej, chcę podłączyć dysk HDD i widzieć go w laptopie jako dysk sieciowy, tylko wewnątrz sieci domowej

żeby kopiować na dysk i pobierać z dysku np zdjęcia , filmy itp

faktycznie rozleciał się system jednak po wykonaniu aktualizacji nr 2 z wątku o exroot wszystko ruszyło Pytanie z innej beczki, klient bt ściąga plik na /mnt/sda1/torrenty poprzez ftp widzę i mam możliwość kopiowania plików na komputer, jednak nie mogę usuwać ich z ftp'a np w krusanderze
nie mogę również zmieniać nazw, wychodzi na to ze nie mam praw do edycji folderu torrent, dobrze myślę??
w terminalu wpisałem
chmod 777 /mnt/sda1/torrenty jednak nadal nic
prosze bardziej doświadczonych użytkowników o potwierdzenie lub wyprowadzenie mnie z błędu
pozdrawiam

a jeszcze pytanie o istniejącą partycję FAT na HDD, może pozostać mając extroota na 3420, czy musi być przeformatowany na ext2, no i czy będzie widoczna dla routera i laptopów w sieci?