Do you actually use the name /dev/md_d0 in /etc/mdadm/mdadm.conf?
Maybe you updated the superblocks to that name but not mdadm.conf.
The following will recreate a static mdadm.conf and update the initramfs
images:
# start your array manually
# cp /etc/mdadm/mdadm.conf /etc/mdadm/mdadm.conf.bak
patch above
--
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-bugs@lists.ubuntu.com
attatching above patch again as a file upload in order for this issue
being listeted as containing patch.
** Attachment added: patch
http://launchpadlibrarian.net/42384132/patch
** Summary changed:
- mdadm -A device... fails
+ madam: no devices found for /dev/md0
--
madam: no devices found
Cann't you change the partition type with cfdisk?
sudo update-initramfs -k all -u will recreate your initramfs images
** Summary changed:
- apt-get install mdadm on a 8e partion type
+ initramfs images not recreated during uninstall
--
initramfs images not recreated during uninstall
** Summary changed:
- mdadm segfault when OTHER fs data= in fstab
+ segfault with data= option in fstab
--
segfault with data= option in fstab
https://bugs.launchpad.net/bugs/425213
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
A note for /etc/mdadm/mdadm.conf:
# ARRAY definitions you make here will be honored only when executing mdadm
manually.
# The mdadm calls executed on udev events do use this file replacing all lines
containing ARRAY.
--
[-UUIDudev] installing mdadm (or outdated mdadm.conf) breaks bootup
** Also affects: apport (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mdadm (Ubuntu)
Status: New = Invalid
--
ubuntu-bug mdadm - Fails due to permission denied
https://bugs.launchpad.net/bugs/442737
You received this bug notification because you are a member of
** Changed in: mdadm (Ubuntu)
Status: New = Fix Released
--
raid partition is not recognized during system startup
https://bugs.launchpad.net/bugs/446445
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
*** This bug is a duplicate of bug 136252 ***
https://bugs.launchpad.net/bugs/136252
From what you wrote the first ARRAY line should not be there. (You did
not create it after creating the array.)
So I suspect maybe you called dpkg-reconfigure mdadm or
/usr/share/mdadm/mkconf force-generate
Bug #442735 dmraid eats mdadm-managed raid in upgrading from 9.04 to
9.10
If you don't use sata fakeraid, try uninstalling dmraid and sudo
update-initramfs -k all -u.
--
RAID1 partitions created in Jaunty not recognised by Karmic
https://bugs.launchpad.net/bugs/538597
You received this bug
I think it was in 9.04 when udev switched to use mdadm --incremental.
So you reported what's discussed at
http://ubuntuforums.org/showthread.php?p=8407182, and experience those
Bug #550131 initramfs missing /var/run/mdadm dir (loosing state)
Bug #136252 [-UUIDudev] mdadm.conf w/o ARRAY lines but
Your old arrays probably work because they got written to mdadm.conf
during the update.
** Summary changed:
- mdadm does not remember its actions correctly
+ [-UUIDudev] new array not assembled correctly after reboot
** Changed in: mdadm (Ubuntu)
Status: New = Confirmed
--
[-UUIDudev]
workaround:
# start your arrays manualy
# /usr/share/mdadm/mkconf force-generate /etc/mdadm/mdadm.conf
# update-initramfs -k all -u
--
[-UUIDudev] new array not assembled correctly after reboot
https://bugs.launchpad.net/bugs/469574
You received this bug notification because you are a member of
Also dmraid eats mdadm-managed raid in upgrading from 9.04 to 9.10 Bug
#442735
** Summary changed:
- RAID5 partitions disappear after initial reboot
+ RAID5 partitions disappear after initial reboot [old superblocks]
--
RAID5 partitions disappear after initial reboot [old superblocks]
** Summary changed:
- initramfs' mdadm degrades all arrays (not just those required to boot)
+ initramfs' init-premount degrades *all* arrays (not just those required to
boot)
--
initramfs' init-premount degrades *all* arrays (not just those required to boot)
*** This bug is a duplicate of bug 497186 ***
https://bugs.launchpad.net/bugs/497186
** This bug has been marked a duplicate of bug 497186
initramfs' init-premount degrades *all* arrays (not just those required to
boot)
--
init-premount does mdadm --assemble --scan --run *all* arrays.
As long as the proper mdadm --incremental mode command (to start a
single array) is not available (Bug #251646) a workaround needs to be
used:
mdadm --remove incomplete-md-device arbitrary-member-device-of-
incomplete-array
mdadm --incremental --run arbitrary-member-device-of-incomplete-array
Have a look at dmraid eats mdadm-managed raid in upgrading from 9.04 to
9.10 Bug #442735
** Summary changed:
- jaunty 1st boot: second drive not found
+ jaunty 1st boot: second drive not found [old superblocks]
** Summary changed:
- jaunty 1st boot: second drive not found [old superblocks]
+
** Summary changed:
- mdadm 2.6.7.1-1ubuntu8 fails to install (missing obsolete /dev/MAKEDEV)
+ install fails missing obsolete /dev/MAKEDEV
--
install fails missing obsolete /dev/MAKEDEV
https://bugs.launchpad.net/bugs/368986
You received this bug notification because you are a member of Ubuntu
** Summary changed:
- mdadm uses one more spare that specified while creating a RAID5 array
+ mdadm uses one more spare than specified while creating a RAID5 array
--
mdadm uses one more spare than specified while creating a RAID5 array
https://bugs.launchpad.net/bugs/491377
You received this
** Changed in: mdadm (Ubuntu)
Status: New = Confirmed
--
initramfs' init-premount degrades *all* arrays (not just those required to boot)
https://bugs.launchpad.net/bugs/497186
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Wait, you created the arrays by hand, mdadm --create does not put
anything in mdadm.conf and you are experiencing:
Bug #136252 [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not
assembling arrays. (boot fails)
Bug #550131 initramfs missing /var/run/mdadm dir (loosing state)
--
mdadm,
Does that workaround help?
Bug #469574 [-UUIDudev] new array not assembled correctly after reboot
--
[-UUIDudev] mdadm fails to assemble raid during boot
https://bugs.launchpad.net/bugs/541058
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I meant the workaround in Bug #469574. Does it help without applying
Sami's?
--
[-UUIDudev] mdadm fails to assemble raid during boot
https://bugs.launchpad.net/bugs/541058
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Summary changed:
- mdadm uses one more spare than specified while creating a RAID5 array
+ no console message when array is not created as specified
--
no console message when array is not created as specified
https://bugs.launchpad.net/bugs/491377
You received this bug notification because
** Summary changed:
- old raid superblocks can prevent formating a new partition
+ can not format new partition [old superblocks]
--
can not format new partition [old superblocks]
https://bugs.launchpad.net/bugs/342777
You received this bug notification because you are a member of Ubuntu
Bugs,
** Summary changed:
- harsh crashes during mdadm rebuild [SCARING!!!]
+ harsh crashes during mdadm rebuild [-Update]
** Changed in: mdadm (Ubuntu)
Status: Fix Committed = Fix Released
--
harsh crashes during mdadm rebuild [-Update]
https://bugs.launchpad.net/bugs/344748
You received
** Summary changed:
- RAID1 partitions created in Jaunty not recognised by Karmic
+ RAID1 partitions created in Jaunty not recognised by Karmic [old superblocks?]
--
RAID1 partitions created in Jaunty not recognised by Karmic [old superblocks?]
https://bugs.launchpad.net/bugs/538597
You
Well the initramfs boot process needs to be (a state machine) capable of
assembling the base system from devices appearing in any order and
starting necessary raids degraded if they are not complete after some
time.
Bug #491463 upstart init within initramfs
Bug #251164 boot impossible due to
Well the initramfs boot process needs to be (a state machine) capable of
assembling the base system from devices appearing in any order and
starting necessary raids degraded if they are not complete after some
time.
Bug #491463 upstart init within initramfs
Bug #251164 boot impossible due to
Oh, no. Sorry made last comment #8 in wrong tab.
--
raid setups fail due to mdadm.conf with explicit ARRAY statements and HOMEHOST
!=any
https://bugs.launchpad.net/bugs/252345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Summary changed:
- mdadm, not using uid of the array breaks after a reboot of a new install
+ [-UUIDudev] mdadm, not using uid of the array breaks after a reboot of a new
install
--
[-UUIDudev] mdadm, not using uid of the array breaks after a reboot of a new
install
** Summary changed:
- installed system fails to boot with degraded raid holding cryptdisk
+ [-Initramfs] boot fails with degraded raid
** Summary changed:
- [-Initramfs] boot fails with degraded raid
+ [-Initramfs] no degraded boot lvm-luks-raid
--
[-Initramfs] no degraded boot lvm-luks-raid
** Summary changed:
- [-UUIDudev] 9.04 upgrade lose my Raid1
+ [-UUIDudev] 8.109.04 upgrade lost raid1
--
[-UUIDudev] 8.109.04 upgrade lost raid1
https://bugs.launchpad.net/bugs/368428
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Summary changed:
- RAID1 partitions created in Jaunty not recognised by Karmic [old superblocks?]
+ RAID1 partitions created in 9.04 not recognised 9.10 [old superblocks?]
--
9.10 not recognizing 9.04 partitions [old superblocks?]
https://bugs.launchpad.net/bugs/538597
You received this bug
** Summary changed:
- [-UUIDudev] mdadm, not using uid of the array breaks after a reboot of a new
install
+ [-UUIDudev] mdadm.conf without ARRAY definition breaks reboot new arrays
** Summary changed:
- [-UUIDudev] mdadm.conf without ARRAY definition breaks reboot new arrays
+ [-UUIDudev]
** Summary changed:
- RAID1 partitions created in 9.04 not recognised 9.10 [old superblocks?]
+ 9.10 not recognizing 9.04 partitions [old superblocks?]
--
9.10 not recognizing 9.04 partitions [old superblocks?]
https://bugs.launchpad.net/bugs/538597
You received this bug notification because
** Summary changed:
- option to start selected arrays in auto-read mode (like --incremental)
+ missing option to start selected arrays in auto-read mode (like
--incremental)
** Summary changed:
- missing option to start selected arrays in auto-read mode (like
--incremental)
+ missing command
** Summary changed:
- /dev/md_* devices are not created in /dev
+ /dev/md_* devices are not created
** Summary changed:
- /dev/md_* devices are not created
+ [-UUIDudev] /dev/md_* devices are not created
--
[-UUIDudev] /dev/md_* devices are not created
https://bugs.launchpad.net/bugs/486361
Because md* and md_d* device names aren't uniqe and can collide, if
superblocks and mdadm.conf ARRAY lines don't match devices are not
created.
This should be solved with pure UUID-based raid assembly. Bug #158918
** Changed in: mdadm (Ubuntu)
Status: New = Confirmed
--
[-UUIDudev]
assuming this incomplete report its amoung the fixes upstream, to
unclutter the buglist
** Changed in: mdadm (Ubuntu)
Status: Incomplete = Fix Released
--
mdadm crashed with SIGSEGV in __libc_start_main()
https://bugs.launchpad.net/bugs/344018
You received this bug notification because
no activity for long assuming fix released
** Changed in: mdadm (Ubuntu)
Status: Confirmed = Fix Released
--
mdadm causes boot to hang for 4 minutes
https://bugs.launchpad.net/bugs/67299
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Does Bug #550131 initramfs missing /var/run/mdadm dir (loosing state)
fix this?
--
mdadm does not add spares to arrays on boot
https://bugs.launchpad.net/bugs/252365
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Is this still an issue with newer releases?
** Changed in: mdadm (Ubuntu)
Status: Confirmed = Incomplete
--
mdadm problems after suspend
https://bugs.launchpad.net/bugs/181888
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Summary changed:
- degraded non-root raids don't appear on boot
+ degraded NON-root raids never --run on boot
--
degraded NON-root raids never --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
** Description changed:
Systems with say /home on raid won't come up booting when raid was
degraded during downtime.
An init script like /etc/init.d/mdadm-degrade - or because of already
doing that kind of watchdog functionality - mountall needs to --run
particular necessary arrays
non working boot is covered in more detail by other reports
this may be due to forgotten update-initramfs -u -k all
the release note seems to be about a debconf misconfiguration because
dpkg-reconfigure fixes it
** Changed in: mdadm (Ubuntu)
Status: Confirmed = Fix Released
--
Ubuntu
*** This bug is a duplicate of bug 298481 ***
https://bugs.launchpad.net/bugs/298481
** Tags removed: boot hangs on raid software
** This bug has been marked a duplicate of bug 298481
/dev/disk/by-uuid not set up reliably (sometimes boot is failing)
--
Software raid hangs on boot after
assuming this is one of the crashes fixed upstream
** Changed in: mdadm (Ubuntu)
Status: Incomplete = Fix Committed
--
harsh crashes during mdadm rebuild [SCARING!!!]
https://bugs.launchpad.net/bugs/344748
You received this bug notification because you are a member of Ubuntu
Bugs, which
assuming this is one of the crashes fixed upstream
** Changed in: mdadm (Ubuntu)
Status: Confirmed = Fix Committed
--
shipped old mdadm version crashes with SIGSEGV in __libc_start_main() after
grow interrupted
https://bugs.launchpad.net/bugs/315721
You received this bug notification
Assuming segfault is amoung the fixes upstream or even already in more
recent releases.
** Changed in: mdadm (Ubuntu)
Status: Incomplete = Fix Released
--
Mdadm segfault on booting Hardy
https://bugs.launchpad.net/bugs/252485
You received this bug notification because you are a member of
** Summary changed:
- package mdadm 2.6.7.1-1ubuntu8 failed to install, with error /dev/MAKEDEV not
found
+ mdadm 2.6.7.1-1ubuntu8 fails to install (missing obsolete /dev/MAKEDEV)
--
mdadm 2.6.7.1-1ubuntu8 fails to install (missing obsolete /dev/MAKEDEV)
https://bugs.launchpad.net/bugs/368986
Is this still an issue with newer releases?
Are you sure this is not an issue with sata/pata drivers or bios
settings?
** Summary changed:
- Jaunty install failure with Software RAID (mdadm)
+ jaunty 1st boot: second drive not found
** Changed in: mdadm (Ubuntu)
Status: New = Incomplete
*** This bug is a duplicate of bug 136252 ***
https://bugs.launchpad.net/bugs/136252
A quick workaround to apply before rebooting in in Bug #252345
** This bug has been marked a duplicate of bug 136252
[-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling
arrays. (boot
** Summary changed:
- DeviceDisappeared/Wrong-Level
+ monitoring raid0 floods syslog with DeviceDisappeared/Wrong-Level
** Description changed:
Binary package hint: mdadm
- In the man page it is well documented that monitoring a raid0 device
- will result in an error message like this:
+
Public bug reported:
Binary package hint: mdadm
mdadm --incremental will save state in a map file under
/var/run/mdadm/map.
But in initramfs and early boot this directory does not exist.
The state is then saved in /var/run/mdadm.map.new (man page incorrectly
says /var/run/mdadm.map) and not
Thanks for clarifying Sami.
I had seen that missing dir before, and now filed the separate Bug
#550131, could you add/confirm info there about the error you
encountered with /var/run/mdadm missing.
--
[karmic] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays.
(boot fails)
** Summary changed:
- boot: initramfs missing dir /var/run/mdadm
+ initramfs missing /var/run/mdadm dir (loosing state)
--
initramfs missing /var/run/mdadm dir (loosing state)
https://bugs.launchpad.net/bugs/550131
You received this bug notification because you are a member of Ubuntu
Bugs,
We are missing pure and secure UUID-only incremental assembly (i.e.
allowing DEVICES partititions, ARRAY any and HOMEHOST any).
One that would create unique disk/by-uuid nodes and by-label symlinks
(the later might get numbered on conflicts). This scheme may not even
expose any of the generally
What did you use? Here (9.10) the alternate installer created mdadm.conf
with lines like these
ARRAY /dev/md0 level=raid1 num-devices=2 UUID=...
(no member device names)
--
mdadm, not using uid of the array breaks after a reboot of a new install
https://bugs.launchpad.net/bugs/532960
You
setting to fix commited as uuids are used now
** Changed in: mdadm (Ubuntu)
Status: Confirmed = Fix Committed
--
boot confused after stopping array
https://bugs.launchpad.net/bugs/38438
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
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
** 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
err, released
** Changed in: mdadm (Ubuntu)
Status: Fix Committed = Fix Released
--
boot confused after stopping array
https://bugs.launchpad.net/bugs/38438
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing
what I don't get is why a broken array (with no mount point specified)
would result in an unbootable system.
This is again the glorious mdadm thing of setting up arrays according to
unreliable superblock information (device minor numbers, labels,
hostnames) combined with the idea of fixing the
** Description changed:
Binary package hint: mdadm
Hi,
I could not boot from my /dev/md1 - /dev/vg01/lv_root partition,
because the initrd could not assemble the md0 and md1 devices. After
reading mdadm.conf, I added these two lines to my config:
# definitions of existing MD
You can't rely on device numbering and it's a seriously flawed design of mdadm
to set up arrays according to unreliable superblock information. (device
minor numbers, labels, hostnames) The idea of fixing the unreliability by
limiting array assembly with mdadm.conf (PARTITIONS, ARRAY, HOMEHOST
The solution is a reliable UUID-based raid assembly mechanism.
One that does not depend on ARRAY definitions in mdadm.conf. At the same
time making sure never to create devices named equal to the legacy
'standard' non-uniqe and non-persistent naming scheme /dev/md0 etc.
causing much havoc.
** Description changed:
Binary package hint: mdadm
On a freshly installed ubuntu-7.10-alternate, with latest apt-get
update.
When the 'mdadm' package is installed, the system fails to boot
successfully, and ends up at the initrd '(busybox)' prompt.
Hardware: DELL 1950 - 1RU
Hey, it's also a solution to Bug #158918 (improved there).
--
[karmic] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays.
(boot fails)
https://bugs.launchpad.net/bugs/136252
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
You need to check this with upsteam.
--
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 mailing list
ubuntu-bugs@lists.ubuntu.com
Wherever that is, found no bug tracker.
http://www.linuxfoundation.org/collaborate/workgroups/linux-raid
--
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
** Changed in: mdadm (Ubuntu)
Status: New = Incomplete
--
Mdadm.conf deleted during update.
https://bugs.launchpad.net/bugs/200266
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
*** This bug is a duplicate of bug 120504 ***
https://bugs.launchpad.net/bugs/120504
vol_id has been replaced with blkid by now
** This bug has been marked a duplicate of bug 120504
mdadm : boot failed sometimes, no devices found
--
No devices listed in conf file were found due to mdadm
UUID-based hotplug raid assembly that does not depend on mdadm.conf
maintanance fixes this, too. #158918
--
mkinitramfs with raid makes an unbootable image
https://bugs.launchpad.net/bugs/116727
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Is this still an issue with recent releases?
** Changed in: mdadm (Ubuntu)
Status: Confirmed = Incomplete
--
mdadm fails to stop RAID on shutdown
https://bugs.launchpad.net/bugs/111398
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
setting fix realased
** Changed in: mdadm (Ubuntu)
Status: Confirmed = Fix Released
--
mdadm SEGFAULT
https://bugs.launchpad.net/bugs/108553
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Is this still an issue with recent releases?
** Changed in: mdadm (Ubuntu)
Status: Confirmed = Incomplete
--
initramfs hook script exits prematurely creating bad defaults
https://bugs.launchpad.net/bugs/82653
You received this bug notification because you are a member of Ubuntu
Bugs,
Is this still an issue with recent releases? mdrun isn't around anymore
** Changed in: mdadm (Ubuntu)
Status: Confirmed = Invalid
--
mdrun fails if large disk present, thus boot fails.
https://bugs.launchpad.net/bugs/57972
You received this bug notification because you are a member of
Cleaning up old bugs, this did not occur on subsequent updates, right?
** Changed in: mdadm (Ubuntu)
Status: Incomplete = Fix Released
--
Mdadm.conf deleted during update.
https://bugs.launchpad.net/bugs/200266
You received this bug notification because you are a member of Ubuntu
Bugs,
UUID-based raid assembly makes mdadm.conf ARRAY definitions obsolete
anyway.
--
Mdadm.conf deleted during update.
https://bugs.launchpad.net/bugs/200266
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
(In this context I understand your comment, Sami.)
With UUID-based raid assembly not depending on mdadm.conf ARRAY
definition maintanance this is no issue. Bug #158918
** Summary changed:
- mdadm fails to assemble raid during boot
+ [-UUIDudev] mdadm fails to assemble raid during boot
--
** Summary changed:
- Installing mdadm (or outdated mdadm.conf) breaks bootup
+ [-UUIDudev] installing mdadm (or outdated mdadm.conf) breaks bootup
--
[-UUIDudev] installing mdadm (or outdated mdadm.conf) breaks bootup
https://bugs.launchpad.net/bugs/158918
You received this bug notification
** Summary changed:
- [karmic] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays.
(boot fails)
+ [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling
arrays. (boot fails)
** Description changed:
Binary package hint: mdadm
Hi,
I could not boot from
** Summary changed:
- initramfs/mdrun doesn't honor preferred minor when starting RAID volumes
+ [-UUIDudev] initramfs/mdrun doesn't honor preferred minor when starting RAID
volumes
--
[-UUIDudev] initramfs/mdrun doesn't honor preferred minor when starting RAID
volumes
** Summary changed:
- mkinitramfs with raid makes an unbootable image
+ [-UUIDudev] mkinitramfs with raid makes an unbootable image
--
[-UUIDudev] mkinitramfs with raid makes an unbootable image
https://bugs.launchpad.net/bugs/116727
You received this bug notification because you are a member
workaround sequence:
mdadm --remove incomplete-md-device arbitrary-member-device-of-
incomplete-array
mdadm --incremental --run arbitrary-member-device-of-incomplete-array
--
option to start selected arrays in auto-read mode (like --incremental)
https://bugs.launchpad.net/bugs/251646
You
doesn't happen in 9.10
** Changed in: mdadm (Ubuntu)
Status: New = Fix Released
--
Segfault when readding hotplug devices
https://bugs.launchpad.net/bugs/244803
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
current releases are using --incremental
** Changed in: mdadm (Ubuntu)
Status: New = Fix Released
--
--incremental not creating device nodes
https://bugs.launchpad.net/bugs/251663
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'd consider the missing modules issue as fix released, right?
Christian Reis, does the race still occur in recent releases?
Why is initramfs udev killed instead of transitioned to the rootfs?
https://wiki.ubuntu.com/ReliableRaid
** Changed in: initramfs-tools
Status: New = Fix Released
Is this still an issue with recent releases using UUIDs in mdadm.conf?
** Changed in: mdadm (Ubuntu)
Status: New = Incomplete
--
Mdadm segfault on booting Hardy
https://bugs.launchpad.net/bugs/252485
You received this bug notification because you are a member of Ubuntu
Bugs, which is
With UUID-based raid assembly that does not rely on mdadm.conf
maintanance this is not an issue. Bug #158918
** Summary changed:
- mdadm software raid breaks on intrepid-jaunty upgrade
+ [-UUIDudev] mdadm software raid breaks on intrepid-jaunty upgrade
--
[-UUIDudev] mdadm software raid
Intrepid Ibex (whatever number that is) has 2.6.7
8.10 has 2.6.3+
** Changed in: mdadm (Ubuntu)
Status: Confirmed = Fix Released
--
mdadm cannot resume array reshape
https://bugs.launchpad.net/bugs/25
You received this bug notification because you are a member of Ubuntu
Bugs, which
ok, marking invalid to unclutter the bug list
** Changed in: mdadm (Ubuntu)
Status: New = Invalid
--
installation of mdadm causes freeze during boot of Hardy
https://bugs.launchpad.net/bugs/259797
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Description changed:
- Binary package hint: mdadm
- It is said that the intrepid fix to Bug #120375 re-added support to
- mdadm and initramfs-tools for configurable booting degraded RAIDs, but a
- systems with /home on a degraded array doesn't come up.
+ Systems with say /home on raid
seems or seemed to be an issue with dpkg or something (search bugs with
rm: cannot remove)
** Changed in: powermgmt-base (Ubuntu)
Status: Confirmed = Incomplete
--
[Jaunty] rm: cannot remove 'apm-bios-'
https://bugs.launchpad.net/bugs/294269
You received this bug notification because
seems or seemed to be a general issue with dpkg or udev or something
(search bugs with rm: cannot remove)
** Changed in: libraw1394 (Ubuntu)
Status: New = Incomplete
--
rm: cannot remove `raw1394-': Read-only file system
https://bugs.launchpad.net/bugs/302380
You received this bug
seems or seemed to be a general issue with dpkg or udev or something
(search bugs with rm: cannot remove)
** Changed in: sane-backends (Ubuntu)
Status: New = Incomplete
--
Update Throws errors but completes
https://bugs.launchpad.net/bugs/314875
You received this bug notification because
seems or seemed to be a general issue with dpkg or udev or something
(search bugs with rm: cannot remove)
** Changed in: lm-sensors-3 (Ubuntu)
Status: New = Incomplete
--
Read-only file system errors during install
https://bugs.launchpad.net/bugs/329792
You received this bug notification
seems or seemed to be a general issue with dpkg or udev or something
(search bugs with rm: cannot remove)
--
Read-only file system errors during install
https://bugs.launchpad.net/bugs/329792
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
501 - 600 of 1115 matches
Mail list logo
