Slackware - ARMThis forum is for the discussion of Slackware ARM.
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.
This is probably a more general question but its only failing when I copy a MicroSD card from my PI.
I try to take a MicroSD from one of my Pi's and plug into a reader on my laptop, DD it to an image then DD that to another microsd and plug the new one back into the same Pi and have it boot.
All my hardware should be fine since I can download a pre-made image and write it fine, I can read/write files from the Sd cards fine, I just can't make a bootable copy.
I've tried various block sizes, etc. There must be something simple I'm overlooking.
Distribution: Mainly Devuan, antiX, & Void, with Tiny Core, Fatdog, & BSD thrown in.
Posts: 5,478
Rep:
Raspbian does it from within, not sure how, might be worth taking a look at.
Are you creating your new cards as bootable disks when you create your partition on them(?).
Also the type of formatting has something to do with whether they boot or not, (I think it might have to be 32bit dos formatted).
Sorry I can't be more helpful, as I only bought my one to see if it could replace a desktop computer for every day usage.
I'm taking a bootable MicroSD with a running OS on it, shutting down that OS and DD'ing it to an image. So its copying partitions, formatting, etc. Then I try to DD it back to a new MicroSD and then pop that new microSD into the Pi and it won't boot.
Its similar to how you would download rasbain from the RPi foundation and DD it to a blank card.
/dev/sdx == what the device is... in this example /path/to/image will be the directory created in your home directory. I called my image 'slack.image'. This will take a few minutes.
When done, just pull the card and get your Pi up and running again.
Now, to clone a copy, get another SD card THE SAME SIZE as the copied one.
Insert it into the machine you already copied the Pi SD from and issue (again DO NOT MOUNT IT):
Code: Select all
dd if=/path/to/image of=/dev/sdx
for whatever reason the dd to image and dd from image to new card works fine but the new card won't boot the pi.
I cloned slackwarearm sd card and openelec sd card, got two new rpi3, plugged in cloned sd cards and was up and running after few tweaks here there for this and that.
I'd say post at fatdog but I know the fatdog regulars check here often too.
I've also read sometimes sd cards same brand, size, etc, will sometimes misbehave.
You figure it out post back.
Last edited by glorsplitz; 04-19-2017 at 06:06 PM.
I don't use Raspian, but with Arch, I just copy (as in cp or rsync) the files up to my PC hard disk, then stick a new SDCard in and copy back. Works on a pi3, and also a goflex home backup system (Marvell Sheeva plug) in which I installed a new (real) hard disk about a week ago.
Has the side benefit you know the source filesystem(s) is ok and readable.
Edit: presumes U-Boot or similar has been flashed successfully beforehand.
you cannot copy the sd card which is currently in use.
what you told in post #5 usually works, but would be nice to explain what did you exactly tried and what's happened.
from my own mileage:
1. Some cards ("non brand" names) seem to misbehave on R_Pi?
2. what has the same md5 is the same (try comparing md5sum of the image got from the copy?)
3. R_Pi seems to be cherry picking SDcards, so try sticking to Samsung or the like branded ones for testing?
Once just as I was about to quit, I reiterated with a "branded" SDcard, and got it going?
And I don't speak off top of my head here:
On the zero "track", usually there is the boot loader that "imports" the kernel et al. (in between the partition table and the 1st partition) to the RAM, there from all that matter is the parttion(s) contain filesystems that the kernel has modules for (built-in or pre-loaded (initrd->RAM) )
So for testing try an known good SDcard and only the "boot payload" (the begin and the fat partition).
If You get lucky, go for it and buy an device from an reputable brand?
If fail, try pull back the image from the 2nd SDcard and compare the two copies?
maybe the card reader is faulty, or it has intermittent problems (cable? plugs?)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.