Fwd: Kernel panic - after upgrade

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



2015-01-18 18:20 GMT+01:00 Damjan Georgievski <gdamjan@xxxxxxxxx>:
>> >>Here I exit from the prompt and reboot the machine, but get the same
>> >>error message: can't run init.
>> >>
>> >>What did I wrong?
>> >
>> > You missed that the base group should be reinstalled, as the error is
>> > not with the ramdisk,
>
>
> there's no /init outside of the ramdisk, so his problem seems to be in the
> initramfs, but probably because his base system is a bit borked and it
> mkinitcpio creates the initramfs out of it.
>
>
>> Well, I did so but can't to run successfully the `pacman -S base'
>> command because of some difficulties.
>> It complains about existing files and folder:
>> it won't overwrite the /usr/lib64 folder.
>
> post the exact errors you're getting

The output of `pacman -S base' command is:
(50/50) checking keys in keyring
(50/50) checking package integrity
(50/50) loading package files
(50/50) checking for file conflicts
(50/50) checking available disk space
(  1/50) reinstalling filesystem
error: extract: not overwriting dir with file /usr/lib64
error: problem occured while upgrading filesystem
error: could not commit transaction
error: failed to commit transaction (rransaction aborted)
Errors occured, no packages were upgraded.

I know that that the /usr/lib64 is a symlink only.

What to do?

--
Regards from Pal


[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux