** Changed in: cryptsetup (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: mdadm (Ubuntu)
Status: Incomplete => Fix Released
--
initrd can't mount root luks partition correctly on raid1
https://bugs.launchpad.net/bugs/298906
You received this bug notification because you
setting to dupe/fixed since expired incomplete bugs are cluttering the
default bug listing...
--
initrd can't mount root luks partition correctly on raid1
https://bugs.launchpad.net/bugs/298906
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
sounds plausible.
does anybody still have problems with booting from root on crypt on
raid1?
** Changed in: cryptsetup (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: mdadm (Ubuntu)
Status: New => Incomplete
--
initrd can't mount root luks partition correctly on raid1
htt
I can only speak for myself but I don't have this problem anymore. I
think it was solved when I upgraded to Jaunty, I'm currently running on
the Karmic beta.
I still have the same setup with the root fs on LVM on a LUKS encrypted
md1.
I checked the commit log in the bazaar branch and found this:
please also note that bug #324997 indicates that there are some systems
that do have working root on crypt on raid1. this supports my guess that
this is a race condition.
--
initrd can't mount root luks partition correctly on raid1
https://bugs.launchpad.net/bugs/298906
You received this bug noti
Just triaging this bug.
I don't have a test system here, but this bug reads pretty valid.
According from the changelog, it doesn't look that much has changed in
karmic, though.
--
initrd can't mount root luks partition correctly on raid1
https://bugs.launchpad.net/bugs/298906
You received this b
** Also affects: mdadm (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cryptsetup (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: cryptsetup (Ubuntu)
Assignee: (unassigned) => Reinhard Tartler (siretart)
** Changed in: cryptsetup (Ubuntu)
Assignee: Re
@ddom: check out
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/285392 regarding
the "s-ata-1: soft reset failed" (s-ata 1, 2, 3 and 4)"
--
initrd can't mount root luks partition correctly on raid1
https://bugs.launchpad.net/bugs/298906
You received this bug notification because you are a m
I can even confirm that bug. It first appeared on my 2.6.27-11 kernel
(x86_64, SMP) running Ubuntu 8.10.
The strange thing is that it has been running fine until a few days ago.
My system is running two s-ata disks in raid 1 mode so md0 gets started
correctly, md1 stops as stated by the kernel mes
I noticed that LUKS detection is outside the retry loop which puzzled me
a bit. Then I noticed that I have two entries in /conf/conf.d/cryptroot,
one for the root fs and one for swap and both are on the same LVM.
So I guess my previous comment wasn't entirely correct, it's always on
the fourth att
I can confirm this bug. I have my root fs on LVM on a LUKS encrypted
md1. Same version of Ubuntu and Cryptsetup as razboinik.
The mounting usually succeeds after entering the password three or four
times. The first time it always fails because "/sbin/cryptsetup isLuks"
fails to detect that it's LU
i forgot to mention, i updated cryptsetup, but this error was on the original
intrepid version also
i noticed the md0 gets initialized before calling cryptsetup but my root fs is
on md1
--
initrd can't mount root luks partition correctly on raid1
https://bugs.launchpad.net/bugs/298906
You recei
Intrepid 8.10
Cryptsetup Version: 2:1.0.6-6ubuntu2.1
--
initrd can't mount root luks partition correctly on raid1
https://bugs.launchpad.net/bugs/298906
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
Which version of Ubuntu are you using (and especially cryptsetup ("dpkg
-s cryptsetup|grep Version:")?
** Changed in: cryptsetup (Ubuntu)
Importance: Undecided => Medium
Status: New => Incomplete
--
initrd can't mount root luks partition correctly on raid1
https://bugs.launchpad.net/bu
well it fails first time regardless
so dmraid is setting up the raid after the first attempt, so is not a problem
with the cryptsetup but the init script
--
initrd can't mount root luks partition correctly on raid1
https://bugs.launchpad.net/bugs/298906
You received this bug notification because
15 matches
Mail list logo
