General NAS-Central Forums

Welcome to the NAS community
It is currently Fri Dec 15, 2017 6:36 am

All times are UTC




Post new topic Reply to topic  [ 54 posts ]  Go to page Previous  1, 2, 3, 4  Next
Author Message
PostPosted: Mon May 18, 2015 2:15 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6091
You have a 2nd NAS? Which brand? Do you have shell access?

Actually I don't know what the options are, as I don't know which tools fvdw included in his stand alone kernel. Maybe that question can be answered by posting the output of
Code:
busybox


Top
 Profile  
 
PostPosted: Mon May 18, 2015 2:19 pm 
Offline

Joined: Tue Apr 28, 2015 12:42 pm
Posts: 27
The second NAS is also a 5big network 2 running Lacie firmware.
I can access it from my laptop with SMB or FTP and already I created a public share for storing the data from the corrupt one.

Tried to use tftp but I get violation errors or messages that files are too big.

Code:
root@fvdw-sta-kirkwood:/ # busybox
BusyBox v1.21.0 (2013-02-04 10:48:06 GMT+1) multi-call binary.
BusyBox is copyrighted by many authors between 1998-2012.
Licensed under GPLv2. See source distribution for detailed
copyright notices.

Usage: busybox [function [arguments]...]
   or: busybox --list[-full]
   or: busybox --install [-s] [DIR]
   or: function [arguments]...

        BusyBox is a multi-call binary that combines many common Unix
        utilities into a single executable.  Most people will create a
        link to busybox for each function they wish to use and BusyBox
        will act like whatever it was invoked as.

