Perfect! Thanks!!

Ok, on this particular SD card non of the systems I tried it on in /dev showed anything mounted as say sbd, sbc, or even sba in the case of the Pi where the disk running the active in

Hi Marty, The SD cards are TYPICALLY formatted as xFAT from the factory. Some may slip thru without initial formatting etc. Yes, it warns you that all data will be deleted, but that is because it

This thread has turned into a Gotcha like 3 year olds. Let us get back to discussing RaspberryPi problems.

Narrowing the scope? Below, I'll paste the original in it's unedited format. You can clearly see that I say that if it doesn't work, it's something *other* than the disk image, or the writing

Hi Jeff and all A question for my ongoing education. Not exactly about copying an image onto a new micro SD card, but one on the Pi doing a SD copy backup of the disk in use. Like copying the

I provided facts. When you were presented with them, You danced around them and narrowed your scope to try and retain being righteous.

Wow. Arguing over imaging an SD card. New ultimate low. Grow up guys and move on. Dr. William J. Schmidt - K9HZ J68HZ 8P6HK ZF2HZ PJ4/K9HZ VP5/K9HZ PJ2/K9HZ Owner - Operator Big Signal Ranch

"stop being a cocky ass" As usual, when you cannot argue facts, the weak argument becomes personal. Cool. -- Jeff Palmer Palmer IT Consulting, LLC. https://PalmerIT.net

"To over write what ever is on the disc with the image; the disk must be mounted on the hardware." Again, an unrelated cause. This is not universally true. It's a problem with the OS, and the

When you give an absolute in that "it just works" and ignore hardware issues, that is faulty reasoning. The process fails and you cannot get the process to complete properly Stop being a cocky ass

"but the issue becomes, if the hardware has an issue," Thank you for confirming my point. It's not the disk image, or the process by which the image is written. It's another (and

Jeff, I do not believe anyone is disagreeing with that statement. I do think you do not understand our problem. It is not a direct software problem; it is much more of a hardware problem. To over

Jeff, RELAX. Just because you have not run across something doesn't mean it never happens. That is also an anecdotal observation. Just because someone eats 20 greasy hamburgers a day and lives to

I have also been in IT for 30 years. and I have seen cases where a disk image could NOT be written due to some unforseen corruption on a factory fresh disk/memory card etc. The OS does look at the

Mark, I've done nothing but state facts. You've done nothing but personal attacks ("One day I'll learn enough", "I guess you just haven't seen enough", blah blah blah) You've not stated a single

Well, I suppose my 30+ years also means something too? Eh? I guess you just haven't seen enough yet. My apologies. Argue away. I'm not listening, so your audience is elsewhere. Mark

OK, Now I am trying to argue. There are absolutes in this field. Disk images ARE absolute. writing them to a disk IS absolute. It overwrites *everything* that holds any old layout. That is

Whatever. You *are* trying to argue and tell me my observations are not relevant to your discussion. It's unfortunate, that in what some people may call a discussion, it's obvious that one side

Mark, If you are using a disk image, then no.. the existing partitioning, or filesystems don't matter. They literally get overwritten. If you've seen cases where this doesn't seem to be the case, I