Аналогично с
kern.logNov 21 03:51:07 xenial kernel: [27849.320124] ieee80211 phy0: wlan0: No probe response from AP 62:d9:a0:62:fc:4f after 500ms, disconnecting.
Nov 21 03:51:07 xenial NetworkManager[1226]: <warn> [1511225467.7346] sup-iface[0x21b7d90,wlan0]: connection disconnected (reason -4)
Nov 21 03:51:07 xenial kernel: [27849.401726] cfg80211: World regulatory domain updated:
Nov 21 03:51:07 xenial kernel: [27849.401731] cfg80211: DFS Master region: unset
Nov 21 03:51:07 xenial kernel: [27849.401733] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Nov 21 03:51:07 xenial kernel: [27849.401736] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Nov 21 03:51:07 xenial kernel: [27849.401738] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Nov 21 03:51:07 xenial kernel: [27849.401741] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
Nov 21 03:51:07 xenial kernel: [27849.401743] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
Nov 21 03:51:07 xenial kernel: [27849.401746] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
Nov 21 03:51:07 xenial kernel: [27849.401749] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
Nov 21 03:51:07 xenial kernel: [27849.401751] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
Nov 21 03:51:07 xenial kernel: [27849.401754] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
Nov 21 03:51:07 xenial NetworkManager[1226]: <info> [1511225467.7558] device (wlan0): supplicant interface state: completed -> disconnected
Nov 21 03:51:07 xenial NetworkManager[1226]: <info> [1511225467.8395] device (wlan0): supplicant interface state: disconnected -> scanning
Nov 21 03:51:23 xenial NetworkManager[1226]: <warn> [1511225483.3544] device (wlan0): link timed out.
Nov 21 03:51:23 xenial NetworkManager[1226]: <info> [1511225483.3545] device (wlan0): state change: activated -> failed (reason 'ssid-not-found') [100 120 53]
Nov 21 03:51:23 xenial NetworkManager[1226]: <info> [1511225483.3550] manager: NetworkManager state is now CONNECTED_LOCAL
Nov 21 03:51:23 xenial NetworkManager[1226]: <info> [1511225483.3553] manager: NetworkManager state is now DISCONNECTED
Nov 21 03:51:23 xenial NetworkManager[1226]: <warn> [1511225483.3590] device (wlan0): Activation: failed for connection 'Lenovo P70-A'
Nov 21 03:51:23 xenial kernel: [27865.015641] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Nov 21 03:51:23 xenial NetworkManager[1226]: <info> [1511225483.3651] device (wlan0): state change: failed -> disconnected (reason 'none') [120 30 0]
Nov 21 03:51:23 xenial NetworkManager[1226]: <info> [1511225483.4002] dhcp4 (wlan0): canceled DHCP transaction, DHCP client pid 7128
Nov 21 03:51:23 xenial NetworkManager[1226]: <info> [1511225483.4002] dhcp4 (wlan0): state changed bound -> done
Nov 21 03:51:23 xenial NetworkManager[1226]: <info> [1511225483.4012] dns-mgr: Writing DNS information to /sbin/resolvconf
Nov 21 03:51:24 xenial NetworkManager[1226]: <info> [1511225484.4835] device (wlan0): supplicant interface state: scanning -> inactive
Nov 21 03:51:40 xenial NetworkManager[1226]: <info> [1511225500.9009] audit: op="radio-control" arg="wireless-enabled:1" pid=9228 uid=0 result="success"
Nov 21 03:51:41 xenial NetworkManager[1226]: <info> [1511225501.1072] ModemManager disappeared from bus
Nov 21 17:24:50 xenial kernel: [ 0.000000] microcode: CPU0 microcode updated early to revision 0xa0b, date = 2010-09-28
Nov 21 17:24:50 xenial kernel: [ 0.000000] Initializing cgroup subsys cpuset
Nov 21 17:24:50 xenial kernel: [ 0.000000] Initializing cgroup subsys cpu
Nov 21 17:24:50 xenial kernel: [ 0.000000] Initializing cgroup subsys cpuacct
Nov 21 17:24:50 xenial kernel: [ 0.000000] Linux version 4.4.0-87-generic (buildd@lcy01-31) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #110-Ubuntu SMP Tue Jul 18 12:55:35 UTC 2017 (Ubuntu 4.4.0-87.110-generic 4.4.73)
Nov 21 17:24:50 xenial kernel: [ 0.000000] Command line: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-87-generic root=/dev/sda9 ro rootflags=subvol=@
Nov 21 17:24:50 xenial kernel: [ 0.000000] KERNEL supported cpus:
Nov 21 17:24:50 xenial kernel: [ 0.000000] Intel GenuineIntel
Nov 21 17:24:50 xenial kernel: [ 0.000000] AMD AuthenticAMD
Nov 21 17:24:50 xenial kernel: [ 0.000000] Centaur CentaurHauls
Nov 21 17:24:50 xenial kernel: [ 0.000000] x86/fpu: Supporting XSAVE feature 0x01: 'x87 floating point registers'
Nov 21 17:24:50 xenial kernel: [ 0.000000] x86/fpu: Supporting XSAVE feature 0x02: 'SSE registers'
Nov 21 17:24:50 xenial kernel: [ 0.000000] x86/fpu: Enabled xstate features 0x3, context size is 576 bytes, using 'standard' format.
Nov 21 17:24:50 xenial kernel: [ 0.000000] x86/fpu: Using 'lazy' FPU context switches.
Nov 21 17:24:50 xenial kernel: [ 0.000000] e820: BIOS-provided physical RAM map:
Nov 21 17:24:50 xenial kernel: [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009f3ff] usable
Да и что может писаться в логи, если ОС не загрузилась? Правильно, ничего.
Вот и интересно что там произошло, из-за чего ФС на ровном месте поломалась?
Пользователь добавил сообщение 21 Ноября 2017, 21:30:12:
(инфы может быть очень много, смотрите по дате +/- 1 день)
Это да. Но интересуют записи между
Nov 21 03:51:41 и
Nov 21 17:24:50, именно в этот промежуток времени был произведен ремонт ФС из сторонней системы. А записей таких, по идее, быть не должно, поскольку ОС была не загружена, выключена.
Разве что ФС сама в себе где-то в недрах еще информацию пишет.
Пользователь добавил сообщение 21 Ноября 2017, 21:32:46:
инфы может быть очень много
Оказалось мало:
mart@xenial:~$ journalctl | grep -i btrfs
ноя 21 17:24:40 xenial kernel: Btrfs loaded
ноя 21 17:24:40 xenial kernel: BTRFS: device label xerus devid 1 transid 220509 /dev/sda9
ноя 21 17:24:40 xenial kernel: BTRFS: device label slack devid 1 transid 128 /dev/sda8
ноя 21 17:24:40 xenial kernel: BTRFS: device label gent devid 1 transid 24 /dev/sda7
ноя 21 17:24:40 xenial kernel: BTRFS info (device sda9): disk space caching is enabled
ноя 21 17:24:40 xenial kernel: BTRFS: has skinny extents
ноя 21 17:24:42 xenial kernel: BTRFS info (device sda9): disk space caching is enabled
ноя 21 17:24:49 xenial kernel: BTRFS error (device sda9): could not find root 8
ноя 21 17:24:49 xenial kernel: BTRFS error (device sda9): could not find root 8
mart@xenial:~$ dmesg | grep -i btrfs
[ 5.626130] Btrfs loaded
[ 6.713754] BTRFS: device label xerus devid 1 transid 220509 /dev/sda9
[ 6.714163] BTRFS: device label slack devid 1 transid 128 /dev/sda8
[ 6.714499] BTRFS: device label gent devid 1 transid 24 /dev/sda7
[ 6.843157] BTRFS info (device sda9): disk space caching is enabled
[ 6.843235] BTRFS: has skinny extents
[ 13.243406] BTRFS info (device sda9): disk space caching is enabled
[ 20.063447] BTRFS error (device sda9): could not find root 8
[ 20.063532] BTRFS error (device sda9): could not find root 8
ноя 21 17:24:49 xenial kernel:
BTRFS error (device sda9): could not find root 8Это как раз раздел, на котором стоит 16.04, в которой я сейчас нахожусь и проблем в работе не наблюдаю.