Loading ...
Sorry, an error occurred while loading the content.

Re: Backup fails on Unslung 5.5

Expand Messages
  • bty597733
    Sorry my mistake (damm keyboard), the message should read... over 6 hours to back up just 45gb of data! ... on ... After ... 2 ${LOG}.err ... the ... of ... up
    Message 1 of 4 , Jun 25, 2007
    • 0 Attachment
      Sorry my mistake (damm keyboard), the message should read... over 6
      hours to back up just 45gb of data!

      --- In nslu2-general@yahoogroups.com, "bty597733" <j.wolves@...>
      wrote:
      >
      > Tahnks for the link Mike,
      >
      > I have followed the instructions are have indeed managed a valid
      > backup. However, it did take over 6 hours to backup 251 Gb of data
      > on it's first (and so far only) run!
      >
      > 06/24 19:08:30 Drive Backup: Backup complete.
      > 06/24 12:28:08 Drive Backup: Backup start.
      >
      > I have proven the data is backed by up mounting the backup drive
      on
      > my Windows PC, and my slug boots perfectly when plugging my backup
      > disk into Disk 1, allowing access to my data :-)
      >
      > Just to clarify on the instructions for any one reading this.
      After
      > installing rsync. I deleteed the file 'S57rsyncd' from the
      > directory /opt/etc/init.d.
      >
      > The full drivertodrivercp script (/usr/sbin) is as follows:
      >
      > #!/bin/sh
      >
      > if [ -f /tmp/Scanning ]; then
      > /usr/sbin/set_log backup 1 1
      > exit 1
      > fi
      >
      > if [ -f /tmp/Upgrading ]; then
      > /usr/sbin/set_log backup 1 2
      > exit 1
      > fi
      >
      > if [ -f /tmp/Preparing ]; then
      > /usr/sbin/set_log backup 1 3
      > exit 1
      > fi
      >
      > if [ -f /tmp/Moving ]; then
      > /usr/sbin/set_log backup 1 9
      > exit 1
      > fi
      >
      > if [ -f /tmp/DriveBackuping ]; then
      > exit 1
      > fi
      >
      > if [ -e /share/hdd/conf/.dongle ];then
      > else
      > /usr/sbin/set_log backup 0 1
      > exit 1
      > fi
      >
      >
      > if [ -e /share/flash/conf/.dongle ];then
      > else
      > /usr/sbin/set_log backup 0 1
      > exit 1
      > fi
      >
      > F_HD1=`/bin/cat /share/hdd/conf/.dongle`
      > F_HD2=`/bin/cat /share/flash/conf/.dongle`
      > if [ "$F_HD1" != "$F_HD2" ]; then
      > /usr/sbin/set_log backup 0 12
      > exit 1
      > fi
      >
      > /usr/sbin/CheckBackup
      > if [ $? = 1 ]; then
      > /usr/sbin/set_log backup 0 14
      > exit 1
      > elif [ $? = 2 ];then
      > /usr/sbin/set_log backup 0 15
      > exit 1
      > elif [ $? = 3 ];then
      > /usr/sbin/set_log backup 0 12
      > exit 1
      > fi
      >
      > /usr/sbin/set_log backup 0 3
      > touch /tmp/DriveBackuping
      >
      > LOGDIR=/share/hdd/log
      > # Keep seven days of backup logs named after days of the week
      >
      > LOGBASE=${LOGDIR}/rsync.`date +%A`
      >
      > #To make logging verbose, turn the "-q" into "-v"
      > RSYNC="/opt/bin/rsync -a -H -q --delete"
      >
      > # Backup the conf directory, log to a specific file
      > DIR=conf
      > LOG=${LOGBASE}.${DIR}
      > #
      > # Syntax matters. Do not put ampersands (&) on the rsync command)
      > # It already runs in a crontab
      > # The separation of logging also separates error messages into a
      > separate file.
      > # To keep it in the same file, use "2>${LOG}"
      >
      > ${RSYNC} /share/hdd/${DIR}/ /share/flash/${DIR} 1>${LOG}
      2>${LOG}.err
      > # If conf backup succeeds, backup the data dir
      > if [ $? = 0 ]; then
      > DIR=data
      > LOG=${LOGBASE}.${DIR}
      > ${RSYNC} /share/hdd/${DIR}/ /share/flash/${DIR} 1>${LOG}
      > 2>${LOG}.err
      > fi
      >
      >
      > if [ $? = 0 ]; then
      > /usr/sbin/set_log backup 0 4
      > else
      > /usr/sbin/set_log backup 0 13
      > fi
      >
      > rm -f /tmp/DriveBackuping
      >
      > /usr/sbin/CheckDiskFull
      >
      >
      >
      > --- In nslu2-general@yahoogroups.com, "Mike \(mwester\)"
      > <mwester@> wrote:
      > >
      > > The wiki search says:
      > >
      > > http://www.nslu2-
      > linux.org/wiki/HowTo/FixTheDriveBackupForUnslungFirmware
      > >
      > > Mike (mwester)
      > >
      > > ----- Original Message -----
      > > From: "bty597733" <j.wolves@>
      > > To: <nslu2-general@yahoogroups.com>
      > > Sent: Saturday, June 23, 2007 6:20 PM
      > > Subject: [nslu2-general] Backup fails on Unslung 5.5
      > >
      > >
      > > I have recently invested in a 2nd Maxtor hard disk for my nslu2
      > > (running unslung 5.5) and after plugging the drive into Desk
      > port2,
      > > rebooting my slug, and formatting the new disk via the web
      > > interface; I set the back up to run every Sunday night and hit
      the
      > > Start Back Up Now button to get thing started. Over twho hours
      of
      > > disk activity later the backup was complete. However, the back
      up
      > > log contains the following:
      > >
      > > 06/23 18:06:09 Drive Backup: Backup fail.
      > > 06/23 15:48:52 Drive Backup: Backup start.
      > >
      > > Suspicious of this (if the back up failed what was my disk doing
      > for
      > > over 2 hours), I disabled the back up feature (allowing my disk
      to
      > > be seen by the web interface), and a duplicate of each of my
      > shares
      > > was available. Connecting the drive to my Windows PC (using
      www.fs-
      > > driver.org) show my data is indeed backed up!
      > >
      > > However, connecting the backup drive to my slug in disk 1, and
      > > booting up prevents me from accessing the web interface or the
      > > disk's contents.
      > >
      > > Hopefully someone can answer the following questions:
      > >
      > > - Is there a problem with the disk backup on unslung 5.5 that is
      > > causing Backup fail message in the log?
      > > - Does the backup only backup my shares and not the files
      > associated
      > > with unslung? If so, what is the recommended procedure to get my
      > > system back up and running if my primary disk fails?
      > >
      > > Any answers this group can provide is much appreciated.
      > >
      > > With thanks, Jason.
      > >
      >
    Your message has been successfully submitted and would be delivered to recipients shortly.