[Bug 1751771] Re: [INTEL UBUNTU 18.04] Enable VROC/RSTe features in Ubuntu 18.04

Mdadm-4.1 is not yet released upstream. Please confirm that patches listed above are included in Ubuntu 18.04 LTS. Thanks Pawel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751771 Title: [INTEL

[Bug 1759279] [NEW] [Intel Ubuntu 18.04 Bug] Null pointer dereference, when disconnecting RAID rebuild target

Private bug reported: Kernel panic with null pointer dereference, when RAID10 rebuild target is disconnected during rebuild. It's sporadical issue. Steps to reproduce: 1) Create raid10 with mdadm 2) Wait for resync to end 3) Add spare drive 4) Fail one of the member drive - Raid becomes

[Bug 1756348] Re: [INTEL UBUNTU 18.04 BUG] Installation of Ubuntu 18.04 beta on IMSM RAID doesn't works

Hi, Are there any updates on this one? Do you need any additional information/logs? Thanks Pawel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756348 Title: [INTEL UBUNTU 18.04 BUG] Installation

[Bug 1811795] Re: Mdadm: external metadata arrays and containers are removed incorrectly

Hi, It is fixed in 19.04 (mdadm there is 4.1). Any chances to include the fix in 18.04 LTS? Thanks Pawel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811795 Title: Mdadm: external metadata

[Bug 1811228] Re: Mdadm allows to change the name of the volume to empty and not trim whitespaces.

Hi, It is fixed in 19.04 (mdadm there is 4.1). Any chances to include the fix in 18.04 LTS? Thanks Pawel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811228 Title: Mdadm allows to change the

[Bug 1811228] Re: Mdadm allows to change the name of the volume to empty and not trim whitespaces.

** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811228 Title: Mdadm allows to change the name of the volume to empty and not trim whitespaces.

[Bug 1811795] Re: Mdadm: external metadata arrays and containers are removed incorrectly

** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811795 Title: Mdadm: external metadata arrays and containers are removed incorrectly To manage

[Bug 1758282] Re: [INTEL UBUNTU 18.04] RAID reshape hangs after OS reboot

** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758282 Title: [INTEL UBUNTU 18.04] RAID reshape hangs after OS reboot To manage notifications

[Bug 1831591] [NEW] LEDs not working properly during migration

Public bug reported: Description: LEDs do not work properly during migration with ledmon-0.90-0ubuntu1~18.04.1_amd64 Steps to reproduce: 1. Launch ledmon # ledmon ?all 2. Create RAID container and volume # mdadm --create /dev/md/imsm0 --metadata=imsm --raid-devices=3 /dev/sdb /dev/sdc

[Bug 1831591] Re: LEDs not working properly during migration

Hi, Are there any plans to fix it in bionic for which this issue was originally reported? Thanks Pawel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831591 Title: LEDs not working properly

[Bug 1831733] Re: ledmon incorrectly sets the status LED

Hi, Are there any plans to fix it in bionic for which this issue was originally reported? Thanks Pawel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831733 Title: ledmon incorrectly sets the

[Bug 1885191] Re: [Focal] Installation Fails with "Invalid dep_id" when using Intel VROC

Hi, What is the result of this issue? On my VROC platform I observe that VROC RAID does not appear as install target at all (using live-installer). Mdadm assembles the RAID, but it does not appear on the list of available devices. With d-i it is working fine. Is the result the same in this

[Bug 1903716] [NEW] [20.04.1] VROC - mdadm missing in live-installer ISO

Public bug reported: Intel VROC is Software RAID solution. One of the feature is to allow user to install OS on RAID array. In terms of this to be working - mdadm needs to be installed on such system. I can see that mdadm deb package is missing on Live-installer ISO. If mdadm not installed, OS

[Bug 1902524] Re: [20.04.1] [VROC] grub install fails for VROC RAID5

** Summary changed: - [20.04.1] grub install fails for VROC RAID5 + [20.04.1] [VROC] grub install fails for VROC RAID5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902524 Title: [20.04.1] [VROC]

[Bug 1902524] [NEW] [20.04.1] grub install fails for VROC RAID5

Public bug reported: Steps to reproduce: 1. Create a IMSM RAID array in BIOS. 2. Boot to Ubuntu installation. 3. Move through the installation to the partitioning section 4. Choose installation on RAID device. 5. Move through packages installation and other screens that may pop up. 6. Pop-up

[Bug 1885191] Re: [Focal] Installation Fails with "Invalid dep_id" when using Intel VROC

Are there any updates here? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885191 Title: [Focal] Installation Fails with "Invalid dep_id" when using Intel VROC To manage notifications about this

[Bug 2028891] Re: HTTP boot grub issue

Hi, I tested this with latest ubuntu 22.04 snapshot, and the issue still occurs. I was able to workaround it by replacing grub on http server from the one from Mantic Minotaur (grub-efi-arm64-signed_1.197+2.12~rc1-10ubuntu4_arm64.deb). Are there any plans of fixing that in near future? Thanks