[SOLVED] EFI grub Install problems

I know this topic has been beat to death but I cannot for the life of me figure this out.
My Config:
1 Hard Drive -- /dev/sda
/dev/sda2 is EFI Partition.
/dev/sda5 is /mnt/boot during the install
/dev/sda6 is /mnt/ during the install
PC has windows 8.1 installed and booting fine with rEFInd installed. I run through the basic arch installation and mount my /dev/sda2 to /boot/ like in the beginners guide.
I chroot and do the commands below: (from the wiki)
# mount -t efivarfs efivarfs /sys/firmware/efi/efivars # ignore if already mounted
# pacman -S grub efibootmgr
# grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=arch_grub --recheck
It installs fine, and then I run:
# grub-mkconfig -o /boot/grub/grub.cfg
It completes as well, and im left with a EFI/arch_grub/something.efi and then a /grub folder with the config in it on my EFI partition.
When I reboot, grub completly takes over and doesnt boot anything. Just stuck at grub2>...
I have to boot off live CD and remove the EFI/arch_grub folder and the other grub folder to be able to boot windows again.
What am I doing wrong here?
Any help is appreciated....
Last edited by skwid (2013-11-19 17:38:01)

teateawhy wrote:You mounted the boot partition on sda5 to /boot, instead of mounting the ESP on sda2 to /boot. The beginner's guide expects you to mount the ESP to /boot.
Ok, I went back and re-done the entire thing and made sure I mounted /dev/sda5 to /boot. That left me with a /boot/EFI folder which my refind and microsoft folders are in.
Ran through the installs and everything went fine. I have a /boot/EFI/arch_grub/grubx64.efi file and a /boot/efi/grub/ folder with the grub.cfg file. No errors.
Rebooted, and same thing. reFINd no longer runs first, grub does. grub is broken because there are no kernel lines or anything.
When I reboot the PC and select the boot menu in the BIOS, I get a UEFI entry for "arch_grub" and I can select it and it boots to the broken grub.
I can select rEFInd and it will run, but not automatically like it used to.
If I remove all the arch_grub and grub folder from my EFI partition, then everything works, but of course, no arch.

Similar Messages

[SOLVED][GRUB]Install problem with the new method

Hi,
it is not my first install of Arch Linux but I have a problem with this new kind of installation method, especially with GRUB.
Here is my hard drives configuration :
/dev/sda1 -> SSD 120 GB ntfs (windows)
/dev/sdb1 -> HD 1 TB ext4 (data)
/dev/sdc :
/dev/sdc1 -> ext2 /boot
/dev/sdc2 -> swap
/dev/sdc3 -> ext4 /
/dev/sdc5 -> ext4 /home
During the installation, I installed grub (with grub-install) in /dev/sdc. I assumed it was the correct drive to install it but apparently not, Windows starts automatically and I don't have the grub menu.
Should I install my system again or is there a way to boot on the livecd and install it ?
Should I :
1) mount /dev/sdc3 in /mnt then /dev/sdc1 in /mnt/boot and finally /dev/sdc5 in /mnt/home
2) pacstrap /mnt grub-bios
3) arch-chroot
4) grub-install
Thank you.
Last edited by hiveNzin0 (2012-09-12 06:15:15)

DSpider wrote:
If you set whatever drive "/dev/sdc" is (brand and model) to boot first in the BIOS, all you need to do is install a bootloader on Arch. You don't even need a separate boot partition. It will use the /boot folder on root partition. Then install os-prober (if you don't already have this installed) and re-generate the .cfg.
https://wiki.archlinux.org/index.php/Be … bootloader
The problem is that I cannot select another hard drive. The only one available for the boot order is the Samsung 830 series (/dev/sda with Windows).
The other options are the CD drive and removable disk.
I checked that this morning, maybe I was too tired. I will check again this evening.
But if I am right and I cannot select my intel SSD (containing my arch setup) for the boot order, would the solution I described work ? I don't see why not but my knowledge are basic in Linux.
Thank you again for your help.

[SOLVED]second HDD installing problems

I have tried to install a second hard drive, but when I should try to use it, I got the message:
"An error occurred while accessing «Volum (reiserfs)» The system responded: org freedesktop.Hal.Device.PermissionDeniedByPolicy: org.freedesktop.hal.storage.mount-fixed.auth_admin_keep_always <--action,result"
How do I solve the probleme?
Thanks
Last edited by harida (2009-04-12 23:54:10)

