icon123

What would the syntax be if I wanted to backup a specific directory called Home Movies in a share called Movies be? i.e. /Movies/Home Movies

Thanks @trurl and thanks @dlandon for the great plugin. Any other rsync switches that would be useful to know or anything else people add to their scripts? Only plan on using this to back up my shares and store HDDs offsite.

Can someone show me what/where I need to add in the backup script in the op for backing up additional shares?

I want to start using this plugin to back up my shares to an external HDD. Where could I go to get help with a script for doing this? I know there is an example in the 1st post, but I'm not sure what it does/doesn't do. I'm trying to learn rsync, but I'm not confident plus the rest of the scripting is Greek to me. Thanks,

Thanks for the great docker! I have it running on 2 different unraid servers. I need to try to connect to both of them at the same time from a windows machine. Can anyone here help with this? My understanding is I need to create an additional tap adapter, which I did, but then I don't know how to use it. TIA. Edit: Just a follow up to my original post. What I need to do is create a client config file. If anyone can help with this that would be great. When you first connect to the server, it downloads openvpn connect which auto creates/install a client config file, but I can't access it or copy it. So what I need to do is recreate it. I'm trying, but it is a big learning curve for me.

Awesome, thanks!

I am running rc8 and that appears to me normal operation. At least that is how mine works. Thanks for the confirmation, but I hope there is a way to automatically start the array on power up. I need a set it and forget approach for this technically limited individual.

I recently built a unRaid server for a friend and used RC5-8a. One thing I noticed that whenever the server powers up, the array doesn't start automatically, I have to manual start it. Is this normal and can I have it automatically start at power up? It didn't seem like 4.7 did this. Thanks and sorry if this is a stupid question.

