** Summary changed:
- breaking raid: root raid_member opened as luks
+ silently breaking raid: root raid_members opened as luks
--
silently breaking raid: root raid_members opened as luks
https://bugs.launchpad.net/bugs/531240
You received this bug notification because you are a member of Ubuntu
** 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:
- This is not a support forum. Please do not use it as such (even though
- it has been used as such already).
+ The kernel wiki gathers info about drives with too aggressive power saving
defaults. A script called "storage-fixup" is also available.
+
https://ata.wiki.kern
Could you maybe post the mdadm.conf and try what happens if you
(temporarily) change the homehost of array members to somthing
different, to make sure what problem got solved.
-mdadm.conf "DEVICE partitions" has mdadm consider any partition available to
the system.
-mdadm.conf ARRAY is present i
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 p
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)
https:
** 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, which
We are missing pure and secure UUID-only incremental assembly (i.e.
allowing "DEVICES partititions", "ARRAY " and "HOMEHOST ").
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 ar
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 receiv
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 subscrib
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
** 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, HOMEHOS
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.
Withou
** 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 Se
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
http
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 Ubu
** 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
ubuntu-bugs@lists.ubu
*** 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 mdad
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 Ubu
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 Ubun
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
ubuntu-bug
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, whi
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 Ub
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, w
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
ubuntu-
(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 b
** 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 m
** 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
https://bugs.launchpad
** 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
mdadm --incremental --run
--
option to start selected 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 Ubuntu.
--
ub
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 mai
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 sub
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 bre
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 subscr
** 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 won'
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 noti
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 becau
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 notifica
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 Ub
seems or seemed to be a general issue with dpkg or udev or something
(search bugs with "rm: cannot remove")
--
irda-utils error during installation
https://bugs.launchpad.net/bugs/317528
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
seems or seemed to be a general issue with dpkg or udev or something
(search bugs with "rm: cannot remove")
--
intrepid - rm: cannot remove `md0-': Read-only file system
https://bugs.launchpad.net/bugs/270043
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Maybe this is actually a kernel / module issue. Are those
controllers/disks also so slow with other OS?
Still valid with current releases?
** Summary changed:
- Intrepid ubuntu server won't boot RAID1
+ disk detection is real slow with some hardware (timout shell drops)
** Also affects: linux (
Concerning RAID degradiation, as RAIDs may take minutes until they come up, but
regular ones are quick, this should be handled nicely:
"NOTICE: /dev/mdX required for the root filesystem didn't get up
within the last 10 seconds.
We continue to wait up to a total of xxx seconds comply
** Description changed:
I have installed Intrepid server i386 beta on a Dell PowerEdge 600SC.
Everything seemed to install fine but upon boot it always drops into the
BusyBox shell. The RAID is *not* degraded. At the BusyBox prompt if I
type 'exit' it will proceed to boot normally and both
9.10 here
#ls -l /dev/disk/by-uuid/$ ls -l /dev/disk/by-uuid/
insgesamt 0
lrwxrwxrwx 1 root root 26 2010-03-28 11:35 0a. -> ../../mapper/vg-root
lrwxrwxrwx 1 root root 10 2010-03-28 11:35 1e. -> ../../sda1
lrwxrwxrwx 1 root root 23 2010-03-28 11:35 35. -> ../../mapper/vg-home
lrwxrwxrw
well this made it into the 9.10 release notes
** Changed in: mdadm (Ubuntu)
Status: New => Confirmed
--
Ubuntu asks me what I want to do even if I set BOOT_DEGRADED=true in Ubuntu 8.10
https://bugs.launchpad.net/bugs/291488
You received this bug notification because you are a member of Ub
BOOT_DEGRADED=YES does actually not work in most cases because of Bug
#251164 "boot impossible due to missing initramfs failure hook / event
driven initramfs", see also https://wiki.ubuntu.com/ReliableRaid
--
Ubuntu asks me what I want to do even if I set BOOT_DEGRADED=true in Ubuntu 8.10
https:/
is this still an issue with recent releases?
** Summary changed:
- Problem booting raid 1 since upgrading to intrepid (uuid missing)
+ /dev/disk/by-uuid not set up reliably
** Description changed:
+ ( since upgrading to intrepid )
+
When booting, the system cannot find the /dev/disk-by-uuid
sound just like Bug #298481
** Changed in: mdadm (Ubuntu)
Status: New => Incomplete
--
Software raid hangs on boot after upgrade to 8.10
https://bugs.launchpad.net/bugs/302061
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
** Summary changed:
- mdadm crashed with SIGSEGV in __libc_start_main() after grow interrupted
+ shipped old mdadm version crashes with SIGSEGV in __libc_start_main() after
grow interrupted
--
shipped old mdadm version crashes with SIGSEGV in __libc_start_main() after
grow interrupted
https:/
** Summary changed:
- mdadm segfault on rebuild of raid5
+ shipped (old) mdadm version segfaults on rebuild of raid5
** Changed in: mdadm (Ubuntu)
Status: New => Fix Released
--
shipped (old) mdadm version segfaults on rebuild of raid5
https://bugs.launchpad.net/bugs/320950
You received
*** This bug is a duplicate of bug 251164 ***
https://bugs.launchpad.net/bugs/251164
This is Bug #251164 boot impossible due to missing initramfs failure
hook / event driven initramfs
** This bug has been marked a duplicate of bug 251164
boot impossible due to missing initramfs failure hoo
This should be no issue with UUID-based raid assembly that makes
mdadm.conf ARRAY definition maintanance obsolete.
** Summary changed:
- MD/LVM boot broken
+ [->UUIDudev] MD/LVM boot broken
--
[->UUIDudev] MD/LVM boot broken
https://bugs.launchpad.net/bugs/328892
You received this bug notificat
This should be no issue with UUID-based raid assembly that makes
mdadm.conf ARRAY definition maintenance obsolete. Bug #158918
** Summary changed:
- "HOMEHOST " does not work inside initrd
+ [->UUIDudev] "HOMEHOST " does not work inside initrd
** Changed in: mdadm (Ubuntu)
Status: New =>
UUID-based raid assembly: Bug #158918
--
[->UUIDudev] MD/LVM boot broken
https://bugs.launchpad.net/bugs/328892
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.ubunt
Is this still an issue with recent releases?
Maye related to udev state or mdadm --incremental map not transitioned
from initramfs to rootsystem?
** Changed in: mdadm (Ubuntu)
Status: New => Incomplete
--
race condition finding devices for RAID group
https://bugs.launchpad.net/bugs/34183
** Changed in: mdadm (Ubuntu)
Status: New => Fix Released
--
mdadm docs include broken ostenfeld.dk link
https://bugs.launchpad.net/bugs/344556
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bu
With mdadm --zero-superblock you can remove md info from the partition
(prior to deleting the partition table entry)
Otherwise dd zeros to the partition or try to use the --force
mkfs/gparted.
** Summary changed:
- Old raid array blocks format of new partition
+ old superblocks can prevent forma
May be related to other bugreports about segfaults occuring with older mdadm
versions.
Is this still an issue with recent releases?
** Changed in: mdadm (Ubuntu)
Status: New => Incomplete
--
harsh crashes during mdadm rebuild [SCARING!!!]
https://bugs.launchpad.net/bugs/344748
You receiv
*** This bug is a duplicate of bug 251164 ***
https://bugs.launchpad.net/bugs/251164
This would be fixed with Bug #251164 boot impossible due to missing
initramfs failure hook / event driven initramfs
** Description changed:
- My linux system isn't booting anymore.
+ My linux system isn't bo
** Also affects: mdadm (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mdadm (Ubuntu)
Status: New => Confirmed
--
boot impossible due to missing initramfs failure hook / event driven initramfs
https://bugs.launchpad.net/bugs/251164
You received this bug notification be
non-root filesystems that get degraded on power down are actually never
explicity run (Bug #259145 "degraded non-root raids are not run on
boot".)
However mdadm's init-premount however watches *all* ARRAYS stated in
initramfs' mdadm.conf and indiscriminately executes mdadm --assemble
--scan --run,
Public bug reported:
Binary package hint: mdadm
mdadm's init-premount watches all ARRAYS stated in initramfs' mdadm.conf
and indiscriminately executes "mdadm --assemble --scan --run", starting
*all* arrays that are present with enough redundancy.
This is not good since some collateral arrays may
Err, bad since some collateral arrays may be available incompletely
(only due to the early stage during boot) and the method used is not
designed for later additions with and like mdadm --incremental. (Bug
#550634 )
--
[->UUIDudev] Raid 1 configuration failed to start on boot
https://bugs.launchp
can you check the info in the superblocks of /dev/md/2?
** Changed in: mdadm (Ubuntu)
Status: New => Incomplete
** Summary changed:
- Raid 1 configuration failed to start on boot
+ [->UUIDudev] Raid 1 configuration failed to start on boot
--
[->UUIDudev] Raid 1 configuration failed to s
UUID-based raid assembly that makes mdadm.conf maintenance obsolete
fixes this.
** Summary changed:
- bad mdadm.conf on jaunty upgrade
+ [->UUIDudev] bad mdadm.conf on jaunty upgrade
--
[->UUIDudev] bad mdadm.conf on jaunty upgrade
https://bugs.launchpad.net/bugs/366204
You received this bug no
UUID-based raid assembly that makes mdadm.conf maintenance obsolete
fixes this.
** Summary changed:
- 9.04 upgrade lose my Raid1
+ [->UUIDudev] 9.04 upgrade lose my Raid1
** Changed in: mdadm (Ubuntu)
Status: New => Confirmed
--
[->UUIDudev] 9.04 upgrade lose my Raid1
https://bugs.launc
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
mdadm --incremental --run
--
init-premount does "mdadm --assemble --scan --run" *all* arrays.
https://bugs.launchpad.net/bugs/550634
You
** 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!).
confirmed from Bug #541058 and #136252
** Description changed:
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.n
maybe Bug #550131
--
/dev/disk/by-uuid not set up reliably (sometimes boot is failing)
https://bugs.launchpad.net/bugs/298481
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
is this still an issue with recent releases?
** Changed in: mdadm (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: mdadm (Ubuntu)
Status: Incomplete => Fix Released
--
[apport] mdadm crashed with SIGSEGV
https://bugs.launchpad.net/bugs/96543
You received this bug notificati
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 maili
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 t
** 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 array
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
--
Ubunt
*** 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 u
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 be
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
Y
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 fa
** 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:
+ I
** Description changed:
Binary package hint: mdadm
Anybody who cares about redundancy to use mdadm probably cares enough
about redundancy to want being informed if redundancy is degraded.
Debian systems do have at least local mail enabled and package mdadm
asks for a mail address t
** Description changed:
Binary package hint: mdadm
Anybody who cares about redundancy to use mdadm probably cares enough
about redundancy to want being informed if redundancy is degraded.
Debian systems do have at least local mail enabled and package mdadm
asks for a mail address t
On the other hand mdadm "recommends" postfix | mail-transport-agent.
So a synaptic install (not the initial install) seems to pull in postfix
on Desktops!
Bug #379882
--
mdadm monitor feature broken, not depending on local MTA/MDA or using
wall/notify-send
https://bugs.launchpad.net/bugs/53541
The monitoring facility of mdadm is very important to get notice if
somthing goes wrong with your raid.
So you can replace disks etc. ahead of a total failure.
To send out notifications mdadm needs a sendmail command (MTA mail
transport agent ).
To deliver mail localy you need a mail delivery a
causticsoda: what release were you using?
** Changed in: mdadm (Ubuntu)
Status: Fix Released => Confirmed
--
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.
--
ubuntu-
201 - 300 of 1101 matches
Mail list logo
