spants

There is a setting in sabnzb - config/folders that sets the permissions for downloaded files. Set this to 666. or see my post here: http://lime-technology.com/forum/index.php?topic=12494.0 Let me know if it works for you, Tony

There was an old topic about not seeing files on shares on a mac that could be seen on a windows pc. The problem is that linux maps a linux attrib to a SYSTEM attribute on samba. My problem was that one pc could see the file (settings show hidden/system) and my htpc couldnt see the files (hide hidden/system). The fix: Create a file called smb-extra.conf in the flash/config directory containing [global] map hidden = No map system = No and all normality is restored Tony ---added an umenu script (based on the permissions script) if you would prefer.... 71-unmenu_user_script_samba_system.zip

I just use another windows machine on the same ups (dont forget the switch too!) to execute the powerdown script on the tower as I needed both machines to powerdown cleanly. Tony

Hi If I transfer a large file via a windows pc from one share to another, I will lose the network on 4.6. On 4.56 it seems ok..... This is the error msg in the log: Jan 6 18:28:31 Tower kernel: sky2 eth0: rx error, status 0xb676b676 length 0 Jan 6 18:29:48 Tower kernel: <unknown>: hw csum failure. Jan 6 18:29:48 Tower kernel: Pid: 1386, comm: nmbd Not tainted 2.6.32.9-unRAID #8 Jan 6 18:29:48 Tower kernel: Call Trace: Jan 6 18:29:48 Tower kernel: [<c122f122>] netdev_rx_csum_fault+0x29/0x30 Jan 6 18:29:48 Tower kernel: [<c122b931>] skb_copy_and_csum_datagram_iovec+0xa4/0xc4 Jan 6 18:29:48 Tower kernel: [<c125ea0a>] udp_recvmsg+0xe4/0x256 Jan 6 18:29:48 Tower kernel: [<c1225643>] sock_common_recvmsg+0x31/0x4a Jan 6 18:29:48 Tower kernel: [<c1223e90>] sock_recvmsg+0xd1/0xe9 Jan 6 18:29:48 Tower kernel: [<c103391d>] ? autoremove_wake_function+0x0/0x30 Jan 6 18:29:48 Tower kernel: [<c103391d>] ? autoremove_wake_function+0x0/0x30 Jan 6 18:29:48 Tower kernel: [<c1078427>] ? core_sys_select+0x232/0x280 Jan 6 18:29:48 Tower kernel: [<c11370cc>] ? copy_to_user+0x33/0x3c Jan 6 18:29:48 Tower kernel: [<c1224999>] sys_recvfrom+0x7b/0xba Jan 6 18:29:48 Tower kernel: [<c10950ba>] ? posix_lock_file+0xe/0x10 Jan 6 18:29:48 Tower kernel: [<c10950e3>] ? vfs_lock_file+0x27/0x2b Jan 6 18:29:48 Tower kernel: [<c1039725>] ? ktime_get_ts+0xc3/0xcd Jan 6 18:29:48 Tower kernel: [<c107753f>] ? poll_select_copy_remaining+0xb3/0xcf Jan 6 18:29:48 Tower kernel: [<c1224d51>] sys_socketcall+0xfb/0x170 Jan 6 18:29:48 Tower kernel: [<c1002935>] syscall_call+0x7/0xb Jan 6 18:29:48 Tower kernel: <unknown>: hw csum failure. Jan 6 18:29:48 Tower kernel: Pid: 1386, comm: nmbd Not tainted 2.6.32.9-unRAID #8 Jan 6 18:29:48 Tower kernel: Call Trace: Jan 6 18:29:48 Tower kernel: [<c122f122>] netdev_rx_csum_fault+0x29/0x30 Jan 6 18:29:48 Tower kernel: [<c122b931>] skb_copy_and_csum_datagram_iovec+0xa4/0xc4 Jan 6 18:29:48 Tower kernel: [<c125ea0a>] udp_recvmsg+0xe4/0x256 Jan 6 18:29:48 Tower kernel: [<c1225643>] sock_common_recvmsg+0x31/0x4a Jan 6 18:29:48 Tower kernel: [<c1223e90>] sock_recvmsg+0xd1/0xe9 Jan 6 18:29:48 Tower kernel: [<c103391d>] ? autoremove_wake_function+0x0/0x30 Jan 6 18:29:48 Tower kernel: [<c103391d>] ? autoremove_wake_function+0x0/0x30 Jan 6 18:29:48 Tower kernel: [<c1078427>] ? core_sys_select+0x232/0x280 Jan 6 18:29:48 Tower kernel: [<c11370cc>] ? copy_to_user+0x33/0x3c Jan 6 18:29:48 Tower kernel: [<c1136f51>] ? copy_from_user+0x31/0x54 Jan 6 18:29:48 Tower kernel: [<c1224999>] sys_recvfrom+0x7b/0xba Jan 6 18:29:48 Tower kernel: [<c10950ba>] ? posix_lock_file+0xe/0x10 Jan 6 18:29:48 Tower kernel: [<c10950e3>] ? vfs_lock_file+0x27/0x2b Jan 6 18:29:48 Tower kernel: [<c1039725>] ? ktime_get_ts+0xc3/0xcd Jan 6 18:29:48 Tower kernel: [<c107753f>] ? poll_select_copy_remaining+0xb3/0xcf Jan 6 18:29:48 Tower kernel: [<c1224d51>] sys_socketcall+0xfb/0x170 Jan 6 18:29:48 Tower kernel: [<c1002935>] syscall_call+0x7/0xb Jan 6 18:29:49 Tower kernel: <unknown>: hw csum failure. Jan 6 18:29:49 Tower kernel: Pid: 1386, comm: nmbd Not tainted 2.6.32.9-unRAID #8 Jan 6 18:29:49 Tower kernel: Call Trace: Jan 6 18:29:49 Tower kernel: [<c122f122>] netdev_rx_csum_fault+0x29/0x30 Jan 6 18:29:49 Tower kernel: [<c122b931>] skb_copy_and_csum_datagram_iovec+0xa4/0xc4 Jan 6 18:29:49 Tower kernel: [<c125ea0a>] udp_recvmsg+0xe4/0x256 Jan 6 18:29:49 Tower kernel: [<c1225643>] sock_common_recvmsg+0x31/0x4a Jan 6 18:29:49 Tower kernel: [<c1223e90>] sock_recvmsg+0xd1/0xe9 Jan 6 18:29:49 Tower kernel: [<c103391d>] ? autoremove_wake_function+0x0/0x30 Jan 6 18:29:49 Tower kernel: [<c103391d>] ? autoremove_wake_function+0x0/0x30 Jan 6 18:29:49 Tower kernel: [<c1078427>] ? core_sys_select+0x232/0x280 Jan 6 18:29:49 Tower kernel: [<c11370cc>] ? copy_to_user+0x33/0x3c Jan 6 18:29:49 Tower kernel: [<c1136f51>] ? copy_from_user+0x31/0x54 Jan 6 18:29:49 Tower kernel: [<c1224999>] sys_recvfrom+0x7b/0xba Jan 6 18:29:49 Tower kernel: [<c10950ba>] ? posix_lock_file+0xe/0x10 Jan 6 18:29:49 Tower kernel: [<c10950e3>] ? vfs_lock_file+0x27/0x2b Jan 6 18:29:49 Tower kernel: [<c1039725>] ? ktime_get_ts+0xc3/0xcd Jan 6 18:29:49 Tower kernel: [<c107753f>] ? poll_select_copy_remaining+0xb3/0xcf Jan 6 18:29:49 Tower kernel: [<c1224d51>] sys_socketcall+0xfb/0x170 Jan 6 18:29:49 Tower kernel: [<c1002935>] syscall_call+0x7/0xb Jan 6 18:29:54 Tower kernel: eth0: hw csum failure. Jan 6 18:29:54 Tower kernel: Pid: 0, comm: swapper Not tainted 2.6.32.9-unRAID #8 Jan 6 18:29:54 Tower kernel: Call Trace: Jan 6 18:29:54 Tower kernel: [<c122f122>] netdev_rx_csum_fault+0x29/0x30 Jan 6 18:29:54 Tower kernel: [<c122b3d3>] __skb_checksum_complete_head+0x41/0x57 Jan 6 18:29:54 Tower kernel: [<c122b3f4>] __skb_checksum_complete+0xb/0x10 Jan 6 18:29:54 Tower kernel: [<c1259f35>] tcp_v4_rcv+0x113/0x5d2 Jan 6 18:29:54 Tower kernel: [<c1174473>] ? mix_pool_bytes_extract+0x117/0x11f Jan 6 18:29:54 Tower kernel: [<c1243051>] ip_local_deliver+0xb2/0x154 Jan 6 18:29:54 Tower kernel: [<c1243545>] ip_rcv+0x452/0x481 Jan 6 18:29:54 Tower kernel: [<c10392d9>] ? ktime_get_real+0x13/0x2f Jan 6 18:29:54 Tower kernel: [<c122eb3d>] netif_receive_skb+0x221/0x23c Jan 6 18:29:54 Tower kernel: [<c122eece>] ? __napi_gro_receive+0x85/0x8d Jan 6 18:29:54 Tower kernel: [<c122ebcf>] napi_skb_finish+0x1c/0x31 Jan 6 18:29:54 Tower kernel: [<c122ef25>] napi_gro_receive+0x20/0x24 Jan 6 18:29:54 Tower kernel: [<f8299cd8>] sky2_poll+0x6b6/0x8b6 [sky2] Jan 6 18:29:54 Tower kernel: [<c12312aa>] net_rx_action+0x57/0x102 Jan 6 18:29:54 Tower kernel: [<c1028261>] __do_softirq+0x84/0xf8 Jan 6 18:29:54 Tower kernel: [<c10282fb>] do_softirq+0x26/0x2b Jan 6 18:29:54 Tower kernel: [<c1028556>] irq_exit+0x29/0x2b Jan 6 18:29:54 Tower kernel: [<c10042c5>] do_IRQ+0x80/0x96 Jan 6 18:29:54 Tower kernel: [<c1002f29>] common_interrupt+0x29/0x30 Jan 6 18:29:54 Tower kernel: [<c1008160>] ? default_idle+0x2d/0x42 Jan 6 18:29:54 Tower kernel: [<c1001a14>] cpu_idle+0x3a/0x4e Jan 6 18:29:54 Tower kernel: [<c129c662>] start_secondary+0x195/0x19a Jan 6 18:30:00 Tower kernel: eth0: hw csum failure. Jan 6 18:30:00 Tower kernel: Pid: 0, comm: swapper Not tainted 2.6.32.9-unRAID #8 Jan 6 18:30:00 Tower kernel: Call Trace: Jan 6 18:30:00 Tower kernel: [<c122f122>] netdev_rx_csum_fault+0x29/0x30 Jan 6 18:30:00 Tower kernel: [<c122b3d3>] __skb_checksum_complete_head+0x41/0x57 Jan 6 18:30:00 Tower kernel: [<c122b3f4>] __skb_checksum_complete+0xb/0x10 Jan 6 18:30:00 Tower kernel: [<c1259f35>] tcp_v4_rcv+0x113/0x5d2 Jan 6 18:30:00 Tower kernel: [<c1243051>] ip_local_deliver+0xb2/0x154 Jan 6 18:30:00 Tower kernel: [<c1243545>] ip_rcv+0x452/0x481 Jan 6 18:30:00 Tower kernel: [<c10392d9>] ? ktime_get_real+0x13/0x2f Jan 6 18:30:00 Tower kernel: [<c122eb3d>] netif_receive_skb+0x221/0x23c Jan 6 18:30:00 Tower kernel: [<c122eece>] ? __napi_gro_receive+0x85/0x8d Jan 6 18:30:00 Tower kernel: [<c122ebcf>] napi_skb_finish+0x1c/0x31 Jan 6 18:30:00 Tower kernel: [<c122ef25>] napi_gro_receive+0x20/0x24 Jan 6 18:30:00 Tower kernel: [<f8299cd8>] sky2_poll+0x6b6/0x8b6 [sky2] Jan 6 18:30:00 Tower kernel: [<c12312aa>] net_rx_action+0x57/0x102 Jan 6 18:30:00 Tower kernel: [<c1028261>] __do_softirq+0x84/0xf8 Jan 6 18:30:00 Tower kernel: [<c10282fb>] do_softirq+0x26/0x2b Jan 6 18:30:00 Tower kernel: [<c1028556>] irq_exit+0x29/0x2b Jan 6 18:30:00 Tower kernel: [<c10042c5>] do_IRQ+0x80/0x96 Jan 6 18:30:00 Tower kernel: [<c1002f29>] common_interrupt+0x29/0x30 Jan 6 18:30:00 Tower kernel: [<c1008160>] ? default_idle+0x2d/0x42 Jan 6 18:30:00 Tower kernel: [<c1001a14>] cpu_idle+0x3a/0x4e Jan 6 18:30:00 Tower kernel: [<c129c662>] start_secondary+0x195/0x19a Jan 6 18:30:06 Tower kernel: sky2 eth0: Link is down. Jan 6 18:30:06 Tower ifplugd(eth0)[1340]: Link beat lost. Jan 6 18:30:17 Tower ifplugd(eth0)[1340]: Executing '/etc/ifplugd/ifplugd.action eth0 down'. Jan 6 18:30:17 Tower logger: /etc/rc.d/rc.inet1: /sbin/ifconfig eth0 down Jan 6 18:30:17 Tower ntpd[1561]: ntpd exiting on signal 15 Jan 6 18:30:17 Tower ifplugd(eth0)[1340]: client: Stopping NTP daemon... Jan 6 18:30:17 Tower kernel: sky2 eth0: disabling interface Jan 6 18:30:18 Tower ifplugd(eth0)[1340]: Program executed successfully. Jan 6 18:30:18 Tower kernel: sky2 eth0: enabling interface This is the controller details: 02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8053 PCI-E Gigabit Ethernet Controller (rev 19) Subsystem: Giga-byte Technology Marvell 88E8053 Gigabit Ethernet Controller (Gigabyte) Flags: bus master, fast devsel, latency 0, IRQ 28 Memory at f9000000 (64-bit, non-prefetchable) I/O ports at a000 [virtual] Expansion ROM at fa200000 [disabled] Capabilities: [48] Power Management version 2 Capabilities: [50] Vital Product Data Capabilities: [5c] Message Signalled Interrupts: Mask- 64bit+ Queue=0/1 Enable+ Capabilities: [e0] Express Legacy Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Kernel driver in use: sky2 Kernel modules: sky2 I have seen this msg relating to marvell drivers in older kernels, but just wondering why 4.56 works and 4.6 doesnt! Tony

thanks all for your help I will send it off to seagate. Happy New Year Tony

I have received a replacement for a seagate 1.5tb that would not power on. The replacement is a refurb and I had noticed that after a previous preclear and use, the reallocated counts increased - so I put it back on the shelf. I have decided to have another go and have just completed another preclear. What do you think of the results? Should I send it back? Drive = ST31500341AS Thanks Tony =========================================================================== = unRAID server Pre-Clear disk /dev/sdg = cycle 1 of 1 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Testing if the clear has been successful. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 38C, Elapsed Time: 23:52:00 ============================================================================ == == Disk /dev/sdg has been successfully precleared == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 55c55 < 1 Raw_Read_Error_Rate 0x000f 110 099 006 Pre-fail Always - 170502277 --- > 1 Raw_Read_Error_Rate 0x000f 117 099 006 Pre-fail Always - 125149733 58,59c58,59 < 5 Reallocated_Sector_Ct 0x0033 098 098 036 Pre-fail Always - 100 < 7 Seek_Error_Rate 0x000f 065 060 030 Pre-fail Always - 3630817 --- > 5 Reallocated_Sector_Ct 0x0033 098 098 036 Pre-fail Always - 105 > 7 Seek_Error_Rate 0x000f 066 060 030 Pre-fail Always - 3747850 63c63 < 187 Reported_Uncorrect 0x0032 028 028 000 Old_age Always - 72 --- > 187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 122 65,69c65,69 < 189 High_Fly_Writes 0x003a 060 060 000 Old_age Always - 40 < 190 Airflow_Temperature_Cel 0x0022 068 061 045 Old_age Always - 32 (Lifetime Min/Max 24/32) < 195 Hardware_ECC_Recovered 0x001a 047 032 000 Old_age Always < 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 2 < 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 2 --- > 189 High_Fly_Writes 0x003a 035 035 000 Old_age Always - 65 > 190 Airflow_Temperature_Cel 0x0022 062 059 045 Old_age Always - 38 (Lifetime Min/Max 24/41) > 195 Hardware_ECC_Recovered 0x001a 055 032 000 Old_age Always > 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 > 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 71,73c71,73 < 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 67959267526682 < 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 1034285378 < 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 3709303039 --- > 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 277639570917426 > 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 3966143492 > 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 3113440727 76c76 < ATA Error Count: 72 (device log contains only the most recent five errors) --- > ATA Error Count: 122 (device log contains only the most recent five errors) 91c91 < Error 72 occurred at disk power-on lifetime: 2599 hours (108 days + 7 hours) --- > Error 122 occurred at disk power-on lifetime: 2628 hours (109 days + 12 hours) 102,106c102,106 < 25 00 00 ff ff ff ef 00 1d+20:29:26.691 READ DMA EXT < 27 00 00 00 00 00 e0 00 1d+20:29:26.658 READ NATIVE MAX ADDRESS EXT < ec 00 00 00 00 00 a0 02 1d+20:29:26.638 IDENTIFY DEVICE < ef 03 46 00 00 00 a0 02 1d+20:29:26.618 SET FEATURES [set transfer mode] < 27 00 00 00 00 00 e0 00 1d+20:29:26.579 READ NATIVE MAX ADDRESS EXT --- > 25 00 08 ff ff ff ef 00 13:33:54.290 READ DMA EXT > 27 00 00 00 00 00 e0 00 13:33:54.261 READ NATIVE MAX ADDRESS EXT > ec 00 00 00 00 00 a0 02 13:33:54.241 IDENTIFY DEVICE > ef 03 45 00 00 00 a0 02 13:33:54.221 SET FEATURES [set transfer mode] > 27 00 00 00 00 00 e0 00 13:33:54.171 READ NATIVE MAX ADDRESS EXT 108c108 < Error 71 occurred at disk power-on lifetime: 2599 hours (108 days + 7 hours) --- > Error 121 occurred at disk power-on lifetime: 2628 hours (109 days + 12 hours) 119,123c119,123 < 25 00 00 ff ff ff ef 00 1d+20:29:23.718 READ DMA EXT < 27 00 00 00 00 00 e0 00 1d+20:29:23.679 READ NATIVE MAX ADDRESS EXT < ec 00 00 00 00 00 a0 02 1d+20:29:23.639 IDENTIFY DEVICE < ef 03 46 00 00 00 a0 02 1d+20:29:23.618 SET FEATURES [set transfer mode] < 27 00 00 00 00 00 e0 00 1d+20:29:23.509 READ NATIVE MAX ADDRESS EXT --- > 25 00 08 ff ff ff ef 00 13:33:51.330 READ DMA EXT > 27 00 00 00 00 00 e0 00 13:33:51.301 READ NATIVE MAX ADDRESS EXT > ec 00 00 00 00 00 a0 02 13:33:51.281 IDENTIFY DEVICE > ef 03 45 00 00 00 a0 02 13:33:51.262 SET FEATURES [set transfer mode] > 27 00 00 00 00 00 e0 00 13:33:51.131 READ NATIVE MAX ADDRESS EXT 125c125 < Error 70 occurred at disk power-on lifetime: 2599 hours (108 days + 7 hours) --- > Error 120 occurred at disk power-on lifetime: 2628 hours (109 days + 12 hours) 136,140c136,140 < 25 00 00 ff ff ff ef 00 1d+20:29:20.745 READ DMA EXT < 27 00 00 00 00 00 e0 00 1d+20:29:20.709 READ NATIVE MAX ADDRESS EXT < ec 00 00 00 00 00 a0 02 1d+20:29:20.689 IDENTIFY DEVICE < ef 03 46 00 00 00 a0 02 1d+20:29:20.671 SET FEATURES [set transfer mode] < 27 00 00 00 00 00 e0 00 1d+20:29:20.619 READ NATIVE MAX ADDRESS EXT --- > 25 00 08 ff ff ff ef 00 13:33:48.370 READ DMA EXT > 27 00 00 00 00 00 e0 00 13:33:48.341 READ NATIVE MAX ADDRESS EXT > ec 00 00 00 00 00 a0 02 13:33:48.321 IDENTIFY DEVICE > ef 03 45 00 00 00 a0 02 13:33:48.305 SET FEATURES [set transfer mode] > 27 00 00 00 00 00 e0 00 13:33:48.171 READ NATIVE MAX ADDRESS EXT 142c142 < Error 69 occurred at disk power-on lifetime: 2599 hours (108 days + 7 hours) --- > Error 119 occurred at disk power-on lifetime: 2628 hours (109 days + 12 hours) 153,157c153,157 < 25 00 00 ff ff ff ef 00 1d+20:29:17.739 READ DMA EXT < 27 00 00 00 00 00 e0 00 1d+20:29:17.710 READ NATIVE MAX ADDRESS EXT < ec 00 00 00 00 00 a0 02 1d+20:29:17.688 IDENTIFY DEVICE < ef 03 46 00 00 00 a0 02 1d+20:29:17.670 SET FEATURES [set transfer mode] < 27 00 00 00 00 00 e0 00 1d+20:29:17.558 READ NATIVE MAX ADDRESS EXT --- > 25 00 08 ff ff ff ef 00 13:33:45.430 READ DMA EXT > 27 00 00 00 00 00 e0 00 13:33:45.401 READ NATIVE MAX ADDRESS EXT > ec 00 00 00 00 00 a0 02 13:33:45.381 IDENTIFY DEVICE > ef 03 45 00 00 00 a0 02 13:33:45.348 SET FEATURES [set transfer mode] > 27 00 00 00 00 00 e0 00 13:33:45.221 READ NATIVE MAX ADDRESS EXT 159c159 < Error 68 occurred at disk power-on lifetime: 2599 hours (108 days + 7 hours) --- > Error 118 occurred at disk power-on lifetime: 2628 hours (109 days + 12 hours) 170,174c170,174 < 25 00 00 ff ff ff ef 00 1d+20:29:14.806 READ DMA EXT < 27 00 00 00 00 00 e0 00 1d+20:29:14.768 READ NATIVE MAX ADDRESS EXT < ec 00 00 00 00 00 a0 02 1d+20:29:14.748 IDENTIFY DEVICE < ef 03 46 00 00 00 a0 02 1d+20:29:14.732 SET FEATURES [set transfer mode] < 27 00 00 00 00 00 e0 00 1d+20:29:14.668 READ NATIVE MAX ADDRESS EXT --- > 25 00 08 ff ff ff ef 00 13:33:42.469 READ DMA EXT > 27 00 00 00 00 00 e0 00 13:33:42.441 READ NATIVE MAX ADDRESS EXT > ec 00 00 00 00 00 a0 02 13:33:42.421 IDENTIFY DEVICE > ef 03 45 00 00 00 a0 02 13:33:42.402 SET FEATURES [set transfer mode] > 27 00 00 00 00 00 e0 00 13:33:42.351 READ NATIVE MAX ADDRESS EXT ============================================================================ root@Tower:/boot#

