Cifs vfs error connecting to socket aborting operation

Хочу монтировать сетевые папки в локальные папке при запуске. /etc/fstab: //192.168.0.1/music /home/snake/Music cifs guest,rw,iocharset=utf8 0 0 //192.168.0.1/video /home/snake/Videos cifs guest,rw,iocharset=utf8 0 0 //192.168.0.1/picture /home/snake/Pictures cifs guest,rw,iocharset=utf8 0 0 Лог dmesg: [ 11.920308] CIFS VFS: Error connecting to socket.
  • Печать

Страницы: [1] 2  Все   Вниз

Тема: CIFS VFS: Error connecting to socket. Aborting operation  (Прочитано 9706 раз)

0 Пользователей и 1 Гость просматривают эту тему.

Оффлайн
Sn@ke

Хочу монтировать сетевые папки в локальные папке при запуске.
/etc/fstab:
//192.168.0.1/music /home/snake/Music cifs guest,rw,iocharset=utf8 0 0
//192.168.0.1/video /home/snake/Videos cifs guest,rw,iocharset=utf8 0 0
//192.168.0.1/picture /home/snake/Pictures cifs guest,rw,iocharset=utf8 0 0

Лог dmesg:
[   11.920308] CIFS VFS: Error connecting to socket. Aborting operation
[   11.920382] CIFS VFS: cifs_mount failed w/return code = -101

Пробовал с опцией _netdev, noatime  — cifs пишет, что их не понимает.


Оффлайн
gorven

Я так понял авторизация не нужна? Или строго под гостем заходить?

Эта ваша Ubuntu прикольненькая такая винда (с)


Оффлайн
Sn@ke

Ага, авторизация без надобности.


Оффлайн
gorven

//192.168.0.1/music /home/snake/Music cifs auto,users,noperm,iocharset=utf8,codepage=866А так если?

И да, вот это делал? Если нет, то первым делом сделай, а то не примонтируешь

sudo apt-get install smbfs

« Последнее редактирование: 15 Октября 2010, 13:12:00 от gorven »

Эта ваша Ubuntu прикольненькая такая винда (с)


Оффлайн
Sn@ke

smbfs установлен.

//192.168.0.1/music /home/snake/Music cifs auto,users,noperm,iocharset=utf8,codepage=866
Не монтируется вообще. если монтировать так:

//192.168.0.1/music /home/snake/Music cifs guest,rw,iocharset=utf8 0 0

То папка монтруется, все ок, но меня смущают логи с

[   11.920308] CIFS VFS: Error connecting to socket. Aborting operation
[   11.920382] CIFS VFS: cifs_mount failed w/return code = -101

Мне кажется он не находит сетевой ресурс, потому что сетка еще не поднялась, не?


Оффлайн
gorven

А….инет то как цепляешь? нетворк манагером? Если да, то сетка поднимется когда  X-ы стартанут и начнется сессия пользователя, а монтирование через fstab происходит до этого.
Настрой подключение через консоль
править файлы /etc/network/interfaces и /etc/resolv.conf (для Dns)

« Последнее редактирование: 15 Октября 2010, 14:24:53 от gorven »

Эта ваша Ubuntu прикольненькая такая винда (с)


Оффлайн
Sn@ke

Ну сетку поднимает NM, настройки по dhcp


Оффлайн
gorven

Ну сетку поднимает NM, настройки по dhcp

sudo gedit /etc/network/interfacesтуда добавь

auto eth0
iface eth0 inet dhcp

и потом

sudo /etc/init.d/networking restart или перезагрузись

из NM удали подключение и настройки. Или вообще снеси его

Если на роутере не стоит передача адреса DNS сервера и ты его вбивал руками, то

sudo gedit /etc/resolv.conf и туда впиши

nameserver ip-адрес DNS сервера

« Последнее редактирование: 15 Октября 2010, 14:32:05 от gorven »

Эта ваша Ubuntu прикольненькая такая винда (с)


Оффлайн
Sn@ke

Удаление NM к результатам не привело, в итоге все теже:

[    6.904693] CIFS VFS: Error connecting to socket. Aborting operation
[    6.904772] CIFS VFS: cifs_mount failed w/return code = -101

/etc/fstab

//192.168.0.1/music /home/snake/Music cifs auto,guest,noperm,iocharset=utf8,codepage=866
cifs не поддерживает параметр codepage, его можно убрать

[   12.250097] CIFS: Unknown mount option codepage
/etc/network/interfaces, все настройки получаю по dhcp

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp


Оффлайн
gorven

То бишь монтирование проходит нормально?, но есть такие ошибки в логе. А на 192.168.0.1 стабильно инет есть?
Настройки fstab и инета нормальные, я хз почему такое вылетает.  :idiot2: …..Попробовал с твоими опциями смонтировать свою шару — работает
Жестко указать ip вместо dhcp не вариант? А то наткнулся тут на форуме точно такую же тему, один в один и там решения нет кстати…

« Последнее редактирование: 15 Октября 2010, 16:10:15 от gorven »

Эта ваша Ubuntu прикольненькая такая винда (с)


Оффлайн
Sn@ke

Да, монтирование проходит, но с ошибкой, на 192.168.0.1 стабильно работает, да инет тут не причем. После того как смонтировал и перезагрузился у тебя в dmesg таких ошибок не было?


Оффлайн
gorven

После того как смонтировал и перезагрузился у тебя в dmesg таких ошибок не было?

нет…ничего подобного нет.
Последний вопрос: как расшарены папки? Может там собака зарыта :)

Эта ваша Ubuntu прикольненькая такая винда (с)


Оффлайн
Sn@ke

Мне кажется что диски хотят монтироваться до того как поднята сеть. может попробовать в /etc/rc.local кинуть … надо попробовать


Оффлайн
gorven

Мне кажется что диски хотят монтироваться до того как поднята сеть. может попробовать в /etc/rc.local кинуть … надо попробовать

у меня сеть настроена через /etc/network/interfaces
ip статичный, никаких dhcp
все монтируется. Даже с твоими опциями. Ставлю на то, что причина не в желании дисков маунтится до подъема сети. Скорее всего где то косяк с настройками сети, возможно на стороне сервера.
У меня шара под виндами, не выключатся никогда, Расшарен весь диск сразу. Как у тебя?

Эта ваша Ubuntu прикольненькая такая винда (с)


Оффлайн
Sn@ke

У меня шары настроены с помощью Samba.


Пользователь решил продолжить мысль 16 Октября 2010, 09:05:41:


Скорее всего, не хочет монтироваться до поднятия, мб ранлевел монтирования сменить, но что отвечает за монтирование…


  • Печать

Страницы: [1] 2  Все   Вверх

I have a machine running Precise (12.04 x64), and I cannot mount my SMB drives. It used to work (a week or two ago) and I didn’t touch fstab! The machine hosting the shares is a commercial NAS, and I’m not seeing anything that would indicate it’s an issue with the NAS.

I have an older machine which I updated to Precise at the same time (both fresh installed, not dist-upgrade), so should have a very similar configuration. It is not having any problems. I am not having problems on windows machines/partitions either, only one of my Precise machines.

The two machines are using identical entries in fstab and identical /etc/samba/smb.conf files. I don’t think I’ve ever changed smb.conf (has never mattered before).

My fstab entries all basically look like this:

//<share_path>       /media/<share_name>        cifs  credentials=/home/downbeat/.credentials,iocharset=utf8,uid=downbeat,gid=downbeat,file_mode=0644,dir_mode=0755 0 0

Here’s the dmesg output on boot:

[   51.162198] CIFS VFS: Error connecting to socket. Aborting operation
[   51.162369] CIFS VFS: cifs_mount failed w/return code = -115
[   51.194106] CIFS VFS: Error connecting to socket. Aborting operation
[   51.194250] CIFS VFS: cifs_mount failed w/return code = -115
[   51.198120] CIFS VFS: Error connecting to socket. Aborting operation
[   51.198243] CIFS VFS: cifs_mount failed w/return code = -115

There are no other errors I see in the dmesg output.

Again, it used to work; now it doesn’t. Very similarly configured machine works (but some packages are out of date on the working machine). The NAS has only one interface/IP address, nmblookup works to find it’s IP from it’s hostname (from the machine with the issue) and it responds to a ping. Please any help would be great.

I’m having an issue mounting a shared NAS drive that is hosted on a Windows 2000 server. This is a drive that I’m certain I have access to, and I frequently access it from a Windows 7 machine and a Windows Server 2008 machine. Now, I’m attempting to mount this drive from a RHEL7 machine, but I’m having some issues.

What I’ve done:

mkdir /mnt/neededFolder
mount -t cifs //DNS.forMyDrive.stuff/neededFolder /mnt/neededFolder -o username=myUserId,password=myPassword,domain=myDomain

What I expected:
I expected to be able to access the folder at /mnt/neededFolder

What actually happened:
The error I’m receiving (partially shown in the subject line here) is

mount error(115): Operation now in progress
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

What the log says:

dmesg output:

[1712257.661259] CIFS VFS: Error connecting to socket. Aborting operation.
[1712257.662098] CIFS VFS: cifs_mount failed w/return code = -115

We can all see that there is a connection issue, that is obvious. I know both machines are connected to the network. What can I try next to get this drive mounted?

EDIT: It may be worth noting that I am able to ping the DNS name and the raw IP of the remote location that I am trying to mount.

Содержание

  1. Глюки при монтировании CIFS Samba
  2. Arch Linux
  3. #1 2012-09-30 12:12:38
  4. [SOLVED] — Cannot automount Samba share from fstab
  5. #2 2012-09-30 12:15:16
  6. Re: [SOLVED] — Cannot automount Samba share from fstab
  7. #3 2012-09-30 12:36:45
  8. Re: [SOLVED] — Cannot automount Samba share from fstab
  9. #4 2012-09-30 14:41:34
  10. Re: [SOLVED] — Cannot automount Samba share from fstab
  11. #5 2012-09-30 15:23:58
  12. Re: [SOLVED] — Cannot automount Samba share from fstab
  13. #6 2012-09-30 16:01:49
  14. Re: [SOLVED] — Cannot automount Samba share from fstab
  15. #7 2012-09-30 18:11:13
  16. Re: [SOLVED] — Cannot automount Samba share from fstab
  17. #8 2012-09-30 18:48:01
  18. Re: [SOLVED] — Cannot automount Samba share from fstab
  19. #9 2012-09-30 22:12:56
  20. Re: [SOLVED] — Cannot automount Samba share from fstab
  21. #10 2012-09-30 23:20:56
  22. Re: [SOLVED] — Cannot automount Samba share from fstab
  23. #11 2012-10-01 12:26:45
  24. Re: [SOLVED] — Cannot automount Samba share from fstab
  25. #12 2012-10-01 17:22:30
  26. Re: [SOLVED] — Cannot automount Samba share from fstab
  27. #13 2012-10-01 19:55:43
  28. Re: [SOLVED] — Cannot automount Samba share from fstab
  29. #14 2012-10-01 19:59:40
  30. Re: [SOLVED] — Cannot automount Samba share from fstab
  31. #15 2012-10-01 20:59:22
  32. Re: [SOLVED] — Cannot automount Samba share from fstab
  33. #16 2012-10-02 18:04:00
  34. Re: [SOLVED] — Cannot automount Samba share from fstab
  35. #17 2012-10-03 22:00:22
  36. Re: [SOLVED] — Cannot automount Samba share from fstab
  37. #18 2012-10-04 19:55:44
  38. Re: [SOLVED] — Cannot automount Samba share from fstab
  39. #19 2018-01-07 15:19:54
  40. Re: [SOLVED] — Cannot automount Samba share from fstab
  41. #20 2018-01-07 15:40:17
  42. Re: [SOLVED] — Cannot automount Samba share from fstab
  43. unixforum.org
  44. Re: CIFS
  45. Thread: Samba and fstab: mounting problem
  46. Samba and fstab: mounting problem
  47. Re: Samba and fstab: mounting problem
  48. Re: Samba and fstab: mounting problem
  49. Re: Samba and fstab: mounting problem
  50. Re: Samba and fstab: mounting problem
  51. Re: Samba and fstab: mounting problem

Глюки при монтировании CIFS Samba

Если у вас лезет ошибка

А если сеть не упадёт, то, в принципе, через chroot можно будет порнографию сделать?

Знатоки systemd, а что надо было сделать вместо сабжа, чтобы маунтпойнту добавить зависимость на поднятие конкретного интерфейса?

Нужно во первых установить cifs-utils, smbclient и rpcbind.

Во вторых настроить /etc/network/interfaces

