You are not logged in.
I did the filesytem upgrade and now my system won't boot. The upgrade seemed to complete without error. The error I get is x2dhome.device/start timed out. I am not sure where to go from here.
Offline
Can you provide some details: When in the boot process did that message come up? That looks like a systemd message, which would mean that you can *boot* you just don't get all the way to your normal target.
Someone else may recognize that message more than I do, but I can't help but suspect it is for one of the raid or btrfs or device-mapping partitioning schemes that I must admit complete ignorance of. Is that the case, do you use one of these? If so, some info on that may help.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
greenmanspirit, since the update i see a message like this when booting systemd :
a start job is running for dev/mapper/x2dlvhome.device
after 15-20 seconds it times out with a fail.
My home is an LVM partition and can't be mounted by systemd.
once in recovery mode, i start lvmetad manually, run vgchange -ay followed by systemctl default to continue boot.
A similar thing happens when i boot with openrc.
The problem doesn't occur all the time, but apart from the fact it only happens with lvm volumes i haven't figured out what causes it.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
FWIW, I am having a similar issue, except with both x2dlvhome and x2dlvvar. The only other similar post I've been able to dig up is https://bbs.archlinux.org/viewtopic.php?pid=1248651, which seems to have been solved by updating the UUID in /etc/fstab. However, everything in my fstab is listed by /dev/mapper/hostname-lvvar and the likes already.
I'm stumped.
Offline
Update: I did
mkinitcpio -p linuxfrom the recovery shell upon a suggestion from a somewhat-related post at https://bbs.archlinux.org/viewtopic.php … 0#p1147020
This seems to have fixed the problem for me (I've rebooted successfully 5 times with no issues).
Offline
Trilby. I am running into the same problem as Lone_Wolf. LVM is failing to load my home.
Lone_Wolf, I did go about mounting my partitions but it didn't occur to me to do systemd default to bring myself the rest of the way up.
aclindsa, I am going to go try your suggestion now and I will let you know if it works for me as well.
Offline
greenmanspirit: Did you get this resolved? If so, would you care to mark it [SOLVED]?
Offline