I grabbed both files and copied the button files over to unMenu folder.

I also put build25 into /tmp/snap/ and then uncompressed the contents into that folder.

Running command line './snap-install.sh -i' or using unMenu CHECK and UPDATE both gave the same error:

 

Running /tmp/snap/snap-install.sh -i

New version of SNAP: whereThisScriptIs is /tmp/snap

0.47

SNAP version 0.46 is currently installed.

NewVersion-PriorVersion-REINSTALL is whereThisScriptIs is /tmp/snap 0.47-0.46-no

No update required.

Mon Jan 31 00:19:20 MST 2011

No update required.

Installation was not run, all files are current.: Mon Jan 31 00:19:21 MST 2011

 

Is there something I need to reset in the /boot/config/snap/ 4.6 version to allow upgrade to 4.7?

 

I grabbed both files and copied the button files over to unMenu folder.

I also put build25 into /tmp/snap/ and then uncompressed the contents into that folder.

Running command line './snap-install.sh -i' or using unMenu CHECK and UPDATE both gave the same error:

 

Running /tmp/snap/snap-install.sh -i

New version of SNAP: whereThisScriptIs is /tmp/snap

0.47

SNAP version 0.46 is currently installed.

NewVersion-PriorVersion-REINSTALL is whereThisScriptIs is /tmp/snap 0.47-0.46-no

No update required.

Mon Jan 31 00:19:20 MST 2011

No update required.

Installation was not run, all files are current.: Mon Jan 31 00:19:21 MST 2011

 

Is there something I need to reset in the /boot/config/snap/ 4.6 version to allow upgrade to 4.7?

 

 

Fixed in version 0.47 build 26.  I left in a debug line and it interferred with the install. 

snap_user_script_buttons_01302011.zip

snap-0.47-build26.tgz.zip

Got your PM too late to reply.

 

This time I only updated the unMenu buttons and also made sure to restart unMenu just in case.

Ran UPDATE and the results are good.

 

Running /tmp/snap/snap-install.sh -i

New version of SNAP: 0.47

SNAP version 0.46 is currently installed.

NewVersion-PriorVersion-REINSTALL is 0.47-0.46-no

Stopping snapNotify.sh...

Stopping snapSambaNotify.sh...

Now starting SNAP...

Sharing m1980...

/boot/config/snap/snap.sh: All shares mounted.

 

Installation successful

Mon Jan 31 02:34:07 MST 2011

0.47-0.46-no

Installation successful: Mon Jan 31 02:34:11 MST 2011

 

and also checked installed version

 

root@Tower:/boot/config/snap# ./snap.sh -v

0.47

 

Clicking unMenu button for CHECK Snap Updates gives me a new button

Reinstall SNAP Updates version 0.47

Got your PM too late to reply.

 

This time I only updated the unMenu buttons and also made sure to restart unMenu just in case.

Ran UPDATE and the results are good.

 

Running /tmp/snap/snap-install.sh -i

New version of SNAP: 0.47

SNAP version 0.46 is currently installed.

NewVersion-PriorVersion-REINSTALL is 0.47-0.46-no

Stopping snapNotify.sh...

Stopping snapSambaNotify.sh...

Now starting SNAP...

Sharing m1980...

/boot/config/snap/snap.sh: All shares mounted.

 

Installation successful

Mon Jan 31 02:34:07 MST 2011

0.47-0.46-no

Installation successful: Mon Jan 31 02:34:11 MST 2011

 

and also checked installed version

 

root@Tower:/boot/config/snap# ./snap.sh -v

0.47

 

 

Yep, You got the changes.  The debug line that got left in returned some extra debug text with the version and that caused a mismatch.

And yes, getting the REINSTALL button after having doing the install is correct.  When the new version is same as installed version your only option is reinstalling.  I hope that's not confusing.

 

You can always check the top line of the first post in this thread so see if a new version is available. 

With the new version 0.47-build26 out I'm spending some time getting SNAP to support card readers. 

 

I actually got one to work after hours of repetitious tests and didn't have to do a udev restart.  With the addition of a new script file snapMonitorUsbCardReader.sh I'm able to plug in my portable card reader which linux detects and creates a device entry for.  Then at some point I insert a flash card and that gets mounted and shared by SNAP.  Then at some later time I can pull out the flash card and SNAP will unmount/unshare the device. 

Now that I got it to work I'll be testing edge cases and clean up the logging. 

 

After that I've got a portable reader that has two slots and I'll be experimenting to see if it can handle that one as well. 

You may want to Note in the first post that SNAP does not work with 5.0beta3 that was just released.  There were a lot of changes because of the update to a newer revision of Slackware and a lot of things were broken, just not SNAP.  UnMenu also has some things to fix, as do other plugins I would suspect.

You may want to Note in the first post that SNAP does not work with 5.0beta3 that was just released.  There were a lot of changes because of the update to a newer revision of Slackware and a lot of things were broken, just not SNAP.  UnMenu also has some things to fix, as do other plugins I would suspect.

 

Thanks for the heads up.

For some reason I left the inotify tarball out of 0.47-build26 which would only affect new installs, updates would have worked.

I've added it back in 0.47-build27 ( no other changes) and put it on the first post.  Due to space constraints I needed to take 0.46 off the first post.  It's been moved to the SNAP project on google.code on it's deprecated code page. 

I'm l Investigating for a way to add a drive to the server outside of the unraid server. that could be accessed from my main pc (maybe just part of it)

