[РЕШЕНО] Букет ошибок при загрузке

-- Logs begin at Sun 2015-12-13 14:30:59 YEKT, end at Sun 2015-12-27 17:28:12 YEKT. --
Dec 27 17:27:57 pampas kernel: [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A
Dec 27 17:27:57 pampas kernel: [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun
Dec 27 17:27:58 pampas systemd[1]: Failed to start Daily verification of password and group files.
Dec 27 17:27:58 pampas dhcpcd-run-hooks[450]: wlp3s0: failed to start wpa_supplicant
Dec 27 17:27:58 pampas dhcpcd-run-hooks[451]: wlp3s0: Successfully initialized wpa_supplicant
                                              ctrl_iface exists and seems to be in use - cannot override it
                                              Delete '/var/run/wpa_supplicant/wlp3s0' manually if it is not used anymore
                                              Failed to initialize control interface '/var/run/wpa_supplicant'.
                                              You may have another wpa_supplicant process already running or the file was
                                              left by an unclean termination of wpa_supplicant in which case you will need
                                              to manually remove this file before starting wpa_supplicant again.

                                              nl80211: deinit ifname=wlp3s0 disabled_11b_rates=0

sudo rm /var/run/wpa_supplicant/wlp3s0

cat /etc/group
root:x:0:root,varnava
bin:x:1:root,bin,daemon
daemon:x:2:root,bin,daemon
sys:x:3:root,bin
adm:x:4:root,daemon
tty:x:5:
disk:x:6:root,varnava
lp:x:7:daemon,varnava
mem:x:8:
kmem:x:9:
wheel:x:10:root,varnava
ftp:x:11:
mail:x:12:
uucp:x:14:
log:x:19:root,varnava
utmp:x:20:
locate:x:21:
rfkill:x:24:
smmsp:x:25:
http:x:33:
games:x:50:varnava
lock:x:54:
uuidd:x:68:
dbus:x:81:
network:x:90:varnava
video:x:91:varnava
audio:x:92:varnava,mpd
optical:x:93:varnava
floppy:x:94:
storage:x:95:varnava
scanner:x:96:varnava
power:x:98:varnava
nobody:x:99:
users:x:100:http
systemd-journal:x:190:
polkitd:x:102:
avahi:x:84:
bumblebee:x:998:
git:x:997:
colord:x:124:
systemd-journal-gateway:x:191:
systemd-timesync:x:192:
systemd-network:x:193:
systemd-bus-proxy:x:194:
systemd-resolve:x:195:
mpd:x:45:
systemd-journal-remote:x:1000:
input:x:97:
systemd-journal-upload:x:994:
deluge:x:125:
mysql:x:1001:
proc:x:26:polkitd
wireshark:x:150:varnava
dialout:x:1002:varnava
rtkit:x:133:
tox-bootstrapd:x:993:

>sudo grpck
>sudo pwck
user 'systemd-journal-remote': no group 996
user 'systemd-journal-upload': no group 995
pwck: no changes

> sudo pwck -r
user 'systemd-journal-remote': no group 996
user 'systemd-journal-upload': no group 995
pwck: no changes

> systemctl status shadow.service
● shadow.service
   Loaded: masked (/dev/null; bad)
   Active: inactive (dead)
Warning: shadow.service changed on disk. Run 'systemctl daemon-reload' to reload units.
> sudo systemctl daemon-reload
> systemctl status shadow.service
● shadow.service
   Loaded: masked (/dev/null; bad)
   Active: inactive (dead)

52th
У меня пока две мысли:
Первая: загрузиться в single mode и отделить зёрна от плевел, то бишь попытаться понять где заканчиваются проблемы ядра и начинаются проблемы сети/DE/WM/прикладных утилит.
Вторая мысль верх банальности: pacman -Syyu

pacman -Syyu

yaa
а про single mode обезьяна не понимает...

toZen

yaa
а про single mode обезьяна не понимает...

И читать маны она тоже не умеет, или не хочет...
sudo reboot >> Shift >> e >> 'linux...blablabla...loading parameters' добавляем в конце строки '-s' >> F10
Whaaauuu!!! This is magic!!! Root shell aka single-user mode activated!!!

Failed at step EXEC spawning /bin/plymouth: No such file or directory

# UUID=b1ae5632-48a5-ce01-9006-563248a5ce01
/dev/sdb1           	/         	ext4      	defaults	0 1

# UUID=b1f7ae35-48a5-ce01-90f5-ae3548a5ce01
/dev/sdb3           	/home     	ext4      	defaults	0 2

# UUID=01CEA5484DC900D0
/dev/sdb4           	/mnt/wxp  	ntfs-3g		auto,nls=utf8,umask=000      		0 0

# UUID=28D47A22D479F284

/dev/sda1				/mnt/win  	ntfs-3g		auto,nls=utf8,umask=000      		0 0

whatch log didn't stop

fsck -y /dev/sdX[номер раздела]

toZen
Вы, чё делали-то ради отгрести?

52th
Тгода можно загрузится с флешки и проверить файловую ситему

fsck -y /dev/sdX[номер раздела]

chronos
глянь sudo journalctl --this-boot | grep FIFO

sudo journalctl --this-boot | grep FIFO

chronos
проверь systemctl status wpa_supplicant

>> systemctl status wpa_supplicant
● wpa_supplicant.service - WPA supplicant
   Loaded: loaded (/usr/lib/systemd/system/wpa_supplicant.service; enabled; vendor preset: disabled)
   Active: active (running) since Wed 2015-12-30 08:03:49 YEKT; 5h 24min ago
 Main PID: 392 (wpa_supplicant)
   CGroup: /system.slice/wpa_supplicant.service
           └─392 /usr/bin/wpa_supplicant -u

Dec 30 08:03:49 pampas systemd[1]: Starting WPA supplicant...
Dec 30 08:03:49 pampas wpa_supplicant[392]: Successfully initialized wpa_supplicant
Dec 30 08:03:49 pampas systemd[1]: Started WPA supplicant.
Warning: wpa_supplicant.service changed on disk. Run 'systemctl daemon-reload' to reload units.
( ~ )  >> sudo systemctl daemon-reload
( ~ )  >> systemctl status wpa_supplicant
● wpa_supplicant.service - WPA supplicant
   Loaded: loaded (/usr/lib/systemd/system/wpa_supplicant.service; enabled; vendor preset: disabled)
   Active: active (running) since Wed 2015-12-30 08:03:49 YEKT; 5h 25min ago
 Main PID: 392 (wpa_supplicant)
   CGroup: /system.slice/wpa_supplicant.service
           └─392 /usr/bin/wpa_supplicant -u

Dec 30 08:03:49 pampas systemd[1]: Starting WPA supplicant...
Dec 30 08:03:49 pampas wpa_supplicant[392]: Successfully initialized wpa_supplicant
Dec 30 08:03:49 pampas systemd[1]: Started WPA supplicant.

chronos
ты уже выполнил sudo systemctl daemon-reload
теперь systemctl restart shadow
должно быть все чисто

Failed to restart shadow.service: Unit shadow.service is masked.

Dec 30 09:41:43 pampas kernel: mei_me 0000:00:16.0: timer: init clients timeout hbm_state = 1.

yaa
Failed to restart shadow.service: Unit shadow.service is masked.

systemctl unmask shadow.service
systemctl daemon-reload
systemctl restart shadow