Approximately 3 years ago my boss had another company setup our AWS services. This company used an instance-store backed AMI and unfortunately i cannot launch any new instances from it (the AMI) as it will not boot.
The problem appears to be that it cannot mount an EBS volume to /data, despite me attaching the device to the same block that it is on the running instance "/dev/sdg"
It looks like in the fstab they have not added a nobootwait for the /data drive, here is their entry in fstab:
/dev/xvdg1 /data ext4 noatime 0 0
All i need to do is to be able to edit the AMI and tweak that line in fstab or alternatively send the "M" key to the server to skip loading that drive.
The primary server cannot be switched off, it is critical and i would be concerned if it does not boot we would be unable to copy it.
I need to duplicate this server and upgrade it then rsync the data over and swap it out, but i'm in a catch 22. Any advice is greatly appreciated.