[Bug 1652822] Re: grub efi xfs unsupported filesystem
** Tags added: yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652822 Title: grub efi xfs unsupported filesystem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1652822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1393842] Re: libvirt does not grant qemu-guest-agent channel perms
bummer workaround:
for xml in /etc/libvirt/qemu/*.xml; do VM=$(basename $xml|cut -d. -f1);
rm /var/lib/libvirt/qemu/channel/target/${VM}.org.qemu.guest_agent.0;
virsh dumpxml $VM | /usr/lib/libvirt/virt-aa-helper -c -u libvirt-`virsh
domuuid $VM`; virsh start $VM; done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1393842
Title:
libvirt does not grant qemu-guest-agent channel perms
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1393842/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1393842] Re: libvirt does not grant qemu-guest-agent channel perms
Confirmed. Update in proposed works as mpanella says -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1393842 Title: libvirt does not grant qemu-guest-agent channel perms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1393842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1103389] Re: makedumpfile --dump-dmesg fails on 3.5 kernels and later
Will there be a fix for Precise? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1103389 Title: makedumpfile --dump-dmesg fails on 3.5 kernels and later To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1103389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 567955] Re: grub2 always adds memtest86 serial console even when no serial port
As a related comment, the serial port is *always* ttyS0, even when it's not there, and even when both GRUB2 itself and the kernel are all configured to go to, say ttyS1 or something completely else. I propose to modify /etc/grub.d/20_memtest86+ * Look at /sys/class/tty/ ; if there's nothing in there that's not virtual (there should be a good way to weed out the virtual devices by looking at this), skip the serial port config * AND/OR look at GRUB2/the kernel; if they're not configured for serial communication, why should you for memtest? ** Bug watch added: Debian Bug tracker #612371 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612371 ** Also affects: memtest86+ via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612371 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/567955 Title: grub2 always adds memtest86 serial console even when no serial port To manage notifications about this bug go to: https://bugs.launchpad.net/memtest86+/+bug/567955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 990765] Re: Save button always greyed out when creating openvpn connection
I set the user to 'Always Ask' for password, yet I had to give a (nonsensical) password for the p12 file, otherwise it wouldn't ungrey. Upon connecting, it still asked me for both passwords. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/990765 Title: Save button always greyed out when creating openvpn connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/990765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 653714] Re: Garbage on X display w/ Dell D800 wuxga nouveau driver (Nvidia GeForce4 Ti 4200 Go AGP rev a1 [NV28])
** Bug watch added: freedesktop.org Bugzilla #50403 https://bugs.freedesktop.org/show_bug.cgi?id=50403 ** Also affects: nouveau via https://bugs.freedesktop.org/show_bug.cgi?id=50403 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/653714 Title: Garbage on X display w/ Dell D800 wuxga nouveau driver (Nvidia GeForce4 Ti 4200 Go AGP rev a1 [NV28]) To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/653714/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 658461] Re: -virtual kernel missing dependent modules (ahci fails to load)
*** This bug is a duplicate of bug 570542 *** https://bugs.launchpad.net/bugs/570542 It's largely semantics (it should be 'related'), but the issue is largely the same. For some reason the build farms don't pick up on ahci's dependency on libahci (it's also not registered in modules.dep) and therefore libahci isn't included, leading to the same symptom; SATA won't work with -virtual. The resolution is for both current bugs also the same: include libahci and register the dependency correctly :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/658461 Title: -virtual kernel missing dependent modules (ahci fails to load) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/658461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 570542] Re: linux-image-virtual does not include ahci module, prevents virtualbox from booting an Ubuntu guest
The ahci.ko needs libahci to work, which is included in linux-image-extra-virtual (along with everything but the kitchen sink). It *SHOULD* be included in linux-image-virtual IMHO, because ahci.ko is next to worthless without it, and installing an additional 120MB of drivers, modules and cruft to get a 47KiB module to get SATA to work is just plain silly (bug #658461) Workaround (I guarantee nothing :-P ): ### cd /tmp apt-get download linux-image-extra-3.0.0-12-virtual cd / dpkg --fsys-tarfile /tmp/linux-image-extra-3.0.0-12-virtual*.deb | tar --wildcards -xf - */libahci.ko depmod -a update-initramfs -u shutdown -r now presto -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/570542 Title: linux-image-virtual does not include ahci module, prevents virtualbox from booting an Ubuntu guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/570542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 570542] Re: linux-image-virtual does not include ahci module, prevents virtualbox from booting an Ubuntu guest
On a side note, something appears not right there anyways; modules.dep doesn't list libahci.ko as a dependency for ahci.ko, while modinfo does so either depmod -a silently fails the dependency and doesn't list it, or something strange is going on with the dependency resolution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/570542 Title: linux-image-virtual does not include ahci module, prevents virtualbox from booting an Ubuntu guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/570542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 658461] Re: -virtual kernel missing dependent modules (ahci fails to load)
*** This bug is a duplicate of bug 570542 *** https://bugs.launchpad.net/bugs/570542 The ahci.ko needs libahci to work, which is included in linux-image- extra-virtual (along with everything but the kitchen sink). It *SHOULD* be included in linux-image-virtual IMHO, because ahci.ko is next to worthless without it, and installing an additional 120MB of drivers, modules and cruft to get a 47KiB module to get SATA to work is just plain silly (bug #658461) Workaround (I guarantee nothing :-P ): ### cd /tmp apt-get download linux-image-extra-3.0.0-12-virtual cd / dpkg --fsys-tarfile /tmp/linux-image-extra-3.0.0-12-virtual*.deb | tar --wildcards -xf - */libahci.ko depmod -a update-initramfs -u shutdown -r now presto -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/658461 Title: -virtual kernel missing dependent modules (ahci fails to load) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/658461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 570542] Re: linux-image-virtual does not include ahci module, prevents virtualbox from booting an Ubuntu guest
Natty still doesn't include it. Please reopen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/570542 Title: linux-image-virtual does not include ahci module, prevents virtualbox from booting an Ubuntu guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/570542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 658461] Re: -virtual kernel missing dependent modules (ahci fails to load)
*** This bug is a duplicate of bug 570542 *** https://bugs.launchpad.net/bugs/570542 ** This bug has been marked a duplicate of bug 570542 linux-image-virtual does not include ahci module, prevents virtualbox from booting an Ubuntu guest -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/658461 Title: -virtual kernel missing dependent modules (ahci fails to load) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/658461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 570542] Re: linux-image-virtual does not include ahci module, prevents virtualbox from booting an Ubuntu guest
Neither does Oneiric. Please reopen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/570542 Title: linux-image-virtual does not include ahci module, prevents virtualbox from booting an Ubuntu guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/570542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 742145] Re: dmraid interferes with mdadm
Well, looks like it, yes. I ended up completely nulling out the HD's because dmraid kept refusing deleting both the RAID set (can't be done for DDF1) and the metadata (gave errors no matter what) and completely rebuilding the array again. Problem is resolved now. Although it continues to elude me why this never happened on Maverick... Anyway thanks for your help and sorry for your time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/742145 Title: dmraid interferes with mdadm -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 742145] Re: ddf1 format should be disabled in dmraid in favor of mdadm
Right. That was 'smart' :D Here's the tar now.
mdadm is as before:
root@ubuntu:/tmp# mdadm -E /dev/sdc /dev/sdc1
/dev/sdc:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : ef584e09:52f1d802:3d7ec530:e2926701
Name : ubuntu:SATAs (local to host ubuntu)
Creation Time : Tue Feb 22 23:50:59 2011
Raid Level : raid6
Raid Devices : 6
Avail Dev Size : 3907028896 (1863.02 GiB 2000.40 GB)
Array Size : 15628114944 (7452.07 GiB 8001.59 GB)
Used Dev Size : 3907028736 (1863.02 GiB 2000.40 GB)
Data Offset : 272 sectors
Super Offset : 8 sectors
State : clean
Device UUID : 59f2e93e:39e5e899:5647c5cf:afe86dee
Update Time : Fri Mar 25 14:57:31 2011
Checksum : 1f74ccf6 - correct
Events : 36
Layout : left-symmetric
Chunk Size : 128K
Device Role : Active device 0
Array State : AA ('A' == active, '.' == missing)
mdadm: cannot open /dev/sdc1: No such file or directory
But considering I only used Maverick's mdadm to create the array, which
doesn't support DDF1 or Intel MS, I couldn't have used DDF1. Basically
the metadata choice went between 0.9 and 1.2 natives.
So if the Intel/Adaptec BIOS couldn't have created the DDF1 group, and
mdadm couldn't have, how did I end up with double DDF1 metadata on my
disks!?
** Attachment added: dmraid.tgz
https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/742145/+attachment/1949169/+files/dmraid.tgz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/742145
Title:
ddf1 format should be disabled in dmraid in favor of mdadm
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 742145] Re: dmraid interferes with mdadm
hm. Since that is not the case, I'm rather suspicious of messing with my metadata ;-) I'll try that tonight, after backing up everything on the disks. And/or perhaps I'll try reproducing this in a VM. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/742145 Title: dmraid interferes with mdadm -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 742145] Re: dmraid interferes with mdadm
The mobo is a SuperMicro one with a very very weird option to choose (I kid you not) between Intel MSM or Adaptec BIOS for the SATA ports. However, neither have been active to my knowledge, certainly not in a RAID6 config, as neither support this. It is unlikely but possible I once configured a 6-drive RAID10 in the Adaptec BIOS, but that config won't have survived for more than two boots at max ;-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/742145 Title: dmraid interferes with mdadm -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 742145] Re: ddf1 format should be disabled in dmraid in favor of mdadm
Judging from your tar comment, you're expecting way more output than
this from dmraid -rD:
root@ubuntu:~# dmraid -rD
/dev/sdh: ddf1, .ddf1_disks, GROUP, ok, 3906572288 sectors, data@ 0
/dev/sdg: ddf1, .ddf1_disks, GROUP, ok, 3906572288 sectors, data@ 0
/dev/sdf: ddf1, .ddf1_disks, GROUP, ok, 3906572288 sectors, data@ 0
/dev/sde: ddf1, .ddf1_disks, GROUP, ok, 3906572288 sectors, data@ 0
/dev/sdd: ddf1, .ddf1_disks, GROUP, ok, 3906572288 sectors, data@ 0
/dev/sdc: ddf1, .ddf1_disks, GROUP, ok, 3906572288 sectors, data@ 0
/dev/sdb: sil, sil_acagdccaeafe, stripe, ok, 117229312 sectors, data@ 0
/dev/sda: sil, sil_acagdccaeafe, stripe, ok, 117229312 sectors, data@ 0
However, your guess is wrong. I bought this system only a couple of months ago,
and Maverick was the first and only OS to become alive on it.
The controller on which the SATAs are sitting
00:1f.2 SATA controller: Intel Corporation 82801JI (ICH10 Family) SATA AHCI
Controller (prog-if 01 [AHCI 1.0])
is incapable of doing RAID6.
In the BIOS the controller is in AHCI mode, and has, aside from some very
short-lived experimenting, always been in AHCI mode.
These drives were empty before, and have only been used as an mdadm RAID. I did
however recreate it a couple of times fiddling with various tweaks (mostly
stripsize metadata versions) before settling on the current config.
But each time I never used the assume-clean option or such, allowing the mdadm
RAID6 to fully build before doing anything else with it.
Also, this particular problem didn't occur on Maverick, and simply
excluding ENV{ID_FS_TYPE}!=linux_raid* in udev 'solves' it in Natty,
indicating that at least udev/kernel are aware that this is actually a
linux_raid instead of a FakeRAID one.
As a side note, I never heard of DDF1 before, and it was actually you
who told me it was a metadata format. So I never actually tweaked
neither mdadm nor dmraid as far as to specify an apparently deprecated
format.
** Attachment added: dmraid -n /dev/sdc
https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/742145/+attachment/1942995/+files/dmraid-n
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/742145
Title:
ddf1 format should be disabled in dmraid in favor of mdadm
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 742145] Re: ddf1 format should be disabled in dmraid in favor of mdadm
Philip,
Thanks for responding. Of course I meant 'Upgrade from Maverick to Natty
(problem didn't occur on Maverick)' :)
The array in question was created under Maverick ~~ like this:
mdadm --create /dev/md20 --level=6 --raid-devices=6 -c 128 -e 1.2 --name=SATAs
/dev/sd[cdefgh]
root@ubuntu:~# udevadm info --query=all --name=/dev/sdc
P: /devices/pci:00/:00:1f.2/host4/target4:0:0/4:0:0:0/block/sdc
E: UDEV_LOG=3
E: DEVPATH=/devices/pci:00/:00:1f.2/host4/target4:0:0/4:0:0:0/block/sdc
E: SUBSYSTEM=block
E: MAJOR=8
E: MINOR=32
E: DEVNAME=sdc
E: DEVTYPE=disk
there are no partitions on the disks.
AFAICT, the metadata is native mdadm's:
root@ubuntu:~# mdadm --detail /dev/md/SATAs
/dev/md/SATAs:
Version : 1.2
Creation Time : Tue Feb 22 23:50:59 2011
Raid Level : raid6
Array Size : 7814057472 (7452.07 GiB 8001.59 GB)
Used Dev Size : 1953514368 (1863.02 GiB 2000.40 GB)
Raid Devices : 6
Total Devices : 6
Persistence : Superblock is persistent
Update Time : Fri Mar 25 11:37:24 2011
State : clean
Active Devices : 6
Working Devices : 6
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 128K
Name : ubuntu:SATAs (local to host ubuntu)
UUID : ef584e09:52f1d802:3d7ec530:e2926701
Events : 34
Number Major Minor RaidDevice State
0 8 320 active sync /dev/sdc
1 8 481 active sync /dev/sdd
2 8 642 active sync /dev/sde
3 8 803 active sync /dev/sdf
4 8 964 active sync /dev/sdg
5 8 1125 active sync /dev/sdh
root@ubuntu:~# mdadm --examine /dev/sdc
/dev/sdc:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : ef584e09:52f1d802:3d7ec530:e2926701
Name : ubuntu:SATAs (local to host ubuntu)
Creation Time : Tue Feb 22 23:50:59 2011
Raid Level : raid6
Raid Devices : 6
Avail Dev Size : 3907028896 (1863.02 GiB 2000.40 GB)
Array Size : 15628114944 (7452.07 GiB 8001.59 GB)
Used Dev Size : 3907028736 (1863.02 GiB 2000.40 GB)
Data Offset : 272 sectors
Super Offset : 8 sectors
State : clean
Device UUID : 59f2e93e:39e5e899:5647c5cf:afe86dee
Update Time : Fri Mar 25 11:38:46 2011
Checksum : 1f749e5f - correct
Events : 34
Layout : left-symmetric
Chunk Size : 128K
Device Role : Active device 0
Array State : AA ('A' == active, '.' == missing)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/742145
Title:
ddf1 format should be disabled in dmraid in favor of mdadm
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 742145] Re: ddf1 format should be disabled in dmraid in favor of mdadm
Phillip, It seems Magic : a92b4efc is consistent with native mdadm format, so it seems it's not DDF1. My hypothesis would therefore seem to be that dmraid incorrectly picks up native mdadm RAID sets as DDF1 sets? Also, I assumed the Debian bug was related, because the people over there mention /dev/sd[ab]1 as (Windows) dmraid and /dev/sd[ab]2 as md RAID. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/742145 Title: ddf1 format should be disabled in dmraid in favor of mdadm -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 742145] [NEW] dmraid interferes with mdadm
Public bug reported: Binary package hint: dmraid Setup: * Upgrade from Lucid to Natty (problem didn't occur on Lucid) * /dev/sd[ab] in fakeRAID setup w/rootFS on it * /dev/sd[cdefgh] in an md RAID6 Upon upgrade, system will fail to assemble the RAID6, saying the block devices are busy: mdadm: Cannot open /dev/sdc: Device or resource busy This is due to dmraid having apparently detected the RAID group and udev having ran dmraid-activate script over it. ** Affects: dmraid Importance: Unknown Status: Unknown ** Affects: udev Importance: Undecided Status: New ** Affects: dmraid (Ubuntu) Importance: Undecided Status: New ** Tags: 85-dmraid.rules dmraid mdadm udev ** Bug watch added: Debian Bug tracker #534274 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534274 ** Also affects: dmraid via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534274 Importance: Unknown Status: Unknown ** Also affects: udev Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/742145 Title: dmraid interferes with mdadm -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 742145] Re: dmraid interferes with mdadm
root@ubuntu:/lib/udev# dmraid -r
/dev/sdh: ddf1, .ddf1_disks, GROUP, ok, 3906572288 sectors, data@ 0
/dev/sdg: ddf1, .ddf1_disks, GROUP, ok, 3906572288 sectors, data@ 0
/dev/sdf: ddf1, .ddf1_disks, GROUP, ok, 3906572288 sectors, data@ 0
/dev/sde: ddf1, .ddf1_disks, GROUP, ok, 3906572288 sectors, data@ 0
/dev/sdd: ddf1, .ddf1_disks, GROUP, ok, 3906572288 sectors, data@ 0
/dev/sdc: ddf1, .ddf1_disks, GROUP, ok, 3906572288 sectors, data@ 0
/dev/sdb: sil, sil_acagdccaeafe, stripe, ok, 117229312 sectors, data@ 0
/dev/sda: sil, sil_acagdccaeafe, stripe, ok, 117229312 sectors, data@ 0
/dev/sd[cdefgh] are in a 'ddf1' group.
I do not know whether this is by design or by error, but dmraid-activate is
incapable of activating the mdadm RAID6 array, that's for sure.
patching /lib/udev/rules.d/85-dmraid.rules like so:
orig:
SUBSYSTEM==block, ACTION==add, ENV{ID_TYPE}==disk,
ENV{ID_FS_USAGE}==raid, KERNEL==hd[a-z]|sd[a-z], \
RUN+=/sbin/dmraid-activate %k
patch:
SUBSYSTEM==block, ACTION==add, ENV{ID_TYPE}==disk,
ENV{ID_FS_TYPE}!=linux_raid*, ENV{ID_FS_USAGE}==raid,
KERNEL==hd[a-z]|sd[a-z], \
RUN+=/sbin/dmraid-activate %k
Resolves the problem, but dmraid -r still lists the group. Therefore I
consider this a workaround for now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/742145
Title:
dmraid interferes with mdadm
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 742145] Re: dmraid interferes with mdadm
Also, note that the attached Debian bug 534274 reports the same issue, but fails to consider my scenario as a valid setup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/742145 Title: dmraid interferes with mdadm -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 742145] Re: dmraid interferes with mdadm
** Tags added: mdadm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/742145 Title: dmraid interferes with mdadm -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 577264] Re: libvirt started after cgred - cgroup not working correctly
For me, the workaround works. The related bug has already been filed under #644669 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. https://bugs.launchpad.net/bugs/577264 Title: libvirt started after cgred - cgroup not working correctly -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 644669] Re: cgred should be started before libvirt-bin
** Bug watch added: Red Hat Bugzilla #660402 https://bugzilla.redhat.com/show_bug.cgi?id=660402 ** Also affects: libcgroup (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=660402 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/644669 Title: cgred should be started before libvirt-bin -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 577264] Re: libvirt started after cgred - cgroup not working correctly
For me, the workaround works. The related bug has already been filed under #644669 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/577264 Title: libvirt started after cgred - cgroup not working correctly -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 136252] Re: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails)
And there you go. +1 for fix on my up-to-date 64-bit Maverick Server :) I'm loving it. Been rebuilding my 6*2TB RAID6 for three days now, figuring something went wrong a couple of times. Then I found out the detection issue and then this bug is easily found. FWIW, I've got an array created using: mdadm --create /dev/md20 --level=6 --raid-devices=6 -c 256 -e 1.2 --name=SATAs /dev/sd[cdefgh] The infamous md_d127 device kept showing up as well. doing an mdadm --stop /dev/md_d127 mdadm --assemble -v /dev/md/SATAs /dev/sd[cdefgh] then properly reinitalized the array. The only thing that would work was manually adding ARRAY /dev/md20 level=raid6 num-devices=6 metadata=01.02 name=ubuntu:SATAs UUID=10b2a833:0fac6b94:3224150e:0aeefa84 devices=/dev/sdc,/dev/sdd,/dev/sde,/dev/sdf,/dev/sdg,/dev/sdh to /dev/mdadm/mdadm.conf. Named array (/dev/md/SATAs) will not work. Your mdadm/initramfs correctly detects activates the array without anything in /etc/mdadm/mdadm.conf, albeit as /dev/md127, NOT as /dev/md/SATAs As a fortunate side-note, yours also correctly reports the metadata superblock version as 1.2, as opposed to 01.02 in the other, leading to errors. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/136252 Title: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 659084] Re: 2.6.35-22-virtual is missing nfs modules
Got hit by #570542 at the same time. The two issues seem to have some similarities between them in that they're both broken kernel modules in the -virtual that should've been available and seem to have been compiled in, or the build at least should've tried. I've noticed that the -headers packages contain the same files overall, but the -image-virtual packages are missing both libahci.ko and the aforementioned .ko's. -- 2.6.35-22-virtual is missing nfs modules https://bugs.launchpad.net/bugs/659084 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/listinfo/ubuntu-bugs
[Bug 570542] Re: linux-image-virtual does not include ahci module, prevents virtualbox from booting minimal vm install
I second that. Both upgrade and clean install result in same error as Andy. Got hit by #659084 at the same time. The two issues seem to have some similarities between them in that they're both broken kernel modules in the -virtual that should've been available and seem to have been compiled in, or the build at least should've tried. I've noticed that the -headers packages contain the same files overall, but the -image-virtual packages are missing both libahci.ko and the mentioned .ko's in #659084. -- linux-image-virtual does not include ahci module, prevents virtualbox from booting minimal vm install https://bugs.launchpad.net/bugs/570542 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/listinfo/ubuntu-bugs
[Bug 486218] Re: kerneltop reports wrong map line on 2.6.31-14-generic
Linux ubuntu 2.6.32-22-generic #33-Ubuntu SMP Wed Apr 28 13:28:05 UTC 2010 x86_64 GNU/Linux kerneltop: /boot/System.map-2.6.32-22-generic(27435): wrong map line FWIW, the line is: 8174ce30 r __pci_fixup_PCI_VENDOR_ID_INTELPCI_DEVICE_ID_INTEL_ESB_10quirk_disable_intel_boot_interrupt -- kerneltop reports wrong map line on 2.6.31-14-generic https://bugs.launchpad.net/bugs/486218 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/listinfo/ubuntu-bugs
[Bug 453579] Re: in-place corruption of large files *without fsck or reboot* reported with linux 2.6.31-14.46 on ext4
I see there's a lot of discussion going on about this bug, I'll just drop in my 5c: I cleanly installed/updated a x64 Karmic w/ext4 filesystems on my MacBook 5,1 (no other OSes installed). Due to the nature of my work I downloaded over a dozen ISO's of different HTTP/FTPs, none of which failed their MD5 sums. Yesterday, I cleanly installed/updated a x32 Karmic on some measly Centrino/Pentium M 1,6 Ghz laptop and copied, amongst others, 7 DVD ISO's to it from an external NTFS harddrive, with no apparent issue or corruption (though I'd have to check the MD5's to make absolutely sure). So for me, this issue doesn't seem to exist. Then again, both filesystems are clean-and-simple 3 primary partition layouts (10GB /,RAM*1~1,5 swap, remainder /home, handmade during install), no hw/sw RAID/LVM or whatever. -- in-place corruption of large files *without fsck or reboot* reported with linux 2.6.31-14.46 on ext4 https://bugs.launchpad.net/bugs/453579 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/listinfo/ubuntu-bugs
[Bug 327963] Re: Error activating XKB configuration with MacBook keyboard model
I was having the exact same issue, but then with a Macbook 79 model
keyboard (Macbook/Pro Intl) and the US International with AltGr dead
keys.
One of the commenters in the FreeDesktop bug correctly notes that there
might actually be little use for these symbols anymore, but since I'm
not exactly an XKB guru I find it too hard to tell.
Anway, I added
partial alphanumeric_keys
xkb_symbols altgr-intl{
include us(altgr-intl)
};
to /usr/share/X11/xkb/symbols/macintosh_vndr/us and the error went away.
Everything works as it should AFAICT.
--
Error activating XKB configuration with MacBook keyboard model
https://bugs.launchpad.net/bugs/327963
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/listinfo/ubuntu-bugs
