[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On 26/10/2020 19:37, comrade meowski wrote: > On 26/10/2020 19:22, Henry Bremridge wrote: >> >>> Running sysrescue from usb >>> >> I can see all files, (I have a separate partition for home) > > Unless you're very familiar with working on chrooted systems to repair > them you'll be better off initially returning to letting the system > (fail to) boot under it's own power again. When you reach the > emergency shell give it the root password to login and commence > information gathering. > > Having a look at the output of: > > systemctl --failed UNIT LOAD ACTIVE SUB DESCRIPTION ● vdr.service loaded failed failed Video Disk Recorder LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type. 1 loaded units listed. > journalctl -p err -b $ journalctl -p err -b Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. -- Logs begin at Sun 2020-02-23 07:45:04 GMT, end at Mon 2020-10-26 19:41:04 GMT. -- -- No entries -- > > Will be helpful. > > The obvious conclusion is that something other than the inadvertent > Fn+Del sequence has caused this so cast your mind back over the > previous session before this happened. Did your run any system updates > or change any settings? > > Somewhere a systemd unit file is failing to start up during boot and > it's significant enough that it's stopping the system reaching it's > default target. The output of the above two commands should be > sufficient to figure out what. Post it here if you can't figure it out. > Booted in kernel 4.16, seems to have fixed it. Running back up again Thankyou -- The Mailing List for the Devon & Cornwall LUG https://mailman.dcglug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/listfaq