Your message dated Mon, 28 Dec 2015 17:17:06 +0000
with message-id <e1adbpu-0005sv...@franck.debian.org>
and subject line Bug#784070: fixed in mdadm 3.3.2-5+deb8u1
has caused the Debian Bug report #784070,
regarding base: Stock Debian Jessie - can't boot off degraded raid1?
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
784070: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784070
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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

--- End Message ---
--- Begin Message ---
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 784...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yann Soubeyrand <yann-externe.soubeyr...@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 ftpmas...@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-de...@lists.alioth.debian.org>
Changed-By: Yann Soubeyrand <yann-externe.soubeyr...@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-----

--- End Message ---

Reply via email to