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 - Jerremy

Pages: [1] 2 3
General Discussion / Re: Am I restoring incorrectly??? Files lost :(
« on: October 06, 2017, 02:54:09 am »
Edit: The 'write protection errors' or the other errors when trying to move the file seemed to be due to the source drive being corrupted.

General Discussion / Re: Am I restoring incorrectly??? Files lost :(
« on: October 05, 2017, 06:55:55 am »
I did a chkdsk on all DRU's (by giving them a drive letter in storage manager) and they were all fine. No idea what happened here.

The drive that crashed is still a bit accessible with a USB docking station so I'm moving back files.

Strangely enough, some of the files are generating an "Access Denied" when I try to 'create' (move) them to the array.

Looking with procmon, it seems that IRP_MJ_FILE_SYSTEM_CONTROL is returning "INVALID DEVICE REQUEST". See attached screenshot of all operations for a file that is failing.

I'm currently running a verify + sync and after that I'll reboot the system. See if it fixes anything.

General Discussion / Re: Am I restoring incorrectly??? Files lost :(
« on: September 29, 2017, 06:34:25 am »
It didn't find any problems with the file system. I'm clueless as to what happend. The logs don't really seem to say much either.

General Discussion / Re: Am I restoring incorrectly??? Files lost :(
« on: September 29, 2017, 06:31:30 am »
I first tried online mode, but it failed horribly (it kept saying "Performing action" or something similar). I had to reboot the system and after that I performed the action in offline mode and it worked.

I will see if running scandisk or something on the drive fixes anything.

General Discussion / Am I restoring incorrectly??? Files lost :(
« on: September 28, 2017, 07:56:59 am »
So I lost a drive a few days ago. The drive dropped from the array.

I then performed the following steps:

  • Added a new drive to the system (I have bays free)
  • Had to reboot the system to see the drive
  • Went to the Web UI and selected the dropped drive
  • Pressed 'Restore' (array was online)
  • Web UI got stuck in "Performing action" and after a day I rebooted the system  :(
  • Storage pool didn't start (no idea why)
  • Decided to stop the raid array, had to reboot (again) because OS caching was enabled
  • I selected the dropped drive again and pressed 'Restore' again, this time the system started the restore process
  • After a day the raid said to me "restore successful"

Now the not-so-fun part, I'm not sure what failed in the above sequence (other than the web ui getting stuck at performing action), but all files that are on the dropped drive are no longer available. Hopefully I will be able to restore a lot of them from the broken drive. But I think I might have to accept that they are gone.

This is the second time this happend. The first time I thought I did the steps incorrectly, but this is not exactly rocket science. It's not like there's 10 buttons with "restore".

The logs don't seem to mention anything when I search for one of the specific directory names. I did just solve one issue with a failed update, but not sure if this is directly related. I'll keep an eye on it for the next few days.

No, the universal bin is not enabled on my system. Not sure if I want that either.

Windows likes to put it's temporary directories (for updates) on the drive with the most amount of free diskspace. Which of course is the flexraid array.

However, for some reason the (empty) directories are not being deleted properly. So every so often I end up with 10's (I've had above 100 once) empty random-name directories.

Is this a known issue? Anything that can be done about it?

General Discussion / Faulting application name: NZFSB.exe, version:
« on: February 02, 2017, 05:45:02 am »
Faulting application name: NZFSB.exe, version:, time stamp: 0x56407513
Faulting module name: NZFSB.exe, version:, time stamp: 0x56407513
Exception code: 0xc00000fd
Fault offset: 0x000e2e67
Faulting process id: 0x860
Faulting application start time: 0x01d27080b442311b
Faulting application path: C:\Downloads\TRAID\NZFS-TRAID-HOST\common\NZFSB.exe
Faulting module path: C:\Downloads\TRAID\NZFS-TRAID-HOST\common\NZFSB.exe
Report Id: e7e57db2-e8e3-11e6-811d-d8cb8a3dce40
Faulting package full name:
Faulting package-relative application ID:

After this, the drive (of course) was no longer accessable.

The last lines in the FlexRAID.nzfs.log were:
[2017-02-02 02:06:49.082949][12000][OnReadFile]:[\Multimedia\HD-Movies\Braveheart.mkv] error=1450, offset=0 requested=4096
[2017-02-02 02:06:49.093972][11408]      pReadUpToByHandle error for handle=1244, errorCode=1450, offset=0, requested=4096, read=0

[2017-02-02 02:06:49.093972][11408][OnReadFile]:[\Multimedia\HD-Movies\Braveheart.mkv] error=1450, offset=0 requested=4096
[2017-02-02 02:06:49.104995][11408]      pReadUpToByHandle error for handle=1244, errorCode=1450, offset=0, requested=4096, read=0

[2017-02-02 02:06:49.104995][11408][OnReadFile]:[\Multimedia\HD-Movies\Braveheart.mkv] error=1450, offset=0 requested=4096
[2017-02-02 02:06:49.115018][11304]      pReadUpToByHandle error for handle=1244, errorCode=1450, offset=0, requested=4096, read=0

[2017-02-02 02:06:49.115018][11304][OnReadFile]:[\Multimedia\HD-Movies\Braveheart.mkv] error=1450, offset=0 requested=4096
[2017-02-02 02:06:49.126041][12100]      pReadUpToByHandle error for handle=1244, errorCode=1450, offset=0, requested=4096, read=0

[2017-02-02 02:06:49.126041][12100][OnReadFile]:[\Multimedia\HD-Movies\Braveheart.mkv] error=1450, offset=0 requested=4096
[2017-02-02 02:06:49.137064][12100]      pReadUpToByHandle error for handle=1244, errorCode=1450, offset=0, requested=4096, read=0

[2017-02-02 02:06:49.137064][12100][OnReadFile]:[\Multimedia\HD-Movies\Braveheart.mkv] error=1450, offset=0 requested=4096

Whats up? :)

General Discussion / Is this product dead?
« on: January 04, 2017, 02:57:45 am »
I see a few posts from Brahim today (after a long period of almost nothing). But is this software actively maintained/developed/supported or not?

Lets be honest, its not exactly bug free (a simple example is the "ErrorCode=31 ErrorMessage=A device attached to the system is not functioning" message on raid monitoring page, see for more). Also looking at general discussions you see discussions which could use some followup from Brahim, some examples:,49137.0.html,49125.0.html,49121.0.html,49145.0.html

Just wondering if we can see improvement in support, or if I should start looking at running something other than FlexRAID.

Regards, Jerremy

General Discussion / Intermittent write issues to the array
« on: November 15, 2016, 03:02:34 pm »
Every so often I get a write protection error on the array. Just before this happens all disk access pretty much freezes and it results in a write protection error. It happens more frequently if I overwrite an existing file on the array, but sometimes on a new file too.

I'm not entirely sure if it's a tRAID issue or a controller issue. Because this generates no errors anywhere (not in the NZFS logs and not in the windows event viewer). But the operation fails.

Usually I use Total Commander to copy/move files, but I've seen this behavior with Windows Explorer too. Windows 2012R2, latest release tRAID (from 2015 I think) and HighPoint RR2760A controller with latest drivers and firmware.

Is there any way to debug this, find out if its a drive issue, controller issue or tRAID issue?

General Discussion / Verify failed - which DRU?
« on: October 31, 2016, 03:07:39 am »
I got this error:
Verify RAID [tRAID] started at Mon Oct 31 01:00:00 GMT+100 2016

Name: Verify RAID [tRAID]
Start Date: Mon Oct 31 01:00:00 GMT+100 2016
End Date: Mon Oct 31 01:40:03 GMT+100 2016
Duration: 00:40:03
Throughput: 852.268MB/s
Total Size: 1.953TB

Error Code = 999999999

1 stripe blocks failure

First byte failure at 831363343360

Last byte failure at 831363355136

Operation aborted!

Failed UoR position = 20

Failed UoR ID = 1000000005

Verify RAID [tRAID] ended at Mon Oct 31 01:40:03 GMT+100 2016

How can I find out which drive failed? Because I'm assuming a drive failed.
(it's not DRU20 because DRU20 is a placeholder in the array configuration)

tRAID Feature Requests / Add more drive details to the SMART warnings
« on: September 02, 2016, 04:07:03 am »
I have a drive giving this message:
Negative changes for TOSHIBA DT01ACA300 SCSI Disk Device: Read Error Rate(previous=100 now=95)

To find out which drive it is, I have to go through all 9 of them. Not very convenient.

It would be very nice to add more information in the email. At the very least the serial number of the drive.

Although technically tRAID doesn't know about files, the drive pool that manages the array does. It would be great if a feature was added that would move files off a disk that has been marked as "damaged". Or at least duplicate the files to another drive.

Would be nice to have :)

I never brought the array back online, this was all done offline. Maybe I copied the wrong log part (at some point I just started to smack every button to see what it would do). It gave the same error (RegisteredDisk) exception on all requests. I'll add all logs.

I ended up deleting the configuration and rebuilding it without the dropped drive. After a reboot that drive comes online again (until I find a file which is completely corrupted, two so far), the controller will then drop the drive again until a reboot. So I'm getting most of my files back (copying can be slow if there's a lot of read errors).

Pages: [1] 2 3