[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

Similar Messages

  • [SOLVED] Suddenly booting in emergency mode, why?

    Hi,
    i already searched here and with google and I could find problems regarding the emergency mode but none fitting to mine
    I really dont know what I shall do now.
    I just rebooted because my wifi was connected but i had no internet connection although it was there on other devices. after reboot it showed emergency mode like in the pictures below.
    plus i posted the error parts of the journal output.
    can someone help me with that?
    thank you very much
    Last edited by christian1337 (2015-04-28 18:20:31)

    christian1337 wrote:
    that actually helped, thank you very much
    But how can I prevent this? I guess it was because my notebook booted into windows and because II didn't want it to boot I just restarted while booting. not the gentle way but usually I had no problems with that. I mean I won't do that again now but can I maybe fix something in my fstab?
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    tmpfs /tmp tmpfs nodev,nosuid 0 0
    # /dev/sdb8 UUID=3699c7ac-8e3e-42c6-b215-19965446990e
    LABEL=arch / ext4 rw,relatime,data=ordered 0 2
    # /dev/sdb7 UUID=570f4617-353e-4631-9825-2bc569f35af0
    LABEL=swap none swap defaults 0 0
    LABEL=stuff /media/stuff ntfs defaults,rw 0 2
    why is there a swap at all? When I installed arch I especially tried doing it without a swap drive because I have 16gb of ram, so I thought I don't need that?
    but to be safe I should exchange all the labels with UUIDs right?
    afterwards I will mark this thread as solved.
    UUID's are generally safer because they won't change over time. I got mixed up with labels referring to "/dev/sdb8" or "arch", so your current definitions should be fine as long as you don't introduce a new drive labelled arch.
    To get rid of mounting the swap partition, (This WILL disable hibernation) you can just prefix the swap line with a hash so it isn't parsed.
    To allow skipping of the Windows partition if it's in HybridBoot, add "nofail" to the options region. E.G: LABEL=stuff /media/stuff ntfs defaults,rw,nofail 0 0
    Last thing (Hopefully), the pass field, (the digit 2 in the "stuff" line) should be a zero, as fsck cannot scan NTFS as far as I know.

  • [Solved]Grub booting the wrong partition

    Hello everyone and thank you for reading!
    This is my first post on this forum (and my first step into arch) so appologies for any newbie symtoms (and bad language).
    My problem:
    When I start my laptop (press the power button) my system go's into bios and then boots my HDD (that statement is a bit off I know). After that the system stops and grub rescue starts, saying something about a UUID not found (the UUID is nowhere to be found in my system but it could be one from my previous Ubuntu setup).
    My system:
    An Acer Laptop with a Samsung SSD for OS(sda) and Seagate HDD for storage(sdb)
    a 3d gen i5
    glorious Nvidia optimus
    some more stuff I think is not importend
    My attempted solutions:
    >Switch the boot-order and put my SSD on top.
       My bios only lets me say "Boot from a disk (hdd and ssd)", "Boot from CD", "Network" ,etc.
    >Boot-repair
       Didn't work.
    >try setting this right in grub-rescue
       Could work, but I get an error all the time saying "could not find "grub_real_boot_time"" when running "insmod normal".
    >wipe the entire HDD clean.
       even with all the HDD partitions deleted, grub still pops up from out of nowhere.
    >remove the HDD
       Yes this works the system boots in a blink of an eye.
    Last edited by Lacsapix (2014-07-17 10:17:57)

    thank you karol!
    a simple
    sudo dd if=/dev/zero of=/dev/sdb bs=446 count=1
    did the trick!

  • Network Boot (Rescue Mode)

    I need to rescue a OL5 VM guest the other day and discovered you can Network boot into rescue mode by using the following arguments in the boot string.
    --args rescue http://server/pathtodistribution
    Just thought I would share. You could always just mount the virtual disk on another host but to me... this is simpler and faster.

    I've added extended logging to the console, so there are a few more things to show the errors:
    [ OK ] Mounted /boot.
    [ OK ] Reached target Local File Systems.
    Starting Recreate Volatile Files and Directories...
    Starting Trigger Flushing of Journal to Persistent Storage...
    [ OK ] Started Recreate Volatile Files and Directories.
    Starting Update UTMP about System Reboot/Shutdown...
    [ OK ] Started Update UTMP about System Reboot/Shutdown.
    [ OK ] Started Trigger Flushing of Journal to Persistent Storage.
    [ OK ] Reached target System Initialization.
    Starting Rescue Shell...
    [ OK ] Started Rescue Shell.
    [ OK ] Reached target Rescue Mode.
    [ 2.915824] systemd[255]: Failed at step CHDIR spawning /bin/plymouth: No such file or directory
    [ 2.934292] systemd[257]: Failed at step CHDIR spawning /bin/echo: No such file or directory
    [ 2.952007] systemd[260]: Failed at step CHDIR spawning /sbin/sulogin: No such file or directory
    [ 2.970414] systemd[263]: Failed at step CHDIR spawning /usr/bin/systemctl: No such file or directory
    Remember, this is a fresh installation. Only the base base-devel and vim packages are installed.
    Any ideas?

  • First MBP Grey Screen/Boot Problems/Only boots in Safe Mode

    Hi everyone,
    I've spent the last few days researching previous troubleshoots and threads on the subject, but haven't had much luck unfortunately.
    This is a 2011 MBP, 2.2 GHz, 4 gb RAM, 15 inch. As a preface, I use(d) an external monitor via my MBP's mini-display port, and at some points, the monitor (both) would become distorted, vertical lines running down, and then both would freeze, so I immediately thought my GPU was going. Then after a few restarts after the problem occurred a few times, I got the infamous boot issue: the grey screen (after viewing the spinning logo), so to the forums and research it was.
    Now, my MBP will boot in safe mode with no issues. Getting it to boot off of a disc with the "C" option works about 50/50, but I usually end up being able to get to it.
    This is what I've attempted thus far from everything I've read:
    Repaired Disk: repaired
    Repaired Permissions: repaired (both of which I did in safe-mode AND from disc-booting, if that helps)
    Reset SMC
    Reset PRAM
    Reinstalled factory RAM (2 x 2 gbs) ((I had a 2 gb stick and an 8 gb stick) Status of RAM via Profiler: OK
    Removed peripheral devices to give that a shot with no luck
    Reinstalled OS X (Snow Leopard, by the way, from disc)
    Performed both abridged AND extended Apple Hardware Test: No problems found (which is what took me away from Logic Board or GPU issues..)
    Used Time Machine backups to restore from previous working date (I regularly backed up my MBP) and have two seperate external drives with backups, though no clones.
    Reformatted my entire 750 gb HD, last night, reinstalled the OS X, did not try and restore from Time Machine (as I know I could do that at a later date) and following completion of the OS X install and upon the "restart" requested of me, my MBP had a dark blue freeze, so I cold booted to the same problem of the grey screen, which is where I'm at now.
    Summary:
    Can Safe Boot with no issues. Reformatted drive. Reinstalled OS X (10.6.7, software update to 10.6.8). Operating with original RAM, went through trouble shoot procedures.
    From what I've read, a lot of people have said to replace the MBP Hard Drive cable (SATA) cable, which I have ordered per my model, so I'm waiting on that.
    Is there anything else I can do, or try in the meantime? I'd like to know peoples' thoughts on if my HD has failed (thought DU says it's fine) and the fact I can boot in safe mode, and whether a hard drive cable replacement is a probable fix.
    This MBP was purchased NEW in June of 2011 and has been well maintained.
    Thanks for any thoughts, suggestions, critiques,...anything.

    Hi everyone,
    I've spent the last few days researching previous troubleshoots and threads on the subject, but haven't had much luck unfortunately.
    This is a 2011 MBP, 2.2 GHz, 4 gb RAM, 15 inch. As a preface, I use(d) an external monitor via my MBP's mini-display port, and at some points, the monitor (both) would become distorted, vertical lines running down, and then both would freeze, so I immediately thought my GPU was going. Then after a few restarts after the problem occurred a few times, I got the infamous boot issue: the grey screen (after viewing the spinning logo), so to the forums and research it was.
    Now, my MBP will boot in safe mode with no issues. Getting it to boot off of a disc with the "C" option works about 50/50, but I usually end up being able to get to it.
    This is what I've attempted thus far from everything I've read:
    Repaired Disk: repaired
    Repaired Permissions: repaired (both of which I did in safe-mode AND from disc-booting, if that helps)
    Reset SMC
    Reset PRAM
    Reinstalled factory RAM (2 x 2 gbs) ((I had a 2 gb stick and an 8 gb stick) Status of RAM via Profiler: OK
    Removed peripheral devices to give that a shot with no luck
    Reinstalled OS X (Snow Leopard, by the way, from disc)
    Performed both abridged AND extended Apple Hardware Test: No problems found (which is what took me away from Logic Board or GPU issues..)
    Used Time Machine backups to restore from previous working date (I regularly backed up my MBP) and have two seperate external drives with backups, though no clones.
    Reformatted my entire 750 gb HD, last night, reinstalled the OS X, did not try and restore from Time Machine (as I know I could do that at a later date) and following completion of the OS X install and upon the "restart" requested of me, my MBP had a dark blue freeze, so I cold booted to the same problem of the grey screen, which is where I'm at now.
    Summary:
    Can Safe Boot with no issues. Reformatted drive. Reinstalled OS X (10.6.7, software update to 10.6.8). Operating with original RAM, went through trouble shoot procedures.
    From what I've read, a lot of people have said to replace the MBP Hard Drive cable (SATA) cable, which I have ordered per my model, so I'm waiting on that.
    Is there anything else I can do, or try in the meantime? I'd like to know peoples' thoughts on if my HD has failed (thought DU says it's fine) and the fact I can boot in safe mode, and whether a hard drive cable replacement is a probable fix.
    This MBP was purchased NEW in June of 2011 and has been well maintained.
    Thanks for any thoughts, suggestions, critiques,...anything.

  • Fresh btrfs root partition cannot boot/unknown filesystem [solved]

    Just reformatted my SSD with 3 partitions.
    1) EFI
    2) /boot (ext4)
    3) / (btrfs)
    I copied over my systefrom tars, adjusted the new fstab to use btrfs, I rebuilt my kernel images, and rebuilt grub.cfg in the chroot.  When I reboot, I get:
    Welcome to grub!
    error: unknown filesystem
    Entering rescue mode...
    grub rescue>
    Per the wiki, there should be no special setup steps to boot to a btrfs root with grub.  When did I f-up?
    /etc/fstab
    LABEL=arch64 / btrfs defaults,discard,noatime,ssd,compress=lzo 0 0
    LABEL=boot /boot ext4 defaults,discard,noatime 0 2
    Excuse the short post, typing in a phone.
    Last edited by graysky (2013-07-29 01:24:47)

    Yes, it is dropped to a GRUB rescue shell.  I can boot if I manually type the following but WTF?!  Why isn't grub doing this by itself?
    grub rescue> set prefix=(hd0,2)/grub
    grub rescue> insmod (hd0,2)/grub/x86_64-efi/linux.mod
    grub rescue> set root=(hd0,2)
    grub rescue> linux /vmlinuz-linux-ck root=/dev/sda3
    grub rescue> initrd /initramfs-linux-ck.img
    grub rescue> boot
    Link to my autogenerated /boot/grub/grub.cfg
    Last edited by graysky (2013-07-29 00:28:58)

  • [SOLVED] grub "unknown filesystem" error for big partition layout

    Last night / this morning I copied the root and swap partitions of an Arch Linux installation (stushiba) I had on an old Toshiba hard drive, as well as the "system reserved" and other partitions of a Windows 8 install (stuzate) on another 500GB hard drive, onto a new 2TB Western Digital hard drive using Gparted via an external Arch environment I run off of a microSD card + adapter (sturling).
    After doing so, I installed GRUB to the new drive to the best of my ability, but when I try to boot the system with just that drive, this is what I see:
    GRUB loading.
    Welcome to GRUB!
    error: unknown filesystem.
    Entering rescue mode...
    grub rescue>
    Running ls doesn't find anything:
    grub rescue> ls
    (hd0) (hd0,msdos4) (hd0,msdos3) (hd0,msdos2) (hd0,msdos1)
    grub rescue> ls (hd0,msdos4)
    (hd0,msdos4): Filesystem is unknown.
    grub rescue> ls (hd0,msdos3)
    (hd0,msdos3): Filesystem is unknown.
    grub rescue> ls (hd0,msdos2)
    (hd0,msdos2): Filesystem is unknown.
    grub rescue> ls (hd0,msdos1)
    (hd0,msdos1): Filesystem is unknown.
    The system should be on (hd0,msdos3) - it's ext4, and, if I insert the old Toshiba hard disk to the system and select that as my boot device in BIOS, it boots from the partition on the old drive's grub menu, into the partition in the new drive (because they have the same UUID), so the partition's definitely readable/bootable. (I've tried both regenerating the grub menu and installing grub from this boot scenario, with no change.)
    (That said, if I enter a console on my system with a working GRUB installation and do an ls on that partition, I get more "unrecognized filesystem" messages.)
    Once the new partition had loaded, I ran
    sudo grub-mkconfig -o /boot/grub/grub.cfg
    and rebooted, but GRUB was still broken.
    I tried fixing this by rebooting into the latest installation media, with only the new hard drive plugged in, and running
    mount /dev/sda3 /mnt
    arch-chroot /mnt
    modprobe dm-mod
    grub-install --recheck /dev/sda
    But that still hasn't fixed anything: I still get the "error: unknown filesystem." message whenever I try to do anything in GRUB.
    My /boot/grub/grub.cfg: http://sprunge.us/RMeD
    Help!
    Last edited by STUART (2013-09-12 01:55:16)

    This is the output when running from sturling (neither partition booted).
    /dev/sda is the new disk, /dev/sdb is the microSD card I'm running the system off of, and /dev/sdc is the old disk.
    [stuart@sturling ~]$ sudo lsblk -f
    NAME FSTYPE LABEL UUID MOUNTPOINT
    sda
    ├─sda1 ntfs System Reserved F24C78CE4C788EDB
    ├─sda2 ntfs F68C7D338C7CF00B
    ├─sda3 ext4 stushiba 1c8533ed-4a3c-4a4c-907b-682bd2313492
    └─sda4 swap 97c30b3e-f763-437b-aa71-0378bef4c017
    sdb
    ├─sdb1 vfat savfat A13A-D130 /vfat
    └─sdb2 ext4 saroot 7434b70f-7028-4a8d-ad78-a4975a98e1a6 /
    sdc
    ├─sdc1 ext4 stushiba 1c8533ed-4a3c-4a4c-907b-682bd2313492
    └─sdc2 swap 97c30b3e-f763-437b-aa71-0378bef4c017
    sr0
    [stuart@sturling ~]$ sudo fdisk -l /dev/sda
    Disk /dev/sda: 2000.4 GB, 2000365289472 bytes, 3906963456 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
    Disk label type: dos
    Disk identifier: 0x0005f107
    Device Boot Start End Blocks Id System
    /dev/sda1 2048 718847 358400 7 HPFS/NTFS/exFAT
    /dev/sda2 718848 1937063935 968172544 7 HPFS/NTFS/exFAT
    /dev/sda3 1937063936 3873409023 968172544 83 Linux
    /dev/sda4 3873409024 3906963455 16777216 82 Linux swap / Solaris
    [stuart@sturling ~]$ sudo fdisk -l /dev/sdb
    Disk /dev/sdb: 31.9 GB, 31914983424 bytes, 62333952 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
    Disk label type: dos
    Disk identifier: 0x000c314b
    Device Boot Start End Blocks Id System
    /dev/sdb1 2048 8390655 4194304 c W95 FAT32 (LBA)
    /dev/sdb2 * 8390656 62333951 26971648 83 Linux
    [stuart@sturling ~]$ sudo fdisk -l /dev/sdc
    Disk /dev/sdc: 100.0 GB, 100030242816 bytes, 195371568 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
    Disk label type: dos
    Disk identifier: 0x8bef8bef
    Device Boot Start End Blocks Id System
    /dev/sdc1 2048 178593791 89295872 83 Linux
    /dev/sdc2 178593792 195371007 8388608 82 Linux swap / Solaris

  • Grub starts, but drops to rescue mode: 'grub_term_highlight_color'

    Howdy, all;
    An upgrade involving grub seemed to go well, and it included an update to grub.  Ran grub-mkconfig, and rebooted.
    Grub starts to load with "Welcome to Grub" before the menu loads, and then drops to rescue mode with the error:
    "error: symbol 'grub_term_highlight_color' not found."
    The only [solved] issue I can find is by user cfr, and the 'solution' isn't helpful:  cfr writes "This is sorted though I still don't know what on Earth I did".  Can't seem to find a solution in the Gentoo guides or even the Fedora forums.
    If someone could point me to the right direction so I can solve this thing, I'd be grateful.
    Thanks in advance!
    [edited to add]:  insmod linux.mod and normal.mod both kick back the same 'highlight color' error.
    Last edited by fionn (2013-10-12 16:34:16)

    fionn wrote:
    Howdy, all;
    An upgrade involving grub seemed to go well, and it included an update to grub.  Ran grub-mkconfig, and rebooted.
    Grub starts to load with "Welcome to Grub" before the menu loads, and then drops to rescue mode with the error:
    "error: symbol 'grub_term_highlight_color' not found."
    The only [solved] issue I can find is by user cfr, and the 'solution' isn't helpful:  cfr writes "This is sorted though I still don't know what on Earth I did".  Can't seem to find a solution in the Gentoo guides or even the Fedora forums.
    If someone could point me to the right direction so I can solve this thing, I'd be grateful.
    Thanks in advance!
    [edited to add]:  insmod linux.mod and normal.mod both kick back the same 'highlight color' error.
    Did you update files in /boot/grub via grub-install? The changes i grub-mkconfig depend on updated files in /boot/grub.

  • Boot stopped at "Rescue mode"

    Hey guys,
    I've been using archlinux for a while now (laptop & homeserver). Though I got a dedicated root server (@strato) for a few reasons, I thought I'd give it a try there, too.
    Yet I have to deal with a little problem, though. Installation via the 'squashfs-method' using the RecoverySystem went smoothly. But when I try to boot the maschine, it doesn't start up properly.
    Below's the output of the serial console after grub. I can't see the rescue shell itself, though. Dunno if that's due to the serial attachment.
    Welcome to Arch Linux!
    [ OK ] Set up automount Arbitrary Executable File Formats F...utomount Point.
    [ OK ] Listening on Journal Socket.
    Starting Apply Kernel Variables...
    Starting Journal Service...
    [ OK ] Started Journal Service.
    Mounting Debug File System...
    Starting Setup Virtual Console...
    Mounting Huge Pages File System...
    Starting Create static device nodes in /dev...
    Mounting POSIX Message Queue File System...
    [ OK ] Reached target Encrypted Volumes.
    Mounting Configuration File System...
    [ OK ] Listening on udev Kernel Socket.
    [ OK ] Listening on udev Control Socket.
    Starting udev Coldplug all Devices...
    [ OK ] Reached target Swap.
    Mounting Temporary Directory...
    Starting Remount Root and Kernel File Systems...
    Expecting device dev-sda1.device...
    [ OK ] Started Apply Kernel Variables.
    [ OK ] Mounted Debug File System.
    [ OK ] Started Setup Virtual Console.
    [ OK ] Mounted Huge Pages File System.
    [ OK ] Started Create static device nodes in /dev.
    [ OK ] Mounted POSIX Message Queue File System.
    [ OK ] Mounted Configuration File System.
    [ OK ] Mounted Temporary Directory.
    [ OK ] Started Remount Root and Kernel File Systems.
    [ OK ] Started udev Coldplug all Devices.
    Starting Load Random Seed...
    Starting udev Kernel Device Manager...
    [FAILED] Failed to start Load Random Seed.
    See 'systemctl status systemd-random-seed-load.service' for details.
    [ 2.685427] systemd[1]: Failed to start Load Random Seed.
    [ OK ] Started udev Kernel Device Manager.
    [ OK ] Reached target Local File Systems (Pre).
    [ OK ] Found device M4-CT128M4SSD2.
    Mounting /boot...
    [ OK ] Mounted /boot.
    [ OK ] Reached target Local File Systems.
    Starting Recreate Volatile Files and Directories...
    Starting Trigger Flushing of Journal to Persistent Storage...
    [ OK ] Started Recreate Volatile Files and Directories.
    Starting Update UTMP about System Reboot/Shutdown...
    [ OK ] Started Update UTMP about System Reboot/Shutdown.
    [ OK ] Started Trigger Flushing of Journal to Persistent Storage.
    [ OK ] Reached target System Initialization.
    Starting Rescue Shell...
    [ OK ] Started Rescue Shell.
    [ OK ] Reached target Rescue Mode.
    The output states to look at the journal, but when I chroot into arch or try to look at the journal by hand, all journals are empty.
    Any ideas what could be wrong? What files shall I provide for better help?
    I've looked up some threads in the forum, but none of the ones I found were helping with my issue.
    Thanks for your help in advance!
    Cheers,
    willi hunger

    I've added extended logging to the console, so there are a few more things to show the errors:
    [ OK ] Mounted /boot.
    [ OK ] Reached target Local File Systems.
    Starting Recreate Volatile Files and Directories...
    Starting Trigger Flushing of Journal to Persistent Storage...
    [ OK ] Started Recreate Volatile Files and Directories.
    Starting Update UTMP about System Reboot/Shutdown...
    [ OK ] Started Update UTMP about System Reboot/Shutdown.
    [ OK ] Started Trigger Flushing of Journal to Persistent Storage.
    [ OK ] Reached target System Initialization.
    Starting Rescue Shell...
    [ OK ] Started Rescue Shell.
    [ OK ] Reached target Rescue Mode.
    [ 2.915824] systemd[255]: Failed at step CHDIR spawning /bin/plymouth: No such file or directory
    [ 2.934292] systemd[257]: Failed at step CHDIR spawning /bin/echo: No such file or directory
    [ 2.952007] systemd[260]: Failed at step CHDIR spawning /sbin/sulogin: No such file or directory
    [ 2.970414] systemd[263]: Failed at step CHDIR spawning /usr/bin/systemctl: No such file or directory
    Remember, this is a fresh installation. Only the base base-devel and vim packages are installed.
    Any ideas?

  • [Solved] grub in minimal mode, not using my menu.lst

    Hi everyone,
    Installed Archlinux (using chakra livecd) on a friend's laptop, but for some reason have grub only in minimal mode... I can boot using
    configfile /boot/grub/menu.lst
    but I need to retype this at each boot...
    Partition layout is :
    * sda1 : Windows Vista
    * sda2 : HP resue partition
    * sdb1 : archlinux root ("/"). /boot is on this partition
    * sdb2 : /home
    My menu.lst works as expected.
    I tried to run
    grub-install /dev/sdb
    no error appears on the output, but no effect on next reboot
    I also tried this on the grub prompt :
    root (hd1,0)
    setup (hd1)
    Same thing, no error reported, but no effect on reboot.
    Any idea ?
    Last edited by willy9 (2009-07-01 14:44:25)

    D'oh !!!
    I just realized that
    grub-install /dev/sda
    solved everything... Sorry for the noise

  • [SOLVED]Unable to boot in UEFI mode from CD

    Hello gents!
    Here's the problem:
    According to the beginner's guide I followed the instruction to test if I am in UEFI mode:
    In case you have a UEFI motherboard, the CD/USB will launch UEFI Shell and display a message that
    startup.nsh
    script will be launched. Allow the shell to launch it. Then, to check whether you have booted into UEFI mode, load the efivars kernel module (before chrooting) and then check whether there are files in
    /sys/firmware/efi/vars/
    # modprobe efivars # before chrooting
    # ls -1 /sys/firmware/efi/vars/
    Well, the thing is that when I boot the CD no UEFI Shell is launched as well as no
    startup.nsh
    When I try to load the efivars I don't receive any message, so, I assume, the module is loaded; but the, when I invoke ls the message I receive is:
    #ls: cannot access /sys/firmware/efi/vars/: No such file or directory
    To me it looks that for some reason I am unable to access the UEFI mode when starting the CD iso.
    Thank you guys for your courteous attention.
    Have a wonderful day!!!
    P.S. I've searched already in the following posts:
    https://bbs.archlinux.org/viewtopic.php … 84#p148184
    https://bbs.archlinux.org/viewtopic.php … 55#p148155
    P.S.2
    My mobo is an ASUS Maximus V Gene with i3770K on it.
    Edit:
    Ok guys! Thanks to all of you, but everything was brought about by my scarce knowledge of the mobo. Logging into the BIOS, in the boot section, you have to choose between normal DVD and UEFI DVD. When selecting the last, everything, I mean, the startup phase at least, went well.
    Enjoy everybody
    Any idea how to close/"solved" this forum tread?
    Last edited by guidone (2012-09-11 20:34:21)

    guidone wrote:Any idea how to close/"solved" this forum tread?
    README: Forum Rules
    Simply edit the original post by clicking on the 'edit' button at the lower right corner of it and prepend [SOLVED] to the title.

  • Can't boot in safe mode AND no sleeping, can those be connected? Can those be SOLVED?!

    Hello and thanks for reading this.
    My MBP with Lion is having 2 problems and I:
    -    Would like to solve them
    -    Was wondering if they are connected.
    BTW, tried vastly googling both and read quite a lot in different forums and the Internet, but couldn’t come with a solution, just succeeded to live with. (Something like marriage)…
    The first problem: if I leave my computer to go to sleep and it does for a long time, when I try to wake him up, I get either the SBD (Spinning Ball of Death), or stuck in a black screen. Need to push the power button.
    What I do is, before going to sleep/long time away of computer, either close the lid or Apple icon-> Sleep and that’s fine.
    Second problem: can’t boot into Safe Mode.
    Immediately after the startup chime I press the Shift key, after 2-3 seconds get the login window, key in my password. Instead of logging in, it goes to a screen with the Apple icon, underneath the Apple spinning gear and underneath that a loading bar.
    After quite some time the loading bar disappears, the gear goes on spinning for a LONG time, then black screen, startup chime again and login window. Then, when I key in my password, it just logs in as usual, no safe mode.
    I tried to write in Terminal “sudo nvram boot-args="-x"”, BIG mistake! It got my computer into a never ending loop of those screens. I don’t exactly remember what eventually got me out of this loop (I think I booted from a clone, then started with the Lion CD and wrote back “sudo nvram boot-args=""” in Terminal.
    I also tried reinstalling the OS, all that without any successes.
    Any ideas anyone?
    Thanks in advance for any help.
    GM

    Created.
    Exactly the same process.
    And now I realize something interesting:
    I didn't realize that lately the startup login window, instead of bringing my 3 accounts, brings only mine (in the preferences pane after I login they appear, as usual, but not in the login window).
    Now, I am constantly backing up to 2 separated external hard disks an incremental backup to a bootable clone. If I boot from one of them it does bring the 3 accounts.
    Do you think I should stop bothering about troubleshooting and just erase the hard disk,  install the Lion from scratch and that's it?

  • [SOLVED] dual booting windows 7 with btrfs on grub-bios -- core.img

    I am trying to install arch in a dual boot configuration with an existing windows 7 partition. I have everything from the beginner's guide done but the bootloader. When I run grub-install it tells me that core.img is too big.
    Some googling tells me that this is relatively common with btrfs, and it seems the only work around is to switch to gpt mode and use a grub bios partition. But the info I've seen indicates that I need to use MBR mode to dual boot windows.
    Is it safe to do this with windows? Is there another workaround? Or will I have to settle for ext4?
    Last edited by jorenko (2013-06-09 03:53:24)

    Well there's your problem, your first partition starts at sector 63.  With recent versions of windows and fdisk (and every other partitioning tool I can think of off the top of my head) things now align themselves correctly.  Also because there is now GPT, the first partition typically starts later as the GPT partition table will typically sit between the MBR and the first partition. 
    On a MBR partitioned system, grub2 will actually use the first 446 bytes like normal, but will then also use the space that is empty where GPT would sit.  This is why when you have a GPT partitioned system, it will require you to create a 1-2MB grub boot partition, as it needs somewhere else to put its bloat.  GPT actually still uses the MBR section, but simply creates one large partition covering the whole disk.  This is so that tools that are not GPT aware will not think that they have a whole free disk to use as they please.
    For comparison, here is whe I get from fdisk:
    # fdisk -l /dev/sda
    sudo fdisk -l /dev/sda
    [sudo] password for curtisshima:
    WARNING: fdisk GPT support is currently new, and therefore in an experimental phase. Use at your own discretion.
    Disk /dev/sda: 250.1 GB, 250059350016 bytes, 488397168 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
    Disk label type: gpt
    # Start End Size Type Name
    1 2048 2099199 1G EFI System EFI System
    2 2099200 252166798 119.2G Linux filesyste arch-btrfs-1
    3 252168192 488397134 112.7G Linux filesyste arch-btrfs-3
    Note that I do use GPT.  But that is not the point here. What I am trying to show is where my first partition starts.  This is also where fdisk will start partitions these days.  This is to ensure compatibility with 4k advanced format disks.
    If you are not dead set on Grub2, you could try using syslinux.  I really like it much better, though if you are booting more than one Linux, you need to either employ chainloading to various partition boot records, or have a shared /boot.  Having a windows partition doens't really matter, as you are simply chainloading to that funky reserved partition anyway. 
    The other option is to use grub-legacy, which can still be found in the AUR.  I actually liked the orginal Grub, as it provided a nice feature set, but was still configurable by hand and it actually fit into the MBR.

  • [SOLVED] Having trouble dual booting Windows: normal.mod not found

    Hello every one, I'm a Gentoo user who wants to try something different. So I thought I'd install Arch on my new laptop.
    Anyhow, this is my first proper UEFI install on real hardware. So I might be doing something stupid here, but I've searched all over the forums and the internet and can't seem to find anything similar about it. So please excuse me if there is already a similar or very similar topic
    Since I'm new to Arch I followed the Beginner's guide. Everything went fine, install was very quick compared to Gentoo phew... anyhow there came the tricky part, the bootloader install, as I am a real total noob with EFI. I followed the instructions carefully.
    The result is: I now have 4 entries in my GRUB menu, 2 are Arch and its fallback, one is Windows 8 detected by osprober, and one is my custom Windows 8 with the usual chain loading setup that i've always used (with some fixes found on the 'net). Arch boots fine, but Windows doesn't; I get booted down to the recovery console, with an error that GRUB cannot find /boot/grub/x86_64-efi/normal.mod. Even though the file is of course existing. I tried to "insmod part_gpt" and others, and it couldn't find any of them, except part_msdos. Yeah I know, it's weird. Unfortunately I need to use Windows sometimes for some programs like Guitar Rig which need a good native audio connection.
    My opinion is that there must be some place where the paths are not correct. But I keep looking at the config files and I can't find anything wrong with them...
    The system had a Linux Mint 14 install on it previously but it bricked itself while updating to Mint 15. And I only really had Mint on there because of the automatic bootloader setup. Which worked well up to when I got rid of Mint (it was on /dev/sda8, where Arch is now). I hope it doesn't complicate the matter.
    My EFI system partition is /dev/sda2. There are so many partitions because it's a Samsung laptop and there's a partition for samsung recovery, one for windows 8 recovery, and so on... The only "real" partitions are /dev/sda2 for EFI, /dev/sda4 for Windows, and /dev/sda8 for Arch.
    Here are some command outputs to show you what my system is like. I hope they are helpful. If there's anything missing I shall supplement it of course!
    Thanks in advance
    sudo efibootmgr -v
    BootCurrent: 0002
    Timeout: 0 seconds
    BootOrder: 0002,0001,0006,0003,0000
    Boot0000* Windows Boot Manager Vendor(99e275e7-75a0-4b37-a2e6-c5385e6c00cb,)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
    Boot0001* linuxmint HD(2,fa000,96000,f718c38a-c1d8-4c72-9b59-e098594840a2)File(\EFI\linuxmint\grubx64.efi)
    Boot0002* arch_grub HD(2,fa000,96000,f718c38a-c1d8-4c72-9b59-e098594840a2)File(\EFI\arch_grub\grubx64.efi)
    Boot0003* Windows Boot Manager HD(2,fa000,96000,f718c38a-c1d8-4c72-9b59-e098594840a2)File(\EFI\Microsoft\Boot\bootmgfw.efi)
    Boot0006* Windows Boot Manager HD(6,3a186001,200000,d41549d3-0b93-40ef-4173-636c65706975)File(\EFI\Microsoft\Boot\bootmgfw.efi)
    mount
    proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
    sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
    dev on /dev type devtmpfs (rw,nosuid,relatime,size=2997764k,nr_inodes=749441,mode=755)
    run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
    /dev/sda8 on / type ext4 (rw,relatime,data=ordered)
    securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
    tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
    devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
    tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,mode=755)
    cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
    pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
    efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
    cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
    cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu)
    cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
    cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
    cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
    cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
    cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
    systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=35,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
    hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
    binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
    tmpfs on /tmp type tmpfs (rw)
    mqueue on /dev/mqueue type mqueue (rw,relatime)
    configfs on /sys/kernel/config type configfs (rw,relatime)
    debugfs on /sys/kernel/debug type debugfs (rw,relatime)
    /dev/sda2 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
    fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
    gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)
    [james@James-Laptop ~]$ lsblk
    NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
    sda 8:0 0 465.8G 0 disk
    ├─sda1 8:1 0 499M 0 part
    ├─sda2 8:2 0 300M 0 part /boot
    ├─sda3 8:3 0 128M 0 part
    ├─sda4 8:4 0 342.4G 0 part
    ├─sda5 8:5 0 23.8G 0 part
    ├─sda6 8:6 0 1G 0 part
    ├─sda7 8:7 0 977K 0 part
    ├─sda8 8:8 0 91.8G 0 part /
    └─sda9 8:9 0 5.9G 0 part [SWAP]
    [james@James-Laptop ~]$ cat /boot/grub/grub.cfg
    # 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 ext2
    set root='hd0,gpt8'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt8 --hint-efi=hd0,gpt8 --hint-baremetal=ahci0,gpt8 7e2ee467-3fd3-41b3-8c1f-62cc45f2d098
    else
    search --no-floppy --fs-uuid --set=root 7e2ee467-3fd3-41b3-8c1f-62cc45f2d098
    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_GB
    insmod gettext
    fi
    terminal_input console
    terminal_output gfxterm
    set timeout=5
    ### END /etc/grub.d/00_header ###
    ### BEGIN /etc/grub.d/10_linux ###
    menuentry 'Arch Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-7e2ee467-3fd3-41b3-8c1f-62cc45f2d098' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_gpt
    insmod fat
    set root='hd0,gpt2'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 ECB7-2436
    else
    search --no-floppy --fs-uuid --set=root ECB7-2436
    fi
    echo 'Loading Linux core repo kernel ...'
    linux /vmlinuz-linux root=UUID=7e2ee467-3fd3-41b3-8c1f-62cc45f2d098 rw quiet
    echo 'Loading initial ramdisk ...'
    initrd /initramfs-linux.img
    menuentry 'Arch Linux, with Linux core repo kernel (Fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-fallback-7e2ee467-3fd3-41b3-8c1f-62cc45f2d098' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_gpt
    insmod fat
    set root='hd0,gpt2'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 ECB7-2436
    else
    search --no-floppy --fs-uuid --set=root ECB7-2436
    fi
    echo 'Loading Linux core repo kernel ...'
    linux /vmlinuz-linux root=UUID=7e2ee467-3fd3-41b3-8c1f-62cc45f2d098 rw 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 Boot Manager (on /dev/sda2)' --class windows --class os $menuentry_id_option 'osprober-efi-ECB7-2436' {
    insmod part_gpt
    insmod fat
    set root='hd0,gpt2'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 ECB7-2436
    else
    search --no-floppy --fs-uuid --set=root ECB7-2436
    fi
    chainloader /EFI/Microsoft/Boot/bootmgfw.efi
    ### 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.
    menuentry "Windows 8" {
    insmod part_gpt
    insmod fat
    insmod search_fs_uuid
    insmod chain
    search --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 ECB7-2436
    chainloader /EFI/Microsoft/Boot/bootmgfw.efi
    ### 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+ ###
    Last edited by jabonz2048 (2013-09-19 15:07:34)

    Hello cfr,
    Thanks for your reply!
    Yes, I had /dev/sda2, my EFI partition, mounted at /boot when I did grub-install and grub-mkconfig. I also had the efivars filesystem unmounted, and ran rmmod plus modprobe on efivars as written.
    umount /sys/firmware/efi/efivars
    # modprobe -r efivars
    # modprobe efivars
    My command was exactly the same as the beginner's guide, and it was
    grub-install --efi-directory=/boot --bootloader-id=arch_grub --recheck
    Now looking at that command, I am wondering, should it have been "--efi-directory=/boot/EFI" or something similar like that? But the fact that Arch boots and runs fine kind of shows the bootloader did indeed install correctly... Or partially at least.
    Maybe an ls -l of some of my /boot directories might be useful. Thanks!
    ls -l /boot
    total 16352
    drwxr-xr-x 39 root root 4096 Nov 17 2012 Boot
    -r-xr-xr-x 1 root root 398156 Jul 25 2012 bootmgr
    -rwxr-xr-x 1 root root 1 Jun 2 2012 BOOTNXT
    drwxr-xr-x 6 root root 4096 Aug 26 15:28 EFI
    drwxr-xr-x 6 root root 4096 Aug 26 17:39 grub
    -rwxr-xr-x 1 root root 10351180 Aug 26 14:19 initramfs-linux-fallback.img
    -rwxr-xr-x 1 root root 2185900 Aug 26 14:18 initramfs-linux.img
    -rwxr-xr-x 1 root root 3782368 Aug 21 11:53 vmlinuz-linux
    [james@James-Laptop teamviewer]$ ls -l /boot/EFI
    total 16
    drwxr-xr-x 2 root root 4096 Aug 26 15:28 arch_grub
    drwxr-xr-x 2 root root 4096 May 22 20:53 Boot
    drwxr-xr-x 2 root root 4096 May 22 20:53 linuxmint
    drwxr-xr-x 3 root root 4096 Nov 17 2012 Microsoft
    [james@James-Laptop teamviewer]$ ls -l /boot/grub/
    total 48
    drwxr-xr-x 2 root root 4096 Aug 26 15:28 fonts
    -rwxr-xr-x 1 root root 4767 Aug 26 17:39 grub.cfg
    -rwxr-xr-x 1 root root 4063 Aug 26 14:22 grub.cfg.example
    -rwxr-xr-x 1 root root 1024 Aug 26 15:28 grubenv
    drwxr-xr-x 2 root root 4096 Aug 26 15:28 locale
    drwxr-xr-x 3 root root 4096 Aug 26 15:28 themes
    drwxr-xr-x 2 root root 20480 Aug 26 15:28 x86_64-efi

  • [solved] grub install fails /boot/grub is not readable

    virtualbox install
    single partition install (well, I have two partitions, #2 is / and #1 is the BIOS partition as defined in the install docs)
    when I get to the stage of installing grub, I use :
    grub-install --target=i386-pc --recheck /dev/sda
    which fails with
    Path '/boot/grub' is not readable by GRUB on boot. Installation is impossible. Aborting"
    it is ext4
    fstab looks correct. It shows one entry for
    /dev/sda1 / ext4
    I am not using UUID although when I did the result was the same.
    when run with debug, the problem is
    /usr/bin/grub-probe -t fs /boot/grub
    results in path no readable.
    when I run the grub-probe inside the chroot, I get error: unknown filesystem
    haven't had this before. This is the first time I've tried a GPT install.
    It is virtualbox 4.2.18
    I
    Last edited by timrichardson (2013-10-15 10:10:50)

    Ah, my mistake was an incorrect partition table back when I partitioned the disk. I did not make a partition table for GPT partitions.

Maybe you are looking for