EFI boot failing with system bios warning and booting Bad magic number in super-block

OK, I now have my system BIOS accessible again. My first objective is now to be able to boot to UEFI rescue mode. I have the following options in System Settings > Devices and I/O Ports

Configure SATA as:- default is IDE, other options are RAID and AHCI
Configure IDE mode:- default is Native mode, other option is Compatability
System CDROM/DVD:- default is Enable
Active Video:- default is Add-in Device, other option is Onboard Device
Interrupt Round Robin defaults to Disable, other option is Enable
Scheme
Enable / Disable Onboard Device(s) This only selects Ethernet which is Enabled
Enable / Disable Adapter Option ROM Support This controls Legacy and UEFI-compliant adapter support. Disabling UEFI/Legacy support may adversely affect preboot/boot functions.
Selecting this brings me to the Ethernet and all Slots with options to Enable / Disable Legacy Option ROM(s) and Enable / Disable UEFI Options ROM(s).
These have all defaulted to Enabled now but I cannot be confident this is how they used to be.

Should I try Disabling the Legacy Options. I believe that this is what I had tried earlier but cannot be sure.

I also have:-

System Settings > Legacy Support:-
Force Legacy Video on Boot which defaults to Enable and is required if the OS does not support UEFI video output standards.

I do not know how to answer this now!

Rehook INT 19h defaults to Disable - Prevents devices from taking control of the boot process.

This might be where I have had a problem. How should I have it set if I am to be able to boot UEFI rescue ?

Legacy Thunk Support defaults to Enable, Enable or Disabe UEFI to interact with PCI storage devices that are non UEFI compliant. I am not sure how to answer now.

I also have:-

System Settings > Adapters and UEFI Drivers which gives me a list:- Available Adapters and Drivers.
Two of these are Broadcom Gigabit Ethernet Drivers and the last is an LSI EFI SAS Driver which has three lines:-
| -PciRoot (0x0)/Pci (0x9,0x0)/Pci (0x0,0x0)
| - | -PciRoot (0x0)/Pci (0x9, 0x0)/Pci (0x0, 0x0)/Ctrl (0 . x0)
| - | -PciRoot (0x0)/Pci (0x9, 0x0)/Pci (0x0, 0x0)/Ctrl (0 . x1)

All of these if selected take me to the hardware RAID controller and the disk array of 7 + 1 hot spare.

Please could you advise what if any options I should change please?

If not set to AHCI, you may have a problem with I/O speed or ability to boot. You’ll have to read your manual about when selecting RAID may be appropriate.

Most users have no need of any option ROMs. Those are usually on add-in cards that may optionally be involved in the boot process.

I don’t know either. If no boot menu appears when expected, this would be candidate to try changing.

I don’t remember ever needing to change an INT 19h default setting. It’s not something I’ve ever knowingly used.

This one might be the CSM on/off switch. Non-UEFI compliant basically means legacy. CSM means compatibility support module, fancy words that translate to legacy BIOS support mode, which we want off so as to stick with UEFI booting only.

Hi and many thanks once more. A quick summary of progress:
On investigation Sata did not offer options, only IDE.

I have disabled most Legacy support where options exist but booting USB distro Rescue system still tells me no efi available.

Thinking outside the box for a minute, some questions:-

Is it possible to reinstall Leap OS on my system without erasing my data which is all on the NVME /home partitions? If so can I create new efi and boot files on an USB and connect to grub on the nvme? At present the boot and efi files are on /dev/sda1 on a fat16 file system and it seems these have been damaged.

There may even be repair apps which could fix this at least temporarily as there is plenty of space available on the partition.

FYI my RAID is hardware raid and fully backed up to NAS or cloud. I should not need to touch this.

Are any of these options worth pursuing?

Please describe each option presented when you have opened the BBS menu while your USB rescue media is attached. IME, in CSM support mode, each bootable device will have two (or more) options for booting, with one of them labeled EFI or UEFI. If you cannot find a way to boot anything in UEFI mode, or disable CSM booting, you may need to perform the “UEFI boot recovery” in table 4.

