Remix not booting from GRUB after update - Remix OS for PC

Hi,
Updated Remix to version 3.0.207 yesterday. My PC has Ubuntu 16.04, Windows 10, and Remix OS booting through GRUB 2. After the update, I could no longer boot into Remix via GRUB. I get an error something like "Cannot locate kernel in /RemixOS/kernel" I found this thread and followed the instructions, but this didn't work. My current GRUB config for Remix looks like this:
Code:
menuentry 'Remix OS' --class android-x86 {
insmod part_gpt
insmod ext2
set root='(hd0,gpt7)'
linuxefi /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive SRC=/RemixOS UVESA_MODE=1366x768 verbose logo.showlogo=1
initrdefi /RemixOS/initrd.img
}
I can see several problems with this since there is no "/RemixOS/kernel" directory and no "/RemixOS/initrd.img" on the Remix partition. How do I fix this problem? My Remix OS partition looks like this (I removed data.img to reduce size).
Thanks!
Kp

---

Before using the Grub 2 guide (I don't recommend it), how did you install Remix OS? (with Windows official tool/Linux official beta installer/bootable installer, manually using unofficial methods?)
Did you do manual changes to the grub configuration file?
Can't download that drop box file now, but I'll look later.
It'd be better if you posted a screenshot with filetree of partition where RemixOS folder is placed.

---

Vioner said:
How did you install Remix OS? (with Windows official tool/Linux official beta installer/bootable installer, manually using unofficial methods?).
Click to expand...
Click to collapse
I used the Windows official tool to install it on its own partition. I manually edited GRUB (/etc/grub.d/40_custom) to add Remix OS as a boot menu entry. I initially created the entry using grub.cfg in the RemixOS folder as a guide.
Here's a screenie for the Remix directory:
/F (Remix OS partition)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
/F/RemixOS
Hope this is helpful.
Thanks!
Kp

---

Originally the grub configuration doesn't have static Remix path like in your case - it searches for it instead. Thanks to that, if you switch drives order (f.e. plug drive into different port) it still works.
So I highly recommend switching to this method. Rather try to use the original grub.cfg contents than use unofficial method. Any unofficial stuff makes support harder.
Also this method may be hindered if you have RemixOS folder on multiple partitions so have it in mind.
@HypoTurtle found what's the issue below.

---

Kpenguin.5284 said:
I used the Windows official tool to install it on its own partition. I manually edited GRUB (/etc/grub.d/40_custom) to add Remix OS as a boot menu entry. I initially created the entry using grub.cfg in the RemixOS folder as a guide.
Here's a screenie for the Remix directory:
/F (Remix OS partition)
/F/RemixOS
Hope this is helpful.
Thanks!
Kp
Click to expand...
Click to collapse
Where is your system.sfs/kernel/initrd/ramdisk.img?
In the efi folder maybe?

---

Oh, ur kernel initrd and rmdisk system.sfs should all be in the RemixOS folder. I didn't look closely sorry. @HypoTurtle catched the problem.
The official installer wouldn't put system.sfs to anywhere else than RemixOS. You must've fiddled with the files. I've never heard of this kind of file setup.
I hope the recent OTA didn't go this wrong.

---

I installed Remix-OS (iso downloaded today) on my brother's laptop today after installing Manjaro Linux.
it failed to add itself in grub, and os-prober doesn't find it, but simply adding to /etc/grub.d/40_custom:
Code:
menuentry "Remix-OS" {
set root=(hd0,1)
linux /RemixOS/kernel
initrd /RemixOS/initrd.img
}
solved it.
you have to check out the HD numbering of Grub. the partition was the first of the only HD and I had to choose "hd0,1"

---

Vioner said:
You must've fiddled with the files. I've never heard of this kind of file setup..
Click to expand...
Click to collapse
I'm pretty sure I haven't messed with the files at all.
Here's a timeline of what I did before and after the update:
Got notification that a new update had been downloaded. Hit reboot and update. Computer reboots, and I select Remix in the GRUB menu. Remix boots to a blue update screen with a percentage bar. The update completes and the Remix desktop appears. I use Remix for about five minutes and then shut down. A few hours later, I try to boot into Remix, but it shows a black terminal-like screen with the "cannot find kernel" error.
I'm pretty sure I haven't done anything unusual with the system or files. I've searched in the Remix partition, but the kernel folder, rmdisk, and system.sfs are all missing. I don't understand how Remix was able to work at all after the update if those files were missing. Since those vital files are missing, I guess I'll have to reinstall Remix. Is it possible to me to keep data.img, reinstall the system files, and then copy it in so I don't have to reinstall all my apps and files?
Thanks for your help,
Kp

---

Yes, of course you can move data.img elsewhere and then restore it after reinstall.
Have you looked for the missing files? It'd be good to know where they landed eventually.

---

Vioner said:
Yes, of course you can move data.img elsewhere and then restore it after reinstall.
Have you looked for the missing files? It'd be good to know where they landed eventually.
Click to expand...
Click to collapse
They're nowhere to be found. Turned every folder inside out.

---

Kpenguin.5284 said:
I used the Windows official tool to install it on its own partition. I manually edited GRUB (/etc/grub.d/40_custom) to add Remix OS as a boot menu entry. I initially created the entry using grub.cfg in the RemixOS folder as a guide.
Here's a screenie for the Remix directory:
/F (Remix OS partition)
/F/RemixOS
Hope this is helpful.
Thanks!
Kp
Click to expand...
Click to collapse
you are still having that problem? kernel and initrd.img should be in that boot folder

---

Just did a fresh install of the latest version of Remix OS using the official installer tool. My /RemixOS folder looks like this:
My grub config file in /etc/grub.d/40_custom looks like this:
Code:
menuentry "Remix OS" --class remixos --class android-x86 --class gnu-linux --class os {
set root=(hd0,6)
search --file --no-floppy --set=root /kernel
linux /RemixOS/kernel root=/dev/ram0 SERIAL=random logo.showlogo=1 androidboot.selinux=permissive quiet DATA= USB_DATA_PARTITION=1
initrd /RemixOS/initrd.img
}
Remix still won't boot from GRUB and shows this error whenever I try to boot:
Code:
error: no such device: /kernel.
error: file '/RemixOS/kernel' not found.
alloc magic is broken at 0x9e64ae80: 9e524a20
Aborted. Press any key to exit.
Can someone please post what my grub config needs to look like in order for Remix to work? What am I doing wrong here? I copied the grub configuration out of /boot/grub/grub.cfg in the Remix partition. Please help.
Thank you!
Kp

---

Kpenguin.5284 said:
Just did a fresh install of the latest version of Remix OS using the official installer tool. My /RemixOS folder looks like this:
My grub config file in /etc/grub.d/40_custom looks like this:
Code:
menuentry "Remix OS" --class remixos --class android-x86 --class gnu-linux --class os {
set root=(hd0,6)
search --file --no-floppy --set=root /kernel
linux /RemixOS/kernel root=/dev/ram0 SERIAL=random logo.showlogo=1 androidboot.selinux=permissive quiet DATA= USB_DATA_PARTITION=1
initrd /RemixOS/initrd.img
}
Remix still won't boot from GRUB and shows this error whenever I try to boot:
Code:
error: no such device: /kernel.
error: file '/RemixOS/kernel' not found.
alloc magic is broken at 0x9e64ae80: 9e524a20
Aborted. Press any key to exit.
Can someone please post what my grub config needs to look like in order for Remix to work? What am I doing wrong here? I copied the grub configuration out of /boot/grub/grub.cfg in the Remix partition. Please help.
Thank you!
Kp
Click to expand...
Click to collapse
I don't know what all those extra options are supposed to be doing, but they werent necessary on the install I did for my brother.
You can try a simple:
menuentry "Remix OS" {
set root=(hd0,6)
linux /RemixOS/kernel
initrd /RemixOS/initrd.img
}
Click to expand...
Click to collapse

---

capoeiraES said:
I don't know what all those extra options are supposed to be doing, but they werent necessary on the install I did for my brother.
Click to expand...
Click to collapse
I'm nearly positive those options aren't causing the issue. I tried that setup, and it didn't work.

---

Kpenguin.5284 said:
I'm nearly positive those options aren't causing the issue. I tried that setup, and it didn't work.
Click to expand...
Click to collapse
there is defently some problem with those options since they seam to try to set /kernel as a the root as if it was a HD
try if you find a solution with this search https://www.google.com.br/search?q=...=chrome..69i57j69i58&sourceid=chrome&ie=UTF-8

---

capoeiraES said:
there is defently some problem with those options since they seam to try to set /kernel as a the root as if it was a HD
try if you find a solution with this search https://www.google.com.br/search?q=...=chrome..69i57j69i58&sourceid=chrome&ie=UTF-8
Click to expand...
Click to collapse
I tried the configuration you posted, but no cigar. It's rather late right now where I live, so I can't look at the search you posted right now, but I will look at it as soon as I can. Thanks!

---

Update: Checked the search you posted, didn't find anything useful...

---

from what I read here, https://wiki.archlinux.org/index.php/GRUB, that search option is to search for the root partition. so having both lines, one to set root, and the other to search for it doesn't make sense.
I'm no grub expert. try to find help in a Linux forum.
Anyways, you can try to comenting that search line out