А точнее место allow-hotplug поставить auto.

Если /etc/network/interfaces не настроен, как это в убунте. Порнография эта.

По моему порнография — это этот мануал. Подозреваю, что проблема в том что samba-ресурс из fstab не может смонтироваться на этапе загрузки системы т.к. сетевой интерфейс еще не готов. Так делать не нужно. Гораздо надежнее настроить подключение samba-ресурса по запросу к каталогу в который настроено монтирование данного ресурса (под запросом я имею ввиду просто открытие данного каталога). Я раньше использовал для этого autofs , сейчас может это еще актуально, а может что-то новое придумано.

Это не надежно. А вдруг в процессе работы сеть отрубится при том, что фактически ресурс не используется пользователем? Может быть зависание системы. Лучше монтирование по запросу к каталогу (под запросом я имею ввиду просто открытие данного каталога).

Источник

Arch Linux

You are not logged in.

#1 2012-09-30 12:12:38

Hi guys, I successfully got Samba working on my home serv last night but for some reason I cannot seem to automount the share at boot time (native systemd)

/etc/fstab

errors.log

I thought systemd wouldn’t attempt mounting until network was up?

I have removed both noauto (as I did want to automount at boot) and noatime (as I read that it causes issues when mounting at boot)

Linux zoostorm-arch 3.5.4-1-ARCH #1 SMP PREEMPT Sat Sep 15 08:12:04 CEST 2012 x86_64 GNU/Linux

Last edited by kaipee (2012-10-02 18:04:25)

#2 2012-09-30 12:15:16

Once logged in, however, I can successfully mount the share with

#3 2012-09-30 12:36:45

My look something like this:

//192.168.0.2/big_drive /media/ArchSamba cifs auto,owner,rw,username=magnus,password=*****blabla 0 0

#4 2012-09-30 14:41:34

OK so I think I have narrowed it down to the network not being connected.

My current /etc/fstab

Booting shows failed for a dependency.
Error log shows:

Upon login I can mount the share, however if I disable my wireless connection and try to mount I get:

. and the same error occurs:

So it does indeed look like it won’t mount at boot because of no network connection — however I have included the _netdev option and I am using systemd which is supposed to not attempt mounting until network is available ??

Last edited by kaipee (2012-09-30 14:42:46)

#5 2012-09-30 15:23:58

I just don’t get what is happening here. I have updated my /etc/fstab to read:

. forcing systemd to wait for at least 60 seconds to mount the share. My machine boots and logs in with a working connection in about 15 seconds after initial loading.

Yet it still complains that the network is not available and is clearly ignoring the options about timeout and _netdev .

Moderator edit: The image is too big. Reduced to url.

Last edited by bernarcher (2012-09-30 15:29:43)

#6 2012-09-30 16:01:49

_netdev only works if you have proper activation of network.target. How are you establishing a network connection?

Alternatively, just use an automounter on the share and let it be mounted on first access — add noauto,x-systemd.automount to the options.

#7 2012-09-30 18:11:13

I’m connecting to a wireless network with WPA2 (WUSBN v2) using the NetworkManager service. How do I configure/check this network.target?

#8 2012-09-30 18:48:01

NetworkManager-wait-online.service should activate network.target. You’re still better off using an automount unit.

#9 2012-09-30 22:12:56

How does the automount unit work?
I have a few applications and services that use the samba share/mount so kind of want it always mounted.

#10 2012-09-30 23:20:56

Automount means its. mounted automatically on first access.

#11 2012-10-01 12:26:45

I was leaning more towards are there any benefits of this over mounting at boot?
Is it configured for every user automatically? Is it mounted by user or root?

Why is an automount unit better than automatically mounting during boot?

#12 2012-10-01 17:22:30

I was leaning more towards are there any benefits of this over mounting at boot?

Sure. You don’t have to worry about when the network comes up.

Is it configured for every user automatically? Is it mounted by user or root?

It’s mounted by root according to the options in fstab. It’s exactly the same as if you were insisting it mount on boot.

Why is an automount unit better than automatically mounting during boot?

Boot won’t explicitly hang waiting for this to mount — only for the automount to be initialized on the mountpoint.

#13 2012-10-01 19:55:43

But I kind of want boot to hang — at least until the network comes up and continues to mount the share

#14 2012-10-01 19:59:40

. does the automount launch a ‘daemon’ of sorts, running in the background and waiting for a working network connection before initializing the mount? Allowing the rest of the system to function normally, and mounting the share as soon as a valid connection is confirmed?

#15 2012-10-01 20:59:22

Again, it mounts on first access by you (or will just fail if the endpoint is unreachable). I suggest trying this and seeing how it works before asking the same question again.

#16 2012-10-02 18:04:00

Working /etc/fstab entry:

Last edited by kaipee (2012-10-02 18:04:10)

#17 2012-10-03 22:00:22

I gotta admit I was dead set against the automount solution when I read the suggestion but it works beautifully. Hardly any lag at all on first time access and no hanging issues (so far). Thanks, falconindy.

EDIT: Spoke too soon. This thread is marked solved, so I won’t bring up my issues here. Started a new thread instead. Apologies for the mess.

Last edited by madchine (2012-10-03 22:33:59)

#18 2012-10-04 19:55:44

@falconindy can you give me a hand with the automount option? https://bbs.archlinux.org/viewtopic.php?id=150030

#19 2018-01-07 15:19:54

Just passing by to mention that the entry that turned out to work for @kaipee contains auto, non noauto as @falconindy suggested. And indeed, this works for me too.

1 made 2 edits to my own existing lines:
remove _netdev
replace noauto by auto

Doesn’t make too much sense to me, but it works

#20 2018-01-07 15:40:17

Welcome to the Arch Linux Forums. You opened with a fairly good post that is on topic, but do keep an eye on the age of the threads; this one is five years old.
https://wiki.archlinux.org/index.php/Co … bumping.22

Using this opportunity to close this old thread.

Nothing is too wonderful to be true, if it be consistent with the laws of nature — Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. — Alan Turing

How to Ask Questions the Smart Way

Источник

unixforum.org

Форум для пользователей UNIX-подобных систем

  • Темы без ответов
  • Активные темы
  • Поиск
  • Статус форума

Сообщение ru82 » 21.08.2007 10:49

Установил wine@etersoft Network 1.0.7.
1c успешно запустилась и работала локально на линуксовой машине (openSUSE 10.2)
Затем расшарил базу которая на той же машине расположена, чтобы виндовые клиенты смогли ею пользоваться, но не тут-то было.
wine блокирует базу 1с при открытии, почитав множество постов на этом форуме сделал следующие шаманские действия
(база расположена в папке /home/disk и расшарена под именем dbase)

mount -t cifs //127.0.0.1/dbase /srv/samba -o user,password=XXXXX,rw,noperm

затем создал ссылку следующим образом

ln -s /srv/samba /home/user/.wine/dosdevices/e:

и о чудо! все заработало! можно работать в 1с локально, одновременно с виндовыми клиентами, можно запускать 1с в терминале nxserver
осталась одна маленькая проблемка, если делать монтирование вручную то все нормально, если же добавляю в файл /etc/fstab строку

//127.0.0.1/dbase /srv/samba cifs user,password=XXXX,rw,noperm 0 0

то после перезагрузки машины диск не смонтирован, пробовал также команду прописать в файле автозагрузки /etc/init.d/boot.local
но не помогло. по видимому в момент монтирования модуль cifs еще не загружен, помогите решить проблемку

Re: CIFS

Сообщение On-Lite » 22.08.2007 09:31

если же добавляю в файл /etc/fstab строку

//127.0.0.1/dbase /srv/samba cifs user,password=XXXX,rw,noperm 0 0

то после перезагрузки машины диск не смонтирован, пробовал также команду прописать в файле автозагрузки /etc/init.d/boot.local
но не помогло. по видимому в момент монтирования модуль cifs еще не загружен, помогите решить проблемку

Так есть же в линуксе /etc/samba/smbfstab
можно автоматически монтировать smb и cifs протоколы
почему бы там это не прописать?
затем поместить это в автозагрузку
#chkconfig —level=5 smbfs on

Источник

Thread: Samba and fstab: mounting problem

Thread Tools
Display

Samba and fstab: mounting problem

Hello,
I have two ubuntu machines, server and client. The server shares documents via samba to the client, which mounts the samba shares automatically with fstab. I replaced the client with a new computer and now the samba stopped working. I have the exact same fstab as in the old client. The relevant lines are as follows:

When doing a ‘mount -a’, I get no errors. Also, dmesg shows no errors.

‘Mount’ seems to show that everything is ok:

I can browse to the folder /home/shared_files, but it is empty.

When I try to mount manually with ‘sudo smbmount //192.168.100.22/fileshare /home/shared_files -o user=user1’, it works, so I am assuming the problem is in the fstab file and this is not server or network issue.

What should I try next?

Re: Samba and fstab: mounting problem

do you see any messages from mount in /var/log/dmesg (especially things like ‘not ready’?

this really is ONLY a guess but I wonder if the new client machine uses the network-manager service and the old one used the traditional networking service (via /etc/network/interfaces), and if so whether the start order is later for network-manager since it’s more of a userland thing and the interface is not yet up when it tries to mount?

a lot of ifs I know

Re: Samba and fstab: mounting problem

You may still need map the incoming Windows user user1 to Linux user user1. Have you done that?

Re: Samba and fstab: mounting problem

I don’t know what you mean by mapping the incoming user?

This is really weird, as all this worked just fine before upgrading to 12.04. Could of course be a coincidence.

EDIT:
I tried this with a laptop, running ubuntu 11.10,, and its dmesg shows this:

So, it seems like you are onto something, steeldriver. Now, what can I do to fix this?

Last edited by Ptallqvist; June 10th, 2012 at 10:40 PM . Reason: Human errors in reading log files

Re: Samba and fstab: mounting problem

well I did a bit of reading around the subject, there’s some kind of signaling between network-manager and mountall (via upstart) but I’m still not clear whether that is expected to happen in strict order (local-filesystems, then networking, then remote-filesystems) or whether mountall just keeps re-trying the mount regardless of signals from the various network service upstarts

there’s a (rather old) bug report/discussion here:

I guess you could see if the behavior is different if you revert to defining your interface via /etc/network/interfaces instead of (presumably) using network-manager?

Last edited by steeldriver; June 10th, 2012 at 11:56 PM . Reason: added suggested diagnostic / workaround

Re: Samba and fstab: mounting problem

I disabled network-manager (like this), but it still wouldn’t work. After I added gid=user1 to the fstab samba lines, it seems to work. I still can’t quite figure out what the problem(s) were, but I’m happy it works.

Maybe this whole episode would have been easier with a native linux solution, like nfs?

Источник

PROBLEM:

Mount error 115 on some shares? (LINUX)

SOLUTION 1:

  • Running debian wheezy on a virtual machine and trying to mount some shares from the win8.1 host.

[pastacode lang=”bash” manual=”%2F%2F192.168.0.10%2Fdir1%20%2Fhome%2Fuser%2Fdir1%20cifs%20credentials%3D%2Froot%2F.secret.pwd%2Cuid%3D1000%2Cgid%3D1000%2Cfile_mode%3D0777%2Cdir_mode%3D0777%2Ciocharset%3Dutf8%2Csec%3Dntlm%200%200%0A%2F%2F192.160.0.10%2Fdir2%20%2Fhome%2Fuser%2Fdir2%20cifs%20credentials%3D%2Froot%2F.secret.pwd%2Cuid%3D1000%2Cgid%3D1000%2Cfile_mode%3D0777%2Cdir_mode%3D0777%2Ciocharset%3Dutf8%2Csec%3Dntlm%200%200%0A%2F%2F192.160.0.10%2Fdir3%20%2Fhome%2Fuser%2Fdir3%20cifs%20credentials%3D%2Froot%2F.secret.pwd%2Cuid%3D1000%2Cgid%3D1000%2Cfile_mode%3D0777%2Cdir_mode%3D0777%2Ciocharset%3Dutf8%2Csec%3Dntlm%200%200%0A%0A” message=”bash code” highlight=”” provider=”manual”/]

  • The first share gets mounted correctly, but not the other two.
  • This is the output we get when sudo-ing a mount -a:

Code:

[pastacode lang=”bash” manual=”mount%20error(115)%3A%20Operation%20now%20in%20progress%0ARefer%20to%20the%20mount.cifs(8)%20manual%20page%20(e.g.%20man%20mount.cifs)%0Amount%20error(115)%3A%20Operation%20now%20in%20progress%0ARefer%20to%20the%20mount.cifs(8)%20manual%20page%20(e.g.%20man%20mount.cifs)%0A” message=”bash code” highlight=”” provider=”manual”/]

and this is what /var/log/syslog shows:

Code:

[pastacode lang=”bash” manual=”Mar%2024%2012%3A56%3A12%20hostname%20kernel%3A%20%5B%201887.029043%5D%20CIFS%20VFS%3A%20Error%20connecting%20to%20socket.%20Aborting%20operation%0AMar%2024%2012%3A56%3A12%20hostname%20kernel%3A%20%5B%201887.030013%5D%20CIFS%20VFS%3A%20cifs_mount%20failed%20w%2Freturn%20code%20%3D%20-115%0AMar%2024%2012%3A56%3A22%20hostname%20kernel%3A%20%5B%201897.052130%5D%20CIFS%20VFS%3A%20Error%20connecting%20to%20socket.%20Aborting%20operation%0AMar%2024%2012%3A56%3A22%20hostname%20kernel%3A%20%5B%201897.053885%5D%20CIFS%20VFS%3A%20cifs_mount%20failed%20w%2Freturn%20code%20%3D%20-115%0A” message=”bash code” highlight=”” provider=”manual”/]

  • The same happens at boot time.

Now, we run manually :

Code:

[pastacode lang=”bash” manual=”sudo%20mount%20%2F%2F192.168.0.10%2Fdir2%20%2Fhome%2Fuser%2Fdir2%20-t%20cifs%20-o%20credentials%3D%2Froot%2F.secret.pwd%2Cuid%3D1000%2Cgid%3D1000%0A” message=”bash code” highlight=”” provider=”manual”/]

SOLUTION 2:

mount error(115): Operation now in progress … CIFS VFS: cifs_mount failed w/return code = -115

  • Trying to mount a CIFS path in Ubuntu and getting:
  • mount error(115): Operation now in progress
  • Try to look this /var/log/syslog:

[pastacode lang=”bash” manual=”Feb%20%209%2014%3A08%3A29%20ldap%20kernel%3A%20%5B143452.140157%5D%20CIFS%20VFS%3A%20Error%20connecting%20to%20socket.%20Aborting%20operation%0AFeb%20%209%2014%3A08%3A29%20ldap%20kernel%3A%20%5B143452.140492%5D%20CIFS%20VFS%3A%20cifs_mount%20failed%20w%2Freturn%20code%20%3D%20-115%0A” message=”bash code” highlight=”” provider=”manual”/]

  • Socket error, we know what this is right? IP or port. Ping for domain/IP or Telnet to test port:

[pastacode lang=”bash” manual=”ping%20IP%0Atelnet%20IP%20445%0A” message=”bash code” highlight=”” provider=”manual”/]

  • Telnet was timing out, port closed for IP in firewall.

SOLUTION 3:

LEM mount error(115): Operation now in progress

Overview

  • This article describes an error during the LEM upgrade process where you are asked to specify a network share location containing upgrade files.
  • After entering the network share as \hostnamesharename and the username and password, LEM throws this error and will fail the upgrade process:

Mount error(115): Operation now in progress

Cause

  • A network name resolution failing on the smb client in LEM.

Resolution

  • Check ICMP connectivity (ping) between the hosts.
  • Attempt to mount a share on the same subnet as LEM.
  • Attempt to use the IP address and a simple share name when mounting the share.

e.g. \10.1.1.1lem rather than \some_host_some_place_on_the_networkthis_share.name_desktop_special_unique_and_long

Wikitechy Founder, Author, International Speaker, and Job Consultant. My role as the CEO of Wikitechy, I help businesses build their next generation digital platforms and help with their product innovation and growth strategy. I’m a frequent speaker at tech conferences and events.

Related Tags
  • 192.168 l 128 password,
  • centos mount error 115 operation now in progress,
  • cifs error 115,
  • cifs mount error 115,
  • cifs mount port,
  • cifs vfs error connecting to socket. aborting operation 115,
  • errno 115 operation now in progress,
  • how to access shared folder in ubuntu,
  • how to access windows shared folder from linux,
  • how to share folder in windows 7,
  • linux 15.10,
  • linux error 115 operation now in progress,
  • linux error codes,
  • map network drive linux,
  • mount a network drive in linux,
  • mount error 115,
  • mount error(115): operation now in progress azure,
  • mount network drive in linux,
  • mount windows share in linux,
  • network sharing windows 7,
  • operation now,
  • raspberry pi mount error(115) operation now in progress,
  • Searches related to mount error(115) operation now in progress linux,
  • share desktop windows 7,
  • share folder in windows 7,
  • tns-12537 tns-12560 tns-00507 linux error 115,
  • ubuntu file sharing,
  • ubuntu fstab,
  • ubuntu map network drive gui,
  • ubuntu nas error 115,
  • wd my cloud linux,
  • windows 7 shared folder

gogoleva@USER-03 ~ $ dmesg
[ 0.000000] microcode: microcode updated early to revision 0x1c, date = 2015-02-26
[ 0.000000] Linux version 4.10.0-35-generic (buildd@lcy01-33) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #39~16.04.1-Ubuntu SMP Wed Sep 13 09:02:42 UTC 2017 (Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17)
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic root=UUID=2d48b6f0-57dc-4b24-beeb-0f930fd4bef3 ro quiet splash vt.handoff=7
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] Centaur CentaurHauls
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x001: ‘x87 floating point registers’
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x002: ‘SSE registers’
[ 0.000000] x86/fpu: Enabled xstate features 0x3, context size is 576 bytes, using ‘standard’ format.
[ 0.000000] e820: BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009d3ff] usable
[ 0.000000] BIOS-e820: [mem 0x000000000009d400-0x000000000009ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000001fffffff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000020000000-0x00000000201fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000020200000-0x0000000040003fff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000040004000-0x0000000040004fff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000040005000-0x00000000caabefff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000caabf000-0x00000000caebefff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000caebf000-0x00000000cafbefff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x00000000cafbf000-0x00000000caffefff] ACPI data
[ 0.000000] BIOS-e820: [mem 0x00000000cafff000-0x00000000caffffff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000cb000000-0x00000000cf9fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000f0000000-0x00000000f3ffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000feb00000-0x00000000feb03fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed10000-0x00000000fed19fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000ffc80000-0x00000000ffffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000012f5fffff] usable
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] SMBIOS 2.7 present.
[ 0.000000] DMI: LENOVO 10113/INVALID, BIOS I4KT22AUS 09/23/2013
[ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
[ 0.000000] e820: last_pfn = 0x12f600 max_arch_pfn = 0x400000000
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-BFFFF uncachable
[ 0.000000] C0000-E7FFF write-protect
[ 0.000000] E8000-EFFFF write-combining
[ 0.000000] F0000-FFFFF write-protect
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 000000000 mask F80000000 write-back
[ 0.000000] 1 base 080000000 mask FC0000000 write-back
[ 0.000000] 2 base 0C0000000 mask FF8000000 write-back
[ 0.000000] 3 base 0C8000000 mask FFE000000 write-back
[ 0.000000] 4 base 0CA000000 mask FFF000000 write-back
[ 0.000000] 5 base 0FFC00000 mask FFFC00000 write-protect
[ 0.000000] 6 base 100000000 mask FC0000000 write-back
[ 0.000000] 7 base 12F600000 mask FFFE00000 uncachable
[ 0.000000] 8 base 12F800000 mask FFF800000 uncachable
[ 0.000000] 9 base 130000000 mask FF0000000 uncachable
[ 0.000000] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WC UC- WT
[ 0.000000] e820: last_pfn = 0xcb000 max_arch_pfn = 0x400000000
[ 0.000000] found SMP MP-table at [mem 0x000fe1b0-0x000fe1bf] mapped at [ffff8faf800fe1b0]
[ 0.000000] Scanning 1 areas for low memory corruption
[ 0.000000] Base memory trampoline at [ffff8faf80097000] 97000 size 24576
[ 0.000000] BRK [0xb6428000, 0xb6428fff] PGTABLE
[ 0.000000] BRK [0xb6429000, 0xb6429fff] PGTABLE
[ 0.000000] BRK [0xb642a000, 0xb642afff] PGTABLE
[ 0.000000] BRK [0xb642b000, 0xb642bfff] PGTABLE
[ 0.000000] BRK [0xb642c000, 0xb642cfff] PGTABLE
[ 0.000000] BRK [0xb642d000, 0xb642dfff] PGTABLE
[ 0.000000] BRK [0xb642e000, 0xb642efff] PGTABLE
[ 0.000000] BRK [0xb642f000, 0xb642ffff] PGTABLE
[ 0.000000] RAMDISK: [mem 0x32b1e000-0x35586fff]
[ 0.000000] ACPI: Early table checksum verification disabled
[ 0.000000] ACPI: RSDP 0x00000000000FE020 000024 (v02 LENOVO)
[ 0.000000] ACPI: XSDT 0x00000000CAFFE210 00008C (v01 LENOVO TC-03 00000160 01000013)
[ 0.000000] ACPI: FACP 0x00000000CAFFB000 00010C (v05 LENOVO TC-03 00000160 ACPI 00040000)
[ 0.000000] ACPI: DSDT 0x00000000CAFEF000 00829A (v01 LENOVO TC-03 00000160 ACPI 00040000)
[ 0.000000] ACPI: FACS 0x00000000CAFBB000 000040
[ 0.000000] ACPI: UEFI 0x00000000CAFFD000 000236 (v01 LENOVO TC-03 00000160 ACPI 00040000)
[ 0.000000] ACPI: ASF! 0x00000000CAFFC000 0000A5 (v32 LENOVO TC-03 00000160 ACPI 00040000)
[ 0.000000] ACPI: HPET 0x00000000CAFFA000 000038 (v01 LENOVO TC-03 00000160 ACPI 00040000)
[ 0.000000] ACPI: APIC 0x00000000CAFF9000 00008C (v03 LENOVO TC-03 00000160 ACPI 00040000)
[ 0.000000] ACPI: MCFG 0x00000000CAFF8000 00003C (v01 LENOVO TC-03 00000160 ACPI 00040000)
[ 0.000000] ACPI: WDAT 0x00000000CAFEE000 000224 (v01 LENOVO TC-03 00000160 ACPI 00040000)
[ 0.000000] ACPI: SSDT 0x00000000CAFED000 0009CF (v01 LENOVO TC-03 00000160 ACPI 00040000)
[ 0.000000] ACPI: BOOT 0x00000000CAFEB000 000028 (v01 LENOVO TC-03 00000160 ACPI 00040000)
[ 0.000000] ACPI: ASPT 0x00000000CAFE9000 000034 (v07 LENOVO TC-03 00000160 ACPI 00040000)
[ 0.000000] ACPI: DBGP 0x00000000CAFE8000 000034 (v01 LENOVO TC-03 00000160 ACPI 00040000)
[ 0.000000] ACPI: FPDT 0x00000000CAFE6000 000044 (v01 LENOVO TC-03 00000160 ACPI 00040000)
[ 0.000000] ACPI: SSDT 0x00000000CAFE4000 000B22 (v01 LENOVO TC-03 00000160 ACPI 00040000)
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] No NUMA configuration found
[ 0.000000] Faking a node at [mem 0x0000000000000000-0x000000012f5fffff]
[ 0.000000] NODE_DATA(0) allocated [mem 0x12f5d2000-0x12f5fcfff]
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x0000000000001000-0x0000000000ffffff]
[ 0.000000] DMA32 [mem 0x0000000001000000-0x00000000ffffffff]
[ 0.000000] Normal [mem 0x0000000100000000-0x000000012f5fffff]
[ 0.000000] Device empty
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x0000000000001000-0x000000000009cfff]
[ 0.000000] node 0: [mem 0x0000000000100000-0x000000001fffffff]
[ 0.000000] node 0: [mem 0x0000000020200000-0x0000000040003fff]
[ 0.000000] node 0: [mem 0x0000000040005000-0x00000000caabefff]
[ 0.000000] node 0: [mem 0x00000000cafff000-0x00000000caffffff]
[ 0.000000] node 0: [mem 0x0000000100000000-0x000000012f5fffff]
[ 0.000000] Initmem setup node 0 [mem 0x0000000000001000-0x000000012f5fffff]
[ 0.000000] On node 0 totalpages: 1023579
[ 0.000000] DMA zone: 64 pages used for memmap
[ 0.000000] DMA zone: 21 pages reserved
[ 0.000000] DMA zone: 3996 pages, LIFO batch:0
[ 0.000000] DMA32 zone: 12899 pages used for memmap
[ 0.000000] DMA32 zone: 825535 pages, LIFO batch:31
[ 0.000000] Normal zone: 3032 pages used for memmap
[ 0.000000] Normal zone: 194048 pages, LIFO batch:31
[ 0.000000] Reserving Intel graphics memory at 0x00000000cba00000-0x00000000cf9fffff
[ 0.000000] ACPI: PM-Timer IO Port: 0x408
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[ 0.000000] ACPI: IRQ0 used by override.
[ 0.000000] ACPI: IRQ9 used by override.
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000
[ 0.000000] smpboot: Allowing 8 CPUs, 6 hotplug CPUs
[ 0.000000] PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
[ 0.000000] PM: Registered nosave memory: [mem 0x0009d000-0x0009dfff]
[ 0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009ffff]
[ 0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
[ 0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
[ 0.000000] PM: Registered nosave memory: [mem 0x20000000-0x201fffff]
[ 0.000000] PM: Registered nosave memory: [mem 0x40004000-0x40004fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xcaabf000-0xcaebefff]
[ 0.000000] PM: Registered nosave memory: [mem 0xcaebf000-0xcafbefff]
[ 0.000000] PM: Registered nosave memory: [mem 0xcafbf000-0xcaffefff]
[ 0.000000] PM: Registered nosave memory: [mem 0xcb000000-0xcf9fffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xcfa00000-0xefffffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xf0000000-0xf3ffffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xf4000000-0xfeafffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfeb00000-0xfeb03fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfeb04000-0xfebfffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfec01000-0xfed0ffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfed10000-0xfed19fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfed1a000-0xfed1bfff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfedfffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfee01000-0xffc7ffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xffc80000-0xffffffff]
[ 0.000000] e820: [mem 0xcfa00000-0xefffffff] available for PCI devices
[ 0.000000] Booting paravirtualized kernel on bare hardware
[ 0.000000] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
[ 0.000000] setup_percpu: NR_CPUS:8192 nr_cpumask_bits:8 nr_cpu_ids:8 nr_node_ids:1
[ 0.000000] percpu: Embedded 36 pages/cpu @ffff8fb0af200000 s107992 r8192 d31272 u262144
[ 0.000000] pcpu-alloc: s107992 r8192 d31272 u262144 alloc=1*2097152
[ 0.000000] pcpu-alloc: [0] 0 1 2 3 4 5 6 7
[ 0.000000] Built 1 zonelists in Node order, mobility grouping on. Total pages: 1007563
[ 0.000000] Policy zone: Normal
[ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic root=UUID=2d48b6f0-57dc-4b24-beeb-0f930fd4bef3 ro quiet splash vt.handoff=7
[ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.000000] Calgary: detecting Calgary via BIOS EBDA area
[ 0.000000] Calgary: Unable to locate Rio Grande table in EBDA — bailing!
[ 0.000000] Memory: 3897228K/4094316K available (9068K kernel code, 1667K rwdata, 3828K rodata, 2228K init, 2364K bss, 197088K reserved, 0K cma-reserved)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] Build-time adjustment of leaf fanout to 64.
[ 0.000000] RCU restricting CPUs from NR_CPUS=8192 to nr_cpu_ids=8.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=64, nr_cpu_ids=8
[ 0.000000] NR_IRQS:524544 nr_irqs:488 16
[ 0.000000] vt handoff: transparent VT on vt#7
[ 0.000000] Console: colour dummy device 80×25
[ 0.000000] console [tty0] enabled
[ 0.000000] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 133484882848 ns
[ 0.000000] hpet clockevent registered
[ 0.000000] tsc: Fast TSC calibration using PIT
[ 0.000000] tsc: Detected 1596.453 MHz processor
[ 0.000037] Calibrating delay loop (skipped), value calculated using timer frequency.. 3192.90 BogoMIPS (lpj=6385812)
[ 0.000040] pid_max: default: 32768 minimum: 301
[ 0.000054] ACPI: Core revision 20160930
[ 0.007135] ACPI: 3 ACPI AML tables successfully acquired and loaded
[ 0.007175] Security Framework initialized
[ 0.007176] Yama: becoming mindful.
[ 0.007198] AppArmor: AppArmor initialized
[ 0.007562] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
[ 0.009097] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
[ 0.009789] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes)
[ 0.009795] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes)
[ 0.010116] CPU: Physical Processor ID: 0
[ 0.010117] CPU: Processor Core ID: 0
[ 0.010123] ENERGY_PERF_BIAS: Set to ‘normal’, was ‘performance’
[ 0.010123] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
[ 0.010127] mce: CPU supports 7 MCE banks
[ 0.010137] CPU0: Thermal monitoring enabled (TM1)
[ 0.010149] process: using mwait in idle threads
[ 0.010152] Last level iTLB entries: 4KB 512, 2MB 8, 4MB 8
[ 0.010153] Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32, 1GB 0
[ 0.010330] Freeing SMP alternatives memory: 32K
[ 0.035912] ftrace: allocating 34225 entries in 134 pages
[ 0.059104] smpboot: Max logical packages: 4
[ 0.059183] x2apic: IRQ remapping doesn’t support X2APIC mode
[ 0.059651] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.099342] TSC deadline timer enabled
[ 0.099346] smpboot: CPU0: Intel(R) Celeron(R) CPU 1017U @ 1.60GHz (family: 0x6, model: 0x3a, stepping: 0x9)
[ 0.099415] Performance Events: PEBS fmt1+, IvyBridge events, 16-deep LBR, full-width counters, Intel PMU driver.
[ 0.099444] … version: 3
[ 0.099445] … bit width: 48
[ 0.099446] … generic registers: 8
[ 0.099447] … value mask: 0000ffffffffffff
[ 0.099448] … max period: 00007fffffffffff
[ 0.099448] … fixed-purpose events: 3
[ 0.099449] … event mask: 00000007000000ff
[ 0.100660] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
[ 0.100684] smp: Bringing up secondary CPUs …
[ 0.100791] x86: Booting SMP configuration:
[ 0.100792] …. node #0, CPUs: #1
[ 0.103690] smp: Brought up 1 node, 2 CPUs
[ 0.103692] smpboot: Total of 2 processors activated (6385.81 BogoMIPS)
[ 0.105423] devtmpfs: initialized
[ 0.105513] x86/mm: Memory block size: 128MB
[ 0.108740] evm: security.selinux
[ 0.108741] evm: security.SMACK64
[ 0.108742] evm: security.SMACK64EXEC
[ 0.108742] evm: security.SMACK64TRANSMUTE
[ 0.108743] evm: security.SMACK64MMAP
[ 0.108743] evm: security.ima
[ 0.108744] evm: security.capability
[ 0.108826] PM: Registering ACPI NVS region [mem 0xcaebf000-0xcafbefff] (1048576 bytes)
[ 0.108903] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[ 0.108918] futex hash table entries: 2048 (order: 5, 131072 bytes)
[ 0.108975] pinctrl core: initialized pinctrl subsystem
[ 0.109106] RTC time: 6:07:20, date: 10/06/17
[ 0.109218] NET: Registered protocol family 16
[ 0.123684] cpuidle: using governor ladder
[ 0.139692] cpuidle: using governor menu
[ 0.139696] PCCT header not found.
[ 0.139751] Simple Boot Flag at 0x44 set to 0x1
[ 0.139761] ACPI FADT declares the system doesn’t support PCIe ASPM, so disable it
[ 0.139763] ACPI: bus type PCI registered
[ 0.139764] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[ 0.139850] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf0000000-0xf3ffffff] (base 0xf0000000)
[ 0.139894] PCI: MMCONFIG at [mem 0xf0000000-0xf3ffffff] reserved in E820
[ 0.139902] PCI: Using configuration type 1 for base access
[ 0.140003] core: PMU erratum BJ122, BV98, HSD29 workaround disabled, HT off
[ 0.141564] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
[ 0.155889] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[ 0.156197] ACPI: Added _OSI(Module Device)
[ 0.156198] ACPI: Added _OSI(Processor Device)
[ 0.156199] ACPI: Added _OSI(3.0 _SCP Extensions)
[ 0.156200] ACPI: Added _OSI(Processor Aggregator Device)
[ 0.156420] ACPI: Executed 1 blocks of module-level executable AML code
[ 0.161035] ACPI Error: [_PR_.CPU0._PPC] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 0.161044] ACPI Error: Method parse/execution failed [_PR.CPU0._PDC] (Node ffff8fb0aa8dd578), AE_NOT_FOUND (20160930/psparse-543)
[ 0.161370] ACPI: Dynamic OEM Table Load:
[ 0.161379] ACPI: SSDT 0xFFFF8FB0A9CC4C00 000119 (v01 PmRef ApCst 00003000 INTL 20121220)
[ 0.161808] ACPI : EC: EC started
[ 0.161809] ACPI : EC: interrupt blocked
[ 0.161918] ACPI: _SB_.PCI0.LPCB.EC0_: Used as first EC
[ 0.161920] ACPI: _SB_.PCI0.LPCB.EC0_: GPE=0x17, EC_CMD/EC_SC=0x66, EC_DATA=0x62
[ 0.161922] ACPI: _SB_.PCI0.LPCB.EC0_: Used as boot DSDT EC to handle transactions
[ 0.161923] ACPI: Interpreter enabled
[ 0.161953] ACPI: (supports S0 S3 S4 S5)
[ 0.161954] ACPI: Using IOAPIC for interrupt routing
[ 0.161987] PCI: Using host bridge windows from ACPI; if necessary, use «pci=nocrs» and report a bug
[ 0.162049] platform wdat_wdt: failed to claim resource 4
[ 0.162054] ACPI: watchdog: Device creation failed: -16
[ 0.167532] ACPI: Power Resource [FN00] (off)
[ 0.167648] ACPI: Power Resource [FN01] (off)
[ 0.167768] ACPI: Power Resource [FN02] (off)
[ 0.167882] ACPI: Power Resource [FN03] (off)
[ 0.167991] ACPI: Power Resource [FN04] (off)
[ 0.168815] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
[ 0.168821] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
[ 0.168913] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
[ 0.169503] PCI host bridge to bus 0000:00
[ 0.169506] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7 window]
[ 0.169507] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff window]
[ 0.169509] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
[ 0.169510] pci_bus 0000:00: root bus resource [mem 0xcfa00000-0xfeafffff window]
[ 0.169513] pci_bus 0000:00: root bus resource [bus 00-3e]
[ 0.169522] pci 0000:00:00.0: [8086:0154] type 00 class 0x060000
[ 0.169645] pci 0000:00:02.0: [8086:0156] type 00 class 0x030000
[ 0.169657] pci 0000:00:02.0: reg 0x10: [mem 0xe0000000-0xe03fffff 64bit]
[ 0.169665] pci 0000:00:02.0: reg 0x18: [mem 0xd0000000-0xdfffffff 64bit pref]
[ 0.169670] pci 0000:00:02.0: reg 0x20: [io 0x4000-0x403f]
[ 0.169847] pci 0000:00:16.0: [8086:1e3a] type 00 class 0x078000
[ 0.169873] pci 0000:00:16.0: reg 0x10: [mem 0xe0704000-0xe070400f 64bit]
[ 0.169965] pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
[ 0.170084] pci 0000:00:1a.0: [8086:1e2d] type 00 class 0x0c0320
[ 0.170104] pci 0000:00:1a.0: reg 0x10: [mem 0xe0709000-0xe07093ff]
[ 0.170206] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
[ 0.170281] pci 0000:00:1a.0: System wakeup disabled by ACPI
[ 0.170334] pci 0000:00:1b.0: [8086:1e20] type 00 class 0x040300
[ 0.170355] pci 0000:00:1b.0: reg 0x10: [mem 0xe0700000-0xe0703fff 64bit]
[ 0.170443] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[ 0.170505] pci 0000:00:1b.0: System wakeup disabled by ACPI
[ 0.170555] pci 0000:00:1c.0: [8086:1e10] type 01 class 0x060400
[ 0.170655] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[ 0.170714] pci 0000:00:1c.0: System wakeup disabled by ACPI
[ 0.170765] pci 0000:00:1c.2: [8086:1e14] type 01 class 0x060400
[ 0.170857] pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold
[ 0.170917] pci 0000:00:1c.2: System wakeup disabled by ACPI
[ 0.170975] pci 0000:00:1d.0: [8086:1e26] type 00 class 0x0c0320
[ 0.170997] pci 0000:00:1d.0: reg 0x10: [mem 0xe0708000-0xe07083ff]
[ 0.171098] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
[ 0.171170] pci 0000:00:1d.0: System wakeup disabled by ACPI
[ 0.171223] pci 0000:00:1f.0: [8086:1e5f] type 00 class 0x060100
[ 0.171431] pci 0000:00:1f.2: [8086:1e03] type 00 class 0x010601
[ 0.171452] pci 0000:00:1f.2: reg 0x10: [io 0x4088-0x408f]
[ 0.171462] pci 0000:00:1f.2: reg 0x14: [io 0x4094-0x4097]
[ 0.171472] pci 0000:00:1f.2: reg 0x18: [io 0x4080-0x4087]
[ 0.171482] pci 0000:00:1f.2: reg 0x1c: [io 0x4090-0x4093]
[ 0.171491] pci 0000:00:1f.2: reg 0x20: [io 0x4060-0x407f]
[ 0.171502] pci 0000:00:1f.2: reg 0x24: [mem 0xe0707000-0xe07077ff]
[ 0.171554] pci 0000:00:1f.2: PME# supported from D3hot
[ 0.171653] pci 0000:00:1f.3: [8086:1e22] type 00 class 0x0c0500
[ 0.171672] pci 0000:00:1f.3: reg 0x10: [mem 0xe0705000-0xe07050ff 64bit]
[ 0.171698] pci 0000:00:1f.3: reg 0x20: [io 0x4040-0x405f]
[ 0.171913] pci 0000:01:00.0: [10ec:5289] type 00 class 0xff0000
[ 0.171939] pci 0000:01:00.0: reg 0x10: [mem 0xe0600000-0xe060ffff]
[ 0.172135] pci 0000:01:00.0: supports D1 D2
[ 0.172136] pci 0000:01:00.0: PME# supported from D1 D2 D3hot D3cold
[ 0.172192] pci 0000:01:00.0: System wakeup disabled by ACPI
[ 0.172253] pci 0000:01:00.2: [10ec:8168] type 00 class 0x020000
[ 0.172279] pci 0000:01:00.2: reg 0x10: [io 0x3000-0x30ff]
[ 0.172317] pci 0000:01:00.2: reg 0x18: [mem 0xe0404000-0xe0404fff 64bit pref]
[ 0.172341] pci 0000:01:00.2: reg 0x20: [mem 0xe0400000-0xe0403fff 64bit pref]
[ 0.172454] pci 0000:01:00.2: supports D1 D2
[ 0.172456] pci 0000:01:00.2: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.183786] pci 0000:00:1c.0: PCI bridge to [bus 01]
[ 0.183791] pci 0000:00:1c.0: bridge window [io 0x3000-0x3fff]
[ 0.183795] pci 0000:00:1c.0: bridge window [mem 0xe0600000-0xe06fffff]
[ 0.183802] pci 0000:00:1c.0: bridge window [mem 0xe0400000-0xe04fffff 64bit pref]
[ 0.183920] pci 0000:02:00.0: [10ec:8176] type 00 class 0x028000
[ 0.183969] pci 0000:02:00.0: reg 0x10: [io 0x2000-0x20ff]
[ 0.184041] pci 0000:02:00.0: reg 0x18: [mem 0xe0500000-0xe0503fff 64bit]
[ 0.184274] pci 0000:02:00.0: supports D1 D2
[ 0.184275] pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.184382] pci 0000:02:00.0: System wakeup disabled by ACPI
[ 0.195799] pci 0000:00:1c.2: PCI bridge to [bus 02]
[ 0.195804] pci 0000:00:1c.2: bridge window [io 0x2000-0x2fff]
[ 0.195808] pci 0000:00:1c.2: bridge window [mem 0xe0500000-0xe05fffff]
[ 0.197112] ACPI: Enabled 6 GPEs in block 00 to 3F
[ 0.197164] ACPI : EC: interrupt unblocked
[ 0.197171] ACPI : EC: event unblocked
[ 0.197178] ACPI: _SB_.PCI0.LPCB.EC0_: GPE=0x17, EC_CMD/EC_SC=0x66, EC_DATA=0x62
[ 0.197180] ACPI: _SB_.PCI0.LPCB.EC0_: Used as boot DSDT EC to handle transactions and events
[ 0.197547] SCSI subsystem initialized
[ 0.197597] libata version 3.00 loaded.
[ 0.197648] pci 0000:00:02.0: vgaarb: setting as boot VGA device
[ 0.197651] pci 0000:00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
[ 0.197655] pci 0000:00:02.0: vgaarb: bridge control possible
[ 0.197655] vgaarb: loaded
[ 0.197680] ACPI: bus type USB registered
[ 0.197699] usbcore: registered new interface driver usbfs
[ 0.197708] usbcore: registered new interface driver hub
[ 0.197726] usbcore: registered new device driver usb
[ 0.197865] PCI: Using ACPI for IRQ routing
[ 0.199713] PCI: pci_cache_line_size set to 64 bytes
[ 0.199920] NetLabel: Initializing
[ 0.199921] NetLabel: domain hash size = 128
[ 0.199921] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO
[ 0.199942] NetLabel: unlabeled traffic allowed by default
[ 0.200072] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
[ 0.200079] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
[ 0.202102] clocksource: Switched to clocksource hpet
[ 0.211955] VFS: Disk quotas dquot_6.6.0
[ 0.211981] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 0.212103] AppArmor: AppArmor Filesystem Enabled
[ 0.212166] pnp: PnP ACPI init
[ 0.212344] system 00:00: [io 0x0680-0x069f] has been reserved
[ 0.212346] system 00:00: [io 0x1000-0x100f] has been reserved
[ 0.212348] system 00:00: [io 0xffff] has been reserved
[ 0.212350] system 00:00: [io 0xffff] has been reserved
[ 0.212351] system 00:00: [io 0x0400-0x0453] has been reserved
[ 0.212353] system 00:00: [io 0x0458-0x047f] has been reserved
[ 0.212355] system 00:00: [io 0x0500-0x057f] has been reserved
[ 0.212356] system 00:00: [io 0x164e-0x164f] has been reserved
[ 0.212361] system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.212395] pnp 00:01: Plug and Play ACPI device, IDs PNP0b00 (active)
[ 0.212462] system 00:02: [io 0x0454-0x0457] has been reserved
[ 0.212466] system 00:02: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
[ 0.212507] pnp 00:03: Plug and Play ACPI device, IDs PNP0303 (active)
[ 0.212984] system 00:05: Plug and Play ACPI device, IDs PNP0c01 (active)
[ 0.213011] pnp: PnP ACPI: found 6 devices
[ 0.219813] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
[ 0.219846] pci 0000:00:1c.0: PCI bridge to [bus 01]
[ 0.219850] pci 0000:00:1c.0: bridge window [io 0x3000-0x3fff]
[ 0.220018] NET: Registered protocol family 2
[ 0.220231] TCP established hash table entries: 32768 (order: 6, 262144 bytes)
[ 0.220324] TCP bind hash table entries: 32768 (order: 7, 524288 bytes)
[ 0.220413] TCP: Hash tables configured (established 32768 bind 32768)
[ 0.220447] UDP hash table entries: 2048 (order: 4, 65536 bytes)
[ 0.220463] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes)
[ 0.220520] NET: Registered protocol family 1
[ 0.220537] pci 0000:00:02.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
[ 0.258275] PCI: CLS 64 bytes, default 64
[ 0.258340] Unpacking initramfs…
[ 1.246909] Freeing initrd memory: 43428K
[ 1.246914] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[ 1.246917] software IO TLB [mem 0xc6abf000-0xcaabf000] (64MB) mapped at [ffff8fb046abf000-ffff8fb04aabefff]
[ 1.247166] Scanning for low memory corruption every 60 seconds
[ 1.247599] audit: initializing netlink subsys (disabled)
[ 1.247645] audit: type=2000 audit(1507270041.212:1): initialized
[ 1.248157] Initialise system trusted keyrings
[ 1.248248] workingset: timestamp_bits=36 max_order=20 bucket_order=0
[ 1.250221] zbud: loaded
[ 1.250838] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 1.251089] fuse init (API version 7.26)
[ 1.252649] Key type asymmetric registered
[ 1.252650] Asymmetric key parser ‘x509’ registered
[ 1.252700] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 248)
[ 1.252734] io scheduler noop registered
[ 1.252735] io scheduler deadline registered
[ 1.252745] io scheduler cfq registered (default)
[ 1.253257] vesafb: mode is 1366x768x32, linelength=5504, pages=0
[ 1.253258] vesafb: scrolling: redraw
[ 1.253260] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[ 1.253272] vesafb: framebuffer at 0xd0000000, mapped to 0xffffaba4c1000000, using 4160k, total 4160k
[ 1.253384] Console: switching to colour frame buffer device 170×48
[ 1.253409] fb0: VESA VGA frame buffer device
[ 1.253425] intel_idle: MWAIT substates: 0x21120
[ 1.253426] intel_idle: v0.4.1 model 0x3A
[ 1.253533] intel_idle: lapic_timer_reliable_states 0xffffffff
[ 1.253619] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:01/PNP0C0C:00/input/input0
[ 1.253624] ACPI: Power Button [PWRB]
[ 1.253677] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
[ 1.253679] ACPI: Power Button [PWRF]
[ 1.254439] (NULL device *): hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info().
[ 1.254587] thermal LNXTHERM:00: registered as thermal_zone0
[ 1.254589] ACPI: Thermal Zone [TZ00] (28 C)
[ 1.254863] thermal LNXTHERM:01: registered as thermal_zone1
[ 1.254864] ACPI: Thermal Zone [TZ01] (30 C)
[ 1.254911] GHES: HEST is not enabled!
[ 1.255007] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
[ 1.256843] Linux agpgart interface v0.103
[ 1.258913] loop: module loaded
[ 1.259129] libphy: Fixed MDIO Bus: probed
[ 1.259130] tun: Universal TUN/TAP device driver, 1.6
[ 1.259131] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 1.259173] PPP generic driver version 2.4.2
[ 1.259218] ehci_hcd: USB 2.0 ‘Enhanced’ Host Controller (EHCI) Driver
[ 1.259220] ehci-pci: EHCI PCI platform driver
[ 1.259410] ehci-pci 0000:00:1a.0: EHCI Host Controller
[ 1.259417] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
[ 1.259433] ehci-pci 0000:00:1a.0: debug port 2
[ 1.263333] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
[ 1.263347] ehci-pci 0000:00:1a.0: irq 16, io mem 0xe0709000
[ 1.278135] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
[ 1.278214] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.278216] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.278218] usb usb1: Product: EHCI Host Controller
[ 1.278219] usb usb1: Manufacturer: Linux 4.10.0-35-generic ehci_hcd
[ 1.278221] usb usb1: SerialNumber: 0000:00:1a.0
[ 1.278501] hub 1-0:1.0: USB hub found
[ 1.278512] hub 1-0:1.0: 2 ports detected
[ 1.278910] ehci-pci 0000:00:1d.0: EHCI Host Controller
[ 1.278919] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
[ 1.278936] ehci-pci 0000:00:1d.0: debug port 2
[ 1.282832] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
[ 1.282848] ehci-pci 0000:00:1d.0: irq 23, io mem 0xe0708000
[ 1.298136] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
[ 1.298217] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.298219] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.298221] usb usb2: Product: EHCI Host Controller
[ 1.298222] usb usb2: Manufacturer: Linux 4.10.0-35-generic ehci_hcd
[ 1.298223] usb usb2: SerialNumber: 0000:00:1d.0
[ 1.298504] hub 2-0:1.0: USB hub found
[ 1.298516] hub 2-0:1.0: 2 ports detected
[ 1.298754] ehci-platform: EHCI generic platform driver
[ 1.298775] ohci_hcd: USB 1.1 ‘Open’ Host Controller (OHCI) Driver
[ 1.298783] ohci-pci: OHCI PCI platform driver
[ 1.298800] ohci-platform: OHCI generic platform driver
[ 1.298810] uhci_hcd: USB Universal Host Controller Interface driver
[ 1.298885] i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
[ 1.298886] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
[ 1.301270] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 1.301574] mousedev: PS/2 mouse device common for all mice
[ 1.301863] rtc_cmos 00:01: RTC can wake from S4
[ 1.302003] rtc_cmos 00:01: rtc core: registered rtc_cmos as rtc0
[ 1.302034] rtc_cmos 00:01: alarms up to one month, 242 bytes nvram, hpet irqs
[ 1.302041] i2c /dev entries driver
[ 1.302124] device-mapper: uevent: version 1.0.3
[ 1.302254] device-mapper: ioctl: 4.35.0-ioctl (2016-06-23) initialised: dm-devel@redhat.com
[ 1.302261] intel_pstate: Intel P-state driver initializing
[ 1.302410] ledtrig-cpu: registered to indicate activity on CPUs
[ 1.302797] NET: Registered protocol family 10
[ 1.308432] Segment Routing with IPv6
[ 1.308456] NET: Registered protocol family 17
[ 1.308471] Key type dns_resolver registered
[ 1.308729] microcode: sig=0x306a9, pf=0x10, revision=0x1c
[ 1.308778] microcode: Microcode Update Driver: v2.2.
[ 1.309001] registered taskstats version 1
[ 1.309011] Loading compiled-in X.509 certificates
[ 1.312727] Loaded X.509 cert ‘Build time autogenerated kernel key: 3781ac46c2f7a743322097d3608bc638deea4293’
[ 1.312757] zswap: loaded using pool lzo/zbud
[ 1.326166] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input2
[ 1.328642] Key type big_key registered
[ 1.328647] Key type trusted registered
[ 1.331067] Key type encrypted registered
[ 1.331071] AppArmor: AppArmor sha1 policy hashing enabled
[ 1.331074] ima: No TPM chip found, activating TPM-bypass! (rc=-19)
[ 1.331096] evm: HMAC attrs: 0x1
[ 1.331440] Magic number: 5:174:114
[ 1.331556] rtc_cmos 00:01: setting system clock to 2017-10-06 06:07:21 UTC (1507270041)
[ 1.331644] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[ 1.331645] EDD information not available.
[ 1.331717] PM: Hibernation image not present or could not be loaded.
[ 1.334160] Freeing unused kernel memory: 2228K
[ 1.334162] Write protecting the kernel read-only data: 14336k
[ 1.334696] Freeing unused kernel memory: 1156K
[ 1.335563] Freeing unused kernel memory: 268K
[ 1.348016] x86/mm: Checked W+X mappings: passed, no W+X pages found.
[ 1.363935] random: systemd-udevd: uninitialized urandom read (16 bytes read)
[ 1.364046] random: systemd-udevd: uninitialized urandom read (16 bytes read)
[ 1.364064] random: systemd-udevd: uninitialized urandom read (16 bytes read)
[ 1.364087] random: systemd-udevd: uninitialized urandom read (16 bytes read)
[ 1.364682] random: udevadm: uninitialized urandom read (16 bytes read)
[ 1.364732] random: udevadm: uninitialized urandom read (16 bytes read)
[ 1.366396] random: udevadm: uninitialized urandom read (16 bytes read)
[ 1.366417] random: udevadm: uninitialized urandom read (16 bytes read)
[ 1.367018] random: udevadm: uninitialized urandom read (16 bytes read)
[ 1.367089] random: udevadm: uninitialized urandom read (16 bytes read)
[ 1.415019] FUJITSU Extended Socket Network Device Driver — version 1.2 — Copyright (c) 2015 FUJITSU LIMITED
[ 1.432525] [drm] Initialized
[ 1.438610] ahci 0000:00:1f.2: version 3.0
[ 1.438845] ahci 0000:00:1f.2: SSS flag set, parallel bus scan disabled
[ 1.439706] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 1.439714] r8169 0000:01:00.2: can’t disable ASPM; OS doesn’t have ASPM control
[ 1.440576] r8169 0000:01:00.2 eth0: RTL8411 at 0xffffaba4c06cd000, 20:1a:06:85:1a:44, XID 08800800 IRQ 25
[ 1.440578] r8169 0000:01:00.2 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[ 1.447022] rtsx_pci 0000:01:00.0: rtsx_pci_acquire_irq: pcr->msi_en = 1, pci->irq = 26
[ 1.449101] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 4 ports 6 Gbps 0x15 impl SATA mode
[ 1.449104] ahci 0000:00:1f.2: flags: 64bit ncq stag pm led clo pio slum part ems sxs apst
[ 1.477766] scsi host0: ahci
[ 1.477930] scsi host1: ahci
[ 1.478055] scsi host2: ahci
[ 1.478166] scsi host3: ahci
[ 1.478274] scsi host4: ahci
[ 1.478335] ata1: SATA max UDMA/133 abar m2048@0xe0707000 port 0xe0707100 irq 24
[ 1.478337] ata2: DUMMY
[ 1.478339] ata3: SATA max UDMA/133 abar m2048@0xe0707000 port 0xe0707200 irq 24
[ 1.478340] ata4: DUMMY
[ 1.478343] ata5: SATA max UDMA/133 abar m2048@0xe0707000 port 0xe0707300 irq 24
[ 1.480079] [drm] Memory usable by graphics device = 2048M
[ 1.480082] checking generic (d0000000 410000) vs hw (d0000000 10000000)
[ 1.480083] fb: switching to inteldrmfb from VESA VGA
[ 1.480117] Console: switching to colour dummy device 80×25
[ 1.480393] [drm] Replacing VGA console driver
[ 1.486455] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 1.486456] [drm] Driver supports precise vblank timestamp query.
[ 1.490586] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
[ 1.492189] r8169 0000:01:00.2 enp1s0f2: renamed from eth0
[ 1.618072] usb 1-1: new high-speed USB device number 2 using ehci-pci
[ 1.634067] usb 2-1: new high-speed USB device number 2 using ehci-pci
[ 1.643027] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
[ 1.643604] acpi device:3c: registered as cooling_device7
[ 1.643698] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input3
[ 1.643770] [drm] Initialized i915 1.6.0 20161121 for 0000:00:02.0 on minor 0
[ 1.773460] fbcon: inteldrmfb (fb0) is primary device
[ 1.773583] Console: switching to colour frame buffer device 170×48
[ 1.773621] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[ 1.792997] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 1.794403] ata1.00: ATA-8: ST500DM002-1BD142, KC65, max UDMA/100
[ 1.794407] ata1.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[ 1.794565] usb 1-1: New USB device found, idVendor=8087, idProduct=0024
[ 1.794568] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1.794649] usb 2-1: New USB device found, idVendor=8087, idProduct=0024
[ 1.794651] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1.794984] hub 2-1:1.0: USB hub found
[ 1.795065] hub 1-1:1.0: USB hub found
[ 1.795662] hub 1-1:1.0: 4 ports detected
[ 1.795685] hub 2-1:1.0: 4 ports detected
[ 1.796087] ata1.00: configured for UDMA/100
[ 1.796630] scsi 0:0:0:0: Direct-Access ATA ST500DM002-1BD14 KC65 PQ: 0 ANSI: 5
[ 1.826442] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 GiB)
[ 1.826446] sd 0:0:0:0: [sda] 4096-byte physical blocks
[ 1.826467] sd 0:0:0:0: [sda] Write Protect is off
[ 1.826470] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 1.826503] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn’t support DPO or FUA
[ 1.826681] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 1.875754] sda: sda1 sda2 < sda5 >
[ 1.876207] sd 0:0:0:0: [sda] Attached SCSI disk
[ 2.082094] usb 2-1.1: new high-speed USB device number 3 using ehci-pci
[ 2.082117] usb 1-1.1: new low-speed USB device number 3 using ehci-pci
[ 2.141646] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 2.146188] ata3.00: ATAPI: PLDS DVD-RW DS8A9SH, EL3A, max UDMA/100
[ 2.147169] ata3.00: configured for UDMA/100
[ 2.160388] scsi 2:0:0:0: CD-ROM PLDS DVD-RW DS8A9SH EL3A PQ: 0 ANSI: 5
[ 2.190810] usb 2-1.1: New USB device found, idVendor=0424, idProduct=2502
[ 2.190812] usb 2-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 2.191205] hub 2-1.1:1.0: USB hub found
[ 2.191939] hub 2-1.1:1.0: 2 ports detected
[ 2.201013] sr 2:0:0:0: [sr0] scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
[ 2.201015] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 2.201255] sr 2:0:0:0: Attached scsi CD-ROM sr0
[ 2.201640] sr 2:0:0:0: Attached scsi generic sg1 type 5
[ 2.214932] usb 1-1.1: New USB device found, idVendor=17ef, idProduct=602d
[ 2.214935] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2.214937] usb 1-1.1: Product: Lenovo Black Silk USB Keyboard
[ 2.214938] usb 1-1.1: Manufacturer: Lenovo
[ 2.220991] hidraw: raw HID events driver (C) Jiri Kosina
[ 2.255801] usbcore: registered new interface driver usbhid
[ 2.255803] usbhid: USB HID core driver
[ 2.258421] input: Lenovo Lenovo Black Silk USB Keyboard as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/0003:17EF:602D.0001/input/input4
[ 2.270065] tsc: Refined TSC clocksource calibration: 1596.376 MHz
[ 2.270068] usb 2-1.3: new high-speed USB device number 4 using ehci-pci
[ 2.270076] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x1702c578726, max_idle_ns: 440795205522 ns
[ 2.294075] usb 1-1.2: new low-speed USB device number 4 using ehci-pci
[ 2.318365] hid-generic 0003:17EF:602D.0001: input,hidraw0: USB HID v1.11 Keyboard [Lenovo Lenovo Black Silk USB Keyboard] on usb-0000:00:1a.0-1.1/input0
[ 2.321948] input: Lenovo Lenovo Black Silk USB Keyboard as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.1/0003:17EF:602D.0002/input/input5
[ 2.378349] hid-generic 0003:17EF:602D.0002: input,hidraw1: USB HID v1.11 Device [Lenovo Lenovo Black Silk USB Keyboard] on usb-0000:00:1a.0-1.1/input1
[ 2.406817] usb 1-1.2: New USB device found, idVendor=17ef, idProduct=602e
[ 2.406820] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2.406821] usb 1-1.2: Product: USB Optical Mouse
[ 2.406823] usb 1-1.2: Manufacturer: PixArt
[ 2.410044] input: PixArt USB Optical Mouse as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/0003:17EF:602E.0003/input/input6
[ 2.410254] hid-generic 0003:17EF:602E.0003: input,hidraw2: USB HID v1.11 Mouse [PixArt USB Optical Mouse] on usb-0000:00:1a.0-1.2/input0
[ 2.471910] random: fast init done
[ 2.478071] usb 2-1.1.1: new high-speed USB device number 5 using ehci-pci
[ 2.478544] usb 2-1.3: New USB device found, idVendor=174f, idProduct=1482
[ 2.478547] usb 2-1.3: New USB device strings: Mfr=3, Product=1, SerialNumber=2
[ 2.478549] usb 2-1.3: Product: Lenovo USB2.0 UVC Camera
[ 2.478551] usb 2-1.3: Manufacturer: Lenovo USB2.0 UVC Camera
[ 2.478552] usb 2-1.3: SerialNumber: Lenovo USB2.0 UVC Camera
[ 2.517407] ata5: SATA link down (SStatus 0 SControl 300)
[ 2.587645] usb 2-1.1.1: New USB device found, idVendor=03f0, idProduct=4d17
[ 2.587648] usb 2-1.1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2.587650] usb 2-1.1.1: Product: HP LaserJet M2727nf MFP
[ 2.587651] usb 2-1.1.1: Manufacturer: Hewlett-Packard
[ 2.587652] usb 2-1.1.1: SerialNumber: 00CNFT942GJ5
[ 3.277958] raid6: sse2x1 gen() 4254 MB/s
[ 3.325954] raid6: sse2x1 xor() 3385 MB/s
[ 3.373950] raid6: sse2x2 gen() 5329 MB/s
[ 3.421945] raid6: sse2x2 xor() 3782 MB/s
[ 3.469953] raid6: sse2x4 gen() 6199 MB/s
[ 3.517946] raid6: sse2x4 xor() 4616 MB/s
[ 3.517947] raid6: using algorithm sse2x4 gen() 6199 MB/s
[ 3.517948] raid6: …. xor() 4616 MB/s, rmw enabled
[ 3.517949] raid6: using ssse3x2 recovery algorithm
[ 3.518010] clocksource: Switched to clocksource tsc
[ 3.519756] xor: measuring software checksum speed
[ 3.557938] prefetch64-sse: 8762.000 MB/sec
[ 3.597935] generic_sse: 8060.000 MB/sec
[ 3.597937] xor: using function: prefetch64-sse (8762.000 MB/sec)
[ 3.621335] Btrfs loaded, crc32c=crc32c-intel
[ 3.886484] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[ 5.265174] systemd[1]: systemd 229 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN)
[ 5.265334] systemd[1]: Detected architecture x86-64.
[ 5.274468] systemd[1]: Set hostname to <USER-03>.
[ 5.377056] random: crng init done
[ 6.482468] systemd[1]: Listening on LVM2 poll daemon socket.
[ 6.482601] systemd[1]: Listening on Journal Socket.
[ 6.482666] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[ 6.482700] systemd[1]: Listening on Syslog Socket.
[ 6.482743] systemd[1]: Listening on Device-mapper event daemon FIFOs.
[ 6.482757] systemd[1]: Reached target Remote File Systems (Pre).
[ 6.482793] systemd[1]: Listening on udev Kernel Socket.
[ 16.419040] lp: driver loaded but no devices found
[ 17.388700] ppdev: user-space parallel port driver
[ 17.563144] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
[ 17.576103] systemd-journald[338]: Received request to flush runtime journal from PID 1
[ 17.819675] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 17.859739] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (PMIO) (20160930/utaddress-247)
[ 17.859747] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 17.859751] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (GPIO) (20160930/utaddress-247)
[ 17.859755] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 17.859755] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (GPIO) (20160930/utaddress-247)
[ 17.859759] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 17.859760] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (GPIO) (20160930/utaddress-247)
[ 17.859763] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 17.859764] lpc_ich: Resource conflict(s) found affecting gpio_ich
[ 17.859766] lpc_ich 0000:00:1f.0: No MFD cells added
[ 17.929564] rtl8192ce: Using firmware rtlwifi/rtl8192cfw.bin
[ 17.939796] ieee80211 phy0: Selected rate control algorithm ‘rtl_rc’
[ 17.940109] rtlwifi: rtlwifi: wireless switch is on
[ 18.007229] RAPL PMU: API unit is 2^-32 Joules, 3 fixed counters, 163840 ms ovfl timer
[ 18.007231] RAPL PMU: hw unit of domain pp0-core 2^-16 Joules
[ 18.007232] RAPL PMU: hw unit of domain package 2^-16 Joules
[ 18.007233] RAPL PMU: hw unit of domain pp1-gpu 2^-16 Joules
[ 18.050772] audit: type=1400 audit(1507270058.214:2): apparmor=»STATUS» operation=»profile_load» profile=»unconfined» name=»/sbin/dhclient» pid=600 comm=»apparmor_parser»
[ 18.050774] audit: type=1400 audit(1507270058.214:3): apparmor=»STATUS» operation=»profile_load» profile=»unconfined» name=»/usr/lib/NetworkManager/nm-dhcp-client.action» pid=600 comm=»apparmor_parser»
[ 18.050776] audit: type=1400 audit(1507270058.214:4): apparmor=»STATUS» operation=»profile_load» profile=»unconfined» name=»/usr/lib/NetworkManager/nm-dhcp-helper» pid=600 comm=»apparmor_parser»
[ 18.050777] audit: type=1400 audit(1507270058.214:5): apparmor=»STATUS» operation=»profile_load» profile=»unconfined» name=»/usr/lib/connman/scripts/dhclient-script» pid=600 comm=»apparmor_parser»
[ 18.060663] audit: type=1400 audit(1507270058.222:6): apparmor=»STATUS» operation=»profile_load» profile=»unconfined» name=»/usr/lib/lightdm/lightdm-guest-session» pid=599 comm=»apparmor_parser»
[ 18.060666] audit: type=1400 audit(1507270058.222:7): apparmor=»STATUS» operation=»profile_load» profile=»unconfined» name=»/usr/lib/lightdm/lightdm-guest-session//chromium» pid=599 comm=»apparmor_parser»
[ 18.062100] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC269VC: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[ 18.062103] snd_hda_codec_realtek hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[ 18.062105] snd_hda_codec_realtek hdaudioC0D0: hp_outs=1 (0x15/0x0/0x0/0x0/0x0)
[ 18.062106] snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0
[ 18.062107] snd_hda_codec_realtek hdaudioC0D0: inputs:
[ 18.062110] snd_hda_codec_realtek hdaudioC0D0: Mic=0x18
[ 18.062111] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12
[ 18.065005] audit: type=1400 audit(1507270058.226:8): apparmor=»STATUS» operation=»profile_load» profile=»unconfined» name=»/usr/sbin/cups-browsed» pid=604 comm=»apparmor_parser»
[ 18.073835] snd_hda_intel 0000:00:1b.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[ 18.080883] audit: type=1400 audit(1507270058.242:9): apparmor=»STATUS» operation=»profile_load» profile=»unconfined» name=»/usr/lib/cups/backend/cups-pdf» pid=607 comm=»apparmor_parser»
[ 18.080886] audit: type=1400 audit(1507270058.242:10): apparmor=»STATUS» operation=»profile_load» profile=»unconfined» name=»/usr/sbin/cupsd» pid=607 comm=»apparmor_parser»
[ 18.080888] audit: type=1400 audit(1507270058.242:11): apparmor=»STATUS» operation=»profile_load» profile=»unconfined» name=»/usr/sbin/cupsd//third_party» pid=607 comm=»apparmor_parser»
[ 18.114153] input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input7
[ 18.114229] input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input8
[ 18.114295] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
[ 18.131489] intel_rapl: Found RAPL domain package
[ 18.131492] intel_rapl: Found RAPL domain core
[ 18.131493] intel_rapl: Found RAPL domain uncore
[ 18.131498] intel_rapl: RAPL package 0 domain package locked by BIOS
[ 18.396259] rtl8192ce 0000:02:00.0 wlp2s0: renamed from wlan0
[ 18.485864] media: Linux media interface: v0.10
[ 18.499727] Linux video capture interface: v2.00
[ 18.512157] uvcvideo: Found UVC 1.00 device Lenovo USB2.0 UVC Camera (174f:1482)
[ 18.517668] uvcvideo 2-1.3:1.0: Entity type for entity Extension 5 was not initialized!
[ 18.517672] uvcvideo 2-1.3:1.0: Entity type for entity Extension 2 was not initialized!
[ 18.517674] uvcvideo 2-1.3:1.0: Entity type for entity Processing 3 was not initialized!
[ 18.517675] uvcvideo 2-1.3:1.0: Entity type for entity Camera 1 was not initialized!
[ 18.517871] input: Lenovo USB2.0 UVC Camera as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0/input/input10
[ 18.518139] usbcore: registered new interface driver uvcvideo
[ 18.518140] USB Video Class driver (1.1.1)
[ 19.623684] usblp 2-1.1.1:1.1: usblp0: USB Bidirectional printer dev 5 if 1 alt 0 proto 2 vid 0x03F0 pid 0x4D17
[ 19.623717] usbcore: registered new interface driver usblp
[ 66.797267] usb 1-1.2: USB disconnect, device number 4
[ 68.298902] usb 1-1.2: new low-speed USB device number 5 using ehci-pci
[ 68.411322] usb 1-1.2: New USB device found, idVendor=17ef, idProduct=602e
[ 68.411326] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 68.411328] usb 1-1.2: Product: USB Optical Mouse
[ 68.411329] usb 1-1.2: Manufacturer: PixArt
[ 68.414298] input: PixArt USB Optical Mouse as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/0003:17EF:602E.0004/input/input11
[ 68.414506] hid-generic 0003:17EF:602E.0004: input,hidraw2: USB HID v1.11 Mouse [PixArt USB Optical Mouse] on usb-0000:00:1a.0-1.2/input0
[ 96.657066] cgroup: new mount options do not match the existing superblock, will be ignored
[ 99.712935] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 100.059846] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 100.064918] IPv6: ADDRCONF(NETDEV_UP): enp1s0f2: link is not ready
[ 100.208341] r8169 0000:01:00.2 enp1s0f2: link down
[ 100.208344] r8169 0000:01:00.2 enp1s0f2: link down
[ 100.208413] IPv6: ADDRCONF(NETDEV_UP): enp1s0f2: link is not ready
[ 100.328175] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 102.377404] kauditd_printk_skb: 8 callbacks suppressed
[ 102.377407] audit: type=1400 audit(1507270142.546:20): apparmor=»DENIED» operation=»capable» profile=»/usr/sbin/cupsd» pid=993 comm=»usb» capability=35 capname=»wake_alarm»
[ 102.378268] usblp0: removed
[ 102.384185] usblp 2-1.1.1:1.1: usblp0: USB Bidirectional printer dev 5 if 1 alt 0 proto 2 vid 0x03F0 pid 0x4D17
[ 105.063259] FS-Cache: Loaded
[ 105.078851] FS-Cache: Netfs ‘cifs’ registered for caching
[ 105.078969] Key type cifs.spnego registered
[ 105.078971] Key type cifs.idmap registered
[ 105.085333] CIFS VFS: Error connecting to socket. Aborting operation.
[ 105.086024] CIFS VFS: cifs_mount failed w/return code = -101
[ 107.904701] r8169 0000:01:00.2 enp1s0f2: link up
[ 107.904712] IPv6: ADDRCONF(NETDEV_CHANGE): enp1s0f2: link becomes ready
[ 116.862242] audit: type=1400 audit(1507270157.030:21): apparmor=»DENIED» operation=»file_lock» profile=»/usr/share/hplip/systray.py» name=»/etc/xdg/Trolltech.conf» pid=1756 comm=»python» requested_mask=»k» denied_mask=»k» fsuid=1000 ouid=0
[ 118.092390] audit: type=1400 audit(1507270158.262:22): apparmor=»DENIED» operation=»file_lock» profile=»/usr/share/hplip/systray.py» name=»/etc/xdg/sni-qt.conf» pid=1756 comm=»python» requested_mask=»k» denied_mask=»k» fsuid=1000 ouid=0
[ 2045.903568] audit: type=1400 audit(1507272086.626:23): apparmor=»DENIED» operation=»capable» profile=»/usr/sbin/cupsd» pid=4590 comm=»usb» capability=35 capname=»wake_alarm»
[ 2045.910208] usblp0: removed
[ 2609.982295] usblp0: removed
[ 2611.239151] usblp 2-1.1.1:1.1: usblp0: USB Bidirectional printer dev 5 if 1 alt 0 proto 2 vid 0x03F0 pid 0x4D17
[ 8084.333708] perf: interrupt took too long (2518 > 2500), lowering kernel.perf_event_max_sample_rate to 79250
[10849.133883] perf: interrupt took too long (3156 > 3147), lowering kernel.perf_event_max_sample_rate to 63250
[13556.350379] perf: interrupt took too long (3948 > 3945), lowering kernel.perf_event_max_sample_rate to 50500
[14364.629111] usblp0: removed
[14367.141745] usblp 2-1.1.1:1.1: usblp0: USB Bidirectional printer dev 5 if 1 alt 0 proto 2 vid 0x03F0 pid 0x4D17
[16438.318667] usblp0: removed
[16439.826792] usblp 2-1.1.1:1.1: usblp0: USB Bidirectional printer dev 5 if 1 alt 0 proto 2 vid 0x03F0 pid 0x4D17
[16519.737054] usb 2-1.2: new high-speed USB device number 6 using ehci-pci
[16519.848709] usb 2-1.2: New USB device found, idVendor=0471, idProduct=082b
[16519.848712] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[16519.848714] usb 2-1.2: Product: USB Flash Drive
[16519.848716] usb 2-1.2: Manufacturer: Philips
[16519.848717] usb 2-1.2: SerialNumber: 0601240200023028
[16519.995192] usb-storage 2-1.2:1.0: USB Mass Storage device detected
[16519.995353] scsi host5: usb-storage 2-1.2:1.0
[16519.995873] usbcore: registered new interface driver usb-storage
[16520.012036] usbcore: registered new interface driver uas
[16521.014728] scsi 5:0:0:0: Direct-Access Philips USB Flash Drive 3000 PQ: 0 ANSI: 0 CCS
[16521.016353] sd 5:0:0:0: Attached scsi generic sg2 type 0
[16521.019546] sd 5:0:0:0: [sdb] 1014784 512-byte logical blocks: (520 MB/496 MiB)
[16521.020548] sd 5:0:0:0: [sdb] Write Protect is off
[16521.020551] sd 5:0:0:0: [sdb] Mode Sense: 43 00 00 00
[16521.021669] sd 5:0:0:0: [sdb] No Caching mode page found
[16521.021675] sd 5:0:0:0: [sdb] Assuming drive cache: write through
[16521.084254] sdb: sdb1
[16521.088161] sd 5:0:0:0: [sdb] Attached SCSI removable disk
[16527.283552] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[16543.934676] FAT-fs (sdb1): error, fat_free_clusters: deleting FAT entry beyond EOF
[16543.934682] FAT-fs (sdb1): Filesystem has been set read-only
[16699.721161] usblp0: removed
[18595.303193] usblp0: removed
[18595.304861] Did not find alt setting 1 for intf 0, config 1
[20378.753105] usb 2-1.2: USB disconnect, device number 6
[32273.787314] perf: interrupt took too long (4970 > 4935), lowering kernel.perf_event_max_sample_rate to 40000
gogoleva@USER-03 ~ $

  • Home
  • Forum
  • The Ubuntu Forum Community
  • Ubuntu Official Flavours Support
  • General Help
  • [SOLVED] CIFS VFS error connecting to socket

  1. CIFS VFS error connecting to socket

    I am posting this in case it helps someone with the same problem.

    I am using Lucid. I moved computers around and the one I began using could not see the rest of the network; although the other computers on the network could see it. When booting I would get the message «CIFS VFS error connecting to socket. Aborting operation.» and «CIFS_mount failed». I tried some fixes from the forums that did not work. Finally, I looked at /etc/fstab on one of the other computers and I found that there were some lines on the misbehaving computer:

    The server samba share
    \\192.168.1.100\data /media/server_public cifs guest,uid=1000,iocharset=utf8,codepage=unicode,uni code 0 0
    /tmp/hfsimage /macdisk hfs defaults,noauto,user,loop 0 0

    I commented them out and rebooted. All is good now.

    Last edited by ncpokrt; August 13th, 2010 at 04:29 PM.


  2. Re: CIFS VFS error connecting to socket

    Quote Originally Posted by ncpokrt
    View Post

    I am posting this in case it helps someone with the same problem.

    I am using Lucid. I moved computers around and the one I began using could not see the rest of the network; although the other computers on the network could see it. When booting I would get the message «CIFS VFS error connecting to socket. Aborting operation.» and «CIFS_mount failed». I tried some fixes from the forums that did not work. Finally, I looked at /etc/fstab on one of the other computers and I found that there were some lines on the misbehaving computer:

    The server samba share
    \\192.168.1.100\data /media/server_public cifs guest,uid=1000,iocharset=utf8,codepage=unicode,uni code 0 0
    /tmp/hfsimage /macdisk hfs defaults,noauto,user,loop 0 0

    I commented them out and rebooted. All is good now.

    Thanks ncpokrt! I was having this exact issue and your post was very helpful


