The Debian GUI Installer provides multiple automated partitioning options. I've had no issues with "use entire disk and set up encrypted LVM" so far. But toady I had to install Debian on a disk that is preoccupied by multiple operating systems. In the beginning of the disk there is a Windows installation, and in the end of the disk there is an Ubuntu installation. There is one continuous space in the middle of the disk. When I chose the "use the largest continuous free space" option it correctly selected the entire space but there was no automated process to encrypt the volume. So I have an unencrypted Debian installation in the middle of my disk. Is it possible to encrypt only the entire Debian portion of the disk after an unencrypted installation in the same way as the guided "use entire disk and set up encrypted LVM"? I chose to put "All files in one partition". If there are no native methods, can third party software such as Veracrypt help? If there is no solution but to reinstall, how should I partition next time to achieve what I want?

Whenever I start up, gnome sets the volume to mute automatically. So how can I ask it to remember the volume last time I set before shutting down?

I created a 2TB volume to increase space on home directory. I created the partition: $ parted /dev/xvdb mklabel gpt $ parted -s /dev/xvdb mkpart primary ext4 1 100% Formatted the partition: $ mkfs.ext4 -I 512 /dev/xvdb1 Added the entry to /etc/fstab /dev/xvdb /export/home/brick3 ext4 defaults 0 0 Created the mountpoint: $ mkdir -p /export/home/brick3 $ chmod 0755 /export/home/brick3 Mounted the partition: $ mount /export/home/brick3 $ mkdir /export/home/brick3/home $ chmod 0775 /export/home/brick3/home once I tried to add the new brick to volume thats where I get an error. $ gluster volume add-brick home :/export/home/brick3/home volume add-brick: failed Incorrect number of bricks supplied 1 with count 2

I just installed Debian but I had some problem during the installation. I first installed my OS on HDD cause I wanted a dualboot with Windows (which WAS located on the SSD) but I couldn't complete it so I decided to say goodbye to Windows and install Debian it again on SSD. Now in my desktop I can see both hard drives but I can't mount the HDD. I'll paste some relevant information:

$ sudo fdisk -l
Disk /dev/sdb: 89.4 GiB, 96029466624 bytes, 187557552 sectors
Disk model: KINGSTON RBU-SNS
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x34f08e2e

Device     Boot     Start       End   Sectors  Size Id Type
/dev/sdb1  *         2048 185556991 185554944 88.5G 83 Linux
/dev/sdb2       185559038 187555839   1996802  975M  5 Extended
/dev/sdb5       185559040 187555839   1996800  975M 82 Linux swap / Solaris


Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: ST1000LM024 HN-M
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x55786839

Device     Boot      Start        End    Sectors   Size Id Type
/dev/sda1             2048 1951522815 1951520768 930.6G 83 Linux
/dev/sda2       1951524862 1953523711    1998850   976M  5 Extended
/dev/sda5       1951524864 1953523711    1998848   976M 82 Linux swap / Solaris

Partition 2 does not start on physical sector boundary.

The drive I'm trying to access is /dev/sda

$ df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            5.8G     0  5.8G   0% /dev
tmpfs           1.2G  9.4M  1.2G   1% /run
/dev/sdb1        87G  5.4G   77G   7% /
tmpfs           5.9G   60M  5.8G   1% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           5.9G     0  5.9G   0% /sys/fs/cgroup
tmpfs           1.2G   20K  1.2G   1% /run/user/1000

Here's what I tried:

~$ sudo fsck.ext4 -f /dev/sda
e2fsck 1.44.5 (15-Dec-2018)
ext2fs_open2: Bad magic number in super-block
fsck.ext4: Superblock invalid, trying backup blocks...
fsck.ext4: Bad magic number in super-block while trying to open /dev/sda

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 
 or
    e2fsck -b 32768 

Found a dos partition table in /dev/sda

~$ sudo resize2fs /dev/sda 8193
resize2fs 1.44.5 (15-Dec-2018)
resize2fs: Bad magic number in super-block while trying to open /dev/sda
Couldn't find valid filesystem superblock.

