...
[Jan 21 05:45:27 pampas kernel: ata2.00: exception Emask 0x0 SAct 0x7fcdffff SErr 0x0 action 0x0
Jan 21 05:45:27 pampas kernel: ata2.00: irq_stat 0x40000008
Jan 21 05:45:27 pampas kernel: ata2.00: failed command: READ FPDMA QUEUED
Jan 21 05:45:27 pampas kernel: ata2.00: cmd 60/02:b8:18:48:8a/00:00:00:00:00/40 tag 23 ncq 1024 in
                                        res 51/40:02:12:48:8a/00:00:00:00:00/40 Emask 0x409 (media error) <F>
Jan 21 05:45:27 pampas kernel: ata2.00: status: { DRDY ERR }
Jan 21 05:45:27 pampas kernel: ata2.00: error: { UNC }
Jan 21 05:45:27 pampas kernel: blk_update_request: I/O error, dev sdb, sector 9062424
Jan 21 05:45:27 pampas kernel: ata2.00: exception Emask 0x0 SAct 0x7700ffff SErr 0x0 action 0x0
Jan 21 05:45:27 pampas kernel: ata2.00: irq_stat 0x40000008
Jan 21 05:45:27 pampas kernel: ata2.00: failed command: READ FPDMA QUEUED
Jan 21 05:45:27 pampas kernel: ata2.00: cmd 60/02:c0:1e:48:8a/00:00:00:00:00/40 tag 24 ncq 1024 in
                                        res 51/40:02:32:48:8a/00:00:00:00:00/40 Emask 0x409 (media error) <F>
...
/code]
Запускал fsck, пил горькую, e2fsck, апгрейдил прошивку на SSD, ругался с женой, читал буржуйские форумы, пытался реинсталить пакеты pacman-а.
Горькая кончилась. Что делать? Возвращаться на исходную или изменить арчику с манджаро не хочется.

[code]lspci |grep ATA
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)

