PDA

View Full Version : SLES 11 SP4 Did the command line update mess up my boot loader?



ammoun
08-Jul-2017, 19:35
I have been struggling with this server for few days now. I have SLES 11 SP4 disk and I'm trying to upgrade/Repair the system. Originally I was running SP3, but I tried to update the distribution from the command line and that did not end up well. Right now, on boot, I get ELILO Boot message and then at initrd step, the system reboots automatically and stays in that loop.

With SP4 disk I'm able to see partitions, but every single attempt to install a boot loader has failed. Grub and ELILO alike. :

http://i.imgur.com/COXyVNo.png

GRUB error:

http://i.imgur.com/mjgLpoz.png

The BIOS is set to "UEFI and Legacy"

I noticed that this location was empty???:

http://i.imgur.com/oZZdzjY.png

Here is some of the ELILO error, let me know if you want to see the whole thing please. I already posted too many pictures.

http://i.imgur.com/Smijd8t.png

I cannot copy and paste error texts but I took several screenshots. It would be a blessing if someone could give me a hand.

malcolmlewis
09-Jul-2017, 13:48
On Sat 08 Jul 2017 06:44:01 PM CDT, ammoun wrote:

I have been struggling with this server for few days now. I have SLES 11
SP4 disk and I'm trying to upgrade/Repair the system. Originally I was
running SP3, but I tried to update the distribution from the command
line and that did not end up well. Right now, on boot, I get ELILO Boot
message and then at initrd step, the system reboots automatically and
stays in that loop.

With SP4 disk I'm able to see partitions, but every single attempt to
install a boot loader has failed. Grub and ELILO alike. :

[image: http://i.imgur.com/COXyVNo.png]

GRUB error:

[image: http://i.imgur.com/mjgLpoz.png]

The BIOS is set to "UEFI and Legacy"

I noticed that this location was empty???:

[image: http://i.imgur.com/oZZdzjY.png]

Here is some of the ELILO error, let me know if you want to see the
whole thing please. I already posted too many pictures.

[image: http://i.imgur.com/Smijd8t.png]

I cannot copy and paste error texts but I took several screenshots. It
would be a blessing if someone could give me a hand.




Hi
Are you sure the system is booting in UEFI mode? Can you set the BIOS
to UEFI only. I'm guessing the disk is set to GPT, since it's using an
EFI (type ef00) partition.

If you boot from the SP4 disk and boot to 'rescue mode' and mount sda1
(which should be mounted as /boot/efi on a booting system) is there a
directory called EFI and elilo files exist?

--
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.2|GNOME 3.20.2|4.4.73-18.17-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below... Thanks!

ammoun
09-Jul-2017, 21:22
Hi
Are you sure the system is booting in UEFI mode? Can you set the BIOS
to UEFI only. I'm guessing the disk is set to GPT, since it's using an
EFI (type ef00) partition.

If you boot from the SP4 disk and boot to 'rescue mode' and mount sda1
(which should be mounted as /boot/efi on a booting system) is there a
directory called EFI and elilo files exist?

--
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.2|GNOME 3.20.2|4.4.73-18.17-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below... Thanks!

https://image.ibb.co/cUNPaF/Messages_Image_4011497280.png

I do remember at some point (after trying multiple iso/upgrade/repairs) that there were 2 folders in the root. The one besides efi, was called LILO but Im not 100% sure if fully remember.

Please let me know if you want to look at anything else while I try to force UEFI in the BIOS and update. I do have a boot folder under sda3 (root partition?)

Thank you!

malcolmlewis
09-Jul-2017, 22:36
On Sun 09 Jul 2017 08:24:02 PM CDT, ammoun wrote:

malcolmlewis;38645 Wrote:
> Hi
> Are you sure the system is booting in UEFI mode? Can you set the BIOS
> to UEFI only. I'm guessing the disk is set to GPT, since it's using an
> EFI (type ef00) partition.
>
> If you boot from the SP4 disk and boot to 'rescue mode' and mount sda1
> (which should be mounted as /boot/efi on a booting system) is there a
> directory called EFI and elilo files exist?
>
> --
> Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
> openSUSE Leap 42.2|GNOME 3.20.2|4.4.73-18.17-default
> If you find this post helpful and are logged into the web interface,
> please show your appreciation and click on the star below... Thanks!

[image: https://image.ibb.co/cUNPaF/Messages_Image_4011497280.png]

I do remember at some point (after trying multiple iso/upgrade/repairs)
that there were 2 folders in the root. The one besides efi, was called
LILO but I_m not 100% sure if fully remember.

Please let me know if you want to look at anything else while I try to
force UEFI in the BIOS and update. I do have a boot folder under sda3
(root partition?)

Thank you!




Hi
So for UEFI (elilo) booting you have;
a) Disk type set to GPT (via gdisk)
b) A small FAT partition < 500MB for /boot/efi (mount point)
c) Small FAT partition set to type ef00

For legacy (grub) booting you have;
a) Disk type set to DOS (via fdisk)
b) A separate small ext(2/3) partiton ~ 500MB for /boot (optional)
c) A boot flag set wherever the bootloader installs (or MBR)

