How should I set up my partitions? About to reinstall

Good Afternoon,

I have got into a mess. I have several security updates for the linux kernel 'opensuse-SLE.15.3.2022.370(1) waiting to install, but the installation fails. I would like to reinstall Leap 15.3, but what should my partitions be? (as I suspect my partitions are part of the problem)

https://www.flickr.com/photos/39355512@N00/51884089125/in/dateposted-public/

https://www.flickr.com/photos/39355512@N00/51882474562/in/dateposted-public/

https://www.flickr.com/photos/39355512@N00/51882474562/in/dateposted-public/https://www.flickr.com/photos/39355512@N00/51884089125/in/dateposted-public/
Should I have a separate boot partition?

Thank you in advance.

Shouldn’t you first try to solve the problem you have before just do a blunt re-installation?

So we have some screen shot (btw, we have https://susepaste.org/ to avoid commercial sites for this), but we do not know what you did. I doubt this is when you do YaST > Software > Online Update. So please tell us what you did for that update.

Also I wonder about that SLE mentioned. Better show your repos: (as root)

zypper lr -d

And of course show your present partitioning so we can comment on that if it is really so bad as you seem to think: (as root)

lsblk -f

Yes, I should try to solve the problem.

#  | Alias                       | Name                                                                                      
  | Enabled | GPG Check | Refresh | Priority | Type   | URI                                                                  
                 | Service
---+-----------------------------+-------------------------------------------------------------------------------------------
--+---------+-----------+---------+----------+--------+----------------------------------------------------------------------
-----------------+--------
 1 | google-chrome               | google-chrome                                                                             
  | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | https://dl.google.com/linux/chrome/rpm/stable/x86_64                 
                 |  
 2 | openSUSE-Leap-15.3-1        | openSUSE-Leap-15.3-1                                                                      
  | No      | ----      | ----    |   99     | rpm-md | hd:/?device=/dev/disk/by-id/usb-KIOXIA_TransMemory_0022CFF653F1C4C0E3
1136B6-0:0-part2 |  
 3 | repo-backports-debug-update | Update repository with updates for openSUSE Leap debuginfo packages from openSUSE Backport
s | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/update/leap/15.3/backports_debug/       
                 |  
 4 | repo-backports-update       | Update repository of openSUSE Backports                                                   
  | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/leap/15.3/backports/             
                 |  
 5 | repo-debug                  | Debug Repository                                                                          
  | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/debug/distribution/leap/15.3/repo/oss/  
                 |  
 6 | repo-debug-non-oss          | Debug Repository (Non-OSS)                                                                
  | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/debug/distribution/leap/15.3/repo/non-os
s/               |  
 7 | repo-debug-update           | Update Repository (Debug)                                                                 
  | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/debug/update/leap/15.3/oss/             
                 |  
 8 | repo-debug-update-non-oss   | Update Repository (Debug, Non-OSS)                                                        
  | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/debug/update/leap/15.3/non-oss/         
                 |  
 9 | repo-non-oss                | Non-OSS Repository                                                                        
  | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/distribution/leap/15.3/repo/non-oss/    
                 |  
10 | repo-oss                    | Main Repository                                                                           
  | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/distribution/leap/15.3/repo/oss/        
                 |  
11 | repo-sle-debug-update       | Update repository with debuginfo for updates from SUSE Linux Enterprise 15                
  | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/debug/update/leap/15.3/sle/             
                 |  
12 | repo-sle-update             | Update repository with updates from SUSE Linux Enterprise 15                              
  | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/leap/15.3/sle/                   
                 |  
13 | repo-source                 | Source Repository                                                                         
  | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/source/distribution/leap/15.3/repo/oss/ 
                 |  
14 | repo-update                 | Main Update Repository                                                                    
  | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/leap/15.3/oss                    
                 |  
15 | repo-update-non-oss         | Update Repository (Non-Oss)                                                               
  | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/leap/15.3/non-oss/ 

NAME   FSTYPE FSVER LABEL  UUID                                 FSAVAIL FSUSE% MOUNTPOINT
sda                                                                             
├─sda1 ext2   1.0   System 426a2375-795f-4f3f-8086-06dabedd4872   92.2M    47% /boot
├─sda2 ntfs         OS     FA581FAE581F6921                        5.5G    89% /run/media/janets/OS
├─sda3                                                                          
├─sda5 btrfs               fff0077e-b8dc-4f1b-a2ef-6cd600ba2608    4.4G    55% /
├─sda6 swap   1            ae01c463-94fe-4116-87e8-61f4eda285b7                [SWAP]
├─sda7 xfs                 6012020b-8988-456d-bfff-ae23a4158b35    2.3G    98% /home
└─sda8 xfs                 6911b452-cc02-4466-a69d-003d22691a68  105.8G     0% /BACKUP
sr0                

SUSE Paste
SUSE Paste

I thought I needed more space so deleted a kernel version and replaced with the most recent, but I don’t think that was the right thing to do.

You still did not explain what you did to update. We have some messages from what you did, but what did you do???
To make a shortcut here, can you do and post:

zypper up

You can always cancel that when problems arise.

Your repo list looks fine to me.

Your partitioning is MS-DOS/MBR (and thus no EFI boot) but that should not be a problem.

Sizes are a bit strange.

  • sda5 is your / partition, 55% is in use, and as there is 4.4G left, thus size is ~9GB. That is not to much. I have a rather normal installation and that uses ~12GB. Thus I do not quite understand how you managed that. I assume 40GB is the recommendation for a Btrfs /
  • sda7 is your /home, 98% full. That is indeed critical
  • sda8 is /BACKUP whatever that may be for. Seems to be empty.

The last two mean that it is probably (depends on a few things) rather easy to increase /home and to make /Backup smaller.

Can you also please (to make sure I do not misinterpret) post also

fdisk -l

PS

I see your / is ~14GB, but that is still much lower then the 40GB that is the default as far as I know.

I have about 6 updates, ‘security updates for the linux kernel.’ So it hasn’t updated in a while.

zypper up
Retrieving repository 'Update repository with updates from SUSE Linux Enterprise 15' metadata .........................[done]
Building repository 'Update repository with updates from SUSE Linux Enterprise 15' cache ..............................[done]
Loading repository data...
Reading installed packages...

The following package update will NOT be installed:
  kernel-default-base

The following 7 packages are going to be upgraded:
  cyrus-sasl cyrus-sasl-crammd5 cyrus-sasl-digestmd5 cyrus-sasl-gssapi cyrus-sasl-plain google-chrome-stable libsasl2-3

The following 4 NEW packages are going to be installed:
  kernel-default-5.3.18-150300.59.49.1 kernel-default-extra-5.3.18-150300.59.49.1
  kernel-default-optional-5.3.18-150300.59.49.1 yast2-trans

The following package is going to be REMOVED:
  yast2-trans-en

The following package requires a system reboot:
  kernel-default-5.3.18-150300.59.49.1

7 packages to upgrade, 4 new, 1 to remove.
Overall download size: 119.3 MiB. Already cached: 64.9 MiB. After the operation, additional 168.1 MiB will be used.

    Note: System reboot required.
**Continue? [y/n/v/...? shows all options] (y):**

I’m not sure of the correct response?

Your repo list looks fine to me.

Your partitioning is MS-DOS/MBR (and thus no EFI boot) but that should not be a problem.

Sizes are a bit strange.

  • sda5 is your / partition, 55% is in use, and as there is 4.4G left, thus size is ~9GB. That is not to much. I have a rather normal installation and that uses ~12GB. Thus I do not quite understand how you managed that. I assume 40GB is the recommendation for a Btrfs /
  • sda7 is your /home, 98% full. That is indeed critical
  • sda8 is /BACKUP whatever that may be for. Seems to be empty.

The last two mean that it is probably (depends on a few things) rather easy to increase /home and to make /Backup smaller.

Can you also please (to make sure I do not misinterpret) post also

fdisk -l
fdisk -l
**Disk /dev/sda: 298.09 GiB, 320072933376 bytes, 625142448 sectors**
Disk model: TOSHIBA MK3261GS
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: 0xde2605c2

**Device****Boot****    Start****      End****  Sectors****  Size****Id****Type**
/dev/sda1  *         2048    411647    409600   200M 83 Linux
/dev/sda2          411648 109463551 109051904    52G  7 HPFS/NTFS/exFAT
/dev/sda3       131483648 625139711 493656064 235.4G  5 Extended
/dev/sda5       131485696 162205695  30720000  14.6G 83 Linux
/dev/sda6       162207744 170399743   8192000   3.9G 82 Linux swap / Solaris
/dev/sda7       170401792 402827263 232425472 110.8G 83 Linux
/dev/sda8       402829312 625127423 222298112   106G 83 Linux


That is not too many. I update once a week and often have more.

I do not see problems. Thus : y (or simply the Return key).

**y): **y
Retrieving package google-chrome-stable-98.0.4758.102-1.x86_64                         (1/11),  86.5 MiB (277.0 MiB unpacked)
Retrieving: google-chrome-stable-98.0.4758.102-1.x86_64.rpm ...............................................[done (1.1 MiB/s)]
Retrieving package yast2-trans-84.87.20210502.7b34dbceae-1.1.noarch                    (2/11), 311.6 KiB (    0   B unpacked)
Retrieving: yast2-trans-84.87.20210502.7b34dbceae-1.1.noarch.rpm ........................................[done (670.7 KiB/s)]
In cache kernel-default-5.3.18-150300.59.49.1.x86_64.rpm                               (3/11),  64.9 MiB (148.8 MiB unpacked)
Retrieving package libsasl2-3-2.1.27-150300.4.3.1.x86_64                               (4/11),  57.7 KiB (115.7 KiB unpacked)
Retrieving delta: ./x86_64/libsasl2-3-2.1.27-2.2_150300.4.3.1.x86_64.drpm, 8.3 KiB
Retrieving: libsasl2-3-2.1.27-2.2_150300.4.3.1.x86_64.drpm ............................................................[done]
Applying delta: ./libsasl2-3-2.1.27-2.2_150300.4.3.1.x86_64.drpm ......................................................[done]
Retrieving package kernel-default-extra-5.3.18-150300.59.49.1.x86_64                   (5/11),  20.2 MiB ( 13.5 MiB unpacked)
Retrieving: kernel-default-extra-5.3.18-150300.59.49.1.x86_64.rpm ......................................[done (1017.9 KiB/s)]
Retrieving package cyrus-sasl-2.1.27-150300.4.3.1.x86_64                               (6/11),  54.3 KiB (155.1 KiB unpacked)
Retrieving delta: ./x86_64/cyrus-sasl-2.1.27-2.2_150300.4.3.1.x86_64.drpm, 18.3 KiB
Retrieving: cyrus-sasl-2.1.27-2.2_150300.4.3.1.x86_64.drpm ............................................................[done]
Applying delta: ./cyrus-sasl-2.1.27-2.2_150300.4.3.1.x86_64.drpm ......................................................[done]
Retrieving package kernel-default-optional-5.3.18-150300.59.49.1.x86_64                (7/11),  12.1 MiB (  5.8 MiB unpacked)
Retrieving: kernel-default-optional-5.3.18-150300.59.49.1.x86_64.rpm ......................................[done (1.1 MiB/s)]
Retrieving package cyrus-sasl-plain-2.1.27-150300.4.3.1.x86_64                         (8/11),  19.0 KiB ( 18.4 KiB unpacked)
Retrieving delta: ./x86_64/cyrus-sasl-plain-2.1.27-2.2_150300.4.3.1.x86_64.drpm, 8.3 KiB
Retrieving: cyrus-sasl-plain-2.1.27-2.2_150300.4.3.1.x86_64.drpm ......................................................[done]
Applying delta: ./cyrus-sasl-plain-2.1.27-2.2_150300.4.3.1.x86_64.drpm ................................................[done]
Retrieving package cyrus-sasl-gssapi-2.1.27-150300.4.3.1.x86_64                        (9/11),  25.1 KiB ( 34.8 KiB unpacked)
Retrieving delta: ./x86_64/cyrus-sasl-gssapi-2.1.27-2.2_150300.4.3.1.x86_64.drpm, 8.4 KiB
Retrieving: cyrus-sasl-gssapi-2.1.27-2.2_150300.4.3.1.x86_64.drpm .....................................................[done]
Applying delta: ./cyrus-sasl-gssapi-2.1.27-2.2_150300.4.3.1.x86_64.drpm ...............................................[done]
Retrieving package cyrus-sasl-digestmd5-2.1.27-150300.4.3.1.x86_64                    (10/11),  34.8 KiB ( 55.0 KiB unpacked)
Retrieving delta: ./x86_64/cyrus-sasl-digestmd5-2.1.27-2.2_150300.4.3.1.x86_64.drpm, 8.4 KiB
Retrieving: cyrus-sasl-digestmd5-2.1.27-2.2_150300.4.3.1.x86_64.drpm ..................................................[done]
Applying delta: ./cyrus-sasl-digestmd5-2.1.27-2.2_150300.4.3.1.x86_64.drpm ............................................[done]
Retrieving package cyrus-sasl-crammd5-2.1.27-150300.4.3.1.x86_64                      (11/11),  19.8 KiB ( 22.5 KiB unpacked)
Retrieving delta: ./x86_64/cyrus-sasl-crammd5-2.1.27-2.2_150300.4.3.1.x86_64.drpm, 8.3 KiB
Retrieving: cyrus-sasl-crammd5-2.1.27-2.2_150300.4.3.1.x86_64.drpm ....................................................[done]
Applying delta: ./cyrus-sasl-crammd5-2.1.27-2.2_150300.4.3.1.x86_64.drpm ..............................................[done]

