LINUX.ORG.RU

Сообщения INDIGO

 

Глючит диск SSD. Упала скорость на запись.

Форум — Linux-hardware

Здравствуйте.

САБЖ

Кабель менял, всё перетыкал. Комп работает, примерно, 2 года.

Что может быть? Смарт диска:

root@fserver:/storage1# smartctl -a /dev/sdb
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-28-amd64] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     Netac SSD 1TB
Serial Number:    AA202303201T23001796
Firmware Version: W0222A0
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
TRIM Command:     Available
Device is:        Not in smartctl database 7.3/5625
ATA Version is:   ACS-2 T13/2015-D revision 3
SATA Version is:  SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Wed Jan  8 14:14:39 2025 MSK
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

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

General SMART Values:
Offline data collection status:  (0x02) Offline data collection activity
                                        was completed without error.
                                        Auto Offline Data Collection: Disabled.
Self-test execution status:      (  41) The self-test routine was interrupted
                                        by the host with a hard or soft reset.
Total time to complete Offline
data collection:                (  120) seconds.
Offline data collection
capabilities:                    (0x11) SMART execute Offline immediate.
                                        No Auto Offline data collection support.
                                        Suspend Offline collection upon new
                                        command.
                                        No Offline surface scan supported.
                                        Self-test supported.
                                        No Conveyance Self-test supported.
                                        No Selective Self-test supported.
SMART capabilities:            (0x0002) Does not save SMART data before
                                        entering power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine
recommended polling time:        (   2) minutes.
Extended self-test routine
recommended polling time:        (  10) minutes.
SCT capabilities:              (0x0001) SCT Status supported.

SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x0032   100   100   050    Old_age   Always       -       0
  5 Reallocated_Sector_Ct   0x0032   100   100   050    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   100   100   050    Old_age   Always       -       13465
 12 Power_Cycle_Count       0x0032   100   100   050    Old_age   Always       -       184
160 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       0
161 Unknown_Attribute       0x0033   100   100   050    Pre-fail  Always       -       100
163 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       6
164 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       221122
165 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       453
166 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       157
167 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       443
168 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       5050
169 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       92
175 Program_Fail_Count_Chip 0x0032   100   100   050    Old_age   Always       -       0
176 Erase_Fail_Count_Chip   0x0032   100   100   050    Old_age   Always       -       0
177 Wear_Leveling_Count     0x0032   100   100   050    Old_age   Always       -       0
178 Used_Rsvd_Blk_Cnt_Chip  0x0032   100   100   050    Old_age   Always       -       0
181 Program_Fail_Cnt_Total  0x0032   100   100   050    Old_age   Always       -       0
182 Erase_Fail_Count_Total  0x0032   100   100   050    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   050    Old_age   Always       -       135
194 Temperature_Celsius     0x0022   100   100   050    Old_age   Always       -       37
195 Hardware_ECC_Recovered  0x0032   100   100   050    Old_age   Always       -       313709
196 Reallocated_Event_Count 0x0032   100   100   050    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   100   100   050    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0032   100   100   050    Old_age   Always       -       0
199 UDMA_CRC_Error_Count    0x0032   100   100   050    Old_age   Always       -       0
232 Available_Reservd_Space 0x0032   100   100   050    Old_age   Always       -       100
241 Total_LBAs_Written      0x0030   100   100   050    Old_age   Offline      -       5027391
242 Total_LBAs_Read         0x0030   100   100   050    Old_age   Offline      -       611123
245 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       6359106

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Interrupted (host reset)      90%     13450         -
# 2  Extended offline    Completed without error       00%     13343         -
# 3  Extended offline    Completed without error       00%     12437         -

Selective Self-tests/Logging not supported

Тест скорости. Скорость упала.

root@fserver:/storage3# ./disk_speed.sh
+++++++++++Write to Disk
990904320 bytes (991 MB, 945 MiB) copied, 14 s, 70.8 MB/s
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 14.2501 s, 75.4 MB/s
-----------Read from Disk
809500672 bytes (810 MB, 772 MiB) copied, 2 s, 404 MB/s
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 2.64063 s, 407 MB/s

Через рандомное время прогоняю тест, скорость норм.

root@fserver:/storage3# ./disk_speed.sh
+++++++++++Write to Disk
752877568 bytes (753 MB, 718 MiB) copied, 2 s, 376 MB/s
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 2.88054 s, 373 MB/s
-----------Read from Disk
1059061760 bytes (1.1 GB, 1010 MiB) copied, 2 s, 529 MB/s
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 2.02863 s, 529 MB/s
root@fserver:/storage3#

Как проверяю скорость.

#!/bin/bash

tmpfile=/storage3/disk-test-tempfile
BYTES=1M
COUNT=1024
echo 3 > /proc/sys/vm/drop_caches

measure_write_speed() {
    echo "Write to Disk"
    sync
    dd if=/dev/zero of=$tmpfile bs=$BYTES count=$COUNT oflag=direct status=progress
    sync
}

measure_read_speed() {
    echo 3 > /proc/sys/vm/drop_caches
    echo "Read from Disk"
    dd if=$tmpfile of=/dev/null bs=$BYTES count=$COUNT iflag=direct status=progress
}

measure_write_speed
measure_read_speed

rm -f $tmpfile

 

INDIGO
()

Kernel panic - not syncing: Fatal machine check

Форум — Linux-hardware

Здравствуйте.

Есть такой древний комп:

Ubuntu 20.04.6 LTS

Asus B85M-G rev 1,01 + Intel Core i5 4460

Работает 24/7

Выдал такое:


[ 31.173204] mce: [Hardware Error]: CPU 3: Machine Check Exception: 5 Bank 0: b200000000030005 
[ 31.173237) mce: [Hardware Error]: RIP !INEXACT! 33:<0000563de1ff01af>
[ 31.173254] mce: [Hardware Error]: TSC 23c756ad0c
[ 31.173268] mce: [Hardware Error]: PROCESSOR 0:306c3 TIME 1735891728 SOCKET O APIC 6 microcode 28
[ 31.173293] mce: [Hardware Error]: Run the above through 'mcelog --ascii'
[ 31.173310] mce: [Hardware Error]: Machine check: Processor context corrupt
[ 31.173327] Kernel panic - not syncing: Fatal machine check
[ 31.173348] Kernel Offset: 0x7c00000 from Oxffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff) 
[ 31.173374] Rebooting in 30 seconds..

Переткнул, перепроверил всё, кроме материнки и проца.

Решил проблему так:

В BIOS ограничил использование ядер CPU до 2. Проц работает на 2 ядрах.

Вопрос: процу хана?

Просто интересно, почему если используются все ядра проца, получаем ошибку, а если ограничить 3-я ядрами, то работает?

 

INDIGO
()

6 сетевых на сервере - kernel_bind() failed: -98

Форум — Admin

Здравствуйте.

Задача.
Настроить на сервере Debian12 + targetcli
Настроить на клиентах (Windows 10) MC/S (multiple connections per session)

Структура сети.

В сети установлены 3 коммутатора:
SW1: HP 1820-48G Switch J9981A
SW2: HP 1820-48G Switch J9981A
SW3: HPE OfficeConnect Switch - 1820 24G - J9980A

Коммутаторы соеденены между собой с помощью Trank. По 2 провода. Т.е. между свичами скорость 2Gb

IP адреса сети: 192.168.0.0/24
К каждому коммутатору подключены клиенты - Windows 10

На сервере Debian 12 и настроены 6 сетевых карт. Все сетевые карты подключены к комутаторам, по 2 провода на коммутатор.

Настройка сети:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto enp4s0
iface enp4s0 inet static
	address 192.168.0.21/24
	gateway 192.168.0.1
	dns-nameservers 192.168.0.1
	mtu 9000

auto enp5s0
iface enp5s0 inet static
	address 192.168.0.215/24
	mtu 9000

auto enp1s0f0
iface enp1s0f0 inet static
	address 192.168.0.216/24
	mtu 9000

auto enp1s0f1
iface enp1s0f1 inet static
	address 192.168.0.217/24
	mtu 9000

auto enp1s0f2
iface enp1s0f2 inet static
	address 192.168.0.218/24
	mtu 9000

auto enp1s0f3
iface enp1s0f3 inet static
	address 192.168.0.219/24
	mtu 9000

Настройки targetcli. Весь листинг не буду сюда кидать, 109 клиеннтов

o- / ......................................................................................................................... [...]
  o- backstores .............................................................................................................. [...]
  | o- block ................................................................................................ [Storage Objects: 109]
  | | o- client1 ........................................................ [/dev/mapper/lun0.img.cow.1 (2.7TiB) write-thru activated]
  | | | o- alua ................................................................................................... [ALUA Groups: 1]
  | | |   o- default_tg_pt_gp ....................................................................... [ALUA state: Active/optimized]
  | | o- client2 ........................................................ [/dev/mapper/lun0.img.cow.2 (2.7TiB) write-thru activated]
  | | | o- alua ................................................................................................... [ALUA Groups: 1]
  | | |   o- default_tg_pt_gp ....................................................................... [ALUA state: Active/optimized]
  | | o- client3 ........................................................ [/dev/mapper/lun0.img.cow.3 (2.7TiB) write-thru activated]
  | | | o- alua ................................................................................................... [ALUA Groups: 1]
  | | |   o- default_tg_pt_gp ....................................................................... [ALUA state: Active/optimized]
  | | o- client109 .................................................... [/dev/mapper/lun0.img.cow.109 (2.7TiB) write-thru activated]
  | |   o- alua ................................................................................................... [ALUA Groups: 1]
  | |     o- default_tg_pt_gp ....................................................................... [ALUA state: Active/optimized]
  | o- fileio ................................................................................................. [Storage Objects: 1]
  | | o- storage1 ............................................................... [/storage1/lun0.img (2.7TiB) write-back activated]
  | |   o- alua ................................................................................................... [ALUA Groups: 1]
  | |     o- default_tg_pt_gp ....................................................................... [ALUA state: Active/optimized]
  | o- pscsi .................................................................................................. [Storage Objects: 0]
  | o- ramdisk ................................................................................................ [Storage Objects: 0]
  o- iscsi .......................................................................................................... [Targets: 110]
  | o- iqn.2019-02.pro.office:1 ........................................................................................... [TPGs: 1]
  | | o- tpg1 ............................................................................................... [no-gen-acls, no-auth]
  | |   o- acls .......................................................................................................... [ACLs: 1]
  | |   | o- iqn.1991-05.com.microsoft:fob01 ...................................................................... [Mapped LUNs: 1]
  | |   |   o- mapped_lun0 ............................................................................... [lun0 block/client1 (rw)]
  | |   o- luns .......................................................................................................... [LUNs: 1]
  | |   | o- lun0 .................................................. [block/client1 (/dev/mapper/lun0.img.cow.1) (default_tg_pt_gp)]
  | |   o- portals .................................................................................................... [Portals: 6]
  | |     o- 192.168.0.215:3260 ............................................................................................... [OK]
  | |     o- 192.168.0.216:3260 ............................................................................................... [OK]
  | |     o- 192.168.0.217:3260 ............................................................................................... [OK]
  | |     o- 192.168.0.218:3260 ............................................................................................... [OK]
  | |     o- 192.168.0.219:3260 ............................................................................................... [OK]
  | |     o- 192.168.0.21:3260 ................................................................................................ [OK]
  | o- iqn.2019-02.pro.office:2 ........................................................................................... [TPGs: 1]
  | | o- tpg1 ............................................................................................... [no-gen-acls, no-auth]
  | |   o- acls .......................................................................................................... [ACLs: 1]
  | |   | o- iqn.1991-05.com.microsoft:fob02 ...................................................................... [Mapped LUNs: 1]
  | |   |   o- mapped_lun0 ............................................................................... [lun0 block/client2 (rw)]
  | |   o- luns .......................................................................................................... [LUNs: 1]
  | |   | o- lun0 .................................................. [block/client2 (/dev/mapper/lun0.img.cow.2) (default_tg_pt_gp)]
  | |   o- portals .................................................................................................... [Portals: 6]
  | |     o- 192.168.0.215:3260 ............................................................................................... [OK]
  | |     o- 192.168.0.216:3260 ............................................................................................... [OK]
  | |     o- 192.168.0.217:3260 ............................................................................................... [OK]
  | |     o- 192.168.0.218:3260 ............................................................................................... [OK]
  | |     o- 192.168.0.219:3260 ............................................................................................... [OK]
  | |     o- 192.168.0.21:3260 ................................................................................................ [OK]
  | o- iqn.2019-02.pro.office:109 ......................................................................................... [TPGs: 1]
  | | o- tpg1 ............................................................................................... [no-gen-acls, no-auth]
  | |   o- acls .......................................................................................................... [ACLs: 1]
  | |   | o- iqn.1991-05.com.microsoft:fob109 ..................................................................... [Mapped LUNs: 1]
  | |   |   o- mapped_lun0 ............................................................................. [lun0 block/client109 (rw)]
  | |   o- luns .......................................................................................................... [LUNs: 1]
  | |   | o- lun0 .............................................. [block/client109 (/dev/mapper/lun0.img.cow.109) (default_tg_pt_gp)]
  | |   o- portals .................................................................................................... [Portals: 6]
  | |     o- 192.168.0.215:3260 ............................................................................................... [OK]
  | |     o- 192.168.0.216:3260 ............................................................................................... [OK]
  | |     o- 192.168.0.217:3260 ............................................................................................... [OK]
  | |     o- 192.168.0.218:3260 ............................................................................................... [OK]
  | |     o- 192.168.0.219:3260 ............................................................................................... [OK]
  | |     o- 192.168.0.21:3260 ................................................................................................ [OK]
  | o- iqn.2019-02.pro.office:gserver ..................................................................................... [TPGs: 1]
  |   o- tpg1 ............................................................................................... [no-gen-acls, no-auth]
  |     o- acls .......................................................................................................... [ACLs: 1]
  |     | o- iqn.1991-05.com.microsoft:gserver .................................................................... [Mapped LUNs: 1]
  |     |   o- mapped_lun0 ............................................................................. [lun0 fileio/storage1 (rw)]
  |     o- luns .......................................................................................................... [LUNs: 1]
  |     | o- lun0 ........................................................ [fileio/storage1 (/storage1/lun0.img) (default_tg_pt_gp)]
  |     o- portals .................................................................................................... [Portals: 6]
  |       o- 192.168.0.215:3260 ............................................................................................... [OK]
  |       o- 192.168.0.216:3260 ............................................................................................... [OK]
  |       o- 192.168.0.217:3260 ............................................................................................... [OK]
  |       o- 192.168.0.218:3260 ............................................................................................... [OK]
  |       o- 192.168.0.219:3260 ............................................................................................... [OK]
  |       o- 192.168.0.21:3260 ................................................................................................ [OK]
  o- loopback ......................................................................................................... [Targets: 0]
  o- vhost ............................................................................................................ [Targets: 0]
  o- xen-pvscsi ....................................................................................................... [Targets: 0]