Bookmarks

Bookmarks


Posting Permissions

The Problem

CIFS shared file system is not mounted even after system reboot in CentOS/RHEL 7. If manually execute the “mount -a” command after the system is rebooted, the CIFS file system is normally mounted

fstab entry:

# cat /etc/fstab
//192.168.0.10/Oracle /backup/oracle cifs _netdev,noexec,nosuid,vers=3.0,uid=1001,gid=1002,credentials=/root/backup_creds 0 0

demsg:

[ 27.052981] Key type cifs.idmap registered
[ 33.053711] CIFS VFS: Error connecting to socket. Aborting operation.
[ 33.054048] CIFS VFS: cifs_mount failed w/return code = -113

/var/log/messages:

Nov 21 15:09:29 ***** kernel: CIFS VFS: Error connecting to socket. Aborting operation.
Nov 21 15:09:29 ***** kernel: CIFS VFS: cifs_mount failed w/return code = -113
Nov 21 15:09:29 ***** mount: Unable to find suitable address.
Nov 21 15:09:29 ***** systemd: backup-oracle.mount mount process exited, code=exited status=32
Nov 21 15:09:29 ***** systemd: Failed to mount /backup/oracle.
Nov 21 15:09:29 ***** systemd: Dependency failed for Remote File Systems.
Nov 21 15:09:29 ***** systemd: Job remote-fs.target/start failed with result 'dependency'.
Nov 21 15:09:29 ***** systemd: Unit backup-oracle.mount entered failed state.

