Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
First time the image is no good (gets the root partition, but no boot partition, or what's supposed to be the boot partition is full of files with garbled names).
But if I re-do the same command, it works the second time.
Happened with multiple cards. Latest just yesterday with new card, fresh out of packaging.
Has happened on different writers and different hardware.
I'm wondering if automount is somehow trying to mount before it's done. But, then why does it work the second time...
Or maybe whatever the existing partitioning is messes it up first time around, but since after the first go the partition is screwy and the second time it works.
Looks like a race - the second execution will read the image from page cache. Use "oflag=sync" on the dd command rather than sync afterwards - slows it down (probably what you want in this case), but always works for me.
I didn't even know people still had to use sync manually. I don't think I've used it since ancient versions of SunOS (the BSD version, not Solaris SVR4 versions). I thought those problems were fixed.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.