Problems with Tail02 on Bytemark Cloud Platform

Expected resolution: 21 Apr 2018, 20:00 UTC
Return to issues
Issue status: Resolved Date:

21 Apr 2018
22:34 UTC

Posted by:

Ian Chilton

We've recovered the last disc and successfully migrated it to another tail.

The broken tail is now empty and everything should be back.

Sorry for the inconvenience to those affected.

Issue status: Investigating Date:

21 Apr 2018
22:00 UTC

Posted by:

Ian Chilton

We're just dealing with 1 last disc now.

Issue status: Investigating Date:

21 Apr 2018
20:39 UTC

Posted by:

Ian Chilton

All of the discs on the non affected pools have been migrated off the problem tail.

We can now concentrate on fixing the affected pool.

Issue status: Investigating Date:

21 Apr 2018
19:19 UTC

Posted by:

Doug Targett

We've taken one pool of 29 discs down from tail02 due to the errors we're seeing. We think all the other pools on the tail are unaffected and we're currently starting to migrate them away to a spare tail as a precaution.

If you're experiencing any problems with your services at Bytemark that you think might be related, please do get in touch.

Expected resolution time updated: 21 Apr 2018, 20:00 UTC

Issue status: Investigating Date:

21 Apr 2018
18:34 UTC

Posted by:

Doug Targett

We have had to restart the pool tail02-sata1 in an effort to get the disks usable again.

If you're experiencing any problems with your services at Bytemark that you think might be related, please do get in touch.

Issue status: Investigating Date:

21 Apr 2018
18:30 UTC

Posted by:

Doug Targett

We've been alerted to an issue causing slowness on tail02

You might be affected if your Bytemark Cloud Server has a disk on Tail02

Sorry about this! We're investigating and working to restore full service as soon as possible. We'll post updates here.

If you're experiencing any problems with your services at Bytemark that you think might be related, please do get in touch.

Expected resolution time updated: 21 Apr 2018, 19:30 UTC

Return to issues

Issue still not addressed? Please contact support.