[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 will not be able to boot from RAID array. If it is not on ISO - it will not be possible to install ubuntu without internet access. Currently this issue is blocked by other defect: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1885191 ** Affects: mdadm (Ubuntu) Importance: Undecided Status: New ** Tags: vroc ** Tags added: vroc ** Package changed: debian-installer (Ubuntu) => mdadm (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903716 Title: [20.04.1] VROC - mdadm missing in live-installer ISO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1903716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 name of the volume to empty and not trim whitespaces. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1811228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 arrays and containers are removed incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1811795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 of Ubuntu 18.04 beta on IMSM RAID doesn't works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1756348/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 degraded, rebuild to spare from step 3 starts. 5) disconnect the drive added in step 3 (rebuild target) trace: [ 1022.872118] BUG: unable to handle kernel NULL pointer dereference at 00f0 [ 1022.881072] IP: raid10d+0xaec/0x1430 [raid10] [ 1022.886071] PGD 0 P4D 0 [ 1022.889033] Oops: 0002 [#1] SMP PTI [ 1022.893056] Modules linked in: xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc devlink ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_realtek snd_hda_codec_generic kvm_intel kvm snd_hda_intel snd_hda_codec irqbypass snd_hda_core ipmi_ssif intel_cstate joydev snd_hwdep intel_rapl_perf input_leds snd_pcm snd_timer ioatdma dca lpc_ich snd soundcore shpchp ipmi_si ipmi_devintf ipmi_msghandler tpm_crb acpi_pad acpi_power_meter mac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi sunrpc [ 1022.973751] ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear dm_mirror dm_region_hash dm_log nouveau hid_generic mxm_wmi mgag200 video i2c_algo_bit usbhid ttm e1000e i40e crct10dif_pclmul hid ptp crc32_pclmul ghash_clmulni_intel pcbc drm_kms_helper aesni_intel syscopyarea aes_x86_64 raid1 sysfillrect crypto_simd sysimgblt glue_helper uas fb_sys_fops cryptd ahci vmd drm usb_storage pps_core libahci wmi [ 1023.026580] CPU: 90 PID: 6373 Comm: md126_raid10 Not tainted 4.15.0-10-generic #11-Ubuntu [ 1023.035831] Hardware name: Intel Corporation PURLEY/PURLEY, BIOS PLYDTRL1.86B.0151.R03.1801050249 01/05/2018 [ 1023.046913] RIP: 0010:raid10d+0xaec/0x1430 [raid10] [ 1023.052479] RSP: 0018:b5178747bd70 EFLAGS: 00010246 [ 1023.058429] RAX: RBX: RCX: 99b3bd0d5e20 [ 1023.066517] RDX: c025f8c0 RSI: 0286 RDI: 99b7a1ed5c00 [ 1023.074605] RBP: b5178747be90 R08: 0349 R09: [ 1023.082697] R10: b5178747bd70 R11: 0365 R12: [ 1023.090790] R13: 99b3d97dbf70 R14: 99b3bd0d5e00 R15: 99b3bd0d5e00 [ 1023.098883] FS: () GS:99b7ed88() knlGS: [ 1023.108051] CS: 0010 DS: ES: CR0: 80050033 [ 1023.114602] CR2: 00f0 CR3: 0001d0c0a004 CR4: 007606e0 [ 1023.122707] DR0: DR1: DR2: [ 1023.130804] DR3: DR6: fffe0ff0 DR7: 0400 [ 1023.138915] PKRU: 5554 [ 1023.142086] Call Trace: [ 1023.144964] ? __clear_rsb+0x15/0x3d [ 1023.149105] ? __schedule+0x29f/0x8a0 [ 1023.153340] ? __clear_rsb+0x25/0x3d [ 1023.157478] ? schedule+0x2c/0x80 [ 1023.161326] md_thread+0x129/0x170 [ 1023.165273] ? raid10_start_reshape+0x630/0x630 [raid10] [ 1023.171349] ? md_thread+0x129/0x170 [ 1023.175484] ? wait_woken+0x80/0x80 [ 1023.179521] kthread+0x121/0x140 [ 1023.183267] ? find_pers+0x70/0x70 [ 1023.187204] ? kthread_create_worker_on_cpu+0x70/0x70 [ 1023.192986] ? do_syscall_64+0x118/0x130 [ 1023.197505] ret_from_fork+0x35/0x40 [ 1023.201631] Code: e4 48 8b 57 48 0f 84 92 08 00 00 49 83 7c 24 48 00 0f 84 86 08 00 00 48 63 d8 48 c1 e3 05 48 85 d2 74 41 49 8b 46 08 48 8b 04 18 ff 80 f0 00 00 00 49 8b 46 08 48 8b 04 18 48 8b 40 30 48 8b [ 1023.223245] RIP: raid10d+0xaec/0x1430 [raid10] RSP: b5178747bd70 [ 1023.230490] CR2: 00f0 [ 1023.234340] ---[ end trace 12e1280fca9f2646 ]--- Additional information: Following upstream patches solves the issue: md: document lifetime of internal rdev pointer. https://marc.info/?l=linux-raid&m=151761002007155&w=2 https://git.kernel.org/pub/scm/linux/kernel/git/shli/md.git/commit/?h=for-next&id=f2785b527cda46314805123ddcbc871655b7c4c4 md: only allow remove_and_add_spares when no sync_thread running. https://marc.info/?l=linux-raid&m=151761004007159&w=2 https://git.kernel.org/pub/scm/linux/kernel/git/shli/md.git/commit/?h=for-next&id=39772f0a7be3b3dc26c74ea13fe7847fd1522c8b ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Information type changed from Public to Private -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759279 Title: [Intel Ubuntu 18.04 Bug] Null pointer dereference, when disconnecting RAID rebuild target
[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 /dev/sda ?run # mdadm --create /dev/md/r5d3n1s64-5_A --level=5 --chunk 64 --size=2621440 --raid-devices=3 /dev/sdb /dev/sdc /dev/sda ?run 3. Add spare to RAID volume. # mdadm --add /dev/md/imsm0 /dev/sdj 4. Begin grow from Raid5 with 3 devices to Raid5 with 4 devices. # mdadm ?grow /dev/md/imsm0 ?raid-devices=4 5. Check if LEDs are indicating proper RAID status. Expected results: LEDs are indicating Rebuild status. Actual results: LEDs are showing Normal status. Upstream commit that fixes that: Recognize RAID volume under reshape as DEVICE_TYPE_VOLUME https://github.com/intel/ledmon/commit/c57e7d6d2dabe9e9d17d2e3aa4a2e77f7dc70acd ** Affects: ledmon (Ubuntu) Importance: Undecided Status: New -- 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 during migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ledmon/+bug/1831591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 defect, or there is some user visible error here? I'm asking because I would like to know if I should file separate LP, or this is the issue. 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/1885191 Title: [Focal] Installation Fails with "Invalid dep_id" when using Intel VROC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1885191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 "unable to install GRUB in dummy" occurs. It sporadically fails. It occurs on VROC RAID5 create on 4 SATA devices. RAID has ~500GB of size. It fails in the same way as: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1758038 so it might be related. ** Affects: debian-installer (Ubuntu) Importance: Undecided Status: New ** Tags: vroc -- 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] grub install fails for VROC RAID5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1902524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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] grub install fails for VROC RAID5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1902524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1885191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 UBUNTU 18.04] Enable VROC/RSTe features in Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1751771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1811228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1811795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1758282/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 during migration To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1831591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 status LED To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1831733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Pawel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2028891 Title: HTTP boot grub issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2028891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