The Solution

Mount units referring to local and network file systems are distinguished by their file system type specification. In some cases, this is not sufficient (for example network block device based mounts, such as iSCSI), in which case _netdev may be added to the mount option string of the unit, which forces systemd to consider the mount unit a network mount.

Additionally, systemd supports explicit order dependencies between mount entries and other units. There are 2 ways this issue can be resolved:

1. adding in x-systemd.after=network-online.target in /etc/fstab to the mount options:

//192.168.0.10/Oracle /backup/oracle cifs _netdev,x-systemd.after=network-online.target,noexec,nosuid,vers=3.0,uid=1001,gid=1002,credentials=/root/backup_creds 0 0

2. create custom systemd unit file in /etc/systemd/system with file format samba.service[Unit]:

# vi /etc/systemd/system
Description=CIFS Mount
Requires=network-online.target
After=network-online.service
Before=samba.service
[Mount]
What=//xxx.xxx.xxx.xxx/path/[mountpoint]
Where=/mnt/path
Options=username=yourusername,pass=yourpassword
Type=cifs

[Install]
WantedBy=multi-user.target

Многие годы в fstab у меня было прописано монтирование ресурсов на сетевом хранилище

//X.X.X.X/kino /mnt/dl315/kino cifs vers=1.0,auto,rw,_netdev,noperm,uid=500,gid=500,file_mode=0666,iocharset=utf8,users,credentials=/etc/samba/smbcr_a 0 0
И всё прекрасно монтировалось при старте.
И вдруг монтирование при старте пропало. Сначала подумал «случайность». Нет. Закономерность.
После старта руками прекрасно монтируется.
Покопавшись в логах выяснил, что что всё это произошло после dist-ugrade 2020-02-23. Обновилось 199 пакетов.