Checking for file conflicts: ..........................................................................................[done]
( 1/11) Installing: google-chrome-stable-98.0.4758.102-1.x86_64 .......................................................[done]
( 2/11) Installing: yast2-trans-84.87.20210502.7b34dbceae-1.1.noarch ..................................................[done]
        installing package kernel-default-5.3.18-150300.59.49.1.x86_64 needs 22MB on the /boot filesystem
( 3/11) Installing: kernel-default-5.3.18-150300.59.49.1.x86_64 ......................................................[error]
Installation of kernel-default-5.3.18-150300.59.49.1.x86_64 failed:
Error: Subprocess failed. Error: RPM failed: Command exited with status 1.                                                   
**Abort, retry, ignore? [a/r/i] (a): **


Ah! Now you can see my problem. ‘needs 22MB on the /boot filesystem’ So I thought I needed to sort out my partitions by reinstalling, but what size should they be? Next time I will have 40 gb for root, but what size should /boot be? Or should it not be separate?

I am not using Btrfs, but I assume you do not need a separate /boot for it.

How did you get to this partition lay-out in the first place? When this is a proposal as done by the installer, it is a strange one.

If using BTRFS then boot partition is not recommended. since it reduces the usefulness of snapper at boot. 40 gig is a minimum for BTRFS installations. A full home is also problematic

