For some reason, RAID1, if you delete one of the drives is locked?

Why when removing (disconnecting) one of the two disks of a RAID 1 array, the array enters the status of "super blocks":
5e40d617d8e6f817246849.jpeg

Perhaps this is because initially, before creating the array, I removed the superblocks on the disks?
April 7th 20 at 10:55
2 answers
April 7th 20 at 10:57
Solution
It's a linux raid, and specifically the output of /proc/mdstat

Letter S in sdc1[0] (S) - designates spare disk instead of the disk array. What do you have in the array md1 no data drive. Irreversible loss sushestvovala data, there is no place to write a new one. Because the array is translated in a status of inactive, it is useless and requires administrator intervention.

Where in raid1 might be the only one to spare - for example, do not have time to sync data.
When the first time it happened.
I thought that the problem stems from the fact that mdadm felt that the data in the array is not.
At that time, the data in the array really was not:(
I took and recorded in a section of the array, 2.5 GB of data, then turned off the server, pulled one of the disks of the array, launched the server and the array became inactive:(
Condition to disable the drive:
5e410c8cbd5d7469219615.jpeg
State after disabling drive:
5e410caa47963015229946.jpeg
5e410cb24e02f153841917.jpeg - viva commented on April 7th 20 at 11:00
Look in dmesg the kernel about the arrays wrote. - Gerda42 commented on April 7th 20 at 11:03
@Karen_Spinka, after creating the array does not have given it enough time to sync before pulling the drive (about two to three hours you need for gigs mirror on sata hdd). - twila.Kozey commented on April 7th 20 at 11:06
@Cesar_Weimann, After the creation, I followed him mdstat or how to understand then, whether synchronized or not?
Or now you need to install both disk and force it to re-sync? - viva commented on April 7th 20 at 11:09
mdadm -D /dev/md1
mdadm -E /dev/sdc1
mdadm -E /dev/sdd1
cat /etc/mdadm/mdadm.conf
plus a description what exactly you do and what (the dev? the physical piece of hardware?) - Gerda42 commented on April 7th 20 at 11:12
@Karen_Spinka,
After creation, I followed him mdstat
And mdstat showed that the sync was successful? If so, it is really strange what happened. But the logs should be clear. /var/log/syslog look. - twila.Kozey commented on April 7th 20 at 11:15
@Cesar_Weimann, Yeah, I before those changes are always in control when mdstat play out and then spend manipulation...
I'll try the logs to perform... - viva commented on April 7th 20 at 11:18
@Enid.Fay30,
mdadm -D /dev/md1
5e4139d17b5f1283494585.jpeg

mdadm -E /dev/sdc1
5e413a245bf84812155613.jpeg
5e413a2e9dfa2549190342.jpeg

mdadm -E /dev/sdd1
5e413a567d40f193076064.jpeg

cat /etc/mdadm/mdadm.conf
5e413a9a28fad051979649.jpeg
5e413aa1277fd764078098.jpeg
- viva commented on April 7th 20 at 11:21
@Karen_Spinka, and you'll have to answer some questions?
clearly something strange to do with superbloom. Or defective disks. Where the superblock with sdd1 go? - Gerda42 commented on April 7th 20 at 11:24
Trying to answer everything...
The fact that I don't know where dmesg is:(
With sdd1, I agree, cant come:(
The fact that at the time when I took the logs, I just connected an empty disk in the disk array (in the experiments).
That is connected all the hard drives and normally working with arrays, it looks like this:
cat /proc/mdstat

Faceted personalities : [raid1] [raid0] [linear] [multipath] [raid6] [raid5] [raid4] [raid10]
md2 : active raid0 sdf1[1] sde1[0]
143239168 blocks super 1.2 512k chunks

md1 : active raid1 sdc1[0] sdd1[1]
975453184 blocks super 1.2 [2/2] [UU]
bitmap: 0/8 pages [0KB], 65536KB chunk

md0 : active raid1 sdb1[1] sda1[2]
487172096 blocks super 1.2 [2/2] [UU]
bitmap: 0/4 pages [0KB], 65536KB chunk

unused devices:


mdadm -D /dev/md1

/dev/md1:
Version : 1.2
Creation Time : Thu Feb 5 13:35:42 2020
Raid Level : raid1
Array Size : 975453184 (930.26 GiB 998.86 GB)
Used Dev Size : 975453184 (930.26 GiB 998.86 GB)
Raid Devices : 2
Total Devices : 2
Persistence : Superblock is persistent

Intent Bitmap : Internal

Update Time : Tue Feb 11 11:09:55 2020
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0

Policy Consistency : bitmap

Name : phoenix:1 (local to host phoenix)
UUID : 8677539e:70f9cc03:a26ae668:c9424e90
Events : 20131

Number Major Minor RaidDevice State
0 8 33 0 active sync /dev/sdc1
1 8 49 1 active sync /dev/sdd1

mdadm -E /dev/sdc1

/dev/sdc1:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x1
Array UUID : 8677539e:70f9cc03:a26ae668:c9424e90
Name : phoenix:1 (local to host phoenix)
Creation Time : Thu Feb 5 13:35:42 2020
Raid Level : raid1
Raid Devices : 2

Avail Dev Size : 1950906368 (930.26 GiB 998.86 GB)
Array Size : 975453184 (930.26 GiB 998.86 GB)
Data Offset : 264192 sectors
Super Offset : 8 sectors
Unused Space : before=264112 sectors, after=0 sectors
State : clean
Device UUID : 23b93f64:cd000034:99e6f05c:ba8bb104

Internal Bitmap : 8 sectors from superblock
Update Time : Tue Feb 11 11:09:55 2020
Bad Block Log : 512 entries available at offset 16 sectors
Checksum : 8365060d - correct
Events : 20131

Device Role : Active device 0
Array State : AA ('A' == active, '.' == missing, 'R' == replacing)

mdadm -E /dev/sdd1

/dev/sdd1:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x1
Array UUID : 8677539e:70f9cc03:a26ae668:c9424e90
Name : phoenix:1 (local to host phoenix)
Creation Time : Thu Feb 5 13:35:42 2020
Raid Level : raid1
Raid Devices : 2

Avail Dev Size : 1950906368 (930.26 GiB 998.86 GB)
Array Size : 975453184 (930.26 GiB 998.86 GB)
Data Offset : 264192 sectors
Super Offset : 8 sectors
Unused Space : before=264112 sectors, after=0 sectors
State : clean
Device UUID : b49f0cc2:1b8093e0:48286442:fa57aca9

Internal Bitmap : 8 sectors from superblock
Update Time : Tue Feb 11 11:09:55 2020
Bad Block Log : 512 entries available at offset 16 sectors
Checksum : 183379de - correct
Events : 20131

Device Role : Active device 1
Array State : AA ('A' == active, '.' == missing, 'R' == replacing)

cat /etc/mdadm/mdadm.conf

# mdadm.conf
#
# !NB! Run update-initramfs-u after updating this file.
# !NB! This will ensure that the initramfs has an uptodate copy.
#
# Please refer to mdadm.conf(5) for information about this file.
#

# by default (built-in), scan all partitions (/proc/partitions) and all
# containers for MD superblocks. alternatively, specify devices to scan, using
# wild cards if desired.
#DEVICE partitions containers

# automatically tag new arrays as belonging to the local system
HOMEHOST

# instruct the monitoring daemon where to send mail alerts
MAILADDR root

# definitions of existing MD arrays
ARRAY /dev/md/0 metadata=1.2 UUID=29066ab9:48bffd4b:ec21b29b:4e332b1e name=phoenix:0
ARRAY /dev/md/1 metadata=1.2 UUID=8677539e:70f9cc03:a26ae668:c9424e90 name=phoenix:1
ARRAY /dev/md/2 metadata=1.2 UUID=2d47cdca:3461f154:1dbbbf57:a44ca46c name=phoenix:2

# This configuration was auto-generated on Wed, 05 Feb 2020 13:53:10 +0900 by mkconf
- viva commented on April 7th 20 at 11:27
The fact that I don't know where dmesg is:(

This is the command console. - Gerda42 commented on April 7th 20 at 11:30
@Enid.Fay30,
In dmesg, any criminal have not seen, well understood, moreover, that the md1 array was not trying to initialize.
And lvm on something swears:
[ 24.773005] random: lvm: uninitialized urandom read (4 bytes read)
[ 25.234544] random: init done crng

But I can't understand that he doesn't like it:(

Here is the results:
dmesg with all discs (i.e., when the array active)


[ 4.408074] usb 2-1: new low-speed USB device number 2 using uhci_hcd
[ 4.544083] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 4.563948] ata1.00: ATA-8: WDC WD5000AADS-00S9B0, 01.00A01, max UDMA/133
[ 4.563952] ata1.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 0/32)
[ 4.566725] ata1.00: configured for UDMA/133
[ 4.566967] scsi 0:0:0:0: Direct-Access ATA WDC WD5000AADS-0 0A01 PQ: 0 ANSI: 5
[ 4.585810] usb 2-1: New USB device found, idVendor=2101, idProduct=020f, bcdDevice= 0.01
[ 4.585814] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 4.626275] hidraw: raw HID events driver (C) Jiri Kosina
[ 4.677974] usbcore: registered new interface driver usbhid
[ 4.677977] usbhid: USB HID core driver
[ 4.695042] input: HID 2101:020f as /devices/pci0000:00/0000:00:1d.1/usb2/2-1/2-1:1.0/0003:2101:020F.0001/input/input3
[ 4.752480] hid-generic 0003:2101:020F.0001: input,hidraw0: USB HID v1.01 Keyboard [HID 2101:020f] on usb-0000:00:1d.1-1/input0
[ 4.753723] input: HID 2101:020f as /devices/pci0000:00/0000:00:1d.1/usb2/2-1/2-1:1.1/0003:2101:020F.0002/input/input4
[ 4.753931] hid-generic 0003:2101:020F.0002: input,hidraw1: USB HID v1.01 Mouse [HID 2101:020f] on usb-0000:00:1d.1-1/input1
[ 5.040088] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 5.455100] ata2.00: ATA-8: WDC WD5000AADS-00S9B0, 01.00A01, max UDMA/133
[ 5.455103] ata2.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 0/32)
[ 5.499551] ata2.00: configured for UDMA/133
[ 5.499797] scsi 2:0:0:0: Direct-Access ATA WDC WD5000AADS-0 0A01 PQ: 0 ANSI: 5
[ 5.972082] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 5.974699] ata3.00: ATA-10: WDC WD10EZEX-00WN4A0, 01.01A01, max UDMA/133
[ 5.974702] ata3.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32)
[ 5.977432] ata3.00: configured for UDMA/133
[ 5.977665] scsi 3:0:0:0: Direct-Access ATA WDC WD10EZEX-00W 1A01 PQ: 0 ANSI: 5
[ 6.448085] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 6.450712] ata4.00: ATA-10: WDC WD10EZEX-00WN4A0, 01.01A01, max UDMA/133
[ 6.450716] ata4.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32)
[ 6.453452] ata4.00: configured for UDMA/133
[ 6.453679] scsi 4:0:0:0: Direct-Access ATA WDC WD10EZEX-00W 1A01 PQ: 0 ANSI: 5
[ 6.477829] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 GiB)
[ 6.477853] sd 0:0:0:0: [sda] Write Protect is off
[ 6.477859] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 6.477897] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 6.479234] sd 2:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/466 GiB)
[ 6.479262] sd 2:0:0:0: [sdb] Write Protect is off
[ 6.479267] sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 6.479303] sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 6.481016] sd 3:0:0:0: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[ 6.481023] sd 3:0:0:0: [sdc] 4096-byte physical blocks
[ 6.481047] sd 3:0:0:0: [sdc] Write Protect is off
[ 6.481052] sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[ 6.481086] sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

[ 6.481434] sd 4:0:0:0: [sdd] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[ 6.481439] sd 4:0:0:0: [sdd] 4096-byte physical blocks
[ 6.481460] sd 4:0:0:0: [sdd] Write Protect is off
[ 6.481465] sd 4:0:0:0: [sdd] Mode Sense: 00 3a 00 00
[ 6.481495] sd 4:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 6.490717] sdb: sdb1
[ 6.491743] sda: sda1
[ 6.491792] sd 2:0:0:0: [sdb] Attached SCSI disk

[ 6.492758] sd 0:0:0:0: [sda] Attached SCSI disk
[ 6.497155] sdc: sdc1
[ 6.498017] sd 3:0:0:0: [sdc] Attached SCSI disk

[ 6.500945] sdd: sdd1
[ 6.501926] sd 4:0:0:0: [sdd] Attached SCSI disk
[ 6.666586] random: init done fast
[ 6.731764] md/raid1:md0: active with 2 out of 2 mirrors

[ 6.735693] md/raid1:md1: active with 2 out of 2 mirrors
[ 6.777364] md0: detected capacity change from 0 to 498864226304
[ 6.789093] md1: detected capacity change from 0 to 998864060416
[ 19.396074] scsi host6: Adaptec AIC79XX PCI-X SCSI HBA DRIVER, Rev 3.0

aic7901A: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 67-100MHz, 512 SCBs
[ 19.412183] scsi 6:0:0:0: Direct-Access SEAGATE ST373207LW 0005 PQ: 0 ANSI: 3
[ 19.412197] scsi target6:0:0: asynchronous
[ 19.412200] scsi6:A:0:0:
[ 19.412202] Tagged Queuing enabled. Depth 32
[ 19.436054] scsi target6:0:0: Beginning Domain Validation
[ 19.439800] scsi target6:0:0: wide asynchronous
[ 19.442609] scsi target6:0:0: FAST-160 WIDE SCSI 320.0 MB/s DT IU QAS RDSTRM WRFLOW PCOMP (6.25 ns, offset 63)
[ 19.457827] scsi 6:0:0:0: Power-on or device reset occurred
[ 19.461057] scsi target6:0:0: Ending Domain Validation
[ 19.470597] scsi 6:0:1:0: Direct-Access SEAGATE ST373207LW 0005 PQ: 0 ANSI: 3
[ 19.470611] scsi target6:0:1: asynchronous
[ 19.470614] scsi6:A:1:0:
[ 19.470616] Tagged Queuing enabled. Depth 32
[ 19.488053] scsi target6:0:1: Beginning Domain Validation
[ 19.491820] scsi target6:0:1: wide asynchronous
[ 19.494654] scsi target6:0:1: FAST-160 WIDE SCSI 320.0 MB/s DT IU QAS RDSTRM WRFLOW PCOMP (6.25 ns, offset 63)
[ 19.509848] scsi 6:0:1:0: Power-on or device reset occurred
[ 19.513180] scsi target6:0:1: Ending Domain Validation
[ 22.886009] sd 6:0:0:0: [sde] 143374744 512-byte logical blocks: (73.4 GB/68.4 GiB)
[ 22.886110] sd 6:0:1:0: [sdf] 143374744 512-byte logical blocks: (73.4 GB/68.4 GiB)
[ 22.887459] sd 6:0:0:0: [sde] Write Protect is off
[ 22.887463] sd 6:0:0:0: [sde] Mode Sense: ab 00 10 08
[ 22.887516] sd 6:0:1:0: [sdf] Write Protect is off
[ 22.887520] sd 6:0:1:0: [sdf] Mode Sense: ab 00 10 08
[ 22.889290] sd 6:0:0:0: [sde] Write cache: disabled, read cache: enabled, supports DPO and FUA
[ 22.889349] sd 6:0:1:0: [sdf] Write cache: enabled, read cache: enabled, supports DPO and FUA

[ 22.897399] random: init done crng
[ 22.897478] sdf: sdf1
[ 22.902462] sd 6:0:1:0: [sdf] Attached SCSI disk
[ 22.904255] sde: sde1
[ 22.909179] sd 6:0:0:0: [sde] Attached SCSI disk
[ 23.117350] md2: detected capacity change from 0 to 146676908032
[ 23.328064] raid6: mmxx1 gen() 1989 MB/s
[ 23.396059] raid6: mmxx2 gen() 2523 MB/s
[ 23.464082] raid6: sse1x1 gen() 1283 MB/s
[ 23.532071] raid6: sse1x2 gen() 1770 MB/s
[ 23.600076] raid6: sse2x1 gen() 2106 MB/s
[ 23.668065] raid6: sse2x1 xor() 1579 MB/s
[ 23.736064] raid6: sse2x2 gen() 2622 MB/s
[ 23.804050] raid6: sse2x2 xor() 1581 MB/s
[ 23.804052] raid6: using algorithm sse2x2 gen() 2622 MB/s
[ 23.804054] raid6: .... xor() 1581 MB/s, rmw enabled
[ 23.804056] raid6: using intx1 recovery algorithm
[ 23.808471] xor: measuring software checksum speed
[ 23.848050] pIII_sse : 3430.000 MB/sec
[ 23.888048] prefetch64-sse: 4414.000 MB/sec
[ 23.888052] xor: using function: prefetch64-sse (4414.000 MB/sec)
[ 23.891579] async_tx: api initialized (async)

[ 24.095808] device-mapper: uevent: version 1.0.3
[ 24.096210] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: dm-devel@redhat.com
[ 28.366681] PM: Image not found (code -22)
[ 28.702158] cryptd: max_cpu_qlen set to 1000
[ 29.001577] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null)
[ 30.614061] systemd[1]: Inserted module 'autofs4'
[ 30.721040] systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD-IDN2 +IDN PCRE2 default-hierarchy=hybrid)
[ 30.721434] systemd[1]: Detected architecture x86.
[ 30.734835] systemd[1]: Set hostname to .
[ 31.760262] systemd[1]: Listening on Device-mapper event daemon FIFOs.

[ 31.760543] systemd[1]: Reached target Remote File Systems.
[ 31.760778] systemd[1]: Listening on initctl Compatibility Named Pipe.
[ 31.761284] systemd[1]: Listening on Journal Socket (/dev/log).
[ 31.761795] systemd[1]: Listening on Journal Socket.
[ 31.766952] systemd[1]: Starting Availability of block devices...
[ 31.767723] systemd[1]: Listening on Syslog Socket.
[ 32.147587] EXT4-fs (dm-1): re-mounted. Opts: errors=remount-ro
[ 32.643950] systemd-journald[281]: Received request to flush runtime journal from PID 1

- viva commented on April 7th 20 at 11:33
dmesg from one of the disks in the array (that is, when the array is not active)


[ 4.838039] sata_promise 0000:01:09.0: version 2.12
[ 4.864102] ata_piix 0000:00:1f.1: version 2.13
[ 4.864121] ata_piix 0000:00:1f.1: enabling device (0005 -> 0007)
[ 4.866169] scsi host1: ata_piix
[ 4.866556] scsi host2: ata_piix
[ 4.866709] ata5: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma irq 14 0x3a0
[ 4.866713] ata6: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x3a8 irq 15
[ 4.868324] scsi host0: sata_promise
[ 4.868686] scsi host3: sata_promise
[ 4.869065] scsi host4: sata_promise
[ 4.869348] scsi host5: sata_promise
[ 4.869500] ata1: SATA max UDMA/133 mmio m4096@0xfe8f0000 irq 18 ata 0xfe8f0380
[ 4.869504] ata2: SATA max UDMA/133 mmio m4096@0xfe8f0000 irq 18 ata 0xfe8f0280
[ 4.869508] ata3: SATA max UDMA/133 mmio m4096@0xfe8f0000 irq 18 ata 0xfe8f0200
[ 4.869512] ata4: SATA max UDMA/133 mmio m4096@0xfe8f0000 irq 18 ata 0xfe8f0300

[ 4.900375] e100 0000:01:03.0 eth0: addr 0xfe7e0000, irq 20, MAC addr 00:07:e9:3f:b3:b2
[ 4.906542] e100 0000:01:03.0 enp1s3: renamed from eth0
[ 5.128795] usb 2-1: new low-speed USB device number 2 using uhci_hcd
[ 5.214709] e1000 0000:01:04.0 eth0: (PCI:33MHz:32-bit) 00:07:e9:3f:b3:b3
[ 5.214724] e1000 0000:01:04.0 eth0: Intel(R) PRO/1000 Network Connection
[ 5.218140] e1000 0000:01:04.0 enp1s4: renamed from eth0
[ 5.306517] usb 2-1: New USB device found, idVendor=2101, idProduct=020f, bcdDevice= 0.01
[ 5.306522] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 5.322367] hidraw: raw HID events driver (C) Jiri Kosina

[ 5.340839] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 5.354160] ata1.00: ATA-8: WDC WD5000AADS-00S9B0, 01.00A01, max UDMA/133
[ 5.354164] ata1.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 0/32)
[ 5.356962] ata1.00: configured for UDMA/133
[ 5.357210] scsi 0:0:0:0: Direct-Access ATA WDC WD5000AADS-0 0A01 PQ: 0 ANSI: 5

[ 5.362815] usbcore: registered new interface driver usbhid
[ 5.362818] usbhid: USB HID core driver
[ 5.371955] input: HID 2101:020f as /devices/pci0000:00/0000:00:1d.1/usb2/2-1/2-1:1.0/0003:2101:020F.0001/input/input3
[ 5.429225] hid-generic 0003:2101:020F.0001: input,hidraw0: USB HID v1.01 Keyboard [HID 2101:020f] on usb-0000:00:1d.1-1/input0
[ 5.430571] input: HID 2101:020f as /devices/pci0000:00/0000:00:1d.1/usb2/2-1/2-1:1.1/0003:2101:020F.0002/input/input4
[ 5.430797] hid-generic 0003:2101:020F.0002: input,hidraw1: USB HID v1.01 Mouse [HID 2101:020f] on usb-0000:00:1d.1-1/input1
[ 5.828813] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 5.847630] ata2.00: ATA-8: WDC WD5000AADS-00S9B0, 01.00A01, max UDMA/133
[ 5.847634] ata2.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 0/32)
[ 5.850406] ata2.00: configured for UDMA/133
[ 5.850636] scsi 3:0:0:0: Direct-Access ATA WDC WD5000AADS-0 0A01 PQ: 0 ANSI: 5
[ 6.320809] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 6.323438] ata3.00: ATA-10: WDC WD10EZEX-00WN4A0, 01.01A01, max UDMA/133
[ 6.323441] ata3.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32)
[ 6.326189] ata3.00: configured for UDMA/133
[ 6.326445] scsi 4:0:0:0: Direct-Access ATA WDC WD10EZEX-00W 1A01 PQ: 0 ANSI: 5
[ 6.639040] ata4: SATA link down (SStatus 0 SControl 300)

[ 6.658000] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 GiB)
[ 6.658027] sd 0:0:0:0: [sda] Write Protect is off
[ 6.658032] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 6.658072] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 6.658471] sd 3:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/466 GiB)
[ 6.658498] sd 3:0:0:0: [sdb] Write Protect is off
[ 6.658503] sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 6.658544] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 6.658882] sd 4:0:0:0: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[ 6.658887] sd 4:0:0:0: [sdc] 4096-byte physical blocks
[ 6.658906] sd 4:0:0:0: [sdc] Write Protect is off
[ 6.658911] sd 4:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[ 6.658952] sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 6.667339] sdb: sdb1

[ 6.668044] sd 3:0:0:0: [sdb] Attached SCSI disk
[ 6.669746] sda: sda1

[ 6.670492] sd 0:0:0:0: [sda] Attached SCSI disk
[ 6.677638] sdc: sdc1

[ 6.678313] sd 4:0:0:0: [sdc] Attached SCSI disk

[ 6.904107] md/raid1:md0: active with 2 out of 2 mirrors
[ 6.931704] random: init done fast

[ 6.941949] md0: detected capacity change from 0 to 498864226304

[ 20.184809] scsi host6: Adaptec AIC79XX PCI-X SCSI HBA DRIVER, Rev 3.0

aic7901A: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 67-100MHz, 512 SCBs
[ 20.196921] scsi 6:0:0:0: Direct-Access SEAGATE ST373207LW 0005 PQ: 0 ANSI: 3
[ 20.196935] scsi target6:0:0: asynchronous
[ 20.196938] scsi6:A:0:0:
[ 20.196940] Tagged Queuing enabled. Depth 32
[ 20.216785] scsi target6:0:0: Beginning Domain Validation
[ 20.220527] scsi target6:0:0: wide asynchronous
[ 20.223336] scsi target6:0:0: FAST-160 WIDE SCSI 320.0 MB/s DT IU QAS RDSTRM WRFLOW PCOMP (6.25 ns, offset 63)
[ 20.238551] scsi 6:0:0:0: Power-on or device reset occurred
[ 20.241769] scsi target6:0:0: Ending Domain Validation
[ 20.254285] scsi 6:0:1:0: Direct-Access SEAGATE ST373207LW 0005 PQ: 0 ANSI: 3
[ 20.254299] scsi target6:0:1: asynchronous
[ 20.254303] scsi6:A:1:0:
[ 20.254305] Tagged Queuing enabled. Depth 32
[ 20.268784] scsi target6:0:1: Beginning Domain Validation
[ 20.272546] scsi target6:0:1: wide asynchronous
[ 20.275372] scsi target6:0:1: FAST-160 WIDE SCSI 320.0 MB/s DT IU QAS RDSTRM WRFLOW PCOMP (6.25 ns, offset 63)
[ 20.290578] scsi 6:0:1:0: Power-on or device reset occurred
[ 20.293887] scsi target6:0:1: Ending Domain Validation
[ 23.669757] sd 6:0:0:0: [sdd] 143374744 512-byte logical blocks: (73.4 GB/68.4 GiB)
[ 23.669845] sd 6:0:1:0: [sde] 143374744 512-byte logical blocks: (73.4 GB/68.4 GiB)
[ 23.671192] sd 6:0:0:0: [sdd] Write Protect is off
[ 23.671195] sd 6:0:0:0: [sdd] Mode Sense: ab 00 10 08
[ 23.671251] sd 6:0:1:0: [sde] Write Protect is off
[ 23.671254] sd 6:0:1:0: [sde] Mode Sense: ab 00 10 08
[ 23.673022] sd 6:0:0:0: [sdd] Write cache: disabled, read cache: enabled, supports DPO and FUA
[ 23.673076] sd 6:0:1:0: [sde] Write cache: enabled, read cache: enabled, supports DPO and FUA
[ 23.683643] sdd: sdd1
[ 23.687221] sde: sde1

[ 23.688659] sd 6:0:0:0: [sdd] Attached SCSI disk

[ 23.692199] sd 6:0:1:0: [sde] Attached SCSI disk
[ 23.907807] md2: detected capacity change from 0 to 146676908032
[ 24.124814] raid6: mmxx1 gen() 1994 MB/s
[ 24.192792] raid6: mmxx2 gen() 2529 MB/s
[ 24.260798] raid6: sse1x1 gen() 1277 MB/s
[ 24.328783] raid6: sse1x2 gen() 1758 MB/s
[ 24.396783] raid6: sse2x1 gen() 2141 MB/s
[ 24.464780] raid6: sse2x1 xor() 1576 MB/s
[ 24.532789] raid6: sse2x2 gen() 2627 MB/s
[ 24.600776] raid6: sse2x2 xor() 1582 MB/s
[ 24.600779] raid6: using algorithm sse2x2 gen() 2627 MB/s
[ 24.600780] raid6: .... xor() 1582 MB/s, rmw enabled
[ 24.600782] raid6: using intx1 recovery algorithm
[ 24.605408] xor: measuring software checksum speed
[ 24.644778] pIII_sse : 3422.000 MB/sec
[ 24.684774] prefetch64-sse: 4415.000 MB/sec
[ 24.684777] xor: using function: prefetch64-sse (4415.000 MB/sec)
[ 24.688418] async_tx: api initialized (async)
[ 24.773005] random: lvm: uninitialized urandom read (4 bytes read)
[ 25.234544] random: init done crng
[ 25.295333] device-mapper: uevent: version 1.0.3
[ 25.295564] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: dm-devel@redhat.com
[ 29.311442] PM: Image not found (code -22)
[ 29.611548] cryptd: max_cpu_qlen set to 1000
[ 29.877734] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null)



Additionally, I tried to derive an array of inactive teams:
# mdadm --stop /dev/md1
# mdadm --assemble --force /dev/md1

But while the array became active, and the results mdstat shows that one disk worker, the files in the directory that applies to the array are not visible...
Well and accordingly after a reboot, the array again becomes inactive... - viva commented on April 7th 20 at 11:36
@Cesar_Weimann,
In /var/log/syslog also seems to be all right...
/var/log/syslog part 1


Feb 11 15:46:44 phoenix kernel: [ 4.877917] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
Feb 11 15:46:44 phoenix kernel: [ 4.877928] uhci_hcd 0000:00:1d.2: detected 2 ports
Feb 11 15:46:44 phoenix kernel: [ 4.877955] uhci_hcd 0000:00:1d.2: irq 18, io base 0x00003000
Feb 11 15:46:44 phoenix kernel: [ 4.878150] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 4.19
Feb 11 15:46:44 phoenix kernel: [ 4.878154] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 11 15:46:44 phoenix kernel: [ 4.878157] usb usb3: Product: UHCI Host Controller
Feb 11 15:46:44 phoenix kernel: [ 4.878161] usb usb3: Manufacturer: Linux 4.19.0-8-686-pae uhci_hcd
Feb 11 15:46:44 phoenix kernel: [ 4.878164] usb usb3: SerialNumber: 0000:00:1d.2
Feb 11 15:46:44 phoenix kernel: [ 4.879506] ata_piix 0000:00:1f.1: version 2.13
Feb 11 15:46:44 phoenix kernel: [ 4.879521] ata_piix 0000:00:1f.1: enabling device (0005 -> 0007)
Feb 11 15:46:44 phoenix kernel: [ 4.880252] hub 3-0:1.0: USB hub found
Feb 11 15:46:44 phoenix kernel: [ 4.880277] hub 3-0:1.0: 2 ports detected
Feb 11 15:46:44 phoenix kernel: [ 4.882061] scsi host1: sata_promise
Feb 11 15:46:44 phoenix kernel: [ 4.882094] scsi host2: ata_piix
Feb 11 15:46:44 phoenix kernel: [ 4.882484] scsi host3: ata_piix
Feb 11 15:46:44 phoenix kernel: [ 4.882634] ata5: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma irq 14 0x3a0
Feb 11 15:46:44 phoenix kernel: [ 4.882638] ata6: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x3a8 irq 15
Feb 11 15:46:44 phoenix kernel: [ 4.899891] scsi host4: sata_promise
Feb 11 15:46:44 phoenix kernel: [ 4.900766] scsi host5: sata_promise
Feb 11 15:46:44 phoenix kernel: [ 4.900962] ata1: SATA max UDMA/133 mmio m4096@0xfe8f0000 irq 18 ata 0xfe8f0380
Feb 11 15:46:44 phoenix kernel: [ 4.900966] ata2: SATA max UDMA/133 mmio m4096@0xfe8f0000 irq 18 ata 0xfe8f0280
Feb 11 15:46:44 phoenix kernel: [ 4.900971] ata3: SATA max UDMA/133 mmio m4096@0xfe8f0000 irq 18 ata 0xfe8f0200
Feb 11 15:46:44 phoenix kernel: [ 4.900974] ata4: SATA max UDMA/133 mmio m4096@0xfe8f0000 irq 18 ata 0xfe8f0300
Feb 11 15:46:44 phoenix kernel: [ 4.909946] e100 0000:01:03.0 enp1s3: renamed from eth0
Feb 11 15:46:44 phoenix kernel: [ 5.162138] e1000 0000:01:04.0 eth0: (PCI:33MHz:32-bit) 00:07:e9:3f:b3:b3
Feb 11 15:46:44 phoenix kernel: [ 5.162153] e1000 0000:01:04.0 eth0: Intel(R) PRO/1000 Network Connection
Feb 11 15:46:44 phoenix kernel: [ 5.165628] e1000 0000:01:04.0 enp1s4: renamed from eth0
Feb 11 15:46:44 phoenix kernel: [ 5.296203] usb 2-1: new low-speed USB device number 2 using uhci_hcd
Feb 11 15:46:44 phoenix kernel: [ 5.372231] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Feb 11 15:46:44 phoenix kernel: [ 5.391344] ata1.00: ATA-8: WDC WD5000AADS-00S9B0, 01.00A01, max UDMA/133
Feb 11 15:46:44 phoenix kernel: [ 5.391348] ata1.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 0/32)
Feb 11 15:46:44 phoenix kernel: [ 5.394102] ata1.00: configured for UDMA/133
Feb 11 15:46:44 phoenix kernel: [ 5.394339] scsi 0:0:0:0: Direct-Access ATA WDC WD5000AADS-0 0A01 PQ: 0 ANSI: 5
Feb 11 15:46:44 phoenix kernel: [ 5.473489] usb 2-1: New USB device found, idVendor=2101, idProduct=020f, bcdDevice= 0.01
Feb 11 15:46:44 phoenix kernel: [ 5.473493] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Feb 11 15:46:44 phoenix kernel: [ 5.489819] hidraw: raw HID events driver (C) Jiri Kosina
Feb 11 15:46:44 phoenix kernel: [ 5.529785] usbcore: registered new interface driver usbhid
Feb 11 15:46:44 phoenix kernel: [ 5.529789] usbhid: USB HID core driver
Feb 11 15:46:44 phoenix kernel: [ 5.538567] input: HID 2101:020f as /devices/pci0000:00/0000:00:1d.1/usb2/2-1/2-1:1.0/0003:2101:020F.0001/input/input3
Feb 11 15:46:44 phoenix kernel: [ 5.596809] hid-generic 0003:2101:020F.0001: input,hidraw0: USB HID v1.01 Keyboard [HID 2101:020f] on usb-0000:00:1d.1-1/input0
Feb 11 15:46:44 phoenix kernel: [ 5.598886] input: HID 2101:020f as /devices/pci0000:00/0000:00:1d.1/usb2/2-1/2-1:1.1/0003:2101:020F.0002/input/input4
Feb 11 15:46:44 phoenix kernel: [ 5.599241] hid-generic 0003:2101:020F.0002: input,hidraw1: USB HID v1.01 Mouse [HID 2101:020f] on usb-0000:00:1d.1-1/input1
Feb 11 15:46:44 phoenix kernel: [ 5.868230] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Feb 11 15:46:44 phoenix kernel: [ 5.886540] ata2.00: ATA-8: WDC WD5000AADS-00S9B0, 01.00A01, max UDMA/133
Feb 11 15:46:44 phoenix kernel: [ 5.886543] ata2.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 0/32)
Feb 11 15:46:44 phoenix kernel: [ 5.889318] ata2.00: configured for UDMA/133
Feb 11 15:46:44 phoenix kernel: [ 5.889556] scsi 1:0:0:0: Direct-Access ATA WDC WD5000AADS-0 0A01 PQ: 0 ANSI: 5
Feb 11 15:46:44 phoenix kernel: [ 6.360227] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Feb 11 15:46:44 phoenix kernel: [ 6.362865] ata3.00: ATA-10: WDC WD10EZEX-00WN4A0, 01.01A01, max UDMA/133
Feb 11 15:46:44 phoenix kernel: [ 6.362869] ata3.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32)
Feb 11 15:46:44 phoenix kernel: [ 6.365605] ata3.00: configured for UDMA/133
Feb 11 15:46:44 phoenix kernel: [ 6.365841] scsi 4:0:0:0: Direct-Access ATA WDC WD10EZEX-00W 1A01 PQ: 0 ANSI: 5
Feb 11 15:46:44 phoenix kernel: [ 6.836254] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Feb 11 15:46:44 phoenix kernel: [ 6.838882] ata4.00: ATA-10: WDC WD10EZEX-00WN4A0, 01.01A01, max UDMA/133
Feb 11 15:46:44 phoenix kernel: [ 6.838885] ata4.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32)
Feb 11 15:46:44 phoenix kernel: [ 6.841621] ata4.00: configured for UDMA/133
Feb 11 15:46:44 phoenix kernel: [ 6.841846] scsi 5:0:0:0: Direct-Access ATA WDC WD10EZEX-00W 1A01 PQ: 0 ANSI: 5
Feb 11 15:46:44 phoenix kernel: [ 6.861416] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 GiB)
Feb 11 15:46:44 phoenix kernel: [ 6.861440] sd 0:0:0:0: [sda] Write Protect is off
Feb 11 15:46:44 phoenix kernel: [ 6.861444] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Feb 11 15:46:44 phoenix kernel: [ 6.861479] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 11 15:46:44 phoenix kernel: [ 6.862791] sd 1:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/466 GiB)
Feb 11 15:46:44 phoenix kernel: [ 6.862819] sd 1:0:0:0: [sdb] Write Protect is off

