darias

My guess is something wrong with the latest update of this Docker (7 days ago). I reverted back to the last update (2 months ago) and it's working again. If you want to try this, edit the Docker and change the repository to be: linuxserver/dokuwiki:2018-04-22c-ls41 No warranties, expressed or implied!

This morning I discovered that my parity drive is now showing 31,000+ errors in the Main WebUI. So, my uneducated guess is my new parity drive may be failing/failed? I found my syslog is full of: Tower kernel: md: disk0 read error, sector=3641072456 Oh, and I now see SMART for the disk shows: 197 Current pending sector 0x0032 200 200 000 Old age Always - 26 198 Offline uncorrectable 0x0030 200 200 000 Old age Offline - 26 Can I just get a confirmation that all I need to do is remove and replace the parity drive, and the rebuild will be automatic? I have a pre-cleared drive ready to go already. Is this just a matter of changing the drive assignment through the WebUI? Thanks, Dave tower-diagnostics-20161203-0909.zip

Interestingly, now that I have done a parity check, I cannot recreate the issue. I've tried copying files to all disks discretely, as well as to the array, and I am not seeing the issue. I will test some more tomorrow. Thanks for all the help. Dave

Thanks for the reply. For the copies, I'm going from a directory in /mnt/cache to a directory in /mnt/user. Would it be wise to try to copy direct to each disk (/mnt/diskN)? I will kick off a parity check. To be honest, I can't recall what "normal" speed would be for my system, so I can report back with the results. Thanks for the note on the drive. I have a precleared drive ready to go. Dave

I rebooted the server this morning, and was able to replicate the issues again. I copied a ~700MB file from my cache drive to the array, which took approximately 30 minutes. I did this on the server, with mc, so this is not a network issue. During this copy, I had a video playing on a remote Kodi system, which again suffered from stuttering and buffering. I'm attaching logs from during and after the transfer, in case they may show something between the two. Thanks! Dave tower-diagnostics-20161201-1150_AfterXfer.zip tower-diagnostics-20161201-1126_DuringXfer.zip

I'll go for a reboot tonight, now that a pre-clear is complete. Thanks, Dave

Greetings! I have been experiencing extremely slow writes and reads from my unRAID system, I believe after completing a parity swap. I had to replace a failing data disk, and in the process moved to a larger parity drive (from 2TB to 3TB). Ever since, it seems that when a file is being written to the array, write speeds are slow, and reads are also affected (i.e. playing videos via Kodi results in pausing and stopping). As of this morning, a mover job has been trying to move approximately 80GB from cache to the array. From looking at the syslog, it looks like some writes take a few minutes, while others take 30+ minutes, for files that should be similar in size. I've attached a diagnostics archive from early this morning. I am running unRAID 6.1.4. Any help is appreciated. I cannot figure out anything other than the array writes being the issue, but no obvious cause. Thanks, Dave UPDATE: The parity drive ended up being a shucked WD Green sold as new by a 3rd-party Amazon seller. After replacing it with a new drive, I have not experienced any more issues. Thanks johnnie.black for the support! tower-diagnostics-20161129-0514.zip

I would then guess this explains the loss of data on disk3, the one that unRAID was not seeing. While I cannot exactly recall my actions, I know that the NEW third disk was not a member of the array, so I assigned it and then started the array. If I'm understanding correctly, what I should have done after the preclear was complete, was to just stop and start the array, and let unRAID take over. It is also possible I removed disk3 from the array prior to replacing. In hindsight, it sounds like a bad decision. Does this also explain the loss of data on disk1 and disk2? This is the most confusing part to me. If the data was there, and then overnight is gone, I don't understand what happened. I was able to mount disk3 on my desktop. Thanks for the tip on the DiskInternals utility. Looks like at the very least the disk is readable, so I can recover that data. unRAID was reporting it as unformatted, which I now know may not be the end of the world. Again, thanks for all the help. Even if the data from disk1 & disk2 cannot be recovered, now at least I better understand the recovery process. Dave

