Did the command line update mess up my boot loader?

[malcolmlewis]

[QUOTE=ammoun;38679]ps aux | grep y2base root 9475 0.1 0.1 376800 99596 pts/1 Tl 09:18 0:03 /usr/lib/YaST2/bin/y2base bootloader ncurses root 11512 0.0 0.0 9232 676 pts/1 D+ 09:45 0:00 grep --color=auto y2base’’

Can I kill -9 9475?[/QUOTE]
Hi
No, select grub2-efi and we want to save it… hopefully it will sort out /dev/sda1 as /boot/efi.

Then run efibootmgr -v again to see if it updated the entries…

Then run the command;

lsblk

Just to see what it’s showing… hopefully /dev/sda1 as /boot/efi, if not then I suspect it’s in the / partition still… (which we can sort out with a copy etc…)

[ammoun]

[QUOTE=malcolmlewis;38680]Hi
No, select grub2-efi and we want to save it… hopefully it will sort out /dev/sda1 as /boot/efi.

Then run efibootmgr -v again to see if it updated the entries…

Then run the command;

lsblk

Just to see what it’s showing… hopefully /dev/sda1 as /boot/efi, if not then I suspect it’s in the / partition still… (which we can sort out with a copy etc…)[/QUOTE]

The thing with yast bootloader is that Grub2-Efi is the option already selected when it loads, so saving that does not seem to be updating anything, just my thought though. I guess this confirms my doubt?