So are you saying there is a problem with the unraid driver for the SASLP-MV8 card? I haven't been having great luck with it lately. I even switched from a Asus MB to a recommended Biostar one because of it. I took the same drive and pre_clear is working on it via the onboard sata port. This was the message I received in the syslog in regards to it: Mar 13 21:22:42 Hitch kernel: ------------[ cut here ]------------ Mar 13 21:22:42 Hitch kernel: WARNING: at drivers/ata/libata-core.c:5186 ata_qc_issue+0x10b/0x308() Mar 13 21:22:42 Hitch kernel: Hardware name: A760G M2+ Mar 13 21:22:42 Hitch kernel: Modules linked in: tun md_mod xor atiixp ahci r8169 mvsas libsas scst scsi_transport_sas Mar 13 21:22:42 Hitch kernel: Pid: 25832, comm: hdparm Not tainted 2.6.32.9-unRAID #8 Mar 13 21:22:42 Hitch kernel: Call Trace: Mar 13 21:22:42 Hitch kernel: [<c102449e>] warn_slowpath_common+0x60/0x77 Mar 13 21:22:42 Hitch kernel: [<c10244c2>] warn_slowpath_null+0xd/0x10 Mar 13 21:22:42 Hitch kernel: [<c11b624d>] ata_qc_issue+0x10b/0x308 Mar 13 21:22:42 Hitch kernel: [<c11ba260>] ata_scsi_translate+0xd1/0xff Mar 13 21:22:42 Hitch kernel: [<c11a816c>] ? scsi_done+0x0/0xd Mar 13 21:22:42 Hitch kernel: [<c11a816c>] ? scsi_done+0x0/0xd Mar 13 21:22:42 Hitch kernel: [<c11baa40>] ata_sas_queuecmd+0x120/0x1d7 Mar 13 21:22:42 Hitch kernel: [<c11bc6df>] ? ata_scsi_pass_thru+0x0/0x21d Mar 13 21:22:42 Hitch kernel: [<f843369a>] sas_queuecommand+0x65/0x20d [libsas] Mar 13 21:22:42 Hitch kernel: [<c11a816c>] ? scsi_done+0x0/0xd Mar 13 21:22:42 Hitch kernel: [<c11a82c0>] scsi_dispatch_cmd+0x147/0x181 Mar 13 21:22:42 Hitch kernel: [<c11ace4d>] scsi_request_fn+0x351/0x376 Mar 13 21:22:42 Hitch kernel: [<c1126798>] __blk_run_queue+0x78/0x10c Mar 13 21:22:42 Hitch kernel: [<c1124446>] elv_insert+0x67/0x153 Mar 13 21:22:42 Hitch kernel: [<c11245b8>] __elv_add_request+0x86/0x8b Mar 13 21:22:42 Hitch kernel: [<c1129343>] blk_execute_rq_nowait+0x4f/0x73 Mar 13 21:22:42 Hitch kernel: [<c11293dc>] blk_execute_rq+0x75/0x91 Mar 13 21:22:42 Hitch kernel: [<c11292cc>] ? blk_end_sync_rq+0x0/0x28 Mar 13 21:22:42 Hitch kernel: [<c112636f>] ? get_request+0x204/0x28d Mar 13 21:22:42 Hitch kernel: [<c11269d6>] ? get_request_wait+0x2b/0xd9 Mar 13 21:22:42 Hitch kernel: [<c112c2bf>] sg_io+0x22d/0x30a Mar 13 21:22:42 Hitch kernel: [<c112c5a8>] scsi_cmd_ioctl+0x20c/0x3bc Mar 13 21:22:42 Hitch kernel: [<c11b3257>] sd_ioctl+0x6a/0x8c Mar 13 21:22:42 Hitch kernel: [<c112a420>] __blkdev_driver_ioctl+0x50/0x62 Mar 13 21:22:42 Hitch kernel: [<c112ad1c>] blkdev_ioctl+0x8b0/0x8dc Mar 13 21:22:42 Hitch kernel: [<c1131e2d>] ? kobject_get+0x12/0x17 Mar 13 21:22:42 Hitch kernel: [<c112b0f8>] ? get_disk+0x4a/0x61 Mar 13 21:22:42 Hitch kernel: [<c101b028>] ? kmap_atomic+0x14/0x16 Mar 13 21:22:42 Hitch kernel: [<c11334a5>] ? radix_tree_lookup_slot+0xd/0xf Mar 13 21:22:42 Hitch kernel: [<c104a179>] ? filemap_fault+0xb8/0x305 Mar 13 21:22:42 Hitch kernel: [<c1048c43>] ? unlock_page+0x18/0x1b Mar 13 21:22:42 Hitch kernel: [<c1057c63>] ? __do_fault+0x3a7/0x3da Mar 13 21:22:42 Hitch kernel: [<c105985f>] ? handle_mm_fault+0x42d/0x8f1 Mar 13 21:22:42 Hitch kernel: [<c108b6c6>] block_ioctl+0x2a/0x32 Mar 13 21:22:42 Hitch kernel: [<c108b69c>] ? block_ioctl+0x0/0x32 Mar 13 21:22:42 Hitch kernel: [<c10769d5>] vfs_ioctl+0x22/0x67 Mar 13 21:22:42 Hitch kernel: [<c1076f33>] do_vfs_ioctl+0x478/0x4ac Mar 13 21:22:42 Hitch kernel: [<c105dcdd>] ? do_mmap_pgoff+0x232/0x294 Mar 13 21:22:42 Hitch kernel: [<c1076f93>] sys_ioctl+0x2c/0x45 Mar 13 21:22:42 Hitch kernel: [<c1002935>] syscall_call+0x7/0xb Mar 13 21:22:42 Hitch kernel: ---[ end trace 7f1e9f192190e675 ]---

I'll try it again, but I thought I tried it with /dev/sdb as well as /dev/sdb/ I was in a hurry this morning so who knows. Any clue why the lockup might have occured or anything I can send to you that might help. Edit: I was able to run it with the /dev/sdb command. Must have been in too big of a hurry. It locks up and here are a few of the syslog entries: Mar 15 17:28:06 Hitch kernel: end_request: I/O error, dev sdb, sector 9346240 (Errors) Mar 15 17:28:06 Hitch kernel: ata1: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 (Drive related) Mar 15 17:28:06 Hitch kernel: ata1: status=0x41 { DriveReady Error } (Errors) Mar 15 17:28:06 Hitch kernel: ata1: error=0x04 { DriveStatusError } (Errors) Mar 15 17:28:06 Hitch kernel: ata1: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 (Drive related) Mar 15 17:28:06 Hitch kernel: ata1: status=0x41 { DriveReady Error } (Errors) Mar 15 17:28:06 Hitch kernel: ata1: error=0x04 { DriveStatusError } (Errors) Mar 15 17:28:06 Hitch kernel: ata1: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 (Drive related) Mar 15 17:28:06 Hitch kernel: ata1: status=0x41 { DriveReady Error } (Errors) Mar 15 17:28:06 Hitch kernel: ata1: error=0x04 { DriveStatusError } (Errors) Mar 15 17:28:06 Hitch kernel: ata1: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 (Drive related) Let me know if there is anything else I can provide.

It does appear that my drive (that was connected to a SASLP-MV8) precleard correctly in good time I might add. I couldn't get a full report due to not having enough room on my flash drive. I then hooked that same drive to a different port on that card along with another drive on another port on the same card and preclear locked up and filled the syslog with errors. I then left one of the drives in and although it listed as an available drive to preclear, this is the message I got: Sorry: dev/sdb does not exist as a block device Clearing will NOT be performed Sorry, I couldn't grab any logs and had to leave for work.

Thanks Joe. Perfect timing. It appears to have fix my previous problems and my earlier lockups. Is this normal/ok? Mar 13 21:21:06 Hitch kernel: sdb: sdb1 Mar 13 21:22:42 Hitch kernel: ------------[ cut here ]------------ Mar 13 21:22:42 Hitch kernel: WARNING: at drivers/ata/libata-core.c:5186 ata_qc_issue+0x10b/0x308() Mar 13 21:22:42 Hitch kernel: Hardware name: A760G M2+ Mar 13 21:22:42 Hitch kernel: Modules linked in: tun md_mod xor atiixp ahci r8169 mvsas libsas scst scsi_transport_sas Mar 13 21:22:42 Hitch kernel: Pid: 25832, comm: hdparm Not tainted 2.6.32.9-unRAID #8 Mar 13 21:22:42 Hitch kernel: Call Trace: Mar 13 21:22:42 Hitch kernel: [<c102449e>] warn_slowpath_common+0x60/0x77 Mar 13 21:22:42 Hitch kernel: [<c10244c2>] warn_slowpath_null+0xd/0x10 Mar 13 21:22:42 Hitch kernel: [<c11b624d>] ata_qc_issue+0x10b/0x308 Mar 13 21:22:42 Hitch kernel: [<c11ba260>] ata_scsi_translate+0xd1/0xff Mar 13 21:22:42 Hitch kernel: [<c11a816c>] ? scsi_done+0x0/0xd Mar 13 21:22:42 Hitch kernel: [<c11a816c>] ? scsi_done+0x0/0xd Mar 13 21:22:42 Hitch kernel: [<c11baa40>] ata_sas_queuecmd+0x120/0x1d7 Mar 13 21:22:42 Hitch kernel: [<c11bc6df>] ? ata_scsi_pass_thru+0x0/0x21d Mar 13 21:22:42 Hitch kernel: [<f843369a>] sas_queuecommand+0x65/0x20d [libsas] Mar 13 21:22:42 Hitch kernel: [<c11a816c>] ? scsi_done+0x0/0xd Mar 13 21:22:42 Hitch kernel: [<c11a82c0>] scsi_dispatch_cmd+0x147/0x181 Mar 13 21:22:42 Hitch kernel: [<c11ace4d>] scsi_request_fn+0x351/0x376 Mar 13 21:22:42 Hitch kernel: [<c1126798>] __blk_run_queue+0x78/0x10c Mar 13 21:22:42 Hitch kernel: [<c1124446>] elv_insert+0x67/0x153 Mar 13 21:22:42 Hitch kernel: [<c11245b8>] __elv_add_request+0x86/0x8b Mar 13 21:22:42 Hitch kernel: [<c1129343>] blk_execute_rq_nowait+0x4f/0x73 Mar 13 21:22:42 Hitch kernel: [<c11293dc>] blk_execute_rq+0x75/0x91 Mar 13 21:22:42 Hitch kernel: [<c11292cc>] ? blk_end_sync_rq+0x0/0x28 Mar 13 21:22:42 Hitch kernel: [<c112636f>] ? get_request+0x204/0x28d Mar 13 21:22:42 Hitch kernel: [<c11269d6>] ? get_request_wait+0x2b/0xd9 Mar 13 21:22:42 Hitch kernel: [<c112c2bf>] sg_io+0x22d/0x30a Mar 13 21:22:42 Hitch kernel: [<c112c5a8>] scsi_cmd_ioctl+0x20c/0x3bc Mar 13 21:22:42 Hitch kernel: [<c11b3257>] sd_ioctl+0x6a/0x8c Mar 13 21:22:42 Hitch kernel: [<c112a420>] __blkdev_driver_ioctl+0x50/0x62 Mar 13 21:22:42 Hitch kernel: [<c112ad1c>] blkdev_ioctl+0x8b0/0x8dc Mar 13 21:22:42 Hitch kernel: [<c1131e2d>] ? kobject_get+0x12/0x17 Mar 13 21:22:42 Hitch kernel: [<c112b0f8>] ? get_disk+0x4a/0x61 Mar 13 21:22:42 Hitch kernel: [<c101b028>] ? kmap_atomic+0x14/0x16 Mar 13 21:22:42 Hitch kernel: [<c11334a5>] ? radix_tree_lookup_slot+0xd/0xf Mar 13 21:22:42 Hitch kernel: [<c104a179>] ? filemap_fault+0xb8/0x305 Mar 13 21:22:42 Hitch kernel: [<c1048c43>] ? unlock_page+0x18/0x1b Mar 13 21:22:42 Hitch kernel: [<c1057c63>] ? __do_fault+0x3a7/0x3da Mar 13 21:22:42 Hitch kernel: [<c105985f>] ? handle_mm_fault+0x42d/0x8f1 Mar 13 21:22:42 Hitch kernel: [<c108b6c6>] block_ioctl+0x2a/0x32 Mar 13 21:22:42 Hitch kernel: [<c108b69c>] ? block_ioctl+0x0/0x32 Mar 13 21:22:42 Hitch kernel: [<c10769d5>] vfs_ioctl+0x22/0x67 Mar 13 21:22:42 Hitch kernel: [<c1076f33>] do_vfs_ioctl+0x478/0x4ac Mar 13 21:22:42 Hitch kernel: [<c105dcdd>] ? do_mmap_pgoff+0x232/0x294 Mar 13 21:22:42 Hitch kernel: [<c1076f93>] sys_ioctl+0x2c/0x45 Mar 13 21:22:42 Hitch kernel: [<c1002935>] syscall_call+0x7/0xb Mar 13 21:22:42 Hitch kernel: ---[ end trace 7f1e9f192190e675 ]---