Проблемма вот в чём. Когда добавляю порталы, то получаю ошибки.

targetcli /iscsi/iqn.2019-02.pro.office:$LOOP_NUMBER/tpg1/portals delete 0.0.0.0 3260
targetcli /iscsi/iqn.2019-02.pro.office:$LOOP_NUMBER/tpg1/portals create 192.168.0.21
targetcli /iscsi/iqn.2019-02.pro.office:$LOOP_NUMBER/tpg1/portals create 192.168.0.215
targetcli /iscsi/iqn.2019-02.pro.office:$LOOP_NUMBER/tpg1/portals create 192.168.0.216
targetcli /iscsi/iqn.2019-02.pro.office:$LOOP_NUMBER/tpg1/portals create 192.168.0.217
targetcli /iscsi/iqn.2019-02.pro.office:$LOOP_NUMBER/tpg1/portals create 192.168.0.218
targetcli /iscsi/iqn.2019-02.pro.office:$LOOP_NUMBER/tpg1/portals create 192.168.0.219

Ошибки:

fserver kernel: [ 2010.680452] kernel_bind() failed: -98

На клиентах, вроде бы, всё работает, но эти ошибки напрягают. До этого сервер работал с 1 IP адресом, через бондинг, но там свои проблемы были. Было так: portals 0.0.0.0 3260

Что делать с этой ошибкой?

 

INDIGO
()

Не работает бондинг, если к 3 свичам подключить 6 лан-проводов

Форум — Admin

Здравствуйте.

В сети 3 свича:
SW1 HP 1820-48G Switch J9981A
SW2 HP 1820-48G Switch J9981A
SW2 HPE OfficeConnect Switch 1820 24G J9980A

Между собой соединены так:
SW1 Trunk(Port 50, 51) -> SW2 Trunk(Port 50, 51)
SW2 Trunk(Port 46, 48) -> SW3 Trunk(Port 24, 25)

На каждом свиче порты 1 и 2 объединены в Trunk. В эти порты подключаю провода от сервера.

На сервере Debian 12 установлено 6 сетевых карт:
Встроеная в материнку: 2.5Gb какая-то
Intel <EXPI9301CT> Сетевая карта 1 Гбит/с (1 x 1 Гбит/с, PCI Express)
Intel <Ethernet Server Adapter I350-T4 (I350T4BLK)> Сетевая карта 1 Гбит/с (4 x 1 Гбит/с, PCI Express)

Сеть перестаёт работать (сервак не виден в сети), если в один свич подключено 2 провода от сервера.

Как это выглядит, все подключения в 1 порт:
В SW1 подключая 1 провод от сервера.
В SW2 подключая 1 провод от сервера.
В SW3 подключая 1 провод от сервера.
Всё работает.

Если подключаю в любой свич (во 2-й порт) ещё один провод от сервера, то сервер больше не в сети.

root@fserver:/etc/network# cat interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
#       bond-slaves enp6s0 enp1s0f0 enp1s0f1

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# Frontend bond interface
auto bond0
iface bond0 inet static
        address 192.168.0.3/24
        gateway 192.168.0.1
        bond-slaves enp4s0 enp5s0 enp1s0f0 enp1s0f1 enp1s0f2 enp1s0f3
        bond-mode 6
        bond-miimon 50
        bond-downdelay 200
        bond-updelay 500
        dns-nameservers 192.168.0.1
        mtu 9000
root@fserver:/etc/network# ifconfig
bond0: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST>  mtu 9000
        inet 192.168.0.3  netmask 255.255.255.0  broadcast 192.168.0.255
        ether 04:7c:16:b7:d4:f1  txqueuelen 1000  (Ethernet)
        RX packets 12117215  bytes 26896418862 (25.0 GiB)
        RX errors 0  dropped 406  overruns 0  frame 0
        TX packets 14402119  bytes 90865712754 (84.6 GiB)
        TX errors 0  dropped 2 overruns 0  carrier 0  collisions 0

