<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<atom:link href="http://dev1galaxy.org/extern.php?action=feed&amp;tid=8230&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Dev1 Galaxy Forum / [SOLVED] SD Card problem]]></title>
		<link>http://dev1galaxy.org/viewtopic.php?id=8230</link>
		<description><![CDATA[The most recent posts in [SOLVED] SD Card problem.]]></description>
		<lastBuildDate>Wed, 07 Oct 2026 17:08:33 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[Re: [SOLVED] SD Card problem]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=65928#p65928</link>
			<description><![CDATA[<p>Hello:</p><div class="quotebox"><cite>fsmithred wrote:</cite><blockquote><div><p>One or more of these should work.</p></div></blockquote></div><p>Thanks for the heads-up.<br />Had never heard of [sfdisk] before.</p><p>Best,</p><p>A.</p>]]></description>
			<author><![CDATA[dummy@example.com (Altoid)]]></author>
			<pubDate>Wed, 07 Oct 2026 17:08:33 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=65928#p65928</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] SD Card problem]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=65927#p65927</link>
			<description><![CDATA[<div class="quotebox"><blockquote><div><p>I have yet to find a properly documented (understandable) set of instructions to reset partiton sizes and such operations.</p></div></blockquote></div><p>One or more of these should work.</p><p>Restore partition table with sfdisk<br /><a href="https://html.duckduckgo.com/html?q=restore%20partition%20table%20with%20sfdisk" rel="nofollow">https://html.duckduckgo.com/html?q=rest … h%20sfdisk</a></p>]]></description>
			<author><![CDATA[dummy@example.com (fsmithred)]]></author>
			<pubDate>Wed, 07 Oct 2026 16:28:14 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=65927#p65927</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] SD Card problem]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=65921#p65921</link>
			<description><![CDATA[<p>Hello:</p><p>@KindlyDoRight</p><div class="quotebox"><cite>KindlyDoRight wrote:</cite><blockquote><div><p>... useful to reset the correct partition size, after I have botched a partition when resizing it.</p></div></blockquote></div><p>Yes, I have used the [testdisk] [PhotoRec] utility to recover files from an accidental [dd] stopped at 1.5MB.</p><p>The problem is that losing the directory structure results is an endless stream of [recup_dir.X] directories with a few files in each of them, many times repeated in other directories. ie: a nightmare.<br />Better than nothing, I guess.</p><p>I have yet to find a properly documented (understandable) set of instructions to reset partiton sizes and such operations.<br />That said, most important step is to make an image of the damaged drive before doing anything with [testdisk].</p><p>@dzz</p><div class="quotebox"><cite>dzz wrote:</cite><blockquote><div><p>&quot;64GB&quot; Sandisk Ultra here ...</p><div class="codebox"><pre><code># fdisk -l /dev/sdc
Disk /dev/sdc: 57.3 GiB, 61530439680 bytes, 120176640 sectors
Disk model:  SanDisk 3.2Gen1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x8776131b

Device     Boot Start       End   Sectors  Size Id Type
/dev/sdc1  *     2048 120176639 120174592 57.3G  c W95 FAT32 (LBA)</code></pre></div><p>Gparted also reports 57.3G. Never mind, it works.</p></div></blockquote></div><p>Right.</p><p>Thank you both for your input.</p><p>Best,</p><p>A.</p>]]></description>
			<author><![CDATA[dummy@example.com (Altoid)]]></author>
			<pubDate>Wed, 07 Oct 2026 12:24:44 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=65921#p65921</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] SD Card problem]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=65920#p65920</link>
			<description><![CDATA[<p>Hello:</p><div class="quotebox"><cite>Mercury wrote:</cite><blockquote><div><p>... an image of the entire device then the image should be the same size as the device capacity. All bootloader and partitioning info (if any) will be part of the image ...</p></div></blockquote></div><p>I see.</p><div class="quotebox"><cite>Mercury wrote:</cite><blockquote><div><p>Why are you flashing to a partition here?</p></div></blockquote></div><p>See my previous reply to @rbit.</p><p>Thanks for your input.</p><p>Best,</p><p>A.</p>]]></description>
			<author><![CDATA[dummy@example.com (Altoid)]]></author>
			<pubDate>Wed, 07 Oct 2026 12:08:18 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=65920#p65920</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] SD Card problem]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=65919#p65919</link>
			<description><![CDATA[<p>Hello:</p><p>Sorry for the delayed reply.</p><div class="quotebox"><cite>rbit wrote:</cite><blockquote><div><p>... the &quot;img&quot; file is of the device, but you&#039;re trying to write it to a partition.</p></div></blockquote></div><p>I see.</p><p>I did it so:<br />1. formatted the sd card (clear and then as FAT32 or ext4)<br />2. remount it and check the device name (with dmesg, Gparted, Disks and lsblk) &lt;- imagine why...* <br />All these printed [/dev/sdX1], so I used that for [dd].<br />Made sense to me as the SD Card was not partitioned. <br />ie: just one single partition</p><p>OT -&gt;<br />When new to Linux, I read about [dd] being called &quot;disk destroyer&quot;) so I have always been weary of using it.<br />But I <em>have</em> used it in a few occasions, inevitably resulting in lack of practise / experience.<br />Something you <em>may</em> have noticed. 8^°</p><p>But I will insist, I think it is a very powerful and versatile tool, just have to learn to master it.<br />Eventually. * even with all these precautions, I have lost more than one partition table to [dd].<br />&lt;- OT</p><div class="quotebox"><cite>rbit wrote:</cite><blockquote><div><p> ... fdisk -l /media/storage/isos/chimaera/rpi_chimaera.img</p></div></blockquote></div><div class="codebox"><pre><code># fdisk -l rpi_chimaera.img
Disk rpi_chimaera.img: 7.22 GiB, 7757398016 bytes, 15151168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xd9d859d0

Device            Boot  Start      End  Sectors  Size Id Type
rpi_chimaera.img1 *      2048   524287   522240  255M  b W95 FAT32
rpi_chimaera.img2      524288 15151103 14626816    7G 83 Linux
# </code></pre></div><p>I have managed to properly write an image to the sd card using [disks]; boots/works as expected.<br />[rpi-3-devuan-chimaera-5.10.74-v8-ext4-2021-10-19.img] from the Devuan repository.</p><div class="codebox"><pre><code># fdisk -l rpi-3-devuan-chimaera-5.10.74-v8-ext4-2021-10-19.img
Disk rpi-3-devuan-chimaera-5.10.74-v8-ext4-2021-10-19.img: 1.82 GiB, 1958482432 bytes, 3825161 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xd9d859d0

Device                                                Boot  Start     End Sectors  Size Id Type
rpi-3-devuan-chimaera-5.10.74-v8-ext4-2021-10-19.img1 *      2048  524287  522240  255M  b W95 FAT32
rpi-3-devuan-chimaera-5.10.74-v8-ext4-2021-10-19.img2      524288 3825160 3300873  1.6G 83 Linux
# </code></pre></div><p>I now have to pull configuration and files I need from the last working image which can be mounted with [disks].<br />Only remaining problem (if I stay with Chimaera) is the repository not working yet.<br />Again, eventually. </p><p>Thanks for your input.</p><p>Best,</p><p>A.</p>]]></description>
			<author><![CDATA[dummy@example.com (Altoid)]]></author>
			<pubDate>Wed, 07 Oct 2026 12:01:23 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=65919#p65919</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] SD Card problem]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=65918#p65918</link>
			<description><![CDATA[<p>Hello:</p><div class="quotebox"><cite>rolfie wrote:</cite><blockquote><div><p>... the old GB vs GiB problem.</p></div></blockquote></div><div class="quotebox"><cite>greenjeans wrote:</cite><blockquote><div><p>Look close Altoid ...</p></div></blockquote></div><p>Yes ...<br />And see how easy it is to embarass oneself.&#160; 8^°</p><p>Thank you both.</p><p>Best,</p><p>A.</p>]]></description>
			<author><![CDATA[dummy@example.com (Altoid)]]></author>
			<pubDate>Wed, 07 Oct 2026 11:04:09 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=65918#p65918</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] SD Card problem]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=65914#p65914</link>
			<description><![CDATA[<p>7.8 vs 7.2 is GB vs GiB and <span class="bbc">dd</span> reports both. That&#039;s not an issue.</p><div class="quotebox"><blockquote><div><p>31914983424 bytes, 62333952 sectors</p></div></blockquote></div><p>That looks right. The sectors are a multiple of 1024, and therefore the total capacity is a multiple of 524,288 bytes, or exactly half a MiB. Searching for the exact values you gave pulls up a lot of google results, so this is standard.</p><p>Partitioning and GRUB are not the issue here. If you took an image of the entire device then the image should be the same size as the device capacity. All bootloader and partitioning info (if any) will be part of the image and should not be regarded separately for purposes of <span class="bbc">dd</span> flashing.</p><div class="quotebox"><blockquote><div><p>dd if=/media/storage/isos/chimaera/rpi_chimaera.img of=/dev/sdg1</p></div></blockquote></div><p>Why are you flashing to a partition here?</p>]]></description>
			<author><![CDATA[dummy@example.com (Mercury)]]></author>
			<pubDate>Tue, 06 Oct 2026 23:26:23 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=65914#p65914</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] SD Card problem]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=65912#p65912</link>
			<description><![CDATA[<p>It may be that the &quot;img&quot; file is of the device, but you&#039;re trying to write it to a partition.<br />What does this show <span class="bbc">fdisk -l /media/storage/isos/chimaera/rpi_chimaera.img</span></p>]]></description>
			<author><![CDATA[dummy@example.com (rbit)]]></author>
			<pubDate>Tue, 06 Oct 2026 21:16:44 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=65912#p65912</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] SD Card problem]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=65906#p65906</link>
			<description><![CDATA[<div class="quotebox"><blockquote><div><p>This is the old GB vs GiB problem.</p></div></blockquote></div><p>Yep.</p><p>The GB (Gigabyte) is decimal system and equals 1,000,000,000 bytes. The GiB (Gibibyte) is binary system and equals 1,073,741,824 bytes.</p><p>Look close Altoid : 7.8 <strong>GB</strong>, 7.2 <strong>GiB</strong></p>]]></description>
			<author><![CDATA[dummy@example.com (greenjeans)]]></author>
			<pubDate>Tue, 06 Oct 2026 19:24:29 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=65906#p65906</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] SD Card problem]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=65905#p65905</link>
			<description><![CDATA[<p>Hello:</p><div class="quotebox"><cite>I wrote:</cite><blockquote><div><p>Will post with results.</p></div></blockquote></div><p>Unfortunately, I am getting the same results I posted previously.</p><p>This is the [dd] process:</p><div class="codebox"><pre><code># dd if=/media/storage/isos/chimaera/rpi_chimaera.img of=/dev/sdg1 bs=4M status=progress
7755268096 bytes (7.8 GB, 7.2 GiB) copied, 668 s, 11.6 MB/s^[[B
1849+1 records in
1849+1 records out
7757398016 bytes (7.8 GB, 7.2 GiB) copied, 787.312 s, 9.9 MB/s
# </code></pre></div><p>ie: all records written but only 7.2 GB of 7.8 GB copied. &lt;-- what did not get copied? </p><div class="codebox"><pre><code># mount /dev/sdg1 /mnt/SD
mount: /mnt/SD: wrong fs type, bad option, bad superblock on /dev/sdg1, missing codepage or helper program, or other error.
       dmesg(1) may have more information after failed mount system call.
# </code></pre></div><p>As I was able to install an old Devuan Beowulf and boot without issues it would seem that the SD Card is working properly, <br />I will try to burn and [*iso] file to see what happens.</p><p>Will post with results.</p><p>Best,</p><p>A.</p>]]></description>
			<author><![CDATA[dummy@example.com (Altoid)]]></author>
			<pubDate>Tue, 06 Oct 2026 18:56:57 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=65905#p65905</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] SD Card problem]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=65904#p65904</link>
			<description><![CDATA[<p>Hello:</p><div class="quotebox"><cite>Mercury wrote:</cite><blockquote><div><p>... took a dd image of this device.<br />... trying to write that image using dd back to the same device ...<br />... getting the error that there is insufficient space. Correct?</p></div></blockquote></div><p>Yes to all.</p><p>There&#039;s still <em>more</em>:<br />While [dd] prints that all records have been written [1849+1 records in / 1849+1 records out], at the same time it prints that of the 7.8 GB that had to be copied, only 7.2 GB had been written [(7.8 GB, 7.2 GiB) copied].</p><div class="codebox"><pre><code># dd if=/media/storage/isos/chimaera/rpi_chimaera.img of=/dev/sdh1 bs=4M status=progress
7757398016 bytes (7.8 GB, 7.2 GiB) copied, 577 s, 13.4 MB/s
1849+1 records in
1849+1 records out
7757398016 bytes (7.8 GB, 7.2 GiB) copied, 703.66 s, 11.0 MB/s
#</code></pre></div><p>Also, if I try to mount the card, I get this:</p><div class="codebox"><pre><code># mount /dev/sdh1 /mnt/SD
mount: /mnt/SD: wrong fs type, bad option, bad superblock on /dev/sdh1, missing codepage or helper program, or other error.
       dmesg(1) may have more information after failed mount system call.
# </code></pre></div><p>[dmesg] prints the same data.</p><p>Curiously enough I was able to install an old [Beowulf] netinstall but stopped short of installing [LiLO] because GRUB was not offered as an option.</p><p>So what&#039;s up with my not being to install [*.img] files? <br />I insisted with the Beowulf installation this time in automatic mode and (lo and behold) I was able to install it, booting just fine.</p><p>Here is what [fdisk -l] and [df -h] print:</p><div class="codebox"><pre><code>Disk /dev/sdg: 29.72 GiB, 31914983424 bytes, 62333952 sectors
Disk model: Storage Device  
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xb403ed78

Device     Boot Start      End  Sectors  Size Id Type
/dev/sdg1  *     2048 62332927 62330880 29.7G 83 Linux</code></pre></div><div class="codebox"><pre><code># df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/sdg1        30G  607M   27G   3% /mnt/SD
# </code></pre></div><p>I can also mount it manually with no issues:</p><div class="codebox"><pre><code># mount /dev/sdg1 /mnt/SD
# cd /mnt/SD
# ls
bin   dev  home        initrd.img.old  lib64	   media  opt	root  sbin  sys  usr  vmlinuz
boot  etc  initrd.img  lib	       lost+found  mnt	  proc	run   srv   tmp  var  vmlinuz.old
# </code></pre></div><p>So the next test would be to see if installing [GRUB] to the card has cleared out whatever was causing the problem.<br />ie: any one (or more) of these: wrong fs type, bad option, bad superblock on /dev/sdh1, missing codepage or helper program, or other error.</p><p>Will post with results.</p><p>Best,</p><p>A.</p>]]></description>
			<author><![CDATA[dummy@example.com (Altoid)]]></author>
			<pubDate>Tue, 06 Oct 2026 18:11:44 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=65904#p65904</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] SD Card problem]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=65899#p65899</link>
			<description><![CDATA[<p>To recap:</p><p>You took a <span class="bbc">dd</span> image of <em>this device</em>. Now your are trying to write that image using <span class="bbc">dd</span> back to <em>the same device</em> but you are getting the error that there is insufficient space. Correct?</p><p>It&#039;s natural to blame the device since cards like this are known for failing, and that&#039;s if they&#039;re even legitimate. However, I&#039;m wondering if something about <em>the image you took</em> is the problem. Maybe it somehow got &quot;padded out&quot;.</p><p>Exactly how large (in bytes or sectors) is the card, and exactly how large is the image?</p><p>Look at the image itself. Is the end filled with zeroes or does it contain data? (I use wxHexEditor for such things but other tools exist)</p>]]></description>
			<author><![CDATA[dummy@example.com (Mercury)]]></author>
			<pubDate>Tue, 06 Oct 2026 15:28:57 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=65899#p65899</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] SD Card problem]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=65898#p65898</link>
			<description><![CDATA[<p>I found &quot;testdisk&quot; <span class="bbc">apt show testdisk</span> useful to reset the correct partition size, after I have botched a partition when resizing it.</p>]]></description>
			<author><![CDATA[dummy@example.com (KindlyDoRight)]]></author>
			<pubDate>Tue, 06 Oct 2026 14:58:09 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=65898#p65898</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] SD Card problem]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=65897#p65897</link>
			<description><![CDATA[<p>That download link is perfecty ok. </p><p>This is the old GB vs GiB problem.</p>]]></description>
			<author><![CDATA[dummy@example.com (rolfie)]]></author>
			<pubDate>Tue, 06 Oct 2026 14:56:41 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=65897#p65897</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] SD Card problem]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=65896#p65896</link>
			<description><![CDATA[<p>&quot;64GB&quot; Sandisk Ultra here:</p><div class="codebox"><pre><code># fdisk -l /dev/sdc
Disk /dev/sdc: 57.3 GiB, 61530439680 bytes, 120176640 sectors
Disk model:  SanDisk 3.2Gen1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x8776131b

Device     Boot Start       End   Sectors  Size Id Type
/dev/sdc1  *     2048 120176639 120174592 57.3G  c W95 FAT32 (LBA)</code></pre></div><p>Gparted also reports 57.3G. Never mind, it works.</p><p>! That link is a M$ platform executable..</p>]]></description>
			<author><![CDATA[dummy@example.com (dzz)]]></author>
			<pubDate>Tue, 06 Oct 2026 14:43:17 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=65896#p65896</guid>
		</item>
	</channel>
</rss>