~$ sudo resize2fs /dev/sda 32768
resize2fs 1.44.5 (15-Dec-2018)
resize2fs: Bad magic number in super-block while trying to open /dev/sda
Couldn't find valid filesystem superblock.

inside mount output I fount the other drive infos:

/dev/sdb1 on / type ext4 (rw,relatime,errors=remount-ro)

So I wrote:

sudo mount /dev/sda1 /

And the hard disk icon on my desktop disappeared. After a reboot everything's back as it was, I can see the icon, I can't access the driver. If I click on the Icon: **Failed to mount "999 GB Volume"** **Not authorized to perform operation** *Please help*

I'm new to Linux (just over 1 month) and I’ve encountered a problem with my drive. I have the main drive (SSD) and a secondary drive (HDD). The HDD was working fine, but now I’m getting this error message:

An error occurred while accessing 'New Volume', the system responded:
The requested operation has failed: 
Error mounting /dev/sda1 at /run/media/spicypenguin/New Volume: 
wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error

And now my HDD is not accessible. I’ve tried rebooting, upgrading the system, etc., but none of these solutions worked. I’m using CachyOS:latest (Arch-based).

I am using OpenStack Cloud and using LVM on RHEL 7 to manage volumes. As per my use case, I should be able to detach and attach these volumes to different instances. While updating fstab, I have used defaults,nofail for now but I am not sure what exactly I should be using. I am aware of these options: rw, nofail, noatime, discard, defaults But I don't how to use them. What should be the ideal configuration for my use case ?

Kind of similar to this question , but not quite the same. I want to know how I can *reliably* add a *persistent label* to a disk, *especially* a **USB flash drive** or **[Micro]SD card**, that is ***on the disk itself***, such that when I move the disk to *another system*, it can be easily identified with the *same label* - that is, ***the label is on the disk*** and enables the disk to 'self-identify' to any system to which it is subsequently connected to. I am doing this on Windows, and it is apparent that some SD card/USB flash drive manufacturers do not even embed/encode a serial number, let alone a drive label. I know I can 'rename' a 'volume' in Windows Explorer by right-clicking the drive or selecting it and pressing F2, but this technically isn't a physical disk label, it is a volume label, and the associated volume serial number appears to be assigned by Windows and would be lost if the drive is reformatted. Anyone know of a reliable way of applying persistent labels to physical hard drives/removable disks that does not involve the use of a configuration file on the host system to map a label upon connecting the disk to the host system? (Before you joke about printing a sticky label and sticking it to the outside of the physical disk, yes, I can do that, but when I have more than one drive/card plugged into the system I need a way of easily identifying which logical disk in Windows maps to which physical drive).

