Jump to content
Division-M Community
Stacy

Desperately Need help and ticket is not being answered.

Recommended Posts

I have a 60TB pool for a client and am struggling with it it since what I think was Folderwall in version 3.200a messed it all up.  I have a ticket in with Anthony but he has not answered any of my questions in 2 days.. so I am not sure if Divisions is shut down for holidays or what is happening. Totally unlike Anthony to not answer my questions.  I am quite Desperate for some help so posting here in the hopes that someone has some insight.

I wont spell out the entire ticket but the revolving issue is event viewer keeps popping up with these:

Warnings:

The IO Operation at logical block  address 0x21 for Disk 11 (PDO name: \Device\0000004d) was retired.
The IO Operation at logical block  address 0x11 for Disk 11 (PDO name: \Device\0000004d) was retired.
The IO Operation at logical block  address 0x01 for Disk 11 (PDO name: \Device\0000004d) was retired.

The File System Structure on Volume C:\Program Files\Division-M\Drivebender\System\Mounts\{B941F5A3-8C64-425D-A2AD-71B7ED808C11} has now been repaired. (4 times)

Disk 11 is the actual pool

Errors:

Volume C:\Program Files\Division-M\Drive Bender\System\Mounts\{B941F5A3-8C64-425D-A2AD-71B7ED808C11} (\Device\HarddiskVolume16) needs to be taken offline to perform a Full Chkdsk.  Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell.

The file system structure on volume C:\Program Files\Division-M\Drive Bender\System\Mounts\{B941F5A3-8C64-425D-A2AD-71B7ED808C11} cannot be corrected.
Please run the chkdsk utility on the volume C:\Program Files\Division-M\Drive Bender\System\Mounts\{B941F5A3-8C64-425D-A2AD-71B7ED808C11}.

A corruption was discovered in the file system structure on volume C:\Program Files\Division-M\Drive Bender\System\Mounts\{B941F5A3-8C64-425D-A2AD-71B7ED808C11}.

The file system structure on volume C:\Program Files\Division-M\Drive Bender\System\Mounts\{B941F5A3-8C64-425D-A2AD-71B7ED808C11} cannot be corrected.
Please run the chkdsk utility on the volume C:\Program Files\Division-M\Drive Bender\System\Mounts\{B941F5A3-8C64-425D-A2AD-71B7ED808C11}.

A corruption was discovered in the file system structure on volume C:\Program Files\Division-M\Drive Bender\System\Mounts\{B941F5A3-8C64-425D-A2AD-71B7ED808C11}.

And this one which actually restarted the server:

The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000001a (0x0000000000005200, 0xffff83849d254000, 0x364c26344a233148, 0xd933bca0ea82e464). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 7206ce76-60c8-40d3-b33c-2fcbb2b9817f.

 

I have taken each drive in the Pool and have mapped it to a drive letter and have ran Check the Drive with  Correct any errors found check marked on each drive until they came back with no errors.

Also to note:

C:\Program Files\Division-M\Drive Bender\System\Mounts\{B941F5A3-8C64-425D-A2AD-71B7ED808C11} - This folder does not exist at this path

Yesterday I cleaned up all the Folders.00X on each drive 1 at a time and deleted the recycle bin which was reported as corrupt.  Then set Drive bender to perform a Pool Health Check and overnight the system crashed and produced all the information above.

I am at a lose how to fix this issue and the only thing I can think to do is it create a new Pool with new Hard Drives in the same machine and migrate the data to it ?

Anyone got any suggestions or direction that can help ?

 

Thank much and Merry Christmas,

 

Stacy

 

 

 

 

 

 

 

 

 

Share this post


Link to post
Share on other sites

Hi Stacy,

I'm responding as best as I can... however, we are located in Australia (it was 2AM here when you posted this) and we can't spend 24 hours a day monitoring support, not to mention, you are not the only customer we have.

Here are some support tips.
1) First of all, don't panic! (this is important)... remember, all files are stores using the Windows NTFS format, and can be access outside of Drive Bender if needed.
2) When submitting a ticket, wait for a responses before spamming support, ever time you update a ticket, it goes to the back of the support queue as tickets are sorted by "last updated", oldest first.
3) Try and keep tickets on topic, adding unrelated issues confuses things and can make it difficult to track what is going on.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...