Check this: http://bbs.archlinux.org/viewtopic.php?id=65652

[Solved] No grub installed. Now laptop running a little too hot.

I had fedora and crunchbang already running on my laptop so I had't installed grub. Now my laptop is running little hot even after installing Laptop Mode Tools
and there is no grub in /etc or /etc/default where I can change any values. If I install now and update after changes, will it affect my existing crunchbang grub?
Last edited by celebrimbor (2014-10-12 07:10:09)

derhamster At first I'd thought MatLab is the culprit. But then even with only leafpad running, the laptop was too hot.
And my
lspci
is
http://pastebin.archlinux.fr/449158
tomk : In #! forums I'd found that changing the GRUB line to
GRUB_CMDLINE_LINUX_DEFAULT="quiet i915.lvds_downclock=1 i915.i915_enable_fbc=1 i915.i915_enable_rc6=1"
made things a lot quieter. Hence I had asked.
DSpider and cfr You confuse me! I have intel graphics only. Don't have a dedicated graphics card.

Laptop stopped booting due to EFI boot device problems [SOLVED]

Hi,
I'm writing this from my old laptop. My Lenovo U330 touch will not boot. When I turn it on it states that 'default boot device is missing or boot failed'. It used to go to gummiboot and there were Linux and Windows boot options.
I can boot from an Arch USB drive and chroot but when I try to reinstall gummiboot or grub I get errors:
#gummiboot --path=$esp install
#failed to check filesystem type of install: No such file or directory
# grub-install --target=x86_64-efi --efi-directory=$esp --bootloader-id=grub --recheck --debug
#grub install error failed to get canonical path of `'
On this laptop there are various partitions for EFI and a small Windows 8 partition.
I guess there is some problem with the $esp
It should be /dev/sda2 and / is dev/sda6. All seem to be present and correct with fdisk -l, however, for some reason there is a boot flag on /
I've tried to sort it out for a few hours now. Please if anyone can help that would be amazing.
P
Last edited by pepedopolous (2014-06-22 22:38:55)

Head_on_a_Stick wrote:
pepedopolous wrote:[..] it is btrfs. [...]
Try again without using btrfs --- it is not production ready...
This is a pretty ridiculous suggestion. It may not be production ready and it may not be the best choice for the user, but it has nothing to do with the problem at hand.
@OP, are you literally typing:
gummiboot --path=$esp install
If so, $esp is a variable. So in your case you would need to set esp=/boot. But gummiboot's default --path for install is actually /boot. So you should only need to do:
gummiboot install

[SOLVED] grub-install command failing for UEFI

