Comment 33 for bug 1171945

Revision history for this message
RoyK (roysk) wrote : Re: [Bug 1171945] Re: Nested RAID levels aren't started after reboot

Give me some time - I have a test VM somewhere to test this… It's just a wee bit late now (CEST)

Vennlig hilsen / Best regards

roy
--
Roy Sigurd Karlsbakk
(+47) 98013356
http://blogg.karlsbakk.net/
GPG Public key: http://karlsbakk.net/roysigurdkarlsbakk.pubkey.txt
--
Da mihi sis bubulae frustrum assae, solana tuberosa in modo Gallico fricta, ac quassum lactatum coagulatum crassum. Quod me nutrit me destruit.

----- Original Message -----
> From: "Luis Alvarado" <email address hidden>
> To: "Roy Sigurd Karlsbakk" <email address hidden>
> Sent: Thursday, 15 September, 2016 04:16:52
> Subject: [Bug 1171945] Re: Nested RAID levels aren't started after reboot

> I have not being able to test this on 16.04, but is this still happening
> on 16.04 and above?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1171945
>
> Title:
> Nested RAID levels aren't started after reboot
>
> Status in mdadm package in Ubuntu:
> Confirmed
>
> Bug description:
> If creating a RAID5+0 or similar, the lower RAID-5s are started, but
> not the RAID-0 on top of them. I've tested this with Lucid (works),
> Precise (does not work) and Raring (does not work). A successive mdadm
> --assemble --scan finds the new RAID-0 and allows it to be mounted. On
> Lucid, however, this is found automatically. Something funky with
> udev?
>
> ProblemType: Bug
> DistroRelease: Ubuntu 12.04
> Package: mdadm 3.2.5-1ubuntu0.2
> ProcVersionSignature: Ubuntu 3.2.0-40.64-generic-pae 3.2.40
> Uname: Linux 3.2.0-40-generic-pae i686
> ApportVersion: 2.0.1-0ubuntu17.2
> Architecture: i386
> CurrentDmesg: [ 17.144075] eth0: no IPv6 routers present
> Date: Tue Apr 23 19:28:48 2013
> InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release i386
> (20120817.3)
> Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> MachineType: Bochs Bochs
> MarkForUpload: True
> ProcEnviron:
> LANGUAGE=en_US:en
> TERM=xterm-color
> PATH=(custom, no user)
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-40-generic-pae
> root=/dev/mapper/hostname-root ro
> SourcePackage: mdadm
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 01/01/2007
> dmi.bios.vendor: Bochs
> dmi.bios.version: Bochs
> dmi.chassis.type: 1
> dmi.chassis.vendor: Bochs
> dmi.modalias:
> dmi:bvnBochs:bvrBochs:bd01/01/2007:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr:
> dmi.product.name: Bochs
> dmi.sys.vendor: Bochs
> etc.blkid.tab: Error: [Errno 2] No such file or directory: '/etc/blkid.tab'
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1171945/+subscriptions