Since in GPT the mbr is set protective (more secure) you can't install
grub (which you tried) since it's too old to support efi (hence elilo).
It is possible, but some extra steps to do... stick with one type or
the other.....

In rescue mode run the command fdisk and gdisk to see the state of the
disk...



fdisk -l /dev/sda
gdisk -l /dev/sda


The above should help to see what is what....

--
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.2|GNOME 3.20.2|4.4.74-18.20-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below... Thanks!

ammoun
10-Jul-2017, 00:50
Hi
So for UEFI (elilo) booting you have;
a) Disk type set to GPT (via gdisk)
b) A small FAT partition < 500MB for /boot/efi (mount point)
c) Small FAT partition set to type ef00

For legacy (grub) booting you have;
a) Disk type set to DOS (via fdisk)
b) A separate small ext(2/3) partiton ~ 500MB for /boot (optional)
c) A boot flag set wherever the bootloader installs (or MBR)

Since in GPT the mbr is set protective (more secure) you can't install
grub (which you tried) since it's too old to support efi (hence elilo).
It is possible, but some extra steps to do... stick with one type or
the other.....

In rescue mode run the command fdisk and gdisk to see the state of the
disk...



fdisk -l /dev/sda
gdisk -l /dev/sda


The above should help to see what is what....

--
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.2|GNOME 3.20.2|4.4.74-18.20-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below... Thanks!

https://image.ibb.co/dq0kXv/Messages_Image_3212646448.png

I didn't find gdisk command in the SP4 rescue disk but I tried gparted. I'm not sure if this is what you wanted to see, please let me know while I try if SLES 12 has the command. In the meantime, I did force UEFI only in the BIOS, and the boot loop is still happening.

https://image.ibb.co/eVAxea/Messages_Image_3122203770.png

Thank you!

malcolmlewis
10-Jul-2017, 01:35
Hi
So when booting, can you select efi type booting (eg F12 or esc) and either select the install media, or the elilo efi file?

Seems to me it's wanting to be UEFI, but set to legacy.....

For example (this is SLES 12 SP2 though);


parted -l /dev/sda

Model: ATA TOSHIBA MQ01ABF0 (scsi)
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
1 1049kB 274MB 273MB fat16 EFI System boot
2 274MB 108GB 107GB btrfs Linux filesystem
3 108GB 116GB 8590MB linux-swap(v1) Linux swap
4 116GB 180GB 63.8GB Linux filesystem
5 180GB 234GB 53.7GB xfs Linux RAID raid
6 234GB 500GB 266GB xfs Linux RAID raid


In rescue mode, is there any output from the following command;


efibootmgr -v


Bottomline, need to boot in UEFI mode...

ammoun
10-Jul-2017, 02:10
Hi
So when booting, can you select efi type booting (eg F12 or esc) and either select the install media, or the elilo efi file?

Seems to me it's wanting to be UEFI, but set to legacy.....

For example (this is SLES 12 SP2 though);


parted -l /dev/sda

Model: ATA TOSHIBA MQ01ABF0 (scsi)
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
1 1049kB 274MB 273MB fat16 EFI System boot
2 274MB 108GB 107GB btrfs Linux filesystem
3 108GB 116GB 8590MB linux-swap(v1) Linux swap
4 116GB 180GB 63.8GB Linux filesystem
5 180GB 234GB 53.7GB xfs Linux RAID raid
6 234GB 500GB 266GB xfs Linux RAID raid


In rescue mode, is there any output from the following command;


efibootmgr -v


Bottomline, need to boot in UEFI mode...
Hi,

I switched to SLES 12 rescue disk and gdisk command was in there!

https://image.ibb.co/dCzLXv/Messages_Image_1684686328.png

Here is the output of efibootmgr -v

https://image.ibb.co/f1dKQF/Messages_Image_3965545515.png