- viva commented on April 7th 20 at 11:39
/var/log/syslog part 2

Feb 11 15:46:44 phoenix kernel: [ 6.862825] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Feb 11 15:46:44 phoenix kernel: [ 6.862866] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 11 15:46:44 phoenix kernel: [ 6.863265] sd 4:0:0:0: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
Feb 11 15:46:44 phoenix kernel: [ 6.863272] sd 4:0:0:0: [sdc] 4096-byte physical blocks
Feb 11 15:46:44 phoenix kernel: [ 6.863297] sd 4:0:0:0: [sdc] Write Protect is off
Feb 11 15:46:44 phoenix kernel: [ 6.863302] sd 4:0:0:0: [sdc] Mode Sense: 00 3a 00 00
Feb 11 15:46:44 phoenix kernel: [ 6.863345] sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 11 15:46:44 phoenix kernel: [ 6.865567] sd 5:0:0:0: [sdd] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
Feb 11 15:46:44 phoenix kernel: [ 6.865573] sd 5:0:0:0: [sdd] 4096-byte physical blocks
Feb 11 15:46:44 phoenix kernel: [ 6.865602] sd 5:0:0:0: [sdd] Write Protect is off
Feb 11 15:46:44 phoenix kernel: [ 6.865606] sd 5:0:0:0: [sdd] Mode Sense: 00 3a 00 00
Feb 11 15:46:44 phoenix kernel: [ 6.865645] sd 5:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 11 15:46:44 phoenix kernel: [ 6.874210] sdb: sdb1
Feb 11 15:46:44 phoenix kernel: [ 6.874960] sda: sda1
Feb 11 15:46:44 phoenix kernel: [ 6.874982] sd 1:0:0:0: [sdb] Attached SCSI disk
Feb 11 15:46:44 phoenix kernel: [ 6.875628] sd 0:0:0:0: [sda] Attached SCSI disk
Feb 11 15:46:44 phoenix kernel: [ 6.883882] sdd: sdd1
Feb 11 15:46:44 phoenix kernel: [ 6.884584] sdc: sdc1
Feb 11 15:46:44 phoenix kernel: [ 6.884691] sd 5:0:0:0: [sdd] Attached SCSI disk
Feb 11 15:46:44 phoenix kernel: [ 6.885444] sd 4:0:0:0: [sdc] Attached SCSI disk
Feb 11 15:46:44 phoenix kernel: [ 7.048536] random: init done fast
Feb 11 15:46:44 phoenix kernel: [ 7.113517] md/raid1:md0: active with 2 out of 2 mirrors
Feb 11 15:46:44 phoenix kernel: [ 7.113811] md/raid1:md1: active with 2 out of 2 mirrors
Feb 11 15:46:44 phoenix kernel: [ 7.148958] md0: detected capacity change from 0 to 498864226304
Feb 11 15:46:44 phoenix kernel: [ 7.164653] md1: detected capacity change from 0 to 998864060416
Feb 11 15:46:44 phoenix kernel: [ 20.184219] scsi host6: Adaptec AIC79XX PCI-X SCSI HBA DRIVER, Rev 3.0
Feb 11 15:46:44 phoenix kernel: [ 20.184219]
Feb 11 15:46:44 phoenix kernel: [ 20.184219] aic7901A: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 67-100MHz, 512 SCBs
Feb 11 15:46:44 phoenix kernel: [ 20.196266] scsi 6:0:0:0: Direct-Access SEAGATE ST373207LW 0005 PQ: 0 ANSI: 3
Feb 11 15:46:44 phoenix kernel: [ 20.196280] scsi target6:0:0: asynchronous
Feb 11 15:46:44 phoenix kernel: [ 20.196283] scsi6:A:0:0:
Feb 11 15:46:44 phoenix kernel: [ 20.196285] Tagged Queuing enabled. Depth 32
Feb 11 15:46:44 phoenix kernel: [ 20.224199] scsi target6:0:0: Beginning Domain Validation
Feb 11 15:46:44 phoenix kernel: [ 20.227960] scsi target6:0:0: wide asynchronous
Feb 11 15:46:44 phoenix kernel: [ 20.230773] scsi target6:0:0: FAST-160 WIDE SCSI 320.0 MB/s DT IU QAS RDSTRM WRFLOW PCOMP (6.25 ns, offset 63)
Feb 11 15:46:44 phoenix kernel: [ 20.245970] scsi 6:0:0:0: Power-on or device reset occurred
Feb 11 15:46:44 phoenix kernel: [ 20.249178] scsi target6:0:0: Ending Domain Validation
Feb 11 15:46:44 phoenix kernel: [ 20.258782] scsi 6:0:1:0: Direct-Access SEAGATE ST373207LW 0005 PQ: 0 ANSI: 3
Feb 11 15:46:44 phoenix kernel: [ 20.258796] scsi target6:0:1: asynchronous
Feb 11 15:46:44 phoenix kernel: [ 20.258799] scsi6:A:1:0:
Feb 11 15:46:44 phoenix kernel: [ 20.258801] Tagged Queuing enabled. Depth 32
Feb 11 15:46:44 phoenix kernel: [ 20.276197] scsi target6:0:1: Beginning Domain Validation
Feb 11 15:46:44 phoenix kernel: [ 20.279949] scsi target6:0:1: wide asynchronous
Feb 11 15:46:44 phoenix kernel: [ 20.282781] scsi target6:0:1: FAST-160 WIDE SCSI 320.0 MB/s DT IU QAS RDSTRM WRFLOW PCOMP (6.25 ns, offset 63)
Feb 11 15:46:44 phoenix kernel: [ 20.297995] scsi 6:0:1:0: Power-on or device reset occurred
Feb 11 15:46:44 phoenix kernel: [ 20.301260] scsi target6:0:1: Ending Domain Validation
Feb 11 15:46:44 phoenix kernel: [ 23.675229] sd 6:0:0:0: [sde] 143374744 512-byte logical blocks: (73.4 GB/68.4 GiB)
Feb 11 15:46:44 phoenix kernel: [ 23.675329] sd 6:0:1:0: [sdf] 143374744 512-byte logical blocks: (73.4 GB/68.4 GiB)
Feb 11 15:46:44 phoenix kernel: [ 23.676679] sd 6:0:0:0: [sde] Write Protect is off
Feb 11 15:46:44 phoenix kernel: [ 23.676682] sd 6:0:0:0: [sde] Mode Sense: ab 00 10 08
Feb 11 15:46:44 phoenix kernel: [ 23.676735] sd 6:0:1:0: [sdf] Write Protect is off
Feb 11 15:46:44 phoenix kernel: [ 23.676738] sd 6:0:1:0: [sdf] Mode Sense: ab 00 10 08
Feb 11 15:46:44 phoenix kernel: [ 23.678503] sd 6:0:0:0: [sde] Write cache: disabled, read cache: enabled, supports DPO and FUA
Feb 11 15:46:44 phoenix kernel: [ 23.678560] sd 6:0:1:0: [sdf] Write cache: enabled, read cache: enabled, supports DPO and FUA
Feb 11 15:46:44 phoenix kernel: [ 23.691875] random: init done crng
Feb 11 15:46:44 phoenix kernel: [ 23.691944] sdf: sdf1
Feb 11 15:46:44 phoenix kernel: [ 23.694961] sde: sde1
Feb 11 15:46:44 phoenix kernel: [ 23.697001] sd 6:0:1:0: [sdf] Attached SCSI disk
Feb 11 15:46:44 phoenix kernel: [ 23.699884] sd 6:0:0:0: [sde] Attached SCSI disk
Feb 11 15:46:44 phoenix kernel: [ 23.919498] md2: detected capacity change from 0 to 146676908032
Feb 11 15:46:44 phoenix kernel: [ 24.128211] raid6: mmxx1 gen() 1845 MB/s
Feb 11 15:46:44 phoenix kernel: [ 24.196212] raid6: mmxx2 gen() 2513 MB/s
Feb 11 15:46:44 phoenix kernel: [ 24.264208] raid6: sse1x1 gen() 1294 MB/s
Feb 11 15:46:44 phoenix kernel: [ 24.332229] raid6: sse1x2 gen() 1773 MB/s
Feb 11 15:46:44 phoenix kernel: [ 24.400206] raid6: sse2x1 gen() 2125 MB/s
Feb 11 15:46:44 phoenix kernel: [ 24.468193] raid6: sse2x1 xor() 1580 MB/s
Feb 11 15:46:44 phoenix kernel: [ 24.536206] raid6: sse2x2 gen() 2627 MB/s
Feb 11 15:46:44 phoenix kernel: [ 24.604199] raid6: sse2x2 xor() 1583 MB/s
Feb 11 15:46:44 phoenix kernel: [ 24.604202] raid6: using algorithm sse2x2 gen() 2627 MB/s
Feb 11 15:46:44 phoenix kernel: [ 24.604204] raid6: .... xor() 1583 MB/s, rmw enabled
Feb 11 15:46:44 phoenix kernel: [ 24.604207] raid6: using intx1 recovery algorithm
Feb 11 15:46:44 phoenix kernel: [ 24.608697] xor: measuring software checksum speed
Feb 11 15:46:44 phoenix kernel: [ 24.648193] pIII_sse : 3406.000 MB/sec
Feb 11 15:46:44 phoenix kernel: [ 24.688192] prefetch64-sse: 4242.000 MB/sec
Feb 11 15:46:44 phoenix kernel: [ 24.688196] xor: using function: prefetch64-sse (4242.000 MB/sec)
Feb 11 15:46:44 phoenix kernel: [ 24.691702] async_tx: api initialized (async)
Feb 11 15:46:44 phoenix kernel: [ 24.895843] device-mapper: uevent: version 1.0.3
Feb 11 15:46:44 phoenix kernel: [ 24.896072] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: dm-devel@redhat.com
Feb 11 15:46:44 phoenix kernel: [ 29.082510] PM: Image not found (code -22)
Feb 11 15:46:44 phoenix kernel: [ 29.386746] cryptd: max_cpu_qlen set to 1000
Feb 11 15:46:44 phoenix kernel: [ 29.685428] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null)
Feb 11 15:46:44 phoenix kernel: [ 33.049490] EXT4-fs (dm-1): re-mounted. Opts: errors=remount-ro
Feb 11 15:46:44 phoenix kernel: [ 34.095398] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input5
Feb 11 15:46:44 phoenix kernel: [ 34.095466] ACPI: Power Button [PWRF]
Feb 11 15:46:44 phoenix kernel: [ 34.113580] input: PC Speaker as /devices/platform/pcspkr/input/input6
Feb 11 15:46:44 phoenix kernel: [ 34.167564] version 39.2
Feb 11 15:46:44 phoenix kernel: [ 34.182882] ipmi device interface
Feb 11 15:46:44 phoenix kernel: [ 34.228310] IPMI System Interface driver.
Feb 11 15:46:44 phoenix kernel: [ 34.228378] ipmi_si dmi-ipmi-si.0: ipmi_platform: probing via SMBIOS
Feb 11 15:46:44 phoenix kernel: [ 34.228386] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Feb 11 15:46:44 phoenix kernel: [ 34.228390] ipmi_si: Adding SMBIOS-specified kcs state machine