$ journalctl -b -3 --no-pager | grep installed | wc -l
199

В логах появилось такое

ICI3.lan kernel: FS-Cache: Netfs 'cifs' registered for caching
ICI3.lan kernel: Key type cifs.spnego registered
ICI3.lan kernel: Key type cifs.idmap registered
ICI3.lan kernel: CIFS VFS: Error connecting to socket. Aborting operation.
ICI3.lan kernel: CIFS VFS: cifs_mount failed w/return code = -101
ICI3.lan kernel: CIFS VFS: Error connecting to socket. Aborting operation.
ICI3.lan kernel: CIFS VFS: cifs_mount failed w/return code = -101

Если при старте убрать сплеш, то видно как материться где-то так

"Не могу смонтировать /mnt/dl315/kino по причине отсутсвия сети"
Технические подробности:
Ситема = KWorkstation p9 64bit
Сетью управляет etcnet (поскольку комп стационарный, к сети подключен витой парой, и в НетворкМенеджере необходимости нет).
Роутер и сетевое хранилище никогда не выключаются.

Как оживить монтирование при старте?


Записан

Если я попался вам навстречу, Значит вам со мной не по пути.
(С) Воскресение


Скорее всего, в таком случае лучше Вам юнит для systemd оформить, где указать зависимость, что подключать сетевые ресурсы следует после соединения сети…