Reposting from [here](https://forums.docker.com/t/docker-compose-not-synchronising-file-changes-in-volume/79177) as I don't quite understand how the "solution" works. **Symptom:** As reported [here](https://forums.docker.com/t/docker-compose-not-synchronising-file-changes-in-volume/79177) : I mount my local files into the container for development. My docker-compose.yml file is as follows:

version: '3.7'
services:
  node:
    build: .
    command: npm run dev
    image: node
    ports:
      - "4000:3000"
    volumes:
      - .:/code
    working_dir: /code

when I run the Next JS server in a container, it will initially load fine, but any changes made afterwards will not be shown. This is same as my observation as well. **Answers:** There has been discussion on the issues of running docker in Windows 10 Pro, but I'm hosting in Linux for Linux, and the "solution" mentioned nothing about Windows either. **Solution:** The reported working "solution" is:

version: '3.7'
services:
  node:
    build: .
    command: npm run dev
    image: node
    ports:
      - "4000:3000"
    volumes:
      - type: bind
        source: .
        target: /code
    working_dir: /code

This, to my knowledge, would be the same as what used by OP, i.e.:

volumes:
      - .:/code

I.e., I think the question of why _"docker Compose not synchronising file changes in volume"_ was not clearly answered. And neither of the following pages: - https://stackoverflow.com/questions/44678042/named-docker-volume-not-updating-using-docker-compose - https://stackoverflow.com/questions/44251094/i-want-to-share-code-content-across-several-containers-using-docker-compose-volu/44265470 - https://stackoverflow.com/questions/42958573/docker-compose-recommended-way-to-use-data-containers My case: I have a php site hosted on nginx:

version: '3.7'
services:
    web:
        image: nginx:latest
        ports:
            - "80:8081"
        volumes:
            - ./nginx.conf:/etc/nginx/conf.d/default.conf:delegated
            - ./app:/app:delegated
    php:
        build:
            context: .
            dockerfile: PHP.Dockerfile
        volumes:
            - ./app:/app:delegated
        restart: always

This is my observation: - I do docker compose up - Then ^-C to stop it - Update code in host, - Re- do / start docker compose up - Check the modified volume-mounted file within docker compose container, - The file stays the same, as before the change.

On my 240 GB SSD I had at first two partitions, one containing the Logical Volume with Linux Mint and the other had contained a NTFS partition to share with Windows. Now I removed the NTFS partition and want to extend my logical volume group to use the released disk space. How do I **extend the volume group**, my **logical volume containing /home** and the **filesystem (ext4)** on /home? Is this possible to do online? PS: Yes, I know that I have to backup my data :) /dev/sdb/ (240GB) linuxvg (160GB) should use 100% of the disk space swap root home (ext4, 128GB) should be extended to use the remaining space output of sudo vgdisplay: --- Volume group --- VG Name linuxvg System ID Format lvm2 Metadata Areas 1 Metadata Sequence No 4 VG Access read/write VG Status resizable MAX LV 0 Cur LV 3 Open LV 3 Max PV 0 Cur PV 1 Act PV 1 VG Size 160,00 GiB PE Size 4,00 MiB Total PE 40959 Alloc PE / Size 40959 / 160,00 GiB Free PE / Size 0 / 0 VG UUID ... --- Logical volume --- LV Path /dev/linuxvg/swap LV Name swap VG Name linuxvg LV UUID ... LV Write Access read/write LV Creation host, time mint, 2013-08-06 22:48:32 +0200 LV Status available # open 2 LV Size 8,00 GiB Current LE 2048 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 252:0 --- Logical volume --- LV Path /dev/linuxvg/root LV Name root VG Name linuxvg LV UUID ... LV Write Access read/write LV Creation host, time mint, 2013-08-06 22:48:43 +0200 LV Status available # open 1 LV Size 24,00 GiB Current LE 6144 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 252:1 --- Logical volume --- LV Path /dev/linuxvg/home LV Name home VG Name linuxvg LV UUID ... LV Write Access read/write LV Creation host, time mint, 2013-08-06 22:48:57 +0200 LV Status available # open 1 LV Size 128,00 GiB Current LE 32767 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 252:2 --- Physical volumes --- PV Name /dev/sdb1 PV UUID ... PV Status allocatable Total PE / Free PE 40959 / 0 output of sudo fdisk -l: Disk /dev/sdb: 240.1 GB, 240057409536 bytes 255 heads, 63 sectors/track, 29185 cylinders, total 468862128 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdb1 1 468862127 234431063+ ee GPT Disk /dev/mapper/linuxvg-swap: 8589 MB, 8589934592 bytes 255 heads, 63 sectors/track, 1044 cylinders, total 16777216 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Disk /dev/mapper/linuxvg-root: 25.8 GB, 25769803776 bytes 255 heads, 63 sectors/track, 3133 cylinders, total 50331648 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Disk /dev/mapper/linuxvg-home: 137.4 GB, 137434759168 bytes 255 heads, 63 sectors/track, 16708 cylinders, total 268427264 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000

