August 9, 201015 yr One thing I'm not sure of is when I install my stick it shows in \\tower\redstick but there is no beeps and when I check the hotPlugAfterShareEvent.log its blank. So I'm not sure if the beep feature isnt' working or if the code is getting stuck and its not performing past the the mount. I typed beep in console and it didn't complain so I'm guessing that is not an issue. Beats me what I did. I just kept tinkering with it and tinkering with it and it seems to at least work. Ah I think looking through the logs it wasn't unable to create the /mnt/usr/Backup/redstick directory for some odd reason. I created it on my own and it went. Now I'll try and tinker and see what I can mess up on my own. Thanks for an awesome script.
August 9, 201015 yr Author Beats me what I did. I just kept tinkering with it and tinkering with it and it seems to at least work. Ah I think looking through the logs it wasn't unable to create the /mnt/usr/Backup/redstick directory for some odd reason. I created it on my own and it went. Ok, you said /mnt/usr/Backup/redstick but I said /mnt/user/Backup/Lexar. I have an unRAID share /mnt/user/Backup. You probably didn't have that. If you actually created and are using /mnt/usr/Backup/redstick then you are saving to the unRAID flash drive.
August 9, 201015 yr Dang it, no I meant "user". Joe L caught me on a mistype like that earlier on something else. I had it right, but explaining myself I didnt type it correctly. I did try to mount a blackberry and a samsung phone last night with no results, but one the blackberry has enable usb connection on by default and my samsung running android you enable usb after you plug it in and it prompts you. I havent given up, but it was late last night when I decided to give it a rest. I was able to add both to the snap.list, but they didnt seem to automount when replugged in. Ill follow up later. At least the usb works and I have a clue to what im supposed to do.
August 9, 201015 yr Struggling with the device setup with SNAP. I'm not sure what is happening. Let's do some troubleshooting. Rename your snap.list to save it. Now type these in the reverse order. Does either of them have the same problem? If so, delete the snap.list and do just one at a time. Also, what does Snap.Log have in in? /boot/config/snap# ./snap.sh -a WCASJ0338244 DriveBay2 /boot/config/snap# ./snap.sh -a JK1171YAG7UTSS DeviceBay1 First...removed snap.list, and log so everything is clean. root@MyUnRaid:/boot/config/snap# ./snap.sh -a WCASJ0338244 DriveBay2 root@MyUnRaid:/boot/config/snap# ./snap.sh -listDeviceConfigurationInfo unRAID=No SNAP=No 3815 /dev/sdf /dev/disk/by-id/ata-Hitachi_HDS722020ALA330_JK1171YAG7UTSS unRAID=Yes SNAP=No 3607 /dev/sdc /dev/disk/by-id/ata-SAMSUNG_HD103UJ_S13PJ1DQ402223 unRAID=Yes SNAP=No 3665 /dev/sdd /dev/disk/by-id/ata-SAMSUNG_HD103UJ_S13PJ1DQ402224 unRAID=No SNAP=No 3847 /dev/sdg /dev/disk/by-id/ata-WDC_WD10EACS-00ZJB0_WD-WCASJ0338244 unRAID=No SNAP=No 3466 /dev/sda /dev/disk/by-id/ata-WDC_WD10EAVS-00D7B0_WD-WCAU41934321 unRAID=No SNAP=No 3732 /dev/sde /dev/disk/by-id/ata-WDC_WD2500JB-00GVA0_WD-WCAL73606663 unRAID=No SNAP=No 3815 /dev/sdf /dev/disk/by-id/scsi-SATA_Hitachi_HDS7220_JK1171YAG7UTSS unRAID=Yes SNAP=No 3607 /dev/sdc /dev/disk/by-id/scsi-SATA_SAMSUNG_HD103UJS13PJ1DQ402223 unRAID=Yes SNAP=No 3665 /dev/sdd /dev/disk/by-id/scsi-SATA_SAMSUNG_HD103UJS13PJ1DQ402224 unRAID=No SNAP=No 3847 /dev/sdg /dev/disk/by-id/scsi-SATA_WDC_WD10EACS-00_WD-WCASJ0338244 unRAID=No SNAP=No 3466 /dev/sda /dev/disk/by-id/scsi-SATA_WDC_WD10EAVS-00_WD-WCAU41934321 unRAID=No SNAP=No 3732 /dev/sde /dev/disk/by-id/scsi-SATA_WDC_WD2500JB-00_WD-WCAL73606663 unRAID=No SNAP=No 3551 /dev/sdb /dev/disk/by-id/usb-Generic-_SD_MMC_20090815198100000-0:0 root@MyUnRaid:/boot/config/snap# more snap.list WCASJ0338244=DriveBay2 So it isn't showing up. Then I add the other drive, and that does show up. root@MyUnRaid:/boot/config/snap# ./snap.sh -a JK1171YAG7UTSS DeviceBay1 root@MyUnRaid:/boot/config/snap# ./snap.sh -listDeviceConfigurationInfo unRAID=No SNAP=Yes 3815 /dev/sdf /dev/disk/by-id/ata-Hitachi_HDS722020ALA330_JK1171YAG7UTSS unRAID=Yes SNAP=No 3607 /dev/sdc /dev/disk/by-id/ata-SAMSUNG_HD103UJ_S13PJ1DQ402223 unRAID=Yes SNAP=No 3665 /dev/sdd /dev/disk/by-id/ata-SAMSUNG_HD103UJ_S13PJ1DQ402224 unRAID=No SNAP=No 3847 /dev/sdg /dev/disk/by-id/ata-WDC_WD10EACS-00ZJB0_WD-WCASJ0338244 unRAID=No SNAP=No 3466 /dev/sda /dev/disk/by-id/ata-WDC_WD10EAVS-00D7B0_WD-WCAU41934321 unRAID=No SNAP=No 3732 /dev/sde /dev/disk/by-id/ata-WDC_WD2500JB-00GVA0_WD-WCAL73606663 unRAID=No SNAP=Yes 3815 /dev/sdf /dev/disk/by-id/scsi-SATA_Hitachi_HDS7220_JK1171YAG7UTSS unRAID=Yes SNAP=No 3607 /dev/sdc /dev/disk/by-id/scsi-SATA_SAMSUNG_HD103UJS13PJ1DQ402223 unRAID=Yes SNAP=No 3665 /dev/sdd /dev/disk/by-id/scsi-SATA_SAMSUNG_HD103UJS13PJ1DQ402224 unRAID=No SNAP=No 3847 /dev/sdg /dev/disk/by-id/scsi-SATA_WDC_WD10EACS-00_WD-WCASJ0338244 unRAID=No SNAP=No 3466 /dev/sda /dev/disk/by-id/scsi-SATA_WDC_WD10EAVS-00_WD-WCAU41934321 unRAID=No SNAP=No 3732 /dev/sde /dev/disk/by-id/scsi-SATA_WDC_WD2500JB-00_WD-WCAL73606663 unRAID=No SNAP=No 3551 /dev/sdb /dev/disk/by-id/usb-Generic-_SD_MMC_20090815198100000-0:0 root@MyUnRaid:/boot/config/snap# more snap.list WCASJ0338244=DriveBay2 JK1171YAG7UTSS=DeviceBay1 snap.log.txt
August 9, 201015 yr Author Struggling with the device setup with SNAP. unRAID=No SNAP=Yes 3815 /dev/sdf /dev/disk/by-id/ata-Hitachi_HDS722020ALA330_JK1171YAG7UTSS unRAID=Yes SNAP=No 3607 /dev/sdc /dev/disk/by-id/ata-SAMSUNG_HD103UJ_S13PJ1DQ402223 unRAID=Yes SNAP=No 3665 /dev/sdd /dev/disk/by-id/ata-SAMSUNG_HD103UJ_S13PJ1DQ402224 unRAID=No SNAP=No 3847 /dev/sdg /dev/disk/by-id/ata-WDC_WD10EACS-00ZJB0_WD-WCASJ0338244 unRAID=No SNAP=No 3466 /dev/sda /dev/disk/by-id/ata-WDC_WD10EAVS-00D7B0_WD-WCAU41934321 unRAID=No SNAP=No 3732 /dev/sde /dev/disk/by-id/ata-WDC_WD2500JB-00GVA0_WD-WCAL73606663 unRAID=No SNAP=Yes 3815 /dev/sdf /dev/disk/by-id/scsi-SATA_Hitachi_HDS7220_JK1171YAG7UTSS unRAID=Yes SNAP=No 3607 /dev/sdc /dev/disk/by-id/scsi-SATA_SAMSUNG_HD103UJS13PJ1DQ402223 unRAID=Yes SNAP=No 3665 /dev/sdd /dev/disk/by-id/scsi-SATA_SAMSUNG_HD103UJS13PJ1DQ402224 unRAID=No SNAP=No 3847 /dev/sdg /dev/disk/by-id/scsi-SATA_WDC_WD10EACS-00_WD-WCASJ0338244 unRAID=No SNAP=No 3466 /dev/sda /dev/disk/by-id/scsi-SATA_WDC_WD10EAVS-00_WD-WCAU41934321 unRAID=No SNAP=No 3732 /dev/sde /dev/disk/by-id/scsi-SATA_WDC_WD2500JB-00_WD-WCAL73606663 unRAID=No SNAP=No 3551 /dev/sdb /dev/disk/by-id/usb-Generic-_SD_MMC_20090815198100000-0:0 I know what the problem is. It's the "_" versus the "-" in the device name. It's somewhere between a bug and a misunderstanding. unRAID=No SNAP=Yes 3815 /dev/sdf /dev/disk/by-id/ata-Hitachi_HDS722020ALA330_JK1171YAG7UTSS unRAID=No SNAP=No 3847 /dev/sdg /dev/disk/by-id/ata-WDC_WD10EACS-00ZJB0_WD-WCASJ0338244 Linux adds the "_" between device name parts. So SNAP looks for *_$serialnumber as in diskX="/dev/disk/by-id/*_$serialnumber". For our purposes the "WD-" is actually part of the serial number for western digital drives. I'll think about whether I should modify the code to work around this issue. In the meantime, use ./snap.sh -a WD-WCASJ0338244 DriveBay2
August 9, 201015 yr Perfect, it works. Thanks for the quick response. root@MyUnRaid:/boot/config/snap# ./snap.sh -listDeviceConfigurationInfo unRAID=No SNAP=Yes 3815 /dev/sdf /dev/disk/by-id/ata-Hitachi_HDS722020ALA330_JK1171YAG7UTSS unRAID=Yes SNAP=No 3607 /dev/sdc /dev/disk/by-id/ata-SAMSUNG_HD103UJ_S13PJ1DQ402223 unRAID=Yes SNAP=No 3665 /dev/sdd /dev/disk/by-id/ata-SAMSUNG_HD103UJ_S13PJ1DQ402224 unRAID=No SNAP=Yes 3847 /dev/sdg /dev/disk/by-id/ata-WDC_WD10EACS-00ZJB0_WD-WCASJ0338244 unRAID=No SNAP=No 3466 /dev/sda /dev/disk/by-id/ata-WDC_WD10EAVS-00D7B0_WD-WCAU41934321 unRAID=No SNAP=No 3732 /dev/sde /dev/disk/by-id/ata-WDC_WD2500JB-00GVA0_WD-WCAL73606663 unRAID=No SNAP=Yes 3815 /dev/sdf /dev/disk/by-id/scsi-SATA_Hitachi_HDS7220_JK1171YAG7UTSS unRAID=Yes SNAP=No 3607 /dev/sdc /dev/disk/by-id/scsi-SATA_SAMSUNG_HD103UJS13PJ1DQ402223 unRAID=Yes SNAP=No 3665 /dev/sdd /dev/disk/by-id/scsi-SATA_SAMSUNG_HD103UJS13PJ1DQ402224 unRAID=No SNAP=Yes 3847 /dev/sdg /dev/disk/by-id/scsi-SATA_WDC_WD10EACS-00_WD-WCASJ0338244 unRAID=No SNAP=No 3466 /dev/sda /dev/disk/by-id/scsi-SATA_WDC_WD10EAVS-00_WD-WCAU41934321 unRAID=No SNAP=No 3732 /dev/sde /dev/disk/by-id/scsi-SATA_WDC_WD2500JB-00_WD-WCAL73606663 unRAID=No SNAP=No 3551 /dev/sdb /dev/disk/by-id/usb-Generic-_SD_MMC_20090815198100000-0:0
August 9, 201015 yr Author I did try to mount a blackberry and a samsung phone last night with no results, but one the blackberry has enable usb connection on by default and my samsung running android you enable usb after you plug it in and it prompts you. I havent given up, but it was late last night when I decided to give it a rest. I was able to add both to the snap.list, but they didnt seem to automount when replugged in. Ill follow up later. At least the usb works and I have a clue to what im supposed to do. EDIT 8/13/2010: Solved. I discovered what is going on. I have a related posting here. I'm going to add a feature (rereading partition table) to SNAP for flash usb devices. I have a new Samsung Moment phone running Android 2.1. I'm connecting it for the first time to unRAID. After Plugging it in I see /dev/disk/by-id/usb-Android_UMS_Composite_M900152533ef-0:0 ./snap.sh -a M900152533ef-0:0 davesphone I unplug and plug back in, SNAP tries to mount and share but fails and I know that because I try to browse the share from my other machine and it's not there. So then using the telnet session I look in /mnt/disk/ and there is no entry for davesphone. So the mounting didn't work. Backtracking I use SNAP's individual commands to try to isolate where the problem is. ./snap.sh -listDeviceConfigurationInfo unRAID=No SNAP=Yes 4888686 /dev/sdh /dev/disk/by-id/usb-Android_UMS_Composite_M900152533ef-0:0 I see that SNAP is configured for the device so what is causing the problem? I'll try some of the SNAP commands. ./snap.sh -m davesphone Partition doesn't exist. Cannot be mounted. Well ok, thats some good feedback. The partition doesn't exist yet. The usb controller is visible to Linux, but the flash part isn't showing up. Hmm, Linux creates the device for the controller...SNAP mounts and shares partitions. How do I make the phones flash drive show up? I remember that the phone's Android operating system is linux. Aha, there is a way to mount the flash drive in my phone's settings. That must mean the phone is internally mounting and sharing it's flash partition so that it can be seen by external browsing (by unRAID server in this case). But after selecting mount in my phone, unRAID still says there isn't any partition for the phone device. Here is where I'm stuck. I don't know how to make the phones flash appear so unRAID can make a partition device entry. Without that, SNAP can't mount or share the partition. I've tried usb connection from phone to Win7 machine and that works. In another test I have a usb flash reader with removable flash chip. If I plug in the reader without any chip in it then unRAID creates a device for it as expected but no partition. Then I inserted the chip in the reader. Nothing. unRAID doesn't make a device entry for the partition. So, just like the phone, if the flash chip isn't available when unRAID detects the flash reader being plugged in then the partition is never recognized later when the chip is inserted. So it looks like unRAID checks for partitions when the device is detected. And the phone is made so that the flash drive is not automatically mounted when the usb cable is plugged in...you have to manually mount it. And it won't let you mount it until the usb cable is plugged in. Kind of a catch 22 situation. Until this situation is resolved you will have to either connect the phone to a Win machine which works or browse the unRAID wirelessly and I have done both of these things. In the Android market I installed "ES File Explorer". Search market for estrong. It allowed me to browse wirelessly all my home machines including my unRAID machine. You can use it to copy/paste files in both directions. Wirelessly is slower but pretty convienient.
August 10, 201015 yr Perhaps you can try this command after you plug in the phone and it shares its partition /etc/rc.d/rc.udev restart It will cause the udev process to re-scan for devices. It might just pick up the phone's partition and let you proceed.
August 10, 201015 yr Author Perhaps you can try this command after you plug in the phone and it shares its partition /etc/rc.d/rc.udev restart It will cause the udev process to re-scan for devices. It might just pick up the phone's partition and let you proceed. Thanks Joe. I tried but it didn't work for the phone or my flash reader.
August 10, 201015 yr I'm having a bit of a tough time figuring out to mount an external WD Passport drive. I think it's just that I can't find out what the proper serial number is. root@nas:/boot/config/snap# snap.sh -listDeviceConfigurationInfo unRAID=Yes SNAP=No 3443 /dev/sdc /dev/disk/by-id/ata-SAMSUNG_HD753LJ_S13UJ1MQ119474 unRAID=Yes SNAP=No 3580 /dev/sdf /dev/disk/by-id/ata-WDC_WD10EACS-00ZJB0_WD-WCASJ2051348 unRAID=Yes SNAP=No 3638 /dev/sde /dev/disk/by-id/ata-WDC_WD10EADS-00L5B1_WD-WCAU4D889836 unRAID=Yes SNAP=No 3501 /dev/sdd /dev/disk/by-id/ata-WDC_WD10EAVS-00D7B1_WD-WCAU4A145092 unRAID=Yes SNAP=No 3385 /dev/sdb /dev/disk/by-id/ata-WDC_WD15EADS-00P8B0_WD-WCAVU0220004 unRAID=Yes SNAP=No 3316 /dev/sda /dev/disk/by-id/ata-WDC_WD15EADS-00P8B0_WD-WMAVU0509700 unRAID=Yes SNAP=No 3443 /dev/sdc /dev/disk/by-id/scsi-SATA_SAMSUNG_HD753LJS13UJ1MQ119474 unRAID=Yes SNAP=No 3580 /dev/sdf /dev/disk/by-id/scsi-SATA_WDC_WD10EACS-00_WD-WCASJ2051348 unRAID=Yes SNAP=No 3638 /dev/sde /dev/disk/by-id/scsi-SATA_WDC_WD10EADS-00_WD-WCAU4D889836 unRAID=Yes SNAP=No 3501 /dev/sdd /dev/disk/by-id/scsi-SATA_WDC_WD10EAVS-00_WD-WCAU4A145092 unRAID=Yes SNAP=No 3385 /dev/sdb /dev/disk/by-id/scsi-SATA_WDC_WD15EADS-00_WD-WCAVU0220004 unRAID=Yes SNAP=No 3316 /dev/sda /dev/disk/by-id/scsi-SATA_WDC_WD15EADS-00_WD-WMAVU0509700 unRAID=No SNAP=No 3733 /dev/sdg /dev/disk/by-id/usb-Multi_Flash_Reader_058F0O1111B-0:0 unRAID=No SNAP=No 894928 /dev/sdh /dev/disk/by-id/usb-WD_My_Passport_070A_575832304143395937343134-0:0 I'm trying to mount the WD My Passport drive. I've tried every permutation of snap.sh -a WD_My_Passport_070A_575832304143395937343134-0:0 Ext1 that I can come up with but none of it seems to stick and mount the drive. I'm sure it's a syntax error but with no error message I'm not sure which bit of that drive identification to pull out. Any help would be appreciated... Thanks
August 10, 201015 yr Author I'm having a bit of a tough time figuring out to mount an external WD Passport drive. I think it's just that I can't find out what the proper serial number is. root@nas:/boot/config/snap# snap.sh -listDeviceConfigurationInfo unRAID=Yes SNAP=No 3443 /dev/sdc /dev/disk/by-id/ata-SAMSUNG_HD753LJ_S13UJ1MQ119474 unRAID=Yes SNAP=No 3580 /dev/sdf /dev/disk/by-id/ata-WDC_WD10EACS-00ZJB0_WD-WCASJ2051348 unRAID=Yes SNAP=No 3638 /dev/sde /dev/disk/by-id/ata-WDC_WD10EADS-00L5B1_WD-WCAU4D889836 unRAID=Yes SNAP=No 3501 /dev/sdd /dev/disk/by-id/ata-WDC_WD10EAVS-00D7B1_WD-WCAU4A145092 unRAID=Yes SNAP=No 3385 /dev/sdb /dev/disk/by-id/ata-WDC_WD15EADS-00P8B0_WD-WCAVU0220004 unRAID=Yes SNAP=No 3316 /dev/sda /dev/disk/by-id/ata-WDC_WD15EADS-00P8B0_WD-WMAVU0509700 unRAID=Yes SNAP=No 3443 /dev/sdc /dev/disk/by-id/scsi-SATA_SAMSUNG_HD753LJS13UJ1MQ119474 unRAID=Yes SNAP=No 3580 /dev/sdf /dev/disk/by-id/scsi-SATA_WDC_WD10EACS-00_WD-WCASJ2051348 unRAID=Yes SNAP=No 3638 /dev/sde /dev/disk/by-id/scsi-SATA_WDC_WD10EADS-00_WD-WCAU4D889836 unRAID=Yes SNAP=No 3501 /dev/sdd /dev/disk/by-id/scsi-SATA_WDC_WD10EAVS-00_WD-WCAU4A145092 unRAID=Yes SNAP=No 3385 /dev/sdb /dev/disk/by-id/scsi-SATA_WDC_WD15EADS-00_WD-WCAVU0220004 unRAID=Yes SNAP=No 3316 /dev/sda /dev/disk/by-id/scsi-SATA_WDC_WD15EADS-00_WD-WMAVU0509700 unRAID=No SNAP=No 3733 /dev/sdg /dev/disk/by-id/usb-Multi_Flash_Reader_058F0O1111B-0:0 unRAID=No SNAP=No 894928 /dev/sdh /dev/disk/by-id/usb-WD_My_Passport_070A_575832304143395937343134-0:0 I'm trying to mount the WD My Passport drive. I've tried every permutation of snap.sh -a WD_My_Passport_070A_575832304143395937343134-0:0 Ext1 that I can come up with but none of it seems to stick and mount the drive. I'm sure it's a syntax error but with no error message I'm not sure which bit of that drive identification to pull out. Any help would be appreciated... Thanks Try snap.sh -a 575832304143395937343134-0:0 Ext1 Linux adds the "_" between device name parts. So SNAP looks for *_$serialnumber as in diskX="/dev/disk/by-id/*_$serialnumber". I wanted to make certain that whatever was used for the serial number could never accidently appear anyplace else in the device name, making sure it was unique to a single device. Given the following device name: /dev/disk/by-id/usb-WD_My_Passport_070A_575832304143395937343134-0:0 These parts of the device name are preceded by an "_" character. The best selection would be: 575832304143395937343134-0:0 This might work: 070A_575832304143395937343134-0:0 This might work: Passport_070A_575832304143395937343134-0:0 This might work: My_Passport_070A_575832304143395937343134-0:0
August 10, 201015 yr Thank you, one of those commands seems to have worked but I still can't find the drive in Windows Explorer. It looks like it's been shared out but I can't find it: root@nas:/boot/config/snap# snap.sh -listDeviceConfigurationInfo unRAID=Yes SNAP=No 3443 /dev/sdc /dev/disk/by-id/ata-SAMSUNG_HD753LJ_S13UJ1MQ119474 unRAID=Yes SNAP=No 3580 /dev/sdf /dev/disk/by-id/ata-WDC_WD10EACS-00ZJB0_WD-WCASJ2051348 unRAID=Yes SNAP=No 3638 /dev/sde /dev/disk/by-id/ata-WDC_WD10EADS-00L5B1_WD-WCAU4D889836 unRAID=Yes SNAP=No 3501 /dev/sdd /dev/disk/by-id/ata-WDC_WD10EAVS-00D7B1_WD-WCAU4A145092 unRAID=Yes SNAP=No 3385 /dev/sdb /dev/disk/by-id/ata-WDC_WD15EADS-00P8B0_WD-WCAVU0220004 unRAID=Yes SNAP=No 3316 /dev/sda /dev/disk/by-id/ata-WDC_WD15EADS-00P8B0_WD-WMAVU0509700 unRAID=Yes SNAP=No 3443 /dev/sdc /dev/disk/by-id/scsi-SATA_SAMSUNG_HD753LJS13UJ1MQ119474 unRAID=Yes SNAP=No 3580 /dev/sdf /dev/disk/by-id/scsi-SATA_WDC_WD10EACS-00_WD-WCASJ2051348 unRAID=Yes SNAP=No 3638 /dev/sde /dev/disk/by-id/scsi-SATA_WDC_WD10EADS-00_WD-WCAU4D889836 unRAID=Yes SNAP=No 3501 /dev/sdd /dev/disk/by-id/scsi-SATA_WDC_WD10EAVS-00_WD-WCAU4A145092 unRAID=Yes SNAP=No 3385 /dev/sdb /dev/disk/by-id/scsi-SATA_WDC_WD15EADS-00_WD-WCAVU0220004 unRAID=Yes SNAP=No 3316 /dev/sda /dev/disk/by-id/scsi-SATA_WDC_WD15EADS-00_WD-WMAVU0509700 unRAID=No SNAP=No 3733 /dev/sdg /dev/disk/by-id/usb-Multi_Flash_Reader_058F0O1111B-0:0 unRAID=No SNAP=Yes 894928 /dev/sdh /dev/disk/by-id/usb-WD_My_Passport_070A_575832304143395937343134-0:0 Any idea?
August 10, 201015 yr Author Thank you, one of those commands seems to have worked but I still can't find the drive in Windows Explorer. It looks like it's been shared out but I can't find it: root@nas:/boot/config/snap# snap.sh -listDeviceConfigurationInfo unRAID=Yes SNAP=No 3443 /dev/sdc /dev/disk/by-id/ata-SAMSUNG_HD753LJ_S13UJ1MQ119474 unRAID=Yes SNAP=No 3580 /dev/sdf /dev/disk/by-id/ata-WDC_WD10EACS-00ZJB0_WD-WCASJ2051348 unRAID=Yes SNAP=No 3638 /dev/sde /dev/disk/by-id/ata-WDC_WD10EADS-00L5B1_WD-WCAU4D889836 unRAID=Yes SNAP=No 3501 /dev/sdd /dev/disk/by-id/ata-WDC_WD10EAVS-00D7B1_WD-WCAU4A145092 unRAID=Yes SNAP=No 3385 /dev/sdb /dev/disk/by-id/ata-WDC_WD15EADS-00P8B0_WD-WCAVU0220004 unRAID=Yes SNAP=No 3316 /dev/sda /dev/disk/by-id/ata-WDC_WD15EADS-00P8B0_WD-WMAVU0509700 unRAID=Yes SNAP=No 3443 /dev/sdc /dev/disk/by-id/scsi-SATA_SAMSUNG_HD753LJS13UJ1MQ119474 unRAID=Yes SNAP=No 3580 /dev/sdf /dev/disk/by-id/scsi-SATA_WDC_WD10EACS-00_WD-WCASJ2051348 unRAID=Yes SNAP=No 3638 /dev/sde /dev/disk/by-id/scsi-SATA_WDC_WD10EADS-00_WD-WCAU4D889836 unRAID=Yes SNAP=No 3501 /dev/sdd /dev/disk/by-id/scsi-SATA_WDC_WD10EAVS-00_WD-WCAU4A145092 unRAID=Yes SNAP=No 3385 /dev/sdb /dev/disk/by-id/scsi-SATA_WDC_WD15EADS-00_WD-WCAVU0220004 unRAID=Yes SNAP=No 3316 /dev/sda /dev/disk/by-id/scsi-SATA_WDC_WD15EADS-00_WD-WMAVU0509700 unRAID=No SNAP=No 3733 /dev/sdg /dev/disk/by-id/usb-Multi_Flash_Reader_058F0O1111B-0:0 unRAID=No SNAP=Yes 894928 /dev/sdh /dev/disk/by-id/usb-WD_My_Passport_070A_575832304143395937343134-0:0 Any idea? The way SNAP works with hard drives versus usb devices can seem different. It's just that hard drives are more likely to have multiple partitions and SNAP will attempt to mount/share each of the partitions. Only partitions with filesystems on them can be shared. SNAP appends "-part#" to the sharename for each of the partitions (except the first which defaults to not having the extention). In unRAID type ls /dev/disk/by-id There should be lines like usb-WD_My_Passport_070A_575832304143395937343134-0:0 usb-WD_My_Passport_070A_575832304143395937343134-0:0-part1 SNAP mounts and shares partitions. If the drive has never been partitioned then SNAP will know about the device but won't be able to do anything with it. If you have a brand new drive it may have no partitions on it yet. Also, it's possible for the drive to have multiple partitions on it. Each one will have a line with it's own partition number in /dev/disk/by-id. If there are multiple partitions then SNAP will try to mount and share out each one. The first one will be shared as \\tower\Ext1. The next one will be shared as \\tower\Ext1-part2 and so on. Example: So lets say for example the hard drive has two partitions and that part1 doesn't have an filesystem on it, and that part2 does. In this case SNAP will not share the first partition so \\tower\Ext1 would not be created. But because the second partition has an filesystem on it that one would get shared and it would be shared as \\tower\Ext1-part2. I hope this helps. If your hard drive doesn't have any partitions you will have to partition it and put a filesystem on it before SNAP can do anything with it.
August 10, 201015 yr Author Perhaps you can try this command after you plug in the phone and it shares its partition /etc/rc.d/rc.udev restart It will cause the udev process to re-scan for devices. It might just pick up the phone's partition and let you proceed. Joe, can you help troubleshoot this linux/unRAID issue? I expect you are busy with the unRAID beta so I understand if you don't have time now. I can mail you a flash drive that can be used for testing.
August 11, 201015 yr Hey guys, what is the maximum speed you all get when copying from a SNAP mounted USB drive to the array? With the cache drive in use, I get a maximum of about 14MB/sec. The cache drive is a 7200RPM drive so I thought it would be faster than that. I am using MC to copy the files. When copying to the USB drive on another computer I get about 25MB/sec so I thought it would at least be as close when copying from. What do you guys get?
August 11, 201015 yr What speed USB port did you plug the drive into? Its plugged into a USB 2.0 port. The external HD is a WD Scorpio 500GB.
August 11, 201015 yr Author I can't help, my flash devices are using usb but I'm using eSata for hard drive connections.
August 11, 201015 yr Thanks queeg. I guess I'll have to stick with USB because I'll need to buy a PCIe card for an extra SATA port. I was using MC to do the copying from a remote Ubuntu machine. Think that could be the source of the slowdown?
August 11, 201015 yr Author Hey guys, what is the maximum speed you all get when copying from a SNAP mounted USB drive to the array? With the cache drive in use, I get a maximum of about 14MB/sec. The cache drive is a 7200RPM drive so I thought it would be faster than that. I am using MC to copy the files. When copying to the USB drive on another computer I get about 25MB/sec so I thought it would at least be as close when copying from. What do you guys get? SNAP doesn't really enter into the speed issue. SNAP uses the same mount/share commands that you would use manually. Any speed issue has got to be hardware related. Are you plugging into one of the ports on the motherboard backplane or on the front of the case? I've seen issues with the ones on the case being flakey.
August 12, 201015 yr Hey guys, what is the maximum speed you all get when copying from a SNAP mounted USB drive to the array? With the cache drive in use, I get a maximum of about 14MB/sec. The cache drive is a 7200RPM drive so I thought it would be faster than that. I am using MC to copy the files. When copying to the USB drive on another computer I get about 25MB/sec so I thought it would at least be as close when copying from. What do you guys get? SNAP doesn't really enter into the speed issue. SNAP uses the same mount/share commands that you would use manually. Any speed issue has got to be hardware related. Are you plugging into one of the ports on the motherboard backplane or on the front of the case? I've seen issues with the ones on the case being flakey. Sadly, its one on the motherboard backplane. I'll try telneting into the box and doing a basic command line copy to see if using MC has any effect.
August 19, 201015 yr Everything seems to be working great now. queeg, have you considered creating a front-end that will work maybe with unMENU? This would make adding drives to the SNAP config so much easier than having to manually edit or run commands (not that I am complaining but for the less command savy persons) ?
August 20, 201015 yr Author Everything seems to be working great now. queeg, have you considered creating a front-end that will work maybe with unMENU? This would make adding drives to the SNAP config so much easier than having to manually edit or run commands (not that I am complaining but for the less command savy persons) ? I'm going to wait until unRAID 5.0 is out to see what that has to offer. I don't expect it to change the existing code but there might be easier support for web interfaces. I'm also attempting to hack a Win7 gadget network monitor that only does pings into running shell scripts across telnet for reporting various unRAID status. If that works then maybe it could morph into a configuration tool somehow. Currently I'm fiddling around trying to get card readers working because Android phones behave like card readers when they are connected and I want to be able to connect mine.
August 20, 201015 yr I'm also attempting to hack a Win7 gadget network monitor that only does pings into running shell scripts across telnet for reporting various unRAID status. Look at how netcat or socart (or similiar tool) can be used to connect to a program run from inetd Using telnet to run a remote command like that is going to be tedious. In comparison, a remote agent designed to run from inetd or ssh might be easier and it simplifies how the client/server work together. When it comes down to it, unRAID 5.x will be more suitable as you can write a webgui plugin that accepts input from a remote socket. You can pretty much do wget's of remote pages and parse the output.
August 20, 201015 yr Author I'm also attempting to hack a Win7 gadget network monitor that only does pings into running shell scripts across telnet for reporting various unRAID status. Look at how netcat or socart (or similiar tool) can be used to connect to a program run from inetd Using telnet to run a remote command like that is going to be tedious. In comparison, a remote agent designed to run from inetd or ssh might be easier and it simplifies how the client/server work together. When it comes down to it, unRAID 5.x will be more suitable as you can write a webgui plugin that accepts input from a remote socket. You can pretty much do wget's of remote pages and parse the output. Wget can help with reporting status. But in order to have a web configuration tool for SNAP I'm not sure of what different options might be available. How is the unRAID 5.x plugin going to work? What languages or script can the pages be written in? I've installed and modified php pages but really not ever started them from scratch. Where do the files get placed within unRAID?
Archived
This topic is now archived and is closed to further replies.