title: Mounting a NVME disk on AWS EC2
body: <p>So I created i3.large with NVME disk on each nodes, here was my process :</p>
  <ol>
  <li>lsblk -&gt; nvme0n1 (check if nvme isn't yet mounted)</li>
  <li>sudo mkfs.ext4 -E nodiscard /dev/nvme0n1</li>
  <li>sudo mount -o discard /dev/nvme0n1 /mnt/my-data</li>
  <li>/dev/nvme0n1 /mnt/my-data ext4 defaults,nofail,discard 0 2</li>
  <li>sudo mount -a (check if everything is OK)</li>
  <li>sudo reboot</li>
  </ol>
  <p>So all of this works, I can connect back to the instance. I have 500 GiB on my new partition.</p>
  <p>But after I stop and restart the EC2 machines, some of them randomly became inaccessible (AWS warning only 1/2 test status checked)</p>
  <p>When I watch the logs of why it is inaccessible it tells me, it's about the nvme partition (but I did sudo mount -a to check if this was ok, so I don't understand)</p>
  <p>I don't have the AWS logs exactly, but I got some lines of it :</p>
  <blockquote>
  <p>Bad magic number in super-block while trying to open</p>
  <p>then the superblock is corrupt, and you might try running e2fsck with an alternate superblock:</p>
  <p>/dev/fd/9: line 2: plymouth: command not found</p>
  </blockquote>