- viva commented on April 7th 20 at 11:42
/var/log/syslog part 3

Feb 11 15:46:44 phoenix kernel: [ 34.228583] ipmi_si: Trying SMBIOS-specified kcs state machine at i/o address 0xca2, slave address 0x20, irq 0
Feb 11 15:46:44 phoenix kernel: [ 34.294606] EDAC e7xxx: tolm = f0000, remapbase = 100000, remaplimit = 10c000
Feb 11 15:46:44 phoenix kernel: [ 34.295101] EDAC MC0: Giving out device to module e7xxx_edac controller E7501: DEV 0000:00:00.0 (POLLED)
Feb 11 15:46:44 phoenix kernel: [ 34.295126] EDAC PCI0: Giving out device to module e7xxx_edac controller EDAC PCI controller: DEV 0000:00:00.0 (POLLED)
Feb 11 15:46:44 phoenix kernel: [ 34.373884] intel_rng: FWH not detected
Feb 11 15:46:44 phoenix kernel: [ 34.463062] sd 0:0:0:0: Attached scsi generic sg0 type 0
Feb 11 15:46:44 phoenix kernel: [ 34.463914] sd 1:0:0:0: Attached scsi generic sg1 type 0
Feb 11 15:46:44 phoenix kernel: [ 34.467477] sd 4:0:0:0: Attached scsi generic sg2 type 0
Feb 11 15:46:44 phoenix kernel: [ 34.468369] sd 5:0:0:0: Attached scsi generic sg3 type 0
Feb 11 15:46:44 phoenix kernel: [ 34.471635] sd 6:0:0:0: Attached scsi generic sg4 type 0
Feb 11 15:46:44 phoenix kernel: [ 34.474430] sd 6:0:1:0: Attached scsi generic sg5 type 0
Feb 11 15:46:44 phoenix kernel: [ 34.649778] ipmi_si dmi-ipmi-si.0: Found new BMC (man_id: 0x000157, prod_id: 0x001c, device ID's: 0x20)
Feb 11 15:46:44 phoenix kernel: [ 34.729733] parport_pc 00:07: reported by Plug and Play ACPI
Feb 11 15:46:44 phoenix kernel: [ 34.729942] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE]
Feb 11 15:46:44 phoenix kernel: [ 34.730161] iTCO_vendor_support: vendor-support=0
Feb 11 15:46:44 phoenix kernel: [ 34.745735] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
Feb 11 15:46:44 phoenix kernel: [ 34.745833] iTCO_wdt: unable to reset NO_REBOOT flag, device disabled by hardware/BIOS
Feb 11 15:46:44 phoenix kernel: [ 34.772324] ipmi_si dmi-ipmi-si.0: IPMI kcs interface initialized
Feb 11 15:46:44 phoenix kernel: [ 34.797655] ppdev: user-space parallel port driver
Feb 11 15:46:44 phoenix kernel: [ 35.747637] Adding 7811068k swap on /dev/mapper/lvgroot-lvlswap. Priority:-2 extents:1 across:7811068k FS
Feb 11 15:46:44 phoenix kernel: [ 36.757223] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Feb 11 15:46:44 phoenix kernel: [ 37.050537] EXT4-fs (dm-6): mounted filesystem with ordered data mode. Opts: (null)
Feb 11 15:46:44 phoenix kernel: [ 37.467832] audit: type=1400 audit(1581403604.520:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=424 comm="apparmor_parser"
Feb 11 15:46:44 phoenix kernel: [ 37.467856] audit: type=1400 audit(1581403604.520:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=424 comm="apparmor_parser"
Feb 11 15:46:44 phoenix kernel: [ 37.680972] IPv6: ADDRCONF(NETDEV_UP): enp1s4: link is not ready
Feb 11 15:46:44 phoenix kernel: [ 37.688664] e1000: enp1s4 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
Feb 11 15:46:44 phoenix kernel: [ 37.688833] IPv6: ADDRCONF(NETDEV_CHANGE): enp1s4: link becomes ready
Feb 11 15:46:44 phoenix cron[446]: (CRON) INFO (Running @reboot jobs)
Feb 11 15:46:44 phoenix systemd[1]: Started System Logging Service.
Feb 11 15:46:44 phoenix systemd[1]: Started Raise network interfaces.
Feb 11 15:46:44 phoenix systemd[1]: Started Login Service.
Feb 11 15:46:44 phoenix systemd[1]: Reached target Network.
Feb 11 15:46:45 phoenix systemd[1]: Starting OpenBSD Secure Shell server...
Feb 11 15:46:45 phoenix systemd[1]: Starting Permit User Sessions...
Feb 11 15:46:45 phoenix systemd[1]: Started Permit User Sessions.
Feb 11 15:46:45 phoenix systemd[1]: Started Getty on tty1.
Feb 11 15:46:45 phoenix systemd[1]: Reached target Login Prompts.
Feb 11 15:46:45 phoenix systemd[1]: Started OpenBSD Secure Shell server.
Feb 11 15:46:45 phoenix systemd[1]: Reached target Multi-User System.
Feb 11 15:46:45 phoenix systemd[1]: Reached target Graphical Interface.
Feb 11 15:46:45 phoenix systemd[1]: Starting Update UTMP about System Runlevel Changes...
Feb 11 15:46:45 phoenix systemd[1]: systemd-update-utmp-runlevel.service: Succeeded.
Feb 11 15:46:45 phoenix systemd[1]: Started Update UTMP about System Runlevel Changes.
Feb 11 15:46:45 phoenix systemd[1]: Startup finished in 31.043 s (kernel) + 7.377 s (userspace) = 38.420 s.
Feb 11 15:47:13 phoenix systemd[1]: systemd-fsckd.service: Succeeded.
Feb 11 15:49:16 phoenix systemd[1]: Created slice User Slice of UID 0.
Feb 11 15:49:16 phoenix systemd[1]: Starting User Runtime Directory /run/user/0...
Feb 11 15:49:16 phoenix systemd[1]: Started User Runtime Directory /run/user/0.
Feb 11 15:49:16 phoenix systemd[1]: Starting User Manager for UID 0...
Feb 11 15:49:16 phoenix systemd[469]: Reached target Timers.
Feb 11 15:49:16 phoenix systemd[469]: Reached target Sockets.
Feb 11 15:49:16 phoenix systemd[469]: Reached target Paths.
Feb 11 15:49:16 phoenix systemd[469]: Reached target Basic System.
Feb 11 15:49:16 phoenix systemd[469]: Reached target Default.
Feb 11 15:49:16 phoenix systemd[469]: Startup finished in 193ms.
Feb 11 15:49:16 phoenix systemd[1]: Started User Manager for UID 0.
Feb 11 15:49:16 phoenix systemd[1]: Started Session 1 of user root.
Feb 11 16:01:22 phoenix systemd[1]: Starting Cleanup of Temporary Directories...
Feb 11 16:01:22 phoenix systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
Feb 11 16:01:22 phoenix systemd[1]: Started Cleanup of Temporary Directories.
Feb 11 16:17:02 phoenix CRON[482]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Feb 11 16:33:37 phoenix systemd[1]: Created slice User Slice of UID 1000.
Feb 11 16:33:37 phoenix systemd[1]: Starting User Runtime Directory /run/user/1000...
Feb 11 16:33:37 phoenix systemd[1]: Started User Runtime Directory /run/user/1000.
Feb 11 16:33:37 phoenix systemd[1]: Starting User Manager for UID 1000...
Feb 11 16:33:37 phoenix systemd[489]: Reached target Timers.
Feb 11 16:33:37 phoenix systemd[489]: Reached target Paths.
Feb 11 16:33:37 phoenix systemd[489]: Reached target Sockets.
Feb 11 16:33:37 phoenix systemd[489]: Reached target Basic System.
Feb 11 16:33:37 phoenix systemd[489]: Reached target Default.
Feb 11 16:33:37 phoenix systemd[489]: Startup finished in 173ms.
Feb 11 16:33:37 phoenix systemd[1]: Started User Manager for UID 1000.
Feb 11 16:33:37 phoenix systemd[1]: Started Session 4 of user anton.
Feb 11 16:42:35 phoenix systemd[1]: Stopping Availability of block devices...
Feb 11 16:42:35 phoenix systemd[1]: Stopping event LVM activation on device 9:1...
Feb 11 16:42:35 phoenix systemd[1]: lvm2-lvmpolld.socket: Succeeded.
Feb 11 16:42:35 phoenix systemd[1]: Closed LVM2 poll daemon socket.
Feb 11 16:42:35 phoenix systemd[1]: Stopped target Graphical Interface.
Feb 11 16:42:35 phoenix systemd[1]: Stopping Session 4 of user anton.
Feb 11 16:42:35 phoenix systemd[1]: Stopped target Multi-User System.
Feb 11 16:42:35 phoenix systemd[1]: Stopping event LVM activation on device 9:0...

- viva commented on April 7th 20 at 11:45
and show the structure of their disks..
the command lsblk

after reboot - you always start emegrency mode ? - Karlie.Ki commented on April 7th 20 at 11:48
@mafalda.Ha,
after reboot - you always start emegrency mode ?

Not always... Only if you disconnect from the motherboard one of the disks of the array md1.

the results lsblk


NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465,8 G 0 disk
└─sda1 8:1 0 of 464.7 G 0 part
└─md0 9:0 0 464,6 G 0 raid1
├─lvgroot-lvlroot-real 253:0 0 372,5 G 0 lvm
│ ├─lvgroot-lvlroot 253:1 0 372,5 G 0 lvm /
│ └─lvgroot-snaphot_root 253:3 0 372,5 G 0 lvm
├─lvgroot-snaphot_root-cow 253:2 0 10G 0 lvm
│ └─lvgroot-snaphot_root 253:3 0 372,5 G 0 lvm
└─lvgroot-lvlswap 253:4 0 7,5 G 0 lvm [SWAP]
sdb 8:16 0 465,8 G 0 disk
└─sdb1 8:17 0 of 464.7 G 0 part
└─md0 9:0 0 464,6 G 0 raid1
├─lvgroot-lvlroot-real 253:0 0 372,5 G 0 lvm
│ ├─lvgroot-lvlroot 253:1 0 372,5 G 0 lvm /
│ └─lvgroot-snaphot_root 253:3 0 372,5 G 0 lvm
├─lvgroot-snaphot_root-cow 253:2 0 10G 0 lvm
│ └─lvgroot-snaphot_root 253:3 0 372,5 G 0 lvm
└─lvgroot-lvlswap 253:4 0 7,5 G 0 lvm [SWAP]
sdc 8:32 0 931,5 G 0 disk
└─sdc1 8:33 0 930,4 G 0 part
└─md1 9:1 0 930,3 G 0 raid1
└─lvgvirtualos-lvlvirtualos 253:6 0 930,3 G 0 lvm /virtualos
sdd 8:48 0 931,5 G 0 disk
└─sdd1 8:49 0 930,4 G 0 part
└─md1 9:1 0 930,3 G 0 raid1
└─lvgvirtualos-lvlvirtualos 253:6 0 930,3 G 0 lvm /virtualos
sde 8:64 0 68,4 G 0 disk
└─sde1 8:65 0 68,4 G 0 part
└─md2 9:2 0 136,6 G 0 raid0
└─lvgtempbackup-lvltempbackup 253:5 0 136,6 G 0 lvm /tempbackup
sdf 8:80 0 68,4 G 0 disk
└─sdf1 8:81 0 68,4 G 0 part
└─md2 9:2 0 136,6 G 0 raid0
└─lvgtempbackup-lvltempbackup 253:5 0 136,6 G 0 lvm /tempbackup
- viva commented on April 7th 20 at 11:51
Not always... Only if you disconnect from the motherboard one of the disks of the array md1.

this is most likely due to the fact that breaks lvm /virtualos
the system fails to mount and it falls out

and which team created the array? probably a mistake was made at this stage.
now the data in the array or is it important experiments for understanding?

what is the status at the moment? both drives connected? the array is assembled, or, as in fasting, one is disabled? - Karlie.Ki commented on April 7th 20 at 11:54
@mafalda.Ha,
this is most likely due to the fact that breaks lvm /virtualos
the system fails to mount and it falls out

Perhaps the only question is, what exactly is the error:(
and which team created the array?

The array was created during Debian installation (by the installer).
now the data in the array or is it important experiments for understanding?

No, it's not important. This is an experiment. That is, the server only at the stage of commissioning...
what is the status at the moment? both drives connected? the array is assembled, or, as in fasting, one is disabled?

At this point, it is possible to implement both state... - viva commented on April 7th 20 at 11:57
Then try all in the manual.
stop md1
mdadm --stop /dev/md1

The deleted superblocks to finally remove the information about the belonging to the array:

mdadm --zero-superblock /dev/sdc1
mdadm --zero-superblock /dev/sdd1

Delete the array
mdadm --remove /dev/md1


Create again:
mdadm --create --verbose /dev/md0 --level=1 --raid-devices=2 /dev/sdd1 /dev/sdc1


follow the timing:
watch "cat /proc/mdstat"

after the sync mount /dev/md1 and fill the data

to check that the array works mark one of the disks as failed:
mdadm --manage /dev/md1 --fail /dev/sdd1

then remove the disk from the array:
mdadm --manage /dev/md1 --remove /dev/sdd1

the pattern must remain to fly on one disk. the mount point must be available. you can throw the files or delete

Return the disk to the array:
mdadm --manage /dev/md1 --add /dev/sdd1


To check, you can stop the array and mount the partitions in different directories - the contents should be the same. but accurate anything that is not changing, otherwise the data in the array will be incorrect. when you switch it on or crumble, or will overwrite one of the drives.

About stop loading during a reboot and the mount point virtualos - before removing the disk physically remove it from the LVM. or, if this is an experiment - comment out /virtualos in fstab - the system tried to mount it. then the system will fall back normally. - Karlie.Ki commented on April 7th 20 at 12:00
@mafalda.Ha,
Well try to do a recreation of the array.

About stop loading during a reboot and the mount point virtualos - before removing the disk physically remove it from the LVM. or, if this is an experiment - comment out /virtualos in fstab - the system tried to mount it. then the system will fall back normally.


I imagine it as, in reality, the disk may simply fall off, of course being mounted and added to the array.
Just before this "arrogant" exclude disk from the array, the system booted in normal mode...
Even booting in safe mode (or how is called?). You can just make the partition active and add a clean (i.e. new) drive in return, the old and everything will work normally. But I'm not sure that's right?:(

In other words, what happens in my case is a normal situation?
Or all the same if you remove one of the disks of the RAID 1 array after a reboot in safe mode to move the system should not? - viva commented on April 7th 20 at 12:03
In other words, what happens in my case is a normal situation?

Definitely not.

@mafalda.Ha, I forgot to mention edit the /etc/mdadm/mdadm.conf and the associated with him update initramfs. - Gerda42 commented on April 7th 20 at 12:06
@Enid.Fay30,
forgot to mention editing /etc/mdadm/mdadm.conf and the associated with him update initramfs.

For debian I will not say. And ubuntu / Centos is to edit it not sure if it is not a system partition that needs to be downloaded

In other words, what happens in my case is a normal situation?

Definitely not.


Also agree that there is. In your case there are two problems:
1. With the array - if degradacii array in raid1 - with a live one of the disks - the system should boot normally
2. With mount point /virtualos. Why the server goes into "recovery mode" - Karlie.Ki commented on April 7th 20 at 12:09
@mafalda.Ha,
And ubuntu / Centos is to edit it not sure if it's not the system partition

Definitely if you do not want surprises when the system is restarted. (usually accompanied by auto-assembling the array, but with arbitrarily renaming somewhere md127) - Gerda42 commented on April 7th 20 at 12:12
@mafalda.Ha,
Produced recreation of the array on your instructions. After checked, the problem remained(
But there were a few additional questions:

1.
after the sync mount /dev/md1 and fill the data

You mean the LVM? The fact that I have automatically mounted...
All the same, or before removing him from the mount?

2. You say:
to check that the array works mark one of the disks as failed:

mdadm --manage /dev/md1 --fail /dev/sdd1

then remove the disk from the array:

mdadm --manage /dev/md1 --remove /dev/sdd1

the pattern must remain to fly on one disk. the mount point must be available. you can throw the files or delete

Return the disk to the array:

mdadm --manage /dev/md1 --add /dev/sdd1

If you do so, then I've would've all wound up... the Question is that if a disk in a brazen disable and after reboot the OS should boot in normal mode or not? Maybe just in this case, it is safe and to boot, the LVM that I'm not mounted, etc ...

3.
(usually accompanied by auto-assembling the array, but with arbitrarily renaming somewhere md127)

Yes, really jumped into md127 :)))

In General, now I am trying to do this:
1. From the mounted LVM
2. Removed local volume in LVM
3. Removed the array
4. Zeroed superblocks
5. For comment on md1 in /etc/mdadm/mdadm.conf
6. Updated the initramfs with the command:
update-initramfs-u
7. Created array

After the sync, create all the LVM and mounted back.
If everything remains as it was, probably I will use as is... At least, the data in this case, do not get lost and if you can be on this server is hot to properly change the drives in the array(and it still needs to be verified), then I will use that. Most importantly, it turns out, the time to notice the drive failure and prevent restarting, otherwise ssh will be lost:( - viva commented on April 7th 20 at 12:15
I created a new array. I waited and when it syncs. As a result, in mdstat seems fine.
Then I rebooted and now:
5e4518800c07b599841986.jpeg

It seems that initramfs that something was wrong or needed before rebooting md1 in /etc/mdadm/mdadm.conf to uncomment.

I'll try to do it all again And install the OS on a completely blank discs. And check how will such a configuration work array md1... - viva commented on April 7th 20 at 12:18
on screen he swears on md0....
alternatively, boot into Rescue mode mode with a boot disk. and run update-initrumfs
about broken mount points - can be in fstab to prescribe the nofail mount option - then the system will stop loading if the mount point is corrupted, and just propostition stage and gets loaded - Karlie.Ki commented on April 7th 20 at 12:21
on screen he swears on md0....

Yes, I see, but it is not clear what happened to him, because I did not touch upon.

Generally, in the end, I completely reinstalled the system on a formatted hard disk but the problem remains, if you remove one of the disks in the second array, the system ceases to boot.
Have to use at least the data and the array can be activated and restore, only what if you lose the disk and reboot does not work (SSH - viva commented on April 7th 20 at 12:24
April 7th 20 at 10:59
Solution
before creating the array, I removed the superblocks on the disks?

Eco you shakes.
Do not delete the superblocks, this is the heart of ext4, for example.
On screen - the regular output of mdadm with information about the blocks, everything is fine.
I mean, before you can create an array... don't you need to still clean your hard disk to carry out the removal of superblocks? - viva commented on April 7th 20 at 11:02
@Karen_Spinka, why? Format and forth. - albert.Kulas45 commented on April 7th 20 at 11:05
@phyllis.Webe, Then did the right thing:( So the reason is different:( - viva commented on April 7th 20 at 11:08

Find more questions by tags LinuxDebianRAIDArrays