** Also affects: upstart (Ubuntu)
Importance: Undecided
Status: New
--
upstart init within initramfs
https://bugs.launchpad.net/bugs/491463
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
First step to allow using upstart in initramfs would probably be an
option to copy/run upstart into initramfs by adding an initramfs-hook
script to the upstart package.
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/lucid/initramfs-
tools/lucid/annotate/head%3A/docs/example_hook
--
upstart
All right, maybe you could try if that ppa facility can build your
modified source package into one that is installable with a ppa
sources.list entry. I think mdadm --incremental needs the map file in
the system to be successfull with later hot-plugging of raid devices. At
least what I remember fro
** Tags added: patch
--
RAID not implemented (use alternate CD instead)
https://bugs.launchpad.net/bugs/44609
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.c
Can't the post-install script of libdvdread check if the dvd readers
present have a region set, if that is required for libdvdread to work?
--
Something needs to set the region code on new DVD drives
https://bugs.launchpad.net/bugs/16722
You received this bug notification because you are a member
Mathieu what version did you use, and what did you preseed? I used plain
9.10 alternate to install on raid and it did not install postfix with
mdadm, but synaptic would pull it in if it's installed later.
--
mdadm installs postfix
https://bugs.launchpad.net/bugs/379882
You received this bug notif
** Description changed:
Ubuntu 9.04, fresh install on Acer Aspire 5005.
(confirmed also with 9.10)
Not sure about package, but it seems the problem is with CPU frequency
adjustment or fan control.
Laptop shuts down right in the middle of CPU-greedy operation overheated. I
haven't seen
** Description changed:
Ubuntu 9.04, fresh install on Acer Aspire 5005.
(confirmed also with 9.10)
Not sure about package, but it seems the problem is with CPU frequency
adjustment or fan control.
Laptop shuts down right in the middle of CPU-greedy operation overheated. I
haven't seen
Are you using brasero? Its CD images burned produce kernel I/O errors
with some optical drives.
https://bugzilla.redhat.com/show_bug.cgi?id=571074
** Bug watch added: Red Hat Bugzilla #571074
https://bugzilla.redhat.com/show_bug.cgi?id=571074
--
IO errors when inserting a disc
https://bugs.l
are you using brasero?
https://bugzilla.redhat.com/show_bug.cgi?id=571074
--
IO errors when inserting a disc
https://bugs.launchpad.net/bugs/304954
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@
are you using brasero?
https://bugzilla.redhat.com/show_bug.cgi?id=571074
** Bug watch added: Red Hat Bugzilla #571074
https://bugzilla.redhat.com/show_bug.cgi?id=571074
--
ISO burn on Intrepid with Brasero will not mount
https://bugs.launchpad.net/bugs/295795
You received this bug notificati
are you using brasero?
https://bugzilla.redhat.com/show_bug.cgi?id=571074
** Bug watch added: Red Hat Bugzilla #571074
https://bugzilla.redhat.com/show_bug.cgi?id=571074
--
Buffer I/O error on device sr0 Logical Block XX in Intrepid Ibex Alpha 5
https://bugs.launchpad.net/bugs/266951
You
Public bug reported:
Binary package hint: debian-installer
i.e. it's not possible to span a mirror over the laptop's internal disk
and the docking station's disk at the office, while the data on the
laptop resides inside a luks partition.
After creating a luks partition, the installer does not
Public bug reported:
Binary package hint: mdadm
Raid is designed to provide redundancy and failure tolerance. If a raid member
fails and redundancy allows it, system operation is not compromised. Upon
failure of components the raid array is properly degraded on the fly, and the
system *will h
** Description changed:
Binary package hint: mdadm
-
- Raid is designed to provide redundancy and failure tolerance. If a raid
member fails and redundancy allows it, system operation is not compromised.
Upon failure of components the raid array is properly degraded on the fly, and
the sys
Maybe https://wiki.ubuntu.com/ReliableRaid (Blocked hotplugging
mechanisims)?
--
RAID1 partitions created in Jaunty not recognised by Karmic
https://bugs.launchpad.net/bugs/538597
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
The thread http://ubuntuforums.org/showthread.php?p=8407182 mentioned on
https://wiki.ubuntu.com/ReliableRaid talks about /dev/md_d* type autocreated
devices, as a symptom of "un-defined/un-white-listed" arrays with ubuntu's
hotplug setup.
--
/dev/md_* devices are not created in /dev
https://
Defaulting to boot_degraded=false is bad replacement for buggy handling
of raid degradation. (not a valid fix)
https://wiki.ubuntu.com/ReliableRaid
--
bogus debconf question "mdadm/boot_degraded"
https://bugs.launchpad.net/bugs/539597
You received this bug notification because you are a member of
manual workaround: install esmtp and procmail (and configure procmail as
local delivery agent, see /usr/share/doc/esmtp)
--
mdadm monitor feature broken, not depending on local MTA/MDA or using
wall/notify-send
https://bugs.launchpad.net/bugs/535417
You received this bug notification because you
** Summary changed:
- firehol not started on boot (with START_FIREHOL=yes)
+ not started on boot (DNS resolv fails)
--
not started on boot (DNS resolv fails)
https://bugs.launchpad.net/bugs/490317
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Description changed:
Binary package hint: firehol
ubuntu 9.10
- * /etc/init.d/firehol script is there
- * /etc/firehol/firehol.conf is in place
+ The failure to load with domain names used in the firehol.conf may have
+ arisen with the network now set up by upstart's native /etc/
** Changed in: ubuntu-docs (Ubuntu)
Assignee: viclyn (oobiauk) => Connor Imes (rocket2dmn)
--
server guide: warn about using ubuntu with raid or provide reliable raid config
https://bugs.launchpad.net/bugs/496478
You received this bug notification because you are a member of Ubuntu
Bugs, whi
** Also affects: mdadm (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- dm-linear, lookup failed
+ dm-linear: lookup failed / mdadm: breaks boot
--
dm-linear: lookup failed / mdadm: breaks boot
https://bugs.launchpad.net/bugs/418803
You received this bug notification b
Hm, I'm sorry I can't trace this down to other bugs then and help
finding the cause. Maybe superblock metadata are found on your disks is
causing mdadm to wait for arrays. You could add if installing mdadm did
create a /etc/mdadm/mdadm.conf with ARRAY definitions? Since you did not
purge mdadm it s
Didn't you write "A apt-get remove mdadm doesn't fix the error." in the
bug description, you may want to clarify the description a bit.
--
dm-linear: lookup failed / mdadm: breaks boot
https://bugs.launchpad.net/bugs/418803
You received this bug notification because you are a member of Ubuntu
Bug
As it's not caused by kernel raid autodetection I guess this probably
belongs to package mdadm.
Have you tested if the 9.10-10.04 update works for raid systems this
time?
You can see quite some raid bugs filed and also
https://wiki.ubuntu.com/ReliableRaid
** Package changed: linux (Ubuntu Lucid
Note that initramfs actually also wrongly executes "mdadm --assemble
--scan --run" if it finds any arrays degraded.
Bug #497186 initramfs' init-premount degrades *all* arrays (not just
those required to boot)
--
booting out of sync RAID1 array fails with ext3 (comes up as already in sync)
https:
> I believe this should fail and refuse to use the second disk until you
manually re-add it to the array, causing a full resync.
Yes, if there is a way for mdadm to determine if members are out of sync
it should fail on conflicting updates that occured on separated parts of
the array (as is the ca
Current mdadm versions support AUTO lines in mdadm.conf, that may
supersede dynamic mdadm.conf rewriting.
--
[->UUIDudev] installing mdadm (or outdated mdadm.conf) breaks bootup
https://bugs.launchpad.net/bugs/158918
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Could you please reopen/update the upstram bug with the current
description?
--
listview: inaccessible dir has same emblem as read-only dir [emblem
inconsistency]
https://bugs.launchpad.net/bugs/489977
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
** Package changed: ubuntu => mdadm (Ubuntu)
--
Server edition cannot boot when raid-1 is incomplete
https://bugs.launchpad.net/bugs/544625
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ub
Is this still an issue with Bug #546929 fixed in beta2?
** Changed in: debian-installer (Ubuntu)
Status: Confirmed => Incomplete
--
lucid 20100324 alternate cd: "no common cdrom drive" error
https://bugs.launchpad.net/bugs/546489
You received this bug notification because you are a member
*** This bug is a duplicate of bug 259145 ***
https://bugs.launchpad.net/bugs/259145
Dupe of #259145 degraded NON-root raids never --run on boot
** This bug has been marked a duplicate of bug 259145
degraded NON-root raids never --run on boot
--
Server edition cannot boot when raid-1 is
Looking under "bugs" where this bug has been filed (/ubuntu/lucid/) does
not turn up a serious bug besides this one, but mdadm not only in 10.04
actually has some: https://bugs.launchpad.net/ubuntu/+source/mdadm
--
booting out of sync RAID1 array fails with ext3 (comes up as already in sync)
htt
> Activating the degraded array is done only if the root fs is not
found,
Right, its only in a failure hook, and things like cryptsetup won't be run
after that...
The initramfs boot mechanism is just not designed with the right event driven
approach yet. Bug #488317
> and only if the mdadm pac
> the problem is that the second disk is automatically added back into
the array by mdadm --increment. Once the disk has been marked as removed
from the array, it should require manual intervention to put it back.
In the case at hand mdadm should not only refuse addition due to it
being "removed".
** Tags added: dist-upgrade
--
install fails missing obsolete /dev/MAKEDEV
https://bugs.launchpad.net/bugs/368986
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubu
Anybody tested if karmic to lucid upgrades work with raid_members
wrongly identified as luks?
Is there a ubuntu VM farm/cloud where test cases and bug replications
can be run?
--
breaking raid: root raid_member opened as luks
https://bugs.launchpad.net/bugs/531240
You received this bug notifica
Thanks for responding. Oh I see, my comment about changing the partition type
was under the assumption of type fd Linux raid autodetect.
Looking for the message you reported, could it be a little different and
rather unrelated to mdadm? (Bug #115616
http://forum.ubuntuusers.de/topic/device-mappe
Assigning to lvm, sounds more appropriate to me, given the information.
** Summary changed:
- initramfs images not recreated during *un*-install
+ dm-linear, lookup failed
** Changed in: mdadm (Ubuntu)
Status: Invalid => New
** Package changed: mdadm (Ubuntu) => lvm2 (Ubuntu)
--
dm-lin
I see, thanks for the pointer, David. Currently there isn't any real
forwarding going on, anyway. The LP project mdadm is only a place to
gather the upstream related things (no upstream bug tracker).
--
{upstream} Raid10,o2 only reads from a single disk
https://bugs.launchpad.net/bugs/320418
You
> blkid currently, deliberately, returns only the first detected RAID or LUKS
> container
> for a filesystem - with the checking order being raid first.
Did someone change it already?
The issue I reported is actually the other way around. A RAID member
device partition (version 0.90 metadata, l
Yeah, it was a production karmic machine where this got in with update
to 2.16-1ubuntu5.
I'm sorry, noticed I only mentioned that in the the issue that led to
adding this behaviour.
--
breaking raid: root raid_member opened as luks
https://bugs.launchpad.net/bugs/531240
You received this bug not
Can you confirm the behavior for 2.16-1ubuntu5?
Else:
As I reported the type was correctly reported as raid member upon (re)setting
the array up (while it was mounted). But on one of the subsequent reboots
things got changed around, and then blkid reported luks type (while it was
mounted as suc
Sorry, I was unclear: I did not try raid with lucid.
** Changed in: util-linux (Ubuntu)
Status: Incomplete => Confirmed
--
breaking raid: root raid_member opened as luks
https://bugs.launchpad.net/bugs/531240
You received this bug notification because you are a member of Ubuntu
Bugs, whic
I only have one of the luks on raid member drives left to examine (I
reinstalled the system since I have no use for data corrupting raid
setups and not unlimited disks available.), but I booted lucid beta1 CD
and looked at that drive.
The blkid output looks just the same as on 9.10 to me:
/dev/s
(The sdc/sdd change was due to me disconnecting the USB drive in
between.)
--
breaking raid: root raid_member opened as luks
https://bugs.launchpad.net/bugs/531240
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
At the same time "fdisk -l" output looks OK:
Disk /dev/sdc: 120.1 GB, 120060444672 bytes
255 heads, 63 sectors/track, 14596 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical / optimal IO): 512 bytes / 512 bytes
Device Boot Start End Blocks Id
Back on 9.10: cfdisk and fdisk see those partitions as raid and only
blkid gives luks (just as reported)
--
breaking raid: root raid_member opened as luks
https://bugs.launchpad.net/bugs/531240
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Are newer blkid and cfdisk still probing the end of devices (older
metadata)?
--
breaking raid: root raid_member opened as luks
https://bugs.launchpad.net/bugs/531240
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
Hi Dustin, I am not a developer and don't know how to create packages
etc. Though, I have gathered information from using mdadm and
bugreports to make it easier for a developer to bring ubuntu's mdadm
setup in shape.
--
initramfs' init-premount degrades *all* arrays (not just those required to bo
>> All would be clearer if * mdadm -E would report "missing" instead of
>> removed (which sounds like it really got "mdadm --removed")
>
> There already exists a faulty state. It might be appropriate to use that
This and the detection process sounds reasonable to me.
I am not sure how much sense
A name for this might be "safe segmentation". It prevents data-loss that
could occur by syncing unreliable disks.
--
array with conflicting changes is assembled with data corruption/silent loss
https://bugs.launchpad.net/bugs/557429
You received this bug notification because you are a member of U
I understand the md device dependencies are not available in fstab, I am
not sure though what should prevent going through the filesystems and
identifying their dependencies in the running system?
In the suggestion the fstab gets merely used as a starting point, a list
of filesystems that get set
I got the beginning with
dd if=/dev/sdc7 of=raid-part-head bs=1M count=1
Fdisk etc. output with various units and "block sizes" but never stating the
actual unit sizes is a mess.
#blockdev --report /dev/sdc7
RORA SSZ BSZ StartSecSize Device
rw 256 512 512 19589667
Does cfdisk (in lucid) deliberately show blkid output instead of types
given in the partition table? If so, would it make sense to show that
additionally not exclusively.
--
breaking raid: root raid_member opened as luks
https://bugs.launchpad.net/bugs/531240
You received this bug notification be
** Changed in: cryptsetup (Ubuntu)
Status: Incomplete => New
--
breaking raid: root raid_member opened as luks
https://bugs.launchpad.net/bugs/531240
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubu
Dear ubuntu developer,
I have finished assessing the mdadm bugs and found the four
(distribution related) bugs in ubuntu's mdadm setup which mostly render
it unusable.
All four reports contain proposed solutions, now.
Mostly they're just simple adjustments to the mdadm commands used in the
manag
** Summary changed:
- The rcS.d script for firehol starts before NFS and NIS
+ init script starts before NFS, NIS, DNS (need two stages)
--
init script starts before NFS, NIS, DNS (need two stages)
https://bugs.launchpad.net/bugs/28906
You received this bug notification because you are a member
Public bug reported:
Ubuntu's current kernel option
CONFIG_MD_AUTODETECT=y
enables the kernel's RAID autodetection during boot.
Aside from causing a delay for everyone this often also disturbs the udev/mdadm
setup of raid devices in the system.
(i.e. devices partly busy/set up without an entry
** Summary changed:
- enabled kernel raid autodetection disturbs initramfs
+ enabled kernel raid autodetection disturbs udev/mdadm (initramfs & later)
--
enabled kernel raid autodetection disturbs udev/mdadm (initramfs & later)
https://bugs.launchpad.net/bugs/551719
You received this bug notific
Note that with the UUID-based raid assembly
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/158918/comments/33
the mdadm.conf file is not used to store ARRAY definitions any more.
Thus the (UUID) list of raid devices required to mount the rootfs must
be stored in a separate file within initra
> Well, we can consider it a wishlist bug that 'cryptsetup isLuks' returns true
> in this case;
> fixing that isn't actually relevant to resolving the problem you're having.
As the cryptsetup init checks the device with "cryptsetup isLuks" it
would actually stop that raid desyncing (i.e. fix the
Yes, software RAID in is a non-acceptable state in ubuntu. For servers just as
well as for workstations.
Beware, if you want to securely save your data and that is probably
mainly why anybody would use redundant disks anyway.
But ubuntu actually started to implement true udev/mdadm hotplugging,
Ok, so you used synaptic to install mdadm later on (it did not come with
the initial install from alternate CD), right?
--
mdadm installs postfix
https://bugs.launchpad.net/bugs/379882
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
u
Ah, sorry I over-read you updated.
** Description changed:
Binary package hint: mdadm
When upgrading to Jaunty from Intrepid, the mdadm package installed
postfix. I can't see why a package that manage software RAID partitions
needs a mail transport agent, but what is worse is that my d
Yeah, if only maintainers with responsibilty for specific packages
existed...
--
mdadm --create with typo overwrites device file
https://bugs.launchpad.net/bugs/215542
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
** Summary changed:
- no console message when array is not created as specified
+ {upstream} no console message when array is not created as specified
** Also affects: mdadm
Importance: Undecided
Status: New
--
{upstream} no console message when array is not created as specified
https
** Changed in: mdadm (Ubuntu)
Status: New => Invalid
--
'md: invalid superblock checksum' when adding empty device to raid
https://bugs.launchpad.net/bugs/447059
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
** Summary changed:
- initramfs images not recreated during uninstall
+ initramfs images not recreated during *un*-install
--
initramfs images not recreated during *un*-install
https://bugs.launchpad.net/bugs/418803
You received this bug notification because you are a member of Ubuntu
Bugs, whic
** Summary changed:
- madam: no devices found for /dev/md0
+ {upstream} madam: no devices found for /dev/md0
** Also affects: mdadm
Importance: Undecided
Status: New
--
{upstream} madam: no devices found for /dev/md0
https://bugs.launchpad.net/bugs/403767
You received this bug notific
** Summary changed:
- monitoring raid0 floods syslog with DeviceDisappeared/Wrong-Level
+ {upstream} monitoring raid0 floods syslog with DeviceDisappeared/Wrong-Level
** Also affects: mdadm
Importance: Undecided
Status: New
--
{upstream} monitoring raid0 floods syslog with DeviceDisap
** Summary changed:
- Raid10,o2 only reads from a single disk
+ {upstream} Raid10,o2 only reads from a single disk
** Also affects: mdadm
Importance: Undecided
Status: New
--
{upstream} Raid10,o2 only reads from a single disk
https://bugs.launchpad.net/bugs/320418
You received this bu
** Summary changed:
- missing command to start *single* arrays in "auto-read" mode (like
--incremental)
+ {upstream} missing command to start *single* arrays in "auto-read" mode (like
--incremental)
** Also affects: mdadm
Importance: Undecided
Status: New
--
{upstream} missing comma
** Summary changed:
- inconsistency with the --no-degraded option
+ {upstream} inconsistency with the --no-degraded option
** Also affects: mdadm
Importance: Undecided
Status: New
--
{upstream} inconsistency with the --no-degraded option
https://bugs.launchpad.net/bugs/244810
You rece
** Summary changed:
- --incremental --scan --run does not start anything
+ [upstream] --incremental --scan --run does not start anything
** Summary changed:
- [upstream] --incremental --scan --run does not start anything
+ {upstream} --incremental --scan --run does not start anything
** Also af
how to remove issue from a LP project / reassign to another project?
** Package changed: mdadm (Ubuntu) => ubuntu
** Package changed: ubuntu => mdadm (Ubuntu)
--
{upstream} no console message when array is not created as specified
https://bugs.launchpad.net/bugs/491377
You received this bug not
To disable raid assembly by the kernel (before it is disabled in the
kernel config) add the boot option "raid=noautodetect".
--
enabled kernel raid autodetection disturbs udev/mdadm (initramfs & later)
https://bugs.launchpad.net/bugs/551719
You received this bug notification because you are a mem
** Changed in: mdadm (Ubuntu)
Status: New => Invalid
--
{upstream} madam: no devices found for /dev/md0
https://bugs.launchpad.net/bugs/403767
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
** Changed in: mdadm (Ubuntu)
Status: New => Invalid
--
{upstream} missing command to start *single* arrays in "auto-read" mode (like
--incremental)
https://bugs.launchpad.net/bugs/251646
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
** Changed in: mdadm (Ubuntu)
Status: New => Invalid
--
{upstream} inconsistency with the --no-degraded option
https://bugs.launchpad.net/bugs/244810
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubu
** Changed in: mdadm (Ubuntu)
Status: New => Invalid
--
{upstream} --incremental --scan --run does not start anything
https://bugs.launchpad.net/bugs/244808
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
** Changed in: mdadm (Ubuntu)
Status: New => Invalid
--
{upstream} Raid10,o2 only reads from a single disk
https://bugs.launchpad.net/bugs/320418
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
Instead of using the PPA from experimental branch, should manually
installing the grub2 package from lucid be ok?
** Changed in: grub2 (Ubuntu)
Status: In Progress => Fix Released
--
Current grub-pc takes several minutes to show menu
https://bugs.launchpad.net/bugs/420933
You received thi
*** This bug is a duplicate of bug 136252 ***
https://bugs.launchpad.net/bugs/136252
Hi, thanks for responding.
It's a duplicate if it works with one correct ARRAY line, but does not
work without any ARRAY line.
Bug #136252 [->UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not
assembli
Agreed.
Cryptsetup can just use blkid (if available) to safety check if the user
or a buggy/incorrect script of his is not trying to open a RAID type
device.
--
breaking raid: root raid_member opened as luks
https://bugs.launchpad.net/bugs/531240
You received this bug notification because you ar
I don't have the disks to reproduce raid10.
I went through the mdadm buglist that hasn't seen much caretaking for
long, sorting dupes etc. As this is issue is genereal (not packaging
related) I wanted to forward this to mdadm (not only mdadm in ubuntu). I
tried to do a reassigning but obviously t
** Changed in: mdadm (Ubuntu)
Status: Invalid => New
--
{upstream} madam: no devices found for /dev/md0
https://bugs.launchpad.net/bugs/403767
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
** Changed in: mdadm (Ubuntu)
Status: Invalid => New
--
{upstream} missing command to start *single* arrays in "auto-read" mode (like
--incremental)
https://bugs.launchpad.net/bugs/251646
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
** Changed in: mdadm (Ubuntu)
Status: Invalid => New
--
{upstream} inconsistency with the --no-degraded option
https://bugs.launchpad.net/bugs/244810
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubu
** Changed in: mdadm (Ubuntu)
Status: Invalid => New
--
{upstream} --incremental --scan --run does not start anything
https://bugs.launchpad.net/bugs/244808
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
** Summary changed:
- User Privileges ignored
+ user:group privileges ignored
** Summary changed:
- user:group privileges ignored
+ policykit breaking unix user/group privileges
--
policykit introduction broke unix user/group privileges
https://bugs.launchpad.net/bugs/326135
You received this
** Description changed:
I have set up a number of user accounts. On one of these accounts I
adjusted the user privileges (System->Administration->Users and
Groups->Properties->User Privileges). For one particular user I de-
selected the two options:
- * Connect to Internet using a m
concerning cryptsetup "wishlist":
Precautions like this show the level of safety and quality in
implementing basic OS operations. If cryptsetup would check the given
device before opening, this data loss would not occur now or any time
later if blkid, an admin or another script makes an error.
It
** Description changed:
Binary package hint: util-linux
After the member is opened as luks device it is booted instead of the md
device, while the raid remains "inactive".
I first noticed /proc/mdstat reported the root raid as inactive
(although the system seemed to run fine!).
** Summary changed:
- non-root raids fail to run degraded on boot
+ degraded non-root raids are not run on boot
--
degraded non-root raids are not run on boot
https://bugs.launchpad.net/bugs/259145
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
finaly found that "cryptsetup isLuks" is actually used in
scripts/local-top/cryptroot line 236:
if /sbin/cryptsetup isLuks $cryptsource > /dev/null 2>&1; then
Please remember to have the bootscripts output messages about what they
are doing and their results to the (hidden) text console.
Phillip, before suggesting something I try to think through the issue,
and the same I try with feedback.
But after several attempts to explain that changing metadata and
removing the "failed" status (of allready running parts) in the
superblocks of the conflicting parts that are plugged-in (but no
> whether some other component automatically invokes mdadm
> to move the second disk to a brand new array, or the admin has to by
> hand, I don't really care.
You are probably not aware enough that all udev/hotplug magic for raid
is within mdadm --incremental. I.e. in the future it will even set
u
** Also affects: gvfs (Ubuntu)
Importance: Undecided
Status: New
--
digikam cannot download pictures due to gvfsd-gphoto2
https://bugs.launchpad.net/bugs/288470
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
601 - 700 of 1101 matches
Mail list logo
