Rescue CD UEFI
hello,I am doing a follow up of the threat https://community.f-secure.com/t5/Security/Rescue-CD-scanning-failed/td-p/33171 I have a computer that is only able to boot with UEFI.it seems impossible to boot the rescue CD as it is only for BIOS... is there an update planned or other options? thanks to all the community for any help. Steven
Hi Rusli, thanks for replying.well I haven't tried it anyother yet. I was hoppying to use the F-Secure version. of the live CD. If f-secure is the best (malware & rootkit detection), this is the one I want to use. if not than we are very much open to use another one (the best...) again thanks for the help on this subject
Similar Messages
-
Efibootmgr & gummiboot replaced UEFI entry for Windows Boot Manager
TLDR
I am now in Windows 7 and dual boot with Arch is working fine.
But before I update Arch, I would like to understand what happened, as in why adding an efibootmgr entry for Arch replaced/deleted the Windows Boot Manager entry although I followed the BG.
The status of my UEFI boot menu was, before the installation of Arch:
Windows Boot Manager
AHCI HDJ... (hard drive 1)
AHCI ST... (hard drive 2)
While working through the BG, I decided to use gummiboot=> https://wiki.archlinux.org/index.php/Be … #Gummiboot. So:
pacman -S gummiboot
gummiboot install
pacman -S efibootmgr
gummiboot install
[some error ocurred, as mentioned in red box]
efibootmgr -c -L "Gummiboot" -l /EFI/gummiboot/gummibootx64.efi
nano /boot/loader/entries/arch.conf
title Arch Linux
linux /vmlinuz-linux
initrd /initramfs-linux.img
options root=/dev/sdb3 ro
[CTRL + X, Y, Enter]
exit
umount /mnt/{boot,home,}
reboot
I then saw a new list of the UEFI boot order:
Gummiboot
AHCI HDJ... (hard drive 1)
AHCI ST... (hard drive 2)
Chose Gummiboot and it brought up a gummiboot menu with entries
Arch Linux
Windows Boot Manager
EFI Shell something
Selected Arch Linux and it went to a message something along "boot device ' ' not found" and I was in a shell which was, I think, rootfs.
I rebooted via the button on my desktop and out the Arch Linux USB drive back. After mounting the partitions:
gummiboot remove
efibootmgr
[0000: Windows Boot Manager
[0001: Arch Linux
[0002: AHCI HDJ...
[0003: AHCI ST...
exit
umount /mnt/{boot,home,}
reboot
Now I booted into a black screen with white text which said something "Reboot and select proper Boot device"
=> Inserted Win 7 64-bit DVD, repaired the boot sector. Rebooted, saw I had these entries again:
Windows Boot Manager
AHCI HDJ... (hard drive 1)
AHCI ST... (hard drive 2)
The boot into Windows worked fine. Rebooted, chrooted into my install again and:
efibootmgr
[0000: Arch Linux
[0001: Windows Boot Manager
[0003: AHCI HDJ...
[0003: AHCI ST...
efibootmogr -b 0 -B
Then I used the EFISTUB method:
efibootmgr -c -L "Arch Linux" -l /vmlinuz-linux -u "root=/dev/sdb3 ro initrd=/initramfs-linux.img"
efibootmgr
[0000: Windows Boot Manager
[0001: Arch Linux
[0002: AHCI HDJ...
[0003: AHCI ST...
exit
umount /mnt/{boot,home,}
reboot
On reboot, 'Windows Boot Manager' was again replaced by 'Arch Linux'.
=> Inserted Win 7 64-bit DVD, repaired the boot sector.
Rebooted, I have now Windows Boot Manager + Arch Linux and dual boot works now.
My questions:
What is going on with efibootmgr replacing/deleting the Windows entry? Is there something wrong with my UEFI menu?
In connection with 1., I would like to sync the EFISTUB Kernel (wiki entry) before I run pacman -Syu. Can I do that now?
Can I uninstall gummiboot now?
Last edited by jones (2013-07-11 12:30:55)henrik wrote:So in light of your post, I decided to ditch EFISTUB + gummiboot and try out GRUB. Thanks for clearing it up a bit. Which is what confuses me a great deal more, as GRUB/gummiboot obviously do not meddle with Microsoft's EFI files. Right?
EFI relies on two things to boot:
Boot loader program files on the ESP (or occasionally elsewhere).
NVRAM entries pointing to the boot loader files.
Your own problems seem to be with the NVRAM entries, not with the boot loader files themselves. Unfortunately, managing those NVRAM entries has proven to be problematic because of bugs in specific EFI implementations, bugs in efibootmgr and other tools that manipulate the NVRAM entries, poor documentation, and other factors.
To answer your question, though, no boot loader should mess with another's files. Such things can happen, though. The number of bugs that cause Microsoft's boot loader (EFI/Microsoft/Boot/bootmgfw.efi) to be treated deferentially have provoked some tools to use it as a target location for other boot loaders. (Ubuntu's Boot Repair tool does this in a rather overzealous way. So does my own rEFInd installer script, but only under certain narrow circumstances.) Also, the EFI/BOOT/bootx64.efi file is a special case; it's the fallback bootloader that's used when NVRAM entries are missing or don't work, and various boot loader installation procedures place copies in that location, so it can be overwritten and could contain just about anything.
However, the whole thing happened again with GRUB. So I did the whole "repairing Boot problems" with the Windows DVD rescue thingy again and deleted all non-Microsoft files from the EFI partition, /dev/sda1.
Then I formatted / (root) and installed arch again and followed the Beginners' Guide which suggest mounting /dev/sda1/ to /mnt/boot (in contrast to the GRUB entry where the ESP should be mounted to /mnt/boot/efi).
I strongly advise against doing a complete re-installation just to overcome a boot loader problem. Instead, figure out what the problem is and fix it. Doing a complete re-installation is not likely to fix anything, and depending on precisely how you do it, you could end up with a more complex problem. The reason is that the re-installation is not likely to erase the NVRAM entries from the old installation, so you could find that you've got additional stray NVRAM entries. If you do happen to fix the problem by re-installing (say, because you selected a different installation option), you're not likely to know what changed to fix the problem, so you could end up in the same boat should you need to re-install again in the future.
But it did not show this line
Found Windows 7 (loader) on /dev/sda1
... how come??
I've given up trying to understand GRUB's configuration scripts. You could try creating an entry manually by editing /etc/grub.d/40_custom; or you could forget about using the GRUB scripts and create a hand-crafted grub.cfg; or you could forget about using GRUB at all. I'm not a fan of GRUB, so my personal choice is the final one.
So for all the headache and time ... should I delete the EFI partition and recreate it maybe? I think it's possible using the Windows 7 DVD.
But somehow using efibootmgr on my UEFI list somehow invalidated the Windows entry.
Reviewing your posts, it seems that you want to use the EFI stub loader directly, but you're having problems with that because when you add it to the NVRAM entries, Windows drops off your boot manager's boot options. The obvious solution to this problem is to forget about adding the EFI stub loader directly to the NVRAM entries, and instead add a boot manager that can handle either a Linux kernel or the Windows boot loader. (IMHO, this is the superior solution anyhow; I disagree with the Arch wiki's emphasis on using the EFI stub loader "raw.") It seems you were trying to do this with GRUB but had problems booting Windows. Earlier you tried gummiboot but had problems booting Linux. My suggestion is to either go back to gummiboot and fix its problem or try rEFInd. The "device not found" error you reported with gummiboot is usually caused by either a missing (or incorrectly-specified) initrd file or by an incorrectly-specified "root=" option passed to the kernel. Check those possitilities, and if you need help, report what happens in more detail. If necessary, take a digital photo of the screen and post it here. (Make sure it's legible, though!)
You can try rEFInd with minimal disk by using a CD-R or USB flash drive image. Boot with that and your NVRAM and ESP won't be affected at all. If you can get rEFInd working from the flash drive, you can then install it to your hard disk and it should continue working. Note that you probably won't be able to boot Linux directly from rEFInd with your current configuration without adding a "root=" specification to the kernel command line. You can do this by hitting F2 or Insert twice rather than launching Linux by pressing Enter. Alternatively, you can create a refind_linux.conf file in the directory that holds your kernel. That file's contents are described in the rEFInd documentation. -
Unable to boot in UEFI mode.
After looking around at the wiki for a few days and playing around with Arch in VirtualBox I went to see if it would boot on my native hardware, and all the turns up is a black screen. Legacy mode is not an option as I am dual booting Windows 8.1 64 bit. I suspect this is related to my issues with Fedora as the Fedora installation media will not boot either, though it once did. Fedora used to work on my machine until it got dropped one day. After the drop I started having some strange issues and tried reinstalling Fedora, only to find that once it hit the bootloader I would face a black screen that never goes away until I power the system down. I sent my laptop in to Lenovo to be serviced and they replaced the optical drive, hard drive and did a reinstall of Windows 8. Fedora still would not boot after I got the machine back. I tried Ubuntu after the drop before sending it off and it worked, and that is what I currently have installed. My knowledge of UEFI is limited. Any ideas? My laptop is a Thinkpad L440 by the way.
Head_on_a_Stick wrote:
Actually, Ubuntu will install and run with Secure Boot enabled (as will the Arch live ISO) -- the blog post is just about making your own Secure Boot keys.
From Ubuntu, post the output of:
# efibootmgr -v
Yeah I know that, but I left it off to save the extra hassle.
Here is the output for the command:
swilliams@speedy:~/Videos$ sudo efibootmgr -v
[sudo] password for swilliams:
BootCurrent: 0014
Timeout: 0 seconds
BootOrder: 0014,0013,0000,0001,0002,0003,0007,0008,0009,000A,000B,000C,000D,0012
Boot0000 Setup
Boot0001 Boot Menu
Boot0002 Diagnostic Splash Screen
Boot0003 Lenovo Diagnostics
Boot0004 Startup Interrupt Menu
Boot0005 Rescue and Recovery
Boot0006 MEBx Hot Key
Boot0007* USB CD 030a2400d23878bc820f604d8316c068ee79d25b86701296aa5a7848b66cd49dd3ba6a55
Boot0008* USB FDD 030a2400d23878bc820f604d8316c068ee79d25b6ff015a28830b543a8b8641009461e49
Boot0009* ATAPI CD0 030a2500d23878bc820f604d8316c068ee79d25baea2090adfde214e8b3a5e471856a35400
Boot000A* ATA HDD0 030a2500d23878bc820f604d8316c068ee79d25b91af625956449f41a7b91f4f892ab0f604
Boot000B* ATA HDD1 030a2500d23878bc820f604d8316c068ee79d25b91af625956449f41a7b91f4f892ab0f605
Boot000C* USB HDD 030a2400d23878bc820f604d8316c068ee79d25b33e821aaaf33bc4789bd419f88c50803
Boot000D* PCI LAN 030a2400d23878bc820f604d8316c068ee79d25b78a84aaf2b2afc4ea79cf5cc8f3d3803
Boot000E* IDER BOOT CDROM ACPI(a0341d0,0)PCI(16,2)ATAPI(0,1,0)
Boot000F* IDER BOOT Floppy ACPI(a0341d0,0)PCI(16,2)ATAPI(0,0,0)
Boot0010* ATA HDD 030a2400d23878bc820f604d8316c068ee79d25b91af625956449f41a7b91f4f892ab0f6
Boot0011* ATAPI CD 030a2400d23878bc820f604d8316c068ee79d25baea2090adfde214e8b3a5e471856a354
Boot0012* PCI LAN 030a2400d23878bc820f604d8316c068ee79d25b78a84aaf2b2afc4ea79cf5cc8f3d3803
Boot0013* Windows Boot Manager HD(2,1f4800,82000,e2e20688-f616-4344-9acc-e7ae20c772e3)File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0014* ubuntu HD(2,1f4800,82000,e2e20688-f616-4344-9acc-e7ae20c772e3)File(\EFI\ubuntu\shimx64.efi) -
Does UEFI exist on Lenovo T61P running Windows 8.1?
Just installed Windows 8.1 on my Lenovo T61P and running great after fixing wi-fi issue. Need to know how to boot from CD in this new operating system, as BIOS is still same as from XP days. I have read I have to change from UEIF mode to Legacy mode but don't know where it is, it it even exists, or what. This is important as I am setting up rescue boot CD's to recover backups. I can only get into the BIOS Setup Utility screen. See no options for setting to legacy anywhere. Please help as I need to boot from CD to test out emergency options. Has to be a way I would think as I believe Windows 8.1 automatically puts this boot mode in UIFE but I have no issues with security and would like to keep this off if possible.
I have tried also to go in via the options route after stariting Windows. When I get to the screen that gives the option to do this, that option is missing. I read that "Lenovo preloaded Windows 8/8.1 is set up with UEFI boot. If your computer is not fitted with UEFI boot, you can only enter BIOS setup or UEFI firmware via the traditional method."
Last updated 26 Mar 2014.
Are there any downloads that will install this? Am I stuck in UEFI mode or what? Please comment. Am I in Legacy mode? How do I find out?
Is the Bios Update Utility for Windows 8 etc released 8/4/2013 the fix for this? Is this an installed feature or one that can only be run off a boot CD or USB? Looks like it only supports T420s and T420si. Sorry. need on for T61P.
Edit to say;
Forgot to add this info.
Bios vers. 2.3 (7LETDOWW)
Bios date 2012-02-27
CPU Type Intel Core 2 Duo CPU T9300
CPU Speed 2.5GHz
I did not know the BIOS checked out so new, as it must have been updated on my last warranted repair for this system. Is their an updated file that adds this UIFE to Legacy option in to some type of system setup screen on boot?
thanks and need help soon while I have time to do this.
Solved!
Go to Solution.Hi,
Your T61p BIOS is pre-UEFI. The Win 8 install couldn't have changed that. You don't need to change anything.
To boot a CD, hit the power button and start tapping F12. That should bring up the boot menu. Select the CD.
[edit] You may find this interesting: https://forums.lenovo.com/t5/General-Discussion-Knowledge/What-is-UEFI-and-when-was-it-introduced-on...
Z.
The large print: please read the Community Participation Rules before posting. Include as much information as possible: model, machine type, operating system, and a descriptive subject line. Do not include personal information: serial number, telephone number, email address, etc. The fine print: I do not work for, nor do I speak for Lenovo. Unsolicited private messages will be ignored. ... GeezBlog
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество -
Arch & Windows 8 Dual Boot -- Windows Boot Loader loads grub-rescue
Arch works fine,but as it always happens Windows boot went down. Both OS are EFI.
Note that boot secure and fast boot were disabled for Windows 8.
I used os-prober, but did not fix anything; so, I removed it. I tried to hack things out using boot-repair from Ubuntu, but it requires a repository, grub-efi, from Ubuntu that Arch doesn't have.
I am trying to modify files in grub.d and grub.cfg and hopefully fix something.
Exact description:
- archgrub loads and shows 3 entries. Two for Arch that load the sys succesfully and one for Windows 8 that fails.
- When I try to execute Windows from grub, it brings me to a grub rescue>
and shows error /boot/grub/x86_64-efi/normal.mod not found
As far as I am concerned this .mod is from Linux, so I don't know why it is being called into Windows loading procedures.
lsblk returns:
[jav@localhost ~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 931.5G 0 disk
|-sda1 8:1 0 1000M 0 part
|-sda2 8:2 0 260M 0 part
|-sda3 8:3 0 1000M 0 part
|-sda4 8:4 0 128M 0 part
|-sda5 8:5 0 605.3G 0 part
|-sda6 8:6 0 5.4G 0 part /boot/efi
|-sda7 8:7 0 25G 0 part
|-sda8 8:8 0 20G 0 part
|-sda9 8:9 0 244.1G 0 part /
`-sda10 8:10 0 29.3G 0 part
sr0 11:0 1 1024M 0 rom
Here's the output of fdisk. Another weird thing is that sometimes ubuntu would show on my terminal. See the first line below, "jav@ubuntu"?!
[jav@ubuntu ~]$ sudo fdisk -l
[sudo] password for jav:
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 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
Disklabel type: gpt
Disk identifier: [i deleted this]
Device Start End Size Type
/dev/sda1 2048 2050047 1000M Windows recovery environment
/dev/sda2 2050048 2582527 260M EFI System
/dev/sda3 2582528 4630527 1000M unknown
/dev/sda4 4630528 4892671 128M Microsoft reserved
/dev/sda5 4892672 1274335231 605.3G Microsoft basic data
/dev/sda6 1847777280 1859151871 5.4G EFI System
/dev/sda7 1859151872 1911580671 25G Microsoft basic data
/dev/sda8 1911580672 1953523711 20G Windows recovery environment
/dev/sda9 1335775232 1847777279 244.1G Linux filesystem
/dev/sda10 1274335232 1335775231 29.3G Microsoft basic data
And, bootinfoscript output:
Boot Info Script 0.61 [1 April 2012]
============================= Boot Info Summary: ===============================
=> No boot loader is installed in the MBR of /dev/sda.
sda1: __________________________________________________________________________
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:
sda2: __________________________________________________________________________
File system: vfat
Boot sector type: Windows 7: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /efi/Boot/bkpbootx64.efi /efi/Boot/bootx64.efi
/efi/ubuntu/grubx64.efi
sda3: __________________________________________________________________________
File system: vfat
Boot sector type: Windows 7: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /efi/Boot/bkpbootx64.efi /efi/Boot/bootx64.efi
/efi/ubuntu/grubx64.efi /bootmgr /boot/bcd
sda4: __________________________________________________________________________
File system:
Boot sector type: -
Boot sector info:
Mounting failed: mount: unknown filesystem type ''
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: /bootmgr /Boot/BCD /Windows/System32/winload.exe
sda6: __________________________________________________________________________
File system: vfat
Boot sector type: SYSLINUX 6.02 ... :..(:,:0:4:8:....D:H:L:[.T:[.\:`:d:[.l:p:t:x:|:.:.:.:.:.:.:.:.....................
Boot sector info: Syslinux looks at sector 99102 of /dev/sda6 for its
second stage. SYSLINUX is installed in the /syslinux
directory. No errors found in the Boot Parameter Block.
Operating System:
Boot files: /grub/grub.cfg /syslinux/syslinux.cfg
/syslinux/ldlinux.sys
sda7: __________________________________________________________________________
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:
sda8: __________________________________________________________________________
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:
sda9: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Arch Linux ()
Boot files: /etc/fstab
sda10: _________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System:
Boot files:
============================ Drive/Partition Info: =============================
Drive: sda _____________________________________________________________________
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 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
Partition Boot Start Sector End Sector # of Sectors Id System
/dev/sda1 1 1,953,525,167 1,953,525,167 ee GPT
GUID Partition Table detected.
Partition Start Sector End Sector # of Sectors System
/dev/sda1 2,048 2,050,047 2,048,000 Windows Recovery Environment (Windows)
/dev/sda2 2,050,048 2,582,527 532,480 EFI System partition
/dev/sda3 2,582,528 4,630,527 2,048,000 -
/dev/sda4 4,630,528 4,892,671 262,144 Microsoft Reserved Partition (Windows)
/dev/sda5 4,892,672 1,274,335,231 1,269,442,560 Data partition (Windows/Linux)
/dev/sda6 1,847,777,280 1,859,151,871 11,374,592 EFI System partition
/dev/sda7 1,859,151,872 1,911,580,671 52,428,800 Data partition (Windows/Linux)
/dev/sda8 1,911,580,672 1,953,523,711 41,943,040 Windows Recovery Environment (Windows)
/dev/sda9 1,335,775,232 1,847,777,279 512,002,048 Data partition (Linux)
/dev/sda10 1,274,335,232 1,335,775,231 61,440,000 Data partition (Windows/Linux)
"blkid" output: ________________________________________________________________
Device UUID TYPE LABEL
/dev/sda1 CE62D9F062D9DCF1 ntfs WINRE_DRV
/dev/sda10 150a8788-6049-45ed-85af-ded92a2c0801 ext4
/dev/sda2 16DC-8816 vfat SYSTEM_DRV
/dev/sda3 7CDD-0403 vfat LRS_ESP
/dev/sda4
/dev/sda5 40E4E0CFE4E0C7EC ntfs Windows8_OS
/dev/sda6 9C3F-2A9E vfat
/dev/sda7 7240E43740E40427 ntfs LENOVO
/dev/sda8 422CE5EA2CE5D945 ntfs PBR_DRV
/dev/sda9 1a765403-f251-43d8-8edf-c191475d3837 ext4
================================ Mount points: =================================
Device Mount_Point Type Options
/dev/sda6 /boot vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/sda6 /boot/efi vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/sda9 / ext4 (rw,relatime,data=ordered)
============================= sda6/grub/grub.cfg: ==============================
# DO NOT EDIT THIS FILE
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_gpt
insmod ext2
set root='hd0,gpt9'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt9 --hint-efi=hd0,gpt9 --hint-baremetal=ahci0,gpt9 1a765403-f251-43d8-8edf-c191475d3837
else
search --no-floppy --fs-uuid --set=root 1a765403-f251-43d8-8edf-c191475d3837
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
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-1a765403-f251-43d8-8edf-c191475d3837' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod fat
set root='hd0,gpt6'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt6 --hint-efi=hd0,gpt6 --hint-baremetal=ahci0,gpt6 9C3F-2A9E
else
search --no-floppy --fs-uuid --set=root 9C3F-2A9E
fi
echo 'Loading Linux core repo kernel ...'
linux /vmlinuz-linux root=UUID=1a765403-f251-43d8-8edf-c191475d3837 rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux.img
menuentry 'Arch Linux, with Linux core repo kernel (Fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-fallback-1a765403-f251-43d8-8edf-c191475d3837' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod fat
set root='hd0,gpt6'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt6 --hint-efi=hd0,gpt6 --hint-baremetal=ahci0,gpt6 9C3F-2A9E
else
search --no-floppy --fs-uuid --set=root 9C3F-2A9E
fi
echo 'Loading Linux core repo kernel ...'
linux /vmlinuz-linux root=UUID=1a765403-f251-43d8-8edf-c191475d3837 rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux-fallback.img
### END /etc/grub.d/10_linux ###
## Attempt at fixing grub
# insmod fat
# set root='hd0,gpt6'
### BEGIN /etc/grub.d/30_os-prober ###
#menuentry 'Windows Boot Manager (on /dev/sda2)' --class windows --class os $menuentry_id_option 'osprober-efi-16DC-8816' {
# insmod part_gpt
# insmod fat
# set root='hd0,gpt2'
# if [ x$feature_platform_search_hint = xy ]; then
# search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 16DC-8816
# else
# search --no-floppy --fs-uuid --set=root 16DC-8816
# fi
# chainloader /EFI/Microsoft/Boot/bootmgfw.efi
menuentry "Windows 8 UEFI" {
set root='(hd0,gpt2)'
chainloader /EFI/Microsoft/Boot/bootmgfw.efi
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
### BEGIN /etc/grub.d/60_memtest86+ ###
### END /etc/grub.d/60_memtest86+ ###
========================= sda6/syslinux/syslinux.cfg: ==========================
# Config file for Syslinux -
# /boot/syslinux/syslinux.cfg
# Comboot modules:
# * menu.c32 - provides a text menu
# * vesamenu.c32 - provides a graphical menu
# * chain.c32 - chainload MBRs, partition boot sectors, Windows bootloaders
# * hdt.c32 - hardware detection tool
# * reboot.c32 - reboots the system
# To Use: Copy the respective files from /usr/lib/syslinux to /boot/syslinux.
# If /usr and /boot are on the same file system, symlink the files instead
# of copying them.
# If you do not use a menu, a 'boot:' prompt will be shown and the system
# will boot automatically after 5 seconds.
# Please review the wiki: https://wiki.archlinux.org/index.php/Syslinux
# The wiki provides further configuration examples
DEFAULT arch
PROMPT 0 # Set to 1 if you always want to display the boot: prompt
TIMEOUT 50
# You can create syslinux keymaps with the keytab-lilo tool
#KBDMAP de.ktl
# Menu Configuration
# Either menu.c32 or vesamenu32.c32 must be copied to /boot/syslinux
UI menu.c32
#UI vesamenu.c32
# Refer to http://syslinux.zytor.com/wiki/index.php/Doc/menu
MENU TITLE Arch Linux
#MENU BACKGROUND splash.png
MENU COLOR border 30;44 #40ffffff #a0000000 std
MENU COLOR title 1;36;44 #9033ccff #a0000000 std
MENU COLOR sel 7;37;40 #e0ffffff #20ffffff all
MENU COLOR unsel 37;44 #50ffffff #a0000000 std
MENU COLOR help 37;40 #c0ffffff #a0000000 std
MENU COLOR timeout_msg 37;40 #80ffffff #00000000 std
MENU COLOR timeout 1;37;40 #c0ffffff #00000000 std
MENU COLOR msg07 37;40 #90ffffff #a0000000 std
MENU COLOR tabmsg 31;40 #30ffffff #00000000 std
# boot sections follow
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
LABEL arch
MENU LABEL Arch Linux
LINUX ../vmlinuz-linux
APPEND root=/dev/sda3 rw
INITRD ../initramfs-linux.img
LABEL archfallback
MENU LABEL Arch Linux Fallback
LINUX ../vmlinuz-linux
APPEND root=/dev/sda3 rw
INITRD ../initramfs-linux-fallback.img
#LABEL windows
# MENU LABEL Windows
# COM32 chain.c32
# APPEND hd0 1
LABEL hdt
MENU LABEL HDT (Hardware Detection Tool)
COM32 hdt.c32
LABEL reboot
MENU LABEL Reboot
COM32 reboot.c32
LABEL poweroff
MENU LABEL Poweroff
COM32 poweroff.c32
=================== sda6: Location of files loaded by Grub: ====================
GiB - GB File Fragment(s)
================= sda6: Location of files loaded by Syslinux: ==================
GiB - GB File Fragment(s)
============== sda6: Version of COM32(R) files used by Syslinux: ===============
syslinux/cat.c32 : not a COM32/COM32R module
syslinux/chain.c32 : not a COM32/COM32R module
syslinux/cmd.c32 : not a COM32/COM32R module
syslinux/config.c32 : not a COM32/COM32R module
syslinux/cptime.c32 : not a COM32/COM32R module
syslinux/cpuid.c32 : not a COM32/COM32R module
syslinux/cpuidtest.c32 : not a COM32/COM32R module
syslinux/debug.c32 : not a COM32/COM32R module
syslinux/disk.c32 : not a COM32/COM32R module
syslinux/dmitest.c32 : not a COM32/COM32R module
syslinux/elf.c32 : not a COM32/COM32R module
syslinux/ethersel.c32 : not a COM32/COM32R module
syslinux/gfxboot.c32 : not a COM32/COM32R module
syslinux/gpxecmd.c32 : not a COM32/COM32R module
syslinux/hdt.c32 : not a COM32/COM32R module
syslinux/hexdump.c32 : not a COM32/COM32R module
syslinux/host.c32 : not a COM32/COM32R module
syslinux/ifcpu.c32 : not a COM32/COM32R module
syslinux/ifcpu64.c32 : not a COM32/COM32R module
syslinux/ifmemdsk.c32 : not a COM32/COM32R module
syslinux/ifplop.c32 : not a COM32/COM32R module
syslinux/kbdmap.c32 : not a COM32/COM32R module
syslinux/kontron_wdt.c32 : not a COM32/COM32R module
syslinux/ldlinux.c32 : not a COM32/COM32R module
syslinux/libcom32.c32 : not a COM32/COM32R module
syslinux/libgpl.c32 : not a COM32/COM32R module
syslinux/liblua.c32 : not a COM32/COM32R module
syslinux/libmenu.c32 : not a COM32/COM32R module
syslinux/libutil.c32 : not a COM32/COM32R module
syslinux/linux.c32 : not a COM32/COM32R module
syslinux/ls.c32 : not a COM32/COM32R module
syslinux/lua.c32 : not a COM32/COM32R module
syslinux/mboot.c32 : not a COM32/COM32R module
syslinux/meminfo.c32 : not a COM32/COM32R module
syslinux/menu.c32 : not a COM32/COM32R module
syslinux/pcitest.c32 : not a COM32/COM32R module
syslinux/pmload.c32 : not a COM32/COM32R module
syslinux/poweroff.c32 : not a COM32/COM32R module
syslinux/prdhcp.c32 : not a COM32/COM32R module
syslinux/pwd.c32 : not a COM32/COM32R module
syslinux/pxechn.c32 : not a COM32/COM32R module
syslinux/reboot.c32 : not a COM32/COM32R module
syslinux/rosh.c32 : not a COM32/COM32R module
syslinux/sanboot.c32 : not a COM32/COM32R module
syslinux/sdi.c32 : not a COM32/COM32R module
syslinux/sysdump.c32 : not a COM32/COM32R module
syslinux/vesainfo.c32 : not a COM32/COM32R module
syslinux/vesamenu.c32 : not a COM32/COM32R module
syslinux/vpdtest.c32 : not a COM32/COM32R module
syslinux/whichsys.c32 : not a COM32/COM32R module
syslinux/zzjson.c32 : not a COM32/COM32R module
=============================== sda9/etc/fstab: ================================
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda9
UUID=1a765403-f251-43d8-8edf-c191475d3837 / ext4 rw,relatime,data=ordered 0 1
# /dev/sda6
#UUID=9C3F-2A9E /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
UUID=9C3F-2A9E /boot vfat defaults 0 2
UUID=9C3F-2A9E /boot/efi vfat defaults 0 1
============== sda9: Version of COM32(R) files used by Syslinux: ===============
boot/syslinux/cat.c32 : not a COM32/COM32R module
boot/syslinux/chain.c32 : not a COM32/COM32R module
boot/syslinux/cmd.c32 : not a COM32/COM32R module
boot/syslinux/config.c32 : not a COM32/COM32R module
boot/syslinux/cptime.c32 : not a COM32/COM32R module
boot/syslinux/cpuid.c32 : not a COM32/COM32R module
boot/syslinux/cpuidtest.c32 : not a COM32/COM32R module
boot/syslinux/debug.c32 : not a COM32/COM32R module
boot/syslinux/disk.c32 : not a COM32/COM32R module
boot/syslinux/dmitest.c32 : not a COM32/COM32R module
boot/syslinux/elf.c32 : not a COM32/COM32R module
boot/syslinux/ethersel.c32 : not a COM32/COM32R module
boot/syslinux/gfxboot.c32 : not a COM32/COM32R module
boot/syslinux/gpxecmd.c32 : not a COM32/COM32R module
boot/syslinux/hdt.c32 : not a COM32/COM32R module
boot/syslinux/hexdump.c32 : not a COM32/COM32R module
boot/syslinux/host.c32 : not a COM32/COM32R module
boot/syslinux/ifcpu.c32 : not a COM32/COM32R module
boot/syslinux/ifcpu64.c32 : not a COM32/COM32R module
boot/syslinux/ifmemdsk.c32 : not a COM32/COM32R module
boot/syslinux/ifplop.c32 : not a COM32/COM32R module
boot/syslinux/kbdmap.c32 : not a COM32/COM32R module
boot/syslinux/kontron_wdt.c32 : not a COM32/COM32R module
boot/syslinux/ldlinux.c32 : not a COM32/COM32R module
boot/syslinux/libcom32.c32 : not a COM32/COM32R module
boot/syslinux/libgpl.c32 : not a COM32/COM32R module
boot/syslinux/liblua.c32 : not a COM32/COM32R module
boot/syslinux/libmenu.c32 : not a COM32/COM32R module
boot/syslinux/libutil.c32 : not a COM32/COM32R module
boot/syslinux/linux.c32 : not a COM32/COM32R module
boot/syslinux/ls.c32 : not a COM32/COM32R module
boot/syslinux/lua.c32 : not a COM32/COM32R module
boot/syslinux/mboot.c32 : not a COM32/COM32R module
boot/syslinux/meminfo.c32 : not a COM32/COM32R module
boot/syslinux/menu.c32 : not a COM32/COM32R module
boot/syslinux/pcitest.c32 : not a COM32/COM32R module
boot/syslinux/pmload.c32 : not a COM32/COM32R module
boot/syslinux/poweroff.c32 : not a COM32/COM32R module
boot/syslinux/prdhcp.c32 : not a COM32/COM32R module
boot/syslinux/pwd.c32 : not a COM32/COM32R module
boot/syslinux/pxechn.c32 : not a COM32/COM32R module
boot/syslinux/reboot.c32 : not a COM32/COM32R module
boot/syslinux/rosh.c32 : not a COM32/COM32R module
boot/syslinux/sanboot.c32 : not a COM32/COM32R module
boot/syslinux/sdi.c32 : not a COM32/COM32R module
boot/syslinux/sysdump.c32 : not a COM32/COM32R module
boot/syslinux/vesainfo.c32 : not a COM32/COM32R module
boot/syslinux/vesamenu.c32 : not a COM32/COM32R module
boot/syslinux/vpdtest.c32 : not a COM32/COM32R module
boot/syslinux/whichsys.c32 : not a COM32/COM32R module
boot/syslinux/zzjson.c32 : not a COM32/COM32R module
======================== Unknown MBRs/Boot Sectors/etc: ========================
Unknown GPT Partiton Type
e7afbfbf4fa38a449a5b6213eb736c22
========= Devices which don't seem to have a corresponding hard drive: =========
sdb
=============================== StdErr Messages: ===============================
cat: /tmp/BootInfo-p9ML2Cte/Tmp_Log: No such file or directory
cat: /tmp/BootInfo-p9ML2Cte/Tmp_Log: No such file or directory
/dev/cdrom: open failed: No medium found
/dev/sdb: open failed: No medium found
No volume groups found
mdadm: No arrays found in config file or automatically
Any ideas?
Here's my grub.cfg:
# DO NOT EDIT THIS FILE
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_gpt
insmod ext2
set root='hd0,gpt9'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt9 --hint-efi=hd0,gpt9 --hint-baremetal=ahci0,gpt9 1a765403-f251-43d8-8edf-c191475d3837
else
search --no-floppy --fs-uuid --set=root 1a765403-f251-43d8-8edf-c191475d3837
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
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-1a765403-f251-43d8-8edf-c191475d3837' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod fat
set root='hd0,gpt6'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt6 --hint-efi=hd0,gpt6 --hint-baremetal=ahci0,gpt6 9C3F-2A9E
else
search --no-floppy --fs-uuid --set=root 9C3F-2A9E
fi
echo 'Loading Linux core repo kernel ...'
linux /vmlinuz-linux root=UUID=1a765403-f251-43d8-8edf-c191475d3837 rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux.img
menuentry 'Arch Linux, with Linux core repo kernel (Fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-fallback-1a765403-f251-43d8-8edf-c191475d3837' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod fat
set root='hd0,gpt6'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt6 --hint-efi=hd0,gpt6 --hint-baremetal=ahci0,gpt6 9C3F-2A9E
else
search --no-floppy --fs-uuid --set=root 9C3F-2A9E
fi
echo 'Loading Linux core repo kernel ...'
linux /vmlinuz-linux root=UUID=1a765403-f251-43d8-8edf-c191475d3837 rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux-fallback.img
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows Boot Manager (on /dev/sda2)' --class windows --class os $menuentry_id_option 'osprober-efi-16DC-8816' {
insmod part_gpt
insmod fat
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 16DC-8816
else
search --no-floppy --fs-uuid --set=root 16DC-8816
fi
chainloader /EFI/Microsoft/Boot/bootmgfw.efi
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
### BEGIN /etc/grub.d/60_memtest86+ ###
### END /etc/grub.d/60_memtest86+ ###
Last edited by knowNothing23 (2013-12-30 00:17:02)Hi,
New to this forum, joined today in anticipation of trying an install of AL...For whatever this may be worth:
I have an HP Pavillion desktop that came with Windows 8 (now 8.1), & has, of course, a UEFI boot system. I tried earlier to install Ubuntu Studio (which I currently run) on the same disk as Windows (/dev/sda), I made (I believe) a huge mistake in trying to install as LVM/ext4... wiped out my Windows install & made the UEFI unavailable... I had to do a complete re-install of Windows (fortunately, I did the recommended system backup, using 4 DVD's!) so then I tried a (non LVM) install on an external usb 3.0, with the Grub 2 on the external disk (great access time, & it worked fine... IMO)...
One other item: as I have been trying to find the right flavor of Linux for my main purposes, I have been trying various distros. & having to try to learn to negotiate the UEFI, secure/legacy procedures (still learning)... As I was unsure of installing rEFind... I did down load the .iso, burn it to a CD...
http://www.rodsbooks.com/refind/getting.html
& in legacy mode, found that simply putting it (rEFind CD into the CD/DVD player, which in the UEFI it is labeled something like HP/UEFI CD/DVD), & then launching it, rEFind worked for some other distros...that is, I was able to boot into my Linux distros, even bypassing Grub), as well as having the option of booting Windows. It may seem trivial that I say this (it maybe is), but I have not seen anywhere (I have scoured the internet rather well) this mentioned as a possibility (though it, of course, would not make such a good permanent solution, especially for computers like mine that have only one CD/DVD player).
HenryP -
Hi there,
I've recently purchased a W530 with Windows 7 pre-installed. Ultimately, I'd like to replace this with Window 8 + Secure Boot. I believe I can get Windows 8 via the Microsoft Upgrade offer for a reasonable price, since this was a recent purchase.
What's the best way to reach my goal?
The Windows 7 install uses Legacy BIOS to boot with an MBR disk.
I had a quick look at Acronis, and I can see that it's possible that the "OS will be automatically converted to support UEFI booting" (http://www.acronis.com/support/documentation/ABR11/index.html#14021.html) when using it's tool.
If I don't use this approach, what can I do? Can I:
1. Use Rescue and Recovery in Windows 7 (Legacy BIOS/MBR disk)
2. Wipe the drive and reformat it with GPT?
3. Install Windows 7 with UEFI enabled using the Rescue and Recovery made in step 1?
4. At this point, I would now have UEFI and GPT.
5. Perform an Upgrade from Windows 7 to Windows 8 and enable Secure Boot?
Any thoughts as to whether this would work?
Richard.Hi richii,
The Acronis approach ends up in failure. Didn't give it a second look at the reason, since the tool it's not necessary. I also tried several other "automatic" tools without success.
The recovery approach will fail because it's tied up to BIOS boot.
But I've performed the conversion from BIOS to UEFI two times successfully. After some digging, is not SO hard. It's just... "undocumented". Very, very undocumented, hehe. I made a step-by-step guide: http://social.technet.microsoft.com/wiki/contents/articles/14286.converting-windows-bios-installatio...
Let me know if it helps you...
Anyway, if you don't have data/software, I would go for the clean install approach.
Cheers.
If I helped you, please give me some kudos! ^^ -
Booting Arch-ISO from USB-Stick in UEFI mode fails
Hi there,
I'm running an Asrock H77M-ITX UEFI mobo. On this system I've already installed Arch on a Samsung 830 SSD (GPT formatted) - but in BIOS legacy mode because I've written the Arch-ISO image with "dd" to an USB-Stick (and UEFI boot mode wasn't even presented at boot).
Out of curiosity I've re-formatted the stick and copied Arch-ISO following https://wiki.archlinux.org/index.php/Un … B_from_ISO.
Now I could start the ISO in UEFI mode, but it failed to start gummiboot with the "No loader found. Configuration files in \loader\entries\*.conf are needed." error message, concerning a problem with gummiboot.
Following some advice on the forum, I did this:
- install refind-efi 0.4.7-2
- copy /usr/lib/refind/refindx64.efi to [USB]/EFI/boot and renaming it to bootx64.efi (i.e. replacing the original bootx64.efi from gummiboot)
- Create a new file in the same directory ([USB]/EFI/boot/) called refind.conf
- Add this to it:
textonly
scanfor manual
menuentry Arch {
loader /arch/boot/x86_64/vmlinuz
initrd /arch/boot/x86_64/archiso.img
options "gpt loglevel=7 add_efi_memmap none=UEFI_ARCH_x86_64"
With this I can launch Arch-ISO from the USB-Stick in UEFI mode and I can choose Arch from rEFIND. Then Arch-ISO starts booting but it always stops at the same point with this message:
sd 6:0:0:0: [sdb] No Caching mode page present
sd 6:0:0:0: [sdb] Assuming drive cache: write through
sd 6:0:0:0: [sdb] Attached SCSI removable disk
ERROR: '/dev/disk/by-label/' device did not show up after 30 seconds ...
Falling back to interactive prompt
You can try to fix the problem manually, log out when you are finished
sh: can't access tty: job control turned off
[rootfs /]#
sdb is the USB-Stick from which I start Arch-ISO. Again - I didn't use dd to write the ISO to the stick.
Maybe this is pretty easy to solve, but I have to admit that I'm somewhat stuck
Last edited by swordfish (2012-11-19 21:31:43)WonderWoofy wrote:See what the difference is between archiso and archboot maybe? Seriously, have you made any effort whatsoever?
Of course. Read:
The "Main Page" ( https://www.archlinux.org/ ) states:
"You've reached the website for Arch Linux, a lightweight and flexible Linux® distribution that tries to Keep It Simple."
"Keep It Simple". Yeah!
In line with that, the "The Arch Way" page ( https://wiki.archlinux.org/index.php/The_Arch_Way ) states:
"The following five core principles comprise what is commonly referred to as the Arch Way, or the Arch Philosophy, perhaps best summarized by the acronym KISS for Keep It Simple, Stupid."
The ArchWiki ( https://wiki.archlinux.org/ ) links to several other pages, such as these:
The "Forum Etiquette" page ( https://wiki.archlinux.org/index.php/Forum_Etiquette ) states under "Ineffective Discussion":
"Arch is a Do It Yourself community" and "treat others as you would be treated; respect them and their views". I am very much a "do it yourself" person -- that's why I like The Arch Way. I also go by the Golden Rule stated here.
Now, everyone is a newbie at some time. I and other posters here are obviously newbies with respect to ArchLinux. Even experts were newbies at one time. Newbies, by definition, do not necessarily know what they're doing, or where to find information. Hence, Arch's "Beginners' Guide" and such. Hence, posts on this board from newbies asking for help.
As regards initial installation of ArchLinux, and consistent with the above, the FAQ ( https://wiki.archlinux.org/index.php/FAQ ), under "Q) Arch needs an installer. Maybe a GUI installer", states:
"A) Since installation doesn't occur often (read the rest of this article to know more about what rolling release means), it is not a high priority for developers or users. The Installation Guide and Beginners' Guide have been fully updated to use the command-line method. If you're still interested in using an installer, consider using Archboot."
So the basic installation instructions explicitly state that Archboot is not needed.
The "Installation Guide" ( https://wiki.archlinux.org/index.php/Installation_Guide ) says nothing about either Archboot or Archiso.
The "Beginners Guide" ( https://wiki.archlinux.org/index.php/Beginners%27_Guide ) says nothing about either Archboot or Archiso.
The "Archboot" page ( https://wiki.archlinux.org/index.php/Archboot ) is consistent with the above information, because it states:
"Archboot is a set of scripts to generate bootable media for CD/USB/PXE.
It is designed for installation or rescue operation."
The "Archiso" page ( https://wiki.archlinux.org/index.php/Archiso ) states:
"Archiso is a small set of bash scripts that is capable of building fully functional Arch Linux based live CD and USB images. It is a very generic tool, so it could potentially be used to generate anything from rescue systems, install disks, to special interest live CD/DVD/USB systems, and who knows what else."
So the pages describing both Archboot and Archiso clearly state that these tools are oriented towards already-existing installations -- even though it seems that they might be used, in certain circumstances, for initial installations.
I happen to be very new at playing around with installing Linux distros (although I've used Unix/Linux as a regular user for more than 30 years), and am brand new with respect to ArchLinux. I only began playing with it this past Saturday. So I would expect a bit of useful help as opposed to "RTFM!" I will soon get past the need to RTFM for basic tasks, but I have a way to go.
The fact is that for me and a number of other new ArchLinux users, the installation guides simply do not work. C.f. my post https://bbs.archlinux.org/viewtopic.php?id=153170 . I've done a lot of googling as well as searching the archives on this board, and others have come up against the same show-stopping installation problems that I have. I and others have posted to several recent threads on this board, trying to get past the problems, so far with no success.
Now, the.ridikulus.rat had written:
"You guys are using Archboot's kernel options for Archiso. Thats the issue in both the cases."
Given that neither of these sets of scripts were used by me or swordfish, this comment is not useful.
Given the above, can you or anyone else tell us what Archiso or Archboot might do to help us with our installation problems? Also, can you tell us how we, as newbies, ought to have found out how these might help?
Alan -
Rescue & recovery on Win 7 (64bit)
Hi all,
Yesterday I heave format my HDD from Vista Business.
After install Win 7 I was trying to install all utilities which was not a big problem. Only when I want install Rescue & recovery (the newest version 4.31) I got a error with code ''6''. After searching on the web I was not able to find a solution. Even after updating Visual C++ it won't install.
What am I dieing wrong and how must I do it right?
Regards Wim
Ps: Sorry for my bad English trying to do my best better it a bit.what language did you try to install? I was not able to install english version, i had to choose some another language.
Lenovo T440s, 20AQ0067MC, Windows 8.1 Pro x64 UEFI, Samsung 840 EVO SSD 250 GB, 8 GB RAM
Lenovo T430s, 2356LQG, Windows 8.1 Pro x64 UEFI, Intel 520 SSD 180 GB, 8 GB RAM
Lenovo T420s, 4171-6SG, Windows 8 Pro x64 UEFI, Intel 320 SSD 120 GB, 8 GB RAM
Lenovo T400s, 2808-CYG, Windows 7 Ultimate x64 -
UEFI Installation on sdc, Windows 8 partitons on sda gone?
Hi all!
I installed arch on my machine today, now it looks like my windows 8 partitions are gone, maybe someone can help me out.
My setting:
sda Windows 8 uefi installation
sdb ntfs
sdc ntfs and arch uefi installation
So what i did:
I freed up 100GB in sdc for the arch partitions:
[root@chief-pc chief]# sudo gdisk -l /dev/sdc
GPT fdisk (gdisk) version 0.8.7
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/sdc: 1953525168 sectors, 931.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): C82D4B3F-BE8C-4B1F-B3D6-73ED7B839865
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1953525134
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)
Number Start (sector) End (sector) Size Code Name
1 2048 1743808511 831.5 GiB 0700 Basic data partition
2 1743808512 1744873471 520.0 MiB EF00 efi
3 1744873472 1753262079 4.0 GiB 8200 swap
4 1753262080 1953525134 95.5 GiB 8300 root
As you can see I made a new efi partition on sdc, because I did not want to touch sda at all.
Then I installed grub:
mount -t vfat /dev/sdc2 /boot/efi
mkdir /boot/efi/EFI
modprobe dm-mod
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=arch_grub --recheck
grub-mkconfig -o /boot/grub/grub.cfg
Everything went fine, I rebooted my system and it automatically booted into grub instead of win8 (win bootloader should have been standard in my asus uefi bios), so I rebooted again and tried to switch back to win bootloader in asus uefi bios, but the win entry was gone.
So back to arch, my output for sda looks like this:
[root@chief-pc chief]# sudo gdisk -l /dev/sda
GPT fdisk (gdisk) version 0.8.7
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 234441648 sectors, 111.8 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): FFB20C3D-64F8-46F9-9504-C591105405FC
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 234441614
Partitions will be aligned on 2048-sector boundaries
Total free space is 233827181 sectors (111.5 GiB)
Number Start (sector) End (sector) Size Code Name
1 2048 616447 300.0 MiB 2700 Basic data partition
So where are all the win8 partitions? efi, system-reserved and ntfs
I never touched sda during the installation.
Please help me out here
best regards chiefchieffun wrote:
[root@chief-pc chief]# sudo gdisk -l /dev/sda
Disk /dev/sda: 234441648 sectors, 111.8 GiB
Number Start (sector) End (sector) Size Code Name
1 2048 616447 300.0 MiB 2700 Basic data partition
So where are all the win8 partitions? efi, system-reserved and ntfs
I never touched sda during the installation.
First, please verify that this is the correct disk. As Trilby pointed out, disk device names (/dev/sda, /dev/sdb, etc.) can change. There may be a clue in the disk size: 111.8GiB. If both /dev/sda and /dev/sdb were identical, that might not be enough of a clue; but if your disks all had unique sizes, the disk size should tell you which one is which.
Second, the type code 2700 refers to a Windows Recovery Environment (RE) partition. This suggests that this partition is an emergency partition, and the size of 300MiB seems consistent with that. OTOH, the partition name of "Basic data partition" suggests something else. The fact that the one partition fills far less than the entire disk is not a good sign. You could try using "blkid" on the partition in Linux to see what its filesystem type is, and perhaps mount it to examine its contents.
Finally, try using gdisk's recovery features. You can start with the "-v" option to perform a check on the GPT's integrity. It's conceivable that this will report a problem that you'll then be able to correct in one way or another. You could also play with the options on the gdisk recovery & transformation menu (type "r" at the main menu to get here). In particular, it's conceivable that the "c" option on that menu will help; it loads the backup partition table and uses it in preference to the main one. If you use that option and it restores your partitions, save your changes with "w".
WonderWoofy wrote:The manual nature of the Arch Linux installation means that you (should) know exactly what you are implementing and what it is doing. So the only way that Arch Linux can wipe out another system is if the administrator (you) wipes them out.
I agree. Some inadvertent action that you haven't reported must be responsible for these problems. It's conceivable that the action was in another distribution's installer or even in Windows.
WonderWoofy wrote:The only thing you can try is to see if you can use some kind of partition recovery software. There are some out there that can (somewhat reliably) detect where the start and end points of the old partitions were, and regenerate the partition table for you. The other type of recovery software is those that scan the device and try to recover individual lost files. Some of them do both. You should probably start reading up on them.
In Linux, the TestDisk utility can scan for missing partitions, while PhotoRec can scan for lost files. I gather there are better Windows tools for scanning for lost files on NTFS volumes, but I don't happen to have any pointers. TestDisk tends to do a decent job, but it's a bit confusing to the uninitiated, and it can become hopelessly confused if the disk has been repartitioned a lot in the past.
chieffun wrote:So I thought that maybe arch does not like 2 efi partitions in one system and corrupted it somehow.
No, that can't be it. As cfr says, Windows doesn't like multiple ESPs; but that's mostly an issue for the Windows installer. (It tends to get confused and aborts halfway through the installation.) I'm not even sure if Windows misbehaves in this way when the ESPs are on different disks; it might handle that situation OK, for all I know. Windows certainly doesn't go postal on its own partitions if it sees two ESPs. That said, it's conceivable that a Windows bug did cause this problem, if you booted Windows at some point during the process.
chieffun wrote:I also tried to rescue with parted rescue command and gpart, looks like something completely wiped (or corrupted) the partitions away. As if they have never been there in the first place...
In my experience, the partition rescue features of GParted and parted are unreliable at best. TestDisk does a much better job. -
Not able to start Rescue and Recovery
Unfortunately I have installed Windows Vista on my own, not using this Vista on my Service Partition. This Partition is not deleded. Now I want to install form this Service Partition. I have installed Rescue and Recovery. I am abel to start the Rescue and Recovery program using the blue button THINKVANTAGE while booting. I selected to get the factory-provided installation. The system reboots and then tells: Boot Disk Failure.
Once again: The partition isn't deleted.
I hope you can help me
Sincerly yours
ColinCheck out BIOS setup (boot mode). For using Recovery media that mode should be Legacy/MBR, not UEFI/GPT.
x220 | i5-2520m | Intel ssd 320 series | Gobi 2000 3G GPS | WiFi
x220 | i5-2520m | hdd 320 | Intel msata ssd 310 series | 3G GPS | WiFi
Do it well, worse becomes itself
Русскоязычное Сообщество English Community Deutsche Community Comunidad en Español -
GRUB loads but get thrown into rescue shell without any errors
I forgot to read the news before I did an upgrade for the first time in a long time and borked my system because of the filesystem update.
Used to get Arch news by mail with a RSS forwarder, but the service I used shut down and I forgot to sign up for another one.
Used chroot and it seems like I fixed the filesystem and bash packages with all the related symlinks, and I did mkinitcpio -p linux and got no errors.
However when I boot I get directly thrown into GRUB rescue shell without any errors. Tried to reinstall GRUB but didn't change anything.
Read GRUB - GRUB UEFI drops to shell, but I still have a grub.cfg. I believe I just have a pretty standard GRUB2 installation, however I'm not really since it's a long time since I installed it and it was a lot of back and forth because I tried a lot of combinations of GPT/MBR and GRUB/Syslinux since my HP ProBook 6460b laptop has UEFI. If more information is needed about my current GRUB install please do ask, chroot is working just fine.
My system is updated and I'm using systemd.
What should I do to fix my boot/GRUB?
Also, I'm not sure if it's relevant, but when I try to run a Lubuntu LiveCD (same arch as my Arch install) it fallbacks to BusyBox with the error "unable to find a medium containing a live file system".
It's still a fully working TTY so I haven't bothered to research further why. Maybe just a corrupt usb memory drive (setup).
Last edited by Occi (2013-08-10 17:40:59)unilx wrote:You can manually create a grub.cfg file, the wiki has a detailed section on this, just Google: "arch linux manually creating grub.cfg"
This might be the fix, but I'm not sure what I did that could've changed it. Anyway, I'm tired of having to use time maintaning my system just for a simple update and switching to Debian testing. Learning alot playing around with Arch, but the last half year or so have just felt like a big hazzle with all the (in my opinion) unecessary changes and distancing from it's BSD-like roots and KISS (systemd and all that jazz). -
[SOLVED] UEFI with gummiboot: somtimes (!) just black screen
Hi,
since two days I'm trying to get UEFI work on my Lenovo T420. The problem is that there's only a black screen when activating the "Arch Linux" entry in gummiboot if I have not plugged in the installation medium (as a USB drive). If it's inserted sytemd starts booting but stops at a certain point complaining there are starting jobs running on /dev/sdc (the USB drive); then I get to the rescue shell. If it's not inserted there's just a black screen. To start the system I have to leave the USB drive plugged in and fastly remove it when systemd starts booting after selecting "Arch Linux" in gummiboot. I don't know why, but the system does boot then.
This is what I have done:
In BIOS I changed the settings that it's booting with UEFI "and" BIOS at least trying first BIOS and then UEFI. I followed the installation instructions of the Beginner's Guide (https://wiki.archlinux.org/index.php/Beginners%27_Guide) installing a system with LVM (ensuring that the install medium is booted in UEFI). I followed the recommendations of https://bbs.archlinux.org/viewtopic.php … 3#p1240883 concerning partitioning. This is the setup I have:
niklaas@len-t420-arch ~ % lsblk --output +UUID
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT UUID
sda 8:0 0 238,5G 0 disk
├─sda1 8:1 0 100M 0 part
└─sda2 8:2 0 238,4G 0 part
sdb 8:16 0 119,2G 0 disk
├─sdb1 8:17 0 512M 0 part /boot D3F0-DA3E
├─sdb2 8:18 0 512M 0 part d66ae708-051f-43f8-bae8-b35a985cd75f
└─sdb3 8:19 0 118,2G 0 part Loovu6-pH7j-Ou8r-HiH0-yJFm-Riq7-Pbsi4s
├─VolGroup00-lvroot 254:0 0 25G 0 lvm / 349e5a88-72ca-40cb-8e44-0b67b85ffee4
├─VolGroup00-lvvar 254:1 0 15G 0 lvm /var 46980ec6-f2f3-4a08-a350-f6621a23054f
├─VolGroup00-lvswap 254:2 0 8G 0 lvm [SWAP] 156243f8-f374-4e27-86f0-d442850c6c3f
└─VolGroup00-lvhome 254:3 0 70,2G 0 lvm /home ae86bb5c-2829-4af9-9ffb-0206d10f02a4
(/dev/sda is Windows 7)
Please note that I /dev/sdb1 is the EFI System Partition and there's also another partition (/dev/sdb2) I created just in case I want to use a separate /boot partition. (Currently there's syslinux on it because I was experimenting whether I get the system to boot normaly, which means without the USB drive, by using Legacy BIOS and syslinux. But I was not successful: Screen also stays black.) This is what /boot looks like and the contents of /boot/loader/entries/arch.conf and /boot/loader/loader.conf:
niklaas@len-t420-arch ~ % tree /boot
/boot
├── EFI
│ ├── BOOT
│ │ └── BOOTX64.EFI
│ └── gummiboot
│ └── gummibootx64.efi
├── initramfs-linux-fallback.img
├── initramfs-linux.img
├── loader
│ ├── entries
│ │ └── arch.conf
│ └── loader.conf
└── vmlinuz-linux
niklaas@len-t420-arch ~ % cat /boot/loader/entries/arch.conf
title Arch Linux
linux /vmlinuz-linux
initrd /initramfs-linux.img
options root=UUID=349e5a88-72ca-40cb-8e44-0b67b85ffee4 rw
niklaas@len-t420-arch ~ % cat /boot/loader/loader.conf
timeout 3
default arch
Additionally to the strange USB-drive-needs-to-be-plugged-in issue there is another one: Because there's a Windows 7 installation (unfortunately I need it) on /dev/sda with Truecrypt I decided to install two bootloaders: one is on /dev/sda and the other one on /dev/sdb. So I can "manually" switch between operating systems by using the boot manager that is provided by the BIOS of the motherboard which makes it possible to change boot priority quite simply. After the installation of gummiboot there was (of course) another entry created, so there are three:
1. Linux Boot Manager
2. ~first SSD (with Windows; /dev/sda)
3. ~second SSD (with Arch Linux; /dev/sdb)
When I select the first entry, even the USB-drive-trick does not work. There just resides the black screen. This I do not understand at all because, as already described above:
If I select the third option, gummiboot gets loaded and I can select "Arch Linux". Then, as already mentioned, there are three options: (a) USB-drive is inserted > I plug it off immediately after systemd starts > system boots (b) USB-drive is inserted > I don't (!) plug it off > systemd complains about starting job running on /dev/sdc > I get the rescue shell (c) USB-drive is not (!) inserted > I just get a black screen.
I hope the issue I have is quite understandable. Otherwise, please ask and I'll try my best to clarify things. Any help is really appreciated,
Niklaas
niklaas@len-t420-arch ~ % uname -a
Linux len-t420-arch 3.10.6-2-ARCH #1 SMP PREEMPT Tue Aug 13 09:47:01 CEST 2013 x86_64 GNU/Linux
Last edited by niklaas (2013-08-18 07:02:01)srs5694 wrote:My hunch is that you're running into the bug that's under discussion here. If so, you may be able to get it working more reliably by switching boot managers (to rEFInd or to the version of rEFInd that's built with GNU-EFI) or boot loaders (to GRUB or ELILO).
OK. I decided to use syslinux and installed it from the AUR. After installation was successfull, I copied all files as described in https://wiki.archlinux.org/index.php/UE … LINUX_6.xx to /boot/syslinux and ran command
# efibootmgr -c -d /dev/sdb -p 1 -l /EFI/syslinux/syslinux.efi -L "syslinux"
to create an entry. And I could just successfully boot without USB-drive. Thank you.
cfr wrote:I don't know why it would work at all in this case but are you sure that you can specify root= like that on the command line? Rather than e.g. root=/dev/VolGroup00/lvroot, for example?
I guess, I also tried this before having the same outcome.
But I still do not understand what's happening when I select my second SSD; because there's still gummiboot loaded and I can still boot the system with the USB-drive. Does anybody know what's happening there? I'm totally clueless why the system is somehow accessing the flash drive?!
Last edited by niklaas (2013-08-18 07:02:31) -
Grub, UEFI, and encrypted partitions
I followed the tutorials on the Wiki regarding setting up luks encryption over LVM which worked fine. Part of this process involved getting grub to decrypt the root partition, which also worked. However, I later went and followed instructions for getting UEFI boot to work; I created a separate /boot partition, used grub-install, etc. I'm now in a weird state, though: grub is still using (and unlocking) the root partition and using whatever is in its /boot directory when it really should be using the /boot partition. I've managed to confuse myself enough through all this that I'm not sure what config files and commands I need to mess with to get grub to load the initramfs from the actual boot partition while not also screwing up the root partition that should be unlocked/mounted by systemd.
My common sense tells me that the latter has nothing to do with the former but it took me long enough to figure out the hack of copying everything in the boot partition to root's /boot just to get the thing booting again after a kernel update that I'd rather just ask heretcdavis wrote:I'm now in a weird state, though: grub is still using (and unlocking) the root partition and using whatever is in its /boot directory when it really should be using the /boot partition.
UEFI and a dedicated /boot partition are separate things, and they are not dependent on one another. The problem is most likely coincidental.
Make sure your "root=" and "cryptdevice=" kernel parameters are correct. Edit /etc/default/grub, and use the UUID of the LUKS container on the new /boot partition, replacing the old UUID of the root filesystem. This should be the UUID of the LUKS container itself, not the filesystem contained within it. Use `cryptsetup luksUUID /dev/sda2` substituting sda2 with your /boot partition. This only applies to the kernel and is not directly related to GRUB, so it's just a precautionary measure.
Make sure /boot is mounted, and regenerate grub.cfg:
mount /boot
grub-mkconfig -o /boot/grub/grub.cfg
Delete the contents of /boot on the root partition to prevent confusion:
umount /boot
rm -r /boot
mkdir /boot
mount /boot
Also make sure your /boot partition is being mounted (via crypttab and a keyfile) automatically at boot, or you will run into problems later on.
Strike0 wrote:If you, in your first attempt, installed grub to the MBR and your bios is set to dual legacy/uefi, the grub bios may take precedence now. You should boot the machine/install ISO in pure efi mode before executing the grub install for uefi and best wipe the grub bios which probably installed itself to sectors before the first partition.
I don't know enough about the GRUB internals to say whether or not the UUID of the /boot partition is embedded in GRUB's UEFI stub, but in theory the following commands should overwrite both the BIOS boot loader and UEFI.
mount /boot
grub-install --target=i386-pc --recheck
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=grub_uefi --recheck
This way GRUB should use the correct /boot no matter if it is booting in BIOS or UEFI mode.
If these instructions don't solve your problem, please specify what stage of the boot process is failing, and what you saw prior to the boot failure (e.g. did you get a GRUB rescue shell? Did you see the GRUB menu? Did GRUB indicate an incorrect UUID?) -
Boot rescue after first install
Hi all,
i've installed arch on my laptop but i've a broblem after the first boot...
This is my system configuration: SSD+GPT+BIOS(not UEFI)
I've follow the beginne's guide...
I've created the GPT partition table with gdisk with 'o'.
I've aligned the disk at 6144 (best for my Samsung 840 evo).
I've created the first partition of 2MB with code ef02 for boot, 2nd partition 225GB for / (root) and 3rd partition for swap.
I've closed gdisk with 'w' for write the scheme, this output no errors...
I've installed the system and configured them but when i install the grub2 this output me this error:
https://www.dropbox.com/s/yagajwmycl1ax … 4.jpg?dl=0
What's wrong i do?
Thanks all and sorry for my english ;-)
PS: This is not the 1st time i've installed arch linux...Thank you for reply!
I've installed again the system to start! :-(
At this time, for installing the grub, i've used this command:
#grub-install --target=i386-pc --recheck --debug /mnt/sdc
This output with no error!!! But when i restart the system the problem it's the same!
error: no such device: 3d95f99c-bla bla...
Entering rescue mode...
Through an ubuntu live: (arch installed device is sdb)
sudo blkid
/dev/loop0: TYPE="squashfs"
/dev/sda1: LABEL="Storage" UUID="158d9c57-60fd-4385-8624-5d4a0ea65353" TYPE="ext4" PARTUUID="000d6c9e-01"
/dev/sdb1: PARTUUID="46ef1da0-44dd-4549-81d9-e49494d9ea92"
/dev/sdb2: UUID="4b3df82d-8e9a-4f0c-9dd6-a6a863e2f1b6" TYPE="ext4" PARTUUID="c33a0ea0-b5bd-45a6-9642-704100589f2c"
/dev/sdb3: UUID="837b4fa3-19f1-4f69-a309-da02eab308e6" TYPE="swap" PARTUUID="7fb8d6b5-d97f-4326-b737-41b677b678ea"
/dev/sdc1: UUID="2014-07-22-22-36-29-00" LABEL="Ubuntu 14.04.1 LTS amd64" TYPE="iso9660" PTUUID="1b45097d" PTTYPE="dos" PARTUUID="1b45097d-01"
/dev/sdc2: SEC_TYPE="msdos" UUID="E63C-163E" TYPE="vfat" PARTUUID="1b45097d-02"
sudo lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 698.7G 0 disk
└─sda1 8:1 0 698.7G 0 part
sdb 8:16 0 232.9G 0 disk
├─sdb1 8:17 0 2M 0 part
├─sdb2 8:18 0 225G 0 part /
└─sdb3 8:19 0 7.9G 0 part [SWAP]
sdc 8:32 1 14.9G 0 disk
├─sdc1 8:33 1 981M 0 part
└─sdc2 8:34 1 2.3M 0 part
loop0 7:0 0 938.7M 1 loop
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sdc2
UUID=4b3df82d-8e9a-4f0c-9dd6-a6a863e2f1b6 / ext4 $
# /dev/sdc3
UUID=837b4fa3-19f1-4f69-a309-da02eab308e6 none swap $
This is the grub.cfg of the installation:
# DO NOT EDIT THIS FILE
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_gpt
insmod ext2
set root='hd2,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd2,gpt2 --hint-efi=hd2,gpt2 --hint-baremetal=ahci2,gpt2 4b3df82d-8e9a-4f0c-9dd6-a6a863e2f1b6
else
search --no-floppy --fs-uuid --set=root 4b3df82d-8e9a-4f0c-9dd6-a6a863e2f1b6
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_input console
terminal_output gfxterm
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=5
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch Linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-4b3df82d-8e9a-4f0c-9dd6-a6a863e2f1b6' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
set root='hd2,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd2,gpt2 --hint-efi=hd2,gpt2 --hint-baremetal=ahci2,gpt2 4b3df82d-8e9a-4f0c-9dd6-a6a863e2f1b6
else
search --no-floppy --fs-uuid --set=root 4b3df82d-8e9a-4f0c-9dd6-a6a863e2f1b6
fi
echo 'Loading Linux linux ...'
linux /boot/vmlinuz-linux root=UUID=4b3df82d-8e9a-4f0c-9dd6-a6a863e2f1b6 rw quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-linux.img
submenu 'Advanced options for Arch Linux' $menuentry_id_option 'gnulinux-advanced-4b3df82d-8e9a-4f0c-9dd6-a6a863e2f1b6' {
menuentry 'Arch Linux, with Linux linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-advanced-4b3df82d-8e9a-4f0c-9dd6-a6a863e2f1b6' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
set root='hd2,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd2,gpt2 --hint-efi=hd2,gpt2 --hint-baremetal=ahci2,gpt2 4b3df82d-8e9a-4f0c-9dd6-a6a863e2f1b6
else
search --no-floppy --fs-uuid --set=root 4b3df82d-8e9a-4f0c-9dd6-a6a863e2f1b6
fi
echo 'Loading Linux linux ...'
linux /boot/vmlinuz-linux root=UUID=4b3df82d-8e9a-4f0c-9dd6-a6a863e2f1b6 rw quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-linux.img
menuentry 'Arch Linux, with Linux linux (fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-fallback-4b3df82d-8e9a-4f0c-9dd6-a6a863e2f1b6' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
set root='hd2,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd2,gpt2 --hint-efi=hd2,gpt2 --hint-baremetal=ahci2,gpt2 4b3df82d-8e9a-4f0c-9dd6-a6a863e2f1b6
else
search --no-floppy --fs-uuid --set=root 4b3df82d-8e9a-4f0c-9dd6-a6a863e2f1b6
fi
echo 'Loading Linux linux ...'
linux /boot/vmlinuz-linux root=UUID=4b3df82d-8e9a-4f0c-9dd6-a6a863e2f1b6 rw 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/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
### BEGIN /etc/grub.d/60_memtest86+ ###
### END /etc/grub.d/60_memtest86+ ### -
Arch drops me to a rescue shell after kernel update
Hello everyone,
I am an Arch newbie and glad if you hold my hand for a little on this one.
Last night I did my first
pacman -Syu
and among others it also updated my kernel to whatever kernel currently in the repositories is. After that I rebooted my Linux box and yes I forgot to update my /boot/efi/EFI/arch first; now it says it can't properly read from my /boot and drops me to a rescue shell.
I have a UEFI motherboard and during installation I followed the EFISTUB instructions in the wiki; using that everything booted flawlessly on my first attempt.
So far I managed to boot from my trusted SystemRescueCD. I can access the Arch documentation via web browser in an X11 environment and I can cleanly mount my partitions and chroot, but I am troubled by the output I am seeing. The obvious solution to my newbie problem would be to go through the EFISTUB instructions in the wiki again, but I have no clue where my boot file sources are. Check this:
root@sysresccd /root % mkdir /mnt/arch-root
root@sysresccd /root % mkdir /mnt/arch-root/boot
root@sysresccd /root % mount /dev/sdc3 /mnt/arch-root
root@sysresccd /root % mount /dev/sdc1 /mnt/arch-root/boot
root@sysresccd /root % ls -al /mnt/arch-root/boot
total 12
drwxr-xr-x 3 root root 4096 Jan 1 1970 .
drwxr-xr-x 20 root root 4096 Mar 6 19:11 ..
drwxr-xr-x 5 root root 4096 Feb 27 20:00 EFI
root@sysresccd /root % ls -al /mnt/arch-root/boot/EFI
total 20
drwxr-xr-x 5 root root 4096 Feb 27 20:00 .
drwxr-xr-x 3 root root 4096 Jan 1 1970 ..
drwxr-xr-x 2 root root 4096 Feb 27 19:55 arch
drwxr-xr-x 3 root root 4096 Feb 27 20:00 boot
drwxr-xr-x 3 root root 4096 Feb 27 19:51 refind
root@sysresccd /root % ls -al /mnt/arch-root/boot/EFI/arch
total 20576
drwxr-xr-x 2 root root 4096 Feb 27 19:55 .
drwxr-xr-x 5 root root 4096 Feb 27 20:00 ..
-rwxr-xr-x 1 root root 14291050 Feb 27 19:47 initramfs-arch-fallback.img
-rwxr-xr-x 1 root root 3083850 Feb 27 19:47 initramfs-arch.img
-rwxr-xr-x 1 root root 164 Feb 27 19:55 refind_linux.conf
-rwxr-xr-x 1 root root 3675776 Feb 27 19:46 vmlinuz-arch.efi
root@sysresccd /root % ls -al /mnt/arch-root/boot/EFI/boot
total 184
drwxr-xr-x 3 root root 4096 Feb 27 20:00 .
drwxr-xr-x 5 root root 4096 Feb 27 20:00 ..
-rwxr-xr-x 1 root root 154688 Feb 27 20:00 bootx64.efi
drwxr-xr-x 2 root root 4096 Feb 27 20:00 icons
-rwxr-xr-x 1 root root 17452 Feb 27 20:00 refind.conf
root@sysresccd /root % ls -al /mnt/arch-root/boot/EFI/refind
total 184
drwxr-xr-x 3 root root 4096 Feb 27 19:51 .
drwxr-xr-x 5 root root 4096 Feb 27 20:00 ..
drwxr-xr-x 2 root root 4096 Feb 27 19:51 icons
-rwxr-xr-x 1 root root 17452 Feb 27 19:50 refind.conf
-rwxr-xr-x 1 root root 154688 Feb 27 19:50 refind_x64.efi
root@sysresccd /root %
Why are there no vmlinuz-linux, initramfs-linux.img, and initramfs-linux-fallback.img in my /mnt/arch-root/boot ?
Why is there an EFI/* in my /mnt/arch-root/boot and not the efi/EFI/* I expect to find? It's as if one level of the file hierarchy is missing... if I mounted something incorrectly, I'd expect an empty mount point, but this phenomenon of having something but not everything really puzzles me.
The rest seems ok as it was Feb27 when I did my intital installation of Arch and Mar6 when I did the pacman -Syu
Thanks for any help, I am really clueless right now.Thanks for the reply.
I've already installed the virtualbox-archlinux-additions.
So after the kernel update there's nothing i need to do ?
Maybe you are looking for
-
Fiscal year 2010 Not allowed while creating Process order in COR1
Dear Friends, We have gone SAP live in the month of October. The fiscal yeat we are using is 2011 as the client is Indian client. I have made the fiscal year variant for 2011 (V3). The FI document posting with Fiscal year 2011. It is also creating th
-
I am trying to config my local OC4J to be able to execute my applications the same way I do it using the application server. If I execute from builder one module works fine, but If I wan to use web.show_document it didn't work. It sends me Teh page c
-
Image of e-mail sender not appearing in e-mail even though it's in Contacts
From Gizmodo: "If you receive an email from a person who has a picture in your contacts, you'll now see a tiny image of him or her in the corner." Sometimes I see the image, but most of the time I do not. And, yes, I confirmed that the image does app
-
Why do my mycloud makes up to 35 icons of the same movie in public movie libory on every streaming divices ?BRKnastaksel
-
I scanned a neg in bw, and it shows small black dots. I tried dust&scratch filter and in the preview the dots disappear, but clicking ok, ps does its calculations and after that the image still have those dots. Clicking undo and redo doesn't have any