Recent Posts

Pages: [1] 2 3 ... 10
1
General Discussion / Re: Files randomly left behind on Landing Disk
« Last post by Brahim on September 21, 2017, 01:52:54 pm »
This can happen if there is a file in the array of the same name and path as the landing disk file.
That or the files could potentially be locked by other programs.

There should be entries in the logs relating to the errors in moving the affected files.
2
General Discussion / Re: How To Pool External USB Drives?
« Last post by Brahim on September 21, 2017, 01:47:55 pm »
USB disks are pooled the exact same way internal disks are.

The one thing to remember is that you should avoid using USB disk in a tRAID parity RAID configuration since USB controllers are not designed for heavy and prolonged loads.
3
General Discussion / Re: Error code on verify
« Last post by Brahim on September 21, 2017, 01:45:43 pm »
Please see this topic in regard to the forensic plugin: http://forum.flexraid.com/index.php/topic,4175.msg26989.html

In the most likely case, you will just run the Verify & Sync task, which will correct the parity.

Block failures are not the expectation. However, they are not critical if they happen once in awhile. Frequent block failures are what you should worry about.

Block failures can come from a variety of sources including memory errors, which you have no control over. This is why servers typically use ECC RAM.
4
General Discussion / Files randomly left behind on Landing Disk
« Last post by jitdor on September 21, 2017, 12:05:46 pm »
I have a 7-disk configuration on tRAID that has been running for a few years, with a 128GB SSD formatted as a single ReFS partition being used solely as a landing disk.

Of late, I notice the landing disk buffer gets filled up very quickly, so I took a peek into the drive and noticed that the available storage is 50-60GB less. I make sure the landing disk is not in use before I took ownership of the hidden folders trying to find out what's hogging the space. To my surprise, there are a few old files being left over on the landing disk, which had already been copied to the array long ago. I am not able to find any pattern because it happens rather randomly - the files that are left behind have different creation dates and during the same period there are many other files of the same type and size which got transferred to the array and removed from the landing disk.

There is no implication to data integrity (so far) and the verify tasks always turn out to be successful. If anything the only compliant is that I need to check the available space on the landing disk regularly.

If anyone has any suggestions on why this occurred, I'd be happy to investigate further. Thanks!
5
General Discussion / Re: Restore of Drive
« Last post by asian on September 20, 2017, 02:36:28 pm »
Thank you for all that assisted working now
6
General Discussion / Re: Need Help with Transferring license to different computer
« Last post by cogliostrio on September 20, 2017, 11:06:53 am »
If you read the link I posted earlier, you must realize you have answered your own question.

Its a completely different system

Quote from: Licensing: hardware changes and license transfer
for cases where key components in the computer are upgraded (motherboard + CPU – essentially you just have a new computer in the old case), the computer will be deemed to be a new computer.
7
General Discussion / How To Pool External USB Drives?
« Last post by Z0m8ie on September 20, 2017, 03:48:06 am »
Hi, I was wondering is it possible to pool USB2 and USB3 External Hard Drives using FlexRaid?
8
General Discussion / Restore of Drive
« Last post by asian on September 19, 2017, 11:42:24 pm »
Can someone be so kind and point me in the right direction to restore a drive on raid-f

I cannot find the link to the wiki or support file.

9
General Discussion / Re: Error code on verify
« Last post by Tiger666 on September 19, 2017, 03:26:04 pm »
Thanks Brahim

Here's the output

Verify RAID [tRAID] started at Tue Sep 19 18:55:12 GMT+1000 2017

Name: Verify RAID [tRAID]
Start Date: Tue Sep 19 18:55:12 GMT+1000 2017
End Date: Tue Sep 19 18:55:57 GMT+1000 2017
Duration: 00:00:45
Throughput: 248.401GB/s
Total Size: 10.916TB

Error Code = 999999999
1 stripe blocks failure
First byte failure at 3203788800
Last byte failure at 3203792896
Operation aborted!
Failed UoR position = 2
Failed UoR ID = 1000000024
Verify RAID [tRAID] ended at Tue Sep 19 18:55:57 GMT+1000 2017

It was just a 'verify' task. My question really is - is any block failure to be expected on a new storage pool (in terms of both hardware and creation). If so, then how often should Verify & Sync be run?
10
General Discussion / Re: Error code on verify
« Last post by Brahim on September 19, 2017, 08:57:59 am »
I get a similar error on a new set of disks after initial build. While I know it's not out of the realm that a disk has a problem no smart indication of issue.

Is this expected? Or should a freshly created / sync'd storage pool return zero bad blocks?
You should post the exact error you are getting. A "similar" answer will likely not do any good to your specific issue.

Negative error codes are Windows error codes: https://msdn.microsoft.com/en-us/library/windows/desktop/ms681382(v=vs.85).aspx
A positive code (Error Code = 999999999) is a parity generic code. It simply means that the parity is out of sync with the data. You should therefore run the Verify & Sync task.
Pages: [1] 2 3 ... 10