the drive would be used by programs like transmission or sabnzb  and  to store system files/addons/ logs etc.  to prevent the usb  from degrading.

is  S.N.A.P. good for that? or should i look for a something different?

 

thanks in advance

I'm l Investigating for a way to add a drive to the server outside of the unraid server. that could be accessed from my main pc (maybe just part of it)

the drive would be used by programs like transmission or sabnzb  and  to store system files/addons/ logs etc.  to prevent the usb  from degrading.

is  S.N.A.P. good for that? or should i look for a something different?

 

thanks in advance

 

Yes, to your question SNAP is for sharing storage devices (usb flash, hard drives,etc) in the unRAID server that will not be part of unRAID's protected array.

thanks for your reply

I will definitely look into it once i got my basic unraid fully up and running.

hi not sure if i missed this,

is it possible to add pasword protection to the share?

 

thanks in advance

hi not sure if i missed this,

is it possible to add pasword protection to the share?

 

thanks in advance

 

SNAP doesn't provide any built in for that.  I think it might be possible to add it in the snapEvents.sh script. 

thanks for your reply

 

for now I have to study some more to understand how to do that

thanks for your reply

 

for now I have to study some more to understand how to do that

 

Keep us informed of what you learn as I'm sure others will be interested and may help test or even research it with you.

I might not use snap as there is a way to mount an drive through unmenu for now. 

I was thinking maybe the share permissions could somehow be set in the smb-extra.conf file

Nice utility - I was looking for a way to share a disk through my Unraid server but not have it protected by parity as it just holds backups for the rest of my Windows clients. If the disk dies, I can just pull it our and add another.

 

Quick question, I did read on a post previous about how when I do a "-listDeviceConfigurationInfo" I see two listings for most devices. One shows up as /dev/disk/by-id/ata_driveID and a second duplicate shows up but has /dev/disk/by-id/scsi-SATA_driveID.

 

This shows for all six of my disk drives, 4 of which are on the Mobo and two on a add-on Raid controller. I would assume they will always show this way and I will not have any issues correct?

 

Cheers!

Nice utility - I was looking for a way to share a disk through my Unraid server but not have it protected by parity as it just holds backups for the rest of my Windows clients. If the disk dies, I can just pull it our and add another.

 

Quick question, I did read on a post previous about how when I do a "-listDeviceConfigurationInfo" I see two listings for most devices. One shows up as /dev/disk/by-id/ata_driveID and a second duplicate shows up but has /dev/disk/by-id/scsi-SATA_driveID.

 

This shows for all six of my disk drives, 4 of which are on the Mobo and two on a add-on Raid controller. I would assume they will always show this way and I will not have any issues correct?

 

Cheers!

 

Yes you are correct on both points.  If you use -listDevInfo you will get a list with the serial number part of the name highlighted.  That highlighted part is what SNAP uses to identify the drive.

Yes you are correct on both points.  If you use -listDevInfo you will get a list with the serial number part of the name highlighted.  That highlighted part is what SNAP uses to identify the drive.

 

Very cool! Thanks!

 

I can confirm that SNAP does not appear to work on the 5.0 betas.  In particular, 5.0b6a.

 

What's interesting is that only the mount fails.  Whatever command it runs to create the samba share still works fine, but the drive won't mount.  If I manually create mount the drive into the place where SNAP expects it to be, I can continue to work.

 

I'm using a SNAP for a fixed drive that holds applications.  Until SNAP is fixed up for the betas, does anyone know what commands it runs to create the samba shares?  I can mount my drive manually in my go script.

If you willing to be a test volunteer I'll try to make it work on the betas.  PM me and we can work on it.

SNAP now works on unRAID 5.0-beta6a.  Thanks goes to Gizmotoy for testing and helping troubleshoot the syntax of the blkid command. 

 

The easiest way to get the update is to use the Update SNAP button in unMenu User Scripts page.  If you don't already have the buttons, you can download them on the first post of this thread. 

How to install SNAP updates without unMenu.

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

 

cd /tmp

mkdir snap

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

Then extract the files from that tarball.

 

cd /tmp/snap

tar -xvf snap-0.47-build23.tgz

Test the installation before actually running it.

 

/tmp/snap/snap-install.sh -t

 

That will return a single word:  install or update or reinstall  

For install or update you will run:

/tmp/snap/snap-install.sh -i

 

For reinstall you will run:

/tmp/snap/snap-install.sh -r

 

There are not any user prompts during the installation.  And that's it.

Hi Queeg,

 

Im trying to make a quick script of the above and I have the following:

mkdir /tmp/snap
cd /tmp/snap
wget -nv ??????
tar -xvf snap-*.tgz
/tmp/snap/snap-install.sh -i

 

Is there a way to grep/awk the latest download path? This a ridiculously simple script but it would be nice to make it future proof.

 

~dpc

 

Would this allow faster transfers to unraid instead of going through my wired network?  For example I have a 60 plus gig iPhoto library file I copy over from my laptop to unraid and it takes some time to copy over.  Would this be faster?  Currently my network is 10/100 but soon to be upgraded to 1000

Would this allow faster transfers to unraid instead of going through my wired network?  For example I have a 60 plus gig iPhoto library file I copy over from my laptop to unraid and it takes some time to copy over.  Would this be faster?  Currently my network is 10/100 but soon to be upgraded to 1000

 

I'm guessing you mean copying the files from your laptop to an external drive, then connecting it into the unRAID server?  Well, 60G isn't really huge so whether it's faster or easier would include how convenient the external drive is.