Ignore this post if you are happy with the current resolution to your issue. On Sat, 20 May 2023 18:17:56 -0600 home user <mattisonw@xxxxxxxxxxx> wrote: > On 5/20/23 3:03 PM, Patrick O'Callaghan wrote: > > On Sun, 2023-05-21 at 04:12 +0930, Tim via users wrote: > >> On Sat, 2023-05-20 at 17:07 +0100, Patrick O'Callaghan wrote: > >>> Apologies if you've already considered this, but I wonder why you > >>> don't > >>> just do a fresh install of F38 (or F37). It would have been much > >>> quicker than all the futzing around you've had to do, and you > >>> could have seized the opportunity to expand the /boot partition > >>> to 1GB. > >>> > >>> My system is probably about as old as yours, and I did this a year > >>> or > >>> two ago when BTRFS became the default filesystem (though I was > >>> already > >>> using it for /home). Haven't regretted it since. > >> > >> My sentiments, exactly. Upgrades in place were a pain when I did > >> them > >> donkey's years ago, and I repeatedly see threads like this on this > >> list > >> (despite someone else's thoughts that they don't). > >> > >> Sure, if things go fine there's an ease of doing nothing more than > >> an update. But when things go haywire, and they often do > >> (immediately or > >> later on), there's an awful lot of housekeeping to go through. > >> > >> And, there's more than just updating files with newer versions. > >> Their > >> can be filesystem changes, different partitioning schemes, etc. > >> Some of which are very difficult to manage in an update over the > >> top. > > > > Just to clarify: I almost always do an upgrade. The reinstall I > > mention was probably the first one I'd done in over 5 years at the > > time. I don't normally have any problems, but little by little a > > lot of cruft tends to accumulate so once in a while it's good to > > house-clean. > > > > poc > > (sigh) > I have multiple reasons for not going that route. > - This is my only computer; no cell phone; no laptop/notebook; no > internet access any other practical way. > - For private reasons, I cannot get anything else. > - This is a dual-boot workstation; the other OS being windows-7. > - I have no sys.admin, OS, file system, etc. training or experience. > So for me, re-installing is too risky and too difficult. I had > severe difficulty with the original install 10 years ago; I still > don't know how that managed to finally work. If I try to re-install > and get into trouble, I would have no way of getting help. This is a fragile situation waiting for a disaster. Some suggestions: Earlier, you posted this as your layout for the fedora disk. """ bash.7[~]: df Filesystem 1K-blocks Used Available Use% Mounted on devtmpfs 4096 0 4096 0% /dev tmpfs 8154012 0 8154012 0% /dev/shm tmpfs 3261608 1696 3259912 1% /run /dev/sda6 51422028 27967968 20816236 58% / tmpfs 8154012 88 8153924 1% /tmp /dev/sda3 485348 379984 75668 84% /boot /dev/sda7 947550748 19685980 879705128 3% /home tmpfs 1630800 3900 1626900 1% /run/user/1001 """ 1. Caveat: This is a complex procedure, and from your past posts of your skill level, maybe too risky for you to do. There is lots of room in / for /boot. Right now you are using a separate /boot, but there is a way to use a /boot under the root partition (currently masked by the separate /boot partition), and you would no longer have this problem. Others can critique the algorithm below for errors or improvements. Have fedora running as you currently do, replicate the contents of the current /boot partition into another temporary directory like /root/boot_copy or /home/[your login]/boot_copy I can't remember if rsync will create a target directory if it doesn't exist, so it might complain unless you create the directory first. rsync -a -i -u -v -x -A -H -X /boot/ /root/boot_copy or rsync -a -i -u -v -x -A -H -X /boot/ /home/[your login]/boot_copy then unmount /boot umount /boot which should expose the /boot under /dev/sda6 which is the root filesystem. Now copy the earlier copy of boot you made into the /boot under /dev/sda6 rsync -a -i -u -v -x -A -H -X /root/boot_copy/ /boot or rsync -a -i -u -v -x -A -H -X /home/[your login]/boot_copy/ /boot Once this is done, and you confirm that all the files are there, have proper permissions, and have proper SElinux context, ls -nZ /boot compared to ls -nZ /root/boot_copy or ls -nZ /home/[your login]/boot_copy and all subdirectories of /boot e.g. ls -nZ /boot/grub2 ls -nZ /boot/loader/entries if you have an efi partition, though I think you said legacy, and it doesn't show in the df ls -nZ /boot/efi/EFI/fedora edit /etc/fstab and comment the line for /dev/sda3, the current separate boot partition. Put a # at the start of the line. You should now be able to reboot, and the system will boot from the /boot under /dev/sda6 If it does, you have no more space issues on /boot as it is now on your root partition, so there is lots of space. If there are problems, at the failure prompt, just edit the fstab nano /etc/fstab and uncomment the line for the current separate /boot partition and save the file. Your system will return to the functionality it has now on reboot. 2. If your system can handle another internal hard drive, a 250 GB or 500 GB drive can be cheap and suit your needs. A 1 TB drive is about $US 50. Then you can either copy your existing Fedora system to the new drive, or install the latest Fedora version to get a working backup so you aren't as vulnerable to a crash in your current system. Don't use a separate /boot on the new install, and link to the current home, so you don't need to copy it. You *can* also copy over your home partition since you are using almost none of it. You can continue to use ext4 or go with the default btrfs on the install. 3. If your system can't handle another internal drive, I think external USB drives are also pretty cheap. 4. If your system can handle it, you could also buy an SSD instead of a sata drive, and use it for the new install, and get a noticeable speedup as part of the deal. > I made multiple tries at making a live USB very recently. They all > failed. I opened a thread on this list about that; the only thing I > got from that was that the sticks were good. I know from other tasks > that the ports and other hardware are also good. Since you are using an older system, it has a CD burner, right? I have found that it is easy to just use the small netinstall disk to burn a CD, and install directly from the internet. It should work with USB, but if you had problems, and you don't have a burner, this suggestion is probably off the table as an option. You can do it two ways, just install a bare minimum system, and then boot in and install the rest of what you want using dnf at the command line. Or, select the groups and packages you want to install during install, and they will automatically install from the repositories. If you want to stick with ext4, you will have to use custom partitioning, because the default will be btrfs. I think the netinstall CD also has a rescue mode, so you can mount and work on your existing installed system by booting it. Before you do any other ameliorations, you could try this to see if it will boot for you. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
