Current mdadm in 9.10 has "recommends": postfix | mail-transport-agent.
My installation did not pull in an MTA. Did you use synaptic that treats
"recommends" as "requires"?
** Changed in: mdadm (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: mdadm (Ubuntu)
Status: Fix Rel
Bug #535417: mdadm monitor feature broken, not depending on local
MTA/MDA or using wall/notify-send
** Changed in: mdadm (Ubuntu)
Status: New => Fix Released
--
mdadm installs postfix
https://bugs.launchpad.net/bugs/379882
You received this bug notification because you are a member of Ubu
** Summary changed:
- Cannot make mdadm autocreate raid1 after crash
+ mdadm assembling -but not auto assembling- after crash
--
mdadm assembling -but not auto assembling- after crash
https://bugs.launchpad.net/bugs/381183
You received this bug notification because you are a member of Ubuntu
Bug
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
https://lists.ubuntu.com/mailman/listinf
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 fo
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
https://
** 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.
--
ub
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
htt
** 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 Ubun
** 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 lis
*** 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-genera
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 not
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]
https:
** 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)
https://bugs.launchpad.net/bugs/497
*** 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
mdadm --incremental --run
** Description changed:
- Binary package hint: mdadm
-
- after a timeout mdadm in initrams degrades all ar
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 bu
** 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, no
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 Ubu
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 y
** 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, w
** 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 t
** 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 received
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 missi
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 missi
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.
--
ubuntu-b
** 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
https://bugs.launchpad
** 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-ra
** Summary changed:
- [->UUIDudev] 9.04 upgrade lose my Raid1
+ [->UUIDudev] 8.10>9.04 upgrade lost raid1
--
[->UUIDudev] 8.10>9.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 n
** 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 you
** 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 com
** 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] /de
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 y
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 Ub
** Description changed:
- Binary package hint: mdadm
+ (also confirmed for 9.10 and 10.04)
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)' pro
** Description changed:
- (also confirmed for 9.10 and 10.04)
+ Original Report (also confirmed with 9.10 and 10.04 beta1):
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
** Description changed:
Original Report (also confirmed with 9.10 and 10.04 beta1):
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.
Solution found in comment #15 of Bug #251164
** Summary changed:
- [->Initramfs] no degraded boot lvm-luks-raid
+ [->Initramfs] no degraded boot (arbitrary lvm, luks, raid, auth, ...
combinations)
--
[->Initramfs] no degraded boot (arbitrary lvm, luks, raid, auth, ...
combinations)
https://bu
** Description changed:
the cryptsetup package needs proper integration into the initramfs
failure hooks
The system must not assume a particular layered setup or sequence of
appearance of (hotplug/udev/crypt/md/degraded-md/lvm) devices.
It must be able to boot with any possible com
** Summary changed:
- initramfs missing /var/run/mdadm dir (loosing state)
+ initramfs missing /var/run/mdadm/ dir (loosing state, race, misconfig)
--
initramfs missing /var/run/mdadm/ dir (loosing state, race, misconfig)
https://bugs.launchpad.net/bugs/550131
You received this bug notification
** Summary changed:
- [->UUIDudev] 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 & hotplug fails)
--
[->UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling ar
** Description changed:
After a timeout mdadm in initrams degrades all arrays instead of just
those required for the rootfs.
This is not good since non-rootfs arrays are likely to be available only
incompletely (due to the early stage during boot) and are getting
desynced by this.
** 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
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
ubuntu 9.04 overheat notebook, to the point of locking the computer.
https://bugs.launchpad.net/bugs/432833
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
closing as it was a bios issue
** Changed in: acpi (Ubuntu)
Status: New => Invalid
--
ACPI fan control problem by ACER
https://bugs.launchpad.net/bugs/209837
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
This looks like a duplicate of Bug #370173, see there for possible
workarounds.
--
Aspire 5315-2713 overheats shuts down using Ubuntu 9.10
https://bugs.launchpad.net/bugs/525756
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
see also Bug #370173
--
[STAGING] Critical temperature reached (100 C), shutting down. throttling too
little, too late.
https://bugs.launchpad.net/bugs/563815
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
see also Bug #370173
--
Lucid makes Acer 5315 overheat and shut down
https://bugs.launchpad.net/bugs/532978
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.ubuntu.co
debian says fixed in v42
** Changed in: partman-md (Ubuntu)
Status: Confirmed => Fix Released
--
dm-crypt on raid - entry in /target/etc/crypttab missing
https://bugs.launchpad.net/bugs/268613
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
Binary package hint: partman-md
Partman fails if you try to set up raid with existing raid superblocks on some
devices. (i.e. on re-installs/updates, if you want to reuse or even if you
deleted exsiting raid partitions/devices.)
Partman may get confused as raid devices ge
** Description changed:
Binary package hint: partman-md
-
- Partman fails if you try to set up raid with existing raid superblocks on
some devices. (i.e. on re-installs/updates, if you want to reuse or even if you
deleted exsiting raid partitions/devices.)
+ Partman fails if you try to set
@Pascal Vandeputte and others using ati's propriatary fglrx driver:
Does "acpi.power_nocheck=1" AND "acpi_osi=linux" work with your
hardware, if you're not using the fglrx driver?
--
laptop overheats and suddenly shuts down/off
https://bugs.launchpad.net/bugs/370173
You received this bug notifi
Debian's package repository has 3.1.2 and ships the upstream udev rules.
http://git.debian.org/?p=pkg-mdadm/mdadm.git;a=log
--
Please upgrade to 3.1.x for lucid
https://bugs.launchpad.net/bugs/495370
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Public bug reported:
Binary package hint: update-manager
10.04
http://www.ubuntu.com/getubuntu/upgrading
But upgrade from alternate CD downloads *all* packages again. Not only
some updated packages.
** Affects: update-manager (Ubuntu)
Importance: Undecided
Status: New
--
Upgrad
** Also affects: update-manager
Importance: Undecided
Status: New
** Also affects: mdadm (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- boot failure with LVM on RAID
+ dist-upgrade LVM on RAID: boot failure
--
dist-upgrade LVM on RAID: boot failure
https:/
Public bug reported:
9.10 -> 10.04 update crashed
needed to reboot into rescue mode, select dpkg repair and reboot to be
able to log in.
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: libggz2 0.0.14.1-1build2
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: L
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/46720096/Dependencies.txt
** Attachment added: "VarLogDistupgradeAptlog.gz"
http://launchpadlibrarian.net/46720097/VarLogDistupgradeAptlog.gz
** Attachment added: "VarLogDistupgradeApttermlog.gz"
http://launchpadlibra
Public bug reported:
Binary package hint: mozilla-noscript
Lucid branch exists but no packages.
No explanation is available of why this popular security add-on has
apparently been dropped.
https://wiki.ubuntu.com/DesktopTeam/Specs/Lucid/FirefoxNewSupportModel
/extension-list
** Affects: mozill
Found explanation:
https://wiki.ubuntu.com/DesktopTeam/Specs/Lucid/FirefoxNewSupportModel
Please link to this from the package overview pages instead of the drop-
list.
--
no package available/build in lucid
https://bugs.launchpad.net/bugs/572923
You received this bug notification because you ar
Besides: Allready installed packages should really get uninstalled when
you drop the package. Otherwise they sit around possibly dirsturbing
manually installed add-ons, while they won't work in lucid and later
anyway.
--
no package available/build in lucid
https://bugs.launchpad.net/bugs/572923
Y
** Description changed:
Note:
When using luks encryption on top of software raid devices, it can eventually
break because linux_raid_member devices get opened directly as luks instead of
being assembled into md devices (Bug #531240), and all this happens silently
because mdadm monitoring is
** Also affects: rescue (Ubuntu)
Importance: Undecided
Status: New
--
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
If we would have a defined state at the and of the initramfs boot, say
"rootfs fully set up" implying all its dependencies would we still need
state passing? Or could the main upstart take it from there.
--
misc: support upstart within an initramfs
https://bugs.launchpad.net/bugs/491463
You recei
Just found the --rebuild-map option in the new version. That may even be
cleaner, to just rebuild the map in the main system before udev is
restarted.
--
Please upgrade to 3.1.x for lucid
https://bugs.launchpad.net/bugs/495370
You received this bug notification because you are a member of Ubuntu
Upstream actually ships with udev hotplug rules by now, maybe those
should be used instead of maintaining ubuntu ones.
With the successor to 3.1.2 mdadm seems to also ship unplug rules.
--
Please upgrade to 3.1.x for lucid
https://bugs.launchpad.net/bugs/495370
You received this bug notification
** Description changed:
Re-attaching parts of an array that have been running degraded
separately and contain the same amount and conflicting
changes, results in the assembly of a corrupt array.
Using the latest beta-2 server ISO and following
http://testcases.qa.ubuntu.com/Inst
** Description changed:
- Re-attaching parts of an array that have been running degraded
- separately and contain the same amount and conflicting
- changes or use a write intent bitmap, results in the assembly of a corrupt
array.
+ Re-attaching parts of an array that have been running degraded se
** Summary changed:
- mdadm monitor feature broken, not depending on local MTA/MDA nor using
beep/wall/notify-send
+ mdadm monitor feature broken, email notification not set up, nor using
beep/wall/notify-send
** Description changed:
Binary package hint: mdadm
Anybody who cares about re
> If one
> port flakes on one boot, the other port flakes on the next, and both ports
> are available on the third, wouldn't that trigger this same bogus
> reassembly?
That depends.
On linux-raid list it was said it would only happen if the event count
on both segements are eqal +/-1. That would
Thanks for the insight!
--
misc: support upstart within an 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-bugs@lists.ubuntu.com
https://lists.ubuntu.co
Your probably hitting several bugs.
I have also seen some differences in the geometry of virtual drives (at
least I tent to size them to some human friendly number). I have seen
some "unused space" things and (c)fdisk complaining.
IIRC the most usefull way with md's partitionable array feature is
i.e. you'll get incomplete md_XpY devices if mdadm is not (re)installed
(or you create a mdadm.conf manually) after creating the array since
ages. Bug #252345
--
mount: mounting /dev/md0 on /root/ failed: Invalid argument
https://bugs.launchpad.net/bugs/569900
You received this bug notification b
(Just to reassure you. I aggree a https://wiki.ubuntu.com/ReliableRaid
could be seen as release critical for a LTS release, not only for a
server/workstation edition.)
--
mount: mounting /dev/md0 on /root/ failed: Invalid argument
https://bugs.launchpad.net/bugs/569900
You received this bug notif
What does blkid return before md's are set up? (maybe booting with
break=top or break=premount)
--
mount: mounting /dev/md0 on /root/ failed: Invalid argument
https://bugs.launchpad.net/bugs/569900
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
also maybe try bootoption raid=noautodetect to get the kernel detection
out of the way
--
mount: mounting /dev/md0 on /root/ failed: Invalid argument
https://bugs.launchpad.net/bugs/569900
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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
The installer fails if there are already superblocks on your disks.
They get set (partly) assembled and the installer is not capable of
showing or handling these.
Try writing zeros to your disk or mdadm --stop and --zero-superblock
from another console.
--
grub-installer fails to install on a r
If you did not re-format you may also see Bug #527401. (Other install
issues in the comments also).
Generally, if your disks already have some preexisting superblocks on
them (even though you deleted the partition) blkid, partman, mdadm etc.
can get confused. When you recreate (similar) partitions
I got the same fatal error stating cfdisk.
FATAL ERROR: Bad primary partition 0: Partition ends in the final
partial cylind
Press any key to exit cfdisk
Installed manually, creating only logical partitions: 500M /boot, 3GB
raid1 for /home, res
mine was the RC, alternate CD
** Also affects: partman-base (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- [lucid beta1] ubiquity creates a strange partition table
+ [lucid] install creates a strange partition table
** Changed in: partman-base (Ubuntu)
Status:
Thank you for helping to track this down.
So the superblock on the member that got mis-opened appears to have been
overwritten. Maybe by writing/using to the opened luks device that
thought the full partition is used by luks, without respecting the room
of the raid superblock at the end of the dis
Importance was set to "wishlist" for cryptsetup, could you please
revisit that with the new findings in mind?
--
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
Bugs, which is sub
I would not thing blkid (util-linux) has altered the metadata on disk.
As it got altered blkid may actually never have (occasionally)
misreported anything to cause the behaviour. (The util-linux bug may not
have exsted in karmic nor lucid.) I have seen blkid reporting raid
correctly after installa
I'd suggest to make "cryptsetup isLuks" check with blikid prior to probing the
luks header (and have it report errors), as the next step in finding/fixing the
root cause and reestablishing trust in using luks on raid.
--
silently breaking raid: root raid_members opened as luks
https://bugs.lau
Public bug reported:
Binary package hint: gnome-system-tools
When creating a new user, there is no (advanced tab/button) option to
specify those options for the new user.
Since gdm does not support to display only selected or unselected users
in the user list, you need to create users that shoul
** Description changed:
Binary package hint: gnome-system-tools
- When creating a new user, there is no (advanced tab/button) option to
- specify those options for the new user.
+ When creating a new user in 10.04, there is no (advanced tab/button)
+ option to specify those options for the ne
Will g-s-t also adjust the ownership of files in the filesystem upon
changing a user's ID, or would that be a different issue?
--
[users-admin] Changing UID doesn't work
https://bugs.launchpad.net/bugs/542183
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Is gst using usermod? Its manpage says:
-u The ownership of files outside of the users home directory must be
fixed manually.
--
[users-admin] Changing UID doesn't work
https://bugs.launchpad.net/bugs/542183
You received this bug notification because you are a member of Ubuntu
Bugs,
Mind you that I'd consider any device-kit privilege escalation
implementation that isn't configured to support/use (be itself easily
configurable by) standard unix user group memberships as a regression.
--
[Karmic]&[Lucid] Only one user has sound; no hw shows in Sound Preferences
https://bugs.l
301 - 400 of 1101 matches
Mail list logo