Until you can get a handle on CSM vs. UEFI boot control, I would delay any thoughts of replacing or installing another operating system. No installation in which you’re deciding what mounts or not and where will force formatting of a non-root volume without your consent. No data on your data filesystem(s) would be lost unless you errantly select it/them for formatting.

What evidence is there of this “damage”. I often see Linux boot messages complaining that FAT filesystem(s) are in need of checking, but I ignore them until such time as I discover a genuine problem with them.

Hi, I may be losing the plot but AFAIK here BBS refers to BIOS Boot Specification and I can only open this menu by using F1 at system start. Is this correct?
If I am correct I cannot do much about the USB rescue system because the rescue system can only start after I have booted from the USB which I must select from the options available once POST has finished. I have to select F12 and then can select from all the options available which is different from the boot options available in the BIOS because the F12 list includes devices not included in the BIOS.

The boot options order shown in the BIOS available at present has changed from when I started this trouble shooting exercise and most significantly I now have the following:-

opensuse-secureboot HD(1,GPT,XXXXX)/\EFI\opensuse\shim.efi

grub-secureboot HD(1,GPT,XXXXX)/\EFI\oldgrub\shim.efi

opensuse-secureboot HD(1,GPT,XXXXX)/\EFI\grub\shim.efi

Unfortunately I cannot boot from any of these to get my system back. All I get is the minimum grub prompt.

It does seem that my system has attempted a repair, hence “oldgrub” but then?

I accept that I should delay trying anything else until I have your further advice but the only evidence of damage I have is the line in my title of this thread and I cannot now recall how I received this prompt.

After all my failed trials I have reset the BIOS defaults and even then can no longer boot from the USB installation system but I can still boot to CD so have run this and selected Rescue system. At no time have I been given the option to run UEFI rescue but I am now at the rescue prompt. It is clear the efi and boot files are on the fat16 partition at /dev/sda1.

I am not sure what more I can try but it seems all the components are still present if not working!

Your system is prepared to boot with UEFI Secure Boot (shim.efi).

Check your UEFI BIOS and enable (UEFI) Secure Boot mode.

Check the partition table:

# fdisk -l /dev/sda
Disk /dev/sda: 476.94 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: Samsung SSD 850 
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: gpt
Disk identifier: C95B18CE-8F41-354A-9D66-A2D2DEE4F7D2

Device         Start        End   Sectors   Size Type
/dev/sda1       2048   25167871  25165824    12G Linux root (x86-64)
/dev/sda2   25167872   25782271    614400   300M EFI System
/dev/sda3   25782272  962545663 936763392 446.7G Linux home
/dev/sda4  962545664 1000215182  37669519    18G Linux swap

A GPT partition table is mandatory for UEFI Secure Boot (“disklabel type: gpt”).

Follow this guide lines to reinstall grub2:

Use a translator like deepl.com to translate from german to english.

Each BIOS is different, made for a specific motherboard or series of related motherboards. We can’t know what yours offers or expects that you don’t share here. We don’t know who made your computer or motherboard. The 3 pages of manual you uploaded provide few clues, other than it’s a server motherboard. The following is what I know about BBS hotkeys:

* Abit		F9
* Acer		F12 or ESC or F9
* ASRock	F11
* Asus		F8
* Biostar	F9
* Dell		F12
* DFI		ESC
* eCS		F12 or F10
* eMachines	F10
* EVGA		F7
* Gateway	F12 or F10
* Gigabyte	F12
* HP/Compaq	F9  or ESC or ESC,F9
* Intel		F10
* Lenovo	F12 or F8 or F10
* MSI		F11
* Shuttle	ESC or F11 or F7
* Toshiba	F12

F1 is one of the common BIOS setup entry keys. In many BIOS, setup provides an alternate route to the BBS menu.

AFAICT, GrandDixence2 is right that, due to the content in your ESP, you need to enable secure boot in BIOS for access to installed OS.

