what's all the diagnostics programs to run typically on a laptop? mint doesnt update

TheEzekielProject · 11-16-2017, 04:16 PM

I would first try holding shift when you boot the machine to get your grub menu (you'll only need to hold shift if you don't normally see grub on boot. Then, when selecting the kernel to boot, go into advanced and select the one with "(recovery)" at the end. That should make the system load only what is necessary to boot and see if that allows you to get past that ERROR: /dev/disk/by-label.

If that is successful we can then look at your /etc/fstab and fix that disk wait issue so you can boot the system normally. If that doesn't work, we'll have to come up with another solution.

Post back with results

ondoho · 11-18-2017, 01:57 AM

if this is the error we are talking about:

Quote:

Originally Posted by linuxhard

starting version 232 ERROR '/dev/disk/by-label/' did not show up after 30 secs. sh: can't access tty: job control turned off

if the "version 232" means systemd, then the answer to op's question "what's all the diagnostics programs to run typically etc." is:

Code:

journalctl

and

Code:

systemctl                       systemd-firstboot               systemd-run
systemd-analyze                 systemd-hwdb                    systemd-socket-activate
systemd-ask-password            systemd-inhibit                 systemd-stdio-bridge
systemd-cat                     systemd-machine-id-setup        systemd-sysusers
systemd-cgls                    systemd-mount                   systemd-tmpfiles
systemd-cgtop                   systemd-notify                  systemd-tty-ask-password-agent
systemd-delta                   systemd-nspawn                  systemd-umount@
systemd-detect-virt             systemd-path 
systemd-escape                  systemd-resolve

each of those is
a) a command to be entered in the terminal
b) a man page for documentation, i.e. 'man some-command', e.g. 'man journalctl' etc.

but, given op's level of expertise, i'd say a reinstall is much better.
and read documentation more carefully BEFORE things break.