Sevag H

Very cool, I'll check it out.

I'm glad the tool has been useful. It could be that the disks are somehow already attached, in which case my code ignores them - I believe that's a corner...

Can you test this hotfix? https://github.com/sevagh/goat/releases/tag/1.0.3-rc0

I _should_ be getting that attached device name from the AWS API: https://docs.aws.amazon.com/sdk-for-go/api/service/ec2/#VolumeAttachment

This same issue is OK. I'll get back to you soon.

Can you print the logs surrounding the above error message? There are some additional functions related to nvme (which another user helped contribute) - I'm not very well versed in...

Nice sleuthing - it looks like I should put a call to this function, GetActualBlockDeviceName, somewhere: https://github.com/sevagh/goat/blob/b6af4b2b37cc6867d154aa19716e1667146b98cc/filesystem/drive.go#L38 Maybe when writing the fstab entry - but I'm having trouble discovering where...

I'm building a 1.0.3-rc1

https://github.com/sevagh/goat/releases/tag/1.0.3-rc1 The gist is that I put the "GetActualBlockDeviceName" call early in the code to have the real nvme name in the volume struct rather than substituting it in the...

What's funny is that I think all of this workaround comes from me choosing `/dev/xvd{b,c,d,e,f,g,...}` as a random device name for both non-NVME and NVME devices. So this "rediscovery" of...