You are not logged in.
i did
pacman -Su
resulting in
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...
Packages (1): filesystem-2013.05-2
Total Installed Size: 0.01 MiB
Net Upgrade Size: -0.30 MiB
warning: /etc/group installed as /etc/group.pacnew
warning: /etc/gshadow installed as /etc/gshadow.pacnew
warning: directory permissions differ on /home/
filesystem: 777 package: 755
what do those warnings mean?
Offline
young lust, that means everything worked as expected. Congratulations, you've upgraded. I also saw the permission difference on (at least) one of my machines. I have a hunch what it is from - but it's harmless.
The pacnew files are also common, see the pacman wiki on what you should do with those.
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
Dudes. I cant boot system after that update
Error: device uuid=xzzzxxxxxxxxxxxxxxx not found. Skipping fsck.
Unable to find root device uuid=xxxxxxxxxx.
You are being dropped to a recov shell. help me
Offline
This should have nothing to do with UUIDs or modification of the bootloader... so I'm not sure this is the same problem at all. Can you check your UUIDs against what you have in your bootloader?
Offline
This should have nothing to do with UUIDs or modification of the bootloader... so I'm not sure this is the same problem at all. Can you check your UUIDs against what you have in your bootloader?
im a nigga, man!!! how i can check this?
Offline
im a nigga, man!!! how i can check this?
WTF does that mean?
Offline
Boot a live media and check it out man... I don't really know what that means either.
Offline
Split from /usr upgrade thread as there is nothing to indicate that it is related so far.
young lust wrote:im a nigga, man!!! how i can check this?
WTF does that mean?
The meaning of the word entirely depends on context, but there is very little here so I can't tell if it was just mildly inappropriate or completely inappropriate.
@young lust
Avoid such language and remain factual in your replies. This is a technical forum, not your Facebook wall.
Please use [code] tags as well to post the commands, output and file contents.
$ echo "this is an example of code tags"
My Arch Linux Stuff • Forum Etiquette • Community Ethos - Arch is not for everyone
Offline
I am having the same issue. Booting install media and using lsblk shows that the root device is present by the same UUID and it is mountable too. It boots GRUB but stops at the very same message as described in this thread.
Not sure what to do now. Reconfigure GRUB perhaps?
Offline
ronnylov, have you tried rebuilding your initramfs?
Offline
When trying to rebuild initramfs I get warning when generating the fallback image:
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: bfa
But generation of images was successful and the system now boots correctly!
Thanks for the help!
Offline
Those are warnings not errors.
Offline
WonderWoofy wrote:This should have nothing to do with UUIDs or modification of the bootloader... so I'm not sure this is the same problem at all. Can you check your UUIDs against what you have in your bootloader?
im a nigga, man!!! how i can check this?
/\
Downright offensive
Offline
Those pacman warnings are just fine. Don't worry about them. My system wasn't booting up. I was stupid enough to close the terminal window before seeing if everything went well after upgrade. So I just chroot my system using latest arch release. But still kernel was not getting upgraded. The problem was with the kmod package. I re-installed it. Kernel upgrade went fine after that.
Offline