You are not logged in.
Hello,
I did update my x64 system with "pacman -Syu" but during "linux" (kernel) update my system turned of because of a powerloss.
Now I can't boot anymore. I have tried to follow the usual descriptions for this scenario but I have trouble get a 100% working chroot.
After booting from cd and mounting the hardisk (xfs) and proc,dev,etc to it I execute "chroot /mnt/arch". When doing a "dir" or "ls" no files are shown.It seems I can't create a directory or file from the shell either.
When doing "pacman -S linux" if fails to create the .img files in /boot when it tries to call mkinitcpio.
I can see and edit all files when I leave the chroot.
What do I miss ? I have tried several linux live cd and it is always the same result.
Offline
Try this: get the list of packages for the interrupted update from your pacman log and use pacman -r from an arch boot cd to reinstall them without chroot.
Last edited by progandy (2012-07-19 15:41:44)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline
Good idea..but it did not help.
On the "mkinitcpio" part of the linux packe install I get:
"Error: unable to write to path : /boot/initramsfs-linux.img"
Same error as when I try it from within the chroot.
Offline
Good idea..but it did not help.
On the "mkinitcpio" part of the linux packe install I get:
"Error: unable to write to path : /boot/initramsfs-linux.img"Same error as when I try it from within the chroot.
Hmm, did you try a bindmount from /mnt/arch/boot to /boot? Maybe mkinitcpio doesn't like a chroot or modified root paths.
Last edited by progandy (2012-07-19 20:01:20)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline
Yes, I have tried mount -o bind already. That did not help too.
I really wonder why I can not write or delete file within the chroot on my harddisk
And why there is no output when trying to list files.
I am away from this linux system for two weeks from now on so I can not test further ideas
But I have to solve it when I am at home again, so I am happy to get some more suggestions.
I did try to invoke the mkinitcpio command manualy and got an image file, but then it fails
To mount /dev/sda2 to new_root during boot after a message waiting 10 seconds for the device.
Maybe I have to do a fresh install then..good time to do a hardisk upgrade.
Thank you for your help
Offline
When you run "ls", no files are shown or does it complain that
bash: /bin/ls: No such file or directory
?
Because if it does, you may have unfinished business with this glibc migration thing.
By the way, mkinitcpio likes chroot evironments just fine. Here's how you can rebuild the initramfs: https://wiki.archlinux.org/index.php/Pa … nger_boot.
(you can skip reinstalling udev and mkinitcpio)
Last edited by DSpider (2012-07-19 21:20:53)
I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).
Offline
When you run "ls", no files are shown or does it complain that
bash: /bin/ls: No such file or directory
?
Because if it does, you may have unfinished business with this glibc migration thing.
When I run "ls" in chroot there is no error message, no output at all, just a new prompt line.
Maybe I still have to check the glibc migration stuff.
The only reason I have tried to run mkinitcpio from outside of the chroot is that it isn't messaging the error
"Unable to write to path: /boot/initramfs.."
Offline
As I couldn't get the chroot to work and I didn't get mkinitcpio to build a working file without chroot I did a complete new install of archlinux with the latest install cd to get a working system again.
Offline