Перейти до

Куди подівся пакет flow-tools в Debian 11 та 12


Рекомендованные сообщения

Після апгрейду сервера виявилось, що пакет flow-tools, що був у Дебіан 10, зник , починаючи з версії 11. Пошук по офсайту не дав ніяких пояснень. Може шановне панство підкаже, який пакет передбачений на заміну flow-tools для реалізації netflow-коллектора? Чи не гаяти часу і збирати самостійно?..

Ссылка на сообщение
Поделиться на других сайтах

Судячи з нагугленого, то майнтейнер забив на підтримку.
Я навіть сорців для білду на перший побіжний погляд не знайшов.
Такі то справи)

Ссылка на сообщение
Поделиться на других сайтах

цей пакет перестали підтримувати  навіть сорци дуже проблемно збираються

 

поки що один з виходів бачимо перехід на NfSen

Ссылка на сообщение
Поделиться на других сайтах

Создайте аккаунт или войдите в него для комментирования

Вы должны быть пользователем, чтобы оставить комментарий

Создать аккаунт

Зарегистрируйтесь для получения аккаунта. Это просто!

Зарегистрировать аккаунт

Вхід

Уже зарегистрированы? Войдите здесь.

Войти сейчас
  • Зараз на сторінці   0 користувачів

    Немає користувачів, що переглядають цю сторінку.

  • Схожий контент

    • Від FOP_Osypenko
      Маємо VPS сервер на Debian 10 і модем MikroTik LHG LTE6. Задача наступна: налаштувати інтернет через VPN тунель.
       
      На сервер Debian 10 встановив і налаштував WireGuard скриптом: https://github.com/angristan/wireguard-install
      Цим же скриптом згенерував файл налаштувань для клієнта wg0-client-mikrotik.conf:
      [Interface] PrivateKey = yBen7Arcy/jRqB3zqJiPn88IHPCoHYRmRW3wT97D2F0= Address = 10.66.66.2/32,fd42:42:42::2/128 DNS = 94.140.14.14,94.140.15.15 [Peer] PublicKey = 004DOgL44aNB5tWmyoifjiGmi0qBIHdp3Og21EdjUV0= PresharedKey = P8nLh48thuDSvNMJ7XPqMknWp4hpfxE4RUIuf5UBGqQ= Endpoint = 145.239.95.214:53849 AllowedIPs = 0.0.0.0/0,::/0  
      Прошивку на Mikrotik оновив до версії 7.1beta5. В цій версії вже вбудована підтримка WireGuarg.
      В головному меню WinBox обираю пункт WireGuard і відкривається таке вікно:

       
      Створюю новий інтерфейс wiregoard1 з типовими параметрами. Змін ніяких не вношу.

       
      Далі переходжу на вкладку Peers і там створюю новий тунель. Вписую параметри з клієнтського файлу конфігурації.

       
      Далі відкриваю вікно Address List і додаю адресу. Параметри знову беру з клієнтського файлу конфігурації.

       
      Після цих налаштувань нічого не змінюється й інтернет через VPN тунель не йде. Можливо щось не так налаштовую чи не повністю?
    • Від axl72
      Здравствуйте , коллеги.
       
      Поднимаем iptv на линукс-сервере с несколькими разными  DVB картами от TBS.
      Есть одна неприятность. При перезагрузке нумерация DVB адаптеров непредсказуемо меняется. Соответственно конфиги приходится каждый раз подправлять.
      Используем Debian 10.2 Buster  c Systemd.
      Предполагаю, что это происходит из за распараллеливания процесса загрузки и определения оборудования в Systemd.
      Думал о том, что бы использовать udev rules, но из за специфики именования dvd адаптеров не понял как это сделать.
       
      Наверняка уже кто то сталкивался  с таким поведением, как решили проблему? 
      Может отказаться от Systemd и установить SysVinit ? поможет ли?
      Или вообще имеет смысл откатиться на более древний дистрибутив Debian ? И будет ли на нем работать Astra 5.xx
       
      Предвижу ответы в стиле "Вот возьми , да и проверь сам", именно так мы и сделаем, но хотелось бы минимизировать downtime - сервер уже в продакшене.
       
    • Від Archy_k
      Всем привет.
      Столкнулся с проблемой: не обновился сертификат SSL.
      Попробовал вручную запустить скрипт:
      # /etc/letsencrypt/certbot/certbot-auto renew Creating virtual environment... Installing Python packages... /opt/eff.org/certbot/venv/bin/python: No module named pip.__main__; 'pip' is a package and cannot be directly executed Traceback (most recent call last):   File "/tmp/tmp.qUAUXX5FHZ/pipstrap.py", line 177, in <module>     sys.exit(main())   File "/tmp/tmp.qUAUXX5FHZ/pipstrap.py", line 149, in main     pip_version = StrictVersion(check_output([python, '-m', 'pip', '--version'])   File "/usr/lib/python2.7/subprocess.py", line 544, in check_output     raise CalledProcessError(retcode, cmd, output=output) subprocess.CalledProcessError: Command '['/opt/eff.org/certbot/venv/bin/python', '-m', 'pip', '--version']' returned non-zero exit status 1 И вот какой ответ получаю.
      Подскажите пожалуйста, как с этим справиться...
      Сервер с Debian и nginx
      Заранее спасибо.
    • Від Futura
      Имеется тазик на Debian c двумя сетевухами:
      Internet-eth0<NAT<eth1-PPPoE
      Если установить еще одну карточку (пусть будет eth2) c резервным каналом
      как организовать автоматическое переключение при падении основного и корректную работу NAT?
    • Від fet4
      Приветствую!
      Подскажите сыпет вот такое в лог и система доступна только для чтения. Я так понял мрет диск, ssd стоит?
      Feb 10 11:05:08 srv-bill kernel: [ 549.009768] ata2.00: exception Emask 0x10 SAct 0x700 SErr 0x400100 action 0x6 frozen Feb 10 11:05:08 srv-bill kernel: [ 549.009796] ata2.00: irq_stat 0x08000000, interface fatal error Feb 10 11:05:08 srv-bill kernel: [ 549.009812] ata2: SError: { UnrecovData Handshk } Feb 10 11:05:08 srv-bill kernel: [ 549.009827] ata2.00: failed command: WRITE FPDMA QUEUED Feb 10 11:05:08 srv-bill kernel: [ 549.009844] ata2.00: cmd 61/40:40:00:d8:52/05:00:00:00:00/40 tag 8 ncq 688128 out Feb 10 11:05:08 srv-bill kernel: [ 549.009844] res 40/00:50:80:e2:52/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Feb 10 11:05:08 srv-bill kernel: [ 549.009882] ata2.00: status: { DRDY } Feb 10 11:05:08 srv-bill kernel: [ 549.009893] ata2.00: failed command: WRITE FPDMA QUEUED Feb 10 11:05:08 srv-bill kernel: [ 549.009917] ata2.00: cmd 61/40:48:40:dd:52/05:00:00:00:00/40 tag 9 ncq 688128 out Feb 10 11:05:08 srv-bill kernel: [ 549.009917] res 40/00:50:80:e2:52/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Feb 10 11:05:08 srv-bill kernel: [ 549.009957] ata2.00: status: { DRDY } Feb 10 11:05:08 srv-bill kernel: [ 549.009969] ata2.00: failed command: WRITE FPDMA QUEUED Feb 10 11:05:08 srv-bill kernel: [ 549.009984] ata2.00: cmd 61/80:50:80:e2:52/05:00:00:00:00/40 tag 10 ncq 720896 out Feb 10 11:05:08 srv-bill kernel: [ 549.009984] res 40/00:50:80:e2:52/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Feb 10 11:05:08 srv-bill kernel: [ 549.010032] ata2.00: status: { DRDY } Feb 10 11:05:08 srv-bill kernel: [ 549.010045] ata2: hard resetting link Feb 10 11:05:08 srv-bill kernel: [ 549.333504] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Feb 10 11:05:08 srv-bill kernel: [ 549.344451] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140926/psargs-359) Feb 10 11:05:08 srv-bill kernel: [ 549.344468] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff88011e8442c0), AE_NOT_FOUND (20140926/psparse-536) Feb 10 11:05:08 srv-bill kernel: [ 549.364345] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140926/psargs-359) Feb 10 11:05:08 srv-bill kernel: [ 549.364349] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff88011e8442c0), AE_NOT_FOUND (20140926/psparse-536) Feb 10 11:05:08 srv-bill kernel: [ 549.374424] ata2.00: configured for UDMA/133 Feb 10 11:05:08 srv-bill kernel: [ 549.374446] ata2: EH complete Feb 10 11:05:08 srv-bill kernel: [ 549.381458] ata2.00: exception Emask 0x10 SAct 0x3800 SErr 0x400100 action 0x6 frozen Feb 10 11:05:08 srv-bill kernel: [ 549.381484] ata2.00: irq_stat 0x08000000, interface fatal error Feb 10 11:05:08 srv-bill kernel: [ 549.382155] ata2: SError: { UnrecovData Handshk } Feb 10 11:05:08 srv-bill kernel: [ 549.382830] ata2.00: failed command: WRITE FPDMA QUEUED Feb 10 11:05:08 srv-bill kernel: [ 549.383504] ata2.00: cmd 61/80:58:80:e2:52/05:00:00:00:00/40 tag 11 ncq 720896 out Feb 10 11:05:08 srv-bill kernel: [ 549.383504] res 40/00:68:00:d8:52/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Feb 10 11:05:08 srv-bill kernel: [ 549.384843] ata2.00: status: { DRDY } Feb 10 11:05:08 srv-bill kernel: [ 549.385520] ata2.00: failed command: WRITE FPDMA QUEUED Feb 10 11:05:08 srv-bill kernel: [ 549.386238] ata2.00: cmd 61/40:60:40:dd:52/05:00:00:00:00/40 tag 12 ncq 688128 out Feb 10 11:05:08 srv-bill kernel: [ 549.386238] res 40/00:68:00:d8:52/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Feb 10 11:05:08 srv-bill kernel: [ 549.387582] ata2.00: status: { DRDY } Feb 10 11:05:08 srv-bill kernel: [ 549.388249] ata2.00: failed command: WRITE FPDMA QUEUED Feb 10 11:05:08 srv-bill kernel: [ 549.388934] ata2.00: cmd 61/40:68:00:d8:52/05:00:00:00:00/40 tag 13 ncq 688128 out Feb 10 11:05:08 srv-bill kernel: [ 549.388934] res 40/00:68:00:d8:52/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Feb 10 11:05:08 srv-bill kernel: [ 549.390268] ata2.00: status: { DRDY } Feb 10 11:05:08 srv-bill kernel: [ 549.390959] ata2: hard resetting link Feb 10 11:05:08 srv-bill kernel: [ 549.709195] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Feb 10 11:05:08 srv-bill kernel: [ 549.720088] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140926/psargs-359) Feb 10 11:05:08 srv-bill kernel: [ 549.720093] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff88011e8442c0), AE_NOT_FOUND (20140926/psparse-536) Feb 10 11:05:08 srv-bill kernel: [ 549.740031] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140926/psargs-359) Feb 10 11:05:08 srv-bill kernel: [ 549.740035] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff88011e8442c0), AE_NOT_FOUND (20140926/psparse-536) Feb 10 11:05:09 srv-bill kernel: [ 549.750094] ata2.00: configured for UDMA/133 Feb 10 11:05:09 srv-bill kernel: [ 549.750115] ata2: EH complete Feb 10 11:05:09 srv-bill kernel: [ 549.757177] ata2.00: exception Emask 0x10 SAct 0x1c000 SErr 0x400100 action 0x6 frozen Feb 10 11:05:09 srv-bill kernel: [ 549.757928] ata2.00: irq_stat 0x08000000, interface fatal error Feb 10 11:05:09 srv-bill kernel: [ 549.758665] ata2: SError: { UnrecovData Handshk } Feb 10 11:05:09 srv-bill kernel: [ 549.759403] ata2.00: failed command: WRITE FPDMA QUEUED Feb 10 11:05:09 srv-bill kernel: [ 549.760148] ata2.00: cmd 61/40:70:00:d8:52/05:00:00:00:00/40 tag 14 ncq 688128 out Feb 10 11:05:09 srv-bill kernel: [ 549.760148] res 40/00:80:80:e2:52/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Feb 10 11:05:09 srv-bill kernel: [ 549.761810] ata2.00: status: { DRDY } Feb 10 11:05:09 srv-bill kernel: [ 549.762609] ata2.00: failed command: WRITE FPDMA QUEUED Feb 10 11:05:09 srv-bill kernel: [ 549.763399] ata2.00: cmd 61/40:78:40:dd:52/05:00:00:00:00/40 tag 15 ncq 688128 out Feb 10 11:05:09 srv-bill kernel: [ 549.763399] res 40/00:80:80:e2:52/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Feb 10 11:05:09 srv-bill kernel: [ 549.764931] ata2.00: status: { DRDY } Feb 10 11:05:09 srv-bill kernel: [ 549.765663] ata2.00: failed command: WRITE FPDMA QUEUED Feb 10 11:05:09 srv-bill kernel: [ 549.766402] ata2.00: cmd 61/80:80:80:e2:52/05:00:00:00:00/40 tag 16 ncq 720896 out Feb 10 11:05:09 srv-bill kernel: [ 549.766402] res 40/00:80:80:e2:52/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Feb 10 11:05:09 srv-bill kernel: [ 549.767760] ata2.00: status: { DRDY } Feb 10 11:05:09 srv-bill kernel: [ 549.768495] ata2: hard resetting link Feb 10 11:05:09 srv-bill kernel: [ 550.084889] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Feb 10 11:05:09 srv-bill kernel: [ 550.095786] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140926/psargs-359) Feb 10 11:05:09 srv-bill kernel: [ 550.095792] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff88011e8442c0), AE_NOT_FOUND (20140926/psparse-536) Feb 10 11:05:09 srv-bill kernel: [ 550.115742] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140926/psargs-359) Feb 10 11:05:09 srv-bill kernel: [ 550.115747] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff88011e8442c0), AE_NOT_FOUND (20140926/psparse-536) Feb 10 11:05:09 srv-bill kernel: [ 550.125761] ata2.00: configured for UDMA/133 Feb 10 11:05:09 srv-bill kernel: [ 550.125774] ata2: EH complete Feb 10 11:05:09 srv-bill kernel: [ 550.132849] ata2: limiting SATA link speed to 1.5 Gbps Feb 10 11:05:09 srv-bill kernel: [ 550.132853] ata2.00: exception Emask 0x10 SAct 0xe0000 SErr 0x400100 action 0x6 frozen Feb 10 11:05:09 srv-bill kernel: [ 550.133572] ata2.00: irq_stat 0x08000000, interface fatal error Feb 10 11:05:09 srv-bill kernel: [ 550.134256] ata2: SError: { UnrecovData Handshk } Feb 10 11:05:09 srv-bill kernel: [ 550.134919] ata2.00: failed command: WRITE FPDMA QUEUED Feb 10 11:05:09 srv-bill kernel: [ 550.135585] ata2.00: cmd 61/80:88:80:e2:52/05:00:00:00:00/40 tag 17 ncq 720896 out Feb 10 11:05:09 srv-bill kernel: [ 550.135585] res 40/00:98:00:d8:52/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Feb 10 11:05:09 srv-bill kernel: [ 550.136969] ata2.00: status: { DRDY } Feb 10 11:05:09 srv-bill kernel: [ 550.137743] ata2.00: failed command: WRITE FPDMA QUEUED Feb 10 11:05:09 srv-bill kernel: [ 550.138420] ata2.00: cmd 61/40:90:40:dd:52/05:00:00:00:00/40 tag 18 ncq 688128 out Feb 10 11:05:09 srv-bill kernel: [ 550.138420] res 40/00:98:00:d8:52/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Feb 10 11:05:09 srv-bill kernel: [ 550.139801] ata2.00: status: { DRDY } Feb 10 11:05:09 srv-bill kernel: [ 550.140470] ata2.00: failed command: WRITE FPDMA QUEUED Feb 10 11:05:09 srv-bill kernel: [ 550.141157] ata2.00: cmd 61/40:98:00:d8:52/05:00:00:00:00/40 tag 19 ncq 688128 out Feb 10 11:05:09 srv-bill kernel: [ 550.141157] res 40/00:98:00:d8:52/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Feb 10 11:05:09 srv-bill kernel: [ 550.142566] ata2.00: status: { DRDY } Feb 10 11:05:09 srv-bill kernel: [ 550.143236] ata2: hard resetting link Feb 10 11:05:11 srv-bill kernel: [ 552.355021] ata2: SATA link down (SStatus 1 SControl 310) Feb 10 11:05:11 srv-bill kernel: [ 552.373873] ata2: hard resetting link Feb 10 11:05:13 srv-bill kernel: [ 554.585189] ata2: SATA link down (SStatus 1 SControl 310) Feb 10 11:05:13 srv-bill kernel: [ 554.592077] ata2: hard resetting link Feb 10 11:05:16 srv-bill kernel: [ 556.803367] ata2: SATA link down (SStatus 1 SControl 310) Feb 10 11:05:16 srv-bill kernel: [ 556.803374] ata2.00: disabled Feb 10 11:05:16 srv-bill kernel: [ 556.811354] ata2: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen t4 Feb 10 11:05:16 srv-bill kernel: [ 556.812812] ata2: irq_stat 0x00000040, connection status changed Feb 10 11:05:16 srv-bill kernel: [ 556.813762] ata2: SError: { CommWake DevExch } Feb 10 11:05:16 srv-bill kernel: [ 556.814813] ata2: hard resetting link Feb 10 11:05:16 srv-bill kernel: [ 557.534767] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Feb 10 11:05:16 srv-bill kernel: [ 557.545661] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140926/psargs-359) Feb 10 11:05:16 srv-bill kernel: [ 557.545665] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff88011e8442c0), AE_NOT_FOUND (20140926/psparse-536) Feb 10 11:05:16 srv-bill kernel: [ 557.549309] ata2.00: ATA-9: INTEL SSDSC2BW120A4, DC32, max UDMA/133 Feb 10 11:05:16 srv-bill kernel: [ 557.549311] ata2.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 31/32), AA Feb 10 11:05:16 srv-bill kernel: [ 557.565604] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140926/psargs-359) Feb 10 11:05:16 srv-bill kernel: [ 557.565608] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff88011e8442c0), AE_NOT_FOUND (20140926/psparse-536) Feb 10 11:05:16 srv-bill kernel: [ 557.575636] ata2.00: configured for UDMA/133 Feb 10 11:05:16 srv-bill kernel: [ 557.575649] sd 1:0:0:0: [sda] Feb 10 11:05:16 srv-bill kernel: [ 557.575651] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Feb 10 11:05:16 srv-bill kernel: [ 557.575652] sd 1:0:0:0: [sda] Feb 10 11:05:16 srv-bill kernel: [ 557.575653] Sense Key : Aborted Command [current] [descriptor] Feb 10 11:05:16 srv-bill kernel: [ 557.575655] Descriptor sense data with sense descriptors (in hex): Feb 10 11:05:16 srv-bill kernel: [ 557.575656] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 Feb 10 11:05:16 srv-bill kernel: [ 557.575662] 00 52 d8 00 Feb 10 11:05:16 srv-bill kernel: [ 557.575664] sd 1:0:0:0: [sda] Feb 10 11:05:16 srv-bill kernel: [ 557.575666] Add. Sense: No additional sense information Feb 10 11:05:16 srv-bill kernel: [ 557.575667] sd 1:0:0:0: [sda] CDB: Feb 10 11:05:16 srv-bill kernel: [ 557.575669] Write(10): 2a 00 00 52 e2 80 00 05 80 00 Feb 10 11:05:16 srv-bill kernel: [ 557.575674] blk_update_request: I/O error, dev sda, sector 5431936 Feb 10 11:05:16 srv-bill kernel: [ 557.576678] EXT4-fs warning (device dm-0): ext4_end_bio:317: I/O error -5 writing to inode 6424068 (offset 0 size 0 starting block 191056) Feb 10 11:05:16 srv-bill kernel: [ 557.576681] Buffer I/O error on device dm-0, logical block 191056 Feb 10 11:05:16 srv-bill kernel: [ 557.577988] Buffer I/O error on device dm-0, logical block 191057 Feb 10 11:05:16 srv-bill kernel: [ 557.579142] Buffer I/O error on device dm-0, logical block 191058 Feb 10 11:05:16 srv-bill kernel: [ 557.580015] Buffer I/O error on device dm-0, logical block 191059 Feb 10 11:05:16 srv-bill kernel: [ 557.580667] Buffer I/O error on device dm-0, logical block 191060 Feb 10 11:05:16 srv-bill kernel: [ 557.581303] Buffer I/O error on device dm-0, logical block 191061 Feb 10 11:05:16 srv-bill kernel: [ 557.581943] Buffer I/O error on device dm-0, logical block 191062 Feb 10 11:05:16 srv-bill kernel: [ 557.582604] Buffer I/O error on device dm-0, logical block 191063 Feb 10 11:05:16 srv-bill kernel: [ 557.583277] Buffer I/O error on device dm-0, logical block 191064 Feb 10 11:05:16 srv-bill kernel: [ 557.583928] Buffer I/O error on device dm-0, logical block 191065 Feb 10 11:05:16 srv-bill kernel: [ 557.584562] EXT4-fs warning (device dm-0): ext4_end_bio:317: I/O error -5 writing to inode 6424068 (offset 0 size 0 starting block 191224) Feb 10 11:05:16 srv-bill kernel: [ 557.584572] sd 1:0:0:0: rejecting I/O to offline device Feb 10 11:05:16 srv-bill kernel: [ 557.585164] sd 1:0:0:0: [sda] killing request Feb 10 11:05:16 srv-bill kernel: [ 557.585173] sd 1:0:0:0: [sda] Feb 10 11:05:16 srv-bill kernel: [ 557.585174] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Feb 10 11:05:16 srv-bill kernel: [ 557.585175] sd 1:0:0:0: [sda] Feb 10 11:05:16 srv-bill kernel: [ 557.585175] Sense Key : Aborted Command [current] [descriptor] Feb 10 11:05:16 srv-bill kernel: [ 557.585176] Descriptor sense data with sense descriptors (in hex): Feb 10 11:05:16 srv-bill kernel: [ 557.585177] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 Feb 10 11:05:16 srv-bill kernel: [ 557.585181] 00 52 d8 00 Feb 10 11:05:16 srv-bill kernel: [ 557.585182] sd 1:0:0:0: [sda] Feb 10 11:05:16 srv-bill kernel: [ 557.585183] Add. Sense: No additional sense information Feb 10 11:05:16 srv-bill kernel: [ 557.585184] sd 1:0:0:0: [sda] CDB: Feb 10 11:05:16 srv-bill kernel: [ 557.585185] Write(10): 2a 00 00 52 dd 40 00 05 40 00 Feb 10 11:05:16 srv-bill kernel: [ 557.585188] blk_update_request: I/O error, dev sda, sector 5430592 Feb 10 11:05:16 srv-bill kernel: [ 557.585775] EXT4-fs warning (device dm-0): ext4_end_bio:317: I/O error -5 writing to inode 6424068 (offset 0 size 0 starting block 190888) Feb 10 11:05:16 srv-bill kernel: [ 557.585818] sd 1:0:0:0: [sda] Feb 10 11:05:16 srv-bill kernel: [ 557.585819] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Feb 10 11:05:16 srv-bill kernel: [ 557.585820] sd 1:0:0:0: [sda] Feb 10 11:05:16 srv-bill kernel: [ 557.585820] Sense Key : Aborted Command [current] [descriptor] Feb 10 11:05:16 srv-bill kernel: [ 557.585821] Descriptor sense data with sense descriptors (in hex): Feb 10 11:05:16 srv-bill kernel: [ 557.585822] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 Feb 10 11:05:16 srv-bill kernel: [ 557.585825] 00 52 d8 00 Feb 10 11:05:16 srv-bill kernel: [ 557.585827] sd 1:0:0:0: [sda] Feb 10 11:05:16 srv-bill kernel: [ 557.585828] Add. Sense: No additional sense information Feb 10 11:05:16 srv-bill kernel: [ 557.585828] sd 1:0:0:0: [sda] CDB: Feb 10 11:05:16 srv-bill kernel: [ 557.585829] Write(10): 2a 00 00 52 d8 00 00 05 40 00 Feb 10 11:05:16 srv-bill kernel: [ 557.585832] blk_update_request: I/O error, dev sda, sector 5429248 Feb 10 11:05:16 srv-bill kernel: [ 557.586414] EXT4-fs warning (device dm-0): ext4_end_bio:317: I/O error -5 writing to inode 6424068 (offset 0 size 0 starting block 190720) Feb 10 11:05:16 srv-bill kernel: [ 557.586496] ata2: EH complete Feb 10 11:05:16 srv-bill kernel: [ 557.586509] sd 1:0:0:0: [sda] Feb 10 11:05:16 srv-bill kernel: [ 557.586510] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK Feb 10 11:05:16 srv-bill kernel: [ 557.586512] sd 1:0:0:0: [sda] CDB: Feb 10 11:05:16 srv-bill kernel: [ 557.586513] Write(10): 2a 00 07 02 e2 98 00 00 b0 00 Feb 10 11:05:16 srv-bill kernel: [ 557.586517] blk_update_request: I/O error, dev sda, sector 117629592 Feb 10 11:05:16 srv-bill kernel: [ 557.587123] sd 1:0:0:0: rejecting I/O to offline device
×
×
  • Створити нове...