Debian Bug report logs - #781172
base: Stock Debian Jessie - can't boot off degraded raid1?

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: carl <c_boben@hotmail.com>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: base: Stock Debian Jessie - can't boot off degraded raid1?

Date: Wed, 25 Mar 2015 12:32:46 -0400

Package: base
Severity: important

Dear Maintainer,


Install a Wheezy VM using debian-7.8.0-amd64-netinst.iso 
create a raid1 mirror in the drive setup
mount / on /dev/md0 and install base system to it
login
grub-install /dev/vdb
poweroff
disable either drive /dev/vda or /dev/vdb (give VM access to only 1 drive)
computer boots

# cat /proc/mdstat
Personalities : [raid1]
md0 : active raid1 vda1[1]
 8382400 blocks super 1.2 [2/1] [_U]

Sweet.



Install a Jessie VM using debian-jessie-DI-rc1-amd64-netinst.iso
create a raid1 mirror in the drive setup
mount / on /dev/md0 and install base system to it
login
grub-install /dev/vdb
poweroff
disable either drive /dev/vda or /dev/vdb (give VM access to only 1 drive)

ALERT! /dev/disk/by-uuid/XXXX does not exist. 
Dropping to a shell!

(where XXXX is the uuid of /dev/md0)

# cat /proc/mdstat
Personalities :
md0 : inactive vda1[0](S)
 8382464 blocks super 1.2

Both refer to md0 by UUID in fstab.

When I remove the "quiet" from the kernel boot args, this is the last line I see repeated over and over again until finally I get the error I described above:

running /scripts/local-block
 
I'm admitedly not a raid expert, but this seems to be really missing the point. Part of the reason I want a raid1 is so it can survive this type of scenario. 