Записан


Скорее всего, в таком случае лучше Вам юнит для systemd оформить, где указать зависимость, что подключать сетевые ресурсы следует после соединения сети…

1. А где-то образец есть?

2. Как-то странно. Работало-работало = и упсс!


Записан

Если я попался вам навстречу, Значит вам со мной не по пути.
(С) Воскресение


Возможно статья по ссылке Вам покажется не авторитетной, но как по Мне, в ней достаточно той информации, с помощью которой можно начать погружаться в тему…


Записан


Многие годы в fstab у меня было прописано монтирование ресурсов на сетевом хранилище//X.X.X.X/kino /mnt/dl315/kino cifs vers=1.0,auto,rw,_netdev,noperm,uid=500,gid=500,file_mode=0666,iocharset=utf8,users,credentials=/etc/samba/smbcr_a 0 0
И всё прекрасно монтировалось при старте.
И вдруг монтирование при старте пропало. Сначала подумал «случайность». Нет. Закономерность.
После старта руками прекрасно монтируется.
Покопавшись в логах выяснил, что что всё это произошло после dist-ugrade 2020-02-23. Обновилось 199 пакетов.
$ journalctl -b -3 --no-pager | grep installed | wc -l
199

В логах появилось такое
ICI3.lan kernel: FS-Cache: Netfs 'cifs' registered for caching
ICI3.lan kernel: Key type cifs.spnego registered
ICI3.lan kernel: Key type cifs.idmap registered
ICI3.lan kernel: CIFS VFS: Error connecting to socket. Aborting operation.
ICI3.lan kernel: CIFS VFS: cifs_mount failed w/return code = -101
ICI3.lan kernel: CIFS VFS: Error connecting to socket. Aborting operation.
ICI3.lan kernel: CIFS VFS: cifs_mount failed w/return code = -101