Currently defined functions:
        [, [[, acpid, add-shell, addgroup, adduser, adjtimex, arp, arping, ash,
        awk, base64, basename, beep, blkid, blockdev, bootchartd, brctl,
        bunzip2, bzcat, bzip2, cal, cat, catv, chat, chattr, chgrp, chmod,
        chown, chpasswd, chpst, chroot, chrt, chvt, cksum, clear, cmp, comm,
        conspy, cp, cpio, crond, crontab, cryptpw, cttyhack, cut, date, dc, dd,
        deallocvt, delgroup, deluser, depmod, devmem, df, dhcprelay, diff,
        dirname, dmesg, dnsd, dnsdomainname, dos2unix, du, dumpkmap,
        dumpleases, echo, ed, egrep, eject, env, envdir, envuidgid, ether-wake,
        expand, expr, fakeidentd, false, fbset, fbsplash, fdflush, fdformat,
        fdisk, fgconsole, fgrep, find, findfs, flock, fold, free, freeramdisk,
        fsck, fsck.minix, fsync, ftpd, ftpget, ftpput, fuser, getopt, getty,
        grep, groups, gunzip, gzip, halt, hd, hdparm, head, hexdump, hostid,
        hostname, httpd, hush, hwclock, id, ifconfig, ifdown, ifenslave,
        ifplugd, ifup, inetd, init, insmod, install, ionice, iostat, ip,
        ipaddr, ipcalc, ipcrm, ipcs, iplink, iproute, iprule, iptunnel,
        kbd_mode, kill, killall, killall5, klogd, last, less, linux32, linux64,
        linuxrc, ln, loadfont, loadkmap, logger, login, logname, logread,
        losetup, lpd, lpq, lpr, ls, lsattr, lsmod, lsof, lspci, lsusb, lzcat,
        lzma, lzop, lzopcat, makedevs, makemime, man, md5sum, mdev, mesg,
        microcom, mkdir, mkdosfs, mke2fs, mkfifo, mkfs.ext2, mkfs.minix,
        mkfs.vfat, mknod, mkpasswd, mkswap, mktemp, modinfo, modprobe, more,
        mount, mountpoint, mpstat, mt, mv, nameif, nanddump, nandwrite,
        nbd-client, nc, netstat, nice, nmeter, nohup, ntpd, od, openvt, passwd,
        patch, pgrep, pidof, ping, ping6, pipe_progress, pivot_root, pkill,
        pmap, popmaildir, poweroff, powertop, printenv, printf, ps, pscan,
        pstree, pwd, pwdx, raidautorun, rdate, rdev, readlink, readprofile,
        realpath, reboot, reformime, remove-shell, renice, reset, resize, rev,
        rm, rmdir, rmmod, route, rpm, rpm2cpio, rtcwake, run-parts, runlevel,
        runsv, runsvdir, rx, script, scriptreplay, sed, sendmail, seq, setarch,
        setconsole, setfont, setkeycodes, setlogcons, setserial, setsid,
        setuidgid, sh, sha1sum, sha256sum, sha3sum, sha512sum, showkey,
        slattach, sleep, smemcap, softlimit, sort, split, start-stop-daemon,
        stat, strings, stty, su, sulogin, sum, sv, svlogd, swapoff, swapon,
        switch_root, sync, sysctl, syslogd, tac, tail, tar, tcpsvd, tee,
        telnet, telnetd, test, tftp, tftpd, time, timeout, top, touch, tr,
        traceroute, traceroute6, true, tty, ttysize, tunctl, ubiattach,
        ubidetach, ubimkvol, ubirmvol, ubirsvol, ubiupdatevol, udhcpc, udhcpd,
        udpsvd, umount, uname, unexpand, uniq, unix2dos, unlzma, unlzop, unxz,
        unzip, uptime, users, usleep, uudecode, uuencode, vconfig, vi, vlock,
        volname, wall, watch, watchdog, wc, wget, which, who, whoami, whois,
        xargs, xz, xzcat, yes, zcat, zcip


Top
 Profile  
 
PostPosted: Mon May 18, 2015 2:42 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6091
OK. That should be enough to do nice things. Ftpput can be useful for you. According to the busybox manual the syntax is
Code:
ftpput [OPTIONS] HOST REMOTE_FILE LOCAL_FILE

Store a local file on a remote machine via FTP

Options:

        -v,--verbose    Verbose
        -u,--username   Username
        -p,--password   Password
        -P,--port       Port number
Try if you can upload a file this way. If you can, it can be scripted this way:
Code:
find /tmp/mountpoint/shares/ -exec ftpput [OPTIONS] HOST {} {} \;
Here 'find' will search all files in /tmp/mountpoint/shares/, and execute ftpput on it. {} expands to the filename.

Possible problems:
  • Don't know if the directories will be automatically generated on the server.
  • Don't know if busybox can handle huge files. (Nor if the Lacie ftp server can).
  • ...


Top
 Profile  
 
PostPosted: Mon May 18, 2015 3:30 pm 
Offline

Joined: Thu Mar 08, 2012 7:47 pm
Posts: 97
a plugout member tried to backup his files but it take many times (~30 hours) with the fvdw-sl console.

So I think you can try to repair first your partition disk to get directly a clean array.


Top
 Profile  
 
PostPosted: Mon May 18, 2015 3:31 pm 
Offline

Joined: Tue Apr 28, 2015 12:42 pm
Posts: 27
Now get this error :-(

Code:
root@fvdw-sta-kirkwood:/ # find /tmp/mountpoint/shares/ -exec ftpput -v -u ftp -
p ftp1 192.168.10.7 {} {} \;
Connecting to 192.168.10.7 (192.168.10.7:21)
ftpput: cmd (null) (null)
ftpput: cmd USER ftp
ftpput: cmd PASS ftp1
ftpput: cmd TYPE I (null)
ftpput: cmd PASV (null)
ftpput: cmd STOR /tmp/mountpoint/shares/
ftpput: unexpected server response to STOR: 550 /tmp/mountpoint/shares/: Operation not permitted


Probably because I get an ftp connection in the root of the FTP server and not the /TH folder.


Top
 Profile  
 
PostPosted: Mon May 18, 2015 5:21 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6091
Yes, possible. Workaround:
Code:
cd /tmp/mountpoint/shares/
find . -exec ftpput -v -u ftp -p ftp1 192.168.10.7 {} {} \;


@Jocko: Of course that's a possibility. But we have 5 disks, from the same batch, which during their lifetime have been accessed exactly the same. Now one is down. If you now start loading them to rebuild the 5th member, what are the odds that a 2nd one will fail?
That's why I don't like raid arrays.


Top
 Profile  
 
PostPosted: Mon May 18, 2015 5:29 pm 
Offline

Joined: Thu Mar 08, 2012 7:47 pm
Posts: 97
@Mijzelf

I agree with you. My purpose is to repair temporarily the raid to allow to start Lacie firmware and backup data because currently we don't have feedback of members who succeed fully to backup their data via fvdw-sl console.
http://plugout.net/viewtopic.php?f=26&t=1412&start=380

and after pacco should plan to change all disks...

@fvdw
static e2fsck package is corrupted on plugout. Can you upload it again.


Top
 Profile  
 
PostPosted: Mon May 18, 2015 5:43 pm 
Offline

Joined: Tue Apr 28, 2015 12:42 pm
Posts: 27
@Mijzelf
Same problem. Remote share is not the root, but /TH. My guess ftpput tries to connect to the root.

Code:
root@fvdw-sta-kirkwood:/tmp/mountpoint/shares # find . -exec ftpput -v -u ftp -p
 ftp1 192.168.10.7 {} {} \;
Connecting to 192.168.10.7 (192.168.10.7:21)
ftpput: cmd (null) (null)
ftpput: cmd USER ftp
ftpput: cmd PASS ftp1
ftpput: cmd TYPE I (null)
ftpput: cmd PASV (null)
ftpput: cmd STOR .
ftpput: unexpected server response to STOR: 550 .: Operation not permitted


@both
First of all I really appreciate your help!!! As soon as we are able to backup the data to another device I will replace everything ASAP. Maybbe QNAP. Data is too important for me.

Regards,

Frank


Top
 Profile  
 
PostPosted: Mon May 18, 2015 6:10 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6091
I don't think replacement is necessary. Your problem is not that the Lacie is crappy, the problem is that you don't have a backup. If you would have had a backup there was no problem at all.

Back to the problem. The error you show is that you can't store a directory. It doesn't matter the ftp share is not the root, it's a relative address. You can try to handle files alone.
Code:
cd /tmp/mountpoint/shares/
find . -type f -exec ftpput -v -u ftp -p ftp1 192.168.10.7 {} {} \;


What is the nature of the data? A few big files or a zillion small ones in numerous directories?


Top
 Profile  
 
PostPosted: Mon May 18, 2015 6:18 pm 
Offline

Joined: Tue Apr 28, 2015 12:42 pm
Posts: 27
True, a backup of data would solve it all. But I purchased the device with RAID5 especially to have a backup of old data. Even put a spare disk on top if one of the disks would fail so I can replace it ASAP.

Anyway, problem is with FTP on the other NAS. When I login to the NAS using FTP I go into the root folder and first have to change directory to TH. Then I can write to it. I suppose the same happens with the ftpput command.

Mostly large files. But some folders with a lot of small files.

Code:
C:\Temp>ftp 192.168.10.7
Verbonden met 192.168.10.7.
220 LACIE FTP Server [192.168.10.7]
Gebruiker (192.168.10.7:(none)): ftp
331 Password required for ftp
Wachtwoord:
230 User ftp logged in
ftp> mkdir test
550 test: Permission denied
ftp> cd TH
250 CWD command successful
ftp> mkdir test
257 "/TH/test" - Directory successfully created
ftp> ls
200 PORT command successful
150 Opening ASCII mode data connection for file list
test
226 Transfer complete
ftp: 6 bytes ontvangen in 0,00 seconden 6000,00 kB/s.
ftp> quit
221 Goodbye.

C:\Temp>


Top
 Profile  
 
PostPosted: Mon May 18, 2015 6:30 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6091
Ah I see. Does
Code:
find . -type f -exec ftpput -v -u ftp -p ftp1 192.168.10.7 /TH/{} {} \;
work? Or do you really have to chdir first?

Quote:
But I purchased the device with RAID5 especially to have a backup of old data.
RAID5 is *not* a backup.


Top
 Profile  
 
PostPosted: Mon May 18, 2015 6:37 pm 
Offline

Joined: Tue Apr 28, 2015 12:42 pm
Posts: 27
Think I really have to chdir first.

Code:
root@fvdw-sta-kirkwood:/tmp/mountpoint/shares # find . -type f -exec ftpput -v -
u ftp -p ftp1 192.168.10.7 TH/{} {} \;
Connecting to 192.168.10.7 (192.168.10.7:21)
ftpput: cmd (null) (null)
ftpput: cmd USER ftp
ftpput: cmd PASS ftp1
ftpput: cmd TYPE I (null)
ftpput: cmd PASV (null)
ftpput: cmd STOR TH/./1/Oude gebruikers Tendris/ALANGEMEYER.PST
ftpput: unexpected server response to STOR: 550 TH/./1/Oude gebruikers Tendris/ALANGEMEYER.PST: No such file or directory


Quote:
RAID5 is *not* a backup.

True! Guess I relied on RAID to much. Next stop...make regular backups of the device.

Isn't it possible to use another program to "ftp" the files? Ftpput is limited.


Top
 Profile  
 
PostPosted: Mon May 18, 2015 6:38 pm 
Offline

Joined: Thu Mar 08, 2012 7:47 pm
Posts: 97
Mijzelf wrote:
RAID5 is *not* a backup.
Many people believe it wrongly ... :mrgreen:

@pacco
About your ftp user account can you change its home directory to be chrooted in TH ?


Last edited by Jocko on Mon May 18, 2015 6:49 pm, edited 1 time in total.

Top
 Profile  
 
PostPosted: Mon May 18, 2015 6:43 pm 
Offline

Joined: Tue Apr 28, 2015 12:42 pm
Posts: 27
Quote:
@pacco
About your ftp user account can you change its home directory to be chrooted in TH ?

Jocko, the irony is that the only device available is a 2nd Lacie 5big network 2 and I created a share (TH) and a user (ftp) that has only access to that share.

Already tried to search for a way to directly access that share. Unfortunately I didn't find a solution yet.

Otherwise I have to wait till Wednesday (even Thursday) to get an external disk large enough to store the data. But I am afraid something might happen to the system before Thursday.

Regards,

Frank


Top
 Profile  
 
PostPosted: Mon May 18, 2015 6:48 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6091
Maybe httpd is usable.
Code:
cd /tmp/mountpoint/shares/
httpd
Now you can access your NAS by a browser. If it shows a directory listing, you can use any site scraper to download the files. But again, I don't know how it will handle huge files.

Another option is the use of nc (netcat). But for that you need to run nc on both ends. So maybe you'll have to run the stand alone kernel on the 2nd NAS either.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 54 posts ]  Go to page Previous  1, 2, 3, 4  Next

All times are UTC


Who is online

Users browsing this forum: Bing [Bot] and 12 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group