Hi and many thanks. Whatever I try I cannot get efibootmgr -v to give me any positive response. The BBS screen is brought up by F1 and the system is IBM, now Lenovo however I cannot find any way to boot my USB installation into efi rescue mode.
I am sure all the information is available and many thanks to GrandDixence2 for his German contribution. I am still reading through all the info but unless I can run rescue system in efi I am stuck.

I have also had a look at my system using SystemRescue which cuts through the problems I have with the BIOS and have access to everything there so will see what I find. Will return when I have made some progress.

I have spent some more time on this problem as I have been able to use my backup machine pro tem.
I still have not found any errors in my boot setup (F1 on IBM) and they are set exactly the same as my backup machine which is working normally but for reasons I cannot fathom when I boot from an USB installation DVD I cannot get anything from efibootmgr.
I can however boot to the SystemRescue DVD from the DVD drive. This rescue system is running in efi mode and I can see and edit all the files on the system but I am well out of my depth. I am enclosing some basic information from my problem machine and hope you have time to look at this and advise. First here is my from /dev/nvme01p1/root/boot/grub2/grub.cfg:-

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub2-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
set btrfs_relative_path="y"
export btrfs_relative_path
if [ -f ${config_directory}/grubenv ]; then
  load_env -f ${config_directory}/grubenv
elif [ -s $prefix/grubenv ]; then
  load_env
fi

if [ "${env_block}" ] ; then
  set env_block="(${root})${env_block}"
  export env_block
  load_env -f "${env_block}"
fi

if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   if [ "${env_block}" ] ; then
     save_env -f "${env_block}" next_entry
   fi
   set boot_once=true
else
   set default="${saved_entry}"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    if [ "${env_block}" ] ; then
      save_env -f "${env_block}" saved_entry
    else
      save_env saved_entry
    fi

  fi
}

function load_video {
  if [ x$feature_all_video_module = xy ]; then
    insmod all_video
  else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_gpt
insmod btrfs
search --no-floppy --fs-uuid --set=root d49782e2-1df9-4013-a8c9-6136ff257446
    font="/usr/share/grub2/unicode.pf2"
fi

if loadfont $font ; then
  if [ "${grub_platform}" = "efi" ]; then
    echo "Please press 't' to show the boot menu on this console"
  fi

  set gfxmode=1920x1080
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=en_US
  insmod gettext
fi
terminal_input console

for i in gfxterm; do
  if [ x${use_append} = xtrue ]; then
     terminal_output --append $i
  elif terminal_output $i; then
     use_append=true;
  fi
done

if [ x${boot_once} = xtrue ]; then
  set timeout=0
elif [ x$feature_timeout_style = xy ] ; then
  set timeout_style=menu
  set timeout=8
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
  set timeout=8
fi
if [ -n "$extra_cmdline" ]; then
  menuentry "Help on bootable snapshot #$snapshot_num" {
    echo "Select the default entry of the snapshot boot menu."
    echo "Examine the snapshot, and if it's OK,"
    echo "   run 'snapper rollback' and reboot."
    echo "See 'System Rollback by Booting from Snapshots'"
    echo "   in the manual for more information."
    echo "  ** Hit Any Key to return to boot menu **  "
    read
  }
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/00_tuned ###
set tuned_params=""
set tuned_initrd=""
### END /etc/grub.d/00_tuned ###

### BEGIN /etc/grub.d/10_linux ###

### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/20_memtest86+ ###
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/30_uefi-firmware ###
### END /etc/grub.d/30_uefi-firmware ###

### BEGIN /etc/grub.d/35_fwupd ###
### END /etc/grub.d/35_fwupd ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f  ${config_directory}/custom.cfg ]; then
  source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f  $prefix/custom.cfg ]; then
  source $prefix/custom.cfg
fi
### END /etc/grub.d/41_custom ###

### BEGIN /etc/grub.d/80_suse_btrfs_snapshot ###
if [ -f "/.snapshots/grub-snapshot.cfg" ]; then
  source "/.snapshots/grub-snapshot.cfg"
fi
### END /etc/grub.d/80_suse_btrfs_snapshot ###

