Your message dated Mon, 23 Nov 2015 12:33:47 +0000
with message-id <e1a0qjx-0005nn...@franck.debian.org>
and subject line Bug#784070: fixed in mdadm 3.3.4-1.1
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.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 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: 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-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.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-----

--- End Message ---

Reply via email to