I googled around and surprisingly came up with very few leads. I found a Ubuntu wiki (https://help.ubuntu.com/community/Installation/SoftwareRAID#Boot_from_Degraded_Disk) that discussed how to force it to boot a degraded raid but seemed to do nothing here on debian. I found a kernel boot arg that promised to do the same (http://serverfault.com/questions/196445/boot-debian-while-raid-array-is-degraded), but it didn't work either.

What am I missing here? Shouldn't this work by default? I think a lot of people will get caught off guard by this thinking their startup drive is mirrored but the server won't boot without some manual intervention? Actually, I was not able to get it to boot at all.




-- System Information:
Debian Release: 7.8
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-0.bpo.4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Message #10 received at 781172@bugs.debian.org (full text, mbox, reply):

From: Florian Attenberger <florian.attenberger@kthread.org>

To: 781172@bugs.debian.org

Subject: Some More Info

Date: Sun, 26 Apr 2015 22:27:10 +0200

Hello,

i can reproduce this reliably, in a kvm vm.
This is only broken if you remove the disks while powered down.
Hot-Remove, reboot, Hot-Add (and Probably Cold-Add) works as it should.

Cheers,

Florian

-- 

Message #15 received at 781172@bugs.debian.org (full text, mbox, reply):

From: Sue Kemsley <skemsley@rav.org.au>

To: "int@in.ca" <int@in.ca>

Subject: Re

Date: Tue, 18 Aug 2015 14:27:36 +0000

I have a proposal for you kindly E-mail me at mshong7764@gmail.com































In the spirit of respect, Relationships Australia Victoria acknowledges the Aboriginal peoples of Australia as the Traditional Custodians of the land

Pleasenote: This message is for the named person's use only. It may contain
confidential, proprietary or legally privileged information. No confidentiality
or privilege is waived or lost by any mistransmission

If you receive this message in error, please immediately delete it and all copies
of it from your system, destroy any hard copies of it and notify the sender.
You must not, directly or indirectly, use, disclose, distribute, print, or copy
any part of this message if you are not the intended recipient. Relationships
Australia Victoria Inc. reserves the right to monitor all email communications
through our networks.

Any views expressed in this message are those of the individual sender, except
where the message states otherwise and the sender is authorised to state them
to be the views of organisation.

Thank You.

Message #20 received at 781172@bugs.debian.org (full text, mbox, reply):

From: Martin Minne <martin.minne@koezio.co>

To: "781172@bugs.debian.org" <781172@bugs.debian.org>

Subject: Re: Some More Info

Date: Wed, 19 Aug 2015 11:17:49 +0000

[Message part 1 (text/plain, inline)]

On Sun, 26 Apr 2015 22:27:10 +0200 Florian Attenberger <florian.attenberger@kthread.org> wrote:
> Hello,
>
> i can reproduce this reliably, in a kvm vm.
> This is only broken if you remove the disks while powered down.
> Hot-Remove, reboot, Hot-Add (and Probably Cold-Add) works as it should.
>
> Cheers,
>
> Florian
>
> --
>
>
>



Hello, i have the same problem as described in the 1st post with RAID10 and you are right, hot-remove/reboot/hot-add works as it should.

Did you find a solution to boot with a hard drive missing?

Thank you

[Message part 2 (text/html, inline)]

Message #25 received at 781172@bugs.debian.org (full text, mbox, reply):

From: Maximilain Schneider <max@schneidersoft.net>

To: 781172@bugs.debian.org

Subject: Re: Some More Info

Date: Mon, 07 Sep 2015 23:00:29 +0000

I have a similar problem on a live system.
I installed jessie and later set up RAID1, making sure to install grub on both drives.
I can boot fine with both disks installed.
When I powerdown and remove a single drive boot will fail after a few seconds.

By removing the quiet and splash params from the boot line I can confirm the "running /scripts/local-block" messages.
Avter the rootdelay timeout I get a (initramfs): prompt.
At this prompt I can run "mdadm --run /dev/md127" then "exit" and the system boots.

Better would be to have a message stating that the raid is degraded, and allow to boot it as such.

On Wed, 19 Aug 2015 11:17:49 +0000 Martin Minne <martin.minne@koezio.co> wrote:
> On Sun, 26 Apr 2015 22:27:10 +0200 Florian Attenberger <florian.attenberger@kthread.org> wrote:
> > Hello,
> >
> > i can reproduce this reliably, in a kvm vm.
> > This is only broken if you remove the disks while powered down.
> > Hot-Remove, reboot, Hot-Add (and Probably Cold-Add) works as it should.
> >
> > Cheers,
> >
> > Florian
> >
> > --
> >
> >
> >
> 
> 
> 
> Hello, i have the same problem as described in the 1st post with RAID10 and you are right, hot-remove/reboot/hot-add works as it should.
> 
> Did you find a solution to boot with a hard drive missing?
> 
> Thank you

Message #30 received at 781172@bugs.debian.org (full text, mbox, reply):

From: "Gupton, Joshua Lee" <JLGUPTON@liberty.edu>

Subject: Please Urgent!

Date: Wed, 30 Sep 2015 19:31:16 +0000

[Message part 1 (text/plain, inline)]

Greetings,

I need your assistance in a project that will be mutual benefit to the both of us.Sincerely  Ms. Nonnita.

[Message part 2 (text/html, inline)]

Message #35 received at 781172@bugs.debian.org (full text, mbox, reply):

From: "Soubeyrand, Yann" <yann.soubeyrand@sogeti.com>

To: "781172@bugs.debian.org" <781172@bugs.debian.org>

Cc: "781172-subscribe@bugs.debian.org" <781172-subscribe@bugs.debian.org>

Subject: Re: base: Stock Debian Jessie - can't boot off degraded raid1?

Date: Tue, 13 Oct 2015 15:44:02 +0000

[Message part 1 (text/plain, inline)]

Hi,


Applying the attached patch and executing sudo update-initramfs -u seems to fix the bug.


Can someone confirm that the patch fixes the problem?


This patch is inspired by the one named debian-disable-udev-incr-assembly.diff in mdadm Wheezy package. For a solution which doesn't imply deactivating incremental assembly, maybe we should look how things are done in Fedora with Dracut.


Cheers
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.

[Message part 2 (text/html, inline)]

[udev-rule.patch (text/x-patch, attachment)]

Message #40 received at 781172@bugs.debian.org (full text, mbox, reply):

From: Guido Haase ♦ ITeHA <guido.haase@iteha.de>

To: 781172@bugs.debian.org

Subject: Re: base: Stock Debian Jessie - can't boot off degraded raid1?

Date: Thu, 22 Oct 2015 14:04:53 +0200

> Can someone confirm that the patch fixes the problem?

Just verified it on two HDDs /dev/sda and /dev/sdb several times by
deleting MBR, BS and PT and booting the RAID1 from just one device.
The boot process performs without stopping at initramfs anyway if
just /dev/sda or /dev/sdb is present.

Disabling disk0 or disk1 in BIOS results in the same. A physical removal
of the drives couldn't be checked because the system is located at a hoster.

So for me Yann's patch works!

Don't forget tp perform a 'update-initramfs -u seems' after patching!

Thanks to Yann for his hint and his patch!

Greetinx,

Guido

Message #55 received at 781172@bugs.debian.org (full text, mbox, reply):

From: Yann-externe SOUBEYRAND <yann-externe.soubeyrand@edf.fr>

To: 781172@bugs.debian.org

Date: Fri, 23 Oct 2015 09:54:55 +0200

[Message part 1 (text/plain, inline)]

Please see bug #784070 for new information about bug and package status.

Cheers

Yann

[Message part 2 (text/html, inline)]

Message #60 received at 781172@bugs.debian.org (full text, mbox, reply):

From: Yang Yang <yang.yang@med.lu.se>

To: Yang Yang <yang.yang@med.lu.se>

Subject: RE: Good News

Date: Tue, 3 Nov 2015 15:50:28 +0000

[Message part 1 (text/plain, inline)]

________________________________
From: Yang Yang
Sent: Tuesday, November 03, 2015 4:39 PM
To: Yang Yang
Subject: Good News

 You are a Recipient to a donation of $ 2M USD. Contact (grantproject1@onet.eu) for claims.

[Message part 2 (text/html, inline)]

Message #61 received at 784070-close@bugs.debian.org (full text, mbox, reply):

From: Yann Soubeyrand <yann-externe.soubeyrand@edf.fr>

To: 784070-close@bugs.debian.org

Subject: Bug#784070: fixed in mdadm 3.3.4-1.1

Date: Mon, 23 Nov 2015 12:33:47 +0000

Source: mdadm
Source-Version: 3.3.4-1.1

We believe that the bug you reported is fixed in the latest version of
mdadm, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 784070@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yann Soubeyrand <yann-externe.soubeyrand@edf.fr> (supplier of updated mdadm package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Tue, 10 Nov 2015 11:18:39 +0100
Source: mdadm
Binary: mdadm mdadm-udeb
Architecture: source amd64
Version: 3.3.4-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian mdadm maintainers <pkg-mdadm-devel@lists.alioth.debian.org>
Changed-By: Yann Soubeyrand <yann-externe.soubeyrand@edf.fr>
Description:
 mdadm      - tool to administer Linux MD arrays (software RAID)
 mdadm-udeb - tool to administer Linux MD arrays (software RAID) (udeb)
Closes: 784070
Changes:
 mdadm (3.3.4-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * disable-incremental-assembly.patch: incremental assembly prevents booting
     in degraded mode (Closes: #784070)
Checksums-Sha1:
 538bcb637865f75ee99ea965d4d3bc6c8796eae3 1970 mdadm_3.3.4-1.1.dsc
 ed9fc1607b26421817207330cfe47111ee143639 86312 mdadm_3.3.4-1.1.debian.tar.xz
 2a023be08c8ae49155dd70b1f4a766331c824b68 257110 mdadm-udeb_3.3.4-1.1_amd64.udeb
 c361786547cf777ffe66ad9d495abc92ed40c0f5 433738 mdadm_3.3.4-1.1_amd64.deb
Checksums-Sha256:
 22585dc6c20b173b433bff0a31028273d5da789f66bab1b61939416557de77c2 1970 mdadm_3.3.4-1.1.dsc
 16dd6b77c14a15afa23e077f0c157c17ef5cc6054b17ccb38cf5af86f7bf55bd 86312 mdadm_3.3.4-1.1.debian.tar.xz
 b6e1d3d178be5556891634712bd4cb5219deade34d2dc1c31620601c2d8134d8 257110 mdadm-udeb_3.3.4-1.1_amd64.udeb
 325ea8354c039ca1fd1bbfad1d19335d36ea9fddbc2cb1eb30500f7e5930dc52 433738 mdadm_3.3.4-1.1_amd64.deb
Files:
 9b3fca39d06b53b8914cd914ef4c3418 1970 admin optional mdadm_3.3.4-1.1.dsc
 3bcd96d08533e7905d1e340dcb3358e4 86312 admin optional mdadm_3.3.4-1.1.debian.tar.xz
 5aeb025930deab41eb93ed0194336177 257110 debian-installer optional mdadm-udeb_3.3.4-1.1_amd64.udeb
 00c829f7f356f48b0a6b25966265a10e 433738 admin optional mdadm_3.3.4-1.1_amd64.deb
Package-Type: udeb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJWUwU2AAoJEFh5eVc0QmhOAu8QAK3LZNClmLKPoYMe4gPhahbQ
LO5blpxTp4TiUfRVcf+3xtXDV6JhoRgz6c8c0kwzjOMK7zZg4vO0DVbHTjgEvFBY
z0l0r1/LzSqJm17O7LaV5lGWWko4D1lcZp8XoSwb5HwYLIALaeB2RNyThPMSZpnL
nmTHjzCOp/YESJcohOfa8AxG89HA5E1KNcVy8yr0yXQYUxsl316/VbtsOJqvkiiH
PEwLS4A3N3naTtEdOdouhauidoaEF0X62z7kobZHgvi83t3O0Rre+Sjd4Uz3Udqy
eDONrx2ZgxcTV9RBWg669eDyJ7w1Fb9NrQ7dHVES0Jgdn+S2h63gpLuAS1YumOZp
fW/juwnOm0haU8cjIhtuPtcLUvcEB2uoggW5DCg3CPSvTpl/zQCOpIXX01mJ23P5
C4dComSWHcLgH/5PBkKYJs9DlvS4F0bBxOSUhVesLA5FG7VJ23gugebsPZeeNbKu
GOMIDE9sOQxM9GEFcwTG8AIWEtDemh1jNzfRcFqH1NECeGbJ/XPrjNjKAQnLsJI8
vNgpJtePQ9fhX0+bSSqkVjQQYMVw0nO1rivPNJq6ez67Z+YNhRRjuWcN19OyhuW4
rAcBVUwOFoLNkFFEQmOc6om5mDqRvISsEiyZ9LD67nOTaP/dNojWMP+tyqQG+Vrv
o1VHja3YbXohwbfHmveF
=X6q1
-----END PGP SIGNATURE-----

Message #62 received at 784070-close@bugs.debian.org (full text, mbox, reply):

From: Yann Soubeyrand <yann-externe.soubeyrand@edf.fr>

To: 784070-close@bugs.debian.org

Subject: Bug#784070: fixed in mdadm 3.3.2-5+deb8u1

Date: Mon, 28 Dec 2015 17:17:06 +0000

Source: mdadm
Source-Version: 3.3.2-5+deb8u1

We believe that the bug you reported is fixed in the latest version of
mdadm, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 784070@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yann Soubeyrand <yann-externe.soubeyrand@edf.fr> (supplier of updated mdadm package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Mon, 23 Nov 2015 17:22:27 +0100
Source: mdadm
Binary: mdadm mdadm-udeb
Architecture: source amd64
Version: 3.3.2-5+deb8u1
Distribution: stable
Urgency: medium
Maintainer: Debian mdadm maintainers <pkg-mdadm-devel@lists.alioth.debian.org>
Changed-By: Yann Soubeyrand <yann-externe.soubeyrand@edf.fr>
Description:
 mdadm      - tool to administer Linux MD arrays (software RAID)
 mdadm-udeb - tool to administer Linux MD arrays (software RAID) (udeb)
Closes: 784070
Changes:
 mdadm (3.3.2-5+deb8u1) jessie; urgency=medium
 .
   * Non-maintainer upload.
   * disable-incremental-assembly.patch: incremental assembly prevents booting
     in degraded mode (Closes: #784070)
Checksums-Sha1:
 aaaa41e1d5afe865d34ede645a63771229071e0c 1985 mdadm_3.3.2-5+deb8u1.dsc
 478989475bbc891263e8b45e87ccc07b5370faed 87060 mdadm_3.3.2-5+deb8u1.debian.tar.xz
 6c356e8810b92745db72f798b3cfb1c5aee46693 432040 mdadm_3.3.2-5+deb8u1_amd64.deb
 0c671004d5255960799a9fc79aba02d2d5df4e93 252638 mdadm-udeb_3.3.2-5+deb8u1_amd64.udeb
Checksums-Sha256:
 b444f4e4b998777ed2039df988afec0823b4bba5e19ed9f87fc37824093ffbea 1985 mdadm_3.3.2-5+deb8u1.dsc
 9235841b13034fc028ab7904907c26ee59b49c6b7e34d06ad2f2f8156a8f7070 87060 mdadm_3.3.2-5+deb8u1.debian.tar.xz
 ae0090b2360fcfb3a19ac8ccba569146b8d4781c20aa1c655c7e27e308fb1089 432040 mdadm_3.3.2-5+deb8u1_amd64.deb
 26c6690b96d83e23218dbfd967ec85e012a9d934467f63a554bb7c6b86f31a1a 252638 mdadm-udeb_3.3.2-5+deb8u1_amd64.udeb
Files:
 f13e1df54c5a83dad53f025b58f6d673 1985 admin optional mdadm_3.3.2-5+deb8u1.dsc
 b4eb60897b90cbf2bb905faa700a6e55 87060 admin optional mdadm_3.3.2-5+deb8u1.debian.tar.xz
 285da22da42530f7a2a2f0da8053e3fa 432040 admin optional mdadm_3.3.2-5+deb8u1_amd64.deb
 b2aa532b31e374f6365dc04049c3f6ed 252638 debian-installer optional mdadm-udeb_3.3.2-5+deb8u1_amd64.udeb
Package-Type: udeb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJWgU5eAAoJEPNPCXROn13ZjwMQANwWdLHeJQtT8W9D8a074s/z
y9PK1FpMOynQOFssos8ZcOuK4C6zghV1LDIgraASXjGBmeuGdlPD4OmeRBJSjr6Q
+Qs9XCjEBnsRwM20n3FN61ZXd1mdVsdVXOedkxa4dTeYwpe/AUHOQ6RKxemnZKb5
kbEyi/u4PsvTpplsjQMx7F8BCy3lYiIM3YOmzJdNsMUpMh4W4X6vr+MnJroIZYr9
4UeDC/H2YBFIQv5/2YxSLt2EgtidKi1RKwquRTwFily8G0tHsJsz2UgH2U3D0+nA
Oc6nfZfP5OEL9e7/pNz/upqsddAumqbzARwTkXXHTBFhh3OEzWvNC9oeJqoD5H0h
nw7yRpe5mKrZunZQXMSiixAubmFbOdezTC/m5uAH8fNR/P9C8Zh2BcBLzh2GVnnL
VnQHvl7bWxtIt7m8h+0iXY/0hDo+RatC5UxmOCrfnAqGenlX3Ai1dCkwuSjJJQLf
S0jgn0r5/4arFx4DSi28t7SpQmyN6N82WmmgvLvjnhTwsFu/wVRXWtp3l7bKQxCF
rLz9GXnfWZXl+4eMYuocPb/9TliTWTG/I/8JjO0i09XrXnsikhy1n5ihbFbzsu9G
uHHn1UslL9SHXMD37dHj/2XT1Te7x15mHOfXlfliIs8Qc3fTRb+/zLw7CoitJIj2
nX3WU5F5frdQmQaFLc1o
=ttV7
-----END PGP SIGNATURE-----

Message #77 received at 781172-close@bugs.debian.org (full text, mbox, reply):

From: Dimitri John Ledkov <xnox@ubuntu.com>

To: 781172-close@bugs.debian.org

Subject: Bug#781172: fixed in mdadm 3.4-2

Date: Tue, 05 Jul 2016 16:47:45 +0000

Source: mdadm
Source-Version: 3.4-2

We believe that the bug you reported is fixed in the latest version of
mdadm, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 781172@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dimitri John Ledkov <xnox@ubuntu.com> (supplier of updated mdadm package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sat, 02 Jul 2016 19:16:01 +0100
Source: mdadm
Binary: mdadm mdadm-udeb
Architecture: source
Version: 3.4-2
Distribution: unstable
Urgency: low
Maintainer: Debian mdadm maintainers <pkg-mdadm-devel@lists.alioth.debian.org>
Changed-By: Dimitri John Ledkov <xnox@ubuntu.com>
Description:
 mdadm      - tool to administer Linux MD arrays (software RAID)
 mdadm-udeb - tool to administer Linux MD arrays (software RAID) (udeb)
Closes: 632401 675452 714155 717609 726390 737132 769201 770002 781172 796624 804973 813335 813637 814036
Changes:
 mdadm (3.4-2) unstable; urgency=low
 .
   * Reneable incremental assembly
   * Rely on udev to assemble incremental arrays
   * In environments with systemd rely on mdadm-last-resort@.timer|.service
     units to activate degrated raids
   * In environments initramfs-tools initrd (no systemd) add local-block
     script to do the same after 2/3rds of root delay iteration
   * Drop local-top initramfs script
   * Drop dependency on initscripts package
   * Drop INITRDSTART support
   * Drop mdadm-raid init script
   * Drop ancient preinst
   * In mdadm.init remove dependency on mdadm-raid
   * In mdadm.init check, and bail out running in a container
   * In mdadm.config drop mdadm/autostart logic
   * Drop CREATE stanzas from mkconf and don't include them in the
     initramfs. The generated defaults, are the compiled-in defaults. And
     the current one generates warnings when running mdadm in the
     initramfs, as there is no passwd|group files to resolve root/disk
     uid/gid. Closes: 717609
   * Adapt changes and formatting of initramfs hook from Ubuntu
   * Bump standards version to 3.9.7, no changes required
   * Fix copyright-refers-to-symlink-license
   * Closes: #781172, #796624, #769201, #813335, #632401, #804973, #714155,
     #770002, #737132, #675452, #726390, #813637, #814036.
Checksums-Sha1:
 3f20bd22e449b43eecf36b7b4a6dfe2275160e63 1602 mdadm_3.4-2.dsc
 46337146e33b6817f3a66bfec99654c84e28c3cd 82184 mdadm_3.4-2.debian.tar.xz
Checksums-Sha256:
 bd7088a2bcc9661b0a7ce548650dfff2e1ebbfdaf6376618ae5cade05645de3a 1602 mdadm_3.4-2.dsc
 c4f287a6b0d33eacbe127889676f5408df5655a6cb3e2ab5c55b6a8ebda7facf 82184 mdadm_3.4-2.debian.tar.xz
Files:
 d0455d6ce0e26d629c9e579e4b933594 1602 admin optional mdadm_3.4-2.dsc
 a5a6321b9570e8d1560d06e3ac7b2d06 82184 admin optional mdadm_3.4-2.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJXe733AAoJEMrC2LnNLKX5X/oH/R8JVRDxFVy/5F3AqrsPTZIF
HGPp3Jlu3tAAUDba+cfsO/PoOX7c3VSjkYt276fMXZ0N3xkI7xXOKwq7eyx2PfiR
l+BqW5ePM3guUq9o6LSf9Ecw69ecftX0WbjVdnUn4gY5XCBouuxwjtmjwIe+4XGb
7uaF9/sRZe7/iNfvwGN8bgZzUGMYAFg4iAFfAh0Xz+LW+9d9mNeU9XU//kwENCkz
VL0ohkU2eYY3nHwr1mzKEFiJ8MLNhPUyckif/RCqTtFVyI8IuPxH2u1+A45F89YS
b8aB87QEpDl85UffaSaC0sKMdF4JTBnK20KN/ZwRDrtMWNGFQ9pyRCp66NM/gXo=
=sGtm
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.