I did not experience a second drive failure, at least not that I was aware of. From what I understand about unRAID, that should have meant no loss of data, apart from what was on my "disk 3". I did have a spare drive, but it was called to duty elsewhere, unfortunately. When I completed the preclear on the replacement drive, I added it to the array and started the array. The array was rebuilt. The data loss appears to have occurred prior to the rebuild. The standard web GUI shows green balls for all drives, but I do see that my "disk1" has 126 errors listed. I will try to mount the old disk and see if it is readable. Thanks for the help! Dave

I discovered this evening that I have lost several hundred GB of data on my unRAID 4.7 machine. I'm hoping someone may be able to assist by either helping me recover the lost data, or confirming it's gone for good, so I can move on... Here is the recent history leading up to the loss and discovery: 5/20 - One HDD (disk 3) is reported as "DISK_DSBL". No spare HDD is available. 5/26 or 5/27 - unRAID server loses power suddenly 5/28 - Data loss is seen via Failure Notification emails (but not discovered until today). Loss appears to have occurred between 23:47 & 00:47. 5/29 - New HDD is installed and preclear is started 6/1 - Preclear is complete and new HDD is added to array, array rebuild is started 6/1 - Array rebuild is complete, 600+GB discovered missing My unRAID machine has three data drives, all WD 2TB Green. Lost data was approximately: md1 - 47.9GB md2 - 104GB md3 (failed HDD) - 486GB The original "disk 3" is still available, and has not been reformatted. It is not currently installed in the unRAID machine. Please let me know what other data I can provide to help sort out this problem. Considering the loss appears to have been several days ago, after at least one reboot, would a syslog even be helpful? Looking at the syslog via unMenu, I rebooted early this morning. Thanks for the help. Dave

Time Machine will work with SMB shares. See the forum post linked in the first post for links to How-To guides. Dave

Time Machine is currently not working for me. It ran fine for a few weeks, but recently Time Machine threw an error & wanted to create a new backup (from scratch). I'm not sure why this has happened. At this point I think I need to start over, create a new sparsebundle, copy, etc. The sparsebundle folder does show up as a User share in the Shares page for me as well. I believe this is the way unRAID works. Any folder on a protected disc will become a share. What I'm not sure of is whether or not mounting Disk 2 and pointing Time Machine to it is the correct way to go here.

Joe, I just tried your attached script, and it fails on my unRAID 4.7 system. It appears to die with the error: xargs: xargs.c:445: main: Assertion `bc_ctl.arg_max <= (131072-2048)' failed. My assumption is that this script is the same as the one you posted in the v4.5 Support topic. I had posted (http://lime-technology.com/forum/index.php?topic=7018.msg97824#msg97824) there with the error as well. A Google search turns up results that seem to indicate a problem with glibc. Any thoughts? Thanks, Dave

I just started this two days ago. Rather than performing the initial backup over the network to unRAID, I built the sparsebundle, transferred it to an external USB drive and pointed Time Machine to the external drive. After the first backup completed, I moved the USB drive to my unRAID server and copied the sparebundle to one of the discs (/mnt/disk2 in my case). Once the copy was complete, I pointed Time Machine to the drive share (again, disk2 for me), and the next scheduled backup went off without a hitch! One thing I have noticed is that Time Machine reports the full size of my drive, and not the size limit I imposed when I built the sparsebundle. I set it to 250GB, so it will be a while before I can determine the actual behavior.

I've just finished building my first UnRAID rig, and I want to move the contents of several USB hard drives to the UnRAID box. They were originally attached to another Linux machine, so they are ext2, and show up in UnRAID. I have them mounted and, as a test, have moved a directory to a user share I created previously, but I want to be sure this is an acceptable method. Here's what I did: I created a user share named 'TV'. I then copied a directory to '/mnt/user/TV' (using the command cp -r /path/to/dir /mnt/user/TV). Here's my question: Will parity be intact using this method, i.e. will it be calculated properly during the file move? From what I can tell, the destination directory exists within the UnRAID protected system. I have read a few threads on the subject of moving data from locally mounted drives that are not in UnRAID (as I'm doing), but none that discussed where to copy files to. Thank you, Dave