Raid Expansion after Migration /Snapshot Issue

[Pellicle]

Just checking on whether there is a fix for the issue caused by when the extra space allocated to snapshot during a Raid 5 to Raid 5 migration when adding additional drives?

Process followed:
Add additional drive
Manually add as spare
Migrate R5 to R5
After migration drive added to array but space allocated to Snapshot.
Expand gives "Not enough space to expand error"
Space Allocation web page allows USB but not Snapshot reallocation of space.

This seems to be a common problem which should be handled in the web interface.
Thecus - Is there a fix for this issue???

[fred7]

I think that I am having the same problem. I migrated a 3-750GB disk raid 5 to a 4-750Gb raid 5 and I cannot expand. My Total Capacity show 2090.5 but my Data capicity is shown as 1281.4 When I try to expand I get the message 'RAID space not enought to expand!!' I am assuming that the missing space was allocated to snapshot - how can I check? I just updated to the latest firmware and that didn't help. Is there going to be a fix for this soon?

[Thecus - Yvon]

Dear Sir,

If we can't execute the Raid Expansion or Migration with snapshot, please mail to support@thecus.com and we will help you to remove the snapshot and make Raid Expansion or Migration working.

Yvon.

[Pellicle]

Yvon,
Thank you for your reply. I have sent an email to the address you supplied detailing the issue.
Regards,

[Thecus - Yvon]

Dear Sir,

We get your mail already, current we are parpare some patch for user to unlock the snapshot, we will reply to you in ASAP, since we complete the patch.

Yvon.

[jordi.c]

Hi Yvon,

Will this patch included in the next firmware?

Because I'm thinking of waiting migrating my RAID5 4x to RAID 5x.

Current FW: V2.00.01

Edit:

Thank you Andreas.

The German Thecus support told me, that a bug fix will be available in FW 2.00.03 at the beginning of October.

Igor

I know enough let's wait until October

[Pellicle]

Dear Sir,

We get your mail already, current we are parpare some patch for user to unlock the snapshot, we will reply to you in ASAP, since we complete the patch.

Yvon.

Yvon,

Any updatre on when the patch will be complete?

Regards,

[Thecus - Yvon]

Dear Pellicle,

Current we would fix this function via new version, if need remove he snapshot imminently, please mail to support@thecus.com and we would remove the snapshot by manually.

Yvon.

[Pellicle]

Yvon, I have emailed support but have not had a response. I am now running low on disk capacity and urgently need a fix. Could you please help?
Thanks,

[Thecus - Yvon]

Dear Sir,

Current we would fix this function via new version, thus we have no patch to release, if need the help in this period, please provide an IP address to support@thecus.com for us doing this remotely.


Following three ways to publish the NAS on the internet for your reference:

1.
Public Fixed IP (most easy)
Just assign a public fixed IP on the NAS WAN/LAN1 port

2.
DMZ (easy)
Enable Router DMZ function and fill in NAS WAN/LAN1 private IP in the Router DMZ column, and then tell me the Router WAN IP.
For Example:
Router WAN IP is 139.175.55.244
NAS WAN/LAN1 IP is 192.168.1.100
Enable Router DMZ function and fill in 192.168.1.100 for DMZ, thus the Router will forward all connection of 139.175.55.244 from internet to NAS WAN/LAN1 IP 192.168.1.100, than I could access to the NAS.

3.
Virtual Server (port forward) (a little difficult)
Assign port 21/22/80 and 443 forward to NAS private IP, following case study about port 443 for your reference: Thecus About Storage.

Yvon.

[Pellicle]

Yvon,
I have sent the suggested info to the email address supplied. I used option 3.
Thanks,