New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
ping... traceroute...etc etc pls
Hi,
Thank you for opening this thread. You should get email by now to notify you about current problem.
Here is what happened:
Storage array suffered disk loss (metadata corruption of 0.03 %) and all VMs entered into read only mode.
Currently we are rebuilding array, It will take some time.
Expected realistic downtime 12-14 hours.
If you cannot wait that time we can provide full refund upon request.
We will also try to use this downtime to add 2 ssd drives into array so after this fix service should be ssd cached.
I am deeply sorry for all inconvenience that we have caused.
Thank you
hi drserver,
for me it is just fine, no problem.
but i could not find infos on the drserver.net.
Thanks
Update about the current issues can be found here https://drserver.net/drbill/
Current status:
[==>..................] resync = 11.6% (340955264/2916644352) finish=584.4min speed=73444K/sec
I feel with you, RAID array rebuilds are painful!
I saw my box go read-only earlier and wondered what was up. Glad to see you're on it, and am excited about the SSD caching.. disk i/o has been rough at times. Lots of recent signups and everyone loading up their data = sloooow.
I am really sorry guys but we can only wait. After this we will rebuild meta data and all should be ok.
Thank you for your patience and once again i am deeply sorry for the issue we have caused.
Once again if anyone wish refund we will do refund in full amount.
Thank you all for understanding.
Keep update, please!
Hi,
Resync is done, now we are rebuilding metadata
Metadata restored,
VMs are started to boot up.
IO will be slow first few hours, there may be sporadic reboots. We was little bit faster than our provider so another one reboot will be required when ssds are inserted into server.