i have been using these partitions for a long time, it has varied a little over each OpenSuse version.

So just the Windoze partition, /root, /swap, /home and /backup then?

I will about the zypper then?

It is NOT /root, it is /.

We can not decide for you if you need a Windows partition, nor if you need a /backup one, or a /BACKUP one (as it is apparently mounted now).

The present default installation has not separate /home, but again, that is up to you.

I don’t use the Windoze partition, it is just there if I need a repair on my laptop. The man only does windoze,

I think I lack understanding of partitions. I thought that if part of a disk fails, but it is in a partition you can save the other partitions? Also if /home is a separate partition then it is easier to copy it across when you back up your information or want to do a fresh install?

hecking for file conflicts: ..........................................................................................[done]( 1/11) Installing: google-chrome-stable-98.0.4758.102-1.x86_64 .......................................................[done]
( 2/11) Installing: yast2-trans-84.87.20210502.7b34dbceae-1.1.noarch ..................................................[done]
        installing package kernel-default-5.3.18-150300.59.49.1.x86_64 needs 22MB on the /boot filesystem
( 3/11) Installing: kernel-default-5.3.18-150300.59.49.1.x86_64 ......................................................[error]
Installation of kernel-default-5.3.18-150300.59.49.1.x86_64 failed:
Error: Subprocess failed. Error: RPM failed: Command exited with status 1.                               
ab**ort, retry, ignore? [a/r/i] (a): **

