[SOLVED] rm'ed /boot...

long story short:
Arch wasn't booting for another reason (e2fsck aborted or something). I have Debian and Ubuntu as backups. I booted into ubuntu to fix the problem. Instead of doing that, I rm'ed /boot. As you might imagine, the situation with Arch is worse than before. Any ideas about restoring /boot? or backup my crap, do a fresh install, and then replace all my old stuff except /boot?
Ubuntu and Debian are still alive and kicking, and the partitions are all mountable from there, so no serious data recovery issues; just a highly customized Arch install that I don't relish rebuilding (mostly because I had a lot of AUR stuff).
Last edited by ninjaaron (2012-01-06 00:34:43)

Thanks guys! chroot'ed from Ubuntu according to gregor's instructions and it worked. One note: I have a separate /boot partition, so I also had to mount that before reinstalling linux, syslinux, and grub(2, in my case). I didn't do it at first, and when I reinstalled linux, it told me that I had broken my system, so I mounted /boot at did it again and everything seems to be kosher.
Anyway, I'm posting from Arch. Thanks again to all, especially ngoonee and gregor!
Awebb wrote:You could also try testdisk and/or photorec to recover the lost data.
These are great apps, I'd agree, but my personal data is fine, and the only real issue was getting /boot back, which is sort of an all-or-nothing gig. Simply chroot'ing and reinstalling the programs that populate /boot was a perfect solution.
Last edited by ninjaaron (2012-01-06 00:25:31)

Similar Messages

[SOLVED] Error while booting, related to nilfs2

I've just installed my fresh Arch and used nilfs2 inside vlm2 as my home partition. While booting, I'm getting these errors:
fsck: fsck.nilfs2: not found
fsck: error 2 while executing fsck.nilfs2 for /dev/mapper/TheVG-HomeLV
Other logical volumes are getting "clean" output while checked so it's not vlm-related; they are all ext4.
Partition is mounted and seems to work but I'm scared of just ignoring it and creating my user. ;-)
I have nilfs-utils installed. Is there any hook or module I need to add somewhere in order to use nilfs2 properly (like reiserfs hook)? There is nothing in the Wiki about this file system...
Edit: well, it appears that nilfs doesn't not come with check utility so I'm marking this as solved; sorry for garbage post...
Last edited by smsware (2013-03-16 22:07:55)