### BEGIN /etc/grub.d/90_persistent ###
### END /etc/grub.d/90_persistent ###

### BEGIN /etc/grub.d/95_textmode ###
if [ "${grub_platform}" = "efi" ]; then
  # On EFI systems we can only have graphics *or* serial, so allow the user
  # to switch between the two
  hiddenentry 'Text mode' --hotkey 't' {
    set textmode=true
    terminal_output console
  }
fi
### END /etc/grub.d/95_textmode ###

Here is the result from blkid:-

/dev/nvme0n1p1: UUID="d49782e2-1df9-4013-a8c9-6136ff257446" UUID_SUB="d50bcb7e-b0af-482d-9c9a-c34ed48b8ce1" BLOCK_SIZE="4096" TYPE="btrfs" PARTUUID="3c505a18-d6a6-4152-bcf1-52c775229c09"
/dev/sdb1: SEC_TYPE="msdos" LABEL_FATBOOT="diagnostics" LABEL="diagnostics" UUID="4D42-1E23" BLOCK_SIZE="512" TYPE="vfat"
/dev/sr0: BLOCK_SIZE="2048" UUID="2024-08-29-16-50-11-00" LABEL="RESCUE1102" TYPE="iso9660" PTUUID="56f3eb63" PTTYPE="dos"
/dev/loop0: BLOCK_SIZE="524288" TYPE="squashfs"
/dev/sda2: UUID="f6190f68-a732-46c1-97ed-1bd670763810" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="9d422ff5-0d62-4cad-be70-c7af01a346cd"
/dev/sda5: UUID="4272b75a-ea72-4068-8826-e2dfc5611fd5" BLOCK_SIZE="4096" TYPE="xfs" PARTLABEL="primary" PARTUUID="53a507f9-eccf-40a1-b90f-d48cf5227450"
/dev/sda1: SEC_TYPE="msdos" UUID="B738-D576" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="primary" PARTUUID="5a62adf2-d3b4-45d5-abaa-1982f4195eaa"
/dev/sdc1: LABEL="18_USB_64G" UUID="e4bb8dbf-3a48-47d7-b55b-9ae6403d3773" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="primary" PARTUUID="b39972ec-e191-40cc-87bb-8fbf7227881b"

and here is the result from efibootmgr -v

BootCurrent: 0000
Timeout: 10 seconds
BootOrder: 000D,0000,0001,0002,0003,0004,0005,0006,0007,0008,0009,000A,000B,000C
Boot0000* CD/DVD Rom	PciRoot(0x0)/Pci(0x1f,0x2)/Ata(0,0,0)/CDROM(1,0x3d,0xb40)
      dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 02 1f / 03 01 08 00 00 00 00 00 / 04 02 18 00 01 00 00 00 3d 00 00 00 00 00 00 00 40 0b 00 00 00 00 00 00 / 7f ff 04 00
Boot0001* Floppy Disk	VenMedia(0c588db8-6af4-11dd-a992-00197d890238,00)
      dp: 04 03 15 00 b8 8d 58 0c f4 6a dd 11 a9 92 00 19 7d 89 02 38 00 / 7f ff 04 00
Boot0002* Hard Disk 0	VenMedia(0c588db8-6af4-11dd-a992-00197d890238,08)
      dp: 04 03 15 00 b8 8d 58 0c f4 6a dd 11 a9 92 00 19 7d 89 02 38 08 / 7f ff 04 00
Boot0003* PXE Network	VenMedia(0c588db8-6af4-11dd-a992-00197d890238,06)
      dp: 04 03 15 00 b8 8d 58 0c f4 6a dd 11 a9 92 00 19 7d 89 02 38 06 / 7f ff 04 00
Boot0004* Hard Disk 1	VenMedia(0c588db8-6af4-11dd-a992-00197d890238,09)
      dp: 04 03 15 00 b8 8d 58 0c f4 6a dd 11 a9 92 00 19 7d 89 02 38 09 / 7f ff 04 00