ammoun
10-Jul-2017, 02:44
I just learned from here that I could interrupt the boot at "ELILO BOOT" prompt and tab to get options

https://docstore.mik.ua/manuals/hp-ux/en/5991-1247B/ch05s21.html

https://image.ibb.co/iVqkXv/Screen_Shot_2017_07_09_at_9_31_38_PM.png

ammoun
10-Jul-2017, 02:56
To understand this better, what is supposed to happen right after the two files get loaded in the ELILO boot?

Where should there be a reference to the kernel that needs to be loaded? I think SP3 won't exist by now, and I should have at least 2 more instead.

I remember the last time I tried to upgrade to SLES 12, the summary of the steps that were about to happen mentioned SLES 12, 11 SP4 and an Open Suse (I'm assuming the latter got added accidentally after I added OpenSuse repositories and the system tried to update from SLES 11 SP3 to Open Suse back when it was working? ) The source of the original problem I guess?

Anyway, is there a way that I could reset /dev/sda1 to take account of the different kernels that I tried to install?

One thing I should also mention is that while I was desperately playing with upgrade/repair disks, I believe there was a mention that one of the partitions' currupt bit was set, I could have sworn it was sda1. But I guess since vmlinuz and initrd are loading before the boot failure happens, that everything there is ok?

malcolmlewis
10-Jul-2017, 04:32
Hi
So boot from the SLES 11 SP4 install media and try an upgrade again, once you get to the partitioning, select expert mode and hit the rescan disk, select sda and use;

sda1, type ef mountpoint /boot/efi
sda2, type 82 mountpoint your swap
sda3, type 83 mountpoint /

At the final screen is the install summary, here check in the boot section, should be elilo and efi booting...

Else how important is the current/broken / data? Backup's available?

ammoun
10-Jul-2017, 05:44
Hi,

I switched to SLES 12 rescue disk and gdisk command was in there!

https://image.ibb.co/dCzLXv/Messages_Image_1684686328.png

Here is the output of efibootmgr -v

https://image.ibb.co/f1dKQF/Messages_Image_3965545515.png


Hi
So boot from the SLES 11 SP4 install media and try an upgrade again, once you get to the partitioning, select expert mode and hit the rescan disk, select sda and use;

sda1, type ef mountpoint /boot/efi
sda2, type 82 mountpoint your swap
sda3, type 83 mountpoint /

At the final screen is the install summary, here check in the boot section, should be elilo and efi booting...

Else how important is the current/broken / data? Backup's available?
Hi,
I would rather if possible keep formatting as the very last resort. I can currently mount sda3 from rescue, ssh and copy files if I really have to...

Could I do what you suggested with SLES 12 instead? The problem with SP4 is that I couldn't get past this screen, it keeps loading after I clicked Next.

https://image.ibb.co/nvfrPa/Screen_Shot_2017_07_10_at_12_30_19_AM.png

ammoun
10-Jul-2017, 06:40
So I got past that screen, and I got a warning that I was downgrading and might end up with issues but I accepted. The first package to install failed! And I'm glad it did as I aborted and got the option to boot from hard drive in SLES 12 and that worked!. So I guess the challenge left is to fix the EFI partition? Is it easier now that I have regular root access and ssh?

malcolmlewis
10-Jul-2017, 12:36
On Mon 10 Jul 2017 05:44:01 AM CDT, ammoun wrote:

So I got past that screen, and I got a warning that I was downgrading
and might end up with issues but I accepted. The first package to
install failed! And I'm glad it did as I aborted and got the option to
boot from hard drive in SLES 12 and that worked!. So I guess the
challenge left is to fix the EFI partition? Is it easier now that I have
regular root access and ssh?




Hi
So your at SLES 12 SP2 now?

Is sda1 mounted as /boot/efi? if so is there a EFI/sles subdirectory
with efi files present? Also has the output from efibootmgr -v changed?


--
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.2|GNOME 3.20.2|4.4.74-18.20-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below... Thanks!

ammoun
10-Jul-2017, 15:41
Hi
So your at SLES 12 SP2 now?

Is sda1 mounted as /boot/efi? if so is there a EFI/sles subdirectory
with efi files present? Also has the output from efibootmgr -v changed?


--
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.2|GNOME 3.20.2|4.4.74-18.20-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below... Thanks!

Apparently yes! I'm running SLES 12 but I don't think it's SP2.


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)03 11050000
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)