As there is no fsck utility and as it actually is planned to be created (I read that it's needed because the fs can easily crash on power loss; still, it can be recreated, as you stated) - there is a warning while building the kernel. I deleted fsck hook to not see it as my /var and root are sub-volumes of btrfs partition which doesn't need fsck as well. I made a service to umount, fsck and mount back the /boot (ext4) and uefi partitions... just to let you know what you can expect. But it's great anyway, snapshots are really easy to mount and use. I thought it has no wiki page because it's not popular (and probably for a reason) but now I believe it's because there is nothing to write about... it just works. ;-)
Last edited by smsware (2013-05-29 15:58:26)

[SOLVED] Unable to Boot Windows 7 from GRUB

I recently reinstalled Arch onto my laptop (Lenovo Thinkpad t520) and have been having problems with Grub. For the last week I've been having trouble getting it to run grub at boot at all, only being able to run windows 7 by flagging it as the bootable drive. The other day I finally got it to boot into grub, and from grub I can boot into Arch. However, I can not boot into windows 7 through grub. When I attempt to, it throws an error:
Invalid EFI file path
I'm somewhat new to arch, and especially new to efi bootloading and such. Right now the only way I can get into windows is either booting from the arch install disk > boot other os and specifying partition 2 (where I have windows installed) or by pressing f12 at boot. When I do this (not sure what the term is, if anyone knows please tell me), it brings up a menu asking where I want to boot with "arch_efi" "cd drive" "Hard drive" etc. I choose hard drive and it will then boot to windows by default. Booting normally takes me to grub where I can boot into arch but not windows. If there's any more info you need please let me know and I'll try to provide it. Thanks in advance.
Also, here is my current partition setup
/dev/sda1 /boot/efi
/dev/sda2 Windows7
/dev/sda3 Extended partition containing sda 5,6, & 7
/dev/sda4 swap
/dev/sda5 /boot
/dev/sda6 /
/dev/sda7 /home
UPDATE
Terminator seems to be right (still on a roll!), so I wiped the partition I had grub on, removed grub, and installed syslinux. Now I have another problem that I'm hoping can be solved in the same thread to avoid another. It boots to syslinux no problem, and I can boot to windows from there all good, but when I select arch I get:
Root device mounted successfully but /sbin/init does not exist
I haven't been able to look for solutions too much on my own, but any help would be appreciated, thank you.
Last edited by IamFuzzles (2012-08-22 04:20:56)

Terminator wrote:If I understand it correctly, what you are trying is impossible: you are trying to boot windows using UEFI on a disk with MBR partitioning. Windows 7 only supports UEFI on discs with GPT partitioning but AFAIK, extended partitions only exist in MBR partitioning.
i also saw this in the arch wiki, but i have a brand new lenovo ideapad y570 running windows 7 64-bit that i'm in the process of setting up for someone, and it has what i think is an efi system partition but the disk uses mbr partitioning. does anyone know why this might be, or is there a way i can verify that the system is actually being booted via bios-mbr?
Last edited by e_tank (2012-08-21 11:56:15)

[SOLVED]Unable to boot in UEFI mode from CD

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

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

[SOLVED] Unable to boot after update

After full system upgrade my arch is unable to boot kernel:
ERROR: device 'UUID=xxx...' not found, skipping fsck.
ERROR: unable to find root device 'UUID=xxx...'
You're being dropped to a recovery shell
I'm pretty sure UUID of /dev/sda2 is correct (double checked with Ubuntu live cd).
Last edited by soroush (2012-09-06 12:20:15)

Then you need to provide more information. Bootloader? Kernel? Tried fallback initramfs?
Edit: OK, you solved it. pacman does regenerate the initramfs if the kernel is updated. It just didn't work for you this time.
Last edited by progandy (2012-09-06 12:21:55)

[SOLVED]Unable to boot from SATA, but it works from USB

I have strange problem. I made an Arch installation in VMware virtual computer and then I copied the virtual disk to new SSD. When I install the disk into the real hardware (Intel Canoe Creek D2500CC board), i get the "ERROR: Unable to find root device '/dev/sda1'." error.
The strange thing is, that the computer can boot correctly, when I connect the SSD using SATA->USB bridge.
In the recovery shell there are no disk devices (/dev/sd*) so I think it is not a problem of changed device name (f.e. /dev/sdb1 instead of /dev/sda1), to me it looks like udev is not running.
What can be the problem, that the system boots normally when SSD is connected via USB and can not boot when connected directly to SATA port?
My mkinitcpio.conf:
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES=""
# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image. This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way. This is useful for config files.
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
## This setup specifies all modules in the MODULES setting above.
## No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
## This setup will autodetect all modules for your system and should
## work as a sane default
# HOOKS="base udev autodetect block filesystems"
## This setup will generate a 'full' image which supports most systems.
## No autodetection is done.
# HOOKS="base udev block filesystems"
## This setup assembles a pata mdadm array with an encrypted root FS.
## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
# HOOKS="base udev block mdadm encrypt filesystems"
## This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev block lvm2 filesystems"
## NOTE: If you have /usr on a separate partition, you MUST include the
# usr, fsck and shutdown hooks.
HOOKS="base udev autodetect modconf block filesystems keyboard fsck"
# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""
Last edited by MaVac (2014-08-15 05:55:18)

MaVac wrote:Problem solved! :-) I made update with pacman -Su and then everything is working perfectly. :-)
Then please mark the thread as solved as well.

[Solved] Unable to boot after install

Forgive me for the lack of code tags, having to write this on my phone.
I am unable to boot after installation. I receive an error wich has the incorrect UDID string. It doesn't even exist. I will update with error after posting so I can give grub config generation error first
When I run:
grub-mkconfig -o /boot/grub/grub.cfg
I get this:
Found Linux image : /boot/vmlinuz-linux
Found initd image: /boot/initramfs-linux.img
Warning: failed to connect to lvmetad: no such file or directory. falling back to internal scanning.
No volume groups found
[ 279.601712] SQUASHFS error: can't find a SQUASHFS superblock on sda3
[ 279.604502] EXT4-fs (sda3):unable to read superblock
[ 279.607266] EXT4-fs (sda3):unable to read superblock
[ 279.609928] EXT4-fs (sda3):unable to read superblock
Found Windows 7 (loader) on /dev/sda1
Done
Sda3 is an extended volume
Edit: I just deleted the old .cfg and recreated a new one by re running the above command, uncounted and rebooted and it booted into CLI. 3rd time a charm after all. Marking this one solved
Last edited by Kirito (2013-05-15 07:55:31)

