Fandom of Halloween Specials Archive

 

  Most wikis that were only the original db141 have now been brought back online. The db141 hostname has been retired due to it's history, and is now replaced with db142. A few of the original ones have not yet been able to be restored, and wikis that had been recreated after the initial outage are also still not back online yet. We are still working at this process to bring wikis back online fully. Wikis created (initial creation) after November 25 will not be possible to be restored. However, we have backups for all  public  wikis beginning with A-O, and can restore those from backups. If you requested a recreation after the initial outage, it will take a bit more time to get those wikis back online. The version that will eventually be restored will be the pre November 16 version. If you wish to have the wiki reset, or imported from personal backups, or if it is one we have backups from, you may later request a reset of that wiki, to this state. Also not that around 20 ...

  20:00 (UTC), Monday, 26 December 2022 - We have uploaded the databases to our new database server. We are now working to get the wiki back online. Due to the holidays, this may take a bit longer than usual. Thank you for your understanding.

 

 

 

  LATEST UPDATE: 06:00 (UTC), Thursday, 22 December 2022 - We are uploading the data from the recovered disks onto our servers. This may take up to 2 more days. Afterwards, we will work to restore all wikis once again.

  We have very important news regarding db141. Yesterday, we were able to access and recover the data on the corrupted drives, including the drives which contained the original  db141 . We intend to begin restoring affected wikis as soon as possible and we will be releasing more information about it once we get details finalised. Now, during our scheduled maintenance yesterday, we encountered an issue attempting to get new storage drives detected by our  cloud13 server. We asked our hosting provider to reseat the disks but we then deemed it unnecessary and cancelled the request. Unfortunately, the request was still being processed and our hosting provider mistakenly reseated  cloud14 's drives while the server was on. Due to this, the server locked up and we had to run some file system repair tools (fsck specifcially) to get it back online. Once  cloud14  and all its virtual servers came back up, we discovered that because the new  db141  was runn...