Announcement

Collapse
No announcement yet.

24.04 Installation is vastly different

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    24.04 Installation is vastly different

    I'm moving from 22.04 to 24.04. When I previously moved from 20.04 to 22.04, I was able to set up identically sized partitions and not format the /home partition, which retained it intact. When I tried that with 24.04, the installation created its own /home partition, relegating my saved partition to /media/name/etc. The system's home partition is not large enough to simply copy my old files into it. Is there a step-by-step that someone can direct me to for this iteration of Kubuntu? (I haven't lost any data; I have several external backups of my /home.)

    At this point I'm thinking that I should reinstall and specify /home of sufficient size, since I have all the partition information from 22.04. Thanks for the help.

    #2
    The installer doesn't create a home partition on its own. That hasn't changed.

    This can actually be salvaged fairly easily, though. With some info, a quick edit of your fstab will mount your original partition as your /home again.
    Then, you can delete the extra one, and resize another partition to fill the space.

    We need:
    1. the current contents of your fstab file
    2. The output of lsblk to see your partitions and current mount points, with the old home mounted and visible in Dolphin
    3. The output of sudo blkid to get us the uuid number for the correct /home

    Comment


      #3
      I did get 24.04 installed, but only by doing it Kubuntu's way. The good news is that it's up and running. The bad news is that I really wanted /home in a separate partition from the system installation. On my 22.04 system, after the grub2 core.img, EFI System Partion, and my 22.04 partition of about 30Gb (dev/nvme0n1p3), I had a /dev/nvme0n1p5 of 1.75Tb that was /home. (dev/nvme0n1p4 was swap). I would like to get back to that, but I don't know how. Or shouldn't I bother?

      fstab:
      # /etc/fstab: static file system information.
      #
      # Use 'blkid' to print the universally unique identifier for a device; this may
      # be used with UUID= as a more robust way to name devices that works even if
      # disks are added and removed. See fstab(5).
      #
      # <file system> <mount point> <type> <options> <dump> <pass>
      UUID=EB0C-969B /boot/efi vfat defaults 0 2
      UUID=a179bd6d-63ab-4406-a776-43d862e9a866 / ext4 defaults 0 1
      /swapfile swap swap defaults 0 0
      tmpfs /tmp tmpfs defaults,noatim
      e,mode=1777 0 0

      lsblk:
      NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
      loop0 7:0 0 74.2M 1 loop /snap/core22/1380
      loop1 7:1 0 4K 1 loop /snap/bare/5
      loop2 7:2 0 269.6M 1 loop /snap/firefox/4173
      loop3 7:3 0 10.7M 1 loop /snap/firmware-updater/127
      loop4 7:4 0 505.1M 1 loop /snap/gnome-42-2204/176
      loop5 7:5 0 91.7M 1 loop /snap/gtk-common-themes/1535
      loop6 7:6 0 137.3M 1 loop /snap/thunderbird/470
      loop7 7:7 0 38.7M 1 loop /snap/snapd/21465
      loop8 7:8 0 162.5M 1 loop /snap/chromium/2859
      loop9 7:9 0 66.1M 1 loop /snap/cups/1047
      sda 8:0 0 2.7T 0 disk
      └─sda1 8:1 0 2.7T 0 part
      sdb 8:16 0 465.8G 0 disk
      └─sdb1 8:17 0 465.8G 0 part
      sdc 8:32 0 3.6T 0 disk
      ├─sdc1 8:33 0 1M 0 part
      ├─sdc2 8:34 0 513M 0 part
      ├─sdc3 8:35 0 1.8T 0 part
      └─sdc4 8:36 0 1.8T 0 part /media/<account name>/Home 8-22-23
      sr0 11:0 1 1024M 0 rom
      nvme0n1 259:0 0 1.8T 0 disk
      ├─nvme0n1p1 259:1 0 300M 0 part /boot/efi
      └─nvme0n1p2 259:2 0 1.8T 0 part /var/snap/firefox/common/host-hunspell

      sudo blkid:
      /dev/nvme0n1p1: UUID="EB0C-969B" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="e4782dee
      -eb84-46c5-ba2c-66c12a6e0db2"
      /dev/nvme0n1p2: LABEL="kubuntu_2404" UUID="a179bd6d-63ab-4406-a776-43d862e9a866"
      BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="kubuntu_2404" PARTUUID="4aec183a-5dd5-
      4c27-b2fe-bc754300dbe0"
      /dev/sdb1: LABEL="HomeBackup" UUID="0b92220c-24eb-420d-bc7a-22c29f2ec944" BLOCK_
      SIZE="4096" TYPE="ext4" PARTUUID="0001982e-01"
      /dev/sda1: LABEL="HomeBackup2TB" UUID="898c8c87-1680-4392-9393-5d0d0eadb958" BLO
      CK_SIZE="4096" TYPE="ext4" PARTLABEL="HomeBackup2TB" PARTUUID="1d2d626a-f463-4d4
      3-ab0a-eef6e26e4c38"
      /dev/loop1: BLOCK_SIZE="131072" TYPE="squashfs"
      /dev/loop8: BLOCK_SIZE="131072" TYPE="squashfs"
      /dev/loop6: BLOCK_SIZE="131072" TYPE="squashfs"
      /dev/loop4: BLOCK_SIZE="131072" TYPE="squashfs"
      /dev/loop2: BLOCK_SIZE="131072" TYPE="squashfs"
      /dev/loop0: BLOCK_SIZE="131072" TYPE="squashfs"
      /dev/loop9: BLOCK_SIZE="131072" TYPE="squashfs"
      /dev/sdc2: UUID="38BA-F449" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI System P
      artition" PARTUUID="012561a9-5bb9-48a7-99ab-a729a28d573c"
      /dev/sdc3: UUID="beb14078-1e98-43b0-a503-c5c67aebca3e" BLOCK_SIZE="4096" TYPE="e
      xt4" PARTUUID="cc638d6e-79c9-457c-8413-fb7240b46e43"
      /dev/sdc1: PARTUUID="6b42957e-2db8-44aa-b6d2-639d3a24b5ec"
      /dev/sdc4: LABEL="Home 8-22-23" UUID="c6367ece-2b64-4e47-b367-ff4763a47519" BLOC
      K_SIZE="4096" TYPE="ext4" PARTLABEL="Home" PARTUUID="1e678669-268e-431d-b3ca-bed
      7d0d008ef"
      /dev/loop7: BLOCK_SIZE="131072" TYPE="squashfs"
      /dev/loop5: BLOCK_SIZE="131072" TYPE="squashfs"
      /dev/loop3: BLOCK_SIZE="131072" TYPE="squashfs"




      Comment


        #4
        You should be able to do this if you choose "Manual Partitioning" - did this not work and a new /home was created regardless?

        PS: For lsblk you can use the -e7 option to get rid of those stupid Snap loop device entries in *Ubuntu - lsblk -e7.
        Oh, and if you use lsblk -f -e7 you don't need an additional blkid to list the UUIDs.
        Last edited by Schwarzer Kater; May 22, 2024, 06:31 PM. Reason: added PS
        Debian KDE & LXQt • Kubuntu & Lubuntu • openSUSE KDE • Windows • macOS X
        Desktop: Lenovo ThinkCentre M75s • Laptop: Apple MacBook Pro 13" • and others

        get rid of Snap script (20.04 +)reinstall Snap for release-upgrade script (20.04 +)
        install traditional Firefox script (22.04 +)​ • install traditional Thunderbird script (24.04)

        Comment


          #5
          Originally posted by Don View Post
          I did get 24.04 installed, but only by doing it Kubuntu's way. The good news is that it's up and running. The bad news is that I really wanted /home in a separate partition from the system installation. On my 22.04 system, after the grub2 core.img, EFI System Partion, and my 22.04 partition of about 30Gb (dev/nvme0n1p3), I had a /dev/nvme0n1p5 of 1.75Tb that was /home. (dev/nvme0n1p4 was swap). I would like to get back to that, but I don't know how. Or shouldn't I bother?

          fstab:
          # /etc/fstab: static file system information.
          #
          # Use 'blkid' to print the universally unique identifier for a device; this may
          # be used with UUID= as a more robust way to name devices that works even if
          # disks are added and removed. See fstab(5).
          #
          # <file system> <mount point> <type> <options> <dump> <pass>
          UUID=EB0C-969B /boot/efi vfat defaults 0 2
          UUID=a179bd6d-63ab-4406-a776-43d862e9a866 / ext4 defaults 0 1
          /swapfile swap swap defaults 0 0
          tmpfs /tmp tmpfs defaults,noatim
          e,mode=1777 0 0

          lsblk:
          NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS

          sda 8:0 0 2.7T 0 disk
          └─sda1 8:1 0 2.7T 0 part
          sdb 8:16 0 465.8G 0 disk
          └─sdb1 8:17 0 465.8G 0 part
          sdc 8:32 0 3.6T 0 disk
          ├─sdc1 8:33 0 1M 0 part
          ├─sdc2 8:34 0 513M 0 part
          ├─sdc3 8:35 0 1.8T 0 part
          └─sdc4 8:36 0 1.8T 0 part /media/<account name>/Home 8-22-23
          sr0 11:0 1 1024M 0 rom
          nvme0n1 259:0 0 1.8T 0 disk
          ├─nvme0n1p1 259:1 0 300M 0 part /boot/efi
          └─nvme0n1p2 259:2 0 1.8T 0 part /var/snap/firefox/common/host-hunspell

          sudo blkid:
          /dev/nvme0n1p1: UUID="EB0C-969B" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="e4782dee
          -eb84-46c5-ba2c-66c12a6e0db2"
          /dev/nvme0n1p2: LABEL="kubuntu_2404" UUID="a179bd6d-63ab-4406-a776-43d862e9a866"
          BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="kubuntu_2404" PARTUUID="4aec183a-5dd5-
          4c27-b2fe-bc754300dbe0"
          /dev/sdb1: LABEL="HomeBackup" UUID="0b92220c-24eb-420d-bc7a-22c29f2ec944" BLOCK_
          SIZE="4096" TYPE="ext4" PARTUUID="0001982e-01"
          /dev/sda1: LABEL="HomeBackup2TB" UUID="898c8c87-1680-4392-9393-5d0d0eadb958" BLO
          CK_SIZE="4096" TYPE="ext4" PARTLABEL="HomeBackup2TB" PARTUUID="1d2d626a-f463-4d4
          3-ab0a-eef6e26e4c38"

          /dev/sdc2: UUID="38BA-F449" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI System P
          artition" PARTUUID="012561a9-5bb9-48a7-99ab-a729a28d573c"
          /dev/sdc3: UUID="beb14078-1e98-43b0-a503-c5c67aebca3e" BLOCK_SIZE="4096" TYPE="e
          xt4" PARTUUID="cc638d6e-79c9-457c-8413-fb7240b46e43"
          /dev/sdc1: PARTUUID="6b42957e-2db8-44aa-b6d2-639d3a24b5ec"
          /dev/sdc4: LABEL="Home 8-22-23" UUID="c6367ece-2b64-4e47-b367-ff4763a47519" BLOC
          K_SIZE="4096" TYPE="ext4" PARTLABEL="Home" PARTUUID="1e678669-268e-431d-b3ca-bed
          7d0d008ef"


          It can be easy enough to do to get it back as has been noted you need to get the UUID of the partition to mount as the home in the fstab.

          Mine for example.

          Code:
          root@9600k:~# cat /etc/fstab
          # /etc/fstab: static file system information.
          #
          # Use 'blkid' to print the universally unique identifier for a
          # device; this may be used with UUID= as a more robust way to name devices
          # that works even if disks are added and removed. See fstab(5).
          #
          # <file system> <mount point> <type> <options> <dump> <pass>
          # / is on /dev/nvme1n1p2 9600k machine SP NVMe
          UUID=a4410a13-b1ea-4007-b22f-6eb9e0a2ead4 / ext4 errors=remount-ro 0 1
          # /home is on /dev/nvme1n1p3 9600k machine SP NVMe
          UUID=1ba697ed-bde7-4bd3-b9f3-b47045b44585 /home ext4 defaults 0 2
          # /boot/efi is on /dev/nvme1n1p1 9600k machine SP NVMe
          UUID=FEC4-39C0 /boot/efi vfat umask=0077 0 1
          # use swapfile instead of partition
          /swapfile none swap sw 0 0
          
          ​
          Code:
          root@9600k:~# blkid | grep nvme1
          /dev/nvme1n1p2: LABEL="SPNVMERoot" UUID="a4410a13-b1ea-4007-b22f-6eb9e0a2ead4" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="Linux filesystem" PARTUUID="f979d6b1-0c46-4357-88b3-6afd8e25dfe5"
          /dev/nvme1n1p3: LABEL="SPNVMEHome" UUID="1ba697ed-bde7-4bd3-b9f3-b47045b44585" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="Linux filesystem" PARTUUID="8854aa17-12b1-464f-9abf-a686e7d64b6b"
          /dev/nvme1n1p1: SEC_TYPE="msdos" LABEL_FATBOOT="SPNVMEEFI" LABEL="SPNVMEEFI" UUID="FEC4-39C0" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="254da66f-ea2b-43db-ab14-480480308d14"
          ​


          Your output above does not show the old home use sudo blkid |grep nvme to get it then use a line similar to mine assuming ext4 for the filesystem.
          You may want to mount the partition first to confirm it has the files you want there sudo mkdir /tmp/home, sudo mount /dev/nvme0n1p5 /tmp/home and finally ls -l /tmp/home/ where it should show you the name of your user account which contains all your old files. Once you confirm everything is there and you have edited your fstab to create a home entry for the partition reboot and it should all be back to the way you want it.

          Comment


            #6
            Originally posted by Don View Post
            └─sdc4 8:36 0 1.8T 0 part /media/<account name>/Home 8-22-23
            So this is your previous /home partition, on the other drive from your currently running OS on the nvme SSD.
            You want to use this as the /home for this currently running OS, correct?
            And inside this directory, (/media/account_name/Home​) the only directory you see when you enter it is <account_name>, correct?

            So the tree looks like: /media/ ---> /account_name/ --->/Home​/ --->- /account_name/ as the only dir or file seen?


            if so:
            Originally posted by Don;n679587[CODE
            ]/dev/sdc4: LABEL="Home 8-22-23" UUID="c6367ece-2b64-4e47-b367-ff4763a47519"[/CODE] B
            This gives us the UUID to use in the fstab.

            So, add this line to the bottom of it:

            Code:
            UUID=c6367ece-2b64-4e47-b367-ff4763a47519 /home ext4 defaults 0 2
            Save the file.

            Next, rename the existing /home dir and create a new one for the mount point:
            Code:
            sudo mv /home /home_backup && sudo mkdir /home
            This preserves the files in the new home, just in case, or you want to access to any files there.

            Reboot, and your previous home should be in use, with all your desktop settings and data.
            you can delete /home_backup if youi don't want it.


            Source reference for migrating a /home:
            https://help.ubuntu.com/community/Pa...ng/Home/Moving
            and this one is good as well
            https://help.ubuntu.com/community/Pa...ng/Home/Moving

            Comment

            Working...
            X