Если при старте убрать сплеш, то видно как материться где-то так "Не могу смонтировать /mnt/dl315/kino по причине отсутсвия сети" Не могу смонтировать /mnt/dl315/kino по причине отсутсвия сети

Технические подробности:
Ситема = KWorkstation p9 64bit
Сетью управляет etcnet (поскольку комп стационарный, к сети подключен витой парой, и в НетворкМенеджере необходимости нет).

Угу.
Ошибка 101: [SOLVED] Samba, error(101): Network is unreachable
Монтирование сетевого ресурса раньше, чем был поднят сетевой сервис.


Записан


Скорее всего, в таком случае лучше Вам юнит для systemd оформить, где указать зависимость, что подключать сетевые ресурсы следует после соединения сети…

1. А где-то образец есть?

Есть.
Вам нужно в systemd заново изобрести очерёдность старт-стоп sysvinit.
Тестируйте:
Скрипт монтирует cifs ресурс только после старта сетевого сервиса, —  прописать в скрипте команду монтирования в процедуре start(). Скрипт учитывает очерёдность старта и NetworkManager. Имеет LSB хидер для использования в системах на systemd.

$ cat cifsmount

#!/bin/sh
#
# cifsmount:   mounting and unmounting of the cifs resource
#
# chkconfig: 345 92 34
# description:  mounting and unmounting of the cifs resource
#
### BEGIN INIT INFO
# Provides: cifsmount
# Required-Start: $local_fs $network $remote_fs $named $time
# Required-Stop: $local_fs $network $remote_fs $named
# Default-Start:  3 4 5
# Default-Stop: 0 1 6
# Description: mounting and unmounting of the cifs resource
### END INIT INFO

# Do not load RH compatibility interface.
WITHOUT_RC_COMPAT=1

# Source function library.
. /etc/init.d/functions

LOCKFILE=/var/lock/subsys/cifsmount
RETVAL=0

start() {
    # mounting cifs resource
    touch "$LOCKFILE"
    команда монтирования cifs ресурса
    return $RETVAL
}

stop() {
    # Umount all cifs
    rm -f "$LOCKFILE"
    umount -a -t cifs
    return $RETVAL
}

case "$1" in
    start)
start
;;
    stop)
stop
        ;;
    *)
        echo $"Usage: $0 {start|stop}"
        exit 1
esac
exit 0


LSB-хидер нужен для того, чтобы сервис мог работать и в системах на systemd, правильно обрабатывая старт-стоп.

2. Как-то странно. Работало-работало = и упсс!

Speccyfighter ехидно хихикает…
А вы думаете Speccyfighter от нечего делать уже который раз цитирует пункт 6 статьи спектрумовского электронного журнала Oberon #02? С толстым намёком на Линукс-разработчиков. Это специально когда-то было написано спектрум-кодером для программистов, чтобы не было этих «Работало-работало = и упсс!». И чтобы не было регрессий, которыми называют рукожопый код.

« Последнее редактирование: 27.02.2020 12:28:13 от Speccyfighter »


Записан


Многие годы в fstab у меня было прописано монтирование ресурсов на сетевом хранилище

Покопавшись в логах выяснил, что что всё это произошло после dist-ugrade 2020-02-23. Обновилось 199 пакетов.

В логах появилось такое
...
ICI3.lan kernel: CIFS VFS: Error connecting to socket. Aborting operation.
ICI3.lan kernel: CIFS VFS: cifs_mount failed w/return code = -101

Если при старте убрать сплеш, то видно как материться где-то так "Не могу смонтировать /mnt/dl315/kino по причине отсутсвия сети"

Это тянет на багрепорт.

« Последнее редактирование: 27.02.2020 12:22:16 от Speccyfighter »


Записан


Скорее всего, в таком случае лучше Вам юнит для systemd оформить, где указать зависимость, что подключать сетевые ресурсы следует после соединения сети…

видимо systemd то ли не знал, то ли забыл, что такое опция _netdev в fstab.


Записан


Многие годы в fstab у меня было прописано монтирование ресурсов на сетевом хранилище

Если не секрет, почему не autofs?


Записан


Понравилась статья? Поделить с друзьями:
  • Cifs mount error 112 host is down
  • Cid font dictionary error
  • Ciblockelement add error
  • Ci модуль ошибка нет доступа
  • Cisco anyconnect secure gateway internal error