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

2015-10-22 Thread Guido Haase ♦ ITeHA 
> 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

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

2015-10-13 Thread Soubeyrand, Yann 
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.
--- 64-md-raid-assembly.rules	2015-10-13 17:32:51.603414258 +0200
+++ /lib/udev/rules.d/64-md-raid-assembly.rules	2015-10-13 17:33:05.091572628 +0200
@@ -25,6 +25,8 @@
 
 LABEL="md_inc"
 
+GOTO="md_inc_end"
+
 # remember you can limit what gets auto/incrementally assembled by
 # mdadm.conf(5)'s 'AUTO' and selectively whitelist using 'ARRAY'
 ACTION=="add|change", IMPORT{program}="/sbin/mdadm --incremental --export $tempnode --offroot ${DEVLINKS}"

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

2015-03-25 Thread carl 
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/ does not exist. 
Dropping to a shell!

(where  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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org