You are not logged in.

#1 2021-10-05 12:43:42

redshoe
Member
Registered: 2015-12-16
Posts: 99

[Solved] RAID becomes inactive after every reboot

I am in the process of building (not rebuilding) a RAID, and I have meticulously followed the mdadm part of the Arch Linux RAID wikipedia page. For your info, I have six 4 TB drives that I would like to build it as RAID5. So, this is what I did

mdadm --create --verbose --level=5 --metadata=1.2 --raid-devices=5 /dev/md/bighdd /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1 /dev/sdf1 --spare-devices=1 /dev/sda1

and the output seems correct

mdadm: layout defaults to left-symmetric
mdadm: chunk size defaults to 512K
mdadm: size set to 3906885120K
mdadm: automatically enabling write-intent bitmap on large array
mdadm: array /dev/md/bighdd started.

Okay cool. Now when I do

cat /proc/mdstat

I get

md126 : active raid5 sdf1[6] sda1[5](S) sde1[3] sdd1[2] sdc1[1] sdb1[0]
      15627540480 blocks super 1.2 level 5, 512k chunk, algorithm 2 [5/4] [UUUU_]
      [>....................]  recovery =  0.0% (1812688/3906885120) finish=430.8min speed=151057K/sec
      bitmap: 0/30 pages [0KB], 65536KB chunk

md127 : active raid0 nvme1n1p1[1] nvme0n1p1[0]
      976506880 blocks super 1.2 128k chunks

So, it is working as intended. After this, I did update the mdadm.conf file, assembled the array and formatted the RAID filesystem

mdadm --detail --scan >> /etc/mdadm.conf
mdadm --assemble --scan
mkfs.ext4 -v -b 4096 -E stride=128,stripe-width=640 /dev/md126

Now when I reboot, I get

Personalities : [raid0] 
md126 : inactive sdc1[1] sdf1[6] sdd1[2] sdb1[0] sda1[5](S) sde1[3]
      23441312685 blocks super 1.2
       
md127 : active raid0 nvme1n1p1[1] nvme0n1p1[0]
      976506880 blocks super 1.2 128k chunks
      
unused devices: <none>

And I thought I did something wrong during the initial steps, but I checked, double triple checked and this keeps happening.... I don't know what to do now.. Help anyone...?

Last edited by redshoe (2021-10-05 17:22:00)

Offline

#2 2021-10-05 13:01:32

frostschutz
Member
Registered: 2013-11-15
Posts: 1,089

Re: [Solved] RAID becomes inactive after every reboot

do you have dmesg of assembly process?

Offline

#3 2021-10-05 13:05:56

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 9,583

Re: [Solved] RAID becomes inactive after every reboot

please post /etc/mdadm.conf contents .


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
Did you use the guided installer ? If yes, I can't help you.