Oh, looking at your setup, it would seem that your system is likely still configured to boot to /dev/sdd (the windows drive).
As a user with numerous drives, you should be aware that using /dev/sdXY to identify your disks is a bad idea. There is no gaurantee that Arch will be /dev/sde every time, nor that windows will be /dev/sdd. You should use either filesystem labels (LABEL= or /dev/disk/by-label) or UUIDs (UUID= or /dev/disk/by-uuid). Though if you are using GPT, there is also the option of the PARTLABEL as well (which are the labels you create within the partitioner).

[SOLVED]Can't boot into OS after installation

Hello all,
I've ran into a few problems already all of which I could solve with somme googling etc.
Until now the installation of arch Linux went pretty smoothly until I rebooted to get into the OS via grub (version 2), once I select Arch Linux in the menu the os starts booting but it stops at this: "a start job is running for dhcpcd on enp7s0 (x s/1m31s)" this always fails. After that 3 extra lines appear starting with a green OK all saying reached target ..........
This is where no more progress is made, the only keys that generate a response are Ctrl+alt+Del then the system reboots.
Here is a clear image of the status of the machine
https://i.imgur.com/queQkEOh.jpg
EDIT: If you guys need any extra information please ask, but I can't access the systems config files or anything due to this problem so suggestions on how to pull that data are welcome
-- mod edit: converted img tags to url - Trilby --
Last edited by Covati (2014-10-06 13:04:05)

Trilby wrote:
Welcome to the forums - please see the forum guidelines on how to post including image size restrictions.
As for the issue - can you Alt-F2 or Alt-F3 to get to another tty?
It worked, wow I feel dumb now.
Anyways thank you for helping me out, I will look into the guidelines.
Can mark this thread as solved!

[Solved] MSI 965P boot message ODD0:HL-DT-ST DVDRAM GSA-4167B

My dear friends,
I have just bought MSI 965P Neo-f and at every boot I get a message “ODD0:HL-DT-ST DVDRAM GSA-4167B. I’m absolutely sure that I have the right settings for the IDE-Cable and the Jumper setting on the DVD/RW is set to master (also I have tried the other two settings for SL and CS).
Therefore the DVD/RW couldn’t be recognized in the BIOS , my DVD/RW works only in PIO mode(no way to force it in DMA) and I have conflicts and a really awful performance with my Windows XP SP2 ???.
Please help if someone already solved this problem.

I actually had a bad installation of the jmicron driver in Windows . I have also connected my HDD on the jmicron SATA controller ,and SiSoft Sandra reported that it’s working in UDMA-6 mode,just cannot see if my DVD/RW drive works also in DMA mode. I have tried with Nero Info tool , but since all my drives are now connected on the SCSI controller, there is no such information. Any suggestions?....

[SOLVED] Can only boot Arch via CD

Hi all,
I've installed 64 bit Arch on the 2nd hard drive of a Dell Optiplex 980.
It works very nicely, but I have a strange boot issue:
If I boot from the Arch CD, and select "Boot other OS", hit Tab, and manually edit the grub line to "chain.c32 hd 1 0", I am taken to the grub menu on the hard drive and can select my install which boots and runs fine.
If I select the 2nd HD in the BIOS boot menu (instead of the CD), I get to the same grub menu, but upon selecting my install, I get an Error 17.
Has anyone run into this before?
Thanks in advance!
Last edited by basementhead (2010-09-24 17:52:11)

Turns out I misunderstood how grub works.
When I changed my menu.lst to (hd 0,0) it works.
I thought that the 2nd drive was (hd 1,0), which was reinforced by the boot CD working with (1,0), but I guess the drives are renumbered when you boot from CD?
The big clues were that the partition that grub said couldn't boot was 0xde (a Dell partition), and I was sure I'd wiped the entire drive, but I knew that the 1st drive was a default Dell/Windows7 install.
Then using grub command line menu, I typed "find /sbin/init" and it found it on (hd0,2), and the mystery was solved....
Anyway - fixed by treating the drive as if it was /dev/sda (hd 0,0) instead of /dev/sdb (hd 1,0)
Thanks!

[SOLVED] Fail to boot Arch x86_64 live CD on a HP laptop

Hey, guys, what's up?
Well, here's the thing: I bought a new laptop a couple days ago and I'm kind of having some trouble. Its a HP Pavilion dm4-1063cl (this model: http://www.notebookcheck.info/HP-Pavili … 579.0.html, just in case).
I ran some tests in Windows 7 about the architecture of the processor and it clearly seems that it can support arch x86_64 bits. However, I tried to boot Arch x86_64 by a Net Installation CD and it doesn't work. The process fail in the "Loadin UDEV events" phase, something like that. PS: the i686 image boots perfectly.
Then, I thought that was the CD I burned the reason for trouble - I did not check md5sum and stuff like that. So, I burned another dual image (with boths i686 and x86_64) and tried to run again the 64bits kernel. It did not work in the same phase.
The only response I get is a dark screen that never seems to go away. It was a panic I've never seen before with Arch Linux.
The only alternative I can think right now is trying an older version of the live image CD and see what happens, but it doesn't seem like a very good option. Any ideas?
Hope someone of you can help me. Here in Brazil, most of computers we buy come with Windows installed and we don't have quite a chance of not getting - or paying for - it. I'm sure I'll have such a trouble installing dual boot with Arch Linux, but I really miss my Arch Linux...
And, damn, I worked too hard to get a new processor. I really dont wanna use Arch i686 on a pc with x86_64 architecture, it seems like an option, but a dumb one. =p
Cheers,
Wilson.
EDIT: It turns out that tt was not a kernel panic as I thought. The kernel changed the resolution of the display during this fase, and somehow it doesent work.
The trick I used to solve this was adding "nomodeset" to the kernel line in the Live CD booting. Btw, you can do it by selecting the booting option you want in the live CD and pressing TAB. Then, you can edit the kernel line. (:
Last edited by wilsaooo (2010-12-28 06:17:41)

lamegaptop wrote:
Resurrecting this post because I may help you or someone else.
HP DM4-1265, Intel Corei5, Intel Graphics. (Two days old, windoze wiped, Arch installed)
At boot the brightness is, for some unexplained reason, set all the way down to 0 on these intel based DM4 laptops. A few simple <Fn>+<F3> turns the brightness back up.
To solve this I had to put this in rc.local -
echo 6 > /sys/class/backlight/acpi_video0/brightness
you can enter it manually to test first (as root). Try to turn your brightness up and down with it to make sure it works.
My fan ran like crazy too. HP chose to default a BIOS setting that keeps the fan running constantly. I disabled that and all is well. Fan only comes on when needed and lm_sensors shows my temps, right now, at 43C. Ambient is at 77F right now (I'm in Florida) and this kick butt Arch laptop is, in fact, on my lap.....
Don't give up man.
First of all: thanks for replying.
I installed manually the "coretemp" kernel modules and lm-sensors now give some different response. The script "sensors-detect" does not find any answer.
Looks like the temperature run in a regular level (50º-60º), which I consider a good sign. However, sometimes when I use arch for 24h+, it shuts down suddenly and does not let me boot my computer again - I believe it is a overheating problem. Happened a couple times, big no big deal.
On the other hand, in Windows 7 I have no trouble at all. The temperature goes around 40º with some daily activities. It worries me out because I used - and I do use - largely and successfully Arch i686 version in crappy notebooks with no heating at all.
I tried some tweaks in the rc.local, but none of them seemed to really work. With cpufreq, I could slow down the processors and maintain a regular temperature. Looks like I can list some of the fans speed in the /sys/ files, but much of them do not seem to have any change at all. Some of them looks like to have some "max_state" set to low values like 1, but most do have a limit like 10.
I will keep trying. If there's anything new, I'll post here
Cheers,
Wilson

[SOLVED]Can't boot mac air mid-2012 (GPT,EFISTUB,rEFInd,LUKS,LVM2)

Partition scheme:
/dev/sda/
- /dev/sda1: /boot/efi, 512M
- /dev/sda2: /boot, 100M
- /dev/sda3: lvm partition (/, var, home)
+ lvm on luks.
install from usb: dd if=archlinux-2012-08-04.iso of=/dev/sdX
Installation steps:
- boot from usb with noapic parameter
- partition
- encrypt /dev/sda3
- partitioning on /dev/sda3 (/,var,home)
- mkfs.vfat -F32 /dev/sda1; mkfs.ext2 /dev/sda2; mkswap /dev/arch/swap; mkfs.ext4 /dev/arch/root; mkfs.ext4 /dev/arch/home; mkfs.reiserfs /dev/arch/var
- mount /dev/arch/root /mnt; mkdir /mnt/{boot,home,var,boot/efi}; mount /dev/sda2 /mnt/boot; mount /dev/sda1 /mnt/boot/efi; mount /dev/arch/home /mnt/home; mount /dev/arch/var /mnt/var
- pacstrap /mnt base base-devel
--- SETTING EFISTUB: https://wiki.archlinux.org/index.php/UE … up_EFISTUB
/boot/efi/EFI/arch/linux.conf
root=/dev/mapper/arch-root ro rootfstype=ext4 add_efi_memmap initrd=\EFI\arch\initramfs-linux.img
- pacman -Syy; pacman -Rdd sysvinit; pacman -S systemd-vcompat; pacman -S systemd-arch-units; pacman -Rns initscripts
--- Sync EFISTUB Kernel in UEFISYS partition using Systemd: https://wiki.archlinux.org/index.php/UE … ng_Systemd
--- Booting EFISTUB: pacman -S refind-efi-x86_64
/boot/efi/EFI/arch/refind_linux.conf
"Boot with defaults" "root=/dev/mapper/arch-root ro rootfstype=ext4 add_efi_memmap"
"Boot to Terminal" "root=/dev/mapper/arch-root ro rootfstype=ext4 add_efi_memmap 3"
---- Native systemd configuration files: https://wiki.archlinux.org/index.php/Sy … tion_files
- arch-root /mnt; ln -s /usr/share/zoneinfo/Europe/Athens /etc/localtime; locale-gen; mkinitcpio -p linux; passwd; reboot
+++ and result: white screen without output +++
my english is very bad, forgive me.
i'm wong or miss something?
EDIT 1: /etc/mkinitcpio.conf : HOOKS=....encrypt lvm2 filesystem.....
Last edited by angelfalls (2012-09-07 19:40:38)

sr am wrong. i must install grub2 follow wiki, i read wiki but don't understand much
solved.

[SOLVED]GRUB Dual-boot problem

Hey guys, I need some help since I haven't had any issues with GRUB until now. I've read the GRUB page on the wiki and several other sites, but I'm still not sure which method I should use.
Anyway, everything was fine yesterday, I could boot into both my Windows and Arch. Then for some reason today, I tried booting into Windows, but stated BOOTMGR is missing, press CTRL+ALT+DEL to restart. So I tried booting into Arch, which was fine. So I used the Windows CD and then used Startup Repair to fix Windows, but unfortunately it didn't work. I then typed bootrec /fixmbr (which was typed impulsively, since I use that whenever I uninstall Linux). Anyway, that makes Windows overwrite to the MBR, so after booting my laptop it goes straight to Windows.
So I was wondering whether to use the method where you have to use chroot, the method you can just use grub> find /grub/stage1 and install to MBR, or just run through the Arch install CD and skip everything except installing the bootloader and rebooting.
Replies are appreciated, thanks in advance.
EDIT: Solved it. I booted in the Arch Linux install CD and followed the instructions on the wiki. I switched to the grub shell and used
grub> find /grub/stage1
for use in root. It displayed (hd0,6), so I then used
grub> root (hd0,6)
. Lastly I used
grub> setup (hd0)
to install GRUB to the MBR. It works perfectly again.
Last edited by Reki (2011-11-27 14:31:23)

I know exactly what the problem is.
If you're using rEFIt, sync your partition tables (should be the menu item called 'Partitioning Tool'). The problem is that GRUB has been installed, but doesn't know where to find the Arch partition.
After syncing, you may find that the boot process hangs at the Linux logo on a gray background. No worries — just reboot and the problem should fix itself.
N.B. You will need to do a partition table sync every time you change your hard drive's layout.

[SOLVED] impossible to boot (UEFI-grub2) after update

Hi,
problem : after update my computer refuses to boot. It doesn't get to the grub2 (actually 1.99) menu, it just says : no boot device found.
My hardware : Asus M8Z77-V LX motherboard with 1 SSD.
In the bios I disabled the bios legacy option to force it to boot with UEFI.
As I hadn't moved to systemd yet, I waited to update a while(2 months).
Last week I updated several pacakges by hand (kernel, vlc, ...) : All updates that according to me didn't involve with systemd.
Then I rebooted and ... problem.
I have tried a whole weekend to solve it by browsing through the wiki's but to no avail.
I can boot with live-cd and access my SSD. All data is there. I can also chroot and do stuff.
The SSD is partitionned in GPT as follows :
sda1 : 1 gb fat 32
sda2 : 20 gb ext4 root
sda3 : 20 gb ext4 var
sda4 : 79 gb ext4 home
I did not do any update of my bios or changed anything on my hardware.
It seems that my bios does not see my SSD as UEFI-bootable device anymore.
When I installed Arch in June on my brand new computer I made a backup with redobackup (partclone) of a working installation.
As a final ressort I put back the image I created then.
But it doesn't work either!
Then I updated my bios but same problem.
My bios can see the fat 32 partition. I know this because to update the bios it looks for attached fat 32 storage and there is shows the partition .
I there anywone who can point me in a good direction?
Thanks a lot in advance.
Last edited by BelgiumArcher (2013-01-08 16:20:43)

I am sorry if I lost your confidence. I can't find any contradictory info in my post.
The Arch Wiki-Grub 2 says that you need to boot in UEFI before you can (re)install grub2.
As my live-cd won't boot in UEFI mode, the only option is that I make a live-usb stick and see if that one will boot in UEFI.
But in the end it is still strange that a software update breaks my Asus UEFI-boot.
I just found another unlucky guy with a simular problem. I'll try his solution tonight.
http://superuser.com/questions/372962/w … ot-manager
http://superuser.com/questions/376470/h … -grub2-efi
I will try the live-usb method and report on it later.

[solved] Can't boot with LVM and usb external disk

I successfully installed Archlinux on my first computer, using LVM on two internal Hard Drives.
I'm trying to do exactly the same on my second computer, but I got a problem: the LVM volume is not found at boot, so that the root partition can't be mounted and the boot fails.
The only difference is that, on my second computer, the second hard drive is connected through USB.
Some hints: my second computer boots perfectly with LVM and Ubuntu. Archlinux needs to be configured adequately.
I tried to add rootdelay=30 in menu.lst, but it changes nothing. Of course, in /etc/rc.conf I have USELVM="yes" and in /etc/mkinitcpio.conf I have HOOKS="base udev autodetect pata scsi sata keymap lvm2 filesystems"
Thank you for helping me to keep Archlinux on my second computer!
Last edited by Achille (2008-06-29 21:59:09)

I finally solved my problem!
In the file /etc/mkinitcpio.conf, I modified the MODULES loaded:
MODULES="pata_acpi ata_generic ata_piix usbcore usb_storage uhci_hcd ehci_hcd sg scsi_mod sd_mod dm_mod"
I also add in the file /lib/initcpio/hooks/lvm2 the line /bin/sleep 10
/bin/sleep 10
msg "Scanning logical volumes..."
And finally, I ran the command:
mkinitcpio -p kernel26

[Solved] Can't boot, root device not found

I recently performed an update of udev and my kernel and after this I am unable to boot the normal kernel or the fallback. When I try I get this error:
ERROR: Unable to find root device '/dev/disk/by-uid/03619a2f-908f-4724-ba4b-1fb3985e382b' You are being dropped to a recovery shell Type 'exit' to try and continue booting sh: can't access tty; job control turned off
Typing exit results in me dropping to another shell and if done repeatedly a kernel panic. I attempted to boot via the grub console using the sda device block but I came up with the same error. When I look in /dev through the recovery console that comes up the sda* blocks aren't present.
I need to know if there is a way to do this without entirely reformatting my system, I also don't have easy access to another computer but I have an android phone. Any assistance is greatly appreciated.
Last edited by Surry (2012-03-20 00:06:12)

This has been solved.
For anybody's reference:
From the recovery shell I had to load the modules ahci and sd_mod and that got the sda* to appear in /dev. After that I had to mount /dev/sda3 (my root partition) under /root and /new_root and then enter 'exit' to continue booting.
Pretty much:
modprobe ahci
modprobe sd_mod
mount /dev/sda3 /root
mount /dev/sda3 /new_root
exit

[SOLVED] rm'ed /boot...

Similar Messages

Maybe you are looking for