efibootmgr -v Timeout: 10 seconds BootOrder: 0005,0000,0003,0001,0002 Boot0000* CD/DVD Rom ACPI(a0341d0,0)PCI(1d,0)USB(0,0)USB(0,0)USB(2,0)0311050000 Boot0001* Hard Disk 0 ACPI(a0341d0,0)PCI(2,2)PCI(0,0)Controller(0)SCSI(0,0)HD(1,800,4e000,b1006802-14af-40ed-8e33-3a1508bf38b5) Boot0002* PXE Network ACPI(a0341d0,0)PCI(3,2)PCI(0,0)MAC(90e2ba428eae,0)IPv4(0.0.0.0:0<->0.0.0.0:0,0, 0 Boot0003* Floppy Disk Vendor(0c588db8-6af4-11dd-a992-00197d890238,00) Boot0005* SUSE Linux Enterprise Server 11 SP3 HD(1,800,4e000,b1006802-14af-40ed-8e33-3a1508bf38b5)File(\\efi\\SuSE\\elilo.efi)

lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 1.9T 0 disk ├─sda1 8:1 0 156M 0 part ├─sda2 8:2 0 2G 0 part [SWAP] └─sda3 8:3 0 1.9T 0 part / sr0 11:0 1 1024M 0 rom sr1 11:1 1 3.2G 0 rom sr2 11:2 1 5.2G 0 rom

Should I maybe select Grub, apply and then switch back to Grub2-Efi, apply?

[malcolmlewis]

[QUOTE=ammoun;38682]The thing with yast bootloader is that Grub2-Efi is the option already selected when it loads, so saving that does not seem to be updating anything, just my thought though. I guess this confirms my doubt?

efibootmgr -v Timeout: 10 seconds BootOrder: 0005,0000,0003,0001,0002 Boot0000* CD/DVD Rom ACPI(a0341d0,0)PCI(1d,0)USB(0,0)USB(0,0)USB(2,0)0311050000 Boot0001* Hard Disk 0 ACPI(a0341d0,0)PCI(2,2)PCI(0,0)Controller(0)SCSI(0,0)HD(1,800,4e000,b1006802-14af-40ed-8e33-3a1508bf38b5) Boot0002* PXE Network ACPI(a0341d0,0)PCI(3,2)PCI(0,0)MAC(90e2ba428eae,0)IPv4(0.0.0.0:0<->0.0.0.0:0,0, 0 Boot0003* Floppy Disk Vendor(0c588db8-6af4-11dd-a992-00197d890238,00) Boot0005* SUSE Linux Enterprise Server 11 SP3 HD(1,800,4e000,b1006802-14af-40ed-8e33-3a1508bf38b5)File(\\efi\\SuSE\\elilo.efi)

lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 1.9T 0 disk ├─sda1 8:1 0 156M 0 part ├─sda2 8:2 0 2G 0 part [SWAP] └─sda3 8:3 0 1.9T 0 part / sr0 11:0 1 1024M 0 rom sr1 11:1 1 3.2G 0 rom sr2 11:2 1 5.2G 0 rom

Should I maybe select Grub, apply and then switch back to Grub2-Efi, apply?[/QUOTE]
Hi
No, go change the menu timeout 10 say 10 seconds…

Now, can you check the following;

ls -lah /boot/efi/EFI

If it shows files then we need to fix up /dev/sda1 and move the files over and create the efi entry.

[ammoun]

[QUOTE=malcolmlewis;38683]Hi
No, go change the menu timeout 10 say 10 seconds…

Now, can you check the following;

ls -lah /boot/efi/EFI

If it shows files then we need to fix up /dev/sda1 and move the files over and create the efi entry.[/QUOTE]
Hi,

Problems I think…

After I update the timeout (smart trick ), Hit OK, restart yast bootloader again, I get the old value 8 No errors whatsoever when saving and quitting.

The other bad news is that:

[QUOTE]ls -lah /boot/efi/EFI
ls: cannot access /boot/efi/EFI: No such file or directory[/QUOTE]

And [QUOTE]ls -lah /boot/efi/efi/SuSE/
total 8.0K
drwxr-xr-x 2 root root 4.0K Jul 8 08:33 .
drwxr-xr-x 3 root root 4.0K Jul 8 08:33 …[/QUOTE]

SuSE is from an older version I think?

[QUOTE]ls -lah /boot/
total 38M
drwxr-xr-x 6 root root 4.0K Jul 9 20:59 .
drwxr-xr-x 27 root root 4.0K Jul 9 21:00 …
-rw-r–r-- 1 root root 65 Oct 8 2014 .vmlinuz-3.12.28-4-default.hmac
-rw-r–r-- 1 root root 2.5M Oct 8 2014 System.map-3.12.28-4-default
-rw-r–r-- 1 root root 512 Jul 8 10:07 backup_mbr
-rw-r–r-- 1 root root 1.5K Sep 26 2014 boot.readme
-rw-r–r-- 1 root root 133K Oct 8 2014 config-3.12.28-4-default
drwxr-xr-x 2 root root 4.0K Oct 8 2014 dracut
drwxr-xr-x 3 root root 4.0K Jul 8 08:33 efi
drwxr-xr-x 2 root root 4.0K Jul 8 11:57 grub
drwxr-xr-x 7 root root 4.0K Jul 8 14:28 grub2
lrwxrwxrwx 1 root root 24 Jul 8 11:14 initrd → initrd-3.12.28-4-default
-rw------- 1 root root 11M Jul 5 15:24 initrd-2.6.34-12-default-kdump
-rw------- 1 root root 13M Jul 8 11:18 initrd-3.12.28-4-default
-rw-r–r-- 1 root root 407K Jul 8 11:17 message
-rw-r–r-- 1 root root 230K Jun 24 2015 symsets-3.0.101-63-default.tar.gz
-rw-r–r-- 1 root root 649K Jun 24 2015 symtypes-3.0.101-63-default.gz
-rw-r–r-- 1 root root 699K Oct 8 2014 symtypes-3.12.28-4-default.gz
-rw-r–r-- 1 root root 242K Oct 8 2014 symvers-3.12.28-4-default.gz
-rw-r–r-- 1 root root 409 Oct 8 2014 sysctl.conf-3.12.28-4-default
-rw-r–r-- 1 root root 5.5M Oct 8 2014 vmlinux-3.12.28-4-default.gz
lrwxrwxrwx 1 root root 25 Jul 8 11:14 vmlinuz → vmlinuz-3.12.28-4-default
-rw-r–r-- 1 root root 4.7M Oct 8 2014 vmlinuz-3.12.28-4-default[/QUOTE]

[malcolmlewis]

Hi
OK, then neet to run the yast disk command to setup /dev/sda1 in post #17, then go back try to update yast bootloader again…

[ammoun]

QUOTE=malcolmlewis;38676]

yast disk

In here you need to select sda1 and edit to format to vfat, set type ef00 (for efi) and set the mount point to /boot/efi from the dropdown. When finished save and exit.[/QUOTE]Device: │ │ │└┬─sda ││ │ │ │ ├──sda1 ││ * Device: /dev/sda1 │ │ │ ├──sda2 ││ * Size: 156.00 MiB │ │ │ └──sda3 ││ * Encrypted: No │ │ ├──RAID ││ * Device Path: pci-0000:16:00.0-scsi-0:2:0:0-part1 │ │ ├──Volume Management ││ * Device ID 1: scsi-36005076058061f40198115e013fce7b3-part1 │ │ ├──Crypt Files ││ Device ID 2: scsi-SIBM_ServeRAID_M5110e_00b3e7fc13e0158119401f0658600705-part1 │ │ ├──Device Mapper ││ Device ID 3: wwn-0x6005076058061f40198115e013fce7b3-part1 │ │ ├──NFS ││ * Used by 1: │ │ ├──Btrfs ││ * FS ID: 0x103 EFI boot │ │ ├──tmpfs ││ │ │ └──Unused Devices ││File System: │ │───Installation Summary ││ │ │───Settings ││ * File System: FAT │ │───Log ││ * Mount Point: │ │ ││ * Mount by: │ │ ││ * UUID: F436-A914 │ │ ││ * Label:

I formatted sda1 to FAT, but I did not see a type option. I typed the mount path.

Summary

*  Format partition /dev/sda1 (156.00 MiB) for /boot/efi with vfat

Then I got this:

Failure occurred during the following action: │ │ │ │ Mounting /dev/sda1 to /boot/efi │ │ │ │ │ │ │ │ System error code was: -3003 │ │ │ │ │ │ │ │ /bin/mount -t vfat -o umask=0002,utf8=true '/dev/sda1' '/boot/efi': │ │ │ │ mount: unknown filesystem type 'vfat' │ │ │ │ │ │ │ │ Continue despite the error?

yast bootloader is still not retaining the timeout value, when I exit it it does not confirm the saving of changes I’m not familiar with it so I can’t say if that’s normal behavior.

Check this out:

[CODE]yast bootloader summary

The boot partition is of type NFS. Bootloader cannot be installed.[/CODE]

[malcolmlewis]

[QUOTE=ammoun;38687]QUOTE=malcolmlewis;38676]

