You are not logged in.
Pages: 1
My Windows updated from version 8.0 to 8.1. and after the update I couldn't start Arch Linux anymore and was dropped into emergency shell.
I used a live USB and tried to reinstall grub.
This is what I did:
mkdir /mnt/arch
mount /dev/<root> /mnt/arch
mount /dev/<boot> /mnt/arch/boot
mount /dev/<home> /mnt/arch/home
arch-chroot /mnt/arch
The last command didn't work and I've got following error
mount point /mnt/arch/proc does not exist
After searching the web I found out that I should try to mount `proc` using following command
mount -t /proc proc /mnt/arch/proc/
This didn't worked either, because there was nor folder `/mnt/arch/proc`
I saw that none of the following folders is present in `/mnt/arch`:
@bin
dev
lib64@
proc
run
sys
tmp
var
etc
lib@
lost+found
opt
I searched the wiki and forum, but didn't found something helpful.
Could someone give me a hint please?
Last edited by Paul15071992 (2015-08-21 17:31:50)
Offline
Wow, that's a lot of folders that aren't in /mnt/arch. Which folders are present? And do they have anything in them? It sounds like your Arch partitions (at least your root partition) may have been corrupted. Assuming it's not too much trouble and everything on /home is saved, I'd probably recommend reformatting your root partition and just reinstalling everything -- since /etc and /var are not present, you've likely lost all of your system-wide configuration files and your package cache and therefore would not be able to rebuild your system in its state.
Also your title mentions GRUB but if you're getting to the emergency shell GRUB is doing its job -- booting the kernel and loading the initramfs.
Last edited by steelcowboy (2015-08-20 01:28:22)
Offline
mkdir /mnt/arch
mount /dev/<root> /mnt/arch
mount /dev/<boot> /mnt/arch/boot
mount /dev/<home> /mnt/arch/home
arch-chroot /mnt/arch
Somehow I doubt you actually used <root> as the device. Don't paraphrase.
Are you sure you mounted the right devices? Windows could easily have added a partition and screwed up the numbers.
Offline
Yes I'm 100% sure that I mounted the <root>, because after mounting it, following two folders appeared:
boot
home
this are the only folders which were present in /mnt/arch
After mounting <boot>, all my initframs are present in the folder /mnt/arch/boot
What more disturbing is, that after mounting <home>, the folder /mnt/arch/home also contains
boot
home
but they are empty
Last edited by Paul15071992 (2015-08-20 08:10:49)
Offline
I give up.
Offline
does this mean that I'll have to reinstall Arch?
Offline
No, no, no ...
Do it one more time - in EXAMPLE /dev/sda1 is boot partition and /dev/sda2 is root partition:
mount /dev/sda2 /mnt
mount /dev/sda1 /mnt/boot
mount -o bind /proc /mnt/proc
mount -o bind /sys /mnt/sys
mount -o bind /dev /mnt/dev
mount -o bind /dev/pts /mnt/dev/pts
chroot /mnt /bin/bash
If you have any troubles with Grub recovery / installation - post output of bootinfoscript:
http://sourceforge.net/projects/bootinfoscript/ .
Offline
The problem is that after mounting <root> the folders for proc, sys and dev do not appear -> the mounting commands do not work throwing following errors:
mount point /mnt/arch/proc does not exist
mount point /mnt/arch/sys does not exist
mount point /mnt/arch/dev does not exist
Offline
From what system do you want "to chroot" into Arch? What livecd are you running then?
Directory "arch" in /mnt/arch isn't necessary - as same as mounting /home. On livecd directory tree it does not exist. Do as I wrote above OR create the directory first:
mkdir -p /mnt/arch
===========
Here is EXAMPLE (chroot from SystemRescueCD into Arch Linux on VirtualBox). I don't have /boot partition:
Last edited by Fixxer (2015-08-20 14:37:51)
Offline
So this time I managed to mount all partitions, but I can't change root.
@Fixxer: I mounted everything what can be seen in your photo
chroot /mnt/arch /bin/bash
chroot: failed to run command /bin/bash: No such file or directory
chroot /mnt/arch
chroot: failed to run command /usr/bin/zsh: No such file or directory
In folder /mnt/arch I've got following folders :
bin
boot
dev
etc
home
proc
run
sys
tmp
Offline
http://s11.postimg.org/tta41s0tf/IMAG1554.jpg
http://s11.postimg.org/h35voosv7/IMAG1560.jpg
-- mod edit: converted img to url tags. Trilby --
Last edited by Trilby (2015-08-22 13:48:12)
Offline
You appear to have two separate Windows systems on that disk -- why?
What are the two GNU/Linux partitions for?
Why are you using `chroot` rather than `arch-chroot` (from the Arch live ISO)?
To which partition are you attempting the chroot?
Please post the *exact* commands you have used and the *exact* output of those commands.
Rather than posting screenshots (which should be thumbnail links, BTW) use a pastebin client to generate a link and post that here instead.
https://wiki.archlinux.org/index.php/Li … in_clients
EDIT: Please also post the output of:
# efibootmgr -v
You can use any live ISO to generate this output.
Last edited by Head_on_a_Stick (2015-08-22 12:45:06)
Offline
I give up.
does this mean that I'll have to reinstall Arch?
No, it means you should have heeded the advice provided which has now been reiterated by Head_on_a_Stick.
If you persist in 'paraphrasing' away the important information no one will be able to help you.
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
@Head_on_a_Stick:
All the Windows partitions where there when I bought the laptop and thought to keep Windows because it's with license and I'll never know when I'll be need it.
there are 3 partitions for Arch:
sda7 - boot partition
sda8 - home partition
sda10 - root partition
I tried to chroot on sda10, and I used chroot instead of arch-chroot because in one answer from above it was suggested to use chroot.
Offline
You have to create a folder, before you can mount anything to it. Since arch-chroot is just a shell script, you can read it to see what it does, this might help.
Offline
A little spoon-feeding -- from the Arch live ISO:
# mount /dev/sda10 /mnt
# mount /dev/sda7 /mnt/boot
# mount /dev/sda8 /mnt/home
# arch-chroot /mnt /bin/bash
Post any error messages verbatim.
Offline
I already tried it. Following error message appears:
chroot: failed to run command /bin/bash: No such file or directory
Offline
With the same environment as Head_on_a_Stick suggested so
# mount /dev/sda10 /mnt
# mount /dev/sda7 /mnt/boot
# mount /dev/sda8 /mnt/home
The output of
#ls -la /mnt/bin
#ls -la /mnt/usr
Edit: note the absence of the trailing / is intended and important
Last edited by loqs (2015-08-24 16:49:41)
Offline
ls -la /mnt/bin
lrwxrwxrwx 1 root root 7 /mnt/bin -> usr/bin
ls -la /mnt/usr
total 8
drwxr-xr-x 2 root root 4096 .
drwxr-xr-x 2 root root 4096 ..
Offline
ls -la /mnt/bin lrwxrwxrwx 1 root root 7 /mnt/bin -> usr/bin ls -la /mnt/usr total 8 drwxr-xr-x 2 root root 4096 . drwxr-xr-x 2 root root 4096 ..
As there is nothing in /mnt/usr ( speciffically no /mnt/usr/bin and /mnt/usr/lib ) chroot / arch-chroot can not succeed as the expected binaries inside /mnt are missing.
If /dev/sda10 really is your root file system then it seems a lot of files / directories have been erased from it.
In your first post of this thread
I saw that none of the following folders is present in `/mnt/arch`:
@bin
dev
lib64@
proc
run
sys
tmp
var
etc
lib@
lost+found
opt
In post 10
In folder /mnt/arch I've got following folders :
bin
boot
dev
etc
home
proc
run
sys
tmp
If that is the same file system and you did not recreate the directories without mentioning it then that file system / disk appears to be suffering from ongoing issues.
Given what is absent from the root file system a fresh install / restore from backups would certainly seem simpler to me than trying to fix the existing situation.
Offline
That's my fault
I recreated them and mounted them with "-o bind", because I saw so on a site.
The recreation of the files took place in a different attempt to chroot.
Is it bad?
Offline
If my understanding is correct and the only folders you had on the root file system before you recreated them were
/boot
/home
Then all of the arch install is missing and you need to either recover the entire install if that is even possible given the file system has been written to after the erasure has occurred.
Or restore / reinstall as I said above.
Offline
Pages: 1