Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
General Discussion / Re: Files randomly left behind on Landing Disk
« Last post by Brahim on May 29, 2018, 03:19:13 pm »
Nothing logical can be done if a file is locked or has a duplicate in the pool. There is a consistent attempt to move the files. However, if the conditions preventing it persist, so will the issue.

What would you see happen in the case of duplicate file name? Discard one file in favor of the other? Which one?

Is the case of locks, you might need to restart the system for the lock to be released. There are also 3rd party tools to forcefully unlock files that you could look into to avoid having to restart.
22
General Discussion / Re: tRaid suddenly stopped working on windows server 2016
« Last post by Brahim on May 29, 2018, 03:14:40 pm »
Disk "ST3000DM001-1E6166 ATA Device" might not be healthy.
It looks like it might have failed. Are you able to see it in the Windows disk manager? Are you able to run SMART on it?

Transparent RAID won't flag a disk as failed until write operations affecting that disk fail. This is for flexibility.
Disk health management is done through the SMART monitoring feature. So, use SMART to check on the health of that disk.
23
I can also add that by going back to the previous windows build (1709) using the recovery feature instantly fixed everything.

I really think there's something going on between flexraid transparent raid and that new windows 10 build.

Fyi my installed versions are as follows:



Transparent RAID - Home & Small Business License

OS: Microsoft Professional (build 9200), 64-bit
Broker: 1.1.0 2017.11.22
Kernel: 1.1.0 2017.11.22

Thanks again.

24
Hello there Brahim,
after updating to windows 10 build 1803 flexraid transparent raid does not start anymore the array, giving a bsod.

Here's the minidup analysis. Hope you can help.

Thanks

Code: [Select]
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 17134 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff802`8f011000 PsLoadedModuleList = 0xfffff802`8f3ce1d0
Debug session time: Tue May 29 07:34:10.853 2018 (UTC - 4:00)
System Uptime: 0 days 0:03:31.549
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffcf8909a9e658, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80af66fb5a4, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 000000000000000c, (reserved)

Debugging Details:
------------------


Could not read faulting driver name
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

OVERLAPPED_MODULE: Address regions for 'srvnet' and 'dump_storpor' overlap

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 ffffcf8909a9e658

FAULTING_IP:
NZFSD+2b5a4
fffff80a`f66fb5a4 3bb808030000    cmp     edi,dword ptr [rax+308h]

MM_INTERNAL_CODE:  c

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  AV

PROCESS_NAME:  System

CURRENT_IRQL:  1

TRAP_FRAME:  fffffe87f91a3990 -- (.trap 0xfffffe87f91a3990)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffcf8909a9e350 rbx=0000000000000000 rcx=0000000000000001
rdx=ffffcf8910f7e1f0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80af66fb5a4 rsp=fffffe87f91a3b20 rbp=000000003b9aca04
 r8=fffffe87f91a3b00  r9=0000000000000000 r10=ffffbe01844b79e0
r11=ffffcf890fa5b050 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
NZFSD+0x2b5a4:
fffff80a`f66fb5a4 3bb808030000    cmp     edi,dword ptr [rax+308h] ds:ffffcf89`09a9e658=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8028f1ecd39 to fffff8028f1a8670

STACK_TEXT: 
fffffe87`f91a36d8 fffff802`8f1ecd39 : 00000000`00000050 ffffcf89`09a9e658 00000000`00000000 fffffe87`f91a3990 : nt!KeBugCheckEx
fffffe87`f91a36e0 fffff802`8f0826d8 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffb8dc`6e371b88 : nt!MiSystemFault+0x16eb89
fffffe87`f91a3820 fffff802`8f1b79c7 : 00000000`00000000 00000000`000001d4 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x1f8
fffffe87`f91a3990 fffff80a`f66fb5a4 : ffffcf89`14937700 ffffcf89`14937a20 ffffcf89`0fa5b0e0 ffffcf89`1064a2c0 : nt!KiPageFault+0x3c7
fffffe87`f91a3b20 ffffcf89`14937700 : ffffcf89`14937a20 ffffcf89`0fa5b0e0 ffffcf89`1064a2c0 00000000`00000000 : NZFSD+0x2b5a4
fffffe87`f91a3b28 ffffcf89`14937a20 : ffffcf89`0fa5b0e0 ffffcf89`1064a2c0 00000000`00000000 00000000`00000080 : 0xffffcf89`14937700
fffffe87`f91a3b30 ffffcf89`0fa5b0e0 : ffffcf89`1064a2c0 00000000`00000000 00000000`00000080 ffffcf89`0fbbcc60 : 0xffffcf89`14937a20
fffffe87`f91a3b38 ffffcf89`1064a2c0 : 00000000`00000000 00000000`00000080 ffffcf89`0fbbcc60 fffff80a`f66f942f : 0xffffcf89`0fa5b0e0
fffffe87`f91a3b40 00000000`00000000 : 00000000`00000080 ffffcf89`0fbbcc60 fffff80a`f66f942f ffffcf89`0fa5b050 : 0xffffcf89`1064a2c0


STACK_COMMAND:  kb