I have a stereo. I like it, because the sound is nice, but it's not quite sophisticated engineered: It has an internal USB Card soldered on some board, directly outputting audio to the power amp. Well.. both devices, the USB card and the power amp have their own volume control, and they are (how smart) not in sync. I already hacked the remote , so that it can receive volume commands. Now I want to implement some kind of sync for convenience. Both of my audio sources (shairport-sync and spotifyd) do already support controlling the ALSA volume sliders, so that pressing the volume buttons on my smartphone forwards the signals to the ALSA device (you can verify this with alsamixer). My best guess is something like this: I've never worked with ALSA before and I just started to get familiar with the architecture, but I haven't found any solution yet that would help me implementing this 'Forward' arrow in the graphics. I could deal with the sync script myself, but I honestly have no idea where to start with the ALSA part.

Guys help me understand this! I'm using **eCryptfs** with mount command to encrypt a single folder. In first time for setup the volume I run:

mount --types ecryptfs /path/to/.private /path/to/.private

So I choose the options. For second time or any other after setup I run:

mount --types ecryptfs --options key=passphrase,ecryptfs_key_bytes=,ecryptfs_cipher=,ecryptfs_passthrough=no /path/to/.private /path/to/.private

So, when I do this steps directly in **command line** and I type a wrong password the volume are mounted but your content stay encrypted, works as expected but, when I put this steps inside a script even though I type a wrong password the content of volume are decrypted! The **eCryptfs** has some cache for the passphrase? It some that I'm not knowledg? PS: sorry for my english, I'm learning yet :)

I have monitor speakers that go into a sleep state when they don't receive a certain level of sound input. The speakers often turn off when I am watching/listening to something quietly. To remedy this, I have a crontab set to play a 10Hz wave file every 15 minutes using Sox Play: */15 * * * * XDG_RUNTIME_DIR=/run/user/1000 /usr/bin/play -v 1.25 /home/USER/rmas/10Hz.wav This works much of them time, but I have to be sure to have my system volume up around 40+% and my application volume super low. This is due to the -v (--volume) option being **relative** to system volume. I need a way to do this in an absolute fashion, where the sound is played at 100% (or a user-specified variable) volume without affecting the sound level of anything else.  And I do not want any windows popping up (action should occur completely in the background). Am I able to do this with Sox? or what is another route I could take? * Pop!_OS 22.04 - * KRK Rokit 5 Monitors (Gen 2) - * Scarlett 2i2 USB Audio Interface routing sound to speakers.

