You are not logged in.
Pages: 1
Hi!
I'm having trouble installing Arch on my Lenovo Ideapad 3. Grub boots fine, but hitches when I try to launch Arch.
I'm stuck on "/dev/mapper/volgroup0-lv_root: clean, xxx/xxx files, xxx/xxx blocks". The number of files and blocks increases slightly every time I attempt to boot.
I do not get a consistent result when removing the quiet tag either. There is no answer, just a freeze. I've reinstalled multiple times and am confident I have not made any errors.
If anyone knows what is going wrong I would be very appreciative, thank you!
Offline
Could be a lot of causes, normally this often happens with graphics drivers initialising too late, did you set up a graphical boot? try booting with nomodeset and/or the debug parameter, or if that doesn't work let it fail, boot into the live disk, chroot in and check whether a journal was written with e.g.
journalctl -band post that: https://wiki.archlinux.org/title/List_o … n_services
Offline
Could be a lot of causes, normally this often happens with graphics drivers initialising too late, did you set up a graphical boot? try booting with nomodeset and/or the debug parameter, or if that doesn't work let it fail, boot into the live disk, chroot in and check whether a journal was written with e.g.
journalctl -band post that: https://wiki.archlinux.org/title/List_o … n_services
This worked, thank you!
Offline
What worked? None of my suggestions were meant as permanent solutions but rather ways to pinpoint the problem and none of them should actually remain present on a healthy to be normally used system. If nomodeset "worked" then you'll get to a terminal but likely not much further if you want to do anything graphical. If the nomodeset worked either post the logs from a previous/failing boot with journalctl -b-1 or try enabling early KMS support: https://wiki.archlinux.org/title/Kernel … _KMS_start
Offline
Hi, I came up with the same issue.
the starting process freezes on
Starting version 250.4-1-arch"/dev/sda3: clean, xxx/xxx files, xxx/xxx blocks". I waited for like 30 seconds until there's an error message and successfully booted into the system.
the error message can be seen with
journalctl -bit says
Timed out waiting for device /dev/disk/by-uuid/62db49b4-067f-4bca-978b-6ebf574219cfDependency failed for /dev/disk/by-uuid//dev/disk/by-uuid/62db49b4-067f-4bca-978b-6ebf574219cfDependency failed for SwapsWhat went wrong? What can I do?
Last edited by pallas (2022-03-14 16:20:33)
Offline
Generally don't rely on /dev/sda anything being stable and otherwise post your fstab and
lsblk -fyou either have a device in your fstab (... maybe in the initramfs) that doesn't exist or doesn't exist in that form anymore.
Offline
Pages: 1