You are not logged in.

#1 2019-01-14 08:09:17

ultra2mh
Member
Registered: 2017-04-20
Posts: 30

[SOLVED] Arch Boot stuck at starting version 240

hi i did update my system few minute ago ... but after reboot it dont boot anymore and it stuck at starting version 240.
i did some try like booting from live media enter arch-chroot and  installing  lts-kernel // regenerate initramfs // make new grub .cfg file had no success.... any solution ? is there any way to find out why this problem occurr ?.. note i cant access to tty.

Last edited by ultra2mh (2019-01-14 16:41:36)

Offline

#2 2019-01-14 08:22:44

ceauke
Member
Registered: 2013-05-07
Posts: 15

Re: [SOLVED] Arch Boot stuck at starting version 240

hello, I just recovered from a similar thing.

My issue:
In my case I was running arch inside a virtual machine. I could use my keyboard inside the grub menu but after the error the keyboard doesnt work.  The error stated that it couldnt mount the hard disk drive. (I checked fstab and the UUID that was given in the error message is the correct one)

My attempts:
I tried:
  mkinitcpio: it didn't resolve my issue
  reinstalled the previous linux package with pacman (from the pacman cache). This didn't resolve it either

What worked: (downgrade systemd package)
I was pretty sure that systemd is the problem since that is what changed since my machine was previously working. I couldnt see anything incorrect in the pacman log, so I tried to downgrade to the 239 version of systemd and it worked then.

Rough steps:
- Boot with some other image (arch iso for me)
- Mount your filesystem (standard mount command)
- arch-chroot into the mounted location
- pacman the previous version (pacman -U) of systemd (/var/cache/pacman/pkg and then find the name of the 239 version of systemd)

Sorry for very inaccurate statements (I'm not at my normal machine), but it may help you in the right direction.

I'm quite new to this as well and would like to know what I missed with this update. There was no note (that I'm aware of) that warned me that my system is not ready for 240.

Good luck!

Last edited by ceauke (2019-01-14 08:34:07)

Offline

#3 2019-01-14 10:23:12

ultra2mh
Member
Registered: 2017-04-20
Posts: 30

Re: [SOLVED] Arch Boot stuck at starting version 240

i downgraded systemd but still have the problem sad

Offline

#4 2019-01-14 10:28:50

ceauke
Member
Registered: 2013-05-07
Posts: 15

Re: [SOLVED] Arch Boot stuck at starting version 240

do you get any error message? For me I had the text "starting version 240" and then the error of not being able to mount the UUID of my filesystem to the mount point. Then it said something about putting me into an emergency root user with a prompt where the keyboard wasnt working.

Offline

#5 2019-01-14 10:55:44

ultra2mh
Member
Registered: 2017-04-20
Posts: 30

Re: [SOLVED] Arch Boot stuck at starting version 240

no, my case i have only "starting version 240" and no more information ... and i have only alt ctrl del for restarting it

Offline

#6 2019-01-14 11:05:44

progandy
Member
Registered: 2012-05-17
Posts: 5,190

Re: [SOLVED] Arch Boot stuck at starting version 240

Did you try systemd 240.34 which has been released to [core] today?


| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |

Offline

#7 2019-01-14 11:18:20

ceauke
Member
Registered: 2013-05-07
Posts: 15

Re: [SOLVED] Arch Boot stuck at starting version 240

sorry man, then I dont know. the failure is different from mine then.

I would read up on systemd and the sequence in which it does things and try to see at which possible stages it could freeze (before providing output) and check system logs.

There's some tips in boot troubleshooting section. see if you can find some detailed log or debug mode.
https://wiki.archlinux.org/index.php/Ge … leshooting

Offline

#8 2019-01-14 12:14:34

once
Member
From: Taiwan
Registered: 2006-09-12
Posts: 266

Re: [SOLVED] Arch Boot stuck at starting version 240

downgrade to 239.

Offline

#9 2019-01-14 16:40:00

ultra2mh
Member
Registered: 2017-04-20
Posts: 30

Re: [SOLVED] Arch Boot stuck at starting version 240

thanks all for responses. i fixed my system few moment ago ... in my case the problem was blacklisting 'radeon' in  /etc/modprobe.d/blacklist.conf .
i dont know why this occured after today's update .
i comment out related line and the issue is resolved

Last edited by ultra2mh (2019-01-14 16:43:12)

Offline

Board footer

Powered by FluxBB