You are not logged in.
Pages: 1
Hi All
I have just installed ArchLinux for the first time, using the beginners guide
After installing it, configuring it, generating the master key required for pacman updated, I run:
pacman -Syu
After some of the things have been installed, I did get an error:
error: failed to commit transaction (conflicting files)
filesystem: /etc/mtab exists in filesystem
So after searching the forums, I found this command, which didn't help:
pacman -S filesystem --force
So then I run:
pacman -Syu --force
This seemed to install some stuff and finished apparently successful. So I did a reboot, just to have everything clear, and I found out I can not login anymore when the system starts.
This means that the login prompt from tty1 appear:
Arch Linux 3.4.4-2-ARCH (tty1)
<hostname> login:
after typing root (or my other user I have created) the system hands a few seconds(I can still type rubbish in the meantime), and just returns to the same message to enter my login. The prompt to enter the password never appears...
Of course even if I change tty's it doesn't get better.
After it comes back to the logging it has the message: Hint: Num lock on. It's like he is checking for my password and it's wrong. But I do not provide him with one.
Any suggestions you might have?
The system is a WM machine, so I don't care if I have to Nuke it.
Offline
It is never a good idea to use the --force switch when doing a full system upgrade. The --force switch is necessary for the filesytem upgrade, but only for this particular upgrade. If it is not too much effort, I would suggest you start over again. If you are facing problems with the filesystem upgrade, I would suggest that you post again.
Offline
Start over means the entire install procedure....:( (some steps take time...but well)
I will probably try that, but right now I go for a beer
P.S. I did a --force install on the filesystem..but it did't fix it. That's why I tried a --force on the entire pacman update.
Last edited by bioshark (2012-07-07 16:54:29)
Offline
Do you have the testing repos turned on? If so, you are probably fighting this
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
@ewaller
Obviously now that I can't log on I can't check what repos are turned on.
Offline
I think you are going to be booting from a rescue disk
I just borked my system as described in the linked thread. In my case, I had a Linux From Scratch installation I could boot to instead of using the install media.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
I met a same problem,at last I pacman xorg and kde through chroot by ubuntu system,then I can login KDE,but can't login cosole. why?
My partitions are as listed below:
sda1 -win7
sda5 windows partition
sda6 / archlinux
sda7 /home archlinux
sda8 / ubuntu
I login on ubuntu,open a console, input as below:
sudo mount /dev/sda6 /mnt
sudo mount -t proc none /mnt/proc
sudo mount -t sysfs none /mnt/sys
sudo mount --bind /dev /mnt/dev
chroot /mnt /bin/bash
pacman -S xorg-server xorg-xinit xorg-utils xorg-server-utils xf86-video-nouveau nouveau-dri
pacman -S kde
sudo gedit /mnt/etc/rc.conf
sudo gedit /mnt/etc/inittab
exit
logoff ubuntu
reboot
Now there is a kdm
Last edited by xinbo (2012-07-11 14:45:02)
Offline
pacman -Syu --force
This command will break your system. Probably best to just reinstall and learn from your mistake rather than try and fight through all the issues this might have caused.
Last edited by Pres (2012-07-12 14:41:46)
Offline
While I did not do the actions that were mentioned here, I did encounter the same issue. It did occur after updating filesystem and glibc as per the wiki instructions (and not from the testing repo). Reinstalling util-linux and filesystem fixed the issue. I'm not sure which of those was the actual fix, but of course I suspect filesystem.
Offline
Just for the record, it is not the filesystem error you got, its the mtab error
This is how I fixed the mtab error as I seem to remember
http://archlinuxarm.org/forum/viewtopic.php?f=29&t=2169
And this is how to fix the filesystem error
https://www.archlinux.org/news/filesyst … -required/
Not the same procedure
Offline
While we're adding things to the record, I didn't get any actual errors... I did the update as per wiki instructions. But I still had issues, which may be directly related to either the filesystem package, or perhaps the order in which it was installed.
Offline
Why did you even get that error? Are you using an old core installation media? 2012.07.15 is the current version. And that one should give a running system without any conflicts like that.
EDIT:
Oh and since you are new to Arch: Please don't use --force unless told otherwise. You can seriously bork your system with that. If a news item says to use --force and it doesn't work, you're better off to search or ask in the forums before using --force on your own.
EDIT2:
Sorry, must be tired or something... just saw the OP is older than the new installation media -.-
Last edited by derhamster (2012-07-26 18:18:40)
Offline
@bioshark
you could try reinstall util-linux
Offline
Pages: 1