D5-300 disk corrupt on reboot

[randyf]

Hi I have a D5-300 and put new 8TB disks from the compatibility list in, and when I first tried to initialize in Disk Manager it took a verrry long time and eventually failed. I restarted the computer and tried again and had to fight with it several times to get it to work.

Now, I've created a RADI5, which is ok in RAID Manager, but if I disconnect the device or restart the computer, the entire volume becomes corrupt. I have copied about 10TB to it just fine when it was running, but then if I unplug and replug the device, it's all gone and says the drive is corrupt. Any help here? It's all brand new.

[RyanYang]

You can contact our technical support team for remote inspection.

[mrslother]

I have a similar problem. Win Server 2022 using D5-300C.
5 disk RAID 5 with ~12Tb usable space
Was working well for several weeks.
Rebooted the other day, drive shows up uninitialized, no partitions. Device Manager shows as "TDAS RAID5 SUB Device".
Attempts to run Raid Manager app results in crash. From EventLog:

Code: Select all

Faulting application name: RAID Manager.exe, version: 2.1.9.0, time stamp: 0x6035bc38
Faulting module name: raidapi.dll, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000055e6
Faulting process id: 0x2c50
Faulting application start time: 0x01d9af7d9a38c6bb
Faulting application path: C:\Program Files (x86)\TerraMaster\RAID Manager\RAID Manager.exe
Faulting module path: C:\Program Files (x86)\TerraMaster\RAID Manager\raidapi.dll
Report Id: 32572b0f-19dd-4243-a46a-1b951abed8a0
Faulting package full name: 
Faulting package-relative application ID: 

WER Report Event Log Entry:

Code: Select all

Fault bucket 1932370577096057648, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: RAID Manager.exe
P2: 2.1.9.0
P3: 6035bc38
P4: raidapi.dll
P5: 0.0.0.0
P6: 00000000
P7: c0000005
P8: 000055e6
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.9fb06a22-1409-4bd1-b773-0d9f94c7e9f4.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.a38feff6-8905-43ec-be73-86ec43759dcc.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.855cd2a6-7265-44de-8f77-38070260258e.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.fec6699c-8223-4e85-8fd5-2e70f24eb13c.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.b1198a88-d62c-4098-a632-ed088b8c3e22.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_RAID Manager.exe_86ad7b44ccdef2be673908ed8751ecd86d5ac1_5f098c84_eca936a6-d457-4542-a5ca-e61b8c6444ba

Analysis symbol: 
Rechecking for solution: 0
Report Id: 32572b0f-19dd-4243-a46a-1b951abed8a0
Report Status: 268435456
Hashed bucket: 70e261860bf7a0c95ad128cd3e3a2330
Cab Guid: 0

[TMzethar]

{L_BUTTON_AT}mrslother

Your model is different from the topic's model. You can open a topic for your peoblem alone. Or post under the corresponding topic.

[mrslother]

My apologies. The model is D5-300 (not the D5-300C I previously wrote).

It ends up that I discovered the issue. Somehow, through magic, the USB bus drivers had changed on the machine (I dunno, maybe a Windows Update?) Once I reinstalled them the RAID Manager.exe started working again. I had lost all of my data on the disk, but at least I can recreate everything.