FOLLOWUP_IP:
NZFSD+2b5a4
fffff80a`f66fb5a4 3bb808030000    cmp     edi,dword ptr [rax+308h]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  NZFSD+2b5a4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NZFSD

IMAGE_NAME:  NZFSD.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5a15a5da

FAILURE_BUCKET_ID:  X64_AV_NZFSD+2b5a4

BUCKET_ID:  X64_AV_NZFSD+2b5a4

Followup: MachineOwner
---------
25
tRAID on Windows / Anyone upgraded to Windows 10 build 1803?
« Last post by astuni on May 29, 2018, 12:44:33 am »
Unfortunately the system forced the update past night and today I get a bsod while trying to start the array.

I’ve already tried to uninstall and reinstall transparent raid without success.
May I send you something like the mini dump to try to find a reason?


Inviato dal mio iPhone utilizzando Tapatalk
26
General Discussion / Re: Response From Sales?
« Last post by Haldanite on May 28, 2018, 02:49:11 pm »
Thanks.  I love the product as well.  I started using it 4 years ago and have loved it since.  I'll hang tight and wait for a response.
27
General Discussion / Re: Response From Sales?
« Last post by efishta on May 27, 2018, 06:07:03 pm »
I ran into a similar issue a couple of years ago. There's not much you can do but wait for "customer service" to respond at their whim. Brahim, lead developer (or only developer?), has a regular tendency to disappear for months at a time, so don't expect direct developer feedback. Best thing you can hope for is continuing to renew the trial license and hope someone will get back to you. Bug fixes happen at the developer's whim, not any regular or scheduled periods.

Not talking smack, I love this product, as I'm still using it, I just wish there was any level of care for this product beyond initial release.
28
General Discussion / Re: Files randomly left behind on Landing Disk
« Last post by efishta on May 27, 2018, 06:01:23 pm »
Is there a resolution to this, perhaps via a new version that might try more aggressively to move the files off the landing disk at future times?

Or perhaps a feature that serves as an indicator as to which files are locked/not moved and reason why?

As is, it's poorly implemented. There should be consistent attempts to move these files given changing circumstances in file locks and warnings available, not having to look at free space and change security settings to explore stuck files in the landing disk.
29
General Discussion / Response From Sales?
« Last post by Haldanite on May 26, 2018, 10:37:35 am »
I had to replace my motherboard and along with it my CPU and RAM.  I reinstalled the hard drives used in my Transparent RAID, but I can't activate my license.  I've been waiting on someone to respond from the sales email for almost 2 weeks (multiple emails sent) since the system fails to transfer my license.  I have all the same drives from my raid installed and I'm using the trial license, but I would really rather be using the license I paid for.  Anyone have suggestions on how to get my license transferred or any idea when I might expect to hear back on my emails?
30
Hi,

No software has been installed, this is my home server than runs headless as a media server, cant find anything in event viewer, going back through all the logs, it looks like something happened at 1:17, then when trying to access it had no luck starting the array

[2018-04-20 01:16:22,599] INFO  start(56) - Setting Http port to 8080
[2018-04-20 01:16:23,080] INFO  start(56) - Https port not set. Https requests will not be serviced...
[2018-04-20 01:16:30,516] INFO  init(248) - Build date: 2017.11.22
[2018-04-20 01:16:30,796] INFO  init(248) - Session UUID: dd478ee4-4e9f-4fff-a1cc-743f30d28679
[2018-04-20 01:16:33,686] WARN  init(248) - Client connection not found for host=1!
[2018-04-20 01:17:15,798] WARN  run(41) - One or more configuration changes have been made to your system. You must restart your system for the changes to take effect. <br/><b>Do not attempt to start and use the array until you have rebooted!</b>
[2018-04-20 08:41:55,542] WARN  startStoragePool(757) - Cannot find Disk Info for ST3000DM001-1E6166 ATA Device
[2018-04-20 08:41:55,828] WARN  startStoragePool(757) -     ID=1
[2018-04-20 08:41:55,828] WARN  startStoragePool(757) -     Key=nzfs--795742405923420985--7452503252210072718

lists the same for all the hard drives in the system, then with every reboot I did that day trying to get it working just lists

[2018-04-20 08:50:47,407] WARN  init(248) - Client connection not found for host=1!
[2018-04-20 08:51:29,520] WARN  run(41) - One or more configuration changes have been made to your system. You must restart your system for the changes to take effect. <br/><b>Do not attempt to start and use the array until you have rebooted!</b>
[2018-04-20 08:57:49,700] WARN  getDiskInfos(757) - ErrorCode=21 ErrorMessage=The device is not ready.
[2018-04-20 08:58:13,566] WARN  getDiskInfos(757) - ErrorCode=21 ErrorMessage=The device is not ready.
[2018-04-20 08:58:16,686] WARN  getDiskInfos(757) - ErrorCode=21 ErrorMessage=The device is not ready.
[2018-04-20 08:58:16,686] WARN  startStoragePool(757) - Cannot find Disk Info for ST3000DM001-1E6166 ATA Device
[2018-04-20 08:58:16,686] WARN  startStoragePool(757) -     ID=1
[2018-04-20 08:58:16,686] WARN  startStoragePool(757) -     Key=nzfs--795742405923420985--7452503252210072718

after trying to uninstall/reinstall and various reboots the log now just states

[2018-04-23 13:43:31,593] WARN  run(41) - The storage pool cannot be started as there is no mounted volume to pool!
[2018-04-23 14:39:23,021] WARN  getDiskInfos(757) - ErrorCode=21 ErrorMessage=The device is not ready.
[2018-04-23 14:39:26,402] WARN  getDiskInfos(757) - ErrorCode=21 ErrorMessage=The device is not ready.

the only thing I can find that would have been installed around that date was these updates that installed on the 18th, maybe a delayed reboot?

Windows Malicious Software Removal Tool x64 - April 2018 (KB890830)
2018-04 Update for Windows Server 2016 for x64-based Systems (KB4093137)
2018-04 Cumulative Update for Windows Server 2016 for x64-based Systems (KB4093119)

Any ideas ?

Thanks
Matt
Pages: 1 2 [3] 4 5 ... 10