tools-prometheus-04 did not entirely migrate according to plan. I noticed it was listed as down by alertmanager and checked it. This is the console:
```
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... Waiting 5s for disks to show up (T131961)
Usage: sleep seconds[.fraction]
done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Will now check root file system ... fsck from util-linux 2.33.1
[/sbin/fsck.ext4 (1) -- /dev/vda2] fsck.ext4 -a -C0 /dev/vda2
/dev/vda2 contains a file system with errors, check forced.
/dev/vda2: | | 0.5% [ 2.618215] usb 1-1: new full-speed USB device number 2 using uhci_hcd
/dev/vda2: |==== / 7.8% /dev/vda2: |========= - 15.2% [ 2.815939] usb 1-1: New USB device found, idVendor=0627, idProduct=0001, bcdDevice= 0.00
[ 2.822678] usb 1-1: New USB device strings: Mfr=1, Product=3, SerialNumber=5
[ 2.828158] usb 1-1: Product: QEMU USB Tablet
[ 2.830770] usb 1-1: Manufacturer: QEMU
[ 2.832199] usb 1-1: SerialNumber: 42
[ 2.847395] hidraw: raw HID events driver (C) Jiri Kosina
[ 2.857145] usbcore: registered new interface driver usbhid
[ 2.860841] usbhid: USB HID core driver
/dev/vda2: Inode 786453, end of extent exceeds allowed value
(logical block 72, physical block 34128, len 33)
/dev/vda2: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
[ 2.876239] input: QEMU QEMU USB Tablet as /devices/pci0000:00/0000:00:01.2/usb1/1-1/1-1:1.0/0003:0627:0001.0001/input/input4
fsck exited with status code 4
done.
Failure: File system check of the root filesystem failed
The root filesystem on /dev/vda2 requires a manual fsck
(initramfs) [ 2.890976] hid-generic 0003:0627:0001.0001: input,hidraw0: USB HID v0.01 Mouse [QEMU QEMU USB Tablet] on usb-0000:00:01.2-1/input0
```
Might not be a terribly big deal (fsck might do it). However, I noticed that it's partner is on the schedule for the morning and wanted to make sure we didn't lose both copies.