yast disk

In here you need to select sda1 and edit to format to vfat, set type ef00 (for efi) and set the mount point to /boot/efi from the dropdown. When finished save and exit.[/QUOTE]Device: │ │ │└┬─sda ││ │ │ │ ├──sda1 ││ * Device: /dev/sda1 │ │ │ ├──sda2 ││ * Size: 156.00 MiB │ │ │ └──sda3 ││ * Encrypted: No │ │ ├──RAID ││ * Device Path: pci-0000:16:00.0-scsi-0:2:0:0-part1 │ │ ├──Volume Management ││ * Device ID 1: scsi-36005076058061f40198115e013fce7b3-part1 │ │ ├──Crypt Files ││ Device ID 2: scsi-SIBM_ServeRAID_M5110e_00b3e7fc13e0158119401f0658600705-part1 │ │ ├──Device Mapper ││ Device ID 3: wwn-0x6005076058061f40198115e013fce7b3-part1 │ │ ├──NFS ││ * Used by 1: │ │ ├──Btrfs ││ * FS ID: 0x103 EFI boot │ │ ├──tmpfs ││ │ │ └──Unused Devices ││File System: │ │───Installation Summary ││ │ │───Settings ││ * File System: FAT │ │───Log ││ * Mount Point: │ │ ││ * Mount by: │ │ ││ * UUID: F436-A914 │ │ ││ * Label:

I formatted sda1 to FAT, but I did not see a type option. I typed the mount path.

Summary

*  Format partition /dev/sda1 (156.00 MiB) for /boot/efi with vfat

Then I got this:

Failure occurred during the following action: │ │ │ │ Mounting /dev/sda1 to /boot/efi │ │ │ │ │ │ │ │ System error code was: -3003 │ │ │ │ │ │ │ │ /bin/mount -t vfat -o umask=0002,utf8=true '/dev/sda1' '/boot/efi': │ │ │ │ mount: unknown filesystem type 'vfat' │ │ │ │ │ │ │ │ Continue despite the error?

yast bootloader is still not retaining the timeout value, when I exit it it does not confirm the saving of changes I’m not familiar with it so I can’t say if that’s normal behavior.

Check this out:

[CODE]yast bootloader summary

The boot partition is of type NFS. Bootloader cannot be installed.[/CODE][/QUOTE]

Hi
All strange…

OK, try formatting from the command line and also lets see your fstab…

cat /etc/fstab
mkfs.vfat /dev/sda1

Any reason you can’t update to SLES 12 SP2 (to get to the latest release)? But probably need to clean a few things up first…

1. Get rid of the old elilo stuff
2. remove the old efi entry.

[ammoun]

I don’t mind, I just happened to be using SLES 12 disk.

cat /etc/fstab /dev/disk/by-id/scsi-36005076058061f40198115e013fce7b3-part2 swap swap defaults 0 0 /dev/disk/by-id/scsi-36005076058061f40198115e013fce7b3-part3 / ext3 acl,user_xattr 1 1

mkfs.vfat /dev/sda1 mkfs.fat 3.0.26 (2014-03-07)

[QUOTE]Any reason you can’t update to SLES 12 SP2 (to get to the latest release)? But probably need to clean a few things up first…

1. Get rid of the old elilo stuff
2. remove the old efi entry.[/QUOTE]

Not sure how to do that Did you mean folders under /boot/?

[malcolmlewis]

[QUOTE=ammoun;38690]I don’t mind, I just happened to be using SLES 12 disk.

cat /etc/fstab /dev/disk/by-id/scsi-36005076058061f40198115e013fce7b3-part2 swap swap defaults 0 0 /dev/disk/by-id/scsi-36005076058061f40198115e013fce7b3-part3 / ext3 acl,user_xattr 1 1

mkfs.vfat /dev/sda1 mkfs.fat 3.0.26 (2014-03-07)

Not sure how to do that Did you mean folders under /boot/?[/QUOTE]
Hi
Ok, if you cd down into /boot and backup the old efi directory then will delete and create a mountpont and see if can reload the boot info…

cd /boot
tar -cvf old_efi.tar efi
rm -rf efi
efibootmgr -b 5 -B 5
vi /etc/fstab
{and add}
/dev/sda1 /boot/efi vfat umask=0002,utf8=true 0 0
mount /dev/sda1 /boot/efi
yast bootloader

Now try to make a change and let it save…

Else look at upgrading the current setup (including the new /boot/efi | /dev/sda1 ) to SP2.

[ammoun]

mount /dev/sda1 /boot/efi
yast bootloader

I had to recreate directory /boot/efi.

mount /dev/sda1 /boot/efi mount: unknown filesystem type 'vfat'

Why

And of course yast bootloader isn’t saving

[malcolmlewis]

[QUOTE=ammoun;38692] mount /dev/sda1 /boot/efi yast bootloader

I had to recreate directory /boot/efi.

mount /dev/sda1 /boot/efi mount: unknown filesystem type 'vfat'

Why

And of course yast bootloader isn’t saving :([/QUOTE]

Strange indeed… wonder if it’s not loaded…

modprobe vfat

Then try the mount command again…