[SOLVED] Grub entry for Arch console-mode

Is there any way to add a grub menuentry to start arch without x?
Last edited by Quatro (2014-08-21 00:14:42)

By menuentry i assume you mean one other than the default for arch.
There is, I believe this may help you. https://wiki.archlinux.org/index.php/GR … b-mkconfig
Currently on phone so its too hard to give exact instructions atm. Internets out -.-

Similar Messages

Grub (os-prober) doesn't generate the right entries for Arch

I'm getting Arch installed (on a separate partition) from a system which has Manjaro on it already. [I had lots of trouble yesterday and finally just had Manjaro do a complete install, because I couldn't get the EFI boot to work, so that's why I'm started from that.]
Manjaro generates entries for itself which work, and it generates entries for Arch, but it fills in the UUID and hdX,gptX information for Arch wrong - it puts the same information in as for itself.
I've checked under Arch's own /boot/grub/grub.cfg and that file has the correct entries.
How do I get the os-prober to see these? (i'm running the grub-update while the Arch partition is mounted).

CarlD wrote:
If I understand your post correctly, you are installing on a UEFI system. os-prober basically doesn't work on UEFI (i.e. it only works for BIOS systems).
Gummiboot is a better alternative, as it will automatically detect installed OSs via their .efi stubs.
Ah, I didn't know that (this is the first time I've done anything substantial in terms of config on an UEFI system).
Is Gummiboot fairly easy to set up? It'll find the other OSs .efi entries? I'm somewhat loath to fiddle with this as I ended up with an unbootable system yesterday (now Manjaro's installer has something in place which works (for itself), which is GRUB based).
Additional:
Right now Manjaro has got some sort of "legacy_boot" partition (256MiB) mounting at /boot, and the actual EFI partition (100MiB) mounting at /boot/efi. I understand that I should actually have the EFI partition mounting directly at /boot but am worried about a non-breaking way of trying to setup gummiboot.
Last edited by emacsomancer (2014-10-01 17:37:06)

Grub entry for debian

Hi,
this is my grub menu.lst
(hd0,0)=windows
(hd1,0)=boot for Arch.
(hd1,1)= Swap
(hd1,2)=root for Arch.
(hd1,3)=(debian) note yet.
Can I just just use part hdb4 or will better if i create a boot partion and root partion for debian in order to to have a better grub entry for it.
Thanks

Yes, you can put them there.
The tricky part is that you've already got four (primary) partitions, so you need to delete one of them to replace it with an extended partition... Not very fun.
If you can afford the time/effort, you might want to wipe out all partitions but the Windows one and re-partition the drive with extended ones (or combine Arch's root and /boot parts into one, so each distro only takes a single partition).

[SOLVED] Grub Entry to boot via UUID

I'm trying to get my system booting by UUID but I am having issues with the grub entry as it won't boot. The following is the non uuid one that works:
# (2) Arch Linux
title Arch Linux sda5
root (hd0,4)
kernel /boot/vmlinuz-linux root=/dev/sda5 ro
initrd /boot/initramfs-linux.img
And below are the two that I have tried for uuid:
title Arch Linux by UUID (sda5)
uuid 857136db-0356-46bd-9fff-0126b575218b
kernel /boot/vmlinuz-linux root=UUID=857136db-0356-46bd-9fff-0126b575218b
initrd /boot/initramfs-linux.img
and
title Arch Linux by UUID (sda5)
uuid 857136db-0356-46bd-9fff-0126b575218b
kernel /boot/vmlinuz-linux root=/dev/disk/by-uuid/857136db-0356-46bd-9fff-0126b575218b
initrd /boot/initramfs-linux.img
Can someone point out which bit is wrong?
Thanks
Last edited by morphjk (2011-10-11 04:08:53)

Try:
title Arch Linux by UUID (sda5)
kernel /boot/vmlinuz-linux root=/dev/disk/by-uuid/857136db-0356-46bd-9fff-0126b575218b
initrd /boot/initramfs-linux.img
You may need the root (hd0,4) line as well. I think that is required to tell Grub where to find it's intermediate files. It would go in front of the kernel line.
Edit: I assume, of course, that your UUID is correct You might check that.
Last edited by ewaller (2011-10-11 03:16:48)

[solved] fstab entry for user mounting of iso files?

fstab entry for user mounting of iso files?
I've seen it before but I can't seem to find it again.
Last edited by eilenbeb (2010-03-21 20:11:40)

I did, but couldn't find what I was looking for.
I got fuseiso to work, and that will do the trick, so I'm marking this one solved.
(I simply had to give 'others' write access to the mount point)
Last edited by eilenbeb (2010-03-21 20:15:09)

[solved] GRUB parameters for specific kernel

Is any way for putting options in _specific_ kernel and not using GRUB_CMDLINE_LINUX_DEFAULT? I want to pass
"apparmor=1 security=apparmor"
in linux-apparmor
Thanks a lot,
Last edited by xanb (2015-03-09 11:37:04)

xanb wrote:
mkoskar wrote:Have you looked inside "/etc/grub.d/"?
What about "/etc/grub.d/40_custom"?
This is not exactly what I want: I have already defined the entries. So I don't need to have specific entries (40_custom is for that purpose).
I have "GRUB_DEFAULT='gnulinux-advanced-ef7df8c4-97a9-45d9-a80e-7a16254034b0>gnulinux-linux-advanced-ef7df8c4-97a9-45d9-a80e-7a16254034b0'" in /etc/default/grub. I wonder if I could add CMDLINE only to this entry....
Please post following:
# grep -E '^menuentry' /boot/grub/grub.cfg
$ ls -la /boot/vmlinuz-*
$ ls -la /vmlinuz-*
$ ls -la /boot/kernel-*
$ grep -Ev '^(#|$)' /etc/default/grub
You say you installed "linux-apparmor", I assume it drops kernel in /boot, and then you just regenerate grub which picks it up. Right?
Just go to /boot/grub/grub.cfg and take the whole relevant menuentry and paste it in /etc/grub.d/40_custom, there just modify it to your liking.

[SOLVED] Cookie settings for Arch Linux forum

I really do like the Arch Linux forum.
It is fast, plain and simple; perfect for a distro which is the same
But one thing is bothering me; the cookies.
The arch forum is the only forum for me where the 'new post' colored picture at the left side of the forum parts is not unmarked after reading the new posts.
After I have read all new posts, I do 'mark all topics as read' (the link at the right top) to have this result.
For example phpbb forums do have cookie settings where the forums which are read, automatically turn the 'new post' icon off; it is not colored but the normal color again.
Can it be that some forum settings are not completely right and this should be also the case at the Arch forums?
Hope I have explained it that way you can understand what I mean.
Jan
Last edited by Lontronics (2007-03-03 17:07:04)

Yes, and it has nothing to do with the cookie (except a session).. at least i hope it doesn't cuz that would just make me twice as glad that we switched away from that horrid chunk of code called phpbb.
And on that note, search around a bit, because this has already been explained like three times.

[Solved] Basic research for arch beginner - kernel

Hello,
if i want to compile my own new kernel so i create a directory to
"/usr/src/" like "linux-2.6.17.7". So i have in some cases more like one kernel directory.
Other distributions set a symlink to the actual kernel directory with
the name "linux", because in the system is "linux" the reference.
So it easy to change the link to the actualy kernel-directory.
I have seen, that Archlinux don't use a symlink to the kernel-directory.
How can i change the reference in the system for a new kernel-directory,
because i think if i compile some modules, the system will got every time
the "old" modules directory and not the new one ?
Thank you and
best regards
bademeister

brain0 wrote:
What does "the actual kernel-directory" mean? There is absolutely no part of the system that looks for /usr/src/linux.
You only need the source (or at least part of it) to compile external modules. The necessary headers are located via the /lib/modules/$(uname -r)/build/ directory.
As said above, you should use abs for kernel compilation so that pacman can keep track of the files.
The best solution for 99% of the users is using the stock kernel anyway, as it is slim and modular, supports all you need and there are tons of precompiled kernel modules for it in the repos.
Hi brain0,
"the actual kernel-directory" means, which directory is now use by the system.
For example, if i download the kernel and place it to /usr/src/linux-2.6.17.7, so i have two directories. With the old kernel before (linux-2.6.17-ARCH) and my new one.
"uname -r" show me the reference directory, now with "2.6.17-ARCH", also
all modules will loaded from: /lib/modules/2.6.17-ARCH/.
Now i compile the new kernel (linux-2.6.17.7-NEW) and during the compilation, all modules will be copied to the new module directory:
/lib/modules/2.6.17-NEW/.
If i look to the reference directory with "uname -r", so i get
2.6.17-ARCH again. All kind of modules will be loaded from the old directory.
So i'm looking for a solution to switch the reference directory, that
all modules will be loaded from "/lib/modules/2.6.17-NEW/".
Regards
bademeister

[SOLVED]Two entries for the same partiotion in Nautilus

Hi, I'm trying to auto-mount two (recently converted from NTFS to) EXT4 partitions using /etc/fstab, everything works fine but I now have 4 icons in Nautilus' Device section.
/etc/fstab:
#/dev/sda7:
UUID=3a3baae3-b81e-485b-9994-9ea14c31f914 /media/VMs ext4 defaults,users,exec,relatime 0 2
#/dev/sda8:
UUID=00b28db3-bf6f-44ad-8674-572e2302024a /media/Games ext4 defaults,users,exec,relatime 0 2
Screenshot:
If I comment out an entry in /etc/fstab and save, the icon disappears immediately.
EDIT: Never mind, I removed ',users' and everything is fine now, sorry
Last edited by rAX (2011-08-19 20:42:31)

Try this:
1) Highlight all tracks you want in the same album.
2) Right-Click, Get-Info.
3) Edit the Album name - This will populate the same ALbum name across all selected tracks.
You may or may not want iTunes organizing your music. If 'yes' then the physical song files will be re-arranged on your PC's folder structure.
Best of Luck

Efibootmgr & gummiboot replaced UEFI entry for Windows Boot Manager

TLDR
I am now in Windows 7 and dual boot with Arch is working fine.
But before I update Arch, I would like to understand what happened, as in why adding an efibootmgr entry for Arch replaced/deleted the Windows Boot Manager entry although I followed the BG.
The status of my UEFI boot menu was, before the installation of Arch:
Windows Boot Manager
AHCI HDJ... (hard drive 1)
AHCI ST... (hard drive 2)
While working through the BG, I decided to use gummiboot=> https://wiki.archlinux.org/index.php/Be … #Gummiboot. So:
pacman -S gummiboot
gummiboot install
pacman -S efibootmgr
gummiboot install
[some error ocurred, as mentioned in red box]
efibootmgr -c -L "Gummiboot" -l /EFI/gummiboot/gummibootx64.efi
nano /boot/loader/entries/arch.conf
title Arch Linux
linux /vmlinuz-linux
initrd /initramfs-linux.img
options root=/dev/sdb3 ro
[CTRL + X, Y, Enter]
exit
umount /mnt/{boot,home,}
reboot
I then saw a new list of the UEFI boot order:
Gummiboot
AHCI HDJ... (hard drive 1)
AHCI ST... (hard drive 2)
Chose Gummiboot and it brought up a gummiboot menu with entries
Arch Linux
Windows Boot Manager
EFI Shell something
Selected Arch Linux and it went to a message something along "boot device ' ' not found" and I was in a shell which was, I think, rootfs.
I rebooted via the button on my desktop and out the Arch Linux USB drive back. After mounting the partitions:
gummiboot remove
efibootmgr
[0000: Windows Boot Manager
[0001: Arch Linux
[0002: AHCI HDJ...
[0003: AHCI ST...
exit
umount /mnt/{boot,home,}
reboot
Now I booted into a black screen with white text which said something "Reboot and select proper Boot device"
=> Inserted Win 7 64-bit DVD, repaired the boot sector. Rebooted, saw I had these entries again:
Windows Boot Manager
AHCI HDJ... (hard drive 1)
AHCI ST... (hard drive 2)
The boot into Windows worked fine. Rebooted, chrooted into my install again and:
efibootmgr
[0000: Arch Linux
[0001: Windows Boot Manager
[0003: AHCI HDJ...
[0003: AHCI ST...
efibootmogr -b 0 -B
Then I used the EFISTUB method:
efibootmgr -c -L "Arch Linux" -l /vmlinuz-linux -u "root=/dev/sdb3 ro initrd=/initramfs-linux.img"
efibootmgr
[0000: Windows Boot Manager
[0001: Arch Linux
[0002: AHCI HDJ...
[0003: AHCI ST...
exit
umount /mnt/{boot,home,}
reboot
On reboot, 'Windows Boot Manager' was again replaced by 'Arch Linux'.
=> Inserted Win 7 64-bit DVD, repaired the boot sector.
Rebooted, I have now Windows Boot Manager + Arch Linux and dual boot works now.
My questions:
What is going on with efibootmgr replacing/deleting the Windows entry? Is there something wrong with my UEFI menu?
In connection with 1., I would like to sync the EFISTUB Kernel (wiki entry) before I run pacman -Syu. Can I do that now?
Can I uninstall gummiboot now?
Last edited by jones (2013-07-11 12:30:55)

henrik wrote:So in light of your post, I decided to ditch EFISTUB + gummiboot and try out GRUB. Thanks for clearing it up a bit. Which is what confuses me a great deal more, as GRUB/gummiboot obviously do not meddle with Microsoft's EFI files. Right?
EFI relies on two things to boot:
Boot loader program files on the ESP (or occasionally elsewhere).
NVRAM entries pointing to the boot loader files.
Your own problems seem to be with the NVRAM entries, not with the boot loader files themselves. Unfortunately, managing those NVRAM entries has proven to be problematic because of bugs in specific EFI implementations, bugs in efibootmgr and other tools that manipulate the NVRAM entries, poor documentation, and other factors.
To answer your question, though, no boot loader should mess with another's files. Such things can happen, though. The number of bugs that cause Microsoft's boot loader (EFI/Microsoft/Boot/bootmgfw.efi) to be treated deferentially have provoked some tools to use it as a target location for other boot loaders. (Ubuntu's Boot Repair tool does this in a rather overzealous way. So does my own rEFInd installer script, but only under certain narrow circumstances.) Also, the EFI/BOOT/bootx64.efi file is a special case; it's the fallback bootloader that's used when NVRAM entries are missing or don't work, and various boot loader installation procedures place copies in that location, so it can be overwritten and could contain just about anything.
However, the whole thing happened again with GRUB. So I did the whole "repairing Boot problems" with the Windows DVD rescue thingy again and deleted all non-Microsoft files from the EFI partition, /dev/sda1.
Then I formatted / (root) and installed arch again and followed the Beginners' Guide which suggest mounting /dev/sda1/ to /mnt/boot (in contrast to the GRUB entry where the ESP should be mounted to /mnt/boot/efi).
I strongly advise against doing a complete re-installation just to overcome a boot loader problem. Instead, figure out what the problem is and fix it. Doing a complete re-installation is not likely to fix anything, and depending on precisely how you do it, you could end up with a more complex problem. The reason is that the re-installation is not likely to erase the NVRAM entries from the old installation, so you could find that you've got additional stray NVRAM entries. If you do happen to fix the problem by re-installing (say, because you selected a different installation option), you're not likely to know what changed to fix the problem, so you could end up in the same boat should you need to re-install again in the future.
But it did not show this line
Found Windows 7 (loader) on /dev/sda1
... how come??
I've given up trying to understand GRUB's configuration scripts. You could try creating an entry manually by editing /etc/grub.d/40_custom; or you could forget about using the GRUB scripts and create a hand-crafted grub.cfg; or you could forget about using GRUB at all. I'm not a fan of GRUB, so my personal choice is the final one.
So for all the headache and time ... should I delete the EFI partition and recreate it maybe? I think it's possible using the Windows 7 DVD.
But somehow using efibootmgr on my UEFI list somehow invalidated the Windows entry.
Reviewing your posts, it seems that you want to use the EFI stub loader directly, but you're having problems with that because when you add it to the NVRAM entries, Windows drops off your boot manager's boot options. The obvious solution to this problem is to forget about adding the EFI stub loader directly to the NVRAM entries, and instead add a boot manager that can handle either a Linux kernel or the Windows boot loader. (IMHO, this is the superior solution anyhow; I disagree with the Arch wiki's emphasis on using the EFI stub loader "raw.") It seems you were trying to do this with GRUB but had problems booting Windows. Earlier you tried gummiboot but had problems booting Linux. My suggestion is to either go back to gummiboot and fix its problem or try rEFInd. The "device not found" error you reported with gummiboot is usually caused by either a missing (or incorrectly-specified) initrd file or by an incorrectly-specified "root=" option passed to the kernel. Check those possitilities, and if you need help, report what happens in more detail. If necessary, take a digital photo of the screen and post it here. (Make sure it's legible, though!)
You can try rEFInd with minimal disk by using a CD-R or USB flash drive image. Boot with that and your NVRAM and ESP won't be affected at all. If you can get rEFInd working from the flash drive, you can then install it to your hard disk and it should continue working. Note that you probably won't be able to boot Linux directly from rEFInd with your current configuration without adding a "root=" specification to the kernel command line. You can do this by hitting F2 or Insert twice rather than launching Linux by pressing Enter. Alternatively, you can create a refind_linux.conf file in the directory that holds your kernel. That file's contents are described in the rEFInd documentation.

[Solved] Dual UEFI Booting Arch against pre-existing Ubuntu install

Hi All,
I'm new to Arch Linux and have just managed to install it on my T530 Lenovo laptop along side a pre-existing Ubuntu installation.
However, although I did consult the dual boot posting and article here on the site beforehand, those articles seemed to be about installing Grub. Since I already have it up and working, I was nervous about deleting it and so potentially loosing my working Ubuntu installation.
I tried installing mounting my pre existing /boot/efi partition but the pre-existing vmlinuz-linux file (no doubt from my Ubuntu installation) prevented it from working. My solution was to create the boot folder on the same partition as my Arch installation.
I now have an installation that works (kind of) however, it appears each time I boot up, I have to edit the Grub entry for my Arch installation to update the UUID Grub points to to get it to load up Arch. I can't find where the actual file being loaded in Grub resides (the file that it appears generates this script, is itself built from a series of predefined variables).
I admit I am playing at the moment - I'm keen to get to grips with this distro and am up for considering all options including deleting and starting again to learn to get it set up correctly. My questions are:
How should I have done this so that my Arch linux distro was loaded via Grub called by the UEFI and had the same booting file structure as the already existing Ubuntu installation (using the BOOTLOADER partition and the /boot/efi folders on it)
How do I edit the Grub file for my Arch distro so it stays edited (no more retyping all the UUIDs each time I load it up
Is there a way to get to the installation I currently have to an the more ideal state
Details taken thanks to the bootrepair application are here:
http://paste.ubuntu.com/10682898/
Thanks and regards,
Simon
Last edited by simon_sjw (2015-04-22 11:50:52)

I don't think there are any Ubuntu kernel images on your EFI system partition (they are in /boot, not /boot/efi).
If you want Arch to boot in an EFI system you should mount /boot (rather than /boot/efi) to the EFI system partition.
To do this, copy the /boot folder over to /dev/sda1 and add it to your /etc/fstab (in Arch):
/dev/sda1 /boot vfat rw,relatime,discard,nodev,nosuid,noexec,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
It's probably best to install & configure GRUB from Arch rather than Ubuntu because Arch mounts /boot to the ESP while all other distributions mount /boot/efi so the results may get confusing (ie, GRUB may create menu entries to boot Ubuntu with your Arch kernel and vice versa); also the Arch kernel image is booted read-write whereas most other kernel images are booted read-only.
https://wiki.archlinux.org/index.php/GRUB#UEFI_systems
I find the os-prober script can fail sometimes so this is probably your problem here.
Personally, I use gummiboot to boot my Debian system by copying the kernel image & initial ramdisk to the EFI system partition using these commands in Debian (this would also work in Ubuntu):
# mount /dev/sda1 /mnt
# cp /vmlinuz /initrd.img /mnt
Then I make a gummiboot menu entry; your Ubuntu entry would look like this:
title Ubuntu
linux /vmlinuz
initrd /initrd.img
options root=/dev/sda2 ro
Add any kernel parameters after "ro" and make an entry for Arch as well (you may also need to configure /boot/loader/loader.conf as per the ArchWiki page) & install gummiboot from Arch using:
# gummiboot install
You can then create a post-install script at /etc/kernel/postinst.d/zz-update-gummiboot in your Ubuntu system to copy over the kernel image & initrd to the ESP whenever the kernel is updated:
#!/bin/sh
mount /dev/sda1 /mnt
cp /vmlinuz /initrd.img /mnt/
umount -R /mnt
Make this executable:
# chmod +x /etc/kernel/postinst.d/zz-update-gummiboot
This method will only work if you have /boot mounted to the EFI system partition (as outlined in the Beginner's Guide).

.jar installer fails in console mode over missing X / variable DISPLAY

Hi all,
I tried to install the WebLogic Server in console mode according to the Installation Guide for Oracle WebLogic Server 12c Release 1, but couldn't get past an error.
My system is a CentOS 6.4 with kernel 2.6.32-358.el6.i686 in a VMWare virtual machine, running text mode only (X is not installed). I have JRockIt installed, and variables MW_HOME, JAVA_HOME and PATH defined accordingly, and I am using a dedicated user to this installation. Both JRockIt and WLS are being installed in this user's home directory.
I downloaded the generic .jar installer for WebLogic Server 12.1.2 (wls_121200.jar) and tried to install the server in console mode, with this command:
java -jar <path>wls_121200.jar -mode=console
In the initial checks, the installer complains that the environment variable DISPLAY is not set and asks if I want to continue or not. The installation guide says this is not required for a console mode installation, so I chose to continue anyway. Then the installation fails with a Java exception:
java.awt.HeadLess exception:
No X11 DISPLAY variable was set, but this program performed an operation which requires it.
(Then the usual class dump)
Should the console mode install ask for X? Did I miss anything? What should I do to be able to install the server in console mode?
Many thanks,
Emerson

Hi,
There is no console mode in WebLogic 12.1.2. It has been remove.
See MOS note: "WebLogic Server 12.1.2 Generic Install Jar File Fails To Recognize Console Install Mode (Doc ID 1577869.1)"
Regards Peter

[SOLVED] Grub boots to rescue mode err: unknown filesystem every drive

So I installed Arch and it all seemed to go reasonably well (well, had a little trouble installing GRUB to begin with, but I think that's just because I needed a BIOS boot partition at the start of the drive). I installed it onto a 4TB I have, which due to its size has a GPT partition table even though my mobo (Gigabyte GA-P67A-UD4-B3, don't think it matters though) uses a regular old BIOS. Initially it was two partitions, the Microsoft reserved partition then a big NTFS data partition. I shrunk the NTFS partition and then made (in this order on the disk, starting at third) an ext4 partition for /boot, a swap partition, and a big btrfs partition (in which I created subvolumes for /, /etc, /home and /var). GRUB wouldn't install (I forgot the exact error) but what I could find suggested it was because there needed to be room for it at the start of the disk, so I deleted the Microsoft reserved partition (Windows is installed on an SSD, and its bootloader is on another hard drive entirely, so I didn't think I needed it) and created an empty partition with the right code using gdisk, then I could install GRUB to the 4TB HDD.
Unfortunately, when I try to boot into GRUB it immediately comes up with error: unknown filesystem and dumps me at the GRUB rescue prompt. Using ls, I can see my HDDs and their partitions, but whenever I try to use (for example) ls (hd0,gpt3)/ - which I think should probably be the ext4 boot partition, but it does this for everything - it just says error: unknown filesystem again.
This seems pretty close to (if not exactly the same as) my problem, so I tried what he suggested, but when I tried to run the command he says worked, (grub-install --recheck --disk-module=native /dev/sda) - and don't worry, I didn't do that blindly, I know /dev/sda is my 4TB HDD - I just get the error grub-install: --disk-module: (PROGRAM ERROR) Option should have been recognized!?. So I'm all out of ideas and I've been trying for a few hours. Please help me, before I go insane... more insane. I can boot the USB drive I used to install Arch and chroot into my installation, but I haven't found a way to actually boot the installation yet.
SOLVED: Apparently the partition I was using for /boot was too far back on the drive (past the first 2TB). When I shuffled partitions around so that the /boot partition was near the start of the drive (it starts at sector 2048 now!) that seemed to fix it.
Last edited by Slashee the Cow (2015-04-12 15:36:51)

Tried using insmod btrfs in the grub rescue shell last night. Didn't work, can't remember if the insmod command itself gave me an error or whether it still couldn't see any files or anything. Tried it again today, but that was after I converted /dev/sda3 back to ext4 and mounted it at /boot (since it being ext2 wasn't working, and not using it wasn't working, so I figure what's the harm) and I just got error: unknown filesystem.
Anyway: using grub-install from outside chroot seems to work (still can't use --disk-module), but grub-mkconfig just generates this:
# DO NOT EDIT THIS FILE
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
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}"
save_env saved_entry
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 ext2
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root ec4cf3cd-d72d-4988-a2ce-421f45d52824
else
search --no-floppy --fs-uuid --set=root ec4cf3cd-d72d-4988-a2ce-421f45d52824
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_input console
terminal_output gfxterm
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=5
fi
### END /etc/grub.d/00_header ###
### 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/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### 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/60_memtest86+ ###
if [ "${grub_platform}" == "pc" ]; then
menuentry "Memory Tester (memtest86+)" --class memtest86 --class gnu --class tool {
search --fs-uuid --no-floppy --set=root ec4cf3cd-d72d-4988-a2ce-421f45d52824
linux16 /boot/memtest86+/memtest.bin
fi
### END /etc/grub.d/60_memtest86+ ###
I'm not an expert on GRUB configuration files, but I figured that even if that didn't just boot me straight to the rescue shell, it wasn't going to boot anything... other than memtest86+ maybe. So I went back into chroot and run grub-mkconfig and it generated this:
# DO NOT EDIT THIS FILE
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
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}"
save_env saved_entry
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
set root='hd0,gpt5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt5 --hint-efi=hd0,gpt5 --hint-baremetal=ahci0,gpt5 b21e6211-5e7a-4769-9f53-b9b5d554a242
else
search --no-floppy --fs-uuid --set=root b21e6211-5e7a-4769-9f53-b9b5d554a242
fi
font="/root/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_input console
terminal_output gfxterm
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=5
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch Linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-b21e6211-5e7a-4769-9f53-b9b5d554a242' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
set root='hd0,gpt3'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3 184916fd-57a7-48cf-858e-93a5d339ade2
else
search --no-floppy --fs-uuid --set=root 184916fd-57a7-48cf-858e-93a5d339ade2
fi
echo 'Loading Linux linux ...'
linux /vmlinuz-linux root=UUID=b21e6211-5e7a-4769-9f53-b9b5d554a242 rw rootflags=subvol=root quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux.img
submenu 'Advanced options for Arch Linux' $menuentry_id_option 'gnulinux-advanced-b21e6211-5e7a-4769-9f53-b9b5d554a242' {
menuentry 'Arch Linux, with Linux linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-advanced-b21e6211-5e7a-4769-9f53-b9b5d554a242' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
set root='hd0,gpt3'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3 184916fd-57a7-48cf-858e-93a5d339ade2
else
search --no-floppy --fs-uuid --set=root 184916fd-57a7-48cf-858e-93a5d339ade2
fi
echo 'Loading Linux linux ...'
linux /vmlinuz-linux root=UUID=b21e6211-5e7a-4769-9f53-b9b5d554a242 rw rootflags=subvol=root quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux.img
menuentry 'Arch Linux, with Linux linux (fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-fallback-b21e6211-5e7a-4769-9f53-b9b5d554a242' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
set root='hd0,gpt3'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3 184916fd-57a7-48cf-858e-93a5d339ade2
else
search --no-floppy --fs-uuid --set=root 184916fd-57a7-48cf-858e-93a5d339ade2
fi
echo 'Loading Linux linux ...'
linux /vmlinuz-linux root=UUID=b21e6211-5e7a-4769-9f53-b9b5d554a242 rw rootflags=subvol=root quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux-fallback.img
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows Vista (loader) (on /dev/sdb1)' --class windows --class os $menuentry_id_option 'osprober-chain-4E94BAB294BA9C41' {
insmod part_gpt
insmod ntfs
set root='hd1,gpt1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt1 --hint-efi=hd1,gpt1 --hint-baremetal=ahci1,gpt1 4E94BAB294BA9C41
else
search --no-floppy --fs-uuid --set=root 4E94BAB294BA9C41
fi
chainloader +1
menuentry 'Windows Vista (loader) (on /dev/sde1)' --class windows --class os $menuentry_id_option 'osprober-chain-CEF01053F010445D' {
insmod part_msdos
insmod ntfs
set root='hd4,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd4,msdos1 --hint-efi=hd4,msdos1 --hint-baremetal=ahci4,msdos1 CEF01053F010445D
else
search --no-floppy --fs-uuid --set=root CEF01053F010445D
fi
chainloader +1
menuentry 'Windows Vista (loader) (on /dev/sde5)' --class windows --class os $menuentry_id_option 'osprober-chain-4E94BAB294BA9C41' {
insmod part_msdos
insmod ntfs
set root='hd4,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd4,msdos5 --hint-efi=hd4,msdos5 --hint-baremetal=ahci4,msdos5 4E94BAB294BA9C41
else
search --no-floppy --fs-uuid --set=root 4E94BAB294BA9C41
fi
chainloader +1
### END /etc/grub.d/30_os-prober ###
### 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/60_memtest86+ ###
### END /etc/grub.d/60_memtest86+ ###
Still didn't work though.
I don't know grub config, but is the UUID specified in
linux /vmlinuz-linux root=UUID=b21e6211-5e7a-4769-9f53-b9b5d554a242 rw rootflags=subvol=root quiet
supposed to be the UUID for /boot or /? Because the UUID there is for the btrfs partition being mounted at / (which I guess would explain why it has the correct subvol listed, which I'm not sure if it's necessary, given that should be the default subvolume). So... that's probably alright (just something that stood out to me).
As for installing grub on another disk: I suppose I could try, though I'd rather keep it on one drive if I can (sometimes it gets complicated enough having Windows and my Windows bootloader on different drives... I should probably try moving the Windows bootloader to the SSD where Windows is installed. Would it matter which drive? The options are:
sda: 4TB, GPT table, the one I'm having problems with now
sdb: 2TB, MBR table, nothing in boot sector AFAIK
sdc: 240GB SSD, GPT table, would rather not use it since Windows is installed on there, even if its bootloader isn't
sdd: 1TB, MBR table, nothing in boot sector AFAIK
sde: 500GB, MBR table, has the Windows bootloader so I'd rather not mess that up (although given it's the smallest and I have no free SATA ports, it'll be next to go when I need more space, so I might want to move the bootloader)
(sdf and sdg which appear in lsblk earlier are just USB flash drives, and I'd rather not have to rely on having to use one of them to boot Linux).
As for repartitioning /dev/sda: as long as I can do it non-destructively, sure. Well I mean non-destructively for the NTFS partition, which is mostly full of Steam games (and I might have enough room on other drives and portable drives to keep the rest safe), but on my crappy Australian internet connection (aren't they all) it'd probably take me a couple of weeks to redownload them. I don't mind if I have to get rid of the Linux partitions, I already tried going through the install again once before to try to get it to work, another time isn't going to matter. So I guess I could try using gparted to delete the Linux partitions, move the NTFS partition to the end of the disk, and recreate the Linux partitions in front of it (although moving that much data might take a while, so I'd probably want to do it overnight). For reference, right now it's:
128MB of unformatted space (where the Microsoft reserved partition was, but now it's flagged as a BIOS boot partition, even though it's far bigger than it needs to be for that, I didn't feel like moving the other partitions back just to claim less than 128MB)
~2.7TB NTFS data partition (important)
~1GB ext4 /boot partition
8GB swap partition
~1TB btrfs partition with subvolumes mounted at /, /home, /etc and /var

[SOLVED] Need help with rEFInd boot entry for rsync backup

I made a successful backup my arch install to an other internal SSD disk (from my HDD).
But now I can't figure out how to make a boot entry for this drive. The wiki only mentions GRUB, which I do not use.
This is the fstab for my HDD:
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda5
UUID=c1822e3c-e037-4445-bdd8-b71778237dee / ext4 rw,relatime,data=ordered 0 1
# /dev/sda2 LABEL=SYSTEM_DRV
UUID=D2DF-9F74 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
And this is the fstab on my SSD which I edited:
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sdb1
UUID=c61a1301-4728-465d-b40b-bde5e084eb50 / ext4 rw,relatime,data=ordered 0 1
# /dev/sda2 LABEL=SYSTEM_DRV
UUID=D2DF-9F74 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
But I'm not sure about the /boot entry, do I need something else here?
Afterward I tried updating rEFInd by reinstalling using refind-install, but that did not work.
ps. I dual boot with Windows.
Last edited by Devenda (2014-08-18 07:58:07)

I also tried adding the menu entry manually by editing refind.conf but that didn't work. I got:
Invalid loader file!
Error: Not Found while loading vmlinuz-linux
Here is some additional info:
refind.conf:
menuentry "SSD Arch Linux" {
icon /EFI/refind/icons/os_arch.png
volume "ArchSSD"
loader /boot/vmlinuz-linux
initrd /boot/initramfs-linux.img
options "root=/dev/sdb1 ro"
I hope this helps.
blkid
/dev/sda1: LABEL="WINRE_DRV" UUID="7C2ADD1D2ADCD4EC" TYPE="ntfs" PARTUUID="b7137819-2ca6-40fb-9167-b73ac37d8d96"
/dev/sda2: LABEL="SYSTEM_DRV" UUID="D2DF-9F74" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="9c77b526-730f-42f9-9904-f9a31b205687"
/dev/sda3: PARTLABEL="Microsoft reserved partition" PARTUUID="f4d5275b-24c1-4847-b937-345bc23bec89"
/dev/sda4: LABEL="Windows 8" UUID="38D6E449D6E408C8" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="d777a359-f42c-4629-a07c-cc55316352fe"
/dev/sda5: UUID="c1822e3c-e037-4445-bdd8-b71778237dee" TYPE="ext4" PARTUUID="3d282004-2515-4630-b82e-35ed7f707b89"
/dev/sda6: UUID="F80680CC06808D76" TYPE="ntfs" PARTUUID="575bc623-c7f1-44da-a79e-220ce3c98d9b"
/dev/sda7: LABEL="Lenovo_Recovery" UUID="0898D76B98D75632" TYPE="ntfs" PARTUUID="99bfc6d6-1b71-46d1-887e-2f7e65e3eab1"
/dev/sdb1: LABEL="ArchSSD" UUID="c61a1301-4728-465d-b40b-bde5e084eb50" TYPE="ext4" PARTUUID="e87704a5-01"
lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
sda
├─sda1 ntfs WINRE_DRV 7C2ADD1D2ADCD4EC
├─sda2 vfat SYSTEM_DRV D2DF-9F74 /boot
├─sda3
├─sda4 ntfs Windows 8 38D6E449D6E408C8
├─sda5 ext4 c1822e3c-e037-4445-bdd8-b71778237dee /
├─sda6 ntfs F80680CC06808D76
└─sda7 ntfs Lenovo_Recovery 0898D76B98D75632
sdb
└─sdb1 ext4 ArchSSD c61a1301-4728-465d-b40b-bde5e084eb50
sr0
boot tree
/boot
├── BOOT
│   └── boot.sdi
├── BOOTSECT.BAK
├── EFI
│   ├── Boot
│   │   ├── bootx64.efi
│   │   ├── LenovoBT.EFI
│   │   ├── License.txt
│   │   └── ReadMe.txt
│   ├── gummiboot
│   │   └── gummibootx64.efi
│   ├── Lenovo
│   │   └── Boot
│   │   ├── BCD
│   │   ├── BCD.LOG
│   │   ├── BCD.LOG1
│   │   ├── BCD.LOG2
│   │   ├── bg-BG
│   │   │   ├── bootmgfw.efi.mui
│   │   │   └── bootmgr.efi.mui
│   │   ├── bootmgfw.efi
│   │   ├── bootmgr.efi
│   │   ├── BOOTSTAT.DAT
│   │   ├── boot.stl
│   │   ├── cs-CZ
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── da-DK
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── de-DE
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── el-GR
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── en-GB
│   │   │   ├── bootmgfw.efi.mui
│   │   │   └── bootmgr.efi.mui
│   │   ├── en-US
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── es-ES
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── et-EE
│   │   │   ├── bootmgfw.efi.mui
│   │   │   └── bootmgr.efi.mui
│   │   ├── fi-FI
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── Fonts
│   │   │   ├── chs_boot.ttf
│   │   │   ├── cht_boot.ttf
│   │   │   ├── jpn_boot.ttf
│   │   │   ├── kor_boot.ttf
│   │   │   ├── malgun_boot.ttf
│   │   │   ├── malgunn_boot.ttf
│   │   │   ├── meiryo_boot.ttf
│   │   │   ├── meiryon_boot.ttf
│   │   │   ├── msjh_boot.ttf
│   │   │   ├── msjhn_boot.ttf
│   │   │   ├── msyh_boot.ttf
│   │   │   ├── msyhn_boot.ttf
│   │   │   ├── segmono_boot.ttf
│   │   │   ├── segoen_slboot.ttf
│   │   │   ├── segoe_slboot.ttf
│   │   │   └── wgl4_boot.ttf
│   │   ├── fr-FR
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── hr-HR
│   │   │   ├── bootmgfw.efi.mui
│   │   │   └── bootmgr.efi.mui
│   │   ├── hu-HU
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── it-IT
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── ja-JP
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── ko-KR
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── lt-LT
│   │   │   ├── bootmgfw.efi.mui
│   │   │   └── bootmgr.efi.mui
│   │   ├── lv-LV
│   │   │   ├── bootmgfw.efi.mui
│   │   │   └── bootmgr.efi.mui
│   │   ├── memtest.efi
│   │   ├── nb-NO
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── nl-NL
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── pl-PL
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── pt-BR
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── pt-PT
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── qps-ploc
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── Resources
│   │   │   ├── bootres.dll
│   │   │   └── en-US
│   │   │   └── bootres.dll.mui
│   │   ├── ro-RO
│   │   │   ├── bootmgfw.efi.mui
│   │   │   └── bootmgr.efi.mui
│   │   ├── ru-RU
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── sk-SK
│   │   │   ├── bootmgfw.efi.mui
│   │   │   └── bootmgr.efi.mui
│   │   ├── sl-SI
│   │   │   ├── bootmgfw.efi.mui
│   │   │   └── bootmgr.efi.mui
│   │   ├── sr-Latn-CS
│   │   │   ├── bootmgfw.efi.mui
│   │   │   └── bootmgr.efi.mui
│   │   ├── sv-SE
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── tr-TR
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── uk-UA
│   │   │   ├── bootmgfw.efi.mui
│   │   │   └── bootmgr.efi.mui
│   │   ├── zh-CN
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── zh-HK
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   └── zh-TW
│   │   ├── bootmgfw.efi.mui
│   │   ├── bootmgr.efi.mui
│   │   └── memtest.efi.mui
│   ├── Microsoft
│   │   └── Boot
│   │   ├── BCD
│   │   ├── BCD.LOG
│   │   ├── BCD.LOG1
│   │   ├── BCD.LOG2
│   │   ├── bg-BG
│   │   │   ├── bootmgfw.efi.mui
│   │   │   └── bootmgr.efi.mui
│   │   ├── bootmgfw.efi
│   │   ├── bootmgr.efi
│   │   ├── BOOTSTAT.DAT
│   │   ├── boot.stl
│   │   ├── cs-CZ
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── da-DK
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── de-DE
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── el-GR
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── en-GB
│   │   │   ├── bootmgfw.efi.mui
│   │   │   └── bootmgr.efi.mui
│   │   ├── en-US
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── es-ES
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── et-EE
│   │   │   ├── bootmgfw.efi.mui
│   │   │   └── bootmgr.efi.mui
│   │   ├── fi-FI
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── Fonts
│   │   │   ├── chs_boot.ttf
│   │   │   ├── cht_boot.ttf
│   │   │   ├── jpn_boot.ttf
│   │   │   ├── kor_boot.ttf
│   │   │   ├── malgun_boot.ttf
│   │   │   ├── malgunn_boot.ttf
│   │   │   ├── meiryo_boot.ttf
│   │   │   ├── meiryon_boot.ttf
│   │   │   ├── msjh_boot.ttf
│   │   │   ├── msjhn_boot.ttf
│   │   │   ├── msyh_boot.ttf
│   │   │   ├── msyhn_boot.ttf
│   │   │   ├── segmono_boot.ttf
│   │   │   ├── segoen_slboot.ttf
│   │   │   ├── segoe_slboot.ttf
│   │   │   └── wgl4_boot.ttf
│   │   ├── fr-FR
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── hr-HR
│   │   │   ├── bootmgfw.efi.mui
│   │   │   └── bootmgr.efi.mui
│   │   ├── hu-HU
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── it-IT
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── ja-JP
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── ko-KR
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── lt-LT
│   │   │   ├── bootmgfw.efi.mui
│   │   │   └── bootmgr.efi.mui
│   │   ├── lv-LV
│   │   │   ├── bootmgfw.efi.mui
│   │   │   └── bootmgr.efi.mui
│   │   ├── memtest.efi
│   │   ├── nb-NO
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── nl-NL
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── pl-PL
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── pt-BR
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── pt-PT
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── qps-ploc
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── Resources
│   │   │   ├── bootres.dll
│   │   │   ├── en-US
│   │   │   │   └── bootres.dll.mui
│   │   │   └── nl-NL
│   │   │   └── bootres.dll.mui
│   │   ├── ro-RO
│   │   │   ├── bootmgfw.efi.mui
│   │   │   └── bootmgr.efi.mui
│   │   ├── ru-RU
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── sk-SK
│   │   │   ├── bootmgfw.efi.mui
│   │   │   └── bootmgr.efi.mui
│   │   ├── sl-SI
│   │   │   ├── bootmgfw.efi.mui
│   │   │   └── bootmgr.efi.mui
│   │   ├── sr-Latn-CS
│   │   │   ├── bootmgfw.efi.mui
│   │   │   └── bootmgr.efi.mui
│   │   ├── sr-Latn-RS
│   │   │   ├── bootmgfw.efi.mui
│   │   │   └── bootmgr.efi.mui
│   │   ├── sv-SE
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── tr-TR
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── uk-UA
│   │   │   ├── bootmgfw.efi.mui
│   │   │   └── bootmgr.efi.mui
│   │   ├── zh-CN
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   ├── zh-HK
│   │   │   ├── bootmgfw.efi.mui
│   │   │   ├── bootmgr.efi.mui
│   │   │   └── memtest.efi.mui
│   │   └── zh-TW
│   │   ├── bootmgfw.efi.mui
│   │   ├── bootmgr.efi.mui
│   │   └── memtest.efi.mui
│   ├── refind
│   │   ├── icons
│   │   │   ├── arrow_left.png
│   │   │   ├── arrow_right.png
│   │   │   ├── boot_linux.png
│   │   │   ├── boot_win.png
│   │   │   ├── func_about.png
│   │   │   ├── func_exit.png
│   │   │   ├── func_firmware.png
│   │   │   ├── func_reset.png
│   │   │   ├── func_shutdown.png
│   │   │   ├── os_altlinux.png
│   │   │   ├── os_arch.png
│   │   │   ├── os_centos.png
│   │   │   ├── os_chrome.png
│   │   │   ├── os_clover.png
│   │   │   ├── os_debian.png
│   │   │   ├── os_ecomstation.png
│   │   │   ├── os_fatdog.png
│   │   │   ├── os_fedora.png
│   │   │   ├── os_freebsd.png
│   │   │   ├── os_freedos.png
│   │   │   ├── os_funtoo.png
│   │   │   ├── os_gentoo.png
│   │   │   ├── os_gummiboot.png
│   │   │   ├── os_haiku.png
│   │   │   ├── os_hwtest.png
│   │   │   ├── os_kubuntu.png
│   │   │   ├── os_legacy.png
│   │   │   ├── os_linuxmint.png
│   │   │   ├── os_linux.png
│   │   │   ├── os_lubuntu.png
│   │   │   ├── os_mac.png
│   │   │   ├── os_mageia.png
│   │   │   ├── os_mandriva.png
│   │   │   ├── os_manjaro.png
│   │   │   ├── os_mythbuntu.png
│   │   │   ├── os_netbsd.png
│   │   │   ├── os_openbsd.png
│   │   │   ├── os_opensuse.png
│   │   │   ├── os_redhat.png
│   │   │   ├── os_refind.png
│   │   │   ├── os_refit.png
│   │   │   ├── os_slackware.png
│   │   │   ├── os_suse.png
│   │   │   ├── os_ubuntu.png
│   │   │   ├── os_unknown.png
│   │   │   ├── os_win.png
│   │   │   ├── tool_apple_rescue.png
│   │   │   ├── tool_memtest.png
│   │   │   ├── tool_mok_tool.png
│   │   │   ├── tool_part.png
│   │   │   ├── tool_shell.png
│   │   │   ├── tool_windows_rescue.png
│   │   │   ├── transparent.png
│   │   │   ├── vol_external.png
│   │   │   ├── vol_internal.png
│   │   │   └── vol_optical.png
│   │   ├── icons-backup
│   │   │   ├── arrow_left.png
│   │   │   ├── arrow_right.png
│   │   │   ├── boot_linux.png
│   │   │   ├── boot_win.png
│   │   │   ├── func_about.png
│   │   │   ├── func_exit.png
│   │   │   ├── func_firmware.png
│   │   │   ├── func_reset.png
│   │   │   ├── func_shutdown.png
│   │   │   ├── os_altlinux.png
│   │   │   ├── os_arch.png
│   │   │   ├── os_centos.png
│   │   │   ├── os_chrome.png
│   │   │   ├── os_clover.png
│   │   │   ├── os_debian.png
│   │   │   ├── os_ecomstation.png
│   │   │   ├── os_fatdog.png
│   │   │   ├── os_fedora.png
│   │   │   ├── os_freebsd.png
│   │   │   ├── os_freedos.png
│   │   │   ├── os_funtoo.png
│   │   │   ├── os_gentoo.png
│   │   │   ├── os_gummiboot.png
│   │   │   ├── os_haiku.png
│   │   │   ├── os_hwtest.png
│   │   │   ├── os_kubuntu.png
│   │   │   ├── os_legacy.png
│   │   │   ├── os_linuxmint.png
│   │   │   ├── os_linux.png
│   │   │   ├── os_lubuntu.png
│   │   │   ├── os_mac.png
│   │   │   ├── os_mageia.png
│   │   │   ├── os_mandriva.png
│   │   │   ├── os_manjaro.png
│   │   │   ├── os_mythbuntu.png
│   │   │   ├── os_netbsd.png
│   │   │   ├── os_openbsd.png
│   │   │   ├── os_opensuse.png
│   │   │   ├── os_redhat.png
│   │   │   ├── os_refind.png
│   │   │   ├── os_refit.png
│   │   │   ├── os_slackware.png
│   │   │   ├── os_suse.png
│   │   │   ├── os_ubuntu.png
│   │   │   ├── os_unknown.png
│   │   │   ├── os_win.png
│   │   │   ├── tool_apple_rescue.png
│   │   │   ├── tool_memtest.png
│   │   │   ├── tool_mok_tool.png
│   │   │   ├── tool_part.png
│   │   │   ├── tool_shell.png
│   │   │   ├── tool_windows_rescue.png
│   │   │   ├── transparent.png
│   │   │   ├── vol_external.png
│   │   │   ├── vol_internal.png
│   │   │   └── vol_optical.png
│   │   ├── keys
│   │   │   ├── altlinux.cer
│   │   │   ├── canonical-uefi-ca.der
│   │   │   ├── fedora-ca.cer
│   │   │   ├── openSUSE-UEFI-CA-Certificate.cer
│   │   │   ├── refind.cer
│   │   │   └── SLES-UEFI-CA-Certificate.cer
│   │   ├── refind.conf
│   │   ├── refind.conf.old
│   │   ├── refind.conf-sample
│   │   └── refind_x64.efi
│   └── tools
├── grub
│   ├── grub.cfg
│   └── grub.cfg.example
├── initramfs-linux-fallback.img
├── initramfs-linux.img
├── loader
│   ├── entries
│   │   └── arch.conf
│   └── loader.conf
├── refind_linux.conf
└── vmlinuz-linux
refind_linux.conf
"Boot with standard options" "ro root=UUID=c1822e3c-e037-4445-bdd8-b71778237dee quiet "
"Boot to single-user mode" "ro root=UUID=c1822e3c-e037-4445-bdd8-b71778237dee quiet single"
"Boot with minimal options" "ro root=UUID=c1822e3c-e037-4445-bdd8-b71778237dee"

[SOLVED] Grub Problems Can boot Arch w/ grub edits only

I had 3 Linux OS's installed on this computer, Arch and 2 versions of Ubuntu on one hard drive.
The MBR belonged to Ubuntu, using grub2. I decided to get rid of the older Ubuntu (sda8 and 9) and add it's HDD space to my Arch home (sda12). Used the current Gparted live to modify the partitions and all went well, but of course, the numbers changed getting rid of 2 partitions.
No boot upon restart so I decided to get Arch's grub back to the MBR with the new partition numbering scheme.
Using a live CD, I used the grub shell, find /boot/grub/stage1.....etc, etc. and after a bit of fumbling, grub indicated success in the shell. When I was through though, a reboot was not successful, although the current stable grub was now written to the MBR. I edited the lines using grub edit option, and got Arch to boot, and figured out the correct partition numbers. Next I edited the menu.lst to reflect the new sda numbers.
Now rebooting results in a long delay when grub should be on the screen, and the numbers on the Arch entries reflect the old numbers still!! I double checked thinking I forgot to save the edits to the menu.lst file, but they are correct. I can boot Arch, but have to edit the lines each time.
The current partitions are as follows. I edited the terminal output to show details.
[jeff@Arch2009p2 ~]$ sudo fdisk -l
Password:
Disk /dev/sda: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000383e7
Device Boot Start End Blocks Id System
/dev/sda1 * 1 91201 732572001 5 Extended
/dev/sda5 1 255 2048224+ 82 Linux swap / Solaris
/dev/sda6 (ubuntu /) 256 1471 9767488+ 83 Linux
/dev/sda7 (ubuntu /home) 1472 22321 167477593+ 83 Linux
/dev/sda8 (arch boot) 22322 22325 32098+ 83 Linux
/dev/sda9 (arch /) 22326 23627 10458283+ 83 Linux
/dev/sda10 (arch /home) 23628 91201 542788123+ 83 Linux
I have a few questions regarding a separate boot partition for Arch.
Should the grub> root (hd0.0) command be directed to the root or boot partition.
My handy printed emergency guide says: Set grubs root device to the partition containing the boot directory.
OK.....Writing it out now, it seems clear, so I'll try reinstalling grub from a live CD.
Why does grub have incorrect partition numbers even though the menu.lst is correct?
There are only 2 OS's on this box now, and one contains grub2.
Is current grub able to interact with grub 2 if I screwed something up on the install?
Last edited by jeff story (2010-05-24 20:05:06)

OK
I managed to fix the problem of grub not reading/using the menu.lst file. Not sure WTF it was reading and where that file was located!
The problem seems to have been the most insignificant detail.
When using the grub terminal, I did not execute the quit command when I was through. I just closed the terminal and rebooted.
After repeating the following code via live CD a few times:
$ sudo grub
grub> find /grub/stage1
grub> root (hd0,7)
grub> setup (hd0)
Grub still didn't read the current menu.lst.
This morning I got things to work correctly and grub to read the current menu.lst by adding a quit command and returning to the linux shell prior to rebooting.
I used the following commands:
$ sudo grub
grub> find /grub/stage1
grub> root (hd0,7)
grub> setup (hd0)
grub> quit

[SOLVED] Grub entry for Arch console-mode

Similar Messages

Maybe you are looking for