I am still trying to work out what to do about this? Did I miss your response?

Do you currently have more than one kernel installed? If yes, uninstall the oldest one, then run zypper up again to get the newer one installed. If more than two, optionally delete all except the one that is running. Another way would be to delete snapshot(s) that free up at least 22MB. If you have persistent journal enabled, check to see if there are files in /var/log/journal/* more than 10 in number or a month old or older in age, and delete the old ones to free more space. .xz files in /var/log/ aren’t needed either. If there are rpms in /var/cache/zypp/packages/*, remove those too. Use the utility ncdu when you wish to easily discover where space is used.

@nappy501
Do not forget we are now on two tracks in this thread. One is about the problem you encountered. The other is about an advice on how to partition when a reinstall is done.

I try not to mix answers to those two to avoid confusion.

I also think the suggestions of @mrmazda about your current problem are worthwhile and consider that as the next step in that part of the thread.

On to the partitioning.

First about what you call a Windoze partition. I know it contains an NTFS (thus not Linux native) file system. I do not know what it is. It is mounted in your post #3 as a personal file system for user janet. If you do not know what that user is using it for then ask that user. Again you, as system manager, should decide if you want to keep it on fresh installation or not.

Same about the xfs file system mounted in post #3 on /BACKUP. The difference being that in this case it is not a normal user, but the system manager that created the mount point and used it (probably in /etc/fstab), so you, as system manager should know if you need it and for what. Also if you need it in the future and how large it has to be. When you need advice on this you first have to explain your goal because we can not read your mind.

About separate /home file system. Yes, when you have /home as a separate file system, it will be easier to e.g. completely recreate your root file system (e.g. on a very fresh installation) without touching all (user data) in /home. That is an advantage. And until not long ago that was the default proposed partitioning on installation. I do not know why that has changed. Maybe because upgrade from one Leap version to the other is now easily done online without creating a fresh root partition, the need to have a separate /home has diminished. Also now /home is inside the Btrfs root partition, which may have advantages when using snapshot. But I can only guess there because I do not use Btrfs and did not dig into the documentation/features/etc. (still have separate / and /home, both on ext4).
Again, it is you that decides if you want a separate /home, and when yes, how large. And when not then add the size you need for /home to the size that is recommended for a Btrfs / (40GB) when creating the root file system.

When you are a bit confused about partitions, file systems (and the difference), etc., there is: https://en.opensuse.org/SDB%3ABasics_of_partitions,_filesystems,_mount_points. (And when still confused about some aspects there you are welcome to ask here).

And it is indeed true that when a disk fails somewhere in one partition, making the file system there unusable, then you will be able to make as soon as possible a copy/backup of the still functioning partitions as part of your recovery action. But, as you never know what will break down, I think a good backup/recovery procedure (at least to another disk and possibly to another system) will cover that.

I think I now answered the majority of your questions as put above. Please repeat a question if I missed it.

I only have one kernel installed SUSE Paste
But zypper up gave the error I posted.
I don’t know how to delete snapshots or how to check for persistent journal.

The image of YaST shows unneeded packages that can be removed to free space to allow installation of the 59.49 kernel:

  • kernel-default-base
  • kernel-firmware-all
  • kernel-firmware* (with 6 or fewer possible exceptions, depending on your actual hardware; around 30 some packages; e.g. kernel-firmware-amdgpu keep for AMD GPU users, kernel-firmware-nvidia keep for NVidia users, kernel-firmware-iwlwifi for WiFi, kernel-firmware-i915 for Intel IGPs, kernel-firmware-network)
  • kernel-default-extra (most people don’t need this; some do, depending on hardware, e.g. nvidia users)
  • kernel-default-optional (most people don’t need this; some do, depending on hardware, e.g. OS/2 multibooters)

Given you were able to provide a 1354x674 screenshot, do you actually have a problem, or is it just the lack of space to update your kernel?

Persistent journal, if it exists, is apparent by existence of /var/log/journal/.

Snapshotting I cannot help with.