<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<atom:link href="https://dev1galaxy.org/extern.php?action=feed&amp;tid=8043&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Dev1 Galaxy Forum / Upgrading to Excalibur - lxdm and /boot]]></title>
		<link>https://dev1galaxy.org/viewtopic.php?id=8043</link>
		<description><![CDATA[The most recent posts in Upgrading to Excalibur - lxdm and /boot.]]></description>
		<lastBuildDate>Mon, 15 Jun 2026 19:03:11 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[Re: Upgrading to Excalibur - lxdm and /boot]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=64308#p64308</link>
			<description><![CDATA[<p>Don&#039;t forget, kernel sizes are growing too. What worked some releases ago must no more work with todays kernels.</p>]]></description>
			<author><![CDATA[dummy@example.com (rolfie)]]></author>
			<pubDate>Mon, 15 Jun 2026 19:03:11 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=64308#p64308</guid>
		</item>
		<item>
			<title><![CDATA[Re: Upgrading to Excalibur - lxdm and /boot]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=64305#p64305</link>
			<description><![CDATA[<p>After reading your post I realized that I don&#039;t have an excalibur install with a separate /boot partition, but I do have a couple of daedalus installs with boot partitions that are 500M or smaller. I&#039;m not ready to upgrade those, so I did a test in a VM. Results below:</p><p>200M /boot was too small. I&#039;m not sure why it failed to boot and dropped me to initramfs prompt. I rebooted with a live iso, went into chroot to reinstall grub, update-grub and then run &#039;update-initramfs -u -k all&#039;. It ran out of disk space and failed.</p><p>360M /boot works. I don&#039;t recommend using such a small size, but only because we&#039;re getting so many kernel upgrades lately, it&#039;s easy to accumulate too many to fit. (I think 300M will hold three kernels)</p><div class="codebox"><pre><code>Disk /dev/sda: 8 GiB, 8589934592 bytes, 16777216 sectors
Disk model: QEMU HARDDISK   
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: 0x460d0caf

Device     Boot  Start      End  Sectors  Size Id Type
/dev/sda1         2048   739327   737280  360M 83 Linux
/dev/sda2       739328 16777215 16037888  7.6G 83 Linux

Disk /dev/mapper/root_fs: 7.63 GiB, 8194621440 bytes, 16005120 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
Filesystem           Size  Used Avail Use% Mounted on
/dev/mapper/root_fs  7.5G  4.2G  3.0G  59% /
/dev/sda1            328M   65M  242M  21% /boot</code></pre></div>]]></description>
			<author><![CDATA[dummy@example.com (fsmithred)]]></author>
			<pubDate>Mon, 15 Jun 2026 15:13:30 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=64305#p64305</guid>
		</item>
		<item>
			<title><![CDATA[Upgrading to Excalibur - lxdm and /boot]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=64300#p64300</link>
			<description><![CDATA[<p>It is reported in :-<br /><a href="https://dev1galaxy.org/viewtopic.php?id=7345" rel="nofollow">https://dev1galaxy.org/viewtopic.php?id=7345</a></p><p>that /boot needs to be at least 768 MB with 300 MB free.</p><p>On my machine df reports :-</p><div class="quotebox"><blockquote><div><p>Filesystem&#160; &#160; &#160; Size&#160; Used Avail Use% Mounted on<br />/dev/sdb5&#160; &#160; &#160; &#160;237M&#160; 133M&#160; &#160;87M&#160; 61% /boot</p></div></blockquote></div><p>It also reported that <span class="bbc">lxdm</span> has problems.</p><p>My first attempt at upgrading from Daedalus to Excalibur was on a virtual machine, running under Xen.<br />This was a fairly simple set up with a single partition and access was via VNC rather than lxdm.<br />The upgrade went very smoothly with nothing much to report.</p><p>The second attempt was my laptop. This had /boot as part of the root partition, so there was little difficulty in upgrading, although when I logged in through lxdm, it failed to start the panel. I was able to open a terminal from the background menu and from there I could run lxpanel, which let me carry on fairly normally.</p><p>The laptop had originally been set up with lxdm and lxde, which is how I had lxpanel available. I had later moved over to using lxQt. After some investigation I found that some package was being held back. I tried :-</p><div class="quotebox"><blockquote><div><p>apt -f install</p></div></blockquote></div><p>which provided some useful info on the problem, which seemed to be that an older version of <span class="bbc">upower</span> was installed. Unfortunately, the version number had &quot;1:&quot; in front of it and <span class="bbc">apt</span> thought that it was newer than the new version, which did not have &quot;1:&quot;. I then switched to using <span class="bbc">Synaptic</span>, as that seems to make it easy to fix. I found <span class="bbc">upower</span>, which displayed the 2 versions with the old one labelled (now) and the new one (stable). Selecting <span class="bbc">Package&gt;force version</span> I was able to select the (stable) version and then install it. It did highlight that I was downgrading it, but did do it. After that I made sure that <span class="bbc">lxQt</span> was properly installed and I am now able to log in through <span class="bbc">lxdm</span> selecting either <span class="bbc">lxde</span> or <span class="bbc">lxQt</span>.</p><p>Boot partition<br />==============</p><p>I then set about my main desktop machine. I see that <span class="bbc">/lost+found</span> is dated Sept 2013, which I take to be when I set the machine up. The machine was set up using <span class="bbc">lvm</span> to make it easy adjust the partitions and set up more partitions for virtual machines. I vaguely recall that at that time grub may not have been able to boot with a /boot partition on lvm. Probably because of that I had /boot as a real partition while root was on an lvm partition. I also gathered that now grub is able to boot off an lvm partition, so my plan was to unmount /boot and then copy its contents over to what was the /boot mount point.</p><p>I did this by booting of a USB memory stick. I downloaded a Daedalus minimal live iso and dd-ed it to the stick, checking up with :-</p><p><a href="https://pendrivelinux.com/create-bootable-usb-from-iso-using-dd/" rel="nofollow">https://pendrivelinux.com/create-bootab … -using-dd/</a></p><p>I was able to boot up and then mount root and the old /boot separately and copy over the content:-</p><div class="codebox"><pre><code>mount /dev/mapper/SSD0-root /mnt
mount /dev/sda5 /mnt/old-boot

cd /mnt/old-boot
tar -cf - . | tar -C /mnt/boot -xpBSf -</code></pre></div><p>I then set about setting up <span class="bbc">grub</span> and <span class="bbc">initramfs</span> for the new set up.</p><p>I followed these two pieces of advice :-</p><p><a href="https://www.youtube.com/watch?v=9nbuKIM78BQ" rel="nofollow">https://www.youtube.com/watch?v=9nbuKIM78BQ</a><br /><a href="https://aaronlauterer.com/blog/2021/move-grub-and-boot-to-other-disk/" rel="nofollow">https://aaronlauterer.com/blog/2021/mov … ther-disk/</a></p><p>mount your real file systems on /mnt, as described in the above links</p><div class="codebox"><pre><code>chroot /mnt
grub-install /dev/sd? #This is the actual device itself and not the root partition
                #the system seems to swap sda and sdb, especially when booting off a memory stick
                #don&#039;t get them the wrong way round. It is the device with the root partition
update-grub
update-initramfs -u -k all</code></pre></div><p>update <span class="bbc">/etc/fstab</span> by commenting out the <span class="bbc">/boot</span> partition</p><p>exit from chroot, unmount your file systems and reboot, removing USB stick.</p><p>This seemed to work nicely and I was able to boot with the /boot as part of the root partition on lvm.</p><p>I then installed <span class="bbc">usrmerge</span>, updated the <span class="bbc">sources.list</span> and proceeded with the upgrade.<br />It did report that I had run out of disk space, so I ran</p><div class="codebox"><pre><code>apt autoremove --purge
apt autoclean</code></pre></div><p>and re-ran the upgrade. This continued smoothly, although when I was watching in a different window <span class="bbc">df</span> was reporting that root was 100% full, but didn&#039;t actually run out of space. After it was all done and I had re-run the <span class="bbc">autoremove</span>&#160; and <span class="bbc">autoclean</span>, <span class="bbc">df</span> reported that there was 1.5G available on the root partition.</p><p>I am now just going round checking that everything is running correctly.</p>]]></description>
			<author><![CDATA[dummy@example.com (Geoff 42)]]></author>
			<pubDate>Mon, 15 Jun 2026 10:16:21 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=64300#p64300</guid>
		</item>
	</channel>
</rss>
