Wednesday, 7 January 2009

unmount: command not found

Just a short and simple note here to new Ubuntu users...
When I first started using Ubuntu, this error message that I received drove me crazy. I could not understand why it would not work for. I was running a command like: sudo unmount /dev/sda3. Then I realized that I had been totally stupid, and had miss read it. The command should have been: sudo umount /dev/sda3 umount, not unmount.

I know this is a pretty dumb post for the more experienced Ubuntu users out there, but I just remembered how much it annoyed when when I first started. If you are like me, and still type unmount, and remember it's not, you could always set up an alias for it. View this post to see how you would do this: http://jamsubuntu.blogspot.com/2008/12/how-to-create-your-own-aliases.html

40 comments :

  1. Thanks. You saved my day!

    ReplyDelete
  2. That's it! I have to read it multiple times to get the typo difference... it's not stupid it's just crazy!

    ReplyDelete
  3. Thank you so much!

    ReplyDelete
  4. YES! What an unintuitive command, was driving me nuts.

    ReplyDelete
  5. Thanks, I was about to start smashing things.

    ReplyDelete
  6. Thanks so much for this sanity check... umount drove me crazy as well

    ReplyDelete
  7. Grant Vanstaden19 March 2011 at 13:19

    Thank you. I had this exact problem.

    ReplyDelete
  8. Thanks for this. You're the best!

    ReplyDelete
  9. lol I had this same problem thanks

    ReplyDelete
  10. omg. me too~! thanks for you.^^

    ReplyDelete
  11. holy shit i'm such a dump...
    thanks i first thought the program was moved to something else.

    ReplyDelete
  12. LOL, you just saved me there, I was doing the exact same thing. This sort of thing is why I avoid the command line. 

    ReplyDelete
  13. Thanks...just what I was looking for.

    ReplyDelete
  14. Same here.... pff xD I was totally stupid xD

    ReplyDelete
  15. OMFG I was so stupid too, thanks dude for helping me fight my own stupidity

    ReplyDelete
  16. Thanks. I misread it too.

    ReplyDelete
  17. Lol had the same problem, thanks a lot!

    ReplyDelete
  18. hahaha it can't be xD

    ReplyDelete
  19. You have no idea how long I've been trying to figure this out...

    ReplyDelete
  20. This is one of those mistakes you keep hitting yourself, asking "No, your kidding?!"

    ReplyDelete
  21. Thnxx ... , studpid mistake :(

    ReplyDelete
  22. THANK YOU!! Thanks for taking the time to make a note to all of us who have been frustrated with this. I too had to reread your post to catch the subtle difference. Was omitting the "n" character all that beneficial/worth it? lol

    ReplyDelete
  23. just made the same mistake :) thanks!

    ReplyDelete
  24. Was making the same mistake myself, thank you for clearing up the command. Helpful to new users

    ReplyDelete
  25. how stupid is Umount? what?? why not plain UNmount..?

    ReplyDelete
  26. Thank you for spending the time to post this. I just spent 3 hours flailing about,.... because I also read "unmount" when the part of the script I was

    using clearly said "umount" . Funny! Maybe it the command should be
    "unmount"? Oh well "garbage in <----> garbage out".

    ReplyDelete
  27. Łukasz Wieczorek26 November 2013 at 16:10

    hah, wow. Same prob. thanks for post.

    ReplyDelete
  28. trying to fix my Synology Crashed Volume. Support just sucked. finally found a the wiki to run a e2fsck. but being a windows guy, yea, I made this mistake. Thanks for posting to help the GUI folks out.

    ReplyDelete
  29. Vinay Kumar Jaiswal29 November 2014 at 08:11

    same problem. I too was typing unmount instead of umount. Thanks.

    ReplyDelete
  30. Ha-ha-ha )) Me too! Thanks a lot!

    ReplyDelete
  31. U're Genius! never would have found that one out :D

    ReplyDelete

Follow by Email

Contact Form

Name

Email *

Message *

2014 © Planer - Responsive Blogger Magazine Theme
Planer theme by Way2themes