If my new 2TB EARS drive consistenly preclears at over 40 hours is that enough of a reason to rma it? Preclear results enclosed. Thanks. preclear_finish_sdg_2011-03-12.txt

I put a new motherboard in and everything came up fine. I also put in a SuperMicro AOC-SASLP-MV8 and when I tried to use it to preclear 2 drives, I get this: Pre-Clear unRAID Disk /dev/sdc ################################################################## 1.7 Error: preclear_disk unable to continue. smartctl is unable to run on /dev/sdc with the -d ata option. smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WMAZA3280454 Firmware Version: 51.0AB51 User Capacity: 2,000,398,934,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Sat Mar 12 17:56:52 2011 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled Error SMART Status command failed Please get assistance from http://smartmontools.sourceforge.net/ Register values returned from SMART Status command are: ST =0x40 ERR=0x00 NS =0x0c SC =0xc0 CL =0x87 CH =0xe0 SEL=0x40 A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.$ I get this when I list drives available for preclearing: ====================================1.7 Disks not assigned to the unRAID array (potential candidates for clearing) ======================================== /dev/sdb = ata-WDC_WD20EARS-00MVWB0_WD-WMAZA0492654 /dev/sdc = scsi-SATA_WDC_WD20EARS-00_WD-WMAZA3280454 It seems like no matter what drive or what port I use, sdc produces this error. I can only assume it has to do with the "scsi", but why or how? Syslog attached for reference. syslog-2011-03-12.zip

