September 12, 201411 yr SNAP is suppose to auto Mount and Share a disk on boot correct? For some reason my drive is only shared on boot and I have to manually mount the disk each time. Is this correct behavior?
September 12, 201411 yr Author SNAP is suppose to auto Mount and Share a disk on boot correct? For some reason my drive is only shared on boot and I have to manually mount the disk each time. Is this correct behavior? Is it a usb drive?
September 12, 201411 yr Author No, it is a sata 250GB SSD with formatted with EXT. Only USB drives are auto mounted. You can add a go file entry to mount the drive on boot up. In the go file enter: /boot/config/plugins/snap/snap.sh -ms ShareName ---> this will mount and share or /boot/config/plugins/snap/snap.sh -m ShareName ---> this will mount and not share If you are using powerdown, you can provide scripts to mount and unmount the disk on array start and stop. More information is available on this post:http://lime-technology.com/forum/index.php?topic=31735.0.
September 14, 201411 yr Author Does XFS or BRFS have a discard flag for SSD's or is it just EXT4? Only ext4.
September 14, 201411 yr Guess I will move back to my go script mounting as this does me no good. My server will not boot correctly because the swap file takes all the space instead of being created on the ssd
September 15, 201411 yr Author Guess I will move back to my go script mounting as this does me no good. My server will not boot correctly because the swap file takes all the space instead of being created on the ssd You can mount the drive in the go file using: /boot/config/plugins/snap/snap/sh -ms ShareName ---> mount and share drive or /boot/config/plugins/snap/snap.sh -m ShareName ---> mount only
September 15, 201411 yr Author What happens tho when I start and stop the array. Does it stay mounted? Yes.
September 23, 201411 yr I found three problems with a new install of SNAP I had a new 4tb WD drive that I added via SNAP as a test for the proper SNAP operation. Everything was working as expected. I then stopped the array and added that drive to the array. It was removed from the list of SNAP controlled drives and added to the SNAP list of array drives. Problem: The drive is still listed as a non-array drive in my network listing of Tower drives on all my Windows computers. So my Unraid machine has 11 drives and a list of 12 drives in Windows Explorer or File Explorer. How can I remove the Windows Explorer network listing and prevent this from occurring again ? There is a drive listed (attached Snip ) that is not a Snap controlled drive. It appears to be a "duplicate' of my Unraid flash drive as it has the flash drive serial number and states "OK to be removed " There are no controls for removal and would that then remove the Flash drive as they have the same serial number ? There is a drive listed as "not found " which was an external USB drive that was removed yet the listing is never updated.
September 23, 201411 yr Author I found three problems with a new install of SNAP I had a new 4tb WD drive that I added via SNAP as a test for the proper SNAP operation. Everything was working as expected. I then stopped the array and added that drive to the array. It was removed from the list of SNAP controlled drives and added to the SNAP list of array drives. Problem: The drive is still listed as a non-array drive in my network listing of Tower drives on all my Windows computers. So my Unraid machine has 11 drives and a list of 12 drives in Windows Explorer or File Explorer. How can I remove the Windows Explorer network listing and prevent this from occurring again ? There is a drive listed (attached Snip ) that is not a Snap controlled drive. It appears to be a "duplicate' of my Unraid flash drive as it has the flash drive serial number and states "OK to be removed " There are no controls for removal and would that then remove the Flash drive as they have the same serial number ? There is a drive listed as "not found " which was an external USB drive that was removed yet the listing is never updated. In order to remove a drive from SNAP, you must remove the share name. Right click on the drive and select "Delete Share Name". SNAP will then release the drive. Your flash is listed and is sdb. The other drive that you think is also your flash is sda and the serial number is different. 3014-0:0 vs 3014-0:1. unRAID sees two drives mounted and SNAP gets this information from unRAID. On the Seagate drive '*not found*' you need to delete the share name and SNAP will release it.
September 23, 201411 yr Hello...I have been trying to read this thread and understand SNAP more. I have unraid 6 beta 9 and the latest SNAP installed. When I installed an external HDD via USB, it picked it up no problem. From that point, I am not certain how to make it accessible to my network like my regular shares. I figured I missed a step, but am not certain. My objective to was to make it available on my network so I can map to it. Please advise. Last thing...would SNAP pick up an external HDD if connected via eSATA?
September 23, 201411 yr Author Hello...I have been trying to read this thread and understand SNAP more. I have unraid 6 beta 9 and the latest SNAP installed. When I installed an external HDD via USB, it picked it up no problem. From that point, I am not certain how to make it accessible to my network like my regular shares. I figured I missed a step, but am not certain. My objective to was to make it available on my network so I can map to it. Please advise. Double click on the share name field of the drive. Enter a share name. Don't use blanks in the name. Then right click on the drive line and click 'Mount and Share'. You should then see the share on your network. Give it a little time to show up. Last thing...would SNAP pick up an external HDD if connected via eSATA? Yes, but unRAID does not hot plug sata drives so you'll need to have it connected and powered before unRAID is booted.
September 23, 201411 yr Double click on the share name field of the drive. Enter a share name. Don't use blanks in the name. Then right click on the drive line and click 'Mount and Share'. You should then see the share on your network. Give it a little time to show up. I had done that, which led to my OP. I will have to check again tonight, but I think it did show up on the network but whenever I tried to access it, I got the "network share not accessible" type error. That's why I thought I figured I had done something wrong. I didn't know if I had to telnet into unraid and set read/write permissions to the SNAP share.
September 23, 201411 yr Author Double click on the share name field of the drive. Enter a share name. Don't use blanks in the name. Then right click on the drive line and click 'Mount and Share'. You should then see the share on your network. Give it a little time to show up. I had done that, which led to my OP. I will have to check again tonight, but I think it did show up on the network but whenever I tried to access it, I got the "network share not accessible" type error. That's why I thought I figured I had done something wrong. I didn't know if I had to telnet into unraid and set read/write permissions to the SNAP share. That should work. Are you accessing the shares with a Windows computer using SMB?
September 23, 201411 yr Double click on the share name field of the drive. Enter a share name. Don't use blanks in the name. Then right click on the drive line and click 'Mount and Share'. You should then see the share on your network. Give it a little time to show up. I had done that, which led to my OP. I will have to check again tonight, but I think it did show up on the network but whenever I tried to access it, I got the "network share not accessible" type error. That's why I thought I figured I had done something wrong. I didn't know if I had to telnet into unraid and set read/write permissions to the SNAP share. That should work. Are you accessing the shares with a Windows computer using SMB? Yes.
September 27, 201411 yr How can i automount the Snap drive? Its an internal sata mounted drive. I tried to use the GO script with this line, but it doesnt work #!/bin/bash #automount SNAP disk /boot/config/plugins/snap/snap.sh -ms disk80 # Start the Management Utility /usr/local/sbin/emhttp &
September 27, 201411 yr Author How can i automount the Snap drive? Its an internal sata mounted drive. I tried to use the GO script with this line, but it doesnt work #!/bin/bash #automount SNAP disk /boot/config/plugins/snap/snap.sh -ms disk80 # Start the Management Utility /usr/local/sbin/emhttp & Can you mount it in the SNAP webgui? The drive has to have a share name assigned. Use the following steps. - Be sure you can mount it from the SNAP webgui. Double click the drive line and assign a share name (no blanks in name), right click on the drive line and click "Mount and Share". Wait to see if SNAP shows it mounted and shared. The M and S icons will highlight. Check that you can see and access the drive from the network. - Start a telnet session and use the command '/boot/config/plugins/snap/snap.sh -ms share name' to verify it mounts and is shared. Check for any errors. The SNAP needs to be put after emhttp in your go file. There are some things that emhttp needs to do before SNAP will work.
September 27, 201411 yr IN the webgui it is working fine, but i didnt want to mount it manually each time. I just tested an extra line in the GO script and that worked: /boot/config/plugins/snap/snap.sh -enable /boot/config/plugins/snap/snap.sh -ms K438T7C2D0KR But i will place it after the emhttp lines. To see if that works too.
September 27, 201411 yr Author IN the webgui it is working fine, but i didnt want to mount it manually each time. I just tested an extra line in the GO script and that worked: /boot/config/plugins/snap/snap.sh -enable /boot/config/plugins/snap/snap.sh -ms K438T7C2D0KR But i will place it after the emhttp lines. To see if that works too. That's probably because the SNAP plugin had not completed. That's why I said put it after emhttp.
October 8, 201411 yr Hopefully not a hijack. Seemed to be the most appropriate place, being unRAID 6b10a, SNAP version 2014.09.11 (installed via web gui to add plugin, which worked well!), lsblk output is available in the attachments. After using parts of the [now DEPRECATED] How to partition, format ext4, and mount an SSD outside the array along with the unRAID 6 Beta 6: Btrfs Quick-Start Guide during the unRAID 6b6 period, and having the 'old' 250GB drive that was BTRFS had checksum issues, locking me out of the qcow2 format *.img (unexpected Checksums on access, when attempting to copy/backup the VM virtual disk after applying a few hundred Windows updates) while the Windows 7 VM would still boot fine (had been looking into running Windows Media Center with a Silicon Dust 3 tuner network device, via cable card). After updating my beta server, from 6b6 to 6b10a, I opted to give a /apps or /vms share another try using an old 2TB WD Black (3Gb/s) that I freed up in the last few months. I partitioned it as 400GB BTRFS (/dev/sdb1), 500GB XFS (/dev/sdb2), and 963GB ext4 (/dev/sdb3, being the remainder of the drive)... SNAP sees the device (drive) as BTRFS (being the format of the first partition). To me, this feels like it may be a "by design" item, rather than an oversight (or reasonable enhancement). After all, SNAP is stated for mounting/sharing DRIVES outside of the array, not partitions. Do others agree with the "by design" conclusion? If so, I'll be heading back to pursue the /boot/config/go & /boot/config/smb-extra.conf avenue.
October 8, 201411 yr Author Hopefully not a hijack. Seemed to be the most appropriate place, being unRAID 6b10a, SNAP version 2014.09.11 (installed via web gui to add plugin, which worked well!), lsblk output is available in the attachments. After using parts of the [now DEPRECATED] How to partition, format ext4, and mount an SSD outside the array along with the unRAID 6 Beta 6: Btrfs Quick-Start Guide during the unRAID 6b6 period, and having the 'old' 250GB drive that was BTRFS had checksum issues, locking me out of the qcow2 format *.img (unexpected Checksums on access, when attempting to copy/backup the VM virtual disk after applying a few hundred Windows updates) while the Windows 7 VM would still boot fine (had been looking into running Windows Media Center with a Silicon Dust 3 tuner network device, via cable card). After updating my beta server, from 6b6 to 6b10a, I opted to give a /apps or /vms share another try using an old 2TB WD Black (3Gb/s) that I freed up in the last few months. I partitioned it as 400GB BTRFS (/dev/sdb1), 500GB XFS (/dev/sdb2), and 963GB ext4 (/dev/sdb3, being the remainder of the drive)... SNAP sees the device (drive) as BTRFS (being the format of the first partition). To me, this feels like it may be a "by design" item, rather than an oversight (or reasonable enhancement). After all, SNAP is stated for mounting/sharing DRIVES outside of the array, not partitions. Do others agree with the "by design" conclusion? If so, I'll be heading back to pursue the /boot/config/go & /boot/config/smb-extra.conf avenue. SNAP only mounts the first partition it finds.
Archived
This topic is now archived and is closed to further replies.