Your message dated Tue, 05 Jul 2016 16:47:45 +0000
with message-id <e1bktvh-0007ku...@franck.debian.org>
and subject line Bug#781172: fixed in mdadm 3.4-2
has caused the Debian Bug report #781172,
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.)


-- 
781172: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781172
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.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 781...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dimitri John Ledkov <x...@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 ftpmas...@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-de...@lists.alioth.debian.org>
Changed-By: Dimitri John Ledkov <x...@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-----

--- End Message ---

Reply via email to