Boot0005* Hard Disk 2	VenMedia(0c588db8-6af4-11dd-a992-00197d890238,0a)
      dp: 04 03 15 00 b8 8d 58 0c f4 6a dd 11 a9 92 00 19 7d 89 02 38 0a / 7f ff 04 00
Boot0006* Hard Disk 3	VenMedia(0c588db8-6af4-11dd-a992-00197d890238,0b)
      dp: 04 03 15 00 b8 8d 58 0c f4 6a dd 11 a9 92 00 19 7d 89 02 38 0b / 7f ff 04 00
Boot0007* USB Storage	VenMedia(0c588db8-6af4-11dd-a992-00197d890238,03)
      dp: 04 03 15 00 b8 8d 58 0c f4 6a dd 11 a9 92 00 19 7d 89 02 38 03 / 7f ff 04 00
Boot0008* Diagnostics	VenMedia(0c588db8-6af4-11dd-a992-00197d890238,da)
      dp: 04 03 15 00 b8 8d 58 0c f4 6a dd 11 a9 92 00 19 7d 89 02 38 da / 7f ff 04 00
Boot0009* iSCSI	VenMedia(0c588db8-6af4-11dd-a992-00197d890238,04)
      dp: 04 03 15 00 b8 8d 58 0c f4 6a dd 11 a9 92 00 19 7d 89 02 38 04 / 7f ff 04 00
Boot000A* iSCSI Critical	VenMedia(0c588db8-6af4-11dd-a992-00197d890238,05)
      dp: 04 03 15 00 b8 8d 58 0c f4 6a dd 11 a9 92 00 19 7d 89 02 38 05 / 7f ff 04 00
Boot000B* Legacy Only	VenMedia(0c588db8-6af4-11dd-a992-00197d890238,ee)
      dp: 04 03 15 00 b8 8d 58 0c f4 6a dd 11 a9 92 00 19 7d 89 02 38 ee / 7f ff 04 00
Boot000C* Embedded Hypervisor	VenMedia(0c588db8-6af4-11dd-a992-00197d890238,01)
      dp: 04 03 15 00 b8 8d 58 0c f4 6a dd 11 a9 92 00 19 7d 89 02 38 01 / 7f ff 04 00
Boot000D* opensuse	HD(1,GPT,5a62adf2-d3b4-45d5-abaa-1982f4195eaa,0x800,0x4e000)/\EFI\opensuse\grubx64.efi
      dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 e0 04 00 00 00 00 00 f2 ad 62 5a b4 d3 d5 45 ab aa 19 82 f4 19 5e aa 02 02 / 04 04 38 00 5c 00 45 00 46 00 49 00 5c 00 6f 00 70 00 65 00 6e 00 73 00 75 00 73 00 65 00 5c 00 67 00 72 00 75 00 62 00 78 00 36 00 34 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00

I can paste all that I have if it would help.
Budge

Please leave out the “here is” part. What we here want to see is what you saw:

ab85m:~ # efibootmgr -u
BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0000
Boot0000* opensusetw    HD(1,GPT,5ea5068c-4f37-4df5-a2a2-65fe082c6794,0x800,0xa0000)/File(\EFI\opensusetw\grubx64.efi)0
ab85m:~ #

It’s just two more lines to copy and paste from your terminal, plus it’s one more line you don’t need to type. This way we can all be sure what command you actually ran, along with the following command prompt indicating end of command completed, the exact same things you saw.

I apologise and will cut the chat.
I have now been able to boot the Leap 15.5 installation DVD and open the Rescue system.
I have asked for a summary of what I have done, courtesy of chatgpt4 working from laptop next to my problem machine. Please see the susepaste link. I hope this helps. I have left the machine at the rescue prompt but am writing on my home workstation now.

https://paste.opensuse.org/pastes/c467a119851b

I agree with the report that grub.cfg lacks any of the expected stanzas that grub2-mkconfig is supposed to provide. It would be wonderful if we could find the cause of their absence, but I don’t have a clue how to find that out from a normal boot, much less a rescue boot.

Do you have any grub.cfg files in any backup of the problem PC that you could plant in the one in /boot/grub2/ for Grub to use? Alternatively or in addition, you could take one, put it in /etc/grub.d/40_custom, modify if necessary, then run grub2-mkconfig -o /boot/grub2/grub.cfg. Take a look in grub.cfg beginning at the ### BEGIN /etc/grub.d/40_custom ### line and you’ll see that’s its purpose. In the following section you can see code that incorporates any stanza you personally create in file /boot/grub2/custom.cfg that you personally create. Without a backup file to work from these things can still be done, but it’s a lot more work building from scratch, digging required data out of a long thread.

All my UEFI booting is done from TW’s Grub via my custom.cfg. Here is one of my self-composed stanzas:

# grep -A6 15.5 /boot/grub2/custom.cfg
menuentry "openSUSE 15.5 defkernel 3 on P21" {
        load_video
        set gfxpayload=keep
        search --no-floppy --set=root --hint-efi=hd0,gpt21 --label tm8p21s155
        linux   /boot/vmlinuz root=LABEL=tm8p21s155 noresume
        initrd  /boot/initrd
}
#

Note it’s much simpler than you find in grub.cfg, and there are no versions for kernel or initrd. The symlinks kernel installation provides are used instead. You would need to use device name or --uuid instead of --label if you haven’t assigned volume labels to the relevant filesystems.

Lotsa ways of skinning cats. We just need to find you the right one. :slight_smile:

Hi and many thanks. Regarding backups most of these are not of the OS but I will spend some time looking. I can also do a line by line comparison with the working system and see what are the differences.

Meanwhile and again standing back a bit, two other thoughts:-

It used to be possible to do a fresh install and not change or format the previous /home directory. This had been my approach previously when upgrading and then I only had to re-install the few apps I use. Has this opportunity been lost with the change to NVME and btrfs?

A second thought. If I unplug the NVME pci card and put it in my backup machine would the file system then be accessible. If so I could simply backup all I need and then put card back and do a complete new installation?

The current defaults include BTRFS for /, and home content on same filesystem as /. Neither are mandatory. As always, you may specify a non-default filesystem for /, and /home/ content on a separate filesystem. /home/ must exist, but may include content, or simply be a mountpoint for a separate filesystem.

As long as the other machine supports NVME and can mount its filesystem(s) in any manner, then whatever it contains can be copied from it. If openSUSE is on both PCs, then of course you can mount and read on the other, subject to any limitations due to any differences in OS or filesystem versions. If both are running only Leap, or the source to be read is the older, then there should be none such.

I think I shall try the expedient route; the two machines are essentially identical so if I have a slot available I should be good to try to copy the data. If it works it will save us all a great deal of effort. Will report how I get on.

So far so good, I now have the second nvme in my system:-

alastair@ibmserv3:~> lsblk
NAME        MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
sda           8:0    0  5.5T  0 disk 
├─sda1        8:1    0  500M  0 part /boot/efi
├─sda2        8:2    0    2G  0 part /boot
├─sda3        8:3    0    2G  0 part [SWAP]
└─sda4        8:4    0  5.4T  0 part /multimedia
sr0          11:0    1 1024M  0 rom  
sr1          11:1    1 1024M  0 rom  
nvme1n1     259:0    0  1.8T  0 disk 
└─nvme1n1p1 259:1    0  1.8T  0 part 
nvme0n1     259:2    0  1.8T  0 disk 
└─nvme0n1p1 259:3    0  1.8T  0 part /var
                                     /usr/local
                                     /tmp
                                     /srv
                                     /root
                                     /opt
                                     /home
                                     /

I assume the second “drive” nvme1n1 and partition nvme1n1p1 with the original sub volumes remain intact but what should I mount and will there be confusion with subvolume names? The second nvme is not mounted at present.

I have it sorted now and am in process of backing up relevant directories from my /home directory of the problem server.
Thanks to all for the help.
Once I am confident I have all my data I shall put the nvme pci card in the original machine and look at upgrade or new installation of Leap 15.6.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.