Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Brahim

Pages: [1] 2 3 ... 511
Below is attached the logfile for the last several days, which includes a few days before and after the restore attempt.

Or did you mean a different log file?

Code: [Select]
[2017-05-10 00:01:08,698] INFO : DRU1 size=1820830639055
[2017-05-10 00:01:08,698] INFO : DRU2 size=1958307109991
[2017-05-10 00:01:08,698] INFO : DRU3 size=1942245718189
[2017-05-10 00:01:08,698] INFO : DRU4 size=0
[2017-05-10 00:01:08,698] INFO : DRU5 size=1897133370502
[2017-05-10 00:01:08,698] INFO : DRU6 size=1851705862189
[2017-05-10 00:01:08,698] INFO : DRU7 size=1898970042381
[2017-05-10 00:01:08,698] INFO : DRU8 size=1666056797912
These logs show DRU 4 with a size of 0, which means it was empty. Do you have previous logs that show it with a different size?

tRAID on Windows / Re: Does tRAID for Windows require SMB 1.0?
« on: May 18, 2017, 05:50:11 pm »
Networking to a tRAID volume is governed by your OS. So, tRAID does not have any dependency on the version of SMB.

Please post the full logs.
Details on what the Update task did are important.

Storage Pooling / Re: Cannot Create Files/Folders in New Pool
« on: May 17, 2017, 01:17:51 pm »
Yeah, I would say create a pool with a single share first and make sure it works the way you wish before adding others.
Then focus of addressing the permission issues of each of the target shares.

Storage Pooling / Re: Cannot Create Files/Folders in New Pool
« on: May 17, 2017, 07:03:19 am »
Which one is DRU1?

Workgroup sharing is more tricky. Operations that need file ownership will typically fail, which is what I think might be happening in your case.

Storage Pooling / Re: Cannot Create Files/Folders in New Pool
« on: May 16, 2017, 10:39:53 pm »
Is this domain based or workgroup based networking?
Which OS on each of the shares?

Storage Pooling / Re: Cannot Create Files/Folders in New Pool
« on: May 16, 2017, 05:00:36 pm »
Check the permissions on the shares and those of the drives hosting the shares. The NTFS permissions on those drives might be restrictive as to block the share permissions.

Gallery / Re: FlexRaid-F Home Server
« on: May 16, 2017, 04:58:46 pm »
Nice. :)

What case is that?

tRAID Bug Reports / Re: Notifications for dropped drives?
« on: May 15, 2017, 06:07:43 pm »
If you have email or SMS configured, you will be notified via those mediums when a disk drops.
Note that the Web UI must be running for that to take place.

tRAID Bug Reports / Re: Scheduled Jobs not working
« on: May 15, 2017, 05:59:19 pm »
Thanks for the report. I will look into it.

Storage Pooling / Re: Cannot Create Files/Folders in New Pool
« on: May 15, 2017, 05:58:15 pm »

Make sure the FlexRAID service is running under a user that has proper permissions to all the shares you are trying to pool.

General Discussion / Re: Hpyer V - VHDX Files using with flexraid
« on: May 15, 2017, 05:53:51 pm »
Snapshot RAID is for static or semi-static files. For dynamic files, please use tRAID.

The totals reported are correct. Each task reports its own processing size, which does not have to correlate with the array or pool size.
Make sure to comply with the restart requirements.

General Discussion / Re: Folder re-appears after deletion (SOLVED)
« on: May 05, 2017, 01:24:47 pm »
Disabling meta-data and rebooting took care of the problem.  I then enabled meta-data again and everything is working fine - the folder did not reappear.
Hum... interesting. Where the tRAID disks mounted at any point?

1. The health of your data disks is unaffected whether positively or negatively. Only parity is affected by the Sync portion of the Verify & Sync task. The Verify/Verify+ tasks affect neither.

2. The power is all yours. That is, tRAID includes a forensic plugin (
In practice, you would run the Verify+ task (not the Verify nor the Verify & Sync, only the Verify+), and then use the forensic plugin to analyze potentially affected data in case of bit mismatch.
Here, you have the ability to analyze and decide which of the data or parity is wrong. A bit mismatch could be due to bad parity or bad data that is benign. In the case of either bad parity or benign data, you would just Sync with the Verify & Sync on the affected range. In the case of bad data that is severe, you could recover from backup or from parity by failing the relevant disk (read about the override feature here:

Pages: [1] 2 3 ... 511