(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#4 2021-10-05 16:10:03

redshoe
Member
Registered: 2015-12-16
Posts: 99

Re: [Solved] RAID becomes inactive after every reboot

Output of /etc/mdadm.conf

# mdadm configuration file
#
# mdadm will function properly without the use of a configuration file,
# but this file is useful for keeping track of arrays and member disks.
# In general, a mdadm.conf file is created, and updated, after arrays
# are created. This is the opposite behavior of /etc/raidtab which is
# created prior to array construction.
#
#
# the config file takes two types of lines:
#
#	DEVICE lines specify a list of devices of where to look for
#	  potential member disks
#
#	ARRAY lines specify information about how to identify arrays so
#	  so that they can be activated
#


# You can have more than one device line and use wild cards. The first 
# example includes SCSI the first partition of SCSI disks /dev/sdb,
# /dev/sdc, /dev/sdd, /dev/sdj, /dev/sdk, and /dev/sdl. The second 
# line looks for array slices on IDE disks.
#
#DEVICE /dev/sd[bcdjkl]1
#DEVICE /dev/hda1 /dev/hdb1
#
# The designation "partitions" will scan all partitions found in
# /proc/partitions
DEVICE partitions


# ARRAY lines specify an array to assemble and a method of identification.
# Arrays can currently be identified by using a UUID, superblock minor number,
# or a listing of devices.
#
#	super-minor is usually the minor number of the metadevice
#	UUID is the Universally Unique Identifier for the array
# Each can be obtained using
#
# 	mdadm -D <md>
#
# To capture the UUIDs for all your RAID arrays to this file, run these:
#    to get a list of running arrays:
#    # mdadm -D --scan >>/etc/mdadm.conf
#    to get a list from superblocks:
#    # mdadm -E --scan >>/etc/mdadm.conf
#
#ARRAY /dev/md0 UUID=3aaa0122:29827cfa:5331ad66:ca767371
#ARRAY /dev/md1 super-minor=1
#ARRAY /dev/md2 devices=/dev/hda1,/dev/hdb1
#
# ARRAY lines can also specify a "spare-group" for each array.  mdadm --monitor
# will then move a spare between arrays in a spare-group if one array has a
# failed drive but no spare
#ARRAY /dev/md4 uuid=b23f3c6d:aec43a9f:fd65db85:369432df spare-group=group1
#ARRAY /dev/md5 uuid=19464854:03f71b1b:e0df2edd:246cc977 spare-group=group1
#


# When used in --follow (aka --monitor) mode, mdadm needs a
# mail address and/or a program.  To start mdadm's monitor mode, enable
# mdadm.service in systemd.
#
# If the lines are not found, mdadm will exit quietly
#MAILADDR root@mydomain.tld
#PROGRAM /usr/sbin/handle-mdadm-events
#
ARRAY /dev/md/archiso:ssdraid metadata=1.2 name=archiso:ssdraid UUID=6d84a226:b2e4e773:f80df9a8:328715b8
ARRAY /dev/md/bighdd metadata=1.2 spares=2 name=Orangke:bighdd UUID=78028620:89c38edb:2a363cc9:772992d9

Offline

#5 2021-10-05 16:10:45

redshoe
Member
Registered: 2015-12-16
Posts: 99

Re: [Solved] RAID becomes inactive after every reboot

frostschutz wrote:

do you have dmesg of assembly process?

Um... should I start from the beginning and get dmesg..?

Offline

#6 2021-10-05 16:30:44

redshoe
Member
Registered: 2015-12-16
Posts: 99

Re: [Solved] RAID becomes inactive after every reboot

Here is the dmesg after

mdadm --stop /dev/md126
mdadm --assemble --scan
...
[    1.734332] systemd[1]: Mounted FUSE Control File System.
[    1.736433] systemd[1]: Finished Load/Save Random Seed.
[    1.736798] audit: type=1130 audit(1633437774.517:8): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-random-seed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[    1.736832] systemd[1]: Condition check resulted in First Boot Complete being skipped.
[    1.743823] systemd[1]: Finished Create Static Device Nodes in /dev.
[    1.744175] audit: type=1130 audit(1633437774.524:9): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[    1.744203] systemd[1]: Reached target Preparation for Local File Systems.
[    1.744554] systemd[1]: Condition check resulted in Virtual Machine and Container Storage (Compatibility) being skipped.
[    1.745280] audit: type=1334 audit(1633437774.524:10): prog-id=14 op=LOAD
[    1.745778] systemd[1]: Starting Rule-based Manager for Device Events and Files...
[    1.760541] systemd[1]: Started Rule-based Manager for Device Events and Files.
[    1.766858] usb 6-1: new SuperSpeed USB device number 2 using xhci_hcd
[    1.767628] systemd[1]: Started Journal Service.
[    1.771210] systemd-journald[432]: Received client request to flush runtime journal.
[    1.783878] usb 6-1: New USB device found, idVendor=0781, idProduct=5583, bcdDevice= 1.00
[    1.783881] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    1.783882] usb 6-1: Product:  SanDisk 3.2Gen1
[    1.783884] usb 6-1: Manufacturer:  USB
[    1.783885] usb 6-1: SerialNumber: 04017b07eab4c3da0738b7f587f4ed874505a465a60f620eec822e1aebb37b4a84c50000000000000000000038357773008a6d188355810770aa9b92
[    1.793875] usb-storage 6-1:1.0: USB Mass Storage device detected
[    1.793963] scsi host10: usb-storage 6-1:1.0
[    1.794027] usbcore: registered new interface driver usb-storage
[    1.795562] usbcore: registered new interface driver uas
[    1.824155] acpi_cpufreq: overriding BIOS provided _PSD data
[    1.840246] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0x1B, rev-id 22)
[    1.844550] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling instead
[    1.848717] MACsec IEEE 802.1AE
[    1.859009] piix4_smbus 0000:00:14.0: SMBus Host Controller at 0xb00, revision 0
[    1.859013] piix4_smbus 0000:00:14.0: Using register 0x02 for SMBus port selection
[    1.859095] piix4_smbus 0000:00:14.0: Auxiliary SMBus Host Controller at 0xb20
[    1.860316] sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver
[    1.860667] sp5100-tco sp5100-tco: Using 0xfeb00000 for watchdog MMIO address
[    1.860740] sp5100-tco sp5100-tco: initialized. heartbeat=60 sec (nowayout=0)
[    1.893621] ccp 0000:24:00.1: enabling device (0000 -> 0002)
[    1.894454] ccp 0000:24:00.1: ccp enabled
[    1.935642] input: PC Speaker as /devices/platform/pcspkr/input/input2
[    1.939067] Linux agpgart interface v0.103
[    1.948629] RAPL PMU: API unit is 2^-32 Joules, 1 fixed counters, 163840 ms ovfl timer
[    1.948634] RAPL PMU: hw unit of domain package 2^-16 Joules
[    1.957344] cryptd: max_cpu_qlen set to 1000
[    1.995171] zram0: detected capacity change from 0 to 32933888
[    1.995233] zram1: detected capacity change from 0 to 32933888
[    1.995302] zram2: detected capacity change from 0 to 32933888
[    1.995383] zram3: detected capacity change from 0 to 32933888
[    2.007122] Adding 16466940k swap on /dev/zram0.  Priority:100 extents:1 across:16466940k SSFS
[    2.007861] Adding 16466940k swap on /dev/zram1.  Priority:100 extents:1 across:16466940k SSFS
[    2.009387] Adding 16466940k swap on /dev/zram2.  Priority:100 extents:1 across:16466940k SSFS
[    2.010967] Adding 16466940k swap on /dev/zram3.  Priority:100 extents:1 across:16466940k SSFS
[    2.033822] AVX2 version of gcm_enc/dec engaged.
[    2.033876] AES CTR mode by8 optimization enabled
[    2.058745] snd_hda_intel 0000:61:00.1: enabling device (0000 -> 0002)
[    2.060265] snd_hda_intel 0000:61:00.1: Force to non-snoop mode
[    2.086460] usb 3-1: New USB device found, idVendor=17aa, idProduct=104d, bcdDevice= 0.10
[    2.086465] usb 3-1: New USB device strings: Mfr=3, Product=1, SerialNumber=0
[    2.086466] usb 3-1: Product: Realtek USB Audio Front
[    2.086467] usb 3-1: Manufacturer: Generic
[    2.172711] input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci0000:60/0000:60:03.1/0000:61:00.1/sound/card0/input3
[    2.172746] input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci0000:60/0000:60:03.1/0000:61:00.1/sound/card0/input4
[    2.172773] input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci0000:60/0000:60:03.1/0000:61:00.1/sound/card0/input5
[    2.172798] input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci0000:60/0000:60:03.1/0000:61:00.1/sound/card0/input6
[    2.172824] input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci0000:60/0000:60:03.1/0000:61:00.1/sound/card0/input7
[    2.176776] kvm: Nested Virtualization enabled
[    2.176778] SVM: kvm: Nested Paging enabled
[    2.176779] SEV supported: 509 ASIDs
[    2.176886] SVM: Virtual VMLOAD VMSAVE supported
[    2.176886] SVM: Virtual GIF supported
[    2.246696] usb 3-6: new high-speed USB device number 3 using xhci_hcd
[    2.301651] MCE: In-kernel MCE decoding enabled.
[    2.304374] EDAC amd64: MCT channel count: 2
[    2.304427] EDAC MC0: Giving out device to module amd64_edac controller F17h_M30h: DEV 0000:00:18.3 (INTERRUPT)
[    2.304429] EDAC amd64: F17h_M30h detected (node 0).
[    2.304432] EDAC MC: UMC0 chip selects:
[    2.304433] EDAC amd64: MC: 0:     0MB 1:     0MB
[    2.304434] EDAC amd64: MC: 2:     0MB 3:     0MB
[    2.304437] EDAC MC: UMC1 chip selects:
[    2.304437] EDAC amd64: MC: 0:     0MB 1:     0MB
[    2.304438] EDAC amd64: MC: 2:     0MB 3:     0MB
[    2.304441] EDAC MC: UMC2 chip selects:
[    2.304441] EDAC amd64: MC: 0: 32768MB 1: 32768MB
[    2.304442] EDAC amd64: MC: 2:     0MB 3:     0MB
[    2.304445] EDAC MC: UMC3 chip selects:
[    2.304445] EDAC amd64: MC: 0: 32768MB 1: 32768MB
[    2.304446] EDAC amd64: MC: 2:     0MB 3:     0MB
[    2.304449] EDAC MC: UMC4 chip selects:
[    2.304449] EDAC amd64: MC: 0:     0MB 1:     0MB
[    2.304450] EDAC amd64: MC: 2:     0MB 3:     0MB
[    2.304452] EDAC MC: UMC5 chip selects:
[    2.304453] EDAC amd64: MC: 0:     0MB 1:     0MB
[    2.304453] EDAC amd64: MC: 2:     0MB 3:     0MB
[    2.304456] EDAC MC: UMC6 chip selects:
[    2.304456] EDAC amd64: MC: 0:     0MB 1:     0MB
[    2.304457] EDAC amd64: MC: 2:     0MB 3:     0MB
[    2.304460] EDAC MC: UMC7 chip selects:
[    2.304460] EDAC amd64: MC: 0:     0MB 1:     0MB
[    2.304461] EDAC amd64: MC: 2:     0MB 3:     0MB
[    2.304461] EDAC amd64: using x16 syndromes.
[    2.304466] EDAC PCI0: Giving out device to module amd64_edac controller EDAC PCI controller: DEV 0000:00:18.0 (POLLED)
[    2.304467] AMD64 EDAC driver v3.5.0
[    2.308821] [drm] amdgpu kernel modesetting enabled.
[    2.309009] amdgpu: Ignoring ACPI CRAT on non-APU system
[    2.309013] amdgpu: Virtual CRAT table created for CPU
[    2.309021] amdgpu: Topology: Add CPU node
[    2.309113] checking generic (14010000000 420000) vs hw (14010000000 10000000)
[    2.309115] fb0: switching to amdgpudrmfb from EFI VGA
[    2.309179] Console: switching to colour dummy device 80x25
[    2.309205] amdgpu 0000:61:00.0: vgaarb: deactivate vga console
[    2.309262] amdgpu 0000:61:00.0: enabling device (0006 -> 0007)
[    2.309357] [drm] initializing kernel modesetting (POLARIS12 0x1002:0x6981 0x17AA:0x104C 0x10).
[    2.309360] amdgpu 0000:61:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported
[    2.309368] [drm] register mmio base: 0xCC000000
[    2.309369] [drm] register mmio size: 262144
[    2.309377] [drm] add ip block number 0 <vi_common>
[    2.309378] [drm] add ip block number 1 <gmc_v8_0>
[    2.309379] [drm] add ip block number 2 <tonga_ih>
[    2.309380] [drm] add ip block number 3 <gfx_v8_0>
[    2.309381] [drm] add ip block number 4 <sdma_v3_0>
[    2.309382] [drm] add ip block number 5 <powerplay>
[    2.309382] [drm] add ip block number 6 <dm>
[    2.309383] [drm] add ip block number 7 <uvd_v6_0>
[    2.309384] [drm] add ip block number 8 <vce_v3_0>
[    2.309404] amdgpu 0000:61:00.0: amdgpu: Fetched VBIOS from VFCT
[    2.309406] amdgpu: ATOM BIOS: 113-D0155500-100
[    2.309423] [drm] UVD is enabled in VM mode
[    2.309424] [drm] UVD ENC is enabled in VM mode
[    2.309426] [drm] VCE enabled in VM mode
[    2.309446] [drm] vm size is 512 GB, 2 levels, block size is 10-bit, fragment size is 9-bit
[    2.309760] intel_rapl_common: Found RAPL domain package
[    2.309762] intel_rapl_common: Found RAPL domain core
[    2.310317] amdgpu 0000:61:00.0: BAR 2: releasing [mem 0x14020000000-0x140201fffff 64bit pref]
[    2.310320] amdgpu 0000:61:00.0: BAR 0: releasing [mem 0x14010000000-0x1401fffffff 64bit pref]
[    2.310340] pcieport 0000:60:03.1: BAR 15: releasing [mem 0x14010000000-0x140201fffff 64bit pref]
[    2.310345] pcieport 0000:60:03.1: BAR 15: assigned [mem 0x10080000000-0x101ffffffff 64bit pref]
[    2.310347] amdgpu 0000:61:00.0: BAR 0: assigned [mem 0x10100000000-0x101ffffffff 64bit pref]
[    2.310355] amdgpu 0000:61:00.0: BAR 2: assigned [mem 0x10080000000-0x100801fffff 64bit pref]
[    2.310363] pcieport 0000:60:03.1: PCI bridge to [bus 61]
[    2.310365] pcieport 0000:60:03.1:   bridge window [io  0xf000-0xffff]
[    2.310368] pcieport 0000:60:03.1:   bridge window [mem 0xcc000000-0xcc0fffff]
[    2.310370] pcieport 0000:60:03.1:   bridge window [mem 0x10080000000-0x101ffffffff 64bit pref]
[    2.310379] amdgpu 0000:61:00.0: amdgpu: VRAM: 4096M 0x000000F400000000 - 0x000000F4FFFFFFFF (4096M used)
[    2.310380] amdgpu 0000:61:00.0: amdgpu: GART: 256M 0x000000FF00000000 - 0x000000FF0FFFFFFF
[    2.310386] [drm] Detected VRAM RAM=4096M, BAR=4096M
[    2.310387] [drm] RAM width 128bits GDDR5
[    2.310412] [drm] amdgpu: 4096M of VRAM memory ready
[    2.310413] [drm] amdgpu: 4096M of GTT memory ready.
[    2.310416] [drm] GART: num cpu pages 65536, num gpu pages 65536
[    2.312761] [drm] PCIE GART of 256M enabled (table at 0x000000F400401000).
[    2.313259] [drm] Chained IB support enabled!
[    2.315459] amdgpu: hwmgr_sw_init smu backed is polaris10_smu
[    2.315994] [drm] Found UVD firmware Version: 1.130 Family ID: 16
[    2.316992] [drm] Found VCE firmware Version: 53.26 Binary ID: 3
[    2.413206] [drm] Display Core initialized with v3.2.141!
[    2.423422] snd_hda_intel 0000:61:00.1: bound 0000:61:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
[    2.493353] [drm] UVD and UVD ENC initialized successfully.
[    2.528421] atlantic 0000:01:00.0 enp1s0: renamed from eth0
[    2.594264] [drm] VCE initialized successfully.
[    2.595703] kfd kfd: amdgpu: Allocated 3969056 bytes on gart
[    2.595900] amdgpu: SRAT table not found
[    2.595901] amdgpu: Virtual CRAT table created for GPU
[    2.595933] amdgpu: Topology: Add dGPU node [0x6981:0x1002]
[    2.595934] kfd kfd: amdgpu: added device 1002:6981
[    2.595936] amdgpu 0000:61:00.0: amdgpu: SE 2, SH per SE 1, CU per SH 5, active_cu_number 10
[    2.598433] [drm] fb mappable at 0x10100931000
[    2.598434] [drm] vram apper at 0x10100000000
[    2.598435] [drm] size 4325376
[    2.598435] [drm] fb depth is 24
[    2.598435] [drm]    pitch is 5632
[    2.598481] fbcon: amdgpu (fb0) is primary device
[    2.678717] usb 3-6: New USB device found, idVendor=17aa, idProduct=1046, bcdDevice= 0.10
[    2.678721] usb 3-6: New USB device strings: Mfr=3, Product=1, SerialNumber=0
[    2.678723] usb 3-6: Product: Realtek USB Audio Rear
[    2.678725] usb 3-6: Manufacturer: Generic
[    2.722727] Console: switching to colour frame buffer device 170x48
[    2.727522] mc: Linux media interface: v0.10
[    2.741376] amdgpu 0000:61:00.0: [drm] fb0: amdgpu frame buffer device
[    2.781538] amdgpu 0000:61:00.0: amdgpu: Using BACO for runtime pm
[    2.782070] [drm] Initialized amdgpu 3.42.0 20150101 for 0000:61:00.0 on minor 0
[    2.807299] scsi 10:0:0:0: Direct-Access      USB      SanDisk 3.2Gen1 1.00 PQ: 0 ANSI: 6
[    2.807852] sd 10:0:0:0: [sdg] 120176640 512-byte logical blocks: (61.5 GB/57.3 GiB)
[    2.808064] sd 10:0:0:0: [sdg] Write Protect is off
[    2.808066] sd 10:0:0:0: [sdg] Mode Sense: 43 00 00 00
[    2.808270] sd 10:0:0:0: [sdg] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[    2.859612]  sdg: sdg1
[    2.861554] sd 10:0:0:0: [sdg] Attached SCSI removable disk
[    2.931808] FAT-fs (sdg1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[    3.365450] usbcore: registered new interface driver snd-usb-audio
[    3.840964] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[    7.893800] atlantic 0000:01:00.0 enp1s0: atlantic: link change old 0 new 1000
[    7.893902] IPv6: ADDRCONF(NETDEV_CHANGE): enp1s0: link becomes ready
[    7.896034] br0: port 1(enp1s0) entered blocking state
[    7.896039] br0: port 1(enp1s0) entered disabled state
[    7.896161] device enp1s0 entered promiscuous mode
[    7.896206] kauditd_printk_skb: 31 callbacks suppressed
[    7.896210] audit: type=1700 audit(1633437780.677:42): dev=enp1s0 prom=256 old_prom=0 auid=4294967295 uid=0 gid=0 ses=4294967295
[    7.896328] br0: port 1(enp1s0) entered blocking state
[    7.896332] br0: port 1(enp1s0) entered forwarding state
[    7.896364] audit: type=1300 audit(1633437780.677:42): arch=c000003e syscall=46 success=yes exit=40 a0=c a1=7fff36292280 a2=0 a3=0 items=0 ppid=1 pid=622 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="NetworkManager" exe="/usr/bin/NetworkManager" key=(null)
[    7.896368] audit: type=1327 audit(1633437780.677:42): proctitle=2F7573722F62696E2F4E6574776F726B4D616E61676572002D2D6E6F2D6461656D6F6E
[    7.897287] IPv6: ADDRCONF(NETDEV_CHANGE): br0: link becomes ready
[    7.898584] audit: type=1334 audit(1633437780.677:43): prog-id=25 op=LOAD
[    7.898591] audit: type=1300 audit(1633437780.677:43): arch=c000003e syscall=321 success=yes exit=23 a0=5 a1=7fff362929c0 a2=78 a3=7fff362929c0 items=0 ppid=1 pid=622 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="NetworkManager" exe="/usr/bin/NetworkManager" key=(null)
[    7.898595] audit: type=1327 audit(1633437780.677:43): proctitle=2F7573722F62696E2F4E6574776F726B4D616E61676572002D2D6E6F2D6461656D6F6E
[   13.006560] audit: type=1131 audit(1633437785.787:44): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   22.858703] audit: type=1101 audit(1633437795.637:45): pid=687 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_permit,pam_time acct="orangke" exe="/usr/bin/sshd" hostname=192.168.1.4 addr=192.168.1.4 terminal=ssh res=success'
[   22.859516] audit: type=1103 audit(1633437795.637:46): pid=687 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_shells,pam_faillock,pam_permit,pam_env,pam_faillock acct="orangke" exe="/usr/bin/sshd" hostname=192.168.1.4 addr=192.168.1.4 terminal=ssh res=success'
[   22.859549] audit: type=1006 audit(1633437795.637:47): pid=687 uid=0 old-auid=4294967295 auid=1000 tty=(none) old-ses=4294967295 ses=1 res=1
[   22.859553] audit: type=1300 audit(1633437795.637:47): arch=c000003e syscall=1 success=yes exit=4 a0=3 a1=7ffe85b59a50 a2=4 a3=3e8 items=0 ppid=630 pid=687 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=1 comm="sshd" exe="/usr/bin/sshd" key=(null)
[   22.859556] audit: type=1327 audit(1633437795.637:47): proctitle=737368643A206F72616E676B65205B707269765D
[   22.868164] audit: type=1130 audit(1633437795.647:48): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1000 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   22.871948] audit: type=1101 audit(1633437795.651:49): pid=690 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_permit,pam_time acct="orangke" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   22.871955] audit: type=1103 audit(1633437795.651:50): pid=690 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=? acct="orangke" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
[   22.871981] audit: type=1006 audit(1633437795.651:51): pid=690 uid=0 old-auid=4294967295 auid=1000 tty=(none) old-ses=4294967295 ses=2 res=1
[   22.871984] audit: type=1300 audit(1633437795.651:51): arch=c000003e syscall=1 success=yes exit=4 a0=9 a1=7ffc1a5b2450 a2=4 a3=3e8 items=0 ppid=1 pid=690 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=2 comm="(systemd)" exe="/usr/lib/systemd/systemd" key=(null)
[   33.075854] kauditd_printk_skb: 9 callbacks suppressed
[   33.075857] audit: type=1131 audit(1633437805.857:58): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   33.177566] audit: type=1334 audit(1633437805.961:59): prog-id=24 op=UNLOAD
[   33.177575] audit: type=1334 audit(1633437805.961:60): prog-id=23 op=UNLOAD
[   33.177579] audit: type=1334 audit(1633437805.961:61): prog-id=22 op=UNLOAD
[  123.134130] audit: type=1131 audit(1633437895.914:62): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=libvirtd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  901.433646] audit: type=1130 audit(1633438674.214:63): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  901.433656] audit: type=1131 audit(1633438674.214:64): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 6065.714376] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 514
[ 6065.714380] {1}[Hardware Error]: It has been corrected by h/w and requires no further action
[ 6065.714381] {1}[Hardware Error]: event severity: corrected
[ 6065.714382] {1}[Hardware Error]:  Error 0, type: corrected
[ 6065.714382] {1}[Hardware Error]:  fru_text: PcieError
[ 6065.714383] {1}[Hardware Error]:   section_type: PCIe error
[ 6065.714384] {1}[Hardware Error]:   port_type: 0, PCIe end point
[ 6065.714384] {1}[Hardware Error]:   version: 0.2
[ 6065.714385] {1}[Hardware Error]:   command: 0x0407, status: 0x0010
[ 6065.714386] {1}[Hardware Error]:   device_id: 0000:01:00.0
[ 6065.714387] {1}[Hardware Error]:   slot: 0
[ 6065.714387] {1}[Hardware Error]:   secondary_bus: 0x00
[ 6065.714387] {1}[Hardware Error]:   vendor_id: 0x1d6a, device_id: 0x07b1
[ 6065.714388] {1}[Hardware Error]:   class_code: 020000
[ 6065.714389] {1}[Hardware Error]:   bridge: secondary_status: 0x0000, control: 0x0000
[ 6065.714434] atlantic 0000:01:00.0: AER: aer_status: 0x00002001, aer_mask: 0x00000000
[ 6065.714481] atlantic 0000:01:00.0:    [ 0] RxErr                  (First)
[ 6065.714482] atlantic 0000:01:00.0:    [13] NonFatalErr           
[ 6065.714483] atlantic 0000:01:00.0: AER: aer_layer=Physical Layer, aer_agent=Receiver ID
[13367.389133] audit: type=1100 audit(1633451140.170:65): pid=822 uid=1000 auid=1000 ses=1 msg='op=PAM:authentication grantors=pam_faillock,pam_permit,pam_faillock acct="orangke" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[13367.390195] audit: type=1101 audit(1633451140.170:66): pid=822 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="orangke" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[13367.390667] audit: type=1110 audit(1633451140.170:67): pid=822 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[13367.390727] audit: type=1105 audit(1633451140.170:68): pid=822 uid=1000 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[13367.398448] audit: type=1106 audit(1633451140.177:69): pid=822 uid=1000 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[13367.398507] audit: type=1104 audit(1633451140.180:70): pid=822 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[13430.893909] audit: type=1101 audit(1633451203.673:71): pid=826 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="orangke" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[13430.894398] audit: type=1110 audit(1633451203.673:72): pid=826 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[13430.894469] audit: type=1105 audit(1633451203.673:73): pid=826 uid=1000 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[13430.900003] audit: type=1106 audit(1633451203.680:74): pid=826 uid=1000 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[13430.900011] audit: type=1104 audit(1633451203.680:75): pid=826 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[13523.498347] audit: type=1101 audit(1633451296.277:76): pid=831 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="orangke" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[13523.498986] audit: type=1110 audit(1633451296.280:77): pid=831 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[13523.499068] audit: type=1105 audit(1633451296.280:78): pid=831 uid=1000 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[13523.500382] md: md126 stopped.
[13523.699765] audit: type=1106 audit(1633451296.480:79): pid=831 uid=1000 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[13523.699839] audit: type=1104 audit(1633451296.480:80): pid=831 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[13555.996180] audit: type=1101 audit(1633451328.777:81): pid=837 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="orangke" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[13555.996982] audit: type=1110 audit(1633451328.777:82): pid=837 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[13555.997128] audit: type=1105 audit(1633451328.777:83): pid=837 uid=1000 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[13556.181917] md: md126 stopped.
[13556.189002] raid6: skip pq benchmark and using algorithm avx2x4
[13556.189005] raid6: using avx2x2 recovery algorithm
[13556.190044] xor: automatically using best checksumming function   avx       
[13556.191057] async_tx: api initialized (async)
[13556.200294] md/raid:md126: device sdb1 operational as raid disk 0
[13556.200298] md/raid:md126: device sde1 operational as raid disk 3
[13556.200299] md/raid:md126: device sdd1 operational as raid disk 2
[13556.200301] md/raid:md126: device sdc1 operational as raid disk 1
[13556.200983] md/raid:md126: raid level 5 active with 4 out of 5 devices, algorithm 2
[13556.250242] md126: detected capacity change from 0 to 31255080960
[13556.250353] md: recovery of RAID array md126
[13557.078966] audit: type=1130 audit(1633451329.860:84): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=mdmonitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[13557.079806] audit: type=1131 audit(1633451329.860:85): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=mdmonitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
[13557.378390] audit: type=1106 audit(1633451330.157:86): pid=837 uid=1000 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[13557.378428] audit: type=1104 audit(1633451330.157:87): pid=837 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[13564.248540] audit: type=1101 audit(1633451337.030:88): pid=865 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="orangke" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[13564.249283] audit: type=1110 audit(1633451337.030:89): pid=865 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[13564.249392] audit: type=1105 audit(1633451337.030:90): pid=865 uid=1000 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[13564.255806] audit: type=1106 audit(1633451337.037:91): pid=865 uid=1000 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[13564.255834] audit: type=1104 audit(1633451337.037:92): pid=865 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[13600.367988] audit: type=1101 audit(1633451373.147:93): pid=868 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="orangke" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[13600.368649] audit: type=1110 audit(1633451373.150:94): pid=868 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[13600.368700] audit: type=1105 audit(1633451373.150:95): pid=868 uid=1000 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'