smartctl -a /dev/sdb
smartctl 6.4 2015-06-04 r4109 [x86_64-linux-4.3.3-3-ARCH] (local build)
Copyright (C) 2002-15, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     SandForce Driven SSDs
Device Model:     Corsair Force GT
Serial Number:    12447911000014820120
LU WWN Device Id: 0 000000 000000000
Firmware Version: 5.05
User Capacity:    120,034,123,776 bytes [120 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS, ACS-2 T13/2015-D revision 3
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Thu Jan 21 06:01:42 2016 YEKT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever
					been run.
Total time to complete Offline
data collection: 		(    0) seconds.
Offline data collection
capabilities: 			 (0x7b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine
recommended polling time: 	 (   1) minutes.
Extended self-test routine
recommended polling time: 	 (  48) minutes.
Conveyance self-test routine
recommended polling time: 	 (   2) minutes.
SCT capabilities: 	       (0x0021)	SCT Status supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   095   095   050    Pre-fail  Always       -       36/36999885
  5 Retired_Block_Count     0x0033   100   100   003    Pre-fail  Always       -       32
  9 Power_On_Hours_and_Msec 0x0032   093   093   000    Old_age   Always       -       6305h+03m+43.870s
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       13
171 Program_Fail_Count      0x0032   000   000   000    Old_age   Always       -       0
172 Erase_Fail_Count        0x0032   000   000   000    Old_age   Always       -       0
174 Unexpect_Power_Loss_Ct  0x0030   000   000   000    Old_age   Offline      -       227
177 Wear_Range_Delta        0x0000   000   000   000    Old_age   Offline      -       1
181 Program_Fail_Count      0x0032   000   000   000    Old_age   Always       -       0
182 Erase_Fail_Count        0x0032   000   000   000    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   000   000   000    Old_age   Always       -       204
194 Temperature_Celsius     0x0022   038   046   000    Old_age   Always       -       38 (Min/Max 13/46)
195 ECC_Uncorr_Error_Count  0x001c   120   120   000    Old_age   Offline      -       0/36999885
196 Reallocated_Event_Count 0x0033   100   100   003    Pre-fail  Always       -       32
201 Unc_Soft_Read_Err_Rate  0x001c   120   120   000    Old_age   Offline      -       0/36999885
204 Soft_ECC_Correct_Rate   0x001c   120   120   000    Old_age   Offline      -       0/36999885
230 Life_Curve_Status       0x0013   100   100   000    Pre-fail  Always       -       100
231 SSD_Life_Left           0x0013   100   100   010    Pre-fail  Always       -       0
233 SandForce_Internal      0x0000   000   000   000    Old_age   Offline      -       3212
234 SandForce_Internal      0x0032   000   000   000    Old_age   Always       -       2823
241 Lifetime_Writes_GiB     0x0032   000   000   000    Old_age   Always       -       2823
242 Lifetime_Reads_GiB      0x0032   000   000   000    Old_age   Always       -       3548

SMART Error Log not supported

SMART Self-test Log not supported

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

chronos
Вот тут глянь https://wiki.archlinux.org/index.php/Dhcpcd_(Русский) и про хуки почитай
скорее всего у тебя и в ручную через конфиг и через systemd стартует
ручной запуск
# wpa_supplicant -B -i interface -c /etc/wpa_supplicant/example.conf
запуск systemd
# systemctl enable wpa_supplicant@interface
https://wiki.archlinux.org/index.php/WPA_supplicant

-- Logs begin at Sun 2015-12-27 21:25:14 YEKT, end at Tue 2016-01-05 21:29:33 YEKT. --
Jan 05 21:29:19 pampas kernel: [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A
Jan 05 21:29:19 pampas kernel: [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun

svicer
dhcpcd -k
systemctl status wpa_supplicant@wlp3s0

( ~ )  >> dhcpcd -k
dhcpcd not running

( ~ )  >> systemctl status wpa_supplicant@wlp3s0
● wpa_supplicant@wlp3s0.service - WPA supplicant daemon (interface-specific version)
   Loaded: loaded (/usr/lib/systemd/system/wpa_supplicant@.service; disabled; vendor preset: disabled)
   Active: inactive (dead)

svicer
И попробуй этот хук

...Если вы самостоятельно подключаетесь к беспроводным сетям с помощью wpa_supplicant, этот хук может приводить к нежелательным попыткам подключения...

svicer

yaa
dhcpcd-run-hooks[

А как ты настраивал, то есть какой инструкцией ты пользовался?

netctl list
cat /etc/dhcpcd.conf
ls -a /var/run/wpa_supplicant/
ip route
ip netconf

( ~ )  >> cat /etc/dhcpcd.conf
# A sample configuration for dhcpcd.
# See dhcpcd.conf(5) for details.

# Allow users of this group to interact with dhcpcd via the control socket.
#controlgroup wheel

# Inform the DHCP server of our hostname for DDNS.
hostname

# Use the hardware address of the interface for the Client ID.
#clientid
# or
# Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361.
# Some non-RFC compliant DHCP servers do not reply with this set.
# In this case, comment out duid and enable clientid above.
duid

# Persist interface configuration when dhcpcd exits.
persistent

# Rapid commit support.
# Safe to enable by default because it requires the equivalent option set
# on the server to actually work.
option rapid_commit

# A list of options to request from the DHCP server.
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
# Most distributions have NTP support.
option ntp_servers
# Respect the network MTU. This is applied to DHCP routes.
option interface_mtu

# A ServerID is required by RFC2131.
require dhcp_server_identifier

# Generate Stable Private IPv6 Addresses instead of hardware based ones
slaac private

# A hook script is provided to lookup the hostname if not set by the DHCP
# server, but it should not be run by default.
nohook lookup-hostname
noipv4ll

( ~ )  >> ls -a /var/run/wpa_supplicant/
.  ..  wlp3s0

( ~ )  >> ip route
default via 192.168.1.1 dev wlp3s0  src 192.168.1.2  metric 303
192.168.1.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.1.2  metric 303 

( ~ )  >> ip netconf
ipv4 dev lo forwarding off rp_filter off mc_forwarding 0 proxy_neigh off
ipv4 dev enp4s0 forwarding off rp_filter strict mc_forwarding 0 proxy_neigh off
ipv4 dev wlp3s0 forwarding off rp_filter strict mc_forwarding 0 proxy_neigh off
ipv4 all forwarding off rp_filter strict mc_forwarding 0 proxy_neigh off
ipv4 default forwarding off rp_filter strict mc_forwarding 0 proxy_neigh off
ipv6 dev lo forwarding off mc_forwarding 0 proxy_neigh off
ipv6 dev enp4s0 forwarding off mc_forwarding 0 proxy_neigh off
ipv6 dev wlp3s0 forwarding off mc_forwarding 0 proxy_neigh off
ipv6 all forwarding off mc_forwarding 0 proxy_neigh off
ipv6 default forwarding off mc_forwarding 0 proxy_neigh off

chronos
Что то еще его запускает, может nm? Тогда прямой запуск из системд лишний, сеть поднимает сам NetworkManager.

( ~ )  >> sudo pacman -Q | grep 'net'
glib-networking 2.46.1-1
inetutils 1.9.4-2
net-snmp 5.7.3-2
net-tools 1.60.20130531git-1
netcdf 4.3.3.1-2
netctl 1.11-1
netctl-auto-ng 1.1.4-1
nettle 3.1.1-1
( ~ )  >> sudo pacman -Q | grep 'wifi'
wifite-git 138.edbdedd-1

( ~ )  >> sudo systemctl status shadow.service
● shadow.service - Verify integrity of password and group files
   Loaded: loaded (/usr/lib/systemd/system/shadow.service; static; vendor preset: disabled)
   Active: inactive (dead)

( ~ )  >> sudo journalctl -b -p err
-- Logs begin at Sat 2015-12-19 17:46:58 YEKT, end at Thu 2015-12-31 11:17:11 YEKT. --
Dec 31 11:07:08 pampas kernel: [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A
Dec 31 11:07:08 pampas kernel: [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun
Dec 31 11:07:09 pampas dhcpcd-run-hooks[452]: wlp3s0: failed to start wpa_supplicant
Dec 31 11:07:09 pampas dhcpcd-run-hooks[453]: 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

svicer

yaa
В каком менять и как это безопаснее сделать?

если про группы 1000 и 994 journalctl и pwsk не пишет ничего плохого то в /etc/passwd должно быть:

systemd-journal-remote:x:1000:1000:systemd Journal Remote:/:/sbin/nologin
systemd-journal-upload:x:994:994:systemd Journal Upload:/:/sbin/nologin

sudo vipw

svicer
посмотри в /etc/passwd и /etc/group какие группы выставлены и идентичны ли они в обоих файлах для строчек с:
systemd-journal-remote
systemd-journal-upload
ну и добавь 996 и 995 группы в систему
а потом:

systemctl daemon-reload
systemctl restart shadow

и навсякий случай:

systemctl reboot

( ~ )  >> cat /etc/passwd
...
systemd-journal-remote:x:996:996:systemd Journal Remote:/:/sbin/nologin
systemd-journal-upload:x:995:995:systemd Journal Upload:/:/sbin/nologin
...
( ~ )  >> cat /etc/group
...
systemd-journal-remote:x:1000:
systemd-journal-upload:x:994:
...

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

svicer

yaa
пользователь «systemd-journal-remote»: группа 996 не существует

а что выводит

 # groups

?

( ~ )  >> groups
root disk lp wheel log games network video audio optical storage scanner power users dialout

svicer

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

а если

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

( ~ )  >> sudo systemctl unmask shadow.service
Removed symlink /etc/systemd/system/shadow.service.
( ~ )  >> sudo systemctl daemon-reload
( ~ )  >> sudo systemctl restart shadow
Job for shadow.service failed because the control process exited with error code. See "systemctl status shadow.service" and "journalctl -xe" for details.
( ~ )  >> sudo systemctl status shadow.service
● shadow.service - Verify integrity of password and group files
   Loaded: loaded (/usr/lib/systemd/system/shadow.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Wed 2015-12-30 15:19:33 YEKT; 20s ago
  Process: 12646 ExecStart=/usr/bin/pwck -r (code=exited, status=2)
 Main PID: 12646 (code=exited, status=2)

Dec 30 15:19:33 pampas systemd[1]: Starting Verify integrity of password and group files...
Dec 30 15:19:33 pampas pwck[12646]: пользователь «systemd-journal-remote»: группа 996 не существует
Dec 30 15:19:33 pampas pwck[12646]: пользователь «systemd-journal-upload»: группа 995 не существует
Dec 30 15:19:33 pampas pwck[12646]: pwck: изменения не внесены
Dec 30 15:19:33 pampas systemd[1]: shadow.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Dec 30 15:19:33 pampas systemd[1]: Failed to start Verify integrity of password and group files.
Dec 30 15:19:33 pampas systemd[1]: shadow.service: Unit entered failed state.
Dec 30 15:19:33 pampas systemd[1]: shadow.service: Failed with result 'exit-code'.

( ~ )  >> sudo journalctl -xe
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit bluetooth.target has finished starting up.
--
-- The start-up result is done.
Dec 30 15:12:07 pampas systemd[1]: Started Load/Save RF Kill Switch Status.
-- Subject: Unit systemd-rfkill.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-rfkill.service has finished starting up.
--
-- The start-up result is done.
Dec 30 15:12:08 pampas dhcpcd[651]: wlp3s0: probing address 192.168.1.2/24
Dec 30 15:12:10 pampas dhcpcd[639]: wlp3s0: leased 192.168.1.2 for 259200 seconds
Dec 30 15:12:10 pampas dhcpcd[639]: wlp3s0: adding route to 192.168.1.0/24
Dec 30 15:12:10 pampas dhcpcd[639]: wlp3s0: adding default route via 192.168.1.1
Dec 30 15:12:10 pampas dhcpcd[639]: wlp3s0: removing route to 192.168.1.0/24
Dec 30 15:12:13 pampas dhcpcd[651]: wlp3s0: leased 192.168.1.2 for 259200 seconds
Dec 30 15:12:13 pampas dhcpcd[651]: wlp3s0: adding route to 192.168.1.0/24
Dec 30 15:12:13 pampas dhcpcd[651]: wlp3s0: adding default route via 192.168.1.1
Dec 30 15:19:08 pampas sudo[12594]:  varnava : TTY=pts/0 ; PWD=/home/varnava ; USER=root ; COMMAND=/usr/bin/systemctl unmask shadow.service
Dec 30 15:19:08 pampas sudo[12594]: pam_unix(sudo:session): session opened for user root by (uid=0)
Dec 30 15:19:08 pampas polkitd[805]: Registered Authentication Agent for unix-process:12595:2612248 (system bus name :1.24 [/usr/bin/pkttyagent --notify-fd 4 --fallback], object path /org/freedesktop/PolicyKit1/A
Dec 30 15:19:08 pampas systemd[1]: Reloading.
Dec 30 15:19:08 pampas sudo[12594]: pam_unix(sudo:session): session closed for user root
Dec 30 15:19:08 pampas polkitd[805]: Unregistered Authentication Agent for unix-process:12595:2612248 (system bus name :1.24, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disc
Dec 30 15:19:22 pampas sudo[12617]:  varnava : TTY=pts/0 ; PWD=/home/varnava ; USER=root ; COMMAND=/usr/bin/systemctl daemon-reload
Dec 30 15:19:22 pampas sudo[12617]: pam_unix(sudo:session): session opened for user root by (uid=0)
Dec 30 15:19:22 pampas polkitd[805]: Registered Authentication Agent for unix-process:12618:2613631 (system bus name :1.25 [/usr/bin/pkttyagent --notify-fd 4 --fallback], object path /org/freedesktop/PolicyKit1/A
Dec 30 15:19:22 pampas systemd[1]: Reloading.
Dec 30 15:19:22 pampas sudo[12617]: pam_unix(sudo:session): session closed for user root
Dec 30 15:19:22 pampas polkitd[805]: Unregistered Authentication Agent for unix-process:12618:2613631 (system bus name :1.25, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disc
Dec 30 15:19:33 pampas sudo[12639]:  varnava : TTY=pts/0 ; PWD=/home/varnava ; USER=root ; COMMAND=/usr/bin/systemctl restart shadow
Dec 30 15:19:33 pampas sudo[12639]: pam_unix(sudo:session): session opened for user root by (uid=0)
Dec 30 15:19:33 pampas polkitd[805]: Registered Authentication Agent for unix-process:12640:2614749 (system bus name :1.26 [/usr/bin/pkttyagent --notify-fd 4 --fallback], object path /org/freedesktop/PolicyKit1/A
Dec 30 15:19:33 pampas systemd[1]: Stopped Verify integrity of password and group files.
-- Subject: Unit shadow.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit shadow.service has finished shutting down.
Dec 30 15:19:33 pampas systemd[1]: Starting Verify integrity of password and group files...
-- Subject: Unit shadow.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit shadow.service has begun starting up.
Dec 30 15:19:33 pampas pwck[12646]: пользователь «systemd-journal-remote»: группа 996 не существует
Dec 30 15:19:33 pampas pwck[12646]: пользователь «systemd-journal-upload»: группа 995 не существует
Dec 30 15:19:33 pampas pwck[12646]: pwck: изменения не внесены
Dec 30 15:19:33 pampas systemd[1]: shadow.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Dec 30 15:19:33 pampas systemd[1]: Failed to start Verify integrity of password and group files.
-- Subject: Unit shadow.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit shadow.service has failed.
--
-- The result is failed.
Dec 30 15:19:33 pampas systemd[1]: shadow.service: Unit entered failed state.
Dec 30 15:19:33 pampas systemd[1]: shadow.service: Failed with result 'exit-code'.
Dec 30 15:19:33 pampas sudo[12639]: pam_unix(sudo:session): session closed for user root
Dec 30 15:19:33 pampas polkitd[805]: Unregistered Authentication Agent for unix-process:12640:2614749 (system bus name :1.26, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disc
Dec 30 15:19:53 pampas sudo[12661]:  varnava : TTY=pts/0 ; PWD=/home/varnava ; USER=root ; COMMAND=/usr/bin/systemctl status shadow.service
Dec 30 15:19:53 pampas sudo[12661]: pam_unix(sudo:session): session opened for user root by (uid=0)
Dec 30 15:19:53 pampas sudo[12661]: pam_unix(sudo:session): session closed for user root
Dec 30 15:23:28 pampas sudo[12775]:  varnava : TTY=pts/0 ; PWD=/home/varnava ; USER=root ; COMMAND=/usr/bin/journalctl -xe
Dec 30 15:23:28 pampas sudo[12775]: pam_unix(sudo:session): session opened for user root by (uid=0)
lines 1775-1843/1843 (END)