enp1s0f0: flags=6147<UP,BROADCAST,SLAVE,MULTICAST>  mtu 9000
        ether 00:e0:ed:43:47:18  txqueuelen 1000  (Ethernet)
        RX packets 543  bytes 262560 (256.4 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 132  bytes 21722 (21.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device memory 0x80900000-8091ffff

enp1s0f1: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST>  mtu 9000
        ether 00:e0:ed:43:47:1b  txqueuelen 1000  (Ethernet)
        RX packets 1921728  bytes 2020118627 (1.8 GiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 8386752  bytes 54815544928 (51.0 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device memory 0x80920000-8093ffff

enp1s0f2: flags=6147<UP,BROADCAST,SLAVE,MULTICAST>  mtu 9000
        ether 00:e0:ed:43:47:1a  txqueuelen 1000  (Ethernet)
        RX packets 4979457  bytes 2812109424 (2.6 GiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1815851  bytes 11126428569 (10.3 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device memory 0x80940000-8095ffff

enp1s0f3: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST>  mtu 9000
        ether 04:7c:16:b7:d4:f1  txqueuelen 1000  (Ethernet)
        RX packets 3087320  bytes 12120738963 (11.2 GiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1728184  bytes 10004123808 (9.3 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device memory 0x80960000-8097ffff

enp4s0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST>  mtu 9000
        ether 00:e0:ed:43:47:19  txqueuelen 1000  (Ethernet)
        RX packets 2127514  bytes 12605476263 (11.7 GiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2464813  bytes 14865868728 (13.8 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device memory 0x82000000-820fffff

enp5s0: flags=6147<UP,BROADCAST,SLAVE,MULTICAST>  mtu 9000
        ether 68:05:ca:aa:9b:7b  txqueuelen 1000  (Ethernet)
        RX packets 653  bytes 47331 (46.2 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 6387  bytes 53724999 (51.2 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 17  memory 0x823c0000-823e0000

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 16630  bytes 4049322 (3.8 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 16630  bytes 4049322 (3.8 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

root@fserver:/etc/network#

 

INDIGO
()

При использовании бондинга ошибка в логах, хотя всё работает.

Форум — Admin

Здравствуйте. После какого-то обновление при старте компа получаю такие ошибки, хотя, всё работает.

Что это? Как лечить? Или работает - не трогать?


Linux fserver 6.1.0-20-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.85-1 (2024-04-11) x86_64

root@fserver:~# dmesg -l err
[    9.168555] bond0: (slave enp1s0f0): invalid new link 3 on slave
[    9.168596] bond0: (slave enp6s0): invalid new link 3 on slave
[    9.376654] bond0: (slave enp1s0f1): invalid new link 3 on slave
[   10.000549] bond0: (slave enp1s0f2): invalid new link 3 on slave
[   10.208663] bond0: (slave enp1s0f3): invalid new link 3 on slave

root@fserver:~# ethtool bond0
Settings for bond0:
        Supported ports: [  ]
        Supported link modes:   Not reported
        Supported pause frame use: No
        Supports auto-negotiation: No
        Supported FEC modes: Not reported
        Advertised link modes:  Not reported
        Advertised pause frame use: No
        Advertised auto-negotiation: No
        Advertised FEC modes: Not reported
        Speed: 6000Mb/s
        Duplex: Full
        Auto-negotiation: off
        Port: Other
        PHYAD: 0
        Transceiver: internal
        Link detected: yes

root@fserver:~# cat /etc/network/interfaces
auto enp6s0
iface enp6s0 inet manual
    bond-master bond0
    bond-mode balance-alb

auto enp7s0
iface enp7s0 inet manual
    bond-master bond0
    bond-mode balance-alb

auto enp1s0f0
iface enp1s0f0 inet manual
    bond-master bond0
    bond-mode balance-alb

auto enp1s0f1
iface enp1s0f1 inet manual
    bond-master bond0
    bond-mode balance-alb

auto enp1s0f2
iface enp1s0f2 inet manual
    bond-master bond0
    bond-mode balance-alb

auto enp1s0f3
iface enp1s0f3 inet manual
    bond-master bond0
    bond-mode balance-alb

auto bond0
iface bond0 inet static
    address 192.168.0.22
    netmask 255.255.255.0
    network 192.168.0.0
    gateway 192.168.0.1
    dns-nameservers 192.168.0.1
    bond-slaves enp6s0 enp7s0 enp1s0f0 enp1s0f1 enp1s0f2 enp1s0f3
    bond-mode balance-alb
    bond-miimon 100
    bond-downdelay 200
    bond-updelay 200
    mtu 9000

 

INDIGO
()

Накрывается диск? critical medium error, dev nvme1n1

Форум — Linux-hardware

Здравствуйте.

В серваке, в RAID0 установлен такой диск. Файлопомока. В один момент начались тормоза. Смотрю логи в логах ошибки. Ребутнул комп. Ошибок нет. Что это было? Диск накрывается?

root@fserver:~# nvme smart-log -H /dev/nvme1n1
Smart Log for NVME device:nvme1n1 namespace-id:ffffffff
critical_warning                        : 0
      Available Spare[0]             : 0
      Temp. Threshold[1]             : 0
      NVM subsystem Reliability[2]   : 0
      Read-only[3]                   : 0
      Volatile mem. backup failed[4] : 0
      Persistent Mem. RO[5]          : 0
temperature                             : 41°C (314 Kelvin)
available_spare                         : 100%
available_spare_threshold               : 1%
percentage_used                         : 1%
endurance group critical warning summary: 0
Data Units Read                         : 396,890,330 (203.21 TB)
Data Units Written                      : 9,853,779 (5.05 TB)
host_read_commands                      : 2,139,154,332
host_write_commands                     : 17,575,839
controller_busy_time                    : 5,678
power_cycles                            : 107
power_on_hours                          : 7,230
unsafe_shutdowns                        : 27
media_errors                            : 208
num_err_log_entries                     : 0
Warning Temperature Time                : 0
Critical Composite Temperature Time     : 0
Temperature Sensor 1           : 41°C (314 Kelvin)
Temperature Sensor 2           : 36°C (309 Kelvin)
Thermal Management T1 Trans Count       : 0
Thermal Management T2 Trans Count       : 0
Thermal Management T1 Total Time        : 0
Thermal Management T2 Total Time        : 0
root@fserver:~# smartctl -a /dev/nvme1n1
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-17-amd64] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       Netac NVMe SSD 1TB
Serial Number:                      AA202303201TB2122149
Firmware Version:                   SN10380
PCI Vendor/Subsystem ID:            0x1f40
IEEE OUI Identifier:                0x000000
Total NVM Capacity:                 1,000,204,886,016 [1.00 TB]
Unallocated NVM Capacity:           0
Controller ID:                      0
NVMe Version:                       1.4
Number of Namespaces:               1
Namespace 1 Size/Capacity:          1,000,204,886,016 [1.00 TB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            000000 1002122149
Local Time is:                      Sun Apr 14 10:25:55 2024 MSK
Firmware Updates (0x1a):            5 Slots, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x001f):     Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat
Log Page Attributes (0x02):         Cmd_Eff_Lg
Maximum Data Transfer Size:         128 Pages
Warning  Comp. Temp. Threshold:     90 Celsius
Critical Comp. Temp. Threshold:     95 Celsius

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     6.50W       -        -    0  0  0  0        0       0
 1 +     5.80W       -        -    1  1  1  1        0       0
 2 +     3.60W       -        -    2  2  2  2        0       0
 3 -   0.0500W       -        -    3  3  3  3     5000   10000
 4 -   0.0025W       -        -    4  4  4  4     8000   45000

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 +     512       0         0

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

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        41 Celsius
Available Spare:                    100%
Available Spare Threshold:          1%
Percentage Used:                    1%
Data Units Read:                    396,890,345 [203 TB]
Data Units Written:                 9,853,779 [5.04 TB]
Host Read Commands:                 2,139,154,388
Host Write Commands:                17,575,843
Controller Busy Time:               5,678
Power Cycles:                       107
Power On Hours:                     7,230
Unsafe Shutdowns:                   27
Media and Data Integrity Errors:    208
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               41 Celsius
Temperature Sensor 2:               36 Celsius

Error Information (NVMe Log 0x01, 16 of 64 entries)
No Errors Logged

root@fserver:~#
2024-04-13T17:11:12.320346+03:00 fserver kernel: [ 2006.314191] bio error: 00000000d40cf897,  err: 10
2024-04-13T17:11:12.372348+03:00 fserver kernel: [ 2006.364467] bio error: 000000002acff031,  err: 10
2024-04-13T17:11:12.420345+03:00 fserver kernel: [ 2006.414736] bio error: 000000000c3ed364,  err: 10
2024-04-13T17:11:12.472348+03:00 fserver kernel: [ 2006.465003] bio error: 0000000029aa643d,  err: 10
2024-04-13T17:11:12.520343+03:00 fserver kernel: [ 2006.515271] bio error: 000000005bb22c65,  err: 10
2024-04-13T17:11:12.576347+03:00 fserver kernel: [ 2006.568341] bio error: 00000000d40cf897,  err: 10
2024-04-13T17:11:12.624346+03:00 fserver kernel: [ 2006.618607] bio error: 0000000012d26e20,  err: 10
2024-04-13T17:11:12.676347+03:00 fserver kernel: [ 2006.668879] bio error: 000000001a4241e1,  err: 10
2024-04-13T17:11:12.724351+03:00 fserver kernel: [ 2006.719151] bio error: 0000000060be55b7,  err: 10
2024-04-13T17:11:12.776367+03:00 fserver kernel: [ 2006.769420] bio error: 0000000091ee7981,  err: 10
2024-04-13T17:11:12.828352+03:00 fserver kernel: [ 2006.821091] bio error: 00000000d40cf897,  err: 10
2024-04-13T17:11:12.876344+03:00 fserver kernel: [ 2006.871359] bio error: 000000000b59f085,  err: 10
2024-04-13T17:11:12.928345+03:00 fserver kernel: [ 2006.921633] bio error: 0000000018df5589,  err: 10
2024-04-13T17:11:12.980347+03:00 fserver kernel: [ 2006.971902] bio error: 000000002fa9a130,  err: 10
2024-04-13T17:11:13.028353+03:00 fserver kernel: [ 2007.022174] bio error: 000000002fa9a130,  err: 10
2024-04-13T17:11:13.080347+03:00 fserver kernel: [ 2007.072446] bio error: 0000000018df5589,  err: 10
2024-04-13T17:11:13.130998+03:00 fserver kernel: [ 2007.125484] nvme_log_error: 89 callbacks suppressed
2024-04-13T17:11:13.131011+03:00 fserver kernel: [ 2007.125490] nvme1n1: I/O Cmd(0x2) @ LBA 940966272, 8 blocks, I/O Error (sct 0x2 / sc 0x81) 
2024-04-13T17:11:13.131016+03:00 fserver kernel: [ 2007.125961] blk_print_req_error: 188 callbacks suppressed
2024-04-13T17:11:13.131018+03:00 fserver kernel: [ 2007.125964] critical medium error, dev nvme1n1, sector 940966272 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
2024-04-13T17:11:13.131027+03:00 fserver kernel: [ 2007.126490] I/O error, dev loop0, sector 3745777024 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 2
2024-04-13T17:11:13.132396+03:00 fserver kernel: [ 2007.127188] bio error: 000000000b59f085,  err: 10
2024-04-13T17:11:13.181436+03:00 fserver kernel: [ 2007.175757] nvme1n1: I/O Cmd(0x2) @ LBA 940966272, 8 blocks, I/O Error (sct 0x2 / sc 0x81) 
2024-04-13T17:11:13.181452+03:00 fserver kernel: [ 2007.176293] critical medium error, dev nvme1n1, sector 940966272 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
2024-04-13T17:11:13.181463+03:00 fserver kernel: [ 2007.176934] I/O error, dev loop0, sector 3745777024 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 2
2024-04-13T17:11:13.184350+03:00 fserver kernel: [ 2007.177547] bio error: 00000000da045632,  err: 10
2024-04-13T17:11:13.232375+03:00 fserver kernel: [ 2007.226026] nvme1n1: I/O Cmd(0x2) @ LBA 940966272, 8 blocks, I/O Error (sct 0x2 / sc 0x81) 
2024-04-13T17:11:13.232392+03:00 fserver kernel: [ 2007.226652] critical medium error, dev nvme1n1, sector 940966272 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
2024-04-13T17:11:13.232396+03:00 fserver kernel: [ 2007.227312] I/O error, dev loop0, sector 3745777024 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 2
2024-04-13T17:11:13.236351+03:00 fserver kernel: [ 2007.228035] bio error: 0000000012d26e20,  err: 10
2024-04-13T17:11:13.282392+03:00 fserver kernel: [ 2007.276297] nvme1n1: I/O Cmd(0x2) @ LBA 940966272, 8 blocks, I/O Error (sct 0x2 / sc 0x81) 
2024-04-13T17:11:13.282409+03:00 fserver kernel: [ 2007.277023] critical medium error, dev nvme1n1, sector 940966272 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
2024-04-13T17:11:13.282417+03:00 fserver kernel: [ 2007.277884] I/O error, dev loop0, sector 3745777024 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 2
2024-04-13T17:11:13.284344+03:00 fserver kernel: [ 2007.278704] bio error: 000000006c0123b3,  err: 10
2024-04-13T17:11:13.332820+03:00 fserver kernel: [ 2007.326568] nvme1n1: I/O Cmd(0x2) @ LBA 940966272, 8 blocks, I/O Error (sct 0x2 / sc 0x81) 
2024-04-13T17:11:13.332834+03:00 fserver kernel: [ 2007.327385] critical medium error, dev nvme1n1, sector 940966272 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
2024-04-13T17:11:13.332844+03:00 fserver kernel: [ 2007.328315] I/O error, dev loop0, sector 3745777024 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 2
2024-04-13T17:11:13.336359+03:00 fserver kernel: [ 2007.329362] bio error: 00000000fb3a2c34,  err: 10
2024-04-13T17:11:13.384351+03:00 fserver kernel: [ 2007.378239] nvme1n1: I/O Cmd(0x2) @ LBA 940966272, 8 blocks, I/O Error (sct 0x2 / sc 0x81) 
2024-04-13T17:11:13.384367+03:00 fserver kernel: [ 2007.379192] bio error: 00000000d40cf897,  err: 10
2024-04-13T17:11:13.436349+03:00 fserver kernel: [ 2007.428509] nvme1n1: I/O Cmd(0x2) @ LBA 940966272, 8 blocks, I/O Error (sct 0x2 / sc 0x81) 
2024-04-13T17:11:13.436364+03:00 fserver kernel: [ 2007.429503] bio error: 0000000018df5589,  err: 10
2024-04-13T17:11:13.484349+03:00 fserver kernel: [ 2007.478781] nvme1n1: I/O Cmd(0x2) @ LBA 940966272, 8 blocks, I/O Error (sct 0x2 / sc 0x81) 
2024-04-13T17:11:13.484373+03:00 fserver kernel: [ 2007.479860] bio error: 00000000475dd87b,  err: 10
2024-04-13T17:11:13.534645+03:00 fserver kernel: [ 2007.529053] nvme1n1: I/O Cmd(0x2) @ LBA 940966272, 8 blocks, I/O Error (sct 0x2 / sc 0x81) 
2024-04-13T17:11:13.536350+03:00 fserver kernel: [ 2007.530159] bio error: 000000002acff031,  err: 10
2024-04-13T17:11:13.584943+03:00 fserver kernel: [ 2007.579323] nvme1n1: I/O Cmd(0x2) @ LBA 940966272, 8 blocks, I/O Error (sct 0x2 / sc 0x81) 

 

INDIGO
()

Как воткнуть сетевуху 2.5Gb в свитч у которого порты только 1GB на полную скорость?

Форум — Linux-hardware

Здравствуйте.

Собран сервак у которого встройка сетевая 2.5Gb.

Скорости не хватает, воткнул сетевую карту 2-головую, каждая по 1GB. Все сетевые в бондинге.

Свичи имеют порты только 1Gb. Т.е. сервак имеет bond0 speed 3Gb

Этого мало…

В общем, САБЖ

Может такой девайс заюзать?

Медиаконвертер Ethernet / TDM, 2*1.25G / 2.5G, 3 SFP-порта

http://n-sistem.net/mediakonverter-ethernet--tdm-2125g--25g-3-sfp-porta/

На свичах есть 4SFP

 

INDIGO
()

Webmin на настроенный сервер.

Форум — Admin

Здравствуйте.

Есть работающий сервер, Ubuntu 20.04: apach, bind, iptables, exim + ещё список всякого.

Если на такой сервак поставлю Webmin, он (Webmin) подхватит все работающие сервисы и сможет ими управлять или Webmin ставит всё в свои каталоги?

 

INDIGO
()

Debian12 - Munin-node stop

Форум — Admin

Здравствуйте.

Munin ставил много раз, всё ок было.

Ставлю на Debian12. Всё как обычно:

apt install munin munin-node

Не работает!

Такие ошибки:

root@fserver:/var/log/munin# cat munin-node.log


2023/06/24-11:12:51 Munin::Node::Server (type Net::Server::Fork) starting! pid(11897)
Resolved [*]:4949 to [::]:4949, IPv6
Not including resolved host [0.0.0.0] IPv4 because it will be handled by [::] IPv6
Binding to TCP port 4949 on host :: with IPv6
2023/06/24-11:12:51 Can't connect to TCP port 4949 on :: [Invalid argument]
  at line 66 in file /usr/share/perl5/Net/Server/Proto/TCP.pm
2023/06/24-11:12:51 Server closing!

shutdown() on unopened socket GEN0 at /usr/lib/x86_64-linux-gnu/perl-base/IO/Socket.pm line 325.


2023/06/24-11:12:51 Munin::Node::Server (type Net::Server::Fork) starting! pid(11902)
Resolved [*]:4949 to [::]:4949, IPv6
Not including resolved host [0.0.0.0] IPv4 because it will be handled by [::] IPv6
Binding to TCP port 4949 on host :: with IPv6
2023/06/24-11:12:51 Can't connect to TCP port 4949 on :: [Invalid argument]
  at line 66 in file /usr/share/perl5/Net/Server/Proto/TCP.pm
2023/06/24-11:12:51 Server closing!
shutdown() on unopened socket GEN0 at /usr/lib/x86_64-linux-gnu/perl-base/IO/Socket.pm line 325.
2023/06/24-11:12:52 Munin::Node::Server (type Net::Server::Fork) starting! pid(11907)
Resolved [*]:4949 to [::]:4949, IPv6
Not including resolved host [0.0.0.0] IPv4 because it will be handled by [::] IPv6
Binding to TCP port 4949 on host :: with IPv6
2023/06/24-11:12:52 Can't connect to TCP port 4949 on :: [Invalid argument]
  at line 66 in file /usr/share/perl5/Net/Server/Proto/TCP.pm
2023/06/24-11:12:52 Server closing!
shutdown() on unopened socket GEN0 at /usr/lib/x86_64-linux-gnu/perl-base/IO/Socket.pm line 325.
2023/06/24-11:12:52 Munin::Node::Server (type Net::Server::Fork) starting! pid(11912)
Resolved [*]:4949 to [::]:4949, IPv6
Not including resolved host [0.0.0.0] IPv4 because it will be handled by [::] IPv6
Binding to TCP port 4949 on host :: with IPv6
2023/06/24-11:12:52 Can't connect to TCP port 4949 on :: [Invalid argument]
  at line 66 in file /usr/share/perl5/Net/Server/Proto/TCP.pm
2023/06/24-11:12:52 Server closing!
shutdown() on unopened socket GEN0 at /usr/lib/x86_64-linux-gnu/perl-base/IO/Socket.pm line 325.
2023/06/24-11:12:52 Munin::Node::Server (type Net::Server::Fork) starting! pid(11916)
Resolved [*]:4949 to [::]:4949, IPv6
Not including resolved host [0.0.0.0] IPv4 because it will be handled by [::] IPv6
Binding to TCP port 4949 on host :: with IPv6
2023/06/24-11:12:52 Can't connect to TCP port 4949 on :: [Invalid argument]
  at line 66 in file /usr/share/perl5/Net/Server/Proto/TCP.pm
2023/06/24-11:12:52 Server closing!
shutdown() on unopened socket GEN0 at /usr/lib/x86_64-linux-gnu/perl-base/IO/Socket.pm line 325.
root@fserver:/var/log/munin#

Куда копать?

 

INDIGO
()

Debian 12 - объединить 2 сетевухи в одну. Конфиг

Форум — Admin

Здравствуйте.

Нужен совет. Проверить сейчас не могу - доступа к серверу нет.

Надо на Debian12 сделать bonding из enp5s0 enp5s1

Какой из конфигов будет работать?

interfaces.bond

 
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# Frontend bond interface
auto bond0
iface bond0 inet static
        address 192.168.201.141/25
        gateway 192.168.201.129
        dns-nameservers 192.168.201.129
        bond-slaves enp5s0 enp5s1
        bond-mode 5
        bond-primary enp5s0
        bond-miimon 100
        bond-downdelay 300
        bond-updelay 700
        mtu 9000
interfaces.bond2
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto enp5s0
iface enp5s0 inet manual
bond-master bond0

auto enp5s1
iface enp5s1 inet manual
bond-master bond0

auto bond0
iface bond0 inet static
        address 192.168.201.141/25
        gateway 192.168.201.129
        dns-nameservers 192.168.201.129
        mtu 9000
        bond-mode 5
        bond-miimon 100
        bond-downdelay 300
        bond-updelay 700
        bond-slaves enp5s0 enp5s1

 

INDIGO
()

Диск заполнен на 99% Чем чревато?

Форум — Linux-hardware

Здравствуйте.

На серваке собран софтовый RAID0 из 3x nwme по 1Тб (/dev/md0) и смонтирован в /storage.

В /storage лежит образ диска lun0.img. Занимает практически весь объем рейда, свободно 5Гб.

lun0.img подключен к targetcli, но это уже детали….

Т.е. все запись/чтение буду происходить ВНУТРИ образа.

Вопрос: такая ситуация, что диск заполнен на 99%, при условии запись/чтение не увеличит занимаемое место, чем чревато?

 

INDIGO
()

Надо поменять настройки сети, не меняя ip у клиентов.

Форум — Admin

Здравствуйте.
Задача в сабже.

Такая сеть:
Инет-шлюз, Ubunta.
2 сетевухи:
enp3s0 - провайдер 175.70.100.4/30
enp2s0 - локалка 175.70.101.128/25 из локалки каждый ПК выходит в инет со своим ip.

Сейчас на стороне провайдера настроено так: все пакеты, предназначенные для сети 175.70.101.128/25 передаются на 175.70.100.4/30
А на шлюзе, через iptables - forwrding идут по назначению.

Появилась необходимость отказаться от сетки 175.70.101.128/25, но менять IP у каждого клиент не вариант, много всего весит на этих IP.

Что планирую сделать.
Сказать провайдеру, чтоб убрал у себя маршрутизацию с маленькой сетки на большую.

У себя добавляю:

iptables -t nat -A POSTROUTING -s 175.70.101.128/25 -j SNAT --to-source 175.70.100.6
или 
iptables -t nat -A POSTROUTING -s 175.70.101.128/25 -j MASQUERADE


Какой результат жду.
Сетка 175.70.101.128/25 выходит в инет с одного ip 175.70.100.6. И всё работает.
Где что не так? Будет работать такой план? Сделать надо быстро, не останавливая работу клиентов на 175.70.101.128/25

 

INDIGO
()

Локальный Git сервер. Не могу залить правки на зеркало.

Форум — General

Здравствуйте.

Поднял в локалке локалный GIT сервер - Gogs

Сделал доступ из инета, https. Все работает.

Когда создаю новый репозиторий, то всё работает. В обе стороны всё заливается и скачивается.

Но когда делаю зеркало с githab`a, и пытаюсь залить какие-либо правки в, то получаю такую ошибку:

$ git push -u origin master
Enumerating objects: 8, done.
Counting objects: 100% (8/8), done.
Delta compression using up to 16 threads
Compressing objects: 100% (5/5), done.
Writing objects: 100% (5/5), 4.66 KiB | 4.66 MiB/s, done.
Total 5 (delta 3), reused 0 (delta 0), pack-reused 0
error: RPC failed; HTTP 403 curl 22 The requested URL returned error: 403
send-pack: unexpected disconnect while reading sideband packet
fatal: the remote end hung up unexpectedly
Everything up-to-date

Внести какие-либо правки в зеркало нелзья что-ли?

 

INDIGO
()

Низкая скорость диска ADATA SX8200PNP

Форум — Linux-hardware

Здравствуйте. Поставил на комп бу диск ADATA SX8200PNP. Смарт фиговый. Но, вроде бы, работает.

Вопрос по скорости диска: это нормальная скорость или всё таки, диску кранты?

Смарт:


root@fserver:~# smartctl -a /dev/nvme0n1
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-192-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       ADATA SX8200PNP
Serial Number:                      2J3620037854
Firmware Version:                   S0118C
PCI Vendor/Subsystem ID:            0x1cc1
IEEE OUI Identifier:                0x000000
Controller ID:                      1
Number of Namespaces:               1
Namespace 1 Size/Capacity:          512,110,190,592 [512 GB]
Namespace 1 Formatted LBA Size:     512
Local Time is:                      Fri Sep  9 12:23:11 2022 MSK
Firmware Updates (0x14):            2 Slots, no Reset required
Optional Admin Commands (0x0016):   Format Frmw_DL *Other*
Optional NVM Commands (0x005f):     Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat *Other*
Maximum Data Transfer Size:         64 Pages
Warning  Comp. Temp. Threshold:     75 Celsius
Critical Comp. Temp. Threshold:     80 Celsius

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     9.00W       -        -    0  0  0  0        0       0
 1 +     4.60W       -        -    1  1  1  1        0       0
 2 +     3.80W       -        -    2  2  2  2        0       0
 3 -   0.0450W       -        -    3  3  3  3     2000    2000
 4 -   0.0040W       -        -    4  4  4  4     6000    8000

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 +     512       0         0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: FAILED!
- NVM subsystem reliability has been degraded

SMART/Health Information (NVMe Log 0x02, NSID 0x1)
Critical Warning:                   0x04
Temperature:                        41 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    101%
Data Units Read:                    59,990,078 [30.7 TB]
Data Units Written:                 744,803,217 [381 TB]
Host Read Commands:                 491,113,033
Host Write Commands:                6,420,138,620
Controller Busy Time:               155,096
Power Cycles:                       116
Power On Hours:                     22,171
Unsafe Shutdowns:                   33
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0

Read Error Information Log failed: NVMe Status 0x02

Тест скорости:

 
root@fserver:~# hdparm -Tt /dev/nvme0n1

/dev/nvme0n1:
 Timing cached reads:   30720 MB in  1.99 seconds = 15450.52 MB/sec
 Timing buffered disk reads:  88 MB in  3.03 seconds =  29.07 MB/sec


root@fserver:~# dd if=/dev/zero of=/nvme/largefile bs=1M count=1024
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 0.288485 s, 3.7 GB/s
root@fserver:~# dd if=/nvme/largefile of=/dev/null bs=4k
262144+0 records in
262144+0 records out
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 5.43145 s, 198 MB/s
root@fserver:~#

 

INDIGO
()

Targetcli. Как разместить кеш на локальном диске клиента?

Форум — Admin

Здравствуйте.

Давно сделал для одной конторы ISCSI систему на основе targetcli. Делал по этому мануалу: http://etherboot.org/wiki/appnotes/cow

Заранее извиняюсь, в терминах могу путаться.

Система такая. Есть основной образ диска с установленными программами, они почти не меняются. Меняются кофиги, временные файлы, всякий мусор не критичный. Клиенты (Win), по ISCSI, подключают этот образ как диск и работают с этими прогами. Каждый раз, при начале рабочего дня, этот образ у клиента сбрасывается до оригинального. Всё работает без ошибок, все хорошо.

Но возникла проблема. Иногда клиентам не хватает места для кеша этого ISCSI диска. Клиенты забивают диск, выделенный для кеша клиентов, и targetcli зависает. Помогает ребут сервера и пересоздание лунов.

Возникла идей: у каждого клиента физически есть како-то диск. Можно ли клиентский кеш перенести на комп клиента?

Конфиг targetcli:


sysadmin@fserver:~$ sudo targetcli ls
o- / ......................................................................................................................... [...]
  o- backstores .............................................................................................................. [...]
  | o- block ................................................................................................ [Storage Objects: 101]
  | | o- client1 ........................................................ [/dev/mapper/lun0.img.cow.1 (2.7TiB) write-thru activated]
  | | o- client100 .................................................... [/dev/mapper/lun0.img.cow.100 (2.7TiB) write-thru activated]
  | | o- client101 .................................................... [/dev/mapper/lun0.img.cow.101 (2.7TiB) write-thru activated]
  | o- fileio ................................................................................................. [Storage Objects: 1]
  | | o- storage1 ............................................................... [/storage1/lun0.img (2.7TiB) write-back activated]
  | o- pscsi .................................................................................................. [Storage Objects: 0]
  | o- ramdisk ................................................................................................ [Storage Objects: 0]
  o- iscsi .......................................................................................................... [Targets: 102]
  | o- iqn.2019-02.pro.office24:1 ........................................................................................... [TPGs: 1]
  | | o- tpg1 ............................................................................................... [no-gen-acls, no-auth]
  | |   o- acls .......................................................................................................... [ACLs: 1]
  | |   | o- iqn.1991-05.com.microsoft:cl01 ...................................................................... [Mapped LUNs: 1]
  | |   |   o- mapped_lun0 ............................................................................... [lun0 block/client1 (rw)]
  | |   o- luns .......................................................................................................... [LUNs: 1]
  | |   | o- lun0 ..................................................................... [block/client1 (/dev/mapper/lun0.img.cow.1)]
  | |   o- portals .................................................................................................... [Portals: 1]
  | |     o- 0.0.0.0:3260 ..................................................................................................... [OK]
  | o- iqn.2019-02.pro.office24:100 ......................................................................................... [TPGs: 1]
  | | o- tpg1 ............................................................................................... [no-gen-acls, no-auth]
  | |   o- acls .......................................................................................................... [ACLs: 1]
  | |   | o- iqn.1991-05.com.microsoft:cl100 ..................................................................... [Mapped LUNs: 1]
  | |   |   o- mapped_lun0 ............................................................................. [lun0 block/client100 (rw)]
  | |   o- luns .......................................................................................................... [LUNs: 1]
  | |   | o- lun0 ................................................................. [block/client100 (/dev/mapper/lun0.img.cow.100)]
  | |   o- portals .................................................................................................... [Portals: 1]
  | |     o- 0.0.0.0:3260 ..................................................................................................... [OK]
  | o- iqn.2019-02.pro.office24:101 ......................................................................................... [TPGs: 1]
  | | o- tpg1 ............................................................................................... [no-gen-acls, no-auth]
  | |   o- acls .......................................................................................................... [ACLs: 1]
  | |   | o- iqn.1991-05.com.microsoft:work3 ...................................................................... [Mapped LUNs: 1]
  | |   |   o- mapped_lun0 ............................................................................. [lun0 block/client101 (rw)]
  | |   o- luns .......................................................................................................... [LUNs: 1]
  | |   | o- lun0 ................................................................. [block/client101 (/dev/mapper/lun0.img.cow.101)]
  | |   o- portals .................................................................................................... [Portals: 1]
  | |     o- 0.0.0.0:3260 ..................................................................................................... [OK]
  | o- iqn.2019-02.pro.office24:gserver ..................................................................................... [TPGs: 1]
  |   o- tpg1 ............................................................................................... [no-gen-acls, no-auth]
  |     o- acls .......................................................................................................... [ACLs: 1]
  |     | o- iqn.1991-05.com.microsoft:gserver .................................................................... [Mapped LUNs: 1]
  |     |   o- mapped_lun0 ............................................................................. [lun0 fileio/storage1 (rw)]
  |     o- luns .......................................................................................................... [LUNs: 1]
  |     | o- lun0 ........................................................................... [fileio/storage1 (/storage1/lun0.img)]
  |     o- portals .................................................................................................... [Portals: 1]
  |       o- 0.0.0.0:3260 ..................................................................................................... [OK]
  o- loopback ......................................................................................................... [Targets: 0]
  o- vhost ............................................................................................................ [Targets: 0]


 

INDIGO
()

Raspberry Pi - Ubuntu Server 20.0.4 LTS - не загружается.

Форум — General

Здравствуйте.

Первый раз собираю Raspberry.

В наличии: Raspberry Pi 4 Model B, X825 V2.0, X735 v2.5

  1. С помощью Raspberry Pi Imager создал на MicroSd карте Bootloader -> USB Boot. Вставил карту, включил Расбери, зелёный диод часто мигает. Вроде бы всё ок. Выключаю. Вытаскиваю карту памяти.
  2. С помощью Raspberry Pi Imager записал на SSD 120Gb Ubuntu Server 20.0.4 LTS 64bt

Всё собрал. Включаю Расбери. Горит красный светодиод и синий, который на плате X825. Зелёный молчит.

Записал на SSD другой образ, Raspberry Pi OS Lite. Всё работает, Расбери загружается с USB.

Как залить Ubuntu на SSD и загрузиться с него??????

 ,

INDIGO
()

Ubuntu 18.4 Server + MB Z390 Taichi Ultimate Lan 10Gb

Форум — Linux-hardware

Здравствуйте.

Надо собрать сервер для раздачи диска по ISCSI (targetcli)

Конфиг будет такой:

MB: Z390 Taichi Ultimate

3 NWME диска, соберу в софтовый RAID0. На рейде будет образ диска для таргета.

1 NWME диск под кеш.

1 SSD диск под ОС

Вопрос: сеть 10Gb заведётся на Ubunte из коробки? Или надо будет что-нибудь настраивать?

 

INDIGO
()

Диск накрывается?

Форум — Admin

Здравствуйте.

Посмотрите смарт, пожалуйста.

Диск накрывается?

root@fserver:~# smartctl -a /dev/sdb
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-128-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     Patriot P200 1TB
Serial Number:    AA000000000000000054
Firmware Version: S0424A0
User Capacity:    1,024,209,543,168 bytes [1.02 TB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-2 T13/2015-D revision 3
SATA Version is:  SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Tue Dec 15 14:36:04 2020 MSK
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

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

General SMART Values:
Offline data collection status:  (0x02) Offline data collection activity
                                        was completed without error.
                                        Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever
                                        been run.
Total time to complete Offline
data collection:                (  120) seconds.
Offline data collection
capabilities:                    (0x11) SMART execute Offline immediate.
                                        No Auto Offline data collection support.
                                        Suspend Offline collection upon new
                                        command.
                                        No Offline surface scan supported.
                                        Self-test supported.
                                        No Conveyance Self-test supported.
                                        No Selective Self-test supported.
SMART capabilities:            (0x0002) Does not save SMART data before
                                        entering power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine
recommended polling time:        (   2) minutes.
Extended self-test routine
recommended polling time:        (  10) minutes.

SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x0032   100   100   050    Old_age   Always       -       0
  5 Reallocated_Sector_Ct   0x0032   100   100   050    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   100   100   050    Old_age   Always       -       7594
 12 Power_Cycle_Count       0x0032   100   100   050    Old_age   Always       -       79
160 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       0
161 Unknown_Attribute       0x0033   100   100   050    Pre-fail  Always       -       100
163 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       20
164 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       22449
165 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       75
166 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       5
167 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       46
168 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       7000
169 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       100
175 Program_Fail_Count_Chip 0x0032   100   100   050    Old_age   Always       -       0
176 Erase_Fail_Count_Chip   0x0032   100   100   050    Old_age   Always       -       0
177 Wear_Leveling_Count     0x0032   100   100   050    Old_age   Always       -       0
178 Used_Rsvd_Blk_Cnt_Chip  0x0032   100   100   050    Old_age   Always       -       0
181 Program_Fail_Cnt_Total  0x0032   100   100   050    Old_age   Always       -       0
182 Erase_Fail_Count_Total  0x0032   100   100   050    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   050    Old_age   Always       -       45
194 Temperature_Celsius     0x0022   100   100   050    Old_age   Always       -       40
195 Hardware_ECC_Recovered  0x0032   100   100   050    Old_age   Always       -       4458908
196 Reallocated_Event_Count 0x0032   100   100   050    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   100   100   050    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0032   100   100   050    Old_age   Always       -       0
199 UDMA_CRC_Error_Count    0x0032   100   100   050    Old_age   Always       -       1
232 Available_Reservd_Space 0x0032   100   100   050    Old_age   Always       -       100
241 Total_LBAs_Written      0x0030   100   100   050    Old_age   Offline      -       260562
242 Total_LBAs_Read         0x0030   100   100   050    Old_age   Offline      -       2933040
245 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       749952

SMART Error Log Version: 1
Warning: ATA error count 0 inconsistent with error log pointer 1

ATA Error Count: 0
        CR = Command Register [HEX]
        FR = Features Register [HEX]
        SC = Sector Count Register [HEX]
        SN = Sector Number Register [HEX]
        CL = Cylinder Low Register [HEX]
        CH = Cylinder High Register [HEX]
        DH = Device/Head Register [HEX]
        DC = Device Command Register [HEX]
        ER = Error register [HEX]
        ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error -4 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  00 00 00 00 00 00 00

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  b0 d0 01 00 4f c2 00 08      00:00:00.000  SMART READ DATA
  b0 d1 01 01 4f c2 00 08      00:00:00.000  SMART READ ATTRIBUTE THRESHOLDS [OBS-4]
  b0 da 00 00 4f c2 00 08      00:00:00.000  SMART RETURN STATUS
  b0 d5 01 00 4f c2 00 08      00:00:00.000  SMART READ LOG
  b0 d5 01 01 4f c2 00 08      00:00:00.000  SMART READ LOG

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%      7594         -
# 2  Extended offline    Completed without error       00%      7592         -
# 3  Extended offline    Interrupted (host reset)      90%      7592         -
# 4  Extended offline    Completed without error       00%      7522         -
# 5  Extended offline    Completed without error       00%      7493         -
# 6  Short offline       Completed without error       00%      7492         -

Ещё один ssd

https://bit.ly/2JZiguC

 

INDIGO
()

targetcli - при записи на диск больших файлов получаем битые файлы.

Форум — Admin

Здравствуйте.

Использовал targetcli, Ubuntu18, клиент WIn10

Комп:

Lan 1Gb, 3SSD 1Tb, собранные в софтовый RAID0, ext4 Смонтировал этот райд на /storage1

Создал файл:

dd if=/dev/zero of=/storage1/lun0.img bs=1M count=1782579

Настройки таргета:

targetcli /backstores/fileio/ create storage1 /storage1/lun0.img
targetcli /iscsi/ create iqn.2019-02.pro.home:gserver
targetcli  /iscsi/iqn.2019-02.pro.home:gserver/tpg1/luns create /backstores/fileio/storage1
targetcli /iscsi/iqn.2019-02.pro.home:gserver/tpg1/acls/ create iqn.1991-05.com.microsoft:gserver

В винде подключился к таргету, появился диск, отформатировал в NTFS, назвал Z

Всё работает, залил файлы.

И тут началось:

При копировании больших файлов (15Gb) на диск Z, получаем битые файлы, не верная контрольная сумма.

Где смотреть? Винда? Убунта? Железо?

 

INDIGO
()

Можно ли ускорить софтовый RAID 5 ?

Форум — Admin

Здравствуйте.

Есть сервак Ubuntu16 с софтовым RAID5.

RAID5 собран из 3 HDD Seagate SV35 ST1000VX000-1ES162. Винты воткнуты в SATA2 (нет возможности перейти на SATA3)

Мерить скорость рейда через hdparm как-то не правильно, но тем не менее...

root@fserver:~# hdparm -Tt /dev/md0

/dev/md0:
 Timing cached reads:   2452 MB in  2.00 seconds = 1225.76 MB/sec
 Timing buffered disk reads: 294 MB in  3.01 seconds =  97.73 MB/sec

Что делал:

echo 8192 > /sys/block/md0/md/stripe_cache_size

Что можно сделать для увеличения скорости чтения и записи?

 

INDIGO
()

RSS подписка на новые темы