Other Help Topics :: error running fieltool.sh



I`m unable to make a backup file with the Backup/Restore menu.
No back backup.tar.gz file is being made, file /.backup_device has sda1 in it.
I found the command is "filetool.sh" & the GUI is filetool.lua thru /.fluxbox/menu.
This is the response from running "filetool.sh backup sda1" at command prompt.
The Broken pipe part is the same as an error on shutdown.

@ = little square made of dots.

@1;34mBacking up files to /cdrom
/mnt/sda1 @[0;39m/@[1]+   Broken pipe       tar -C / -T $HOME/filetool.lst --exclude-Cache -czf $MOUNTPOINT/backup.tar.gz 2>/dev/null
-@\@|@@[1;34mDone.@[0;39m
----end-of-output----
Trying to write to a non writeable device will surely break your pipes.
Why would sda1 the flash drive be nonwritable?
Clean install to Usb drive doesn`t fix problem.
Drive work before so it`s not at fault.
It seems to be a misdirection of a path, but how?
Roberts i think didn't see your sda1..and only saw /cdrom

Uh...I have the same problem sunburnt..I've determined its a race condition, and I thought i was the ONLY one who had it as i've been unable to find anyone else to repeat the condition..

The file you're looking for is not /.backup_device but /opt/.backup_device

A race condition because I can manually do backup (as root, from a terminal - open terminal type 'sudo su ; filetool.sh backup' ) and it works flawlessly everytime...its crappy because my auto-backup doesn't work all of the time (pipe doesn't break all the time, so it works occasionally, a race condition for me because its RANDOM and can only be a race condition if it works the rest of the time.

anyway, like i've said, i think its a race condition...i got tired of it, so i started backing up to my usb drive manually everytime...just got pissed that no one knew anything about it or had the same problem ;p and thats the easiest way to avoid it...but um...here are some suggestions...

i'm not at my console right now, but if there is a 'sleep' or 'wait' or a timer type command, put the backup script on a timer, or, write a shellscript to do it for you...that way it will isolate the backup routine (while its not trying to shut down everything else, etc) and will hopefully terminate race conditions.

i hope this helps, please tell me what happens. ;)
A listing of running filetool.sh from console as root.

root@ttyp0[dsl]# /usr/sbin/filetool.sh backup
tar: /mnt/sda1/backup.tar.gz: Cannot stat: No such file or dir.

  then comes a list of the /opt directory

/cdrom: Cannot open: Is a directory
tar (child): Error is not recoverable: exiting now

  then comes the rest of the /opt dir. & /home dir.

Press enter to continue:
root@ttyp0[dsl]#

  When I type "sda1" at the end it changes.

root@ttyp0[dsl]# /usr/sbin/filetool.sh backup sda1
Backing up files to /cdrom
/mnt/sda1 [1]+  Broken pipe     tar -C / -T $HOME/filetool.lst
  --exclude=Cache -czf $MOUNTPOINT/backup.tar.gz 2>/dev/null
Done.

  It seems there`s something seriously wrong with the PATH
     & or system variables;  "$MOUNTPOINT" ?    Don`t know!
  Your right about the "filetool.sh" path, I just didn`t type it.
Next Page...
original here.