Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sudo file -s /dev/xvdf command failed #13

Open
minnoc opened this issue Aug 19, 2021 · 4 comments
Open

sudo file -s /dev/xvdf command failed #13

minnoc opened this issue Aug 19, 2021 · 4 comments

Comments

@minnoc
Copy link

minnoc commented Aug 19, 2021

sudo file -s /dev/xvdf failed after attaching volume to the EC2 instance. To fix it i named it /dev/xvdf when i attached the volume

@acantril
Copy link
Owner

named what ?
I'm really not sure what you are saying ...
/dev/xvdf is a device ID ... you aren't naming anything.

@acantril
Copy link
Owner

can you give a little more info, what steps you are doing, what error you see
what didn't work
what course this is from
what lesson this is from

@minnoc
Copy link
Author

minnoc commented Aug 19, 2021

Great response time :)
Course is
AWS Certified Solutions Architect - Associate (SAA-C02)
Lesson is
[DEMO] EBS, Snapshots and Instance Store Volumes - PART1

yes i'm referring to the device. In the lesson it's listed as /dev/sdf, to make it so the command sudo file -s /dev/xvdf didn't fail, i changed the name in the EC2 console to /dev/xvdf when attaching the EBSTestVolume to the EC2 instance

@acantril
Copy link
Owner

I'll have a look because /dev/sdf should be mapped as /dev/xvdf in linux
Thats how it is on my video .. and it worked ok.
The device ID changes depending on linux distro, but amazon linux should use /dev/xvdf for /dev/sdf set in console

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants