-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GRUB failing to load kernel on Intel Atom boards (Intel NM10 chipset) #3305
Comments
same problem . HA OS doesn't boot when updating from 12.1 to 12.2 |
Same issue here. Going from 12.1 to 12.2 then I can´t boot. |
Same here... When the VM reboots after the update - it selects "Slot B" which has "unknown filesystem". |
@HAPSagan @ahmetem @Mpgod80 you all are running on native x86-64 hardware? What hardware are you using? @Onepamopa can you open a new issue along with information of your virtualization environment? It also seems yours behaved different as the old boot slot still worked (unlike the case OP reported). |
Its features are below. It was working smoothly until the last update. MacBook Air (11-inch, Mid 2011) a1370 |
On a new installation, what happens exactly when you choose Slot A with HAOS 12.2? Anything written on the screen? Black screen? Reset? |
@agners Intel Atom CPU D2500 @ 1,86Ghz 4,0 Gb RAM 60gb SSD. |
When I try to make a new installation, the same list appears. |
This comment was marked as off-topic.
This comment was marked as off-topic.
Same here 😱 Also running an old Intel atom with cpu integrated on the motherboard. Can’t get any info out of the system. If it would help I can get a live Linux usb. |
i boot ha with Super Grub2 Disk image on usb disk. show all boot menu. and selected slot a. it open normaly. but i dont know How do I make this permanent? or fix it. |
Same problem on a ThinkCentre m93p. |
This comment was marked as off-topic.
This comment was marked as off-topic.
I have an Intel NUC D54250WYK and also experienced this issue when upgrading to 12.2. Luckily, selecting Slot A booted back into 12.1. |
Even downloading haos_generic-x86-64-12.2.img and created new installation does not work. Boot not possible. Same error as afterupgrade from 12.1 to 12.2 |
This comment was marked as off-topic.
This comment was marked as off-topic.
It sounds like a GRUB2 issue of some kind. That got updated from GRUB 2.06 to 2.12 as far as I can tell. FWIW, the rc (and release) versions have been tested and are working fine on various Intel NUC systems. It seems a particular hardware/BIOS which causes issue. It kinda reminds me of that bug fix we added in 8.0.rc4 (#1830 (comment)), but it seems that is applied upstream in GRUB 2.12 today, so that should no longer be the problem 🤔 Can you replace the U-Boot binary (on the first partition of the disk at |
Yes have done that, replaced all files at `/EFI/BOOT/'. It does work. Server can boot again HAS back up. Thanks |
Hi, could you share where from I can download that file? |
same issue. I'm surprised though that the 'backup' entry also does not start. I would assume that the EFI file would still be from 12.1 ? |
This comment was marked as off-topic.
This comment was marked as off-topic.
well...
EDIT: corrected typo 'I am now in 12.2' |
This comment was marked as off-topic.
This comment was marked as off-topic.
typo... I am NOW in 12.2 |
We only ship a single boot loader. In a way, we rely on the bootloader to implement the backup boot method. But if that new bootloader fails in some ways, it is essentially game over 😢
These are the two U-Boot boot loader files from HAOS 12.1 (replace the existing ones in /EFI/BOOT on the first boot partition with these files): Are those affected UEFI BIOS'es maybe 32-bit BIOSes? E.g. can someone check if only replacing |
@ChernyaevAN Right, I know what's wrong 🤦 I will create a patch for that, however, that means the original patch only works on D525 😬 Unfortunately, no one with the affected boards answered my call for testing or tried the RC builds of 13.0. |
Report from @ChernyaevAN in [1] revealed it's 13829424153406670433 in decimal, which means the endianness was wrong for the CPUs I didn't have available for testing. [1] #3305 (comment)
Sorry, but I'm not so advanced to try RC's. |
Report from @ChernyaevAN in [1] revealed it's 13829424153406670433 in decimal, which means the endianness was wrong for the CPUs I didn't have available for testing. [1] #3305 (comment)
@ChernyaevAN It's a bit more complicated, since the current GRUB installed on your machine is faulty. You will need to connect the drive to a different PC, or boot any live USB distro on your Atom, and copy the files from the following archive to overwrite those in Sorry for the complications 😢 |
This is not the problem. I will post after installation. |
The same problem occurred with 13.0. There was no problem with version 12.4. MacBook Air (11-inch, Mid 2011) a1370 |
It works after patching but offers me to upgrade. Do I just need to wait for the new operation system version? |
@ChernyaevAN It should be safe to select the other boot slot with OS 13.0 in GRUB boot menu, or run @ahmetem Can you please also follow the instructions above to get the processor ID? |
I am able to get into grub, but I can't get HAOS to boot linux. I installed Also, I tried the grub patch, and it looked the same as what I have. I am running on an AtomMan X7 Ti with a Intel® Core™ Ultra 9 processor 185H. smbios --type 4 --get-qword 8 When I am in debug mode, this is what I get. It just does nothing after this. |
@randallzapata It's a modern system, so I don't expect it to have problems with the EFI kernel loader. It looks rather like this issue, you can try disabling VT-d in the BIOS settings too. Let's follow up there if it helps, or please create a new issue for your system. |
I have updated to HAOS 13.1. Everything works fine. Thank you. |
Just wanted to let you know I still had this problem with the latest update and a Lenovo Thinkpad [11e (Type 20D9, 20DA)] I used the download above (grub-2.06-haos-12.1.zip together with a debian live usb stick to copy both files to the BOOT directory, which seems to have fixed it again (temporarily)... |
I also ran into this issue on my 2011 Mac Mini running Generic x86-64 when updating HAOS a week ago. It runs a 2.3GHz dual-core Intel Core i5 CPU. Reverting grub via bootable USB solved the issue. Thank you for the pointers in this thread! |
@VerbruggenBart hm, looking at this datasheet, that seems a Celeron CPU from the same era. Can you run the commands @sairon pointed out in #3305 (comment)? |
@sairon i try smbios --type 4 --get-qword 8 but give error. |
@ahmetem did you run the command from the GRUB2 command line? Note you need to install the HAOS 13.0 version to get the |
yes i run GRUB2 command line but my HAOS 12.4 version. i will update and try again. |
@sairon smbios --type 4 --get-qword 8 |
Fix loading issues on this Intel-based platform as well. As described in the patch commit message, there will be likely bigger collateral effect by referring just to the CPU ID but it shouldn't have major detrimental effects. [1] #3305 (comment)
Fix loading issues on this Intel-based platform as well. As described in the patch commit message, there will be likely bigger collateral effect by referring just to the CPU ID but it shouldn't have major detrimental effects. [1] #3305 (comment)
I had this issue updating to 13.1 last week on a Dell Wyse 5070. Using the rescue files mentioned here fixed it. Need any data from me Og can I safely try to upgrade again? I tried to go from 12.4 to 13.1. |
I too have a broken UEFI platform that doesnt load the kernel.
|
Same here, Lenovo ThinkCentre M715q with a Ryzen 5 2400GE
|
Describe the issue you are experiencing
I see GNU GRUB with 4 options - Slot A, Slot B, Slot A rescue shell, Slot B rescue shell.
Selecting any of them results in a message that it's unable to boot.
I dont get any CLI options.
I have used Linux Reader to download the backups from the disk and have then tried to do a fresh installation with OS12.2. The result is the same as after the update - unable to boot from any slot. After that I did a fresh install with OS 12.1 and everything started fine again.
What operating system image do you use?
generic-x86-64 (Generic UEFI capable x86-64 systems)
What version of Home Assistant Operating System is installed?
12.1
Did you upgrade the Operating System.
Yes
Steps to reproduce the issue
...
Anything in the Supervisor logs that might be useful for us?
Anything in the Host logs that might be useful for us?
System information
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: