You are not logged in.
Hello,
booting stops on https://dl.dropboxusercontent.com/u/149 … .19.01.jpg
And after few minutes goes to: https://dl.dropboxusercontent.com/u/149 … .41.57.jpg
I dont know what should I do.
Tried (after chroot):
pacman -S linux
pacman -S grub
grub-mkconfig -o /boot/grub/grub.cfg
still no effect
Last edited by Mhrok (2014-01-06 17:34:47)
Offline
Your second picture says it all. systemd is unable to find /dev/sda5, which it needs to mount /boot - this leads systemd to abort the boot sequence. What I don't understand is why it doesn't go into an emergency shell.
Offline
I have checked twice grub.cfg. I tried to use UUID, names and it still dont work.
sda5 is ext2 filesystem, fsck.ext2 does nothing.
Offline
This isn't caused by your grub.cfg. It is likely that you have the /boot entry in your fstab pointing to the wrong place.
It does seem very odd that it doesn't put you in the emergency shell...
Offline
My Arch works. /boot in fstab should be first, probably...
SOLVED
Offline
The order shouldn't matter as long as it points to the right place. But glad you got it working anyhow.
Offline
It could be caused also by reinstalling systemd.
Offline
It could be caused also by reinstalling systemd.
No. This would have no bearing on an issue of errors in the fstab.
Offline
I found reason! libgcrypt 1.5.3 required by google-chrome and spotify etc. caused this problems. After update to 1.6.0 system boots normally.
Offline
I seem to have a similar problem.
But how can i update a package if i cant boot into the system?
Offline
Use a liveCD and chroot, or use pacman's --root switch.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Thank you very much. Worked
Offline
just in case someone falls into this trap:
yesterday i upgraded by chance libgcrypt (1.5.3) to the proposed 1.6.0, and kernel, and various other stuff - but not everything that could be upgraded. i dont know the exact pattern, but the result was atrocios:
system will boot up to "Created slice Root Slice", and then each next message/action will take 3 minutes (!) to come. And it never boots completely - i waited like 40 minutes.
After a day of fiddling, now i reverted libgcrypt to 1.5.3 (boot some ubuntu stick, manualy copy from .tar in A.R.M.) and all is fine again.
so.. beware of upgrades.
Offline
@svildo, you are not the first person I have seen who has "solved" their issue by reverting libgcrypt. I would just like to point out that this is a horrible idea. There are a number of packages in the official repos that are built against the new libgcrypt. So keeping this old version instead of simply updating to the new will end up breaking things. This is an essential lib that provides core functionality to a vast number of the packages on your system.
Remember also, partial updates are not supported!
Offline
(boot some ubuntu stick, manualy copy from .tar in A.R.M.) and all is fine again.
so.. beware of upgrades.
Please could you explain the method I use to return to the vercion
Thank you very much
Yo T vi salir campeón InTrnacional, yo T di la vuelta en la cara y vi como lloraste y T paraste a aplaudirme. Eso jamas se T va a olvidar.
Offline
After upgrading libgcrypt to 1.6.0-2 (from USB stick and running pacman --root <mount>) and running mkinitcpio, my system is still stuck on "Creating slice..."
What else should I do?
EDIT: I also upgraded lvm2, gpg and systemd, ran another mkinitcpio and now things work. I think lvm2 was the problem.
EDIT2: I had other problem as well, with GDM. It appears a full system upgrade is required.
Last edited by yuvadm (2014-01-27 11:04:57)
Offline