New Application: S. N. A. P.


Recommended Posts

  • Replies 566
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Posted Images

I have a drive which was formatted to ext3 I think from a Synolody DS unit, can you mount this USB drive also with SNAP?

 

Here are my notes in the code.

 

'ext2')

# mount the partition ...

# Note: It seems that unRAID version of slackware doesn't have the ext3 driver.

#      http://lime-technology.com/forum/index.php?topic=5777.0

#      Joe L. There is no ext3 driver module in unRAID, but if the ext3 file-system

#      was cleanly unmounted, and there are no journal entries to replay, it may be mounted as ext2.

mountOptions="-t $filesystem"

readonlyflag="-r"

;;

'ext3')

# mount the partition ...

# Note: It seems that unRAID version of slackware doesn't have the ext3 driver.

#      http://lime-technology.com/forum/index.php?topic=5777.0

#      Joe L. There is no ext3 driver module in unRAID, but if the ext3 file-system

#      was cleanly unmounted, and there are no journal entries to replay, it may be mounted as ext2.

mountOptions="-t ext2"

readonlyflag="-r"

Link to comment

I have UnRaid 5.0b6a and I'm trying to install SNAP.  So far i have put the two files in the flash drive, in the correct director but when i click on the SNAP update button nothing happens and dont see any buttons to install.  

 

Also I am new to UnRaid so i dont really know what you need from me to see what the problem is.

 

Thanks for the help

 

I think I fixed it and put a new set of buttons at the bottom of the first post in this thread.

Thanks to everyone who reported the problem.  

 

It appears to be a difference in how google code returns the file name.  Originally it returned like: http://unraid-snap.googlecode.com/files/snap-.*.tgz

But now it's arriving like this: //unraid-snap.googlecode.com/files/snap-.*.tgz

So a change in the pattern matching is all that was required.

 

 

Edit 7/29/2011:  I posted a newer version of the buttons again today.  Changed the pattern matching to work as is now but also still work if google code changes back to previous pattern.

Link to comment

echo "Running hotPlugAfterShareEvent.sh"

case $SHARENAME in

'bluec4')

beep  -l 100 -f 2000 -n -l 150 -f 3000

beep  -l 100 -f 2000 -n -l 150 -f 3000

if [ ! -d /mnt/disk3/backup/bluec4 ]

then

mkdir /mnt/disk3/backup/bluec4

fi

cp -u -r $MOUNTPOINT/* /mnt/disk3/backup/bluec4 2>&1 >>

$SNAPLOGDIRECTORY/hotPlugAfterShareEvent.log

# changing the file attributes so they will be visible by client windows machines.

  chmod 666 $destination/*

beep  -l 100 -f 2000 -n -l 150 -f 3000

beep  -l 100 -f 2000 -n -l 150 -f 3000

beep  -r 5 -l 100 -f 2000

;;

esac

 

----------------------------------------------

The above is  the part i modified from your sample

 

When i run this nothing happens, i plug /unplug the usb stick (bluec4)

 

My goal was to have SNAP automatically

copy all files from the usb stick (bluec4) to my unraid (disk3 -this is the name which is displayed in windows)

to a folder called backup

 

 

As a side note:

 

I can see the usb stick (bluec4) in windows share and can access it fine, copy and delete also ok.

 

I would appreciate some help working this out....

Thanks

Joe

 

Link to comment

echo "Running hotPlugAfterShareEvent.sh"

case $SHARENAME in

'bluec4')

beep  -l 100 -f 2000 -n -l 150 -f 3000

beep  -l 100 -f 2000 -n -l 150 -f 3000

if [ ! -d /mnt/disk3/backup/bluec4 ]

then

mkdir /mnt/disk3/backup/bluec4

fi

cp -u -r $MOUNTPOINT/* /mnt/disk3/backup/bluec4 2>&1 >>

$SNAPLOGDIRECTORY/hotPlugAfterShareEvent.log

# changing the file attributes so they will be visible by client windows machines.

  chmod 666 $destination/*

beep  -l 100 -f 2000 -n -l 150 -f 3000

beep  -l 100 -f 2000 -n -l 150 -f 3000

beep  -r 5 -l 100 -f 2000

;;

esac

 

----------------------------------------------

The above is  the part i modified from your sample

 

When i run this nothing happens, i plug /unplug the usb stick (bluec4)

 

My goal was to have SNAP automatically

copy all files from the usb stick (bluec4) to my unraid (disk3 -this is the name which is displayed in windows)

to a folder called backup

 

 

As a side note:

 

I can see the usb stick (bluec4) in windows share and can access it fine, copy and delete also ok.

 

I would appreciate some help working this out....

Thanks

Joe

 

 

While you are telnet'd in; cd over to the disk3 share and see if the files are there.  They may be not visible from Windows for some reason.

I noticed that you are using the -u flag.  Maybe the files are already there so nothing happens.  Let me know.

Windows caching can play around with shares.  Have you been using a share for some time or is this the first one? 

Also, have you looked in the logs to see if there are any messages?  They are in /var/log/snap.

 

Link to comment

queeg,

 

I did a cd to disk3 but could not see the backup dir

When i plug the usb stick in (bluec4) I do get a set of tones then a pause then a set of tones.

But there is very little time between the tones - leading me to believe it could not copy that fast.

 

I removed the - u - no change.

 

I can see the bluec4 in windows share.

 

I checked the snap event logs but did not see any thing with reference to bluec4 usb etc

 

Joe

Link to comment

queeg,

 

I did a cd to disk3 but could not see the backup dir

When i plug the usb stick in (bluec4) I do get a set of tones then a pause then a set of tones.

But there is very little time between the tones - leading me to believe it could not copy that fast.

 

I removed the - u - no change.

 

I can see the bluec4 in windows share.

 

I checked the snap event logs but did not see any thing with reference to bluec4 usb etc

 

Joe

 

If you are hearing the beeps then it must be running over the cp command.  There must be an error. 

It may be a spelling error in a name or something.

Reply with the output of the snap.list file. 

cat snap.list

 

Is it possible you have a file named bluec4 in the /mnt/disk3/backup folder?

Link to comment

queeg,

 

 

Here is the content of snap.list

 

 

DEF10B1916B3-0:0=USBFIREFLY

DEF106207355-0:0=EXTWD250

0F1007579239-0:0=netdisk80

20060572910EF1A2098C-0:0=bluec4

 

I decided to reformat the usb stick (ntfs) and noticed I get the ist set of  tones, but now I see activity on the usb stick led indicating like it was copying

then i get the second set of tones.

 

I looked at disk3 on my unraid by telnet - but no Backup dir...

 

I also looked at disk3 windows unraid share and did not find and new directory either

Also  there is no Backup/bluec4 dir

 

I am logged in on the telnet as root.

 

I wonder if the cp does not have sufficient permissions to mkdir and copy? -- I am noob so just thinking out loud....

 

my syslog:

Aug  3 11:54:59 Tower39 kernel: sd 29:0:0:0: [sdh] Attached SCSI removable disk

Aug  3 11:55:03 Tower39 ntfs-3g[24812]: Version 2010.3.6 integrated FUSE 27

Aug  3 11:55:03 Tower39 ntfs-3g[24812]: Mounted /dev/sdh1 (Read-Write, label "MULTIBOOT", NTFS 3.1)

Aug  3 11:55:03 Tower39 ntfs-3g[24812]: Cmdline options: rw,umask=111,dmask=000

Aug  3 11:55:03 Tower39 ntfs-3g[24812]: Mount options: rw,silent,allow_other,nonempty,relatime,fsname=/dev/sdh1,blkdev,blksize=4096,default_permissions

Aug  3 11:55:03 Tower39 ntfs-3g[24812]: Global ownership and permissions enforced, configuration type 1

 

Thanks again for your support

Joe

 

hotPlugAfterShareEvent.txt

Link to comment

queeg,

I looked at disk3 on my unraid by telnet - but no Backup dir...

 

I also looked at disk3 windows unraid share and did not find and new directory either

Also  there is no Backup/bluec4 dir

 

Joe

 

Which way is the backup directory spelled?  mkdir will only create the last directory in the path given to it.

 

if [ ! -d /mnt/disk3/backup/bluec4 ]

  then

      mkdir /mnt/disk3/backup/bluec4

  fi

  cp -u -r $MOUNTPOINT/* /mnt/disk3/backup/bluec4 2>&1 >>

$SNAPLOGDIRECTORY/hotPlugAfterShareEvent.log

Link to comment

queeg,

 

I finally got it working with this:

 

echo "Running hotPlugAfterShareEvent.sh"

case $SHARENAME in

'bluec4')

# MAKE A BEEP STARTING COPY SOUND ----------------------------------

beep  -l 100 -f 2000 -n -l 150 -f 3000

beep  -l 100 -f 2000 -n -l 150 -f 3000

#ASSIGN A LOCATION WHERE YOU WANT DATA TO BE COPIED TO -------------

destination="/mnt/disk3/blueC4data"

#IF DESTINATION DOES NOT EXIST THEN MAKE DIRECTORY------------------

if [ ! -d $destination ]

then

mkdir $destination

fi

#COPY ALL AND SUBDIRS FROM WHERE THE SNAP SHARE IS MOUNTED(MOUNTPOINT) TO THE DESTINATION (disk3/blueC4data)

       #

cp -r $MOUNTPOINT/* $destination 2>&1 >> $SNAPHOME/hotPlugAfterShareEvent.log

       #

# MAKE WINDOWS SHARE VISABLE PLUS READ / WRITE -----------------------

#

       chmod 666 $destination/*

       #

#BEEP JOB IS DONE-----------------------------------------------------

beep  -l 100 -f 2000 -n -l 150 -f 3000

beep  -l 100 -f 2000 -n -l 150 -f 3000

beep  -r 5 -l 100 -f 2000

;;

esac

--------------------------------------------------------------------------------------------------------

 

 

1. What command structure would I use if I wanted to copy only the new dir and or files to destination disk3/blueC4data?

In other words I would like the script to check to see if any files on the usb stick are already at the destination (disk3/blueC4data) and if yes then do not copy over existing only copy new files?

 

2. Where would i add the name to make another but similar script work as well...  I have another usb stick (blackc4)

 

Thanks again for your support

Joe

 

 

 

Link to comment

queeg,

 

I finally got it working with this:

 

echo "Running hotPlugAfterShareEvent.sh"

case $SHARENAME in

'bluec4')

# MAKE A BEEP STARTING COPY SOUND ----------------------------------

beep  -l 100 -f 2000 -n -l 150 -f 3000

beep  -l 100 -f 2000 -n -l 150 -f 3000

#ASSIGN A LOCATION WHERE YOU WANT DATA TO BE COPIED TO -------------

destination="/mnt/disk3/blueC4data"

#IF DESTINATION DOES NOT EXIST THEN MAKE DIRECTORY------------------

if [ ! -d $destination ]

then

mkdir $destination

fi

#COPY ALL AND SUBDIRS FROM WHERE THE SNAP SHARE IS MOUNTED(MOUNTPOINT) TO THE DESTINATION (disk3/blueC4data)

       #

cp -r $MOUNTPOINT/* $destination 2>&1 >> $SNAPHOME/hotPlugAfterShareEvent.log

       #

# MAKE WINDOWS SHARE VISABLE PLUS READ / WRITE -----------------------

#

       chmod 666 $destination/*

       #

#BEEP JOB IS DONE-----------------------------------------------------

beep  -l 100 -f 2000 -n -l 150 -f 3000

beep  -l 100 -f 2000 -n -l 150 -f 3000

beep  -r 5 -l 100 -f 2000

;;

esac

--------------------------------------------------------------------------------------------------------

 

 

1. What command structure would I use if I wanted to copy only the new dir and or files to destination disk3/blueC4data?

In other words I would like the script to check to see if any files on the usb stick are already at the destination (disk3/blueC4data) and if yes then do not copy over existing only copy new files?

 

2. Where would i add the name to make another but similar script work as well...  I have another usb stick (blackc4)

 

Thanks again for your support

Joe

 

Try this.  It will copy updated and new files only.  It will work for both sharenames and create a folder for each using ${SHARENAME}data

rsync -aq --size-only $MOUNTPOINT/* $destination/ 2>&1 >> $SNAPHOME/hotPlugAfterShareEvent.log

 

 

echo "Running hotPlugAfterShareEvent.sh"

case $SHARENAME in

'bluec4' | 'blackc4')

# MAKE A BEEP STARTING COPY SOUND ----------------------------------

beep  -l 100 -f 2000 -n -l 150 -f 3000

beep  -l 100 -f 2000 -n -l 150 -f 3000

#ASSIGN A LOCATION WHERE YOU WANT DATA TO BE COPIED TO -------------

 

destination="/mnt/disk3/${SHARENAME}data"

 

 

#IF DESTINATION DOES NOT EXIST THEN MAKE DIRECTORY------------------

if [ ! -d $destination ]

then

mkdir $destination

fi

#COPY ALL AND SUBDIRS FROM WHERE THE SNAP SHARE IS MOUNTED(MOUNTPOINT) TO THE DESTINATION (disk3/blueC4data)

        #

rsync -aq --size-only $MOUNTPOINT/* $destination/ 2>&1 >> $SNAPHOME/hotPlugAfterShareEvent.log

        #

# MAKE WINDOWS SHARE VISABLE PLUS READ / WRITE -----------------------

#

        chmod 666 $destination/*

        #

#BEEP JOB IS DONE-----------------------------------------------------

beep  -l 100 -f 2000 -n -l 150 -f 3000

beep  -l 100 -f 2000 -n -l 150 -f 3000

beep  -r 5 -l 100 -f 2000

;;

esac

 

Link to comment

Queeg,

 

Yeehah!! - EXCELLENT - Works like a charm.

 

I modified the script with your suggestions then:

 

Plugged in the blue usb and it beeped and copied. .and beeped again... then tried the black usb and it worked as well

 

I see the new dirs in disk 3 - and can read /write / delete - files

 

 

Thanks again, for the support  and for a great UNRAID Addon!!

 

Joe

Link to comment

Hi,

 

I'm currently trying to install S.N.A.P. to my Unraid server using the install procedure for non unMenu users. Not helping in this endeavour is the fact that I know VERY little about linux.

 

Anyway, the procedure is listed like this....

 

How to install SNAP updates without unMenu.

Download the 0.47 version tar file from here.  Telnet to unRAID. 

 

All OK here. I use Putty to Telnet to unRAID.

 

cd /tmp

mkdir snap

 

OK - done and the CLI allows me to go into the snap directory so I know it's created OK.

 

Then copy the downloaded tar file to /tmp/snap directory. 

 

This is currently where I'm coming unstuck. I've downloaded the zip file, extracted the tgz file, but HOW do I copy this file from my Windows PC to the /tmp/snap file? I can't SEE the /tmp/snap directory I've created on UnRAID from my Windows PC so I can't copy & paste it there.

 

ANY help explaining to a linux noob how to do this is appreciated!

Link to comment

Hi,

 

I'm currently trying to install S.N.A.P. to my Unraid server using the install procedure for non unMenu users. Not helping in this endeavour is the fact that I know VERY little about linux.

 

Anyway, the procedure is listed like this....

 

How to install SNAP updates without unMenu.

Download the 0.47 version tar file from here.  Telnet to unRAID. 

 

All OK here. I use Putty to Telnet to unRAID.

 

cd /tmp

mkdir snap

 

OK - done and the CLI allows me to go into the snap directory so I know it's created OK.

 

Then copy the downloaded tar file to /tmp/snap directory. 

 

This is currently where I'm coming unstuck. I've downloaded the zip file, extracted the tgz file, but HOW do I copy this file from my Windows PC to the /tmp/snap file? I can't SEE the /tmp/snap directory I've created on UnRAID from my Windows PC so I can't copy & paste it there.

 

ANY help explaining to a linux noob how to do this is appreciated!

 

I see your point.  I missed a step there.  You can copy the tar file from Windows to \\tower\flash and then from your telnet connection the file will be in the /boot folder.

Copy it to the /tmp/snap folder.

 

cp /boot/snap-0.47*.tgz /tmp/snap

 

I'll update the post with that step for future readers.  :)

Link to comment

Thanks very much. That worked fine.

 

NEXT ISSUE....

 

OK, so after ensuring SNAP had installed OK, I tried assigning a drive to SNAP - in this case I have an Intel SSD in the server that I want to have visible to the network (enter SNAP!)

 

I ran the -listDevInfo switch and got the following....

 

root@Server:~# /boot/config/snap/snap.sh -listDevInfo

unRAID=No  SNAP=No  4117  /dev/sdi  ata-INTEL_SSDSA2CT040G3_CVPR122604U3040AGN

unRAID=Yes SNAP=No  3918  /dev/sdg  ata-WDC_WD15EADS-00S2B0_WD-WCAVY0888436

unRAID=Yes SNAP=No  3463  /dev/sda  ata-WDC_WD15EADS-00S2B0_WD-WCAVY0965613

unRAID=Yes SNAP=No  3993  /dev/sdh  ata-WDC_WD15EARS-00J2GB0_WD-WCAYY0115615

unRAID=Yes SNAP=No  4195  /dev/sdj  ata-WDC_WD15EARS-00S8B1_WD-WCAVY3658864

unRAID=Yes SNAP=No  3692  /dev/sdd  ata-WDC_WD20EARS-00MVWB0_WD-WCAZA0211921

unRAID=Yes SNAP=No  3617  /dev/sdc  ata-WDC_WD20EARS-00MVWB0_WD-WMAZA1287165

unRAID=Yes SNAP=No  3542  /dev/sdb  ata-WDC_WD20EARS-00S8B1_WD-WCAVY5771699

unRAID=Yes SNAP=No  3767  /dev/sde  ata-WDC_WD20EARX-00PASB0_WD-WCAZA7438649

unRAID=No  SNAP=No  4117  /dev/sdi  scsi-SATA_INTEL_SSDSA2CT0CVPR122604U3040AGN

unRAID=Yes SNAP=No  3918  /dev/sdg  scsi-SATA_WDC_WD15EADS-00_WD-WCAVY0888436

unRAID=Yes SNAP=No  3463  /dev/sda  scsi-SATA_WDC_WD15EADS-00_WD-WCAVY0965613

unRAID=Yes SNAP=No  4195  /dev/sdj  scsi-SATA_WDC_WD15EARS-00_WD-WCAVY3658864

unRAID=Yes SNAP=No  3993  /dev/sdh  scsi-SATA_WDC_WD15EARS-00_WD-WCAYY0115615

unRAID=Yes SNAP=No  3542  /dev/sdb  scsi-SATA_WDC_WD20EARS-00_WD-WCAVY5771699

unRAID=Yes SNAP=No  3692  /dev/sdd  scsi-SATA_WDC_WD20EARS-00_WD-WCAZA0211921

unRAID=Yes SNAP=No  3617  /dev/sdc  scsi-SATA_WDC_WD20EARS-00_WD-WMAZA1287165

unRAID=Yes SNAP=No  3767  /dev/sde  scsi-SATA_WDC_WD20EARX-00_WD-WCAZA7438649

unRAID=No  SNAP=No  3845  /dev/sdf  usb-SanDisk_U3_Cruzer_Micro_0000060410037537-0:0

 

The SSD is very easy to see in this list. I then assigned it to SNAP (gave the disk the name ZAPPITI) and ran the -listDevInfo switch again....

 

root@Server:~# /boot/config/snap/snap.sh -a SSDSA2CT0CVPR122604U3040AGN ZAPPITI

root@Server:~# /boot/config/snap/snap.sh -listDevInfo

unRAID=No  SNAP=No  4117  /dev/sdi  ata-INTEL_SSDSA2CT040G3_CVPR122604U3040AGN

unRAID=Yes SNAP=No  3918  /dev/sdg  ata-WDC_WD15EADS-00S2B0_WD-WCAVY0888436

unRAID=Yes SNAP=No  3463  /dev/sda  ata-WDC_WD15EADS-00S2B0_WD-WCAVY0965613

unRAID=Yes SNAP=No  3993  /dev/sdh  ata-WDC_WD15EARS-00J2GB0_WD-WCAYY0115615

unRAID=Yes SNAP=No  4195  /dev/sdj  ata-WDC_WD15EARS-00S8B1_WD-WCAVY3658864

unRAID=Yes SNAP=No  3692  /dev/sdd  ata-WDC_WD20EARS-00MVWB0_WD-WCAZA0211921

unRAID=Yes SNAP=No  3617  /dev/sdc  ata-WDC_WD20EARS-00MVWB0_WD-WMAZA1287165

unRAID=Yes SNAP=No  3542  /dev/sdb  ata-WDC_WD20EARS-00S8B1_WD-WCAVY5771699

unRAID=Yes SNAP=No  3767  /dev/sde  ata-WDC_WD20EARX-00PASB0_WD-WCAZA7438649

unRAID=No  SNAP=Yes 4117  /dev/sdi  scsi-SATA_INTEL_SSDSA2CT0CVPR122604U3040AGN

unRAID=Yes SNAP=No  3918  /dev/sdg  scsi-SATA_WDC_WD15EADS-00_WD-WCAVY0888436

unRAID=Yes SNAP=No  3463  /dev/sda  scsi-SATA_WDC_WD15EADS-00_WD-WCAVY0965613

unRAID=Yes SNAP=No  4195  /dev/sdj  scsi-SATA_WDC_WD15EARS-00_WD-WCAVY3658864

unRAID=Yes SNAP=No  3993  /dev/sdh  scsi-SATA_WDC_WD15EARS-00_WD-WCAYY0115615

unRAID=Yes SNAP=No  3542  /dev/sdb  scsi-SATA_WDC_WD20EARS-00_WD-WCAVY5771699

unRAID=Yes SNAP=No  3692  /dev/sdd  scsi-SATA_WDC_WD20EARS-00_WD-WCAZA0211921

unRAID=Yes SNAP=No  3617  /dev/sdc  scsi-SATA_WDC_WD20EARS-00_WD-WMAZA1287165

unRAID=Yes SNAP=No  3767  /dev/sde  scsi-SATA_WDC_WD20EARX-00_WD-WCAZA7438649

unRAID=No  SNAP=No  3845  /dev/sdf  usb-SanDisk_U3_Cruzer_Micro_0000060410037537-0:0

 

It's all looking successful so far - the drive is now assigned to SNAP but.....can't see it on the network. After some scratching of head and reading further I thought maybe I have to manually get SNAP to mount the drive so I ran the following command...

 

root@Server:~# /boot/config/snap/snap.sh -m ZAPPITI

/dev/disk/by-id/scsi-SATA_INTEL_SSDSA2CT0CVPR122604U3040AGN-part1

driver: scsi

Using: mount  -o noatime,nodiratime -t reiserfs /dev/disk/by-id/scsi-SATA_INTEL_SSDSA2CT0CVPR122604U3040AGN-part1 /mnt/disk/ZAPPITI

 

This looked to be successful to me but......still not seeing any additional disks appear on the network.

 

 

....I must still be missing something.....what's gone wrong?  ???

Link to comment

Groan......never mind, after rebooting the UnRAID server I can now see the zappiti share.

 

This stuff is TOUGH for us linux newbies!!

 

I feel your pain :)

 

You were pretty close.  snap.sh -m  will mount the drive.  Then follow it up with snap.sh -s  to create the share.  Or, rebooting will do it.  Good job.

 

Link to comment

Firstly I'll confess to not reading the whole thread word for word.. :-[

 

I'll list the commands i've done:

 

snap.sh -a 010101012 MyShare

snap.sh -m MyShare

snap.sh -s MyShare

 

Nothing appears in my folder list on my Win7 PC.

 

However, if I restart samba via unmenu everything works. Its this normal or should the script reload the samba config?

Link to comment

Well I am successfully able to snap my 80GB test drive, but cannot mount. My listDevInfo is as follows..

 

unRAID=Yes SNAP=No  3670  /dev/sdc  ata-WDC_WD10EARS-00Y5B1_WD-WCAV5S442512

unRAID=Yes SNAP=No  3612  /dev/sdb  ata-WDC_WD20EARS-00J99B0_WD-WCAWZ1025799

unRAID=No  SNAP=Yes 3548  /dev/sda  ata-WDC_WD800BD-22MRA1_WD-WMAM9CAY2782

unRAID=Yes SNAP=No  3670  /dev/sdc  scsi-SATA_WDC_WD10EARS-00_WD-WCAV5S442512

unRAID=Yes SNAP=No  3612  /dev/sdb  scsi-SATA_WDC_WD20EARS-00_WD-WCAWZ1025799

unRAID=No  SNAP=Yes 3548  /dev/sda  scsi-SATA_WDC_WD800BD-22M_WD-WMAM9CAY2782

unRAID=No  SNAP=No  3730  /dev/sdd  usb-Sony_Storage_Media_9B2001105030015705-0:

 

Device by ID output

 

 

ata-WDC_WD10EARS-00Y5B1_WD-WCAV5S442512@

ata-WDC_WD10EARS-00Y5B1_WD-WCAV5S442512-part1@

ata-WDC_WD20EARS-00J99B0_WD-WCAWZ1025799@

ata-WDC_WD20EARS-00J99B0_WD-WCAWZ1025799-part1@

ata-WDC_WD800BD-22MRA1_WD-WMAM9CAY2782@

ata-WDC_WD800BD-22MRA1_WD-WMAM9CAY2782-part1@

scsi-SATA_WDC_WD10EARS-00_WD-WCAV5S442512@

scsi-SATA_WDC_WD10EARS-00_WD-WCAV5S442512-part1@

scsi-SATA_WDC_WD20EARS-00_WD-WCAWZ1025799@

scsi-SATA_WDC_WD20EARS-00_WD-WCAWZ1025799-part1@

scsi-SATA_WDC_WD800BD-22M_WD-WMAM9CAY2782@

scsi-SATA_WDC_WD800BD-22M_WD-WMAM9CAY2782-part1@

usb-Sony_Storage_Media_9B2001105030015705-0:0@

 

Now when I try to mount it. I get ,....

 

root@SamTower:/boot/config/snap# snap.sh -m temp

./snap.sh: line 863: [: /mnt/disk/temp: binary operator expected

basename: missing operand

Try `basename --help' for more information.

Partition doesn't exist, cannot be mounted.

 

If I try the same with device ID I get

 

root@SamTower:/boot/config/snap# snap.sh -m WD-WMAM9CAY2782

File system is unknown, cannot be mounted for device: /dev/disk/by-id/scsi-SATA_WDC_WD800BD-22M_WD-WMAM9CAY2782-part1

 

Kindly Assist.

 

Regards

Sammy

 

 

 

 

 

 

Link to comment

How do you remove entries from snap.list. I goes 3 entries addes coz of SNAP not snapping the drive, the 3rd one snapped the drive, but now it does not understand what share to create after mounting ...

 

 

root@SamTower:/boot/config/snap# cat snap.list

 

22MRA1=temp

WMAM9CAY2782=temp

WD-WMAM9CAY2782=temp

 

 

The third entry is all that should be there. I need to remove the first two.

 

 

Link to comment

Ok finally I got it working. This is pretty tough for total no Linux guy like me. Though the instructions are good but it seems to take few liberties which only a Linux Savy guy can understand.

 

After hours of head scratching with the procedure, I can say in a nut shell the problem starts or arises if you preclear the disk and then try to do the SNAP stuff. The instructions on the first page do say that you need to have a partition and a filestem for this to work, but it misses the instructions as to how you have to go about it after a preclear is done.

 

As your arrey is running you do not see the drive under the devices and so creating a file system and formatting it becomes a bit unclear.

 

If you can check in my previous post, I managed to SNAP in the drive, but while mounting I had the error, "Partition doesn't exist, cannot be mounted."

 

I tried running ...

 

unraid_partition_disk.sh  -p /dev/xxx

reiserfsck /dev/xxx

 

via the script that Joe shared hoping to be able to create a partition table, but it didnt work (the script isnt for this I guess)

 

The way to solution came from GBH2's post number 88. .Thanks GBH2 for bringing this up else I might have not figured it out.

GBH2 statement .....

 

Must Format and Mount - can be done through unMENU - Disk Management

Scroll down to disk and select "Format to reiserfs"

then select mount as Read only / Writable

 

Which I did, and I was abler to mount the drive (though with hiccups discussed below). It still didnt show up in explorer as I had to share the drive in windows network as well, which needs to be done via another command that again is missing in the instruction on the first page.

 

snap.sh -s

 

I still had few hiccups, like when I tried to mount the drive with my share name "temp" it refused (even after formatting). This might be because when I ran the command "snap.sh -a serial number  share name" to SNAP in my drive I was only successfull on the third try as I was not getting the correct Device ID for my WD. Though successful; what it did I presume was to add 3 entries in the snap.list file as explained in my previous post.

So though SNAPPING worked with my share name "temp". Mounting and sharing gave errors. I had to mount using the device ID.

snap.sh -s temp command with my share drive name; temp gave me error," No such device exists: 22MRA1-part1" Note 22MRA1 is the first entry in the snap.list file. I again had to use the device ID. So snap.sh -s WD-WMAM9CAY2782 worked and I finally was able to open the share drive via explorer.  :)

 

Point to note is that you can also Mount and Share the drive via Unmenu under Disk Management.

 

Hope this would be of some help to someone ..

 

Regards

Sammy

 

 

Link to comment

Ok Update, it seems like mounting and sharing via Unmenu doesnt work, or atleast isnt working for me. It has to be done via telbet/putty with the commands ..

 

-m [serialnumber or sharename] (mount drive)

-M [serialnumber or sharename] (unmount drive)

-s [serialnumber or sharename]  (share drive)

-S [serialnumber or sharename]  (unshare drive)

 

However the creation of the partition table and filesystem has to be done via Unmenu, if a precleared drive is been used for the first time with SNAP.

Link to comment

I tried running ...

 

unraid_partition_disk.sh  -p /dev/xxx

reiserfsck /dev/xxx

 

via the script that Joe shared hoping to be able to create a partition table, but it didnt work (the script isnt for this I guess)

You were close... reiserfsck checks the file system, mkreiserfs creates one.

 

 

unraid_partition_disk.sh  -p /dev/xxx

mkreiserfs  /dev/xxx1

 

Note that you create the file system on the first partition on the disk, therefore, it is /dev/sdX1.  (you need the trailing "1" on the device name when you create the file-system on the partition.)

 

Then, you can mount /dev/sdX1 on your mount-point.

Link to comment

ohh ..okie .. cool  :)..,. Lot of Learning in here .... gald to be a part of Unraid Family ..... Off to Upgrade to 5 and then to Plus. :D

 

Joe any reason why, mounting and sharing via Unmenu does not work, while it does via command window. It would be pretty easy (if I may put it that way) if this can be done via Unmenu. Though it does say that mounting and sharing has been done/completed. Its doesnt work. Explorer does not open the share .....

Link to comment

ohh ..okie .. cool  :)..,. Lot of Learning in here .... gald to be a part of Unraid Family ..... Off to Upgrade to 5 and then to Plus. :D

 

Joe any reason why, mounting and sharing via Unmenu does not work, while it does via command window. It would be pretty easy (if I may put it that way) if this can be done via Unmenu. Though it does say that mounting and sharing has been done/completed. Its doesnt work. Explorer does not open the share .....

no idea.  What version of unMENU are you using?  There was a bug in an older one where it would not share.  Have you checked for updates lately?
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.