Could it be due to the seagate firmware bug? Just a thought Tony

I didn't solve mine either. In the end I just set up a cron job to delete everything after a day from BIN. It solves the problem that I had of accidentally deleting something from a share

I have the same problem.... intermittently.

I am having a few problems with "failed" downloads..... I'm using the latest 2.0 dependencies and if I manually use the PAR2 and associated PARS I can repair it successfully. Any ideas on how to solve? (using newshosting) rgds Spants

I use crashplan to backup my critical files on my pcs to the server and to backup server stuff that I never want to lose to a friends server (about 20gb). Seems to work great!

I have just done the upgrade from 052 to 053 - I had to delete the old .py files to make it work

has anyone tried to update from SABnzbd-0.5.2 to SABnzbd-0.5.3? It now supports .gz files that come from bin-req Tony

... I tried using the alpha3 linux version, the ffmpeg pre-compiled version and still had issues, so I gave up and used the windows version which worked straight away:) (but I must learn linux!) Tony

I have used Joe's method to move all packages from flash to /mnt/cache/.custom/flash/packages and it works brilliantly! Thanks for sharing Tony

Thanks Brit - will try tomorrow as I am off to a BBQ! cheers Tony

definitely failed to build ffmpeg.... no rush! Thanks, Tony

I cant get this working I have tried the manual way and from unraid menu. I can see the server and navigate the directories but when I choose a film, it waits at Loading. I think that it is a similar problem to another poster ie the mp3lame option is not reconised and therefore ffmpeg is not built - I cannot find an executable for it.... Any hints? (I have c compilers and java installed & using 4.5.6) Tony