Thanks!

Were you responding to me or subwars?

If these are the results that I get after (2) preclears on a new 2 TB EARS drive, should I RMA it? ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 143 100 51 ok 5916 Temperature_Celsius = 132 133 0 ok 18 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ** Changed attributes in files: /tmp/smart_start_sdg /tmp/smart_finish_sdg ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 166 143 51 ok 7198 Seek_Error_Rate = 100 200 0 ok 0 Temperature_Celsius = 132 131 0 ok 18 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. Thanks.

Thanks Joe, Yes my default is MBR-4k-aligned so that makes since along with the other explanations you have provided. The problem is, I wanted to make sure my non-AF drive that was MBR-4k-aligned would not notice any problems; performance decreases, etc. Based upon your explanation, I am assuming not and everything will be ok. BTW, I came accross your convert method after this drive was already in service. Thanks again.

Does the newer preclear script automatically set 4k-aligned on non-advanced format drives? Because it appears that it does. Is it a problem since it did this to one of my 500gb drives and it looks like it is going to do it again to another. Thanks.

Thanks, btw, do they offer advance replacements. Its amazing for how many thousands of $$ I've spent there, I have never had a RMA.

Actually, since all un-readable sectors should have been identified in the pre-read, it indicates the "pending sectors" were probably identified in the post-read. That is not a good thing. As bjp999 said we'll see what happens in the next clear cycle. I do not expect you'll have those errors go away. Here's the log after the new run with the new preclear -A and no jumper. I stopped it originally after a couple of hours to switch to your new report version (just in case something looked odd with the original smart report). Let me know your thoughts? Thanks Here's just the smart reports incase you want to see how they came out. I think this time is better, but I don't know if that makes a difference. Not good ... You now have 35 reallocated sectors + 3 new pending sectors. You can keep running preclear cycles in hopes that the reallocated sectors stabalize, but based on experience here I don't believe it will happen. Every run or two will prodice a few more reallocated sectors, and you'll never be able to trust the drive with data. My advice would be to RMA the disk. Remember that it is far better to learn this BEFORE you add a disk to your array. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 193 177 051 Pre-fail Always - 1938 3 Spin_Up_Time 0x0027 253 253 021 Pre-fail Always - 1358 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 13 5 Reallocated_Sector_Ct 0x0033 199 199 140 Pre-fail Always - 35 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 65 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 11 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 8 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 35 196 Reallocated_Event_Count 0x0032 199 199 000 Old_age Always - 1 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 3 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 131 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 142 Thanks for the advise. Yes, better to find out now. Would you recommend RMA through Newegg or Western Digital?

Actually, since all un-readable sectors should have been identified in the pre-read, it indicates the "pending sectors" were probably identified in the post-read. That is not a good thing. As bjp999 said we'll see what happens in the next clear cycle. I do not expect you'll have those errors go away. Here's the log after the new run with the new preclear -A and no jumper. I stopped it originally after a couple of hours to switch to your new report version (just in case something looked odd with the original smart report). Let me know your thoughts? Thanks Here's just the smart reports incase you want to see how they came out. I think this time is better, but I don't know if that makes a difference. Preclear_smart_reports.zip

Actually, since all un-readable sectors should have been identified in the pre-read, it indicates the "pending sectors" were probably identified in the post-read. That is not a good thing. As bjp999 said we'll see what happens in the next clear cycle. I do not expect you'll have those errors go away. Here's the log after the new run with the new preclear -A and no jumper. I stopped it originally after a couple of hours to switch to your new report version (just in case something looked odd with the original smart report). Let me know your thoughts? Thanks syslog_-_16jan11_-_new_preclear_without_jumper.zip

Thanks for the replies. Drive is only 2 days old too. And now its $10 cheaper . I'll post again in about 26 hours. Thanks. Edit - should I stop preclearing and wait for your new version?

I just finished preclearing my 2TB EARS (jumpered) drive. Can someone look through my syslog to see if everything looks ok. I think everything went fine. I am now preclearing it again with the -A switch and no jumper. TIA syslog_-_15jan11_-_preclear_with_jumper.zip