I downloaded the 8/2013 iso and burned it with dd. I have an ASUS Rampage IV Extreme motherboard. I was booted into efi mode on both the ISO and in the chroot (the /sys/firmware/efi directory did exist).
I followed the instructions in the Beginner's Guide, but with a 512 MB EFI partition as sda1, 50 GB root as sda2, the rest of my 256 GB SSD as /home, and a 100 GB space on my HDD as /tmp. Everything was ext4 and the EFI partition was a fat32. The EFI partition was mounted on /boot of the new install, as the beginner's guide stated it should be
Everything worked until I get to the part of installing GRUB. Before installing, I again confirmed that /sys/firmware/efi existed. When booting, on the motherboard boot selection screen, it showed 2 options for my USB, one with the name of my drive and another with [UEFI] in front of the drive name. I selected the UEFI option, so I was booted into UEFI mode, and the USB's bootloader also gave options to boot into a UEFI shell instead of the standard Arch ISO bootloader I get on MBR computers (though I did not try those EFI shell options). I looked into te /sys/firmware/efi/efivars directory and it had 2 items in it
Going back to the chroot's / directory, I did the first command in the guide for installing grub (after installing grub and efibootmgr with pacman).
umount /sys/firmware/efi/efivarsk
This gave the error that the directory was not mounted
modprobe -r efivars and modprobe efivars worked correctly (or at least they didn't output any errors).
When I got to
grub-install --efi-directory=/boot --bootloader-id=arch_grub --recheck
it gave this error:
Fatal: Couldn't open either sysfs or procfs directories for accessing EFI variables.
I searched around on the interwebs and for every other person this problem was occuring because they were booted into BIOS mode instead of UEFI mode, and booting the USB into UEFI mode fixed the problem for them. However, the /sys/firmware/efi directory exists and I made sure to boot into EFI mode in the BIOS.
Are there any other reasons that this could be happening?
Also, is there really any advantage to GPT/EFI booting over GPT/BIOS booting other than a 1-2 second shorter boot time?
Last edited by subraizada3 (2013-08-23 21:10:37)

You burnt it to CD?DVD, right? Not dd? Because that won't create an EFI bootable USB key, for example.
modprobe efivars never gives errors (that I've seen). The question is whether the directories are populated. It isn't enough for /sys/firmware/efi to exist. /sys/firmware/efi/vars/ should be full of a *lot* of stuff. In fact /sys/firmware/efi/efivars/ should have lots of stuff before you umount it.
Did you modprobe before arch-chroot? That's essential if the installed kernel is different from the one on the installer (which is very likely).
I think you are confused. There's no such thing as GPT/MBR booting.
GPT and MBR are 2 ways of partitioning disks. GPT has various advantages explained on the wiki page.
EFI and BIOS are 2 ways of booting.
In my personal opinion, if BIOS booting works for you, I'd stick with BIOS. EFI is buggy - why be a guinea pig if you can help it?
Also in my personal opinion, if you can only use GPT in EFI mode, it is worth the hassle to use EFI to reap the benefits of GPT.
At least, those are the decisions I made. Nothing will convince my laptop to boot BIOS mode with a GPT disk. MBR+BIOS is fine but GPT+BIOS is a non-starter. So I use GPT+EFI. On machines that don't care, I prefer BIOS+GPT.
If you are dual booting Windows, I believe BIOS+GPT may not be an option but I'm not certain of this.
Your kilometres may vary.
By the way, you almost certainly do not want a partition for /tmp unless you are extraordinarily short of RAM and even then...

Grub-install: "cannot find EFI directory" (CSM mode)

Hi,
I'm trying to install grub on the mbr with 'grub-install /dev/sdb', but I get "cannot find EFI directory'. I have an Asus laptop with secure boot disabled and CSM enabled (I *need* CSM because otherwise - I don't know the reason - I can't boot from USB/disk). I have Windows 7 installed (/dev/sdb2) and I know there's a small partition (/dev/sdb1) which was created during Windows 7 installation which contains a 'Boot' directory, a 'bootmgr' file and other stuff. Now, my purpose is to dual boot Windows 7 and Arch while the BIOS is in CSM mode. The problem is that a simple grub-install /dev/sdX does not work as expected (under Gentoo, it simply worked out-of-the-box). By now, I can chroot into my fresh Arch installation (/dev/sdb3). Another thing: possible targets for grub-install are 'i686-pc' and 'x86_64-efi'; when running grub-install the program automatically selects 'x86_64.efi' as target. I don't know if it's correct (I do have an AMD64 laptop, just to clarify). Thanks in advance.

tant0c1b0 wrote:Hi,
I'm trying to install grub on the mbr with 'grub-install /dev/sdb', but I get "cannot find EFI directory'. I have an Asus laptop with secure boot disabled and CSM enabled (I *need* CSM because otherwise - I don't know the reason - I can't boot from USB/disk). I have Windows 7 installed (/dev/sdb2) and I know there's a small partition (/dev/sdb1) which was created during Windows 7 installation which contains a 'Boot' directory, a 'bootmgr' file and other stuff. Now, my purpose is to dual boot Windows 7 and Arch while the BIOS is in CSM mode. The problem is that a simple grub-install /dev/sdX does not work as expected (under Gentoo, it simply worked out-of-the-box). By now, I can chroot into my fresh Arch installation (/dev/sdb3). Another thing: possible targets for grub-install are 'i686-pc' and 'x86_64-efi'; when running grub-install the program automatically selects 'x86_64.efi' as target. I don't know if it's correct (I do have an AMD64 laptop, just to clarify). Thanks in advance.
You are telling the system to act like it is a BIOS system as far as the boot process goes but I don't think you are using a disk with a MBR, master boot record partition table. Is your disk actually GPT? This is a common gotcha when trying to use CSM mode on a UEFI based system since UEFI systems come with GPT disks. I believe this describes Grub installation in your configuration.
https://wiki.archlinux.org/index.php/GR … structions
To be clear though, I don't think this is a good direction to go. This isn't keeping things simple though that may have been why you chose to do it. I don't have enough information to know but it sounds like your disk expected to be in a UEFI system and was created with a GPT partition scheme. I would use it that way for Arch and for Windows if you choose to have that installed. I think it creates unneeded complexity to create a hybrid UEFI/BIOS configuration. I would always have all disks using the same partition scheme (the reason you can't boot "USB/disk" may be that you need GPT) and all OS's booting UEFI on a UEFI system.

When the message arrives, the message tone sound that many times. How this problem can be solved? I installed the new version, but the problem is not resolved, the future is to be taken into account in the new version of this?

When the message arrives, the message tone sound that many times. How this problem can be solved? I installed the new version, but the problem is not resolved, the future is to be taken into account in the new version of this?

I'm not sure I understand the question, is the message tone going more then once?
Turn off repeat message alert here:
settings > notifications > messages > repeat alert > never
Some people have found this does not stop the repeat miessage tone,
if you are one of those then I suggest you contact Apple:
http://www.apple.com/feedback/iphone.html
They may not respond, but hopefully will fix in uodate if enough people complain.

[SOLVED]Grub-Install can't Find Kernel and/or initrd, mkinitcpio Fails

Hi all,
I have recently installed Arch on my new build (with UEFI firmware). I successfully set up xorg, alsa/pulseaudio, xfce, etc... things were looking pretty good. Then, I tried to blacklist the pcspkr in order to silence the annoying beep every time I selected "Log Out" inside xfce. I executed
mkinitcpio -p linux
and was presented with the following errors:
==> Building image from preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> ERROR: specified kernel image does not exist: `/boot/vmlinuz-linux'
==> Building image from preset: 'fallback'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> ERROR: specified kernel image does not exist: `/boot/vmlinuz-linux`
There were no such files anywhere on /boot. I tried doing
find / -name vmlinuz-linux
and nothing was found. I wasn't quite sure why that was happening, but I tried uninstalling/reinstall grub (grub-common and grub2-efi-x86_64). I installed grub to /boot using
grub-install --directory=/usr/lib/grub/x86_64-efi --target=x86_64-efi --efi-directory=/boot --bootloader-id="Arch Linux" --boot-directory=/boot --recheck --debug
and then generated /boot/grub/grub.cfg. I tried rebuilding the initramfs again but got the same error. I was tired and frustrated so I removed the old grub efi entry with
efibootmgr -b 0 -B
and then went to sleep.
I didn't have the chance to turn the computer back on until tonight... I was then presented with a grub2 shell. Since I didn't know where the kernel/initrd were located I tried
set root=(hd1,gpt1)
chainloader +1
but grub told me
error: invalid EFI file path
So that's about it. It appears that grub-mkconfig is having trouble locating the kernel/initrd so it doesn't make any entries, dropping me right into a shell. I've tried booting up with my installation USB and chrooting in and reinstalling grub again but nothing seems to work. So what I'd like to try to do is just boot up into my system and then modify add the grub boot entries entries I want... but I just can't figure out what's causing all these issues.
Sorry if I mess up any terminology... still learning the ropes here. Thanks for any input.
Last edited by cogeary (2012-09-17 05:35:51)

DSpider wrote:
==> ERROR: specified kernel image does not exist: `/boot/vmlinuz-linux'
Probably because you have a separate boot partition (not just the 512 MB "UEFISYS" FAT32 partition), which you forgot to mount (in fstab).
Post your /etc/fstab.
Thank you for your reply!
However, I do not have a separate boot partition apart from the "UEFISYS" partition. Here is my fstab:
# UUID=3ec307aa-0ead-4d33-b292-42bbe783d6ee
/dev/sda2 / ext4 rw,relatime,data=ordered 0 1
# UUID=B192-6C57
/dev/sda1 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
When I first looked at the fstab I saw that both of the entries repeated themselves. This was because I had even tried reformatting /boot so I had to generate a new fstab, but for some reason I used ">> /mnt/etc/fstab" rather than "> ..."
So I executed
genfstab /mnt > /mnt/etc/fstab
and reinstalled grub, but still no difference... mkinitcpio fails and I reboot to a grub shell.
Last edited by cogeary (2012-09-16 18:15:51)

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

[Solved] grub-install hangs

I have an install of ARCH linux on a 2 partitioned hard drive with Ubuntu on a separate partition. Originally the drive contained a 64 bit version of Ubuntu on the first partition. I moved the drive to a different (32 bit) computer and installed 32 bit Ubuntu on the second partition. I then reformatted the first partition and installed 32 bit ARCH running update-grub from Ubuntu which found the new ARCH installation without any difficulty. As this seems to be becoming my main distribution I would like to reinstall grub2 from ARCH. I installed grub2 from the extra repository (1.98-5). When I enter 'sudo grub-install /dev/sda' the command hangs indefinitely. I attempted this in single user mode as well.
I did note the following appearing in /var/log/errors.log and the kernel log:
Aug 18 14:02:46 localhost kernel: end_request: I/O error, dev fd0, sector 0
.. (repeated several times... eventually...)
Aug 18 17:20:54 localhost kernel: Buffer I/O error on device fd0, logical block 0
This seems odd as I don't have a floppy drive connected. Running grub install with the --no-floppy option produced the same result.
EDITED TO ADD: It appears as though the floppy drive related errors are occurring specifically when grub-install is executing. Further they seem to occur when the --no-floppy flag is included. It appears as though the script is stuck repeatedly trying to access the floppy drive despite the flag.
EDITED WITH SOLUTION: I disabled the floppy drive in the system bios (no drive is/was connected) and grub installed without issue. I didn't realize I had the non-existent drive enabled as oddly ubuntu had no problem with installing grub while the ARCH version ignored my explicit instructions to disregard the floppy drive.
Any suggestions most appreciated!
Last edited by scotths (2010-08-19 17:44:11)

I have an install of ARCH linux on a 2 partitioned hard drive with Ubuntu on a separate partition. Originally the drive contained a 64 bit version of Ubuntu on the first partition. I moved the drive to a different (32 bit) computer and installed 32 bit Ubuntu on the second partition. I then reformatted the first partition and installed 32 bit ARCH running update-grub from Ubuntu which found the new ARCH installation without any difficulty. As this seems to be becoming my main distribution I would like to reinstall grub2 from ARCH. I installed grub2 from the extra repository (1.98-5). When I enter 'sudo grub-install /dev/sda' the command hangs indefinitely. I attempted this in single user mode as well.
I did note the following appearing in /var/log/errors.log and the kernel log:
Aug 18 14:02:46 localhost kernel: end_request: I/O error, dev fd0, sector 0
.. (repeated several times... eventually...)
Aug 18 17:20:54 localhost kernel: Buffer I/O error on device fd0, logical block 0
This seems odd as I don't have a floppy drive connected. Running grub install with the --no-floppy option produced the same result.
EDITED TO ADD: It appears as though the floppy drive related errors are occurring specifically when grub-install is executing. Further they seem to occur when the --no-floppy flag is included. It appears as though the script is stuck repeatedly trying to access the floppy drive despite the flag.
EDITED WITH SOLUTION: I disabled the floppy drive in the system bios (no drive is/was connected) and grub installed without issue. I didn't realize I had the non-existent drive enabled as oddly ubuntu had no problem with installing grub while the ARCH version ignored my explicit instructions to disregard the floppy drive.
Any suggestions most appreciated!
Last edited by scotths (2010-08-19 17:44:11)

[SOLVED]Unable to install grub "couldn't find /mnt/boot/grub/menu.lst"

Ok so I was trying to install windows after I had arch installed, used an ubuntu cd to use gparted to create a partition, tried to go to the windows installation but it would endlessly send me back to restart the installation even after succesfully writting all files...
So now I decided to not install it, went back into ubuntu/gparted, deleted the partition and rejoined the space with my main arch partition and then selected the "boot" flag to boot...
Cannot boot, grub its still on /boot/ but the MBR its obviously tempered with by windows ( which coincidentally couldn't even find itself after writing mbr to its liking....*sigh* ).
So I try to use my arch install cd to reinstall grub but i get this:
"couldn't find /mnt/boot/grub/menu.lst is grub installed?"
I tried to use the select packages thing to make sure the cd is mounted and mounts fine but it keeps getting me that error message. I managed to boot to my system just fine with arch root=/dev/sda1 but obviosly the kernell does not has my nvidia module which means I can't get into x which means i am using links and since my grub is not loaded i can't even get framebuffer so this is rather inconvenient.
Im sure im missing a very simple and stupid thing but im so annoyed my brain must be saying "ok im done somebody else figure it out". I still have a backup copy of my grub menu.lst I made before. Do I just delete /bood/grub/ and try again? Am I missing something on the install procedure to be able to rewrite grub? Can I just do it from the command line or with pacman? Any help appreciate it thanks.
Last edited by Misanthrope (2008-06-01 17:22:32)

If you can get into your arch and cli then you should just be able to reinstall grub with
install-grub /dev/sda
or reinstall grub with
pacman -S grub
if the package is messed up or missing.

[Solved]grub2 didnt install correctly suck at grub shell

I upgraded from grub to grub2 and now Im stuck at the grub shell.
I have tried this from my usb live install :
#root
#mount /dev/sda5 /mnt (sd5 is my root partition)
#mount /dev/sda1 /mnt/boot
# mount -t proc none /mnt/proc
# mount -t sysfs none /mnt/sys
# mount --bind /dev /mnt/dev
#chroot /mnt
#pacman -S grub2
#grub-mkconfig -0 /boot/grub/grub.cfg
I look like the upgrade didnt upgrade because when i reboot computer it says gnu grub version 0.97 which isnt grub2
Last edited by specialist125 (2010-06-17 02:51:56)

Let me give you the url to check: http://wiki.archlinux.org/index.php/Grub2
(You have to tell grub-install where you want to install grub.)

GRUB-install weirdness

When I installed Arch I decided not to install its GRUB in the MBR, leaving that to Mepis, which I have on another partition. Now I've decided to get rid of Mepis; before doing that, I want to install Arch's GRUB in the MBR.
I followed the directions in my Knoppix book for reinstalling GRUB in the MBR. Using a Knoppix disk I mounted my Arch partition (hda6) and tried to run grub-install:
root@1[root]# mount -o dev,rw /mnt/hda6
root@1[root]# chroot /mnt/hda6 grub-install /dev/hda
/dev/hda: Not found or not a block device.
Then on a whim I tried reinstalling Mepis' GRUB (Mepis is hdb1) in the MBR:
root@1[root]# mount -o dev,rw /mnt/hdb1
root@1[root]# chroot /mnt/hdb1 grub-install /dev/hda
Installation finished. No error reported.
This is the contents of the device map /boot/grub/device.map.
Check if this is correct or not. If any of the lines is incorrect,
fix it and re-run the script `grub-install'.
(hd0) /dev/hda
(hd1) /dev/hdb
(hd2) /dev/sda
Why this discrepancy--why the /dev/hda error in the first case but not the second? Is this a GRUB bug or am I missing something? I also tried this with the Mepis CD, with the same results. Thanks.

I tried mount --bind dev/proc but it did not solve the problem. I got an error message stating that /dev/hda was not a valid BIOS drive. When I Googled the error message I found a post on the Mandriva forums from a person with the same problem, who found that it was caused by the lack of (hdx) info in /boot/grub/device.map.
Sure enough, I looked in my Arch device.map and found no hd info. I was wondering if this had something to do with udev--I'm still not very udev-savvy. Other distros I have installed that don't use udev (like the Mepis I partition) had device.map listings with hd mapping. Anyway, I added (hd0) /dev/hda to Arch's device.map and GRUB installed in the MBR like I wanted. Just wondering, though, will this mess with udev?

Solaris 10 install problem (requested image to big to fit into memory)

I have just downloaded the iso images and burned to disk. When I go to install I get the message (Requested image to big to fit into memory Error 28) I have 1.5GB so I don't understand the problem. Thanks in advance
It took a long time for me to figure out, but the answer is disable in BIOS memory hole at 15M to 16M. This solved the install problem with Open Solaris and quite a few more such as not being able to install Linux Zenwalk 5.0 or openSUSE 10.3. Their are others also problems I have had with Linux or UNIX that this took care of. JGZ
Edited by: jgz on Mar 8, 2008 9:13 PM

Hi,
I had been able to solve the Error 28 issue that in my case was really related to a corrupted boot image:
1. I went in the path /a/platform/i86pc
2. rm boot_archive.
3. sync
4. reboot
At this point the OS will notice the absence of the boot_image and it will regenerate it.
At the time of this operation the CD with solaris 10 was inserted in the CDROM.
When the system restarted it was able to load the OS properly.
Please use these information at your own risk. I do not accept any liablity.
Cheers

[SOLVED] EFI grub Install problems

Similar Messages

Maybe you are looking for