to close the thread..... I think the answer is here http://lime-technology.com/forum/index.php?topic=6184.0 Tony

Hi I think that my flash drive is becoming full. As a linux newbie, what would be the syntax for booting from USB and then transferring the pkg installations etc from a hidden "." directory on the cache drive?. Are there any gotchas? I would hate to lose my data! cheers Tony My go script is: #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & /boot/unmenu/uu & # determine if cache drive online, retry upto 7 times for i in 0 1 2 3 4 5 6 7 do if [ ! -d /mnt/cache ] then sleep 10 fi done /boot/cache_dirs -w -e "BIN" & cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c cp --preserve=timestamps /boot/custom/etc/ssh/ssh*key* /etc/ssh chmod 600 /etc/ssh/ssh*key* /etc/rc.d/rc.sshd start # install crashplan tar -C / -xvf /boot/packages/crashplan.tar /usr/local/crashplan/bin/CrashPlanEngine start # If Cache drive is online, start SABNzbd if [ -d /mnt/cache ]; then # Start SABnzbd and sickbeard installpkg /boot/custom/SABnzbdDependencies-1.3-i486-unRAID.tgz python /mnt/cache/.custom/sabnzbd/SABnzbd.py -d -s 192.168.1.22:88 nohup python /mnt/cache/.custom/sickbeard/SickBeard.py & fi # setup delete of BIN files older than 1 or 2 days daily crontab -l >/tmp/crontab echo "# delete 2 day old files:" >>/tmp/crontab echo "35 6 * * * root find /mnt/user/BIN -mtime +1 -print -exec rm -rf {} \;" >>/tmp/crontab crontab /tmp/crontab

I am pretty sure that the path parameter allows you to do this. I think that I have solved my problem with exclude not working - I didn't have a /tmp directory and therefore as the first parameter, it caused the other parameters not to be read. Will test further...

Thanks for the suggestion but it is still putting them in the BIN (tried doing the changes and then a reboot) Is my syntax correct? regards Spants

this is working well in that it creates a copy in BIN for me to retrieve.... however, I cant get it to exclude my download directories. Can anyone see what I have done wrong? regards Spants [bIN] path = /mnt/user/BIN read only = No [global] vfs objects = recycle recycle:repository = /mnt/user/BIN/%m recycle:keeptree = Yes recycle:touch = Yes recycle:versions = Yes recycle:exclude = *.tmp *.tib recycle:exclude_dir = /tmp | /mnt/user/Spants/1.5tb/downloads2 | /mnt/user/Spants/1.5tb/downloads | /mnt/user/downloads recycle:noversions = *.doc *.xls *.ppt