You are not logged in.
The error preventing the upgrade is /usr/share/grub, exists in filesystem.
What can be done to complete the install of the downloads held up by this conflict?
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
pacman -Syuf...
will make it install
Offline
You could backup /usr/share/grub and forcing the install: pacman -Sf grub
Then, you can check if the new grub install works and after do pacman -Syu to update rest of pkg..
Offline
I performed pacman -Syuf.
I had done this before and had the system hang at boot time with a failure to find /dev/hda3.
Stupid me, re-installed arch 0.7 , and upgraded to kernel26 in another HDD. After install of kernel26 and lilo ran, reboot gave me a bad log-in which prevented use of the keybd (USB) each key stroke repeating ad-infinitum.
Then installed Knoppix to download pacman -Syuf. After the 40 pkgs downloaded, I had no way to perform lilo since one of the pkgs was a lilo pkg.
Subsequently, found that the HDD would perform exactly the same hang at boot-time with; cannot find /dev/hda3.
I assume (bad) that this means that lilo needs to be run and I have no clue as to how to do that with the system provided in the arch install CD repair chroot which does not permit lilo to execute.
I have lost all my arch files and data and my patience as well.
I do not expect to run anything but Knoppix henceforth. The arch system has reached meltdown since one can't upgrade without special "fixes" and "dodges" or special "patches". Knoppix DVD gives me plenty of pgms and no upgrade problems..9GB of pgms.
Pacman is not doing as well these days due to complexity in the system and Udev convinces me to move on.
Thanks for the advice but it seems it didn't work...I didn't think it would but I was clutching at straws. I found no forum solution that permitted lilo to be run in chroot so no rescue is possible.
I am always told to use grub but never how to fix lilo failure. Bad!
I see things getting even more complex and more failed downloads due to conflicts.
There exists a limit to everything under the sun. I reached mine.
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
the reason I recommended grub was that if you cannot boot you can edit the boot command to try different option, lilo does not have this function
it is the reason why i dont use lilo
the aim was to get your system up, i offered all the help i could.
there seams to be a problem with your set up, your blaming pacman and arch, but this dont seam to be happening to anyone else
Offline
I am having this exact same issue during a fresh re-install on my existing system. Arch installed previously without any issues when I conducted it the first time. After a rebuild and trying to re-install Arch now I receive the same error mentioned above.
Offline
I am having this exact same issue during a fresh re-install on my existing system. Arch installed previously without any issues when I conducted it the first time. After a rebuild and trying to re-install Arch now I receive the same error mentioned above.
try pacman -R grub
psman -Syu usually does the trick, just dont try and reboot till it's reinstalled
Offline
pacman -Syuf...
will make it install
Worked like a charm for me. Thanks.
Offline
the reason I recommended grub was that if you cannot boot you can edit the boot command to try different option, lilo does not have this function
For the record, lilo has this function. Maybe you need the menu (used for dual boot system) to be able to type the option.
Offline
cool , just never seen it myself :oops:
besides my box is dual boot ,just never noticed the option being pointed out, at least grub does this
anyway didn't mean to start a bootloader flamewar just I been trying to help this guy all week then he opens two other threads for the same subject,
Offline
I had the same problem... pacman was complaining about the existence of grub. . so I renamed grub.
mv /usr/share/grub /usr/share/grub.ok
pacman -Syu
and everything is peachy.
except now I'm having issues with udev..
I hope this works for someone else.
Offline
i realise this thread is a bit dusty but I'm curious which one ot these solutions is the best?? I've got the same problem but will lose a lot of info if i have to reinstall arch again...
thanks!
Offline
Well, if you backup what ever is conflicting it should be easier to repair without a reinstall - I can't see how a reinstall is necessary here anyway TBH!
Offline
some of these threads are talking about not being able to boot back into arch... i'm reluctant to backup the conflicting file 'cause if i can't boot back in - i can't reload the file! ... or am i reading these wrong?
...if not I'll just try pacman -Syuf...
Offline
This files have no effect whatsoever on the people unable to boot. These files are the stage files for grub which will be installed, it's just that thinks were moved a bit.
Offline
hmmm.... well after pacman -Syuf, I booted up and now get a kernel panic...
Offline
yeah a bit of optimism is definintely needed... basically, you have to trawl through the wiki and forums about the changes that installing the new kernel and udev does...
the next time i installed arch, i did pacman -Syuf BUT don't reboot yet!!
i changed everything according to:
http://wiki.archlinux.org/index.php/Udev
and I think that was all... but as i said trawl through the wiki and forums just in case.
thanks
Offline