- Newest
- Most votes
- Most comments
I was able to fix the issue quite simply. It seems like the setup was stuck but I went back in the console and clicked the Gateway directly and was able to visualize and assign the disks.
Hello,
I'm Mike with the Storage Gateway team.
The issue you are describing is can have a lot of causes, so more detail would be needed to give you a solid troubleshooting direction. The issue with recognizing disks may be as simple as first rebooting your gateway VM (to make sure the local OS has recognized the added disks) and then trying the console again. If that doesn't work, I strongly recommend opening a case with premium support if you have a contract with them. If not, please provide the following so we can better understand your environment:
- What Hypervisor are you using? KVM, VMware, or Hyper-V? Since you mention Linux, I suspect a KVM system, but please clarify.
- Are you deploying a File, FSx, Tape, or Volume gateway?
- How many disks have you added to the downloaded gateway image? What size(s)?
- When the gateway VM is running, if you go to the VM console, are you able to pass the network connectivity test? Below I provide the test for file gateway, but all gateway types have a similar test: ** https://docs.aws.amazon.com/filegateway/latest/filefsxw/manage-on-premises-fgw.html#MaintenanceTestGatewayConnectivity-fgw **
- Have you successfully activated the gateway? The console allows for activation without the additional disks and they can be added later.
Please let me know if you have any follow up questions I can provide answers to.
Mike H., AWS SGW, SE
Relevant content
- Accepted Answerasked a year ago
- asked 5 years ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
Hey Mike, thanks for your reply. I was able to fix the issue quite simply. It seems like the setup was stuck but I went back in the console and clicked the Gateway directly and was able to visualize and assign the disks.