[SOLVED]arch doesnt boot
i can see the grub menu after that wen i select arch , screen goes blank .I have tried gettin into single user mode thro GRUB it also doesnt work.Wen i select arch fallback it goes upto initrd & hangs.I tried using Ubuntu live cd it gives some wierd msg saying uncompressing linux & hangs .. Pl help...thanks in advance
Last edited by mugen (2008-06-28 19:41:06)
Hello mugen,
Thanks for telling my problem and getting help. I realised that there should be something wrong with my ram, since even a live cd hangs while uncompressing the kernel. So I figured that the problem is either due to the RAM or the RAM slot. Just to test I ran the memtest and the process hanged halfway through.This confirmed my suspicions. So I changed the RAM slot and everything works fine. In case this didnt work I would have tried changing the RAM.
Thanks man,
Spai
P.S:I am posting what I did here, so that it will be helpful to others who face the same problem
Last edited by Isomorphism (2008-06-28 15:23:48)
Similar Messages
-
[SOLVED] Arch Linux Boot from USB fails while loading kernel
I am attempting to get arch linux booting off my usb. I use cfdisk to create a /dev/sdb1 partition then use mkfs.ext4 /dev/sdb1, mount the usb, pacstrap it, use install-syslinux_update -iam, generate fstab and then attempt to boot from it.
The boot extracts the kernel but then complains that DEVICE is missing in the option APPEND root=DEVICE (in syslinux.cfg). I looked in /dev/disk (on the temporary filesystem shell), it showed my ssd and cd drive but not the usb. Does anyone know what could be causing the USB to not load in that particular section of the kernel?
Last edited by afree10 (2013-12-11 14:28:14)afree10 wrote:
Due to my situation I have to type the file in from scratch so I will only type uncommented lines:
MODULES=""
BINARIES=""
FILES=""
HOOKS="base udev autodetect modconf block filesystems keyboard fsck"
I will reboot and get that lsmod output.
Since you'll probably want to boot from different computers (portable USB system), you want to remove 'autodetect' from that line. This is the same as always booting the initramfs-linux-fallback.img image. To save some space, you could remove 'autodetect' from the configuration file, disable the fallback image in /etc/mkinitcpio.d/linux.preset and delete initramfs-linux.img (otherwise, you'll get two identical images).
Of course, run mkinitcpio -P when you're done. -
[SOLVED] arch wont boot after triple boot experiment
Hi,
I cannot boot into arch anymore after installing ubuntu to another partition on my hard drive.
I used grub to dual boot arch and windows, but i need to use ROS and there are no working packages for arch so i tried to install ubuntu on another partition and triple boot.
Somhow my arch got broken by the ubuntu setup.
Windows still boots fine.
I already chrooted (to arch) from a live cd and reinstalled grub and did
grub-mkconfig -o /boot/grub/grub.cfg
, after that ubuntu appeared in the grub selection menu but arch still wont boot.
Arch boot hangs after checking /dev/sda6 for errors (arch partition), i cannot type or ctrl+shift+fx to another terminal
Anybody has an idea what got broken by ubuntu and how i can repair arch?
thanks!
samy
Last edited by Samy (2013-09-09 11:27:09)Hey so i chroot again following this artikle: https://wiki.archlinux.org/index.php/Change_Root
then i did
pacman -Syyu mkinitcpio linux udev
and restarted
I tried starting arch again and it seemed to still not work, this time i gave it some more time and it actually booted.
It took very long though (more then 3 minutes or so)
in journalctl if found those lines:
Sep 09 04:20:00 meanarchy kernel: USB Video Class driver (1.1.1)
Sep 09 04:21:25 meanarchy systemd[1]: Job dev-disk-by\x2duuid-12027d8a\x2dd4b0\x2d4559\x2daa1c\x2de3ea5ca8f5bb.device/start timed out.
Sep 09 04:21:25 meanarchy systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-12027d8a\x2dd4b0\x2d4559\x2daa1c\x2de3ea5ca8f5bb.device.
Sep 09 04:21:25 meanarchy systemd[1]: Dependency failed for /dev/disk/by-uuid/12027d8a-d4b0-4559-aa1c-e3ea5ca8f5bb.
Sep 09 04:21:25 meanarchy systemd[1]: Starting Swap.
so it seems boot is searching for some disk device 1:25 minutes before it fails.
I think i know the reason: I resized the Partition of arch while installing ubuntu this changes the uuid of the partition, now something is waiting for this disk to become ready because it still has the old uuid written somwhere.
UUIDs really suck, they are not human readable and always have problems with them if i touch my partitions.
Last edited by Samy (2013-09-09 11:27:45) -
[SOLVED] Arch freezes after mounting drives, cannot boot
Installed Arch maybe a week ago, and everything worked flawlessly until i rebooted today.
I havent done any major changes during that session that i recall, and after a reboot, my arch "froze" mid boot, after (what i think is) mounting drives (sda3 is OS, sda5 is Data):
/dev/sda3: clean, 168249/2298240 files, 1485743/9175040 blocks
[ 4.203801] microcode: failed to load file amd-ucode/microcode_amd.bin
[ 4.204249] microcode: failed to load file amd-ucode/microcode_amd.bin
[ 4.204628] microcode: failed to load file amd-ucode/microcode_amd.bin
[ 4.204940] microcode: failed to load file amd-ucode/microcode_amd.bin
systemd-fsck[248]: /dev/sda5: clean, 5230/3932656 files, 475548/15729635 blocks
This is all the info that i get.
If i remember right, this was shown when arch was booting up normally too, but it ussualy just hanged for a second or two at it. I've tried leaving it for almost half an hour now, and it didnt budge.
And it doesnt actually freeze, since there is a blinking " | " after the last line (no input is being accepted though)
This might be something stupidly simple, but im completely new to Arch (and linux in general)
I do have a live cd though, so if there's any conf that you think would help, i can get it.
Last edited by TolSatha (2012-12-28 01:09:24)cfr wrote:
Welcome to Arch.
Please search before posting:
https://encrypted.google.com/search?hl= … lla-search
https://wiki.archlinux.org/index.php/Microcode
https://bbs.archlinux.org/viewtopic.php?id=144699
etc.
Will try resolving that, but ive had that before, and arch booted just fine. I doubt thats the problem. -
[Solved] Can't boot into Arch after deleting some partitons
About 6 months ago I installed Arch on a machine that used to run Ubuntu. Had some trouble at the time getting to boot into Arch but somehow managed. Now eventually decided to delete the old Ubuntu partitons to free up some space using gparted. Arch partition number changed from sda12 to sda6.
On rebooting after deleting ubuntu partitions with gparted, I got an ubuntu splash screen and a whole lot of ubuntu boot options. Somehow these were all contained in my Arch's /boot/grub/menu.lst. Arch is all on one partition and no separate boot partition (which I had with Ubuntu - maybe I haven't deleted that and this is the problem?). Will need to check that out.
I can chroot into Arch and did the following -
grub> find /boot/grub/stage1
(hd0,5)
grub> root (hd0,5)
Filesystem type is ext2fs, partition type 0x83
grub> setup (hd0)
Checking if "/boot/grub/stage1" exists... yes
Checking if "/boot/grub/stage2" exists... yes
Checking if "/boot/grub/e2fs_stage1_5" exists... yes
Running "embed /boot/grub/e2fs_stage1_5 (hd0)"... 16 sectors are embedded.
succeeded
Running "install /boot/grub/stage1 (hd0) (hd0)1+16 p (hd0,5)/boot/grub/stage2 /boot/grub/menu.lst"... succeed
ed
Done.
grub>
The Arch /boot/grub/menu.lst had a whole lot of ubuntu stuff in it but I edited to the following -
# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.
## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not use 'savedefault' or your
# array will desync and will not let you boot your system.
default 0
## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 3
## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
hiddenmenu
# Pretty colours
#color cyan/blue white/blue
## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret
# examples
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST
## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,3)
title Arch uuid
#root (hd0,5)
uuid d15cf4f9-18ca-4ec5-95bc-db0f6f264736
kernel /boot/vmlinuz26 root=/dev/sda6 ro vga=775
intrd /boot/kernel26.img
title Arch hd
root (hd0,5)
kernel /boot/vmlinuz26 root=/dev/sda6
intrd /boot/kernel26.img
I have a bootinfo script which gives the following (from the chroot environment) -
Boot Info Script 0.55 dated February 15th, 2010
============================= Boot Info Summary: ==============================
=> Grub 0.97 is installed in the MBR of /dev/sda and looks on the same drive
in partition #6 for /boot/grub/stage2 and /boot/grub/menu.lst.
=> No boot loader is installed in the MBR of /dev/sdb
sda1: _________________________________________________________________________
File system: swap
Boot sector type: -
Boot sector info:
sda2: _________________________________________________________________________
File system: Extended Partition
Boot sector type: -
Boot sector info:
sda5: _________________________________________________________________________
File system: ext3
Boot sector type: -
Boot sector info:
Mounting failed:
mount: /dev/sda5 already mounted or sda5 busy
sda6: _________________________________________________________________________
File system: ext3
Boot sector type: -
Boot sector info:
Mounting failed:
mount: /dev/sda5 already mounted or sda5 busy
mount: /dev/sda6 already mounted or sda6 busy
sda7: _________________________________________________________________________
File system: ext3
Boot sector type: -
Boot sector info:
Operating System:
Boot files/dirs:
sda3: _________________________________________________________________________
File system: ext3
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 10.04.1 LTS
Boot files/dirs: /etc/fstab
sda4: _________________________________________________________________________
File system: ext3
Boot sector type: -
Boot sector info:
Operating System:
Boot files/dirs: /grub/menu.lst /grub/grub.cfg /grub/core.img
sdb1: _________________________________________________________________________
File system: xfs
Boot sector type: -
Boot sector info:
Operating System:
Boot files/dirs:
=========================== Drive/Partition Info: =============================
Drive: sda ___________________ _____________________________________________________
Disk /dev/sda: 750.2 GB, 750155292160 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465147055 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
Partition Boot Start End Size Id System
/dev/sda1 417,690 6,554,519 6,136,830 82 Linux swap / Solaris
/dev/sda2 25,414,954 1,465,144,064 1,439,729,111 5 Extended
/dev/sda5 25,414,956 1,360,287,809 1,334,872,854 83 Linux
/dev/sda6 1,360,287,873 1,423,198,349 62,910,477 83 Linux
/dev/sda7 1,423,198,413 1,465,144,064 41,945,652 83 Linux
/dev/sda3 6,554,520 25,414,829 18,860,310 83 Linux
/dev/sda4 * 63 417,689 417,627 83 Linux
Drive: sdb ___________________ _____________________________________________________
Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
Partition Boot Start End Size Id System
/dev/sdb1 2,048 1,953,523,711 1,953,521,664 83 Linux
blkid -c /dev/null: ____________________________________________________________
Device UUID TYPE LABEL
/dev/loop0 squashfs
/dev/sda1 2a95d85a-45fe-4584-88dd-0ee20e651ec5 swap
/dev/sda2: PTTYPE="dos" PART_ENTRY_SCHEME="dos" PART_ENTRY_TYPE="0x5" PART_ENTRY_NUMBER="2"
/dev/sda3 32495e1a-227c-4d23-9f63-b1319def0dd9 ext3
/dev/sda4 d6dc69b0-967d-4886-b62d-8c0d6be06b41 ext3
/dev/sda5 37971286-b8d3-4a1b-9f94-4008288fed6d ext3 data
/dev/sda6 d15cf4f9-18ca-4ec5-95bc-db0f6f264736 ext3 30GB-02
/dev/sda7 eb736131-b558-4404-9b83-7f1e6d9e76ae ext3 var
/dev/sda: PTTYPE="dos"
/dev/sdb1 0e83045d-a0bd-4d36-b61d-bdb905130dc2 xfs 1TB-04
/dev/sdb: PTTYPE="dos"
============================ "mount | grep ^/dev output: ===========================
Device Mount_Point Type Options
/dev/sda12 / ext3 (rw,commit=0)
=============================== sda3/etc/fstab: ===============================
# /etc/fstab: static file system information.
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda1 = swap
/dev/sda1 none swap sw 0 0
# /dev/sda3 = root
#UUID=32495e1a-227c-4d23-9f63-b1319def0dd9
/dev/sda3 / ext3 relatime,errors=remount-ro 0 1
# /dev/sda4 = boot
# UUID=d6dc69b0-967d-4886-b62d-8c0d6be06b41
/dev/sda4 /boot ext3 relatime 0 2
# /dev/sda5 = home
# UUID=670eee83-0a3e-429c-863f-b9ecced9f97e
/dev/sda5 /home ext3 relatime 0 2
#/dev/sda6
#UUID=37971286-b8d3-4a1b-9f94-4008288fed6d
/dev/sda6 /home/ben/Data ext3 defaults,relatime 0 0
# /dev/sda7
# UUID=fdb14ca4-d71d-489f-a00e-6e608770674c
/dev/sda7 /var ext3 relatime 0 2
# /dev/sda8
/dev/sda8 /opt ext3 relatime 0 2
# /dev/sda10 - Arch
/dev/sda10 /mnt/arch ext3 relatime 0 2
# Not sure what this is doing here
# Have commented it out - May be the reason why xbmc and mythtv were crashing on dvd insert and play
# /dev/hda /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
# /dev/sde1
# uuid appears to be 644406B3570C1846 -> ../../sde1
#/dev/sde1 /home/ben/Data/TVRecordings-1TB01 xfs defaults,relatime 0 0
#1TB-01
UUID=76f3823a-81dc-45c9-a0b7-2bc6c3beb2f8 /media/1TB-01 xfs noatime,nodiratime,allocsize=512m 0 0 #remove
d defaults, relatime
# 1TB-02
UUID=59cbf7a1-7008-40d0-96ed-c6f231823d4f /media/1TB-02 xfs noatime,nodiratime,allocsize=512m 0 0 #remove
d defaults, relatime
# 1TB-03
UUID=0e936800-3c53-4b87-abc8-19be0ffca7f9 /media/1TB-03 xfs noatime,nodiratime,allocsize=512m 0 0 #remove
d defaults, relatime
# 750GB-02 ext3 Partition
# UUID giving problems, trying with dev
# UUID=c23b9c9a-66fc-4256-9211-73156c1ac64a /media/750GB-02_ext3 ext3 defaults,relatime 0 0
/dev/sde2 /media/750GB-02_ext3 ext3 defaults,relatime 0 0
============================= sda4/grub/menu.lst: =============================
# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.
## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not use 'savedefault' or your
# array will desync and will not let you boot your system.
default 0
## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 3
## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
hiddenmenu
# Pretty colours
#color cyan/blue white/blue
## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret
# examples
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST
### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below
## DO NOT UNCOMMENT THEM, Just edit them to your needs
## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro
## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,3)
## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true
## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false
## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash
## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false
## Xen hypervisor options to use with the default Xen boot option
# xenhopt=
## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0
## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery) single
# altoptions=(recovery mode) single
## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all
## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true
## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false
## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false
## ## End Default Options ##
title Ubuntu 10.04.1 LTS, kernel 2.6.32-26-generic
root (hd0,3)
kernel /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-26-generic
quiet
title Ubuntu 10.04.1 LTS, kernel 2.6.32-26-generic (recovery mode)
root (hd0,3)
kernel /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
initrd /initrd.img-2.6.32-26-generic
title Ubuntu 10.04.1 LTS, kernel 2.6.32-24-generic
root (hd0,3)
kernel /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-24-generic
quiet
title Ubuntu 10.04.1 LTS, kernel 2.6.32-24-generic (recovery mode)
root (hd0,3)
kernel /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
initrd /initrd.img-2.6.32-24-generic
title Ubuntu 10.04.1 LTS, kernel 2.6.32-23-generic
root (hd0,3)
kernel /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-23-generic
quiet
title Ubuntu 10.04.1 LTS, kernel 2.6.32-23-generic (recovery mode)
root (hd0,3)
kernel /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
initrd /initrd.img-2.6.32-23-generic
title Ubuntu 10.04.1 LTS, kernel 2.6.32-22-generic
root (hd0,3)
kernel /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-22-generic
quiet
title Ubuntu 10.04.1 LTS, kernel 2.6.32-22-generic (recovery mode)
root (hd0,3)
kernel /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
initrd /initrd.img-2.6.32-22-generic
title Ubuntu 10.04.1 LTS, memtest86+
root (hd0,3)
kernel /memtest86+.bin
quiet
### END DEBIAN AUTOMAGIC KERNELS LIST
============================= sda4/grub/grub.cfg: =============================
# DO NOT EDIT THIS FILE
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default="0"
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 recordfail {
set recordfail=1
if [ -n ${have_grubenv} ]; then if [ -z ${boot_once} ]; then save_env recordfail; fi; fi
insmod ext2
set root='(hd0,3)'
search --no-floppy --fs-uuid --set 32495e1a-227c-4d23-9f63-b1319def0dd9
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
insmod gfxterm
insmod vbe
if terminal_output gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal gfxterm
fi
fi
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
set locale_dir=($root)/grub/locale
set lang=en
insmod gettext
if [ ${recordfail} = 1 ]; then
set timeout=-1
else
set timeout=10
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Ubuntu, with Linux 2.6.32-26-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-26-generic
menuentry 'Ubuntu, with Linux 2.6.32-26-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
-class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
echo 'Loading Linux 2.6.32-26-generic ...'
linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
echo 'Loading initial ramdisk ...'
initrd /initrd.img-2.6.32-26-generic
menuentry 'Ubuntu, with Linux 2.6.32-24-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
linux /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-24-generic
menuentry 'Ubuntu, with Linux 2.6.32-24-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
-class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
echo 'Loading Linux 2.6.32-24-generic ...'
linux /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
echo 'Loading initial ramdisk ...'
initrd /initrd.img-2.6.32-24-generic
menuentry 'Ubuntu, with Linux 2.6.32-23-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
linux /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-23-generic
menuentry 'Ubuntu, with Linux 2.6.32-23-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
-class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
echo 'Loading Linux 2.6.32-23-generic ...'
linux /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
echo 'Loading initial ramdisk ...'
initrd /initrd.img-2.6.32-23-generic
menuentry 'Ubuntu, with Linux 2.6.32-22-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
linux /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-22-generic
menuentry 'Ubuntu, with Linux 2.6.32-22-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
-class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
echo 'Loading Linux 2.6.32-22-generic ...'
linux /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
echo 'Loading initial ramdisk ...'
initrd /initrd.img-2.6.32-22-generic
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
linux16 /memtest86+.bin
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
linux16 /memtest86+.bin console=ttyS0,115200n8
### END /etc/grub.d/20_memtest86+ ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Arch Linux (on /dev/sda10)" {
insmod ext2
set root='(hd0,10)'
search --no-floppy --fs-uuid --set 26851879-58d1-4d65-90b4-e0845fe1176c
linux /boot/vmlinuz26 root=/dev/sda10 ro
initrd /boot/kernel26.img
menuentry "Arch Linux Fallback (on /dev/sda10)" {
insmod ext2
set root='(hd0,10)'
search --no-floppy --fs-uuid --set 26851879-58d1-4d65-90b4-e0845fe1176c
linux /boot/vmlinuz26 root=/dev/sda10 ro
initrd /boot/kernel26-fallback.img
#### 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.
# From Arch grub menu.lst
# (0) Arch Linux
#title Arch Linux [/boot/vmlinuz26]
#root (hd0,0)
#kernel /vmlinuz26 root=/dev/sda3 ro
#initrd /kernel26.img
#Note: With a separate boot partition, omit /boot from the path, (i.e. type set prefix=(hdX,Y)/grub and insmod
(hdX,Y)/grub/linux.mod).
#This introduces the "linux" and "initrd" commands, which should be familiar (see #Configuration).
#An example, booting Arch Linux:
#set root=(hd0,5)
#linux /boot/vmlinuz26 root=/dev/sda5
#initrd /boot/kernel26.img
#boot
###menuentry "Arch1" {
###insmod ext2
###set root='(hd0,10)'
#search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 = FOR UBUNTU THIS IS THE BOOT
PARTITION
#linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash = FOR
UBUNTU THIS IS THE ROOT PARTITION
#initrd /initrd.img-2.6.32-26-generic
###search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 # UBUNTU'S BOOT PARTITION UU
ID
###linux /boot/vmlinuz-26 root=635d7d02-3f5b-4af6-9c74-16b2af8cc7fd ro quiet splash # ARCH'S ROOT UUID
###initrd /boot/kernel26.img
# /dev/sda10 uuid = 635d7d02-3f5b-4af6-9c74-16b2af8cc7fd - obtain using ls -l /dev/disk/by-uuid/
###menuentry "Arch2" {
###insmod ext2
###set root='(hd0,4)' #= TRYING UBUNTU'S BOOT
#search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 = FOR UBUNTU THIS IS THE BOOT
PARTITION
#linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash = FOR
UBUNTU THIS IS THE ROOT PARTITION
#initrd /initrd.img-2.6.32-26-generic
#search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 # UBUNTU'S BOOT PARTITION UUID
###linux /boot/vmlinuz-26 root=/dev/sda10 ro quiet splash # TRYING ARCH'S ROOT DEVICE FORMAT
###initrd /boot/kernel26.img
# /dev/sda10 uuid = 635d7d02-3f5b-4af6-9c74-16b2af8cc7fd - obtain using ls -l /dev/disk/by-uuid/
###menuentry "Arch3" {
###insmod ext2
###set root='(hd0,10)' #= TRYING UBUNTU'S BOOT IN HD FORMAT
#search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 = FOR UBUNTU THIS IS THE BOOT
PARTITION
#linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash = FOR
UBUNTU THIS IS THE ROOT PARTITION
#initrd /initrd.img-2.6.32-26-generic
#search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 # UBUNTU'S BOOT PARTITION UUID
###linux /boot/vmlinuz-26 root=/dev/sda10 ro quiet splash # TRYING ARCH'S ROOT DEVICE FORMAT
###initrd /boot/kernel26.img
# /dev/sda10 uuid = 635d7d02-3f5b-4af6-9c74-16b2af8cc7fd - obtain using ls -l /dev/disk/by-uuid/
### END /etc/grub.d/40_custom ###
=================== sda4: Location of files loaded by Grub: ===================
.0GB: grub/core.img
.0GB: grub/grub.cfg
.0GB: grub/menu.lst
.0GB: grub/stage2
.0GB: initrd.img-2.6.32-22-generic
.0GB: initrd.img-2.6.32-23-generic
.1GB: initrd.img-2.6.32-24-generic
.1GB: initrd.img-2.6.32-26-generic
.0GB: vmlinuz26
.0GB: vmlinuz-2.6.32-22-generic
.0GB: vmlinuz-2.6.32-23-generic
.1GB: vmlinuz-2.6.32-24-generic
.0GB: vmlinuz-2.6.32-26-generic
=============================== StdErr Messages: ===============================
No volume groups found
mdadm: No arrays found in config file or automatically
[/quote]
Output of fdisk -l from chroot is -
[quote]Disk /dev/sda: 750.2 GB, 750155292160 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465147055 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 identifier: 0x0000b084
Device Boot Start End Blocks Id System
/dev/sda1 417690 6554519 3068415 82 Linux swap / Solaris
/dev/sda2 25414954 1465144064 719864555+ 5 Extended
/dev/sda3 6554520 25414829 9430155 83 Linux
/dev/sda4 * 63 417689 208813+ 83 Linux
/dev/sda5 25414956 1360287809 667436427 83 Linux
/dev/sda6 1360287873 1423198349 31455238+ 83 Linux
/dev/sda7 1423198413 1465144064 20972826 83 Linux
Partition table entries are not in disk order
Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00025bd3
Device Boot Start End Blocks Id System
/dev/sdb1 2048 1953523711 976760832 83 Linux
I need to post this now and come back from a different machine to note the error messages I am now getting on boot. ...
Note that when I boot and press esc to get the menu I get the menu.lst I created (in the second quote) above in /dev/sda6, ie the one with the Arch hd and uuid entries - so grub is looking there and finding that menu.lst, but something goes wrong after that.
OK. Have now booted the machine and after pressing esc and selecting the uuid entry (the same thing happens with the hd entry) I get a whole lot of stuff, but what seems relevant is (typing it out) -
List of all partitions:
No filesystem could mount root, tried:
Kernel panic - not syncing: VS: Unable to mount root fs on unknown-block(0,0)
Pid: 1, comm: swapper Not tainted 2.6.39-Arch #1
If anyone can help I'd really appreciate it. This is my MythTV machine so the WAF is about to take a big dive!
If I could just install grub to the MBR as if this was a new installation of Arch that would be great.
I am really lost as to what is going on, which I'm sure is evident.
Thanks a lot
belbo
Last edited by belbo (2011-08-12 13:31:23)Hi. Unfortunately that didn't help.
So next, based on this post https://wiki.archlinux.org/index.php/Ke … el_version I chrooted into Arch and (a) rolled back and (b) reinstalled my kernel but that didn't help either. I suspected it wouldn't because the kernel was working fine before I deleted the partitions in question.
[2011-08-08 23:32] ==> Image generation successful
[2011-08-08 23:32] upgraded kernel26 (2.6.39.3-1 -> 2.6.39.3-1)
I then did a pacman -Suy and the linux package has now replaced kernel26. ( See this wiki entry http://www.archlinux.org/news/changes-t … filenames/). I didn't change anything in menu.lst owing to this and it seems there is no need to. Unfortunately this hasn't helped either - still getting the kernel panic.
Pacman.log relating to the new kernel package below -
[2011-08-09 00:22] Running 'pacman -Suy'
[2011-08-09 00:22] synchronizing package lists
[2011-08-09 00:23] starting full system upgrade
[2011-08-09 00:23] Running 'pacman -Suy'
[2011-08-09 00:23] synchronizing package lists
[2011-08-09 00:23] starting full system upgrade
[2011-08-09 00:26] removed python-mygpoclient (1.5-1)
[2011-08-09 00:26] removed kernel26 (2.6.39.3-1)
[2011-08-09 00:26] warning: /boot/grub/menu.lst installed as /boot/grub/menu.lst.pacnew
[2011-08-09 00:26] upgraded grub (0.97-17 -> 0.97-19)
[2011-08-09 00:26] upgraded icu (4.8-1 -> 4.8.1-1)
[2011-08-09 00:26] upgraded linux-firmware (20110512-2 -> 20110727-1)
[2011-08-09 00:26] >>> Updating module dependencies. Please wait ...
[2011-08-09 00:26] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2011-08-09 00:26] ==> Building image from preset: 'default'
[2011-08-09 00:26] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2011-08-09 00:26] ==> Starting build: 3.0-ARCH
[2011-08-09 00:26] -> Parsing hook: [base]
[2011-08-09 00:26] -> Parsing hook: [udev]
[2011-08-09 00:26] -> Parsing hook: [autodetect]
[2011-08-09 00:26] -> Parsing hook: [pata]
[2011-08-09 00:26] -> Parsing hook: [scsi]
[2011-08-09 00:26] -> Parsing hook: [sata]
[2011-08-09 00:26] -> Parsing hook: [filesystems]
[2011-08-09 00:26] -> Parsing hook: [usbinput]
[2011-08-09 00:26] ==> Generating module dependencies
[2011-08-09 00:26] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2011-08-09 00:26] 7079 blocks
[2011-08-09 00:26] ==> Image generation successful
[2011-08-09 00:26] ==> Building image from preset: 'fallback'
[2011-08-09 00:26] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2011-08-09 00:26] ==> Starting build: 3.0-ARCH
[2011-08-09 00:26] -> Parsing hook: [base]
[2011-08-09 00:26] -> Parsing hook: [udev]
[2011-08-09 00:26] -> Parsing hook: [pata]
[2011-08-09 00:26] -> Parsing hook: [scsi]
[2011-08-09 00:26] -> Parsing hook: [sata]
[2011-08-09 00:26] -> Parsing hook: [filesystems]
[2011-08-09 00:26] -> Parsing hook: [usbinput]
[2011-08-09 00:26] ==> Generating module dependencies
[2011-08-09 00:26] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2011-08-09 00:26] 23360 blocks
[2011-08-09 00:26] ==> Image generation successful
[2011-08-09 00:26] installed linux (3.0.1-1)
I don't think I've mentioned that my old menu.lst seems to have disappeared and so must have been on one of the partitions that were deleted. I did have 2 Arch installations when I was setting things up months ago and that menu.lst may have been on the other partition but pointing to this partiton's kernel for booting. Presumably that's possible since this partiton is definitely the one I have been using for the last several months (confirmed by log and other files updated in the last few days etc). Even so, I suppose that probably wouldn't be relevant to this issue, since grub is finding the menu.lst on this partition when it boots so it is looking in the intended place now.
It seems I'm at a bit of a dead end. It seems these kernel panics are usually because there is something wrong with the kernel - which there wasn't with mine (and presumably the kernel in the new linux package is fine) or there is a typo in menu.lst (I can't see one and nobody has pointed one out yet) or menu.lst is pointing to the wrong partition (mine is pointing to the same partition and /boot directory that is found by grub - which is where my boot image is located - so it seems to be correct). I have nevertheless tried editing the menu.lst entry when booting to boot from different partitions but so far that hasn't worked either.
If anybody has other ideas I'd really appreciate it.
If not, some suggestions on re-installing would also be appreciated. I have a recent tar archive of the partition, but presumably reinstalling that wouldn't be of much use since it would just put back what is currently there. I guess that I need to format the partition, create a separate boot partition, do a fresh install of Arch into the formatted partition (and with boot in the new boot partition). And then restore my tar backup (excluding the boot directory) into the formatted partition?
Any assistance greatly appreciated.
Thanks
belbo
Last edited by belbo (2011-08-08 23:17:49) -
[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). -
MacBook doesnt boot when wi-fi router is on.
Greetings.
Thats pretty weird but it is how it is. First time my mac refused to boot i was really confused: tried everything and it didnt help: i saw a loader on the screen but it didnt boot further. Then i decided to re-install Mac Os. Did it, but next time i turned my Mac off i wasnt able to boot it again.
A miracle solved the problem: occasionally i unplugged power supply from my wi-fi router (D-Link DI-524 that is. Latest firmware update installed. original Release:B), and voila my MacBook did a happy beep-beep and started to load a system. So as it is now my MacBook Doesnt boot when my router is on and it does boot if i turn router off.
My MacOsX 10.4.1 is freshly installed with all latest updates that i downloaded via "update software" thing. Did no tuning to it, almost no 3rd party software installed so far, apart from MS Office 2004. My question is pretty simple: How can i make my MacBook boot without unplugging power from my router (since its pretty weird to do it every time i turn my Mac on).
Any suggestions?
Thank you for your help.Could it just be stuck trying to join a Network, or mounting a Share of some kind?
Might try dragging these to the Desktop, reboot, and see if it works...
/Users/YourUserName/Library/Preferences/com.apple.internetconnect.plist
/Library/Preferences/SystemConfiguration/preferences.plist
/Library/Preferences/SystemConfiguration/com.apple.airport.preferences.plist
/Library/Preferences/com.apple.sharing.firewall.plist
Also any...
~/Library/Preferences/ByHost/com.apple.networkConnect.<12 digit number>.plist -
Laptop doesnt boot after installing a new hard drive
HP G60-630us laptop ...replaced hard drive ...installed 3 startup discs.. after you remove the last disc, when you hit continue it is supposed to boot up ...it reads no bootable device ......if you put the first disc in to boot up, you end up back where you started.....i changed the boot order & put hard drive first ...still doesnt boot up
This question was solved.
View Solution.Hi,
The image you download should just appear as 1 file. You should then use the 'Burn a disc image' option in Power2Go to write this correctly to a disc.
Regards,
DP-K
****Click the White thumb to say thanks****
****Please mark Accept As Solution if it solves your problem****
****I don't work for HP****
Microsoft MVP - Windows Experience -
[SOLVED] Unable to boot in UEFI System
For several days I have been trying to get Arch to boot on my desktop by following the Beginners' guide and refering to other Arch wiki articles as well as Arch Forum posts for any problems that I had. I have tried a few bootloaders such as GRUB, gummiboot, and rEFInd and they all give the same result when I attempt to boot - a blinking cursor with no menu and then it returns me to the BIOS;. My UEFI motherboard is the ASUS VI Hero. I have disabled secure boot and both fast boots. I use a live USB with UEFI that is able to boot on my system and was created with dd.
Below are the outputs of some commands that might be useful.
root@archiso ~ # lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 223.6G 0 disk
├─sda1 8:1 0 512M 0 part
├─sda2 8:2 0 4G 0 part
└─sda3 8:3 0 219.1G 0 part
sdb 8:16 0 931.5G 0 disk
├─sdb1 8:17 0 487.3M 0 part
└─sdb2 8:18 0 931G 0 part
sdc 8:32 0 232.9G 0 disk
├─sdc1 8:33 0 100M 0 part
└─sdc2 8:34 0 232.8G 0 part
sdd 8:48 1 3.8G 0 disk
├─sdd1 8:49 1 595M 0 part /run/archiso/bootmnt
└─sdd2 8:50 1 31M 0 part
loop0 7:0 0 256.8M 1 loop /run/archiso/sfs/airootfs
loop1 7:1 0 32G 1 loop
└─arch_airootfs 254:0 0 32G 0 dm /
loop2 7:2 0 256M 0 loop
└─arch_airootfs 254:0 0 32G 0 dm /
Windows 7 is on sdc and Arch is on sda (sdb is an extra storage device for Windows). Both sdc and sda are SDDs.
root@archiso ~ # parted /dev/sda print
Model: ATA SanDisk SDSSDHII (scsi)
Disk /dev/sda: 240GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 538MB 537MB fat32 boot, esp
2 538MB 4833MB 4295MB linux-swap(v1)
3 4833MB 240GB 235GB ext4
root@archiso ~ # cat /mnt/etc/fstab
# UUID=0dff590b-24f1-47a2-870e-3f4d2c5bcb6a
/dev/sda3 / ext4 rw,relatime,data=ordered,discard 0 1
# UUID=FA3A-728C
/dev/sda1 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
# UUID=524e2980-d1e6-4948-88f9-c193682d5a9e
/dev/sda2 none swap defaults 0 0
# efibootmgr
BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0000,0001,0002,0003
Boot0000* grub
Boot0001* Hard Drive
Boot0002* ubuntu
Boot0003* UEFI: General USB Flash Disk
Boot0008 Hard Drive
Ignore ubuntu, that was on my HDD from before but has been removed. The grub option usually disappears after reboot unless I run efibootmgr -O after I install the bootloader. Using efibootmgr -v option, the output is a bit hard to read.
# efibootmgr -v
BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0000,0001,0002,0003
Boot0000* grub HD(1,800,100000,f9c04628-178b-4c94-9b92-62c04f2a5151)File(\EFI\grub\grubx64.efi)
Boot0001* Hard Drive BIOS(2,0,00)..GO..NO........u.W.D.C. .W.D.1.0.E.Z.E.X.-.0.8.M.2.N.A.0....................A.................................>..Gd-.;.A..MQ..L. . . . .W. .-.D.M.W.3.C.1.F.6.4.5.0.4.6........BO..NO........u.S.a.m.s.u.n.g. .S.S.D. .8.4.0. .E.V.O. .2.5.0.G.B....................A.................................>..Gd-.;.A..MQ..L.1.S.B.D.S.N.F.A.7.1.3.0.7.5. .L. . . . ........BO..NO........o.S.a.n.D.i.s.k. .S.D.S.S.D.H.I.I.2.4.0.G....................A...........................>..Gd-.;.A..MQ..L.4.1.3.4.3.7.0.4.7.0.2.0. . . . . . . . ........BO..NO........u.G.e.n.e.r.a.l. .U.S.B. .F.l.a.s.h. .D.i.s.k....................A.............................B..Gd-.;.A..MQ..L.G.e.n.e.r.a.l. .U.S.B. .F.l.a.s.h. .D.i.s.k........BO
Boot0002* ubuntu HD(1,800,f3a9e,3eaa3162-6352-4ad8-a725-89c738f2b3ad)File(\EFI\Ubuntu\grubx64.efi)
Boot0003* UEFI: General USB Flash Disk ACPI(a0341d0,0)PCI(1d,0)USB(1,0)USB(1,0)HD(1,fc,f800,612a5c68)..BO
Boot0008 Hard Drive BIOS(2,0,00)..GO..NO........o.S.a.n.D.i.s.k. .S.D.S.S.D.H.I.I.2.4.0.G....................A...........................>..Gd-.;.A..MQ..L.4.1.3.4.3.7.0.4.7.0.2.0. . . . . . . . ........BO..NO........u.W.D.C. .W.D.1.0.E.Z.E.X.-.0.8.M.2.N.A.0....................A.................................>..Gd-.;.A..MQ..L. . . . .W. .-.D.M.W.3.C.1.F.6.4.5.0.4.6........BO..NO........u.S.a.m.s.u.n.g. .S.S.D. .8.4.0. .E.V.O. .2.5.0.G.B....................A.................................>..Gd-.;.A..MQ..L.1.S.B.D.S.N.F.A.7.1.3.0.7.5. .L. . . . ........BO..NO........o.G.e.n.e.r.a.l. .U.S.B. .F.l.a.s.h. .D.i.s.k....................A.......................B..Gd-.;.A..MQ..L.G.e.n.e.r.a.l. .U.S.B. .F.l.a.s.h. .D.i.s.k........BO
I mount /dev/sda3 to /mnt and /dev/sda1 to /mnt/boot before I arch-chroot and when I tried grub, I installed with:
# grub-install --target=x86_64-efi --efi-directory=/boot--bootloader-id=grub --recheck
No errors are reported. I then make a config file for grub with:
# grub-mkconfig -o /boot/grub/grub.cfg
Last edited by DetotatedWam (2015-04-01 22:12:06)Boot\ Secure Boot menu >
Secure Boot state: Disabled
Platform Key (PK) state: Unloaded
OS Type: Windows UEFI mode
I have tried setting "OS Type" to "Other OS" before but that doesn't change anything. I just tried it again and the BIOS freezes upon "Save Changes & Reset".
Boot\ Secure Boot menu\ Key Management >
PK Management: Unloaded
KEK Management: Unloaded
DB Management: Unloaded
DBX Management: Unloaded
The other day, I deleted all of them and backed them up on a USB in order to disable secure boot.
Note: After looking at this menu again I am noticing options to append from file for KEK, DB, and DBX that might help.
Append KEK from File
Allows you to load the additional
KEK from a storage device for an
additional db and dbx loaded
management.
[Yes]
Load the default KEK
[No]
Load from a USB storage device
Append db from File
Allows you to load the additional db
variable from a storage device so
that more custom signed UEFI
executble files can be loaded.
*UEFI executabled files include UEFI
boot loaders, drivers and
applications.
[Yes]
Load the default db
[No]
Load from a USB storage device
Append dbx from File
Allows you to load the additional
dbx variable from a storage device
so that more custom signed UEFI
executble files cannot be loaded.
*UEFI executabled files include UEFI
boot loaders, drivers and
applications.
[Yes]
Load the default dbx
[No]
Load from a USB storage device
Boot\ CSM (Compatibility Support Module)
Launch CSM: Enabled
Boot Device Control: UEFI and Legacy OPROM
Boot from Network Devices: Legacy OPROM first
Boot from Storage Devices: Both, UEFI first
Boot from PCI-E/PCI Expansion Devices: Legacy OPROM first
As a side note: After a reboot, I noticed the Arch boot option disappeared again.
Head_on_a_Stick wrote:Have you managed to boot any other distributions that are not compatible with Secure Boot?
I have been able to boot Windows 7 and ubuntu but I beleive both are compatible with Secure Boot so, no.
Head_on_a_Stick wrote:The Arch live ISO has the EFI applications PreLoader.efi & HashTool.efi included so that will boot up with Secure Boot enabled.
I will try this and post the results.
Edit: Now my BIOS Freezes everytime I try to save & exit.
Last edited by DetotatedWam (2015-04-01 19:59:18) -
[SOLVED] Can't boot Windows 8 using grub2. invalid EFI file path
English is not my native language. Please excuse typing errors.
I have just successfully installed Arch linux with grub2 as its boot manager. I
followed the arch beginner guide. I've used grub before and I'm familiar with
it, so chose to use grub instead for efistub. I installed os-prober and
ran grub-mkconfig to create the grub.cfg file. The problem now is that I recieve
an error when I try to boot windows 8. I have two drives (/dev/sda and /dev/sdb)
and I believe both are EFI-systems.
However, it's not very important for me to use grub, so if booting into windows
8 is easier using efistub, I will try that.
The computer is ASUS ux32vd with a hybrid disk with 25GB on the SSD and 500GB on
the hard drive. I believe the SSD part is used by Windows.
This is the first error I recieved when I tried to boot windows.
error: can't find command `drivemap'.
error: invalid EFI file path.
Press any key to continue...
Then I tried to follow this post
https://bbs.archlinux.org/viewtopic.php?id=150183 and made a new boot
entry "Windows 82". And I got a new error:
error: unspecified search type.
error: file '/EFI/Microsoft/Boot/bootmgfw.efi' not found
Press any key to continue...
Here are some command line outputs.
~ ᐅ sudo blkid
/dev/sdb1: PARTLABEL="HFS" PARTUUID="4613ee39-4727-4347-8134-173f590f716f"
/dev/sdb2: LABEL="INTELRST" UUID="BA5E-7431" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="304f2630-89b2-4632-a566-e8c6db9df3a9"
/dev/sda1: LABEL="SYSTEM" UUID="90FA-5332" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="5a60fff2-384a-4168-ad7b-7ba25c03c910"
/dev/sda2: LABEL="Recovery" UUID="ECE43E9AE43E674C" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="5da02b32-607a-4c63-88ef-00499bd6e05c"
/dev/sda3: PARTLABEL="Microsoft reserved partition" PARTUUID="6c501a91-71a5-45d8-a9ee-2e2a1c427258"
/dev/sda4: LABEL="OS" UUID="DE4241E84241C5CD" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="6e182189-b0e3-479a-ac74-8e69452d7c66"
/dev/sda5: LABEL="DATA" UUID="B05448EC5448B6BE" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="be7e04ac-fb01-44fd-9571-e0b001652322"
/dev/sda6: LABEL="Restore" UUID="B8D84520D844DDEE" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="4d42c26d-2c85-4ebf-88ec-7a83a4814a61"
/dev/sda7: LABEL="ROOT" UUID="0d63036d-b624-4596-a296-1db457c068d5" TYPE="ext4" PARTUUID="707f4bca-18b4-4340-838f-ec3a39e9338a"
/dev/sda8: UUID="bcaa2c5f-150d-47c9-9a58-9a7b7ec7bed2" TYPE="swap" PARTUUID="1da43668-418c-4883-810b-e1c3dee75e61"
~ ᐅ sudo lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 300M 0 part /boot/efi
├─sda2 8:2 0 600M 0 part
├─sda3 8:3 0 128M 0 part
├─sda4 8:4 0 186.3G 0 part /mnt/windows
├─sda5 8:5 0 190.1G 0 part /mnt/data
├─sda6 8:6 0 20G 0 part
├─sda7 8:7 0 66.5G 0 part /
└─sda8 8:8 0 1.9G 0 part
sdb 8:16 0 22.4G 0 disk
├─sdb1 8:17 0 18.4G 0 part
└─sdb2 8:18 0 4G 0 part
~ ᐅ sudo 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
set default="0"
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,gpt7'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt7 --hint-efi=hd0,gpt7 --hint-baremetal=ahci0,gpt7 0d63036d-b624-4596-a296-1db457c068d5
else
search --no-floppy --fs-uuid --set=root 0d63036d-b624-4596-a296-1db457c068d5
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
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-0d63036d-b624-4596-a296-1db457c068d5' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
set root='hd0,gpt7'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt7 --hint-efi=hd0,gpt7 --hint-baremetal=ahci0,gpt7 0d63036d-b624-4596-a296-1db457c068d5
else
search --no-floppy --fs-uuid --set=root 0d63036d-b624-4596-a296-1db457c068d5
fi
echo 'Loading Linux core repo kernel ...'
linux /boot/vmlinuz-linux root=UUID=0d63036d-b624-4596-a296-1db457c068d5 ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/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-0d63036d-b624-4596-a296-1db457c068d5' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
set root='hd0,gpt7'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt7 --hint-efi=hd0,gpt7 --hint-baremetal=ahci0,gpt7 0d63036d-b624-4596-a296-1db457c068d5
else
search --no-floppy --fs-uuid --set=root 0d63036d-b624-4596-a296-1db457c068d5
fi
echo 'Loading Linux core repo kernel ...'
linux /boot/vmlinuz-linux root=UUID=0d63036d-b624-4596-a296-1db457c068d5 ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/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/20_memtest86+ ###
### END /etc/grub.d/20_memtest86+ ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows Recovery Environment (loader) (on /dev/sda2)' --class windows --class os $menuentry_id_option 'osprober-chain-ECE43E9AE43E674C' {
insmod part_gpt
insmod ntfs
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 ECE43E9AE43E674C
else
search --no-floppy --fs-uuid --set=root ECE43E9AE43E674C
fi
drivemap -s (hd0) ${root}
chainloader +1
menuentry 'Windows 8 (loader) (on /dev/sda4)' --class windows --class os $menuentry_id_option 'osprober-chain-DE4241E84241C5CD' {
insmod part_gpt
insmod ntfs
set root='hd0,gpt4'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt4 --hint-efi=hd0,gpt4 --hint-baremetal=ahci0,gpt4 DE4241E84241C5CD
else
search --no-floppy --fs-uuid --set=root DE4241E84241C5CD
fi
drivemap -s (hd0) ${root}
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.
#menuentry "Microsoft Windows 8 x86_64 UEFI-GPT NTFS" {
#insmod part_gpt
#insmod ntfs
#insmod search_fs_uuid
#insmod chain
#search --fs-uuid --set=root --hint-bios=hd0,gpt4 --hint-efi=hd0,gpt4 --hint-baremetal=ahci0,gpt4 DE4241E84241C5CD
#chainloader /EFI/Microsoft/Boot/bootmgfw.efi
menuentry "Windows 8" {
insmod part_gpt
insmod fat
insmod search_fs_uuid
insmod chain
search --no-floppy --fs--uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 90FA-5332
chainloader /EFI/Microsoft/Boot/bootmgfw.efi
menuentry "Windows 8-2" --class windows --class os $menuentry_id_option 'osprober-chain-ECE43E9AE43E674C' {
insmod part_gpt
insmod fat
insmod search_fs_uuid
insmod chain
search --no-floppy --fs--uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 90FA-5332
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 ###
~ ᐅ sudo grub-probe --target=fs_uuid /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi
90FA-5332
~ ᐅ sudo grub-probe --target=hints_string /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi
--hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1
bootinitscript
Boot Info Script 0.61 [1 April 2012]
============================= Boot Info Summary: ===============================
=> No boot loader is installed in the MBR of /dev/sda.
=> No boot loader is installed in the MBR of /dev/sdb.
sda1: __________________________________________________________________________
File system: vfat
Boot sector type: Unknown
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /efi/arch-grub/grubx64.efi /efi/Boot/bkpbootx64.efi
/efi/Boot/bootx64.efi /efi/ubuntu/grubx64.efi
sda2: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /bootmgr /Boot/BCD
sda3: __________________________________________________________________________
File system:
Boot sector type: -
Boot sector info:
Mounting failed: mount: unknown filesystem type ''
sda4: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /bootmgr /Boot/BCD /Windows/System32/winload.exe
sda5: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
sda6: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
sda7: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Arch Linux ()
Boot files: /boot/grub/grub.cfg /etc/fstab
sda8: __________________________________________________________________________
File system: swap
Boot sector type: -
Boot sector info:
sdb1: __________________________________________________________________________
File system:
Boot sector type: -
Boot sector info:
Mounting failed: mount: unknown filesystem type ''
mount: unknown filesystem type ''
sdb2: __________________________________________________________________________
File system: vfat
Boot sector type: Unknown
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
============================ Drive/Partition Info: =============================
Drive: sda _____________________________________________________________________
Disk /dev/sda: 500.1 GB, 500107862016 bytes, 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Partition Boot Start Sector End Sector # of Sectors Id System
/dev/sda1 1 976,773,167 976,773,167 ee GPT
GUID Partition Table detected.
Partition Start Sector End Sector # of Sectors System
/dev/sda1 2,048 616,447 614,400 EFI System partition
/dev/sda2 616,448 1,845,247 1,228,800 Windows Recovery Environment (Windows)
/dev/sda3 1,845,248 2,107,391 262,144 Microsoft Reserved Partition (Windows)
/dev/sda4 2,107,392 392,816,639 390,709,248 Data partition (Windows/Linux)
/dev/sda5 392,816,640 791,449,599 398,632,960 Data partition (Windows/Linux)
/dev/sda6 934,809,600 976,773,119 41,963,520 Windows Recovery Environment (Windows)
/dev/sda7 791,449,600 930,902,015 139,452,416 Data partition (Windows/Linux)
/dev/sda8 930,902,016 934,809,599 3,907,584 Swap partition (Linux)
Drive: sdb _____________________________________________________________________
Disk /dev/sdb: 24.0 GB, 24015495168 bytes, 46905264 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
Partition Boot Start Sector End Sector # of Sectors Id System
/dev/sdb1 1 4,294,967,295 4,294,967,295 ee GPT
/dev/sdb1 ends after the last sector of /dev/sdb
GUID Partition Table detected.
Partition Start Sector End Sector # of Sectors System
/dev/sdb1 8,392,704 46,903,295 38,510,592 -
/dev/sdb2 2,048 8,390,655 8,388,608 -
"blkid" output: ________________________________________________________________
Device UUID TYPE LABEL
/dev/sda1 90FA-5332 vfat SYSTEM
/dev/sda2 ECE43E9AE43E674C ntfs Recovery
/dev/sda3
/dev/sda4 DE4241E84241C5CD ntfs OS
/dev/sda5 B05448EC5448B6BE ntfs DATA
/dev/sda6 B8D84520D844DDEE ntfs Restore
/dev/sda7 0d63036d-b624-4596-a296-1db457c068d5 ext4 ROOT
/dev/sda8 bcaa2c5f-150d-47c9-9a58-9a7b7ec7bed2 swap
/dev/sdb1
/dev/sdb2 BA5E-7431 vfat INTELRST
================================ Mount points: =================================
Device Mount_Point Type Options
/dev/sda1 /boot/efi vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/sda4 /mnt/windows fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
/dev/sda5 /mnt/data fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
/dev/sda7 / ext4 (rw,relatime,commit=600,data=ordered)
=========================== sda7/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
set default="0"
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,gpt7'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt7 --hint-efi=hd0,gpt7 --hint-baremetal=ahci0,gpt7 0d63036d-b624-4596-a296-1db457c068d5
else
search --no-floppy --fs-uuid --set=root 0d63036d-b624-4596-a296-1db457c068d5
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
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-0d63036d-b624-4596-a296-1db457c068d5' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
set root='hd0,gpt7'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt7 --hint-efi=hd0,gpt7 --hint-baremetal=ahci0,gpt7 0d63036d-b624-4596-a296-1db457c068d5
else
search --no-floppy --fs-uuid --set=root 0d63036d-b624-4596-a296-1db457c068d5
fi
echo 'Loading Linux core repo kernel ...'
linux /boot/vmlinuz-linux root=UUID=0d63036d-b624-4596-a296-1db457c068d5 ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/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-0d63036d-b624-4596-a296-1db457c068d5' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
set root='hd0,gpt7'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt7 --hint-efi=hd0,gpt7 --hint-baremetal=ahci0,gpt7 0d63036d-b624-4596-a296-1db457c068d5
else
search --no-floppy --fs-uuid --set=root 0d63036d-b624-4596-a296-1db457c068d5
fi
echo 'Loading Linux core repo kernel ...'
linux /boot/vmlinuz-linux root=UUID=0d63036d-b624-4596-a296-1db457c068d5 ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/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/20_memtest86+ ###
### END /etc/grub.d/20_memtest86+ ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows Recovery Environment (loader) (on /dev/sda2)' --class windows --class os $menuentry_id_option 'osprober-chain-ECE43E9AE43E674C' {
insmod part_gpt
insmod ntfs
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 ECE43E9AE43E674C
else
search --no-floppy --fs-uuid --set=root ECE43E9AE43E674C
fi
drivemap -s (hd0) ${root}
chainloader +1
menuentry 'Windows 8 (loader) (on /dev/sda4)' --class windows --class os $menuentry_id_option 'osprober-chain-DE4241E84241C5CD' {
insmod part_gpt
insmod ntfs
set root='hd0,gpt4'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt4 --hint-efi=hd0,gpt4 --hint-baremetal=ahci0,gpt4 DE4241E84241C5CD
else
search --no-floppy --fs-uuid --set=root DE4241E84241C5CD
fi
drivemap -s (hd0) ${root}
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.
menuentry "Windows 8" {
insmod part_gpt
insmod fat
insmod search_fs_uuid
insmod chain
search --no-floppy --fs--uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 90FA-5332
chainloader /EFI/Microsoft/Boot/bootmgfw.efi
menuentry 'Windows 82' --class windows --class os $menuentry_id_option 'osprober-chain-ECE43E9AE43E674C' {
insmod part_gpt
insmod fat
insmod search_fs_uuid
insmod chain
search --no-floppy --fs--uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 90FA-5332
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 ###
=============================== sda7/etc/fstab: ================================
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda7 LABEL=ROOT
UUID=0d63036d-b624-4596-a296-1db457c068d5 / ext4 rw,relatime,data=ordered 0 1
# /dev/sda1 LABEL=SYSTEM
UUID=90FA-5332 /boot/efi vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
LABEL=DATA /mnt/data ntfs-3g uid=sighol,gid=users,dmask=022,fmask=133 0 0
LABEL=OS /mnt/windows ntfs-3g uid=sighol,gid=users,dmask=022,fmask=133 0 0
=================== sda7: Location of files loaded by Grub: ====================
GiB - GB File Fragment(s)
======================== Unknown MBRs/Boot Sectors/etc: ========================
Unknown GPT Partiton Type
5850cbb887c11947baf0379ca2d4c97e
Unknown GPT Partiton Type
dee2bfd3af3ddf11ba40e3a556d89593
Unknown BootLoader on sda1
00000000 eb 58 90 4d 53 44 4f 53 35 2e 30 00 02 08 5e 1b |.X.MSDOS5.0...^.|
00000010 02 00 00 00 00 f8 00 00 3f 00 ff 00 00 08 00 00 |........?.......|
00000020 00 60 09 00 51 02 00 00 00 00 00 00 02 00 00 00 |.`..Q...........|
00000030 01 00 06 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000040 80 01 29 32 53 fa 90 4e 4f 20 4e 41 4d 45 20 20 |..)2S..NO NAME |
00000050 20 20 46 41 54 33 32 20 20 20 33 c9 8e d1 bc f4 | FAT32 3.....|
00000060 7b 8e c1 8e d9 bd 00 7c 88 56 40 88 4e 02 8a 56 |{......|[email protected]|
00000070 40 b4 41 bb aa 55 cd 13 72 10 81 fb 55 aa 75 0a |@.A..U..r...U.u.|
00000080 f6 c1 01 74 05 fe 46 02 eb 2d 8a 56 40 b4 08 cd |...t..F..-.V@...|
00000090 13 73 05 b9 ff ff 8a f1 66 0f b6 c6 40 66 0f b6 |.s......f...@f..|
000000a0 d1 80 e2 3f f7 e2 86 cd c0 ed 06 41 66 0f b7 c9 |...?.......Af...|
000000b0 66 f7 e1 66 89 46 f8 83 7e 16 00 75 39 83 7e 2a |f..f.F..~..u9.~*|
000000c0 00 77 33 66 8b 46 1c 66 83 c0 0c bb 00 80 b9 01 |.w3f.F.f........|
000000d0 00 e8 2c 00 e9 a8 03 a1 f8 7d 80 c4 7c 8b f0 ac |..,......}..|...|
000000e0 84 c0 74 17 3c ff 74 09 b4 0e bb 07 00 cd 10 eb |..t.<.t.........|
000000f0 ee a1 fa 7d eb e4 a1 7d 80 eb df 98 cd 16 cd 19 |...}...}........|
00000100 66 60 80 7e 02 00 0f 84 20 00 66 6a 00 66 50 06 |f`.~.... .fj.fP.|
00000110 53 66 68 10 00 01 00 b4 42 8a 56 40 8b f4 cd 13 |Sfh.....B.V@....|
00000120 66 58 66 58 66 58 66 58 eb 33 66 3b 46 f8 72 03 |fXfXfXfX.3f;F.r.|
00000130 f9 eb 2a 66 33 d2 66 0f b7 4e 18 66 f7 f1 fe c2 |..*f3.f..N.f....|
00000140 8a ca 66 8b d0 66 c1 ea 10 f7 76 1a 86 d6 8a 56 |..f..f....v....V|
00000150 40 8a e8 c0 e4 06 0a cc b8 01 02 cd 13 66 61 0f |@............fa.|
00000160 82 74 ff 81 c3 00 02 66 40 49 75 94 c3 42 4f 4f |[email protected]|
00000170 54 4d 47 52 20 20 20 20 00 00 00 00 00 00 00 00 |TMGR ........|
00000180 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
000001a0 00 00 00 00 00 00 00 00 00 00 00 00 0d 0a 44 69 |..............Di|
000001b0 73 6b 20 65 72 72 6f 72 ff 0d 0a 50 72 65 73 73 |sk error...Press|
000001c0 20 61 6e 79 20 6b 65 79 20 74 6f 20 72 65 73 74 | any key to rest|
000001d0 61 72 74 0d 0a 00 00 00 00 00 00 00 00 00 00 00 |art.............|
000001e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
000001f0 00 00 00 00 00 00 00 00 ac 01 b9 01 00 00 55 aa |..............U.|
00000200
Unknown BootLoader on sdb2
00000000 eb 58 90 4d 53 44 4f 53 35 2e 30 00 02 08 2e 20 |.X.MSDOS5.0.... |
00000010 02 00 00 00 00 f8 00 00 3f 00 ff 00 00 08 00 00 |........?.......|
00000020 00 00 80 00 e9 1f 00 00 00 00 00 00 02 00 00 00 |................|
00000030 01 00 06 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000040 80 00 29 31 74 5e ba 4e 4f 20 4e 41 4d 45 20 20 |..)1t^.NO NAME |
00000050 20 20 46 41 54 33 32 20 20 20 33 c9 8e d1 bc f4 | FAT32 3.....|
00000060 7b 8e c1 8e d9 bd 00 7c 88 56 40 88 4e 02 8a 56 |{......|[email protected]|
00000070 40 b4 41 bb aa 55 cd 13 72 10 81 fb 55 aa 75 0a |@.A..U..r...U.u.|
00000080 f6 c1 01 74 05 fe 46 02 eb 2d 8a 56 40 b4 08 cd |...t..F..-.V@...|
00000090 13 73 05 b9 ff ff 8a f1 66 0f b6 c6 40 66 0f b6 |.s......f...@f..|
000000a0 d1 80 e2 3f f7 e2 86 cd c0 ed 06 41 66 0f b7 c9 |...?.......Af...|
000000b0 66 f7 e1 66 89 46 f8 83 7e 16 00 75 39 83 7e 2a |f..f.F..~..u9.~*|
000000c0 00 77 33 66 8b 46 1c 66 83 c0 0c bb 00 80 b9 01 |.w3f.F.f........|
000000d0 00 e8 2c 00 e9 a8 03 a1 f8 7d 80 c4 7c 8b f0 ac |..,......}..|...|
000000e0 84 c0 74 17 3c ff 74 09 b4 0e bb 07 00 cd 10 eb |..t.<.t.........|
000000f0 ee a1 fa 7d eb e4 a1 7d 80 eb df 98 cd 16 cd 19 |...}...}........|
00000100 66 60 80 7e 02 00 0f 84 20 00 66 6a 00 66 50 06 |f`.~.... .fj.fP.|
00000110 53 66 68 10 00 01 00 b4 42 8a 56 40 8b f4 cd 13 |Sfh.....B.V@....|
00000120 66 58 66 58 66 58 66 58 eb 33 66 3b 46 f8 72 03 |fXfXfXfX.3f;F.r.|
00000130 f9 eb 2a 66 33 d2 66 0f b7 4e 18 66 f7 f1 fe c2 |..*f3.f..N.f....|
00000140 8a ca 66 8b d0 66 c1 ea 10 f7 76 1a 86 d6 8a 56 |..f..f....v....V|
00000150 40 8a e8 c0 e4 06 0a cc b8 01 02 cd 13 66 61 0f |@............fa.|
00000160 82 74 ff 81 c3 00 02 66 40 49 75 94 c3 42 4f 4f |[email protected]|
00000170 54 4d 47 52 20 20 20 20 00 00 00 00 00 00 00 00 |TMGR ........|
00000180 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
000001a0 00 00 00 00 00 00 00 00 00 00 00 00 0d 0a 44 69 |..............Di|
000001b0 73 6b 20 65 72 72 6f 72 ff 0d 0a 50 72 65 73 73 |sk error...Press|
000001c0 20 61 6e 79 20 6b 65 79 20 74 6f 20 72 65 73 74 | any key to rest|
000001d0 61 72 74 0d 0a 00 00 00 00 00 00 00 00 00 00 00 |art.............|
000001e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
000001f0 00 00 00 00 00 00 00 00 ac 01 b9 01 00 00 55 aa |..............U.|
00000200
========= Devices which don't seem to have a corresponding hard drive: =========
sdc {
=============================== StdErr Messages: ===============================
cat: /tmp/BootInfo-wSbit3X4/Tmp_Log: No such file or directory
/dev/sdc: open failed: No medium found
No volume groups found
mdadm: No arrays found in config file or automatically
EDIT:
I gave up trying to make grub work, so I uninstalled grub and deleted all the grub files I could find.
# pacrem grub-efi-x86_64
# rm -fr /boot/grub
That last one I came to regret later on. So I installed rEFInd using the archlinux beginners guide. When I then tried to boot into windows It told me that /boot/grub/x86_64-efi/normal.mod was not found. I then reinstalled grub-efi-x86_64 and copied /usr/lib/grub/x86_64 to /boot/grub. Now everything works fine.
Last edited by sighol (2013-06-08 21:47:49)sighol wrote:However, it's not very important for me to use grub, so if booting into windows
8 is easier using efistub, I will try that.
The EFI stub loader is a Linux-only boot loader; however, it is possible to use the EFI stub loader in conjunction with a separate boot manager, such as rEFInd or gummiboot. In such a configuration, you'd use the boot manager to select the OS to boot (Windows or Linux, and possibly the specific Linux kernel), and the boot loader (the Windows loader or the EFI stub loader built into a specific kernel) will then take over booting the OS. In Arch, this is often easier to configure than is GRUB, since GRUB is very complex and its automated tools to help with setting things up often get it wrong.
This is the first error I recieved when I tried to boot windows.
error: can't find command `drivemap'.
error: invalid EFI file path.
Press any key to continue...
The "drivemap" command in GRUB is generally used when booting a BIOS-mode boot loader, and in fact your "Windows Recovery Environment (loader) (on /dev/sda2)" and "Windows 8 (loader) (on /dev/sda4)" GRUB entries are both built as for BIOS-mode Windows installations -- but the fact that your disks both use GPT means that Windows won't boot in BIOS mode on your computer. (This is one of the many things that the GRUB setup scripts can get wrong.)
Then I tried to follow this post
https://bbs.archlinux.org/viewtopic.php?id=150183 and made a new boot
entry "Windows 82". And I got a new error:
error: unspecified search type.
error: file '/EFI/Microsoft/Boot/bootmgfw.efi' not found
Press any key to continue...
Both your "Windows 8" and "Windows 82" entries refer to an EFI boot loader file called EFI/Microsoft/Boot/bootmgfw.efi on your EFI System Partition (ESP). This should be correct, but your Boot Info Script output doesn't show any evidence of such a file. Sometimes Boot Info Script misses such things, so you may want to check it just to be sure. Your ESP is /dev/sda1, and it looks like it's being mounted at /boot/efi by default, so check for the /boot/efi/EFI/Microsoft directory tree, and for /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi in particular. If that file isn't present, then something is wrong -- perhaps you mistakenly erased the ESP when you installed Linux, thus wiping out the Windows boot loader; or perhaps the file was accidentally deleted somewhere along the way. (Note that on FAT, which the ESP uses, case is irrelevant, and in fact case varies between the filenames reported by Boot Info Script and what's recorded in your configuration files.)
You do have another boot loader file that may be a duplicate of the Windows boot loader: EFI/BOOT/bkpbootx64.efi. This filename is generally created by Ubuntu's "Boot Repair" tool, which IMHO can do as much harm as good, especially on a system that's not booting Ubuntu. If you ran this tool, though, it's conceivable that bkpbootx64.efi is a copy of the Windows boot loader, so copying it to EFI/Microsoft/Boot/bootmgfw.efi might get things working. OTOH, the Windows boot loader relies on other files to do its job, so if they're not present, copying the Windows boot loader to its original location won't be sufficient.
If you can't get things working based on the preceding suggestions, I recommend you run a Windows repair tool. These are accessible from a Windows recovery disc. Such disc images are readily available on the Internet, but I don't happen to have any links handy. Try Microsoft's own site; images obtained from random third-party sites might contain malware. Once you've done this, chances are the computer will boot directly into Windows. You'll then need to either restore GRUB as the default boot loader or install another boot loader or boot manager. You can use the Windows "bcdedit" command to do the former, as in:
bcdedit /set {bootmgr} path \EFI\arch-grub\grubx64.efi
You'll need to type this from an Administrator Command Prompt window. -
[SOLVED] Two Grub boot menus on Macbook pro 7.1 efi boot
Hello
This is my first Arch post and I feel a bit of a fool for making the error I'm going to describe but here we go....
A couple of weeks ago I installed Arch as dual boot on my Macbook pro 7.1 and I'm generally quite happy with the result. I boot as EFI using Grub2 having followed instructions to make a standalone boot.efi and boot from the mac's bootloader. The boot.efi file is placed on a small macosx journaled partition that has been made bootable with "bless". I've been able to boot between the two systems using 'alt' at startup or, more generally, just leave the pc to boot into Arch.
When I generated the boot.cfg file I didn't specify ro or rw but grub added ro. So I've had the "root mounted as ro" warning since upgrading to 3.10.3-1 (I don't subscribe to the testing repository) although it was obviously an issue from the start and I was aware of it. After reading some of the forum posts today I thought I'd have a go at changing the boot parameters at startup and edit the boot menu to include rw. This worked and I didn't get the read only warning. I decided to try to generate a new grub.fcg and specify rw before generating a new boot.efi. On inspecting the new boot.cfg I noticed it had both ro and rw entries. I decided to think about what to do (thinking of removing the ro) before making the standalone file.
Anyway, I had to boot into osx for something else but when doing so noticed that I now have 3 efi boot options in the mac bootmanager. Two are grub and one boots osx. I've had a look in the forums and on the internet in general but can't find out how to remove the second entry. My guess is I've installed grub on my Arch /boot partition but can't figure out how to remove it.
Although I can boot into Arch as normal as the pc defaults to the original grub menu, I'd like to remove the additional entry if possible and would be grateful for any help.
Dylan
Last edited by youngdm (2013-08-06 21:00:37)These are the instructions I followed
grub-mkconfig -o boot/grub/grub.cfg grub-mkstandalone -o boot.efi -d usr/lib/grub/x86_64-efi -O x86_64-efi -C xz boot/grub/grub.cfg
Then in osx:
sudo bless --device /dev/disk0s4 --setBoot
I think that on initial installation I ran the command above as one and then last night ran it as two. Like this:
grub-mkconfig -o boot/grub/grub.cfg
grub-mkstandalone -o boot.efi -d usr/lib/grub/x86_64-efi -O x86_64-efi -C xz boot/grub/grub.cfg
The instructions were from:
http://codylittlewood.com/arch-linux-on … tallation/
From the apple discussion forums..
This one is a bit more tricky, surely there is another way but this one is simple and not so risky
1- burn a GParted Live CD iso
2- boot on the GParted live CD (press alt on boot and wait for the CD boot option to appear) and choose the first boot entry
3- during the boot process accept every option with its default value
4- in GParted select the EFI partition and somewhere in the menus select the "flags" entry and uncheck "boot"
5- exit GParted Live CD and boot in Mac OS
6- a new volume has appeared "/volumes/efi"
in the finder go to "/volumes/efi/EFI" and delete the "ubuntu" folder
7- repeat steps 2/3 and step 4 but check "boot" instead of unchecking it
8- exit GParted live CD and reboot
I have found the instructions above on the apple discussion forums but as noted above I'm a little wary about following them. I guess though that I need to remove the entry in the mac EFI partition which is hidden in osx but shows as sda1 in Arch.
Do you think I could mount sda1 in Arch and have a look at what's on there? From the instructions above it looks like there should be a directory for Arch that could be deleted. I presume that Arch is booting from the blessed partition on sda4. Is this correct?
Last edited by youngdm (2013-08-06 11:46:09) -
Nokia booklet doesnt boot and no bios
hi
Ive bought a new booklet and installed all the updates. While surfing on the internet i suddenly wasnt able to use the keyboard or the touchpad. I wanted to restart but the power button didnt react too. So i took the battery out of the booklet.
But now it doesnt boot and theres a black screen. I cann hear the fan but after a few minutes the booklet turns off aggain. What can i do???There is no fan, but what you hear might be the hard disk. BTW, does the Booklet/BIOS really not offer an option to boot from SD cards (which has been a common feature for ages on many notebooks featuring such readers), or do they just need to be formatted in some particular/peculiar way? I did see an "Operating System not found" error message when waking up from hibernation while an SD card was plugged in, so under some circumstances it DOES seem to try (and give preference over the hard disk).
-
[SOLVED] USB installation, booting: root fs cannot be detected
I followed this guide: http://wiki.archlinux.org/index.php/Ins … _a_USB_key
SYMPTOMS
I installed arch linux on a USB stick.
I can see Grub, I can boot. After the HOOKS get loaded (udev is loaded as well: Loading udev...done.) I get errors as follows:
Attempting to create root device '/dev/disk/by-uuid/myHdUUID'
unknown
ERROR: root fs cannot be detected. Try using rootfstype= kernel parameter.
If the device '/dev/disk/by-uuid/myHdUUID' gets created while you are here, try adding 'rootdelay=8' or higher to the kernel command-line...
Then I get a prompt that doesn't even let me issue the command "ls" (error: /bin/bash: ls: not found
SOLUTION: use the fallback image, or better, rebuild your mkinitcpio kernel image, see: Configuring mkinitcpio
My problem was that "usb" was not included in the HOOKS, it was present, yes but after the "autodetect".
So, in the /etc/mkinitcpio.conf place "usb" before "autodetect", e.g. as follows:
HOOKS="base udev autodetect sata filesystems"
then regenerate the image (refer to the previous link to understand why the autodetect was creating the problems and to see exactly how to regenerate the image)
Last edited by firepol (2008-10-09 19:18:34)Same problem, seems the new kernel broke UUID.
@tim: as I stated above it seems that you fixed the problem with the kernel image file but did not adjust the grub menu to compensate for the fact that UUID is broken and thats why you got the same result even after fixing the image, lucky for me I had some broken hooks and only my fallback image generated properly so I figured it out, although it took me a little while.
Anyhow this is basically what needs to be done to correct the problem.
1. Boot ArchLive
2. mkdir /media/disk
3. mount /dev/sdxX /media/disk
4. chroot /media/disk
5. mkinitcpio -k 2.6.28-ARCH -g /boot/kernel26.img
6. nano /boot/grub/menu.lst
7. Replace any references to UUID with /dev/sdxX (where xX represents your drive and partition) instead, save and exit nano.
8. reboot
Make sure and pay attention to the output of the mkinitcpio command in my step 5. If there are any errors relating to one or more of the hooks you'll need to edit /etc/mkinitcpio.conf and remove the hook it complains about !!IF POSSIBLE!!. I for example had some problem with the autodetect hook which caused my regular kernel to fail to create an image.
If mkinicpio doesn't complain and tells you it SUCCEEDED generating the images then you should be good to go.
Last edited by blazercist (2009-01-29 18:47:25) -
[SOLVED] UEFI system booting from MBR partition table and GRUB legacy
I'm trying to understand once and for all the process by which Arch can be booted from a system with UEFI firmware and an MBR partition table. Some of the information on the wiki seems conflictual / non-nonsensical at times. Apologies in advance if this has been answered time and time again, but I did search around and all I found was fixes to get Arch to boot rather than comprehensive explanations of the boot process.
Now, the way I would imagine it works is that it's just completely identical to the way it would work with a BIOS firmware. The UEFI firmware detects an MBR partitioning scheme (or is configured to know it's an MBR partitioning scheme), activates some "legacy" mode and executes the MBR boot code, just like a BIOS firmware would.
The wiki however, says different. From the Macbook article: "Do not install GRUB onto /dev/sda !!! Doing so is likely to lead to an unstable post-environment."?
So what is there in the MBR boot sector? Nothing?
How does the firmware know what to boot if there's no 0xEF BIOS boot partition and no Grub stage 1 in the MBR boot sector?
Also, how does installing Grub stage 1 to a partition work? Does it have to be at the beginning of the partition? Wouldn't that overwrite some existing data?
I'm especially puzzled since many guides to installing Vista on a macbook recommend simply formatting as MBR, and installing as normal, which I suppose entails having the Windows installation process write its boot code to the MBR, ie the equivalent of installing grub stage 1 to /dev/sda rather than to the /boot partition, as the Macbook article suggests.
Any input is appreciated.
P.S. I realize it's probably simpler, if I just want to dual boot Windows and Arch, to install Windows 7 in UEFI-GPT mode, let it create the EFI System Partition, and then install GRUB 2 to that partition, but I'm still curious about the UEFI-MBR boot process.
Last edited by padavoine (2012-06-06 09:35:10)padavoine wrote:
CSM in UEFI firmwares do the exact same job as normal BIOS firmware.
So it's something specific to the Mac that it's able to boot from a partition's VBR while ignoring the MBR?
The reason that warning is given is because grub-legacy modifies more than just the MBR boot code region. It can overwrite some parts of GPT header.
Not true, the instruction is given in the context of an MBR format, not in the context of a GPT format, so there's nothing to overwrite and Stage 1.5 should be safely embeddable in the post-MBR gap.
In BIOS boot (normal case in non-UEFI firmwares or CSM in UEFI firmwares) does not read the partitition table (atleast it is supposed to be dumb in this regard), it simply launches whatever boot code exists in the 1st 440-byte of the MBR region.
So again, you're saying it's specific to the Mac UEFI that it lets you choose a partition whose VBR to load, regardless of what's in the MBR?
I haven't used Macs so I can't comment on Mac firmware behaviour. But normal BIOS firmwares (legacy and CSM) launch only the MBR boot code and not the partition boot code. We need some chainload capable boot manager in the MBR to launch the partition VBR.
grub-legacy does not know anything about GPT. So when you install grub-legacy to /dev/sda, it install the MBR boot code (stage1) and stage 1.5 code to the (supposed) post MBR gap. Since there is no actual post MBR gap in GPT (which has been taken over by the header and partition table), grub-legacy does not check for GPT and it assumes the post MBR gap actually exists which is invalid in case of GPT. grub-legacy embeds the stage 1.5 code in GPT header and table region (which grub assumes to be unused post MBR gap) and thus corrupts it.
0xEF is the MBR type code for UEFISYS partition. grub stage 1 (used in grub-legacy, not in grub2) is the 440-byte boot code stored in MBR for use in BIOS boot.
That's precisely my point: with neither proper executable code in the MBR (since grub was installed to a partition, not to the MBR) nor a UEFI system partition, what does the firmware default to, and how does it know what partition to boot from?
In that case it might fallback to UEFI Shell (if it exists) or give an error similar to the case where BIOS does not find any bootable code in 440-byte MBR region.
So even with bootcamp/CSM, the disk also needs to be MBR partitioned. So Macs use something called "Hybrid GPT/MBR" ( http://rodsbooks.com/gdisk/hybrid.html ) where the MBR table is synced to match the first 3 partitions in the GPT table.
I know what Bootcamp does, and that's not what I was referring to. I was referring to standalone Vista installs. I wasn't puzzled at the fact that they were using MBR, I was puzzled at the fact that contrary to the recommendations for the standalone Arch install on the wiki (with MBR partitioning, not GPT), they didn't do anything to try and prevent Windows from writing to the MBR.
You can't prevent Windows from overwriting the MBR region. You have to re-install the bootloader (grub2/syslinux etc.) after installing Windows. That is the reason why it is recommended to install Windows first and linux later.
Thats not true. I actually find it is much easier to install Windows UEFI-GPT using USB rather than a DVD.
I haven't done it since the only UEFI system I own has no DVD drive, but I was under the impression that it was simply a matter of choosing DVD UEFI boot in the firmware's boot menu.
format the USB as FAT32 and extract the iso to it. That it.
No, thats not it, precisely, it doesn't work out of the box with a standard Windows install USB, you need to fiddle around:
2.3 Extract bootmgfw.efi from [WINDOWS_x86_64_ISO]/sources/install.wim => [INSTALL.WIM]/1/Windows/Boot/EFI/bootmgfw.efi (using 7-zip aka p7zip for both the files), or copy it from C:\Windows\Boot\EFI\bootmgfw.efi from a working Windows x86_64 installation.
2.4 Copy the extracted bootmgfw.efi file to [MOUNTPOINT]/efi/microsoft/boot/bootmgfw.efi .
Most of the Windows isos already have /EFI/BOOT/BOOTX64.EFI file, so no need to extract the bootmgfw.efi file.
There is no difference between in BIOS booting in UEFI firmwares and BIOS booting with legacy firmware.
There has to be a difference, at least in the Mac firmware (sorry, I keep switching), since legacy firmware, AFAIK, cannot chainload a bootloader in a partition's VBR without there being some sort of "stage1" code in the MBR.
No idea about Mac EFI. Apple made a spagetti out of UEFI Spec. To actually understand how Mac firmwares work, read the blog posts by Matthew Garrett of Redhat, about his efforts in getting Fedora to boot in Macs. -
[Solved] Systemd automounts /boot (was mlocate not traversing /boot)
For some reason, mlocate does not index my /boot:
┌─[Shiv ~ ]
└─╼ locate vmlinuz-linux
/home/jason/Build/chroot/root/boot/vmlinuz-linux
┌─[Shiv ~ ]
└─╼ sudo updatedb -U /boot
[sudo] password for jason:
┌─[Shiv ~ ]
└─╼ locate vmlinuz-linux
/boot/vmlinuz-linux
/boot/vmlinuz-linux-jwr
┌─[Shiv ~ ]
└─╼ sudo updatedb
┌─[Shiv ~ ]
└─╼ locate vmlinuz-linux
/home/jason/Build/chroot/root/boot/vmlinuz-linux
My /etc/updatedb.conf is the stock Arch one, /boot is obviously mounted (as the -U switch works), but a plain updatedb does not return any results from /boot.
I recently moved my ESP from /boot/efi to /boot, and as this is the only machine exhibiting this behaviour, it leads me to suspect something is amiss here.
My fstab:
# ESP: /dev/sda1
UUID=696A-09B3 /boot vfat defaults,relatime,discard 0 2
# /dev/mapper/vgroup-lvroot
UUID=1d2dfd7d-adeb-4786-ag98-c8fg675f8e2f / ext4 rw,relatime,discard,data=ordered 0 1
# /dev/mapper/vgroup-lvhome
UUID=50798021-94b5-4011-a593-9087gfhcd59b8 /home ext4 rw,relatime,discard 0 2
Am I missing something obvious?
# edit: updated thread title with the cause, as opposed to the symptom...WonderWoofy wrote:There is a mechanism in systemd (or maybe gummiboot) that mounts the ESP on /boot as a systemd autostart unit. So it shows up as autofs, which mlocate does not venture into.
Bingo!
┌─[Shiv ~ ]
└─╼ mount | grep boot
systemd-1 on /boot type autofs (rw,relatime,fd=36,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
/dev/sda1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro,discard)
falconindy wrote:If there's one thing I've learned about remote debugging over the years, it's to not trust people.
Especially Antipodeans
lolilolicon wrote:I Googled for this and found this relevant talk in our (duh) wiki
I spent some time yesterday searching, but missed this--to my shame
65kid on the wiki wrote:* this feature isn't even documented in systemd yet
Great. Any way to suppress this?
Maybe you are looking for
-
Jabber for Windows - without LDAP integrated with CUCM Jabber UDS - NO PEOPLE CAN SEARCH
Hi all Jabber Experts, I have the CUCM, which is the versin 8.6 and the Presence Server, which is the version 8.6, that is not integrated the LDAP, but I want to deploy the Jabber for Windows. So I would use the UDS to deploy the Jabber for Windows (
-
Unable to print pages directly from internet explorer 9 script error 2126
HP photosmart wireless b109n-z computer Packard Bell One Two L5861 64bit I am unable after going to many forums where it seems to be quite a problem and trying different ways to try and rectify a error mesage An error has occurred in the script on th
-
Condition based records sent to proxy
Hi all, My interface is a File(FCC)-Proxy in PI7.0. I get 100s of records from the source and there are fields ID and LOC. Fields which has ID=2 and LOC=US or UK, only those particular records should be sent to the proxy. Please help. Thanks, Chaitan
-
Font fitting to edge of text box
Hi all, Does anyone know if it's possible to force a font to go the edge of a text frame? Some fonts have generous space above the cap height of the letters inside a text frame. But I would like the text frame to be the same size (height) as the font
-
TS2972 Home Sharing Issue - Help!
I can view the library in the left hand pane; however, when I select it will not load the music. It states "Loading "XXXXX Library" and then defaults to the music library. Can you please help!