Offline

#7 2021-10-05 16:38:29

redshoe
Member
Registered: 2015-12-16
Posts: 99

Re: [Solved] RAID becomes inactive after every reboot

Wait... Does this

[13556.200983] md/raid:md126: raid level 5 active with 4 out of 5 devices, algorithm 2

mean that one out  of 5 HDD is at fault or something..?

Offline

#8 2021-10-05 17:01:22

frostschutz
Member
Registered: 2013-11-15
Posts: 1,089

Re: [Solved] RAID becomes inactive after every reboot

your mdadm.conf is wrong, should not have spares=2 (raid5 with spare is weird, anyhow)

my personal perference is to remove all these metadata=1.2 spares=2 name=Orangke:bighdd and only keep UUID=

you have to re-run mkinitcpio after changing mdadm.conf

not sure if this is your issue, it's unclear from dmesg (incomplete?) what's going on...

Last edited by frostschutz (2021-10-05 17:01:49)

Offline

#9 2021-10-05 17:08:44

redshoe
Member
Registered: 2015-12-16
Posts: 99

Re: [Solved] RAID becomes inactive after every reboot

frostschutz wrote:

your mdadm.conf is wrong, should not have spares=2 (raid5 with spare is weird, anyhow)

my personal perference is to remove all these metadata=1.2 spares=2 name=Orangke:bighdd and only keep UUID=

you have to re-run mkinitcpio after changing mdadm.conf

not sure if this is your issue, it's unclear from dmesg (incomplete?) what's going on...

Ahhhh. I did not know about mkiticpio. Do I run

mkinitcpio -P

? with the P flag? And do I run this after running

mdamd --assembly --scan

? or before?

Offline

#10 2021-10-05 17:21:35

redshoe
Member
Registered: 2015-12-16
Posts: 99

Re: [Solved] RAID becomes inactive after every reboot

Yeah. Doing

mkinitcpio -P

Solved the problem. Thanks. I wonder why this is not mentioned in the wiki page, though...

Offline

#11 2021-10-06 10:04:07

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 9,583

Re: [Solved] RAID becomes inactive after every reboot

It is sorta mentioned , but under Installing Arch Linux on RAID > Configure mkinitcpio


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
Did you use the guided installer ? If yes, I can't help you.

(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

Board footer

Powered by FluxBB