So apparently it didn't change and I'm sure that as soon as I reboot I would be back in the loop. Here is my theory, please correct me. Since the last upgrade that I tried was SLES 12, and it went through and failed at the set up of the boot loader. The system got upgraded in sda3 but the boot partition didn't! It is still at the 11 SP3 state. For some reason, no upgrade or repair could update the files there. Can I do it manually then?

malcolmlewis
10-Jul-2017, 16:18
Hi
So is sda1 mounted and is there a sles directory with efi files present? If so can you list, this will identify whether we can manually add via efibootmgr, or do a complete grub (yes grub for SLE 12) install via YaST.

ammoun
10-Jul-2017, 17:09
Hi
So is sda1 mounted and is there a sles directory with efi files present? If so can you list, this will identify whether we can manually add via efibootmgr, or do a complete grub (yes grub for SLE 12) install via YaST.

Hi,


fdisk -l /dev/sda

Disk /dev/sda: 1.9 TiB, 2092995444736 bytes, 4087881728 sectors
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: 62F4B386-AE3F-4110-841B-A7470698A5A9

Device Start End Sectors Size Type
/dev/sda1 2048 321535 319488 156M EFI System
/dev/sda2 321536 4530175 4208640 2G Microsoft basic data
/dev/sda3 4530176 4087879679 4083349504 1.9T EFI System


gdisk -l /dev/sda
GPT fdisk (gdisk) version 0.8.8

Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 4087881728 sectors, 1.9 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 62F4B386-AE3F-4110-841B-A7470698A5A9
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 4087881694
Partitions will be aligned on 2048-sector boundaries
Total free space is 4029 sectors (2.0 MiB)

Number Start (sector) End (sector) Size Code Name
1 2048 321535 156.0 MiB EF00 primary
2 321536 4530175 2.0 GiB 0700 primary
3 4530176 4087879679 1.9 TiB EF00 primary


mount /dev/sda1 /mnt
mount: unknown filesystem type 'vfat'

cat /proc/mounts didn't list /dev/sda1.

I guess things were better from the rescue disk when I used to be able to mount /dev/sda1.

malcolmlewis
10-Jul-2017, 17:37
Hi
OK, so from an ssh session as root user run the command;



yast bootloader


On the Boot Code Options tab, what is the 'Boot Loader' set to, can you select an option in the dropdown?

On the Bootloader options tab, is there a 'Default Boot Selection' can you select an option in the dropdown?

Also need to confirm what release your at via;


cat /etc/os-release


Else might need to wipe the efi and start again, but confirm above first.



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.

malcolmlewis
10-Jul-2017, 17:40
Hi
Also in gdisk, fix the partition types....



gdisk /dev/sda
t
2
8200
t
3
8300
w

ammoun
10-Jul-2017, 18:34
https://image.ibb.co/mWUNfF/Screen_Shot_2017_07_10_at_1_26_39_PM.png

The options I have are: Grub2, Grub2 EFI and Do not Install...

I have SLES12 under default boot section.


cat /etc/os-release
NAME="SLES"
VERSION="12"
VERSION_ID="12"
PRETTY_NAME="SUSE Linux Enterprise Server 12"
ID="sles"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:suse:sles:12"

yast disk


Error │
│ The storage subsystem is locked by the application "y2base" (9475). │
│ You must quit that application before you can continue. │
│ │
│ [Continue] [Cancel]

Just finished your gdisk suggestions, thanks!

ammoun
10-Jul-2017, 18:47
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?

malcolmlewis
10-Jul-2017, 19:12
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?
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
10-Jul-2017, 19:33
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....)

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)03 11050000
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
10-Jul-2017, 19:40
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)03 11050000
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?
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
10-Jul-2017, 19:50
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.
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:

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

And
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 ..

SuSE is from an older version I think? :(


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

malcolmlewis
10-Jul-2017, 19:54
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
10-Jul-2017, 21:05
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_00b3e7fc13e0158119401f065860 0705-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:

yast bootloader summary

The boot partition is of type NFS. Bootloader cannot be installed.

malcolmlewis
10-Jul-2017, 22:36
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.
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_00b3e7fc13e0158119401f065860 0705-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:

yast bootloader summary

The boot partition is of type NFS. Bootloader cannot be installed.[/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
11-Jul-2017, 00:37
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)


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.

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

malcolmlewis
11-Jul-2017, 02:34
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/?
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
11-Jul-2017, 03:55
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 :confused:

And of course yast bootloader isn't saving :(

malcolmlewis
11-Jul-2017, 04:13
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 :confused:

And of course yast bootloader isn't saving :(

Strange indeed..... wonder if it's not loaded...


modprobe vfat

Then try the mount command again...