I can't seem to get containers (running podman) to be able to write to directories when running a standard user. This solution also did not work. To be clear I can read files from these directories, I just cant write to or create them. z, Z on the volume does not seem to make it work. I have gotten it to work with a root using chcon, but I have tried adding new policy modules, permissive scopes, permissive mode etc. I think it some sort of permissions error. The folder in the container (in naive case at least) seems be owned by root and has "group" nogroup I don't know if that is standard or not. I have tried chowning (like here ) the directory to the container user id and/or group id (in which case it can be owned by nobody and nogroup (does not work). I have also logged into the container with the host user+group id (it recognized my username in the bash terminal) -- no difference. Also some combination of these with chowning the folder to different users/groups such as the host user/group, container user/group, root user/group (a bit ambiguous container/host root), etc. Here are some sample outputs from ls -lnZ from in and outside the container on a few test files (note I changed the user id's except for 65534 as apparently this is a special id reserved for nobody. The id of the ***host user*** is 9876 and id of the ***container user*** is 1234. I checked with id -u to ensure the actual user id's corresponded to these. Small note, in this case the host group id is different, so lets say 5432, while the group id of the container user would be 1234 test5: - container:

drwxr-xr-x. 2 0 65534 system_u:object_r:container_file_t:s0 4096 Nov  7 23:50 test

- host:

drwxr-xr-x. 2 9876 9876 system_u:object_r:container_file_t:s0             4096 Nov  7 18:50 test5

test4: - container:

drwxr-xr-x. 2 0 65534 system_u:object_r:container_file_t:s0 4096 Nov  8 02:59 test

- host:

drwxr-xr-x. 2 9876 1234 system_u:object_r:container_file_t:s0             4096 Nov  7 21:59 test4

test3: - container:

drwxr-xr-x. 2 0 65534 system_u:object_r:container_file_t:s0 4096 Nov  7 21:40 test

- host before:

drwxr-xr-x. 2 9876 1234 system_u:object_r:container_file_t:s0:c1022,c1023 4096 Nov  7 16:40 test3

- host after:

drwxr-xr-x. 2 9876 1234 system_u:object_r:container_file_t:s0 4096 Nov  7 16:40 test3

If I fix the group id for test5, still does not work: test5 (again): - container:

drwxr-xr-x. 2 0 0 system_u:object_r:container_file_t:s0 4096 Nov  7 23:50 test

- host:

drwxr-xr-x. 2 9876 5432 system_u:object_r:container_file_t:s0 4096 Nov  7 18:50 test5

What problem might I be having writing/creating files in mounted volumes in a container as a standard user, and how can I make the standard user create/write files in mounted directories properly without resorting to very insecure solutions?

I am on Fedora 38 with LXQt. The volume control has no effect on the volume: if I increase it or decrease it until it is mute, the volume always stays the same. The only way around I have found is to use pavucontrol, which is not straightforward. Moreover, whenever I click on the screen, or pause a video, the volume gets back to its previous state.

I didn't properly apportion my volumes when I set up a RHEL 8 server so now I'm trying to rectify that. I need to move disk space from home to root. Here's what I did: 1. Booted from a RHEL ISO, went into troubleshooting mode, and dropped to the shell. 2. Activated the volume group: vgchange -ay 3. Temporarily mounted the volumes

mkdir /mnt/sysimage/rt
    mkdir /mnt/sysimage/backup
    mount /dev/mapper/rhel_ylntest-home /mnt/sysimage/rt/
    mount /dev/mapper/rhel_ylntest-root /mnt/sysimage/backup/

4. Initiated the backup: xfsdump -l 0 -L "home lv backup" -M "backup" -f /mnt/sysimage/backup/home_backup.img /mnt/sysimage/rt 5. Unmounted: umount /mnt/sysimage/rt/ 6. Deleted the logical volume: lvremove /dev/mapper/rhel_ylntest-home 7. Created the desired size: lvcreate -Zy -L 500G -n home rhel 8. Formatted the new volume: mkfs.xfs /dev/mapper/rhel_ylntest-home 9. Mounted the volume: mount /dev/mapper/rhel_ylntest-home /mnt/sysimage/rt 10. Restored from the backup: xfsrestore -f /mnt/sysimage/backup/home_backup.img /mnt/sysimage/rt 11. Unmounted everything: umount /mnt/sysimage/rt/ /mnt/sysimage/backup/ 12. Rebooted back to the command line. The home volume correctly decreased in size but the root volume didn't get any larger and the remaining disk space seems lost to the ether. What did I do wrong? I'm wondering if for step 7, I should have done lvcreate -Zy -L 500G -n home rhel_ylntest. I'm well out of my comfort zone here so please be prescriptive.

I have a 5.1 surround sound card and want to set individual volume for the different channel:

$ pactl list sinks
Sink #1
	State: RUNNING
	Name: alsa_output.usb-0d8c_USB_Sound_Device-00.analog-surround-51
	Description: CM106 Like Sound Device Analog Surround 5.1
	Driver: module-alsa-card.c
	Sample Specification: s16le 6ch 48000Hz
	Channel Map: front-left,front-right,rear-left,rear-right,front-center,lfe
	Owner Module: 23
	Mute: no
	Volume: front-left: 48434 /  74% / -7.88 dB,   front-right: 48434 /  74% / -7.88 dB,   rear-left: 48434 /  74% / -7.88 dB,   rear-right: 48434 /  74% / -7.88 dB,   front-center: 48434 /  74% / -7.88 dB,   lfe: 48434 /  74% / -7.88 dB
	        balance 0.00
	Base Volume: 65536 / 100% / 0.00 dB
[...]

**How to set the volume for rear-left by using the command line?** I tried pactl set-sink-volume 1.rear-left 100% but thats not working. The manpage even is not helpful as there seems to be no syntax for accessing the different channels.

How can I configure the volume up and down keys on my keyboard? I press the volume up, down, and mute keys, but it doesn't work. I want to control volume like windows OS. #### About my OS **OS**: Debian GNU/Linux 11 (bullseye) x86_64 **Kernel**: 5.10.0-21-amd64 **Packages**: 1869 (dpkg) **DE**: x-session-manager **WM**: Openbox

This headset works exactly as expected in non-linux operating systems (e.g. macOS, Windows) such that the volume control smoothly adjusts the loudness of the headset all the way from 0 to 100. In every version of Linux I've tried (e.g. Linux Mint), anything below 25% volume results in complete silence, and anything above 33% volume is ear-splittingly loud, leaving almost no resolution for fine-tuning. I've tried using alsamixer and pavucontrol to explore the available volume levels, with no change in behavior. How can I achieve fine-grained control of this USB headset in Linux?

When using a USB speaker (this one ) in Ubuntu 20.04, I'm observing something weird: when volume is at 100%, sound is audible (and reasonably loud). However when I gradually decrease the volume (via pactl set-sink-volume) by 1%, once I get to 96% there is no longer any audible sound coming out. This is only observed with this particular device (when using HDMI audio output to monitor's speaker or headphones, volume is not that sensitive). So the question is - what could be causing this level of sensitivity in the volume? Is there any other setting that affects it? Here's what pactl shows for this device:

Sink #3
	State: RUNNING
	Name: alsa_output.usb-Generic_USB2.0_Device_20130100ph0-00.analog-stereo
	Description: USB2.0 Device Analog Stereo
	Driver: module-alsa-card.c
	Sample Specification: s16le 2ch 48000Hz
	Channel Map: front-left,front-right
	Owner Module: 25
	Mute: no
	Volume: front-left: 62909 /  96% / -1.07 dB,   front-right: 62909 /  96% / -1.07 dB
	        balance 0.00
	Base Volume: 8573272 / 13082% / 127.00 dB
	Monitor Source: alsa_output.usb-Generic_USB2.0_Device_20130100ph0-00.analog-stereo.monitor
	Latency: 32357 usec, configured 26000 usec
	Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY 
	Properties:
		alsa.resolution_bits = "16"
		device.api = "alsa"
		device.class = "sound"
		alsa.class = "generic"
		alsa.subclass = "generic-mix"
		alsa.name = "USB Audio"
		alsa.id = "USB Audio"
		alsa.subdevice = "0"
		alsa.subdevice_name = "subdevice #0"
		alsa.device = "0"
		alsa.card = "3"
		alsa.card_name = "USB2.0 Device"
		alsa.long_card_name = "Generic USB2.0 Device at usb-0000:00:14.0-13, full speed"
		alsa.driver_name = "snd_usb_audio"
		device.bus_path = "pci-0000:00:14.0-usb-0:13:1.0"
		sysfs.path = "/devices/pci0000:00/0000:00:14.0/usb1/1-13/1-13:1.0/sound/card3"
		udev.id = "usb-Generic_USB2.0_Device_20130100ph0-00"
		device.bus = "usb"
		device.vendor.id = "1908"
		device.vendor.name = "GEMBIRD"
		device.product.id = "2070"
		device.product.name = "USB2.0 Device"
		device.serial = "Generic_USB2.0_Device_20130100ph0"
		device.string = "front:3"
		device.buffering.buffer_size = "384000"
		device.buffering.fragment_size = "192000"
		device.access_mode = "mmap+timer"
		device.profile.name = "analog-stereo"
		device.profile.description = "Analog Stereo"
		device.description = "USB2.0 Device Analog Stereo"
		module-udev-detect.discovered = "1"
		device.icon_name = "audio-card-usb"
	Ports:
		analog-output: Analog Output (priority: 9900)
	Active Port: analog-output
	Formats:
		pcm

After rebooting my server i get the following error message: Begin: Running /scripts/init-premount … done. Begin: Mounting root file system … Begin: Running /scripts/local-top … Volume group “ubuntu-vg” not found Cannot process volume group ubuntu-vg Begin: Running /scripts/local-premount … ... Begin: Waiting for root file system … Begin: Running /scripts/local-block … mdadm: No arrays found in config file or automatically Volume group “ubuntu-vg” not found Cannot process volume group ubuntu vg mdadm: No arrays found in config file or automatically # <-- approximately 30 times mdadm: error opening /dev/md?*: No such file or directory done. Gave up waiting for root file system device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Missing modules (cat /proc/modules: ls /dev) ALERT! /dev/mapper/ubuntu--vg-ubuntu--lv does not exist. Dropping to a shell! The system drops to initramfs shell (busybox) where lvm vgscan doesn't find any volume groups and ls /dev/mapper only shows only one entry control. When i boot the live SystemRescueCD, the Volume Group can be found and the LV is available as usual in /dev/mapper/ubuntu--vg-ubuntu--lv. I am able to mount it and the VG is set to active. So the VG and the LV look fine but something seems broken during the boot process. Ubuntu 20.04 Server, LVM setup on top of hardware raid1+0 with 4 SSDs. The hardware RAID controller is HPE Smart Array P408i-p SR Gen10 controller with firmware version 3.00. Four HPE SSDs model MK001920GWXFK in a RAID 1+0 configuration. The server model is HPE Proliant DL380 Gen10. No software raid, no encryption. Any hints how to find the error and fix the problem? **EDIT I:** /proc/partitions looks good blkid Where - /dev/sdc1 is /boot/efi - /dev/sdc2 is /boot - /dev/sdc3 is the PV Booting from an older kernel version worked once until executing apt update && apt upgrade. After the upgrade the older kernel had the same issue. **EDIT II:** In the module /proc/modules I can find the following entry: smartpqi 81920 0 - Live 0xffffffffc0626000 No output for lvm pvs in initramfs shell. Output for lvm pvchange -ay -v No volume groups found. Output for lvm pvchange -ay --partial vg-ubuntu -v PARTIAL MODE. Incomplete logical volumes will be processed. VG name on command line not found in list of VGs: vg-ubuntu Volume group "vg-ubuntu" not found Cannot process volume group vg-ubuntu There is a second RAID controller with HDDs connected to another PCI slot; same model P408i-p SR Gen10. There is a volume group named "cinder-volumes" configured on top of this RAID. But this VG can't be found either in initramfs. **EDIT III:** Here is a link to the requested files from the root FS: - /mnt/var/log/apt/term.log - /mnt/etc/initramfs-tools/initramfs.conf - /mnt/etc/initramfs-tools/update-initramfs.conf **EDIT IV:** In the SystemRescueCD I mounted the LV / (root), /boot and /boot/efi and chrooted into the LV /. All the mounted volumes have enough disk space left (disk space used < 32%). The output of update-initramfs -u -k 5.4.0.88-generic is: update-initramfs: Generating /boot/initrd.img-5.4.0.88-generic W: mkconf: MD subsystem is not loaded, thus I cannot scan for arrays. W: mdadm: failed to auto-generate temporary mdadm.conf file The image /boot/initrd.img-5.4.0-88-generic has an updated last modified date. Problem remains after rebooting. The boot initrd parameter in the grub menu config /boot/grub/grub.cfg points to /initrd.img-5.4.0-XX-generic, where XX is different for each menu entry, i.e. 88, 86 and 77. In the /boot directory I can find different images (?) vmlinuz-5.4.0-88-generic vmlinuz-5.4.0-86-generic vmlinuz-5.4.0-77-generic The link /boot/initrd.img points to the latest version /boot/initrd.img-5.4.0-88-generic. ***EDIT V:*** Since no measure has led to the desired result and the effort to save the system is too great, I had to completely rebuild the server.