diff --git a/mkdocs-project-dir/docs/Status_page.md b/mkdocs-project-dir/docs/Status_page.md
index abab83c29..aa8b034df 100644
--- a/mkdocs-project-dir/docs/Status_page.md
+++ b/mkdocs-project-dir/docs/Status_page.md
@@ -185,6 +185,30 @@ This page outlines that status of each of the machines managed by the Research C
     We're sorry for this situation and are working to address it. We'll keep you updated as we 
     know more.
 
+  - 2023-06-29 11:30 - We've recovered what was on the failing disk and are missing approximately 
+    250kB of metadata. (Since it is metadata, this doesn't directly translate to the effect on your
+    files, but we can probably be cautiously optimistic about the expected size of impact, should 
+    nothing else go horribly wrong).
+
+    Replacement disks are being sent to us and should arrive today or tomorrow.
+
+    Once the disks arrive, we will proceed with the next step of moving the recovered data onto a 
+    new disk and getting the filesystem to use that in replacement of the failed disk, and then we 
+    can attempt to bring the filesystem up and see what status it thinks it is in. At that point we
+    will have several levels of filesystem health checking to run.
+
+    We are also progressing with some contingency plans relating to the backup data we have, to 
+    make it easier to use should we need to. 
+
+    I've had a couple of questions about when Young will be back up - we don't know yet, but not 
+    during next week. I would expect us to still be doing the filesystem recovery and checks on 
+    the first couple of days of the week even if the disks do arrive today, so we probably won't 
+    have any additional updates for you until midweek.
+
+    It does take a long and unpredictable time to rebuild disks, check all the data, and recover 
+    files: as an example, our metadata recovery was giving us estimates of 19 hours to 5 days while
+    it was dealing with the most damaged portions of the disk. 
+
 
 ### Michael