[Bug 1535277] Re: cannot execute birdfont
The workaround worked for me also and fixed the problem: $ sudo ln -s /usr/lib/x86_64-linux-gnu/libxmlbird.so.1 /usr/lib/x86_64 -linux-gnu/libxmlbird.so.1.0 Maybe someone responsible for distribution of ubuntu ISO could put this link to next release of ubuntu 16.04 ?? I did not check if 18.04 is also effected, but could do ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535277 Title: cannot execute birdfont To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1535277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1571987] Re: error loading libxmlbird.so.1.0 (seems to work with libxmlbird.so.1 though)
*** This bug is a duplicate of bug 1535277 *** https://bugs.launchpad.net/bugs/1535277 The workaround (last comment of Kevin Brubeck Unhammer) worked for me and fixed the problem, but instead of copying it, i created a link: $ sudo ln -s /usr/lib/x86_64-linux-gnu/libxmlbird.so.1 /usr/lib/x86_64 -linux-gnu/libxmlbird.so.1.0 Maybe someone responsible for distribution of ubuntu ISO could put this link to next release of ubuntu 16.04 ?? I did not check if 18.04 is also effected, but could do ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1571987 Title: error loading libxmlbird.so.1.0 (seems to work with libxmlbird.so.1 though) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/birdfont/+bug/1571987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1518421] [NEW] package gir1.2-gst-plugins-base-1.0 1.2.4-1~ubuntu2 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevo
Public bug reported: don't know details only know that problem exists with installation of this :( ProblemType: Package DistroRelease: Ubuntu 14.04 Package: gir1.2-gst-plugins-base-1.0 1.2.4-1~ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Thu Nov 19 11:50:04 2015 DuplicateSignature: package:gir1.2-gst-plugins-base-1.0:1.2.4-1~ubuntu2:Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. InstallationDate: Installed on 2015-09-27 (54 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: gst-plugins-base1.0 Title: package gir1.2-gst-plugins-base-1.0 1.2.4-1~ubuntu2 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gst-plugins-base1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check package-from-proposed trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1518421 Title: package gir1.2-gst-plugins-base-1.0 1.2.4-1~ubuntu2 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base1.0/+bug/1518421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1093918] Re: grub-probe auto-detection fails on raid
tested - OK ! *when will it be available?* there are only - as already mentioned some error messages a little ugly - but it works 2014/1/9 Josef Hope josef.klotz...@gmail.com Ok i will test in next days Am 09.01.2014 17:53 schrieb Phillip Susi ps...@ubuntu.com: The backport to precise is still waiting for someone to test and verify it, see comment #56. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid Status in “multipath-tools” package in Ubuntu: Fix Released Status in “multipath-tools” source package in Precise: Fix Committed Bug description: kpartx was mapping the entire extended partition then stacking the logical partitions on that device. This exposes a device that otherwise appears to be an entire disk device containing the logical partitions, and this confuses grub. The extended partition is supposed to only expose the first two sectors to allow LILO to be installed. The patch has been applied upstream now, and since this is the only change since quantal, a simple copy to quantal-updates should resolve it there as well. I have done this in my ppa and the reporter has verified it has fixed the issue. TEST CASE: Use fdisk to create an extended parition either on a fakeraid disk or an LVM logical volume. Run kpartx -a /dev/mapper/whatever to activate the partitions on the disk. Assuming the extended partition is number 3, then sudo blockdev --getsz /dev/mapper/whatever3 will report the apparent size of the extended partition. The size should only be 2 sectors regardless of the size of the extended partition. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1093918/+subscriptions -- Ing. Josef Klotzner -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1093918/+subscriptions -- 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
Re: [Bug 1093918] Re: grub-probe auto-detection fails on raid
tested - OK ! *when will it be available?* there are only - as already mentioned some error messages a little ugly - but it works 2014/1/9 Josef Hope josef.klotz...@gmail.com Ok i will test in next days Am 09.01.2014 17:53 schrieb Phillip Susi ps...@ubuntu.com: The backport to precise is still waiting for someone to test and verify it, see comment #56. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid Status in “multipath-tools” package in Ubuntu: Fix Released Status in “multipath-tools” source package in Precise: Fix Committed Bug description: kpartx was mapping the entire extended partition then stacking the logical partitions on that device. This exposes a device that otherwise appears to be an entire disk device containing the logical partitions, and this confuses grub. The extended partition is supposed to only expose the first two sectors to allow LILO to be installed. The patch has been applied upstream now, and since this is the only change since quantal, a simple copy to quantal-updates should resolve it there as well. I have done this in my ppa and the reporter has verified it has fixed the issue. TEST CASE: Use fdisk to create an extended parition either on a fakeraid disk or an LVM logical volume. Run kpartx -a /dev/mapper/whatever to activate the partitions on the disk. Assuming the extended partition is number 3, then sudo blockdev --getsz /dev/mapper/whatever3 will report the apparent size of the extended partition. The size should only be 2 sectors regardless of the size of the extended partition. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1093918/+subscriptions -- Ing. Josef Klotzner -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1093918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1093918] Re: grub-probe auto-detection fails on raid
Does it mean it is already fixef in 12.04.3 and newer? Am 09.01.2014 16:13 schrieb Phillip Susi ps...@ubuntu.com: ** No longer affects: multipath-tools (Ubuntu Quantal) -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid Status in “multipath-tools” package in Ubuntu: Fix Released Status in “multipath-tools” source package in Precise: Fix Committed Bug description: kpartx was mapping the entire extended partition then stacking the logical partitions on that device. This exposes a device that otherwise appears to be an entire disk device containing the logical partitions, and this confuses grub. The extended partition is supposed to only expose the first two sectors to allow LILO to be installed. The patch has been applied upstream now, and since this is the only change since quantal, a simple copy to quantal-updates should resolve it there as well. I have done this in my ppa and the reporter has verified it has fixed the issue. TEST CASE: Use fdisk to create an extended parition either on a fakeraid disk or an LVM logical volume. Run kpartx -a /dev/mapper/whatever to activate the partitions on the disk. Assuming the extended partition is number 3, then sudo blockdev --getsz /dev/mapper/whatever3 will report the apparent size of the extended partition. The size should only be 2 sectors regardless of the size of the extended partition. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1093918/+subscriptions -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1093918/+subscriptions -- 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
Re: [Bug 1093918] Re: grub-probe auto-detection fails on raid
Ok i will test in next days Am 09.01.2014 17:53 schrieb Phillip Susi ps...@ubuntu.com: The backport to precise is still waiting for someone to test and verify it, see comment #56. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid Status in “multipath-tools” package in Ubuntu: Fix Released Status in “multipath-tools” source package in Precise: Fix Committed Bug description: kpartx was mapping the entire extended partition then stacking the logical partitions on that device. This exposes a device that otherwise appears to be an entire disk device containing the logical partitions, and this confuses grub. The extended partition is supposed to only expose the first two sectors to allow LILO to be installed. The patch has been applied upstream now, and since this is the only change since quantal, a simple copy to quantal-updates should resolve it there as well. I have done this in my ppa and the reporter has verified it has fixed the issue. TEST CASE: Use fdisk to create an extended parition either on a fakeraid disk or an LVM logical volume. Run kpartx -a /dev/mapper/whatever to activate the partitions on the disk. Assuming the extended partition is number 3, then sudo blockdev --getsz /dev/mapper/whatever3 will report the apparent size of the extended partition. The size should only be 2 sectors regardless of the size of the extended partition. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1093918/+subscriptions -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1093918/+subscriptions -- 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
Re: [Bug 1093918] Re: grub-probe auto-detection fails on raid
Does it mean it is already fixef in 12.04.3 and newer? Am 09.01.2014 16:13 schrieb Phillip Susi ps...@ubuntu.com: ** No longer affects: multipath-tools (Ubuntu Quantal) -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid Status in “multipath-tools” package in Ubuntu: Fix Released Status in “multipath-tools” source package in Precise: Fix Committed Bug description: kpartx was mapping the entire extended partition then stacking the logical partitions on that device. This exposes a device that otherwise appears to be an entire disk device containing the logical partitions, and this confuses grub. The extended partition is supposed to only expose the first two sectors to allow LILO to be installed. The patch has been applied upstream now, and since this is the only change since quantal, a simple copy to quantal-updates should resolve it there as well. I have done this in my ppa and the reporter has verified it has fixed the issue. TEST CASE: Use fdisk to create an extended parition either on a fakeraid disk or an LVM logical volume. Run kpartx -a /dev/mapper/whatever to activate the partitions on the disk. Assuming the extended partition is number 3, then sudo blockdev --getsz /dev/mapper/whatever3 will report the apparent size of the extended partition. The size should only be 2 sectors regardless of the size of the extended partition. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1093918/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1093918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1093918] Re: grub-probe auto-detection fails on raid
Ok i will test in next days Am 09.01.2014 17:53 schrieb Phillip Susi ps...@ubuntu.com: The backport to precise is still waiting for someone to test and verify it, see comment #56. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid Status in “multipath-tools” package in Ubuntu: Fix Released Status in “multipath-tools” source package in Precise: Fix Committed Bug description: kpartx was mapping the entire extended partition then stacking the logical partitions on that device. This exposes a device that otherwise appears to be an entire disk device containing the logical partitions, and this confuses grub. The extended partition is supposed to only expose the first two sectors to allow LILO to be installed. The patch has been applied upstream now, and since this is the only change since quantal, a simple copy to quantal-updates should resolve it there as well. I have done this in my ppa and the reporter has verified it has fixed the issue. TEST CASE: Use fdisk to create an extended parition either on a fakeraid disk or an LVM logical volume. Run kpartx -a /dev/mapper/whatever to activate the partitions on the disk. Assuming the extended partition is number 3, then sudo blockdev --getsz /dev/mapper/whatever3 will report the apparent size of the extended partition. The size should only be 2 sectors regardless of the size of the extended partition. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1093918/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1093918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1093918] Re: grub-probe auto-detection fails on raid
Btw: i like Your Atari logo ... i am still owning a Mega STE and a Falcon, which i had to repair last time as battery of battery buffered NVRAM was dead. Now it still and again is alive !! :D 2013/8/24 Josef Klotzner josef.klotz...@gmail.com Sorry, but in the moment it will not be a good idea to destroy my RAID again only to know, if this would work also with new install. I have several OS Systems on the Raid besides ~ 1 TB data. It would take me days of work to test and bring my machine back to state of before via Backup. I need it currently every day an am not able to. I have already tested was P. Susi created to fix that bug. You can trust it works and implement as it is. Fact is: if you don't implement susi's fix ubuntu installs will still TOTALLY fail if you want to install on extended partitions of a Raid. If you implement it only can improve. What i can imagine to do, is to test with a life CD, updated to include fix, if the Raid is mounted and accessible, because either this did not work properly as far as i can remember. But please don't ask me to destroy my RAID for a further test. Thank You. kind regards Josef 2013/8/18 Launchpad Bug Tracker 1093...@bugs.launchpad.net ** Branch linked: lp:~ubuntu-branches/ubuntu/precise/multipath-tools /precise-proposed -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid Status in “multipath-tools” package in Ubuntu: Fix Released Status in “multipath-tools” source package in Precise: Fix Committed Status in “multipath-tools” source package in Quantal: Triaged Bug description: kpartx was mapping the entire extended partition then stacking the logical partitions on that device. This exposes a device that otherwise appears to be an entire disk device containing the logical partitions, and this confuses grub. The extended partition is supposed to only expose the first two sectors to allow LILO to be installed. The patch has been applied upstream now, and since this is the only change since quantal, a simple copy to quantal-updates should resolve it there as well. I have done this in my ppa and the reporter has verified it has fixed the issue. TEST CASE: Use fdisk to create an extended parition either on a fakeraid disk or an LVM logical volume. Run kpartx -a /dev/mapper/whatever to activate the partitions on the disk. Assuming the extended partition is number 3, then sudo blockdev --getsz /dev/mapper/whatever3 will report the apparent size of the extended partition. The size should only be 2 sectors regardless of the size of the extended partition. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1093918/+subscriptions -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1093918/+subscriptions -- 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
Re: [Bug 1093918] Re: grub-probe auto-detection fails on raid
Sorry, but in the moment it will not be a good idea to destroy my RAID again only to know, if this would work also with new install. I have several OS Systems on the Raid besides ~ 1 TB data. It would take me days of work to test and bring my machine back to state of before via Backup. I need it currently every day an am not able to. I have already tested was P. Susi created to fix that bug. You can trust it works and implement as it is. Fact is: if you don't implement susi's fix ubuntu installs will still TOTALLY fail if you want to install on extended partitions of a Raid. If you implement it only can improve. What i can imagine to do, is to test with a life CD, updated to include fix, if the Raid is mounted and accessible, because either this did not work properly as far as i can remember. But please don't ask me to destroy my RAID for a further test. Thank You. kind regards Josef 2013/8/18 Launchpad Bug Tracker 1093...@bugs.launchpad.net ** Branch linked: lp:~ubuntu-branches/ubuntu/precise/multipath-tools /precise-proposed -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid Status in “multipath-tools” package in Ubuntu: Fix Released Status in “multipath-tools” source package in Precise: Fix Committed Status in “multipath-tools” source package in Quantal: Triaged Bug description: kpartx was mapping the entire extended partition then stacking the logical partitions on that device. This exposes a device that otherwise appears to be an entire disk device containing the logical partitions, and this confuses grub. The extended partition is supposed to only expose the first two sectors to allow LILO to be installed. The patch has been applied upstream now, and since this is the only change since quantal, a simple copy to quantal-updates should resolve it there as well. I have done this in my ppa and the reporter has verified it has fixed the issue. TEST CASE: Use fdisk to create an extended parition either on a fakeraid disk or an LVM logical volume. Run kpartx -a /dev/mapper/whatever to activate the partitions on the disk. Assuming the extended partition is number 3, then sudo blockdev --getsz /dev/mapper/whatever3 will report the apparent size of the extended partition. The size should only be 2 sectors regardless of the size of the extended partition. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1093918/+subscriptions -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1093918/+subscriptions -- 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
Re: [Bug 1093918] Re: grub-probe auto-detection fails on raid
Btw: i like Your Atari logo ... i am still owning a Mega STE and a Falcon, which i had to repair last time as battery of battery buffered NVRAM was dead. Now it still and again is alive !! :D 2013/8/24 Josef Klotzner josef.klotz...@gmail.com Sorry, but in the moment it will not be a good idea to destroy my RAID again only to know, if this would work also with new install. I have several OS Systems on the Raid besides ~ 1 TB data. It would take me days of work to test and bring my machine back to state of before via Backup. I need it currently every day an am not able to. I have already tested was P. Susi created to fix that bug. You can trust it works and implement as it is. Fact is: if you don't implement susi's fix ubuntu installs will still TOTALLY fail if you want to install on extended partitions of a Raid. If you implement it only can improve. What i can imagine to do, is to test with a life CD, updated to include fix, if the Raid is mounted and accessible, because either this did not work properly as far as i can remember. But please don't ask me to destroy my RAID for a further test. Thank You. kind regards Josef 2013/8/18 Launchpad Bug Tracker 1093...@bugs.launchpad.net ** Branch linked: lp:~ubuntu-branches/ubuntu/precise/multipath-tools /precise-proposed -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid Status in “multipath-tools” package in Ubuntu: Fix Released Status in “multipath-tools” source package in Precise: Fix Committed Status in “multipath-tools” source package in Quantal: Triaged Bug description: kpartx was mapping the entire extended partition then stacking the logical partitions on that device. This exposes a device that otherwise appears to be an entire disk device containing the logical partitions, and this confuses grub. The extended partition is supposed to only expose the first two sectors to allow LILO to be installed. The patch has been applied upstream now, and since this is the only change since quantal, a simple copy to quantal-updates should resolve it there as well. I have done this in my ppa and the reporter has verified it has fixed the issue. TEST CASE: Use fdisk to create an extended parition either on a fakeraid disk or an LVM logical volume. Run kpartx -a /dev/mapper/whatever to activate the partitions on the disk. Assuming the extended partition is number 3, then sudo blockdev --getsz /dev/mapper/whatever3 will report the apparent size of the extended partition. The size should only be 2 sectors regardless of the size of the extended partition. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1093918/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1093918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1093918] Re: grub-probe auto-detection fails on raid
Sorry, but in the moment it will not be a good idea to destroy my RAID again only to know, if this would work also with new install. I have several OS Systems on the Raid besides ~ 1 TB data. It would take me days of work to test and bring my machine back to state of before via Backup. I need it currently every day an am not able to. I have already tested was P. Susi created to fix that bug. You can trust it works and implement as it is. Fact is: if you don't implement susi's fix ubuntu installs will still TOTALLY fail if you want to install on extended partitions of a Raid. If you implement it only can improve. What i can imagine to do, is to test with a life CD, updated to include fix, if the Raid is mounted and accessible, because either this did not work properly as far as i can remember. But please don't ask me to destroy my RAID for a further test. Thank You. kind regards Josef 2013/8/18 Launchpad Bug Tracker 1093...@bugs.launchpad.net ** Branch linked: lp:~ubuntu-branches/ubuntu/precise/multipath-tools /precise-proposed -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid Status in “multipath-tools” package in Ubuntu: Fix Released Status in “multipath-tools” source package in Precise: Fix Committed Status in “multipath-tools” source package in Quantal: Triaged Bug description: kpartx was mapping the entire extended partition then stacking the logical partitions on that device. This exposes a device that otherwise appears to be an entire disk device containing the logical partitions, and this confuses grub. The extended partition is supposed to only expose the first two sectors to allow LILO to be installed. The patch has been applied upstream now, and since this is the only change since quantal, a simple copy to quantal-updates should resolve it there as well. I have done this in my ppa and the reporter has verified it has fixed the issue. TEST CASE: Use fdisk to create an extended parition either on a fakeraid disk or an LVM logical volume. Run kpartx -a /dev/mapper/whatever to activate the partitions on the disk. Assuming the extended partition is number 3, then sudo blockdev --getsz /dev/mapper/whatever3 will report the apparent size of the extended partition. The size should only be 2 sectors regardless of the size of the extended partition. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1093918/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1093918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 392089] Re: Slow USB transfer for FAT32
*** This bug is a duplicate of bug 500069 *** https://bugs.launchpad.net/bugs/500069 Hey Guys from ubuntu or linux! You make it too easy. It is no question of rasing a new issue or not. It is 2013 now you can use any version from 10.04 to 13.10 if you like and IT definitly C A N T never ever be, that windows is faster in file transfer as well with fat, fat32 or ntfs, but it is a shame to all - it definitly STILL is You might not see that the driver of fat32 or ntfs is a bottleneck if you are using an i7 running at 3 or more GHz. BUT as ALWAYS and everywhere in the world even with slowest and oldest CPU a USB 2.0 device is still slower and the REAL bottleneck a driver for a filesystem should NEVER EVER be slower than that. But it definitly is. Please escalate this bug if necessary directly to Linus Torvalds, because in my oppinion this must be immediatly improved. IMMEDIATE PERFORMANCE FIX NEEDED FOR ntfs, fat and fat32 drivers please forward to developers able to improve and fix thank you Ing. Josef Klotzner Supervisor at well known austrian (worldwide growing) company -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/392089 Title: Slow USB transfer for FAT32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/392089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1093918] Re: grub-probe auto-detection fails on raid
Dear Philip! i did new install today (30th april 2013) with 12.04.2 same bug it is still not in the updates !!! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1093918/+subscriptions -- 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 1093918] Re: grub-probe auto-detection fails on raid
Dear Philip! i did new install today (30th april 2013) with 12.04.2 same bug it is still not in the updates !!! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1093918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1159400] [NEW] unity usability lost
Public bug reported: in previous releases i just pressed power button for a second and pressed Enter for shutdown ... in 13.04 current version i need to press additionally arrow to left: power + arrow left + enter :( further: to call this bug report i only needed to press Alt+F2 and then enter ubuntu-bug unity and enter with 13.04 enter won't work ... need to select with mouse :D and upon this nautilus lost F3 split screen? who from debian had this crazy idea guys i just tested a few minutes and got disappointed :( ... stay with prevoius versions for sure and think ... ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 6.12.0daily13.03.13.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-13.22-generic 3.8.3 Uname: Linux 3.8.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.1-0ubuntu1 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,imgpng,grid,compiztoolbox,vpswitch,resize,snap,move,regex,gnomecompat,mousepoll,place,unitymtgrabhandles,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell] Date: Sun Mar 24 12:59:34 2013 InstallationDate: Installed on 2010-12-16 (828 days ago) InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) MarkForUpload: True ProcEnviron: LANGUAGE=de_DE:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1159400 Title: unity usability lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1159400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1159400] Re: unity usability lost
** Description changed: - in previous releases i just pressed power button for a second and pressed Enter for shutdown ... - in 13.04 current version i need to press additionally arrow to left: power + arrow left + enter :( + in previous releases i just pressed power button for a second and pressed Enter for shutdown ... + in 13.04 current version i need to press additionally arrow to left: power + arrow left + enter :( + edit: it got even worse with last update ... now i need to press arrow left 2 times! + so why not make shutdown default selection as it was before? - further: - to call this bug report i only needed to press Alt+F2 and then enter ubuntu-bug unity and enter - with 13.04 enter won't work ... - need to select with mouse :D + further: + to call this bug report i only needed to press Alt+F2 and then enter ubuntu-bug unity and enter + with 13.04 enter won't work ... + need to select with mouse :D and upon this nautilus lost F3 split screen? who from debian had this crazy idea guys i just tested a few minutes and got disappointed :( ... stay with prevoius versions for sure and think ... ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 6.12.0daily13.03.13.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-13.22-generic 3.8.3 Uname: Linux 3.8.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.1-0ubuntu1 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,imgpng,grid,compiztoolbox,vpswitch,resize,snap,move,regex,gnomecompat,mousepoll,place,unitymtgrabhandles,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell] Date: Sun Mar 24 12:59:34 2013 InstallationDate: Installed on 2010-12-16 (828 days ago) InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) MarkForUpload: True ProcEnviron: - LANGUAGE=de_DE:en - PATH=(custom, no user) - XDG_RUNTIME_DIR=set - LANG=de_DE.UTF-8 - SHELL=/bin/bash + LANGUAGE=de_DE:en + PATH=(custom, no user) + XDG_RUNTIME_DIR=set + LANG=de_DE.UTF-8 + SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: - in previous releases i just pressed power button for a second and pressed Enter for shutdown ... + in previous releases i just pressed power button for a second and pressed Enter for shutdown (because shutdown was default selction) ... in 13.04 current version i need to press additionally arrow to left: power + arrow left + enter :( edit: it got even worse with last update ... now i need to press arrow left 2 times! so why not make shutdown default selection as it was before? further: to call this bug report i only needed to press Alt+F2 and then enter ubuntu-bug unity and enter with 13.04 enter won't work ... need to select with mouse :D and upon this nautilus lost F3 split screen? who from debian had this crazy idea guys i just tested a few minutes and got disappointed :( ... stay with prevoius versions for sure and think ... ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 6.12.0daily13.03.13.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-13.22-generic 3.8.3 Uname: Linux 3.8.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.1-0ubuntu1 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,imgpng,grid,compiztoolbox,vpswitch,resize,snap,move,regex,gnomecompat,mousepoll,place,unitymtgrabhandles,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell] Date: Sun Mar 24 12:59:34 2013 InstallationDate: Installed on 2010-12-16 (828 days ago) InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) MarkForUpload: True ProcEnviron: LANGUAGE=de_DE:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: - in previous releases i just pressed power button for a second and pressed Enter for shutdown (because shutdown was default selction) ... + in previous releases i just pressed power button for a second and pressed Enter for shutdown (because shutdown was default selection) ... in 13.04 current version i need to press additionally arrow to left: power + arrow left + enter :( edit: it got even worse with last update ... now i need to press arrow left 2 times! so why not make shutdown default selection as it was before? further: to call this bug report i only needed to press Alt+F2 and then enter ubuntu-bug unity and enter with 13.04 enter won't work ... need to select with mouse :D and upon this nautilus lost F3 split screen? who from debian had this crazy idea guys i just tested a few minutes and got disappointed :( ...
[Bug 1093918] Re: grub-probe auto-detection fails on raid
Good Job! Nearly perfect ... only some error message left when doing 'sudo update-grub': josef@josef-maxtor-quad:~$ sudo dmsetup ls --tree [sudo] password for josef: via_jehhchjje9 (252:8) └─via_jehhchjje (252:1) ├─ (8:128) └─ (8:112) via_jehhchjje8 (252:7) └─via_jehhchjje (252:1) ├─ (8:128) └─ (8:112) via_jehhchjje7 (252:6) └─via_jehhchjje (252:1) ├─ (8:128) └─ (8:112) via_jehhchjje6 (252:5) └─via_jehhchjje (252:1) ├─ (8:128) └─ (8:112) via_jehhchjje5 (252:4) └─via_jehhchjje (252:1) ├─ (8:128) └─ (8:112) via_jehhchjje3 (252:3) └─via_jehhchjje (252:1) ├─ (8:128) └─ (8:112) via_jehhchjje2 (252:2) └─via_jehhchjje (252:1) ├─ (8:128) └─ (8:112) via_jehhchjje1 (252:0) └─via_jehhchjje (252:1) ├─ (8:128) └─ (8:112) josef@josef-maxtor-quad:~$ sudo update-grub Generating grub.cfg ... Found linux image: /boot/vmlinuz-3.2.0-35-generic Found initrd image: /boot/initrd.img-3.2.0-35-generic ERROR: ddf1: seeking device /dev/dm-3 to 18446744073709421056 ERROR: hpt37x: seeking device /dev/dm-3 to 4608 ERROR: hpt45x: seeking device /dev/dm-3 to 18446744073709547008 ERROR: isw: seeking device /dev/dm-3 to 18446744073708469760 ERROR: sil: seeking device /dev/dm-3 to 18446744073709289984 ERROR: ddf1: seeking device /dev/dm-3 to 18446744073709421056 ERROR: hpt37x: seeking device /dev/dm-3 to 4608 ERROR: hpt45x: seeking device /dev/dm-3 to 18446744073709547008 ERROR: isw: seeking device /dev/dm-3 to 18446744073708469760 ERROR: sil: seeking device /dev/dm-3 to 18446744073709289984 ERROR: ddf1: seeking device /dev/dm-3 to 18446744073709421056 ERROR: hpt37x: seeking device /dev/dm-3 to 4608 ERROR: hpt45x: seeking device /dev/dm-3 to 18446744073709547008 ERROR: isw: seeking device /dev/dm-3 to 18446744073708469760 ERROR: sil: seeking device /dev/dm-3 to 18446744073709289984 ERROR: ddf1: seeking device /dev/dm-3 to 18446744073709421056 ERROR: hpt37x: seeking device /dev/dm-3 to 4608 ERROR: hpt45x: seeking device /dev/dm-3 to 18446744073709547008 ERROR: isw: seeking device /dev/dm-3 to 18446744073708469760 ERROR: sil: seeking device /dev/dm-3 to 18446744073709289984 ERROR: ddf1: seeking device /dev/dm-3 to 18446744073709421056 ERROR: hpt37x: seeking device /dev/dm-3 to 4608 ERROR: hpt45x: seeking device /dev/dm-3 to 18446744073709547008 ERROR: isw: seeking device /dev/dm-3 to 18446744073708469760 ERROR: sil: seeking device /dev/dm-3 to 18446744073709289984 ERROR: ddf1: seeking device /dev/dm-3 to 18446744073709421056 ERROR: hpt37x: seeking device /dev/dm-3 to 4608 ERROR: hpt45x: seeking device /dev/dm-3 to 18446744073709547008 ERROR: isw: seeking device /dev/dm-3 to 18446744073708469760 ERROR: sil: seeking device /dev/dm-3 to 18446744073709289984 ERROR: ddf1: seeking device /dev/dm-3 to 18446744073709421056 ERROR: hpt37x: seeking device /dev/dm-3 to 4608 ERROR: hpt45x: seeking device /dev/dm-3 to 18446744073709547008 ERROR: isw: seeking device /dev/dm-3 to 18446744073708469760 ERROR: sil: seeking device /dev/dm-3 to 18446744073709289984 ERROR: ddf1: seeking device /dev/dm-3 to 18446744073709421056 ERROR: hpt37x: seeking device /dev/dm-3 to 4608 ERROR: hpt45x: seeking device /dev/dm-3 to 18446744073709547008 ERROR: isw: seeking device /dev/dm-3 to 18446744073708469760 ERROR: sil: seeking device /dev/dm-3 to 18446744073709289984 ERROR: ddf1: seeking device /dev/dm-3 to 18446744073709421056 ERROR: hpt37x: seeking device /dev/dm-3 to 4608 ERROR: hpt45x: seeking device /dev/dm-3 to 18446744073709547008 ERROR: isw: seeking device /dev/dm-3 to 18446744073708469760 ERROR: sil: seeking device /dev/dm-3 to 18446744073709289984 ERROR: ddf1: seeking device /dev/dm-3 to 18446744073709421056 ERROR: hpt37x: seeking device /dev/dm-3 to 4608 ERROR: hpt45x: seeking device /dev/dm-3 to 18446744073709547008 ERROR: isw: seeking device /dev/dm-3 to 18446744073708469760 ERROR: sil: seeking device /dev/dm-3 to 18446744073709289984 ERROR: ddf1: seeking device /dev/dm-3 to 18446744073709421056 ERROR: hpt37x: seeking device /dev/dm-3 to 4608 ERROR: hpt45x: seeking device /dev/dm-3 to 18446744073709547008 ERROR: isw: seeking device /dev/dm-3 to 18446744073708469760 ERROR: sil: seeking device /dev/dm-3 to 18446744073709289984 ERROR: ddf1: seeking device /dev/dm-3 to 18446744073709421056 ERROR: hpt37x: seeking device /dev/dm-3 to 4608 ERROR: hpt45x: seeking device /dev/dm-3 to 18446744073709547008 ERROR: isw: seeking device /dev/dm-3 to 18446744073708469760 ERROR: sil: seeking device /dev/dm-3 to 18446744073709289984 ERROR: ddf1: seeking device /dev/dm-3 to 18446744073709421056 ERROR: hpt37x: seeking device /dev/dm-3 to 4608 ERROR: hpt45x: seeking device /dev/dm-3 to 18446744073709547008 ERROR: isw: seeking device /dev/dm-3 to 18446744073708469760 ERROR: sil: seeking device /dev/dm-3 to 18446744073709289984 ERROR: ddf1: seeking device /dev/dm-3 to 18446744073709421056 ERROR: hpt37x: seeking device /dev/dm-3 to 4608 ERROR: hpt45x: seeking device /dev/dm-3 to 18446744073709547008 ERROR: isw:
[Bug 1093918] Re: grub-probe auto-detection fails on raid
Good Job! Nearly perfect ... only some error message left when doing 'sudo update-grub': josef@josef-maxtor-quad:~$ sudo dmsetup ls --tree [sudo] password for josef: via_jehhchjje9 (252:8) └─via_jehhchjje (252:1) ├─ (8:128) └─ (8:112) via_jehhchjje8 (252:7) └─via_jehhchjje (252:1) ├─ (8:128) └─ (8:112) via_jehhchjje7 (252:6) └─via_jehhchjje (252:1) ├─ (8:128) └─ (8:112) via_jehhchjje6 (252:5) └─via_jehhchjje (252:1) ├─ (8:128) └─ (8:112) via_jehhchjje5 (252:4) └─via_jehhchjje (252:1) ├─ (8:128) └─ (8:112) via_jehhchjje3 (252:3) └─via_jehhchjje (252:1) ├─ (8:128) └─ (8:112) via_jehhchjje2 (252:2) └─via_jehhchjje (252:1) ├─ (8:128) └─ (8:112) via_jehhchjje1 (252:0) └─via_jehhchjje (252:1) ├─ (8:128) └─ (8:112) josef@josef-maxtor-quad:~$ sudo update-grub Generating grub.cfg ... Found linux image: /boot/vmlinuz-3.2.0-35-generic Found initrd image: /boot/initrd.img-3.2.0-35-generic ERROR: ddf1: seeking device /dev/dm-3 to 18446744073709421056 ERROR: hpt37x: seeking device /dev/dm-3 to 4608 ERROR: hpt45x: seeking device /dev/dm-3 to 18446744073709547008 ERROR: isw: seeking device /dev/dm-3 to 18446744073708469760 ERROR: sil: seeking device /dev/dm-3 to 18446744073709289984 ERROR: ddf1: seeking device /dev/dm-3 to 18446744073709421056 ERROR: hpt37x: seeking device /dev/dm-3 to 4608 ERROR: hpt45x: seeking device /dev/dm-3 to 18446744073709547008 ERROR: isw: seeking device /dev/dm-3 to 18446744073708469760 ERROR: sil: seeking device /dev/dm-3 to 18446744073709289984 ERROR: ddf1: seeking device /dev/dm-3 to 18446744073709421056 ERROR: hpt37x: seeking device /dev/dm-3 to 4608 ERROR: hpt45x: seeking device /dev/dm-3 to 18446744073709547008 ERROR: isw: seeking device /dev/dm-3 to 18446744073708469760 ERROR: sil: seeking device /dev/dm-3 to 18446744073709289984 ERROR: ddf1: seeking device /dev/dm-3 to 18446744073709421056 ERROR: hpt37x: seeking device /dev/dm-3 to 4608 ERROR: hpt45x: seeking device /dev/dm-3 to 18446744073709547008 ERROR: isw: seeking device /dev/dm-3 to 18446744073708469760 ERROR: sil: seeking device /dev/dm-3 to 18446744073709289984 ERROR: ddf1: seeking device /dev/dm-3 to 18446744073709421056 ERROR: hpt37x: seeking device /dev/dm-3 to 4608 ERROR: hpt45x: seeking device /dev/dm-3 to 18446744073709547008 ERROR: isw: seeking device /dev/dm-3 to 18446744073708469760 ERROR: sil: seeking device /dev/dm-3 to 18446744073709289984 ERROR: ddf1: seeking device /dev/dm-3 to 18446744073709421056 ERROR: hpt37x: seeking device /dev/dm-3 to 4608 ERROR: hpt45x: seeking device /dev/dm-3 to 18446744073709547008 ERROR: isw: seeking device /dev/dm-3 to 18446744073708469760 ERROR: sil: seeking device /dev/dm-3 to 18446744073709289984 ERROR: ddf1: seeking device /dev/dm-3 to 18446744073709421056 ERROR: hpt37x: seeking device /dev/dm-3 to 4608 ERROR: hpt45x: seeking device /dev/dm-3 to 18446744073709547008 ERROR: isw: seeking device /dev/dm-3 to 18446744073708469760 ERROR: sil: seeking device /dev/dm-3 to 18446744073709289984 ERROR: ddf1: seeking device /dev/dm-3 to 18446744073709421056 ERROR: hpt37x: seeking device /dev/dm-3 to 4608 ERROR: hpt45x: seeking device /dev/dm-3 to 18446744073709547008 ERROR: isw: seeking device /dev/dm-3 to 18446744073708469760 ERROR: sil: seeking device /dev/dm-3 to 18446744073709289984 ERROR: ddf1: seeking device /dev/dm-3 to 18446744073709421056 ERROR: hpt37x: seeking device /dev/dm-3 to 4608 ERROR: hpt45x: seeking device /dev/dm-3 to 18446744073709547008 ERROR: isw: seeking device /dev/dm-3 to 18446744073708469760 ERROR: sil: seeking device /dev/dm-3 to 18446744073709289984 ERROR: ddf1: seeking device /dev/dm-3 to 18446744073709421056 ERROR: hpt37x: seeking device /dev/dm-3 to 4608 ERROR: hpt45x: seeking device /dev/dm-3 to 18446744073709547008 ERROR: isw: seeking device /dev/dm-3 to 18446744073708469760 ERROR: sil: seeking device /dev/dm-3 to 18446744073709289984 ERROR: ddf1: seeking device /dev/dm-3 to 18446744073709421056 ERROR: hpt37x: seeking device /dev/dm-3 to 4608 ERROR: hpt45x: seeking device /dev/dm-3 to 18446744073709547008 ERROR: isw: seeking device /dev/dm-3 to 18446744073708469760 ERROR: sil: seeking device /dev/dm-3 to 18446744073709289984 ERROR: ddf1: seeking device /dev/dm-3 to 18446744073709421056 ERROR: hpt37x: seeking device /dev/dm-3 to 4608 ERROR: hpt45x: seeking device /dev/dm-3 to 18446744073709547008 ERROR: isw: seeking device /dev/dm-3 to 18446744073708469760 ERROR: sil: seeking device /dev/dm-3 to 18446744073709289984 ERROR: ddf1: seeking device /dev/dm-3 to 18446744073709421056 ERROR: hpt37x: seeking device /dev/dm-3 to 4608 ERROR: hpt45x: seeking device /dev/dm-3 to 18446744073709547008 ERROR: isw: seeking device /dev/dm-3 to 18446744073708469760 ERROR: sil: seeking device /dev/dm-3 to 18446744073709289984 ERROR: ddf1: seeking device /dev/dm-3 to 18446744073709421056 ERROR: hpt37x: seeking device /dev/dm-3 to 4608 ERROR: hpt45x: seeking device /dev/dm-3 to 18446744073709547008 ERROR: isw:
[Bug 1093918] Re: grub-probe auto-detection fails on raid
and now? can i do something meanwhile, or need to wait for some nice guy to bugfix kpartx ?? does bug report need an updated title? :D -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1093918/+subscriptions -- 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 1093918] Re: grub-probe auto-detection fails on raid
josef@josef-maxtor-quad:~$ ls -al /sys/block/dm-3/holders/ insgesamt 0 drwxr-xr-x 2 root root 0 Jän 4 20:43 . drwxr-xr-x 8 root root 0 Jän 4 20:43 .. lrwxrwxrwx 1 root root 0 Jän 4 20:47 dm-4 - ../../dm-4 lrwxrwxrwx 1 root root 0 Jän 4 20:47 dm-5 - ../../dm-5 lrwxrwxrwx 1 root root 0 Jän 4 20:47 dm-6 - ../../dm-6 lrwxrwxrwx 1 root root 0 Jän 4 20:47 dm-7 - ../../dm-7 lrwxrwxrwx 1 root root 0 Jän 4 20:47 dm-8 - ../../dm-8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1093918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1093918] Re: grub-probe auto-detection fails on raid
and now? can i do something meanwhile, or need to wait for some nice guy to bugfix kpartx ?? does bug report need an updated title? :D -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1093918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1093918] Re: grub-probe auto-detection fails on raid
Dear Phillip and maybe others involved! Please read the following carefully to understand the situation completely: Since yesterday i tried to work around by bying a SSD to boot from, B U T !!! it seems the problem causing grub-probe to fail are raid drivers (i don't know sure if dmraid currently) AND this problem does not only occur while trying to upgrade from ubuntu 11.10 to 12.04, it also occurs when trying to make a new install on any other harddisk than raid in the system, (like my new SSD) as long as a raid device is present in the system i tried new installation with ubuntu 12.04 onto the SSD a few times: failing installation process gets stuck immediatly after having set up where to install ... installer stucks at page of country to select currently i am writing this out of a ubuntu 11.10 live CD where installation on SSD worked like charm without that i have changed anything manually now -- look at this (no via_jehhchjje3 in between!): ubuntu@ubuntu:~$ sudo dmsetup ls --tree via_jehhchjje9 (253:8) └─via_jehhchjje (253:0) ├─ (8:48) └─ (8:32) via_jehhchjje8 (253:7) └─via_jehhchjje (253:0) ├─ (8:48) └─ (8:32) via_jehhchjje7 (253:6) └─via_jehhchjje (253:0) ├─ (8:48) └─ (8:32) via_jehhchjje6 (253:5) └─via_jehhchjje (253:0) ├─ (8:48) └─ (8:32) via_jehhchjje5 (253:4) └─via_jehhchjje (253:0) ├─ (8:48) └─ (8:32) via_jehhchjje2 (253:3) └─via_jehhchjje (253:0) ├─ (8:48) └─ (8:32) via_jehhchjje1 (253:1) └─via_jehhchjje (253:0) ├─ (8:48) └─ (8:32) perfect ! like it should be i also observed when trying failing installation with 12.04 that the list of partitions presented was absolutely incorrect for raid -- there were not only the partitions itself listed once, they were listed again further down and each single partition twice ! -- one each selectable for installation of system even as i tried to install to SSD with ubuntu 12.04 installer and NOT to raid, it failed -- obviously due to the wrong presented raid in the system, causing the installer to fail. with ubuntu 11.10 live CD also parted -l lists without interrupting the output (and is NOT waiting for input as it does under 12.04 -- and i am pretty sure that grub-install and update-grub fails because of that): ubuntu@ubuntu:~$ sudo parted -l Model: ATA ST2000DL003-9VT1 (scsi) Disk /dev/sda: 2000GB Sector size (logical/physical): 512B/4096B Partition Table: msdos Number Start End SizeType File system Flags 1 1049kB 39,6GB 39,6GB primary ntfs 2 39,6GB 92,0GB 52,4GB primary ntfs 3 92,0GB 1979GB 1887GB primary ntfs 4 1979GB 2000GB 21,0GB extended 5 1979GB 1998GB 18,9GB logical ext4 6 1998GB 2000GB 2096MB logical linux-swap(v1) Model: ATA OCZ-VERTEX4 (scsi) Disk /dev/sdb: 128GB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End SizeType File system Flags 1 1049kB 33,7GB 33,7GB primary ntfsboot 2 33,7GB 107GB 73,4GB primary ntfs 3 107GB 128GB 21,0GB extended 5 107GB 126GB 18,9GB logical ext4 6 126GB 128GB 2096MB logical linux-swap(v1) Error: Can't have a partition outside the disk! Error: /dev/sdd: unrecognised disk label Model: Linux device-mapper (striped) (dm) Disk /dev/mapper/via_jehhchjje: 2000GB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End SizeType File system Flags 1 8225kB 43,0GB 43,0GB primary ntfsboot 2 43,0GB 95,4GB 52,4GB primary ntfs 3 95,4GB 2000GB 1905GB extended 5 95,4GB 148GB 52,4GB logical ntfs 6 148GB 1963GB 1815GB logical ntfs 7 1963GB 1984GB 21,0GB logical ext4raid 8 1984GB 1998GB 14,7GB logical ext4raid 9 1998GB 2000GB 2096MB logical linux-swap(v1) also this is presented different when doing with ubuntu 11.10 live CD (open count is 3 as you can see with 12.04 above and also major was 252 above: ubuntu@ubuntu:~$ sudo dmsetup info /dev/mapper/via_jehhchjje Name: via_jehhchjje State: ACTIVE Read Ahead:256 Tables present:LIVE Open count:7 Event number: 0 Major, minor: 253, 0 Number of targets: 1 UUID: DMRAID-via_jehhchjje this output is the only identical: ubuntu@ubuntu:~$ sudo blockdev --getsize64 /dev/mapper/via_jehhchjje 2000409722880 ... so it looks like more being a dmraid / dmsetup / raid driver problem only effecting grub-install and update-grub in ubuntu 12.04 could you please help to brake down to find the real root cause? ... that then the real root cause bug can be fixed? :D -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection
[Bug 1093918] Re: grub-probe auto-detection fails on raid
no, i was not able to change anything with dmsetup in 12.04 ... only got error messages that this is not possible ... i don't know how to do as your proposal does not work :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1093918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1093918] Re: grub-probe auto-detection fails on raid
ok - sorry - needed to rebuild the raid to answer your question, because i tried at least one work around: deactivating the raid :( . josef@josef-maxtor-quad:~$ sudo sudo dmsetup remove via_hehhchjje3 [sudo] password for josef: device-mapper: remove ioctl failed: Kein passendes Gerät bzw. keine passende Adresse gefunden Command failed . 'Kein passendes Gerät bzw. keine passende Adresse gefunden' means: no fitting device or adress found -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1093918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1093918] Re: grub-probe auto-detection fails on raid
yes - the name was misspelled -- the correct name is via_jahhchjje3 and not via_hehhchjje3 but i only end up with different error message - sorry that it took longer - i deleted whole raid by error and built it new ... i made backup of all partitions with fsarchiver before and do currently recover the raid ... os's are back ... only data to copy .. can do later josef@josef-maxtor-quad:~$ sudo dmsetup remove /dev/mapper/via_jehhchjje3 device-mapper: remove ioctl failed: Das Gerät oder die Ressource ist belegt Command failed Das Gerät oder die Ressource ist belegt means device or resource is busy but no partition is mounted :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1093918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1093918] Re: grub-probe auto-detection fails on raid
nothing changed with ubuntu 12.04 the tree looks like above with via_jehhchjje3 in between while ubuntu 11.10 still shows and behaves correct -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1093918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1093918] Re: grub-probe auto-detection fails on raid
josef@josef-maxtor-quad:~$ sudo blockdev --getsize64 /dev/mapper/via_jehhchjje [sudo] password for josef: 2000409722880 josef@josef-maxtor-quad:~$ josef@josef-maxtor-quad:~$ sudo dmsetup info /dev/mapper/via_jehhchjje Name: via_jehhchjje State: ACTIVE Read Ahead:256 Tables present:LIVE Open count:3 Event number: 0 Major, minor: 252, 1 Number of targets: 1 UUID: DMRAID-via_jehhchjje if you really still think that i can workaround for the meantime with changing stuff in device.map please tell me what should i add there -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1093918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1093918] Re: grub-probe auto-detection fails on raid
/dev/sdg (via): 0x000 signature: 0xaa55 0x002 version_number: 2 0x003 array.disk.bootable: 0 0x003 array.disk.enable_enhanced: 0 0x003 array.disk.in_disk_array: 1 0x003 array.disk.raid_type: 0 0x003 array.disk.array_index: 0 0x003 array.disk.raid_type_info: 1 0x003 array.disk.raid_type_info(INDEX): 1 0x003 array.disk.raid_type_info(MIRROR): 0 0x003 array.disk.raid_type_info(DIRTY): 0 0x003 array.disk.tolerance: 0 0x005 array.disk_array_ex: 0x42 0x006 array.capacity_low: 1953525120 0x00a array.capacity_high: 0 0x00e array.serial_checksum: 415831831 0x012 serial_checksum[0]: 531896097 0x016 serial_checksum[1]: 415831831 0x01a serial_checksum[2]: 0 0x01e serial_checksum[3]: 0 0x022 serial_checksum[4]: 0 0x026 serial_checksum[5]: 0 0x02a serial_checksum[6]: 0 0x02e serial_checksum[7]: 0 0x032 checksum: 69 /dev/sdf (via): 0x000 signature: 0xaa55 0x002 version_number: 2 0x003 array.disk.bootable: 0 0x003 array.disk.enable_enhanced: 0 0x003 array.disk.in_disk_array: 1 0x003 array.disk.raid_type: 0 0x003 array.disk.array_index: 0 0x003 array.disk.raid_type_info: 0 0x003 array.disk.raid_type_info(INDEX): 0 0x003 array.disk.raid_type_info(MIRROR): 0 0x003 array.disk.raid_type_info(DIRTY): 0 0x003 array.disk.tolerance: 0 0x005 array.disk_array_ex: 0x42 0x006 array.capacity_low: 1953525120 0x00a array.capacity_high: 0 0x00e array.serial_checksum: 531896097 0x012 serial_checksum[0]: 531896097 0x016 serial_checksum[1]: 415831831 0x01a serial_checksum[2]: 0 0x01e serial_checksum[3]: 0 0x022 serial_checksum[4]: 0 0x026 serial_checksum[5]: 0 0x02a serial_checksum[6]: 0 0x02e serial_checksum[7]: 0 0x032 checksum: 61 2012/12/28 Phillip Susi ps...@ubuntu.com sudo 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/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1093918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1093918] Re: grub-probe auto-detection fails on raid
/dev/sdg (via): 0x000 signature: 0xaa55 0x002 version_number: 2 0x003 array.disk.bootable: 0 0x003 array.disk.enable_enhanced: 0 0x003 array.disk.in_disk_array: 1 0x003 array.disk.raid_type: 0 0x003 array.disk.array_index: 0 0x003 array.disk.raid_type_info: 1 0x003 array.disk.raid_type_info(INDEX): 1 0x003 array.disk.raid_type_info(MIRROR): 0 0x003 array.disk.raid_type_info(DIRTY): 0 0x003 array.disk.tolerance: 0 0x005 array.disk_array_ex: 0x42 0x006 array.capacity_low: 1953525120 0x00a array.capacity_high: 0 0x00e array.serial_checksum: 415831831 0x012 serial_checksum[0]: 531896097 0x016 serial_checksum[1]: 415831831 0x01a serial_checksum[2]: 0 0x01e serial_checksum[3]: 0 0x022 serial_checksum[4]: 0 0x026 serial_checksum[5]: 0 0x02a serial_checksum[6]: 0 0x02e serial_checksum[7]: 0 0x032 checksum: 69 /dev/sdf (via): 0x000 signature: 0xaa55 0x002 version_number: 2 0x003 array.disk.bootable: 0 0x003 array.disk.enable_enhanced: 0 0x003 array.disk.in_disk_array: 1 0x003 array.disk.raid_type: 0 0x003 array.disk.array_index: 0 0x003 array.disk.raid_type_info: 0 0x003 array.disk.raid_type_info(INDEX): 0 0x003 array.disk.raid_type_info(MIRROR): 0 0x003 array.disk.raid_type_info(DIRTY): 0 0x003 array.disk.tolerance: 0 0x005 array.disk_array_ex: 0x42 0x006 array.capacity_low: 1953525120 0x00a array.capacity_high: 0 0x00e array.serial_checksum: 531896097 0x012 serial_checksum[0]: 531896097 0x016 serial_checksum[1]: 415831831 0x01a serial_checksum[2]: 0 0x01e serial_checksum[3]: 0 0x022 serial_checksum[4]: 0 0x026 serial_checksum[5]: 0 0x02a serial_checksum[6]: 0 0x02e serial_checksum[7]: 0 0x032 checksum: 61 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1093918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1093918] Re: grub-probe auto-detection fails on raid
why should the mirror be broken? if so, this ALSO would fail, but does not!: sudo grub-probe -vd /dev/dm-6 and (!) ... keep in mind as i told you the raid still WORKS without any errors with ubuntu 11.10 and related standard ubuntu version of grub there (ok --- this info was within lots of characters of information in description part :D) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1093918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1093918] Re: grub-probe auto-detection fails on raid
and ... this is 3rd time now that i ask this please: if you really still think that i can workaround for the meantime with changing stuff in device.map please tell me what should i add there -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1093918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1093918] Re: grub-probe auto-detection fails on raid
thanks, but this is one of hundreds of constellations i already checked out from my listing above you would know, that (hd3) /dev/mapper/via_jehhchjje ^ would be correct in my case. anyway -- NO chance seems not being possible to workaround this bug. my current device.map fyi: (fd0) /dev/fd0 (hd0) /dev/disk/by-id/ata-ST31000528AS_6VP9JJJG (hd1) /dev/disk/by-id/ata-ST1000DL002-9TT153_W1V09RY5 (hd2) /dev/disk/by-id/ata-ST1000DL002-9TT153_W1V09HRJ (hd3) /dev/mapper/via_jehhchjje (hd3,1) /dev/mapper/via_jehhchjje1 (hd3,2) /dev/mapper/via_jehhchjje2 (hd3,5) /dev/mapper/via_jehhchjje5 (hd3,7) /dev/disk/by-uuid/90ac6970-5f11-442d-8b51-c336f9e4149c (hd3,8) /dev/disk/by-uuid/f5768a22-a5a9-4ee2-93fa-c2396573dbcf it makes no difference for the line with hd3,7 and hd3,8 if it written with UUID or like this: (hd3,7) /dev/dev/mapper/via_jehhchjje7 (hd3,8) /dev/dev/mapper/via_jehhchjje8 or even (hd3,7) /dev/dm-6 (hd3,8) /dev/dm-7 absolutly no change in error message when update-grub: josef@josef-maxtor-quad:~$ sudo update-grub Generating grub.cfg ... Found linux image: /boot/vmlinuz-3.2.0-35-generic Found initrd image: /boot/initrd.img-3.2.0-35-generic umount: /var/lib/os-prober/mount ist nicht eingehängt rmdir: konnte »/var/lib/os-prober/mount“ nicht entfernen: Das Gerät oder die Ressource ist belegt rmdir: konnte »/var/lib/os-prober/mount“ nicht entfernen: Das Gerät oder die Ressource ist belegt rmdir: konnte »/var/lib/os-prober/mount“ nicht entfernen: Das Gerät oder die Ressource ist belegt rmdir: konnte »/var/lib/os-prober/mount“ nicht entfernen: Das Gerät oder die Ressource ist belegt rmdir: konnte »/var/lib/os-prober/mount“ nicht entfernen: Das Gerät oder die Ressource ist belegt grub-probe: Fehler: cannot find a GRUB drive for /dev/mapper/via_jehhchjje7. Check your device.map. grub-probe: Fehler: cannot find a GRUB drive for /dev/mapper/via_jehhchjje8. Check your device.map. Found Windows 7 (loader) on /dev/mapper/via_jehhchjje1 Found Windows Vista (loader) on /dev/mapper/via_jehhchjje2 done even same error message without any device.map file . could someone have a look to the code in grub-probe please ??!!??!! or are we just discussing (talking in a circle without any outcome?!) here? . as far as i remember there was similar situation in the past when upgrading from 10.04 to 10.10 . issue was solved in the past, but same error popped back . maybe someone in the past forgot to feed back the code changes in grub to http://www.gnu.org/ for root of any code changes in grub ??!!?? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1093918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1093918] Re: grub-probe auto-detection fails on raid
i already wrote that this makes no difference -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1093918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1093918] Re: grub-probe auto-detection fails on raid
i only created file device.map manually, because of the error message, but as i already posted i think more than 3 times now: . NO CHANGE -- AND NO EFFECT to the reason of the bug (of course output is slightly different) . removed partitions anyway now: after sudo grub-mkdevicemap : josef@josef-maxtor-quad:~$ cat /boot/grub/device.map (fd0) /dev/fd0 (hd0) /dev/disk/by-id/ata-ST31000528AS_6VP9JJJG (hd1) /dev/disk/by-id/ata-ST1000DL002-9TT153_W1V09RY5 (hd2) /dev/disk/by-id/ata-ST1000DL002-9TT153_W1V09HRJ (hd3) /dev/mapper/via_jehhchjje -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1093918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1093918] Re: grub-probe auto-detection fails on raid
if you are DEFINITLY NOT READING WHAT I POST then please read this: device.map is not the root cause of the problem please forward this bug to someone who is able to bugfix in code of grub-probe ... otherwise i will start doing that myself :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1093918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1093918] Re: grub-probe auto-detection fails on raid
if i would have liked to discuss the topic i would have posted that to a forum with most likely useless effort. . THIS HERE - i thought - is more likely to report a bug that someone takes care of and starts working in studiing some code possibly causing the bug . i am a bit upset -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1093918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1093918] Re: grub-probe auto-detection fails on raid
josef@josef-maxtor-quad:~$ sudo dmsetup ls --tree
via_jehhchjje9 (252:8)
└─via_jehhchjje3 (252:3)
└─via_jehhchjje (252:1)
├─ (8:96)
└─ (8:80)
via_jehhchjje8 (252:7)
└─via_jehhchjje3 (252:3)
└─via_jehhchjje (252:1)
├─ (8:96)
└─ (8:80)
via_jehhchjje7 (252:6)
└─via_jehhchjje3 (252:3)
└─via_jehhchjje (252:1)
├─ (8:96)
└─ (8:80)
via_jehhchjje6 (252:5)
└─via_jehhchjje3 (252:3)
└─via_jehhchjje (252:1)
├─ (8:96)
└─ (8:80)
via_jehhchjje5 (252:4)
└─via_jehhchjje3 (252:3)
└─via_jehhchjje (252:1)
├─ (8:96)
└─ (8:80)
via_jehhchjje2 (252:2)
└─via_jehhchjje (252:1)
├─ (8:96)
└─ (8:80)
via_jehhchjje1 (252:0)
└─via_jehhchjje (252:1)
├─ (8:96)
└─ (8:80)
josef@josef-maxtor-quad:~$ sudo grub-probe -t device (hd3)
bash: Syntaxfehler beim unerwarteten Wort `('
sure to pass parameters like this, because getting error message
complaining the '(' ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1093918
Title:
grub-probe auto-detection fails on raid
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1093918/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1093918] Re: grub-probe auto-detection fails on raid
josef@josef-maxtor-quad:~$ sudo grub-probe -vt device (hd3) grub-probe: Info: `/dev/fd0' looks like a floppy drive, skipping. grub-probe: Info: Scanning for dmraid_nv RAID devices on disk hd0. grub-probe: Info: the size of hd0 is 1953525168. grub-probe: Info: the size of hd0 is 1953525168. grub-probe: Info: Scanning for dmraid_nv RAID devices on disk hd1. grub-probe: Info: the size of hd1 is 1953525168. grub-probe: Info: the size of hd1 is 1953525168. grub-probe: Info: Scanning for dmraid_nv RAID devices on disk hd2. grub-probe: Info: the size of hd2 is 1953525168. grub-probe: Info: the size of hd2 is 1953525168. grub-probe: Info: Scanning for dmraid_nv RAID devices on disk hd3. grub-probe: Info: the size of hd3 is 3907050240. grub-probe: Info: the size of hd3 is 3907050240. grub-probe: Info: scanning hd0 for LVM. grub-probe: Info: the size of hd0 is 1953525168. grub-probe: Info: no LVM signature found. grub-probe: Info: the size of hd0 is 1953525168. grub-probe: Info: scanning hd1 for LVM. grub-probe: Info: the size of hd1 is 1953525168. grub-probe: Info: no LVM signature found. grub-probe: Info: the size of hd1 is 1953525168. grub-probe: Info: scanning hd2 for LVM. grub-probe: Info: the size of hd2 is 1953525168. grub-probe: Info: no LVM signature found. grub-probe: Info: the size of hd2 is 1953525168. grub-probe: Info: scanning hd3 for LVM. grub-probe: Info: the size of hd3 is 3907050240. grub-probe: Info: no LVM signature found. grub-probe: Info: the size of hd3 is 3907050240. grub-probe: Info: Scanning for mdraid09 RAID devices on disk hd0. grub-probe: Info: the size of hd0 is 1953525168. grub-probe: Info: the size of hd0 is 1953525168. grub-probe: Info: Scanning for mdraid09 RAID devices on disk hd1. grub-probe: Info: the size of hd1 is 1953525168. grub-probe: Info: the size of hd1 is 1953525168. grub-probe: Info: Scanning for mdraid09 RAID devices on disk hd2. grub-probe: Info: the size of hd2 is 1953525168. grub-probe: Info: the size of hd2 is 1953525168. grub-probe: Info: Scanning for mdraid09 RAID devices on disk hd3. grub-probe: Info: the size of hd3 is 3907050240. grub-probe: Info: the size of hd3 is 3907050240. grub-probe: Info: Scanning for mdraid1x RAID devices on disk hd0. grub-probe: Info: the size of hd0 is 1953525168. grub-probe: Info: the size of hd0 is 1953525168. grub-probe: Info: Scanning for mdraid1x RAID devices on disk hd1. grub-probe: Info: the size of hd1 is 1953525168. grub-probe: Info: the size of hd1 is 1953525168. grub-probe: Info: Scanning for mdraid1x RAID devices on disk hd2. grub-probe: Info: the size of hd2 is 1953525168. grub-probe: Info: the size of hd2 is 1953525168. grub-probe: Info: Scanning for mdraid1x RAID devices on disk hd3. grub-probe: Info: the size of hd3 is 3907050240. grub-probe: Info: the size of hd3 is 3907050240. grub-probe: Info: Scanning for mdraid09 RAID devices on disk hd0. grub-probe: Info: the size of hd0 is 1953525168. grub-probe: Info: the size of hd0 is 1953525168. grub-probe: Info: Scanning for mdraid09 RAID devices on disk hd0,msdos6. grub-probe: Info: the size of hd0 is 1953525168. grub-probe: Info: Scanning for mdraid09 RAID devices on disk hd0,msdos5. grub-probe: Info: the size of hd0 is 1953525168. grub-probe: Info: Scanning for mdraid09 RAID devices on disk hd0,msdos3. grub-probe: Info: the size of hd0 is 1953525168. grub-probe: Info: Scanning for mdraid09 RAID devices on disk hd0,msdos2. grub-probe: Info: the size of hd0 is 1953525168. grub-probe: Info: Scanning for mdraid09 RAID devices on disk hd0,msdos1. grub-probe: Info: the size of hd0 is 1953525168. grub-probe: Info: Scanning for mdraid09 RAID devices on disk hd1. grub-probe: Info: the size of hd1 is 1953525168. grub-probe: Info: the size of hd1 is 1953525168. grub-probe: Info: Scanning for mdraid09 RAID devices on disk hd1,msdos2. grub-probe: Info: the size of hd1 is 1953525168. grub-probe: Info: Scanning for mdraid09 RAID devices on disk hd1,msdos1. grub-probe: Info: the size of hd1 is 1953525168. grub-probe: Info: Scanning for mdraid09 RAID devices on disk hd2. grub-probe: Info: the size of hd2 is 1953525168. grub-probe: Info: the size of hd2 is 1953525168. grub-probe: Info: Scanning for mdraid09 RAID devices on disk hd3. grub-probe: Info: the size of hd3 is 3907050240. grub-probe: Info: the size of hd3 is 3907050240. grub-probe: Info: Scanning for mdraid09 RAID devices on disk hd3,msdos9. grub-probe: Info: the size of hd3 is 3907050240. grub-probe: Info: Scanning for mdraid09 RAID devices on disk hd3,msdos8. grub-probe: Info: the size of hd3 is 3907050240. grub-probe: Info: Scanning for mdraid09 RAID devices on disk hd3,msdos7. grub-probe: Info: the size of hd3 is 3907050240. grub-probe: Info: Scanning for mdraid09 RAID devices on disk hd3,msdos6. grub-probe: Info: the size of hd3 is 3907050240. grub-probe: Info: Scanning for mdraid09 RAID devices on disk hd3,msdos5. grub-probe: Info: the size of hd3 is 3907050240. grub-probe: Info: Scanning for mdraid09 RAID devices on disk
[Bug 1093918] Re: grub-probe auto-detection fails on raid
if 'parted -l' is used within grub-probe this could cause problems, as i saw -- i only could get an output by two times ignoring errors as you can see maybe this could also help: josef@josef-maxtor-quad:~$ sudo parted -l Modell: ATA ST31000528AS (scsi) Festplatte /dev/sda: 1000GB Sektorgröße (logisch/physisch): 512B/512B Partitionstabelle: msdos Nummer Anfang EndeGröße Typ Dateisystem Flags 1 32,3kB 32,2GB 32,2GB primary ntfs 2 32,2GB 75,2GB 43,0GB primary ntfsboot 3 75,2GB 988GB 912GB primary ntfs 4 988GB 1000GB 12,6GB extended 5 988GB 998GB 10,5GB logical ext4 6 998GB 1000GB 2095MB logical linux-swap(v1) Fehler: Partitionen ausserhalb der Festplatte sind nicht möglich! Modell: Linux-Device-Mapper (linear) (dm) Festplatte /dev/mapper/via_jehhchjje6: 1815GB Sektorgröße (logisch/physisch): 512B/512B Partitionstabelle: loop Nummer Anfang EndeGröße Dateisystem Flags 1 0,00B 1815GB 1815GB ntfs Fehler: Das Argument ist ungültig, während /dev/mapper/via_jehhchjje3 zum Lesen positioniert wurde Wiederholen/Retry/Ignorieren/Ignore/Abbrechen/Cancel? i parted: Unbekanntes Zeichen: i Wiederholen/Retry/Ignorieren/Ignore/Abbrechen/Cancel? I parted: Unbekanntes Zeichen: I Wiederholen/Retry/Ignorieren/Ignore/Abbrechen/Cancel? r Fehler: Das Argument ist ungültig, während /dev/mapper/via_jehhchjje3 zum Lesen positioniert wurde Wiederholen/Retry/Ignorieren/Ignore/Abbrechen/Cancel? ignore Fehler: Ungültige Partitionstabelle auf /dev/mapper/via_jehhchjje3 -- falsche Signatur 0. Ignorieren/Ignore/Abbrechen/Cancel? ignore Modell: Linux-Device-Mapper (linear) (dm) Festplatte /dev/mapper/via_jehhchjje3: 1905GB Sektorgröße (logisch/physisch): 512B/512B Partitionstabelle: msdos Nummer Anfang EndeGröße Typ Dateisystem Flags 1 1024B 52,4GB 52,4GB primary ntfs 2 52,4GB 1867GB 1815GB extended 5 52,4GB 1867GB 1815GB logical ntfs Modell: Linux-Device-Mapper (linear) (dm) Festplatte /dev/mapper/via_jehhchjje1: 43,0GB Sektorgröße (logisch/physisch): 512B/512B Partitionstabelle: loop Nummer Anfang EndeGröße Dateisystem Flags 1 0,00B 43,0GB 43,0GB ntfs Modell: Linux-Device-Mapper (linear) (dm) Festplatte /dev/mapper/via_jehhchjje2: 52,4GB Sektorgröße (logisch/physisch): 512B/512B Partitionstabelle: loop Nummer Anfang EndeGröße Dateisystem Flags 1 0,00B 52,4GB 52,4GB ntfs Modell: Linux-Device-Mapper (linear) (dm) Festplatte /dev/mapper/via_jehhchjje5: 52,4GB Sektorgröße (logisch/physisch): 512B/512B Partitionstabelle: loop Nummer Anfang EndeGröße Dateisystem Flags 1 0,00B 52,4GB 52,4GB ntfs Modell: Linux-Device-Mapper (linear) (dm) Festplatte /dev/mapper/via_jehhchjje9: 2096MB Sektorgröße (logisch/physisch): 512B/512B Partitionstabelle: loop Nummer Anfang EndeGröße Dateisystem Flags 1 0,00B 2096MB 2096MB linux-swap(v1) Modell: Linux-Device-Mapper (linear) (dm) Festplatte /dev/mapper/via_jehhchjje7: 21,0GB Sektorgröße (logisch/physisch): 512B/512B Partitionstabelle: loop Nummer Anfang EndeGröße Dateisystem Flags 1 0,00B 21,0GB 21,0GB ext4 Modell: Linux-Device-Mapper (linear) (dm) Festplatte /dev/mapper/via_jehhchjje8: 14,7GB Sektorgröße (logisch/physisch): 512B/512B Partitionstabelle: loop Nummer Anfang EndeGröße Dateisystem Flags 1 0,00B 14,7GB 14,7GB ext4 Modell: Linux-Device-Mapper (striped) (dm) Festplatte /dev/mapper/via_jehhchjje: 2000GB Sektorgröße (logisch/physisch): 512B/512B Partitionstabelle: msdos Nummer Anfang EndeGröße Typ Dateisystem Flags 1 8225kB 43,0GB 43,0GB primary ntfsboot 2 43,0GB 95,4GB 52,4GB primary ntfs 3 95,4GB 2000GB 1905GB extended 5 95,4GB 148GB 52,4GB logical ntfs 6 148GB 1963GB 1815GB logical ntfs 7 1963GB 1984GB 21,0GB logical ext4RAID 8 1984GB 1998GB 14,7GB logical ext4RAID 9 1998GB 2000GB 2096MB logical linux-swap(v1) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1093918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1093918] Re: grub-probe auto-detection fails on raid
i don't think zeroing it would be good idea. via_jehhchjje3 is a logical partition basically holding 5,7,8 and 9 with gparted i can see this with parted it looks a little strange . nevertheless i think now that this logical partition via_jehhchjje3 is also the point where grub fails ... not able resolving it .. whatever like this . but as said with grub within ubuntu 11.10 THIS also is no problem THERE, but within grub of ubuntu 12.04 (and 12.10) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1093918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1093918] Re: grub-probe auto-detection fails on raid
you saw that you already got answer above related to your questions for: sudo dmsetup ls --tree and sudo grub-probe -t device (hd3) ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1093918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1093918] Re: grub-probe auto-detection fails on raid
maybe this also is helpful: made a diff of grub-probe -vvd /dev/dm-6 versus grub-probe -vvd /dev/mapper/via_jehhchjje7 at certain stage /dev/dm-6 just gets opened: grub-core/kern/disk.c:338: Closing `hd3'. grub-core/kern/disk.c:245: Opening `hd3,7'... grub-core/partmap/msdos.c:166: partition 0: flag 0x80, type 0x7, start 0x3ec1, len 0x50014e6 grub-core/partmap/msdos.c:166: partition 1: flag 0x0, type 0x7, start 0x50053a7, len 0x61a7966 grub-core/partmap/msdos.c:166: partition 2: flag 0x0, type 0x5, start 0xb1acd4a, len 0xddc60ab6 grub-core/partmap/msdos.c:166: partition 3: flag 0x0, type 0x0, start 0x0, len 0x0 grub-core/partmap/msdos.c:166: partition 0: flag 0x0, type 0x7, start 0xb1acd4c, len 0x61a7927 grub-core/partmap/msdos.c:166: partition 1: flag 0x0, type 0x5, start 0x11354673, len 0xd346918d grub-core/partmap/msdos.c:166: partition 2: flag 0x0, type 0x0, start 0xb1acd4a, len 0x0 grub-core/partmap/msdos.c:166: partition 3: flag 0x0, type 0x0, start 0xb1acd4a, len 0x0 grub-core/partmap/msdos.c:166: partition 0: flag 0x0, type 0x7, start 0x11356000, len 0xd3467800 grub-core/partmap/msdos.c:166: partition 1: flag 0x0, type 0x5, start 0xea9681bf, len 0x270d7b5 grub-core/partmap/msdos.c:166: partition 2: flag 0x0, type 0x0, start 0x11354673, len 0x0 grub-core/partmap/msdos.c:166: partition 3: flag 0x0, type 0x0, start 0x11354673, len 0x0 grub-core/partmap/msdos.c:166: partition 0: flag 0x0, type 0xfd, start 0xe47c08d5, len 0x270d776 grub-core/kern/fs.c:54: Detecting zfs... grub-core/kern/emu/hostdisk.c:507: dm /dev/mapper/via_jehhchjje1 starts at 16065 grub-core/kern/emu/hostdisk.c:507: dm /dev/mapper/via_jehhchjje2 starts at 83907495 grub-core/kern/emu/hostdisk.c:507: dm /dev/mapper/via_jehhchjje3 starts at 186305866 grub-core/kern/emu/hostdisk.c:507: dm /dev/mapper/via_jehhchjje5 starts at 2 grub-core/kern/emu/hostdisk.c:507: dm /dev/mapper/via_jehhchjje6 starts at 102404790 grub-core/kern/emu/hostdisk.c:507: dm /dev/mapper/via_jehhchjje7 starts at 3647028107 grub-core/kern/emu/hostdisk.c:507: dm /dev/mapper/via_jehhchjje8 starts at 3687977792 grub-core/kern/emu/hostdisk.c:507: dm /dev/mapper/via_jehhchjje9 starts at 3716649654 grub-core/kern/emu/hostdisk.c:722: opening the device `/dev/mapper/via_jehhchjje' in open_device() while /dev/mapper/via_jehhchjje7 gets in trouble trying to open extended partition: grub-core/kern/disk.c:338: Closing `hd3'. grub-core/kern/emu/hostdisk.c:1452: /dev/dm-6 is not DM-RAID grub-core/kern/emu/hostdisk.c:1452: /dev/dm-6 is not DM-RAID grub-core/kern/emu/hostdisk.c:1452: /dev/dm-6 is not DM-RAID grub-core/kern/emu/hostdisk.c:507: dm /dev/mapper/via_jehhchjje7 starts at 3647028107 grub-core/kern/disk.c:245: Opening `/dev/mapper/via_jehhchjje3'... grub-core/kern/emu/hostdisk.c:722: opening the device `/dev/mapper/via_jehhchjje3' in open_device() if i do sudo dmsetup rm via_hehhchjje3 i will destroy the raid or the involved partitions? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1093918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1093918] Re: grub only recognizes nvidia fakeraid, not via, pdc, or isw
... sorry ... how has device.map to be look like? i tried hours and hours already with this without any effect. . further: a) you did not explain why grub-probe instists to process partition 3 instead of 7 when doing (as you was able to see in outputs above, which you deleted !! ): sudo grub-probe -vd /dev/mapper/via_jehhchjje7 and b) you did not explain why this works ALSO with via and is still working as in my current system i am writing this ... until ubuntu 11.10 c) how can you know based on my bug report that it works with nvidia ? --- but you changed MY title summary of bug report !! i am NOT amused -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1093918 Title: grub only recognizes nvidia fakeraid, not via, pdc, or isw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1093918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1093918] Re: grub only recognizes nvidia fakeraid, not via, pdc, or isw grub-probe auto-detection fails on raid
** Summary changed: - grub only recognizes nvidia fakeraid, not via, pdc, or isw + grub only recognizes nvidia fakeraid, not via, pdc, or isw grub-probe auto-detection fails on raid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1093918 Title: grub only recognizes nvidia fakeraid, not via, pdc, or isw grub- probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1093918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1093918] [NEW] grub-probe auto-detection fails on raid
Public bug reported: grub-probe auto-detection fails on raid, which can be seen f.e. on update-grub on separate hd in system. error messages: grub-probe: Fehler: cannot find a GRUB drive for /dev/mapper/via_jehhchjje7. Check your device.map. grub-probe: Fehler: cannot find a GRUB drive for /dev/mapper/via_jehhchjje8. Check your device.map. installation of grub in MBR of raid not possible. It was no problem until ubuntu 11.10, which still is in use on raid to boot from (ubuntu on raid /dev/mapper/via_jehhchjje7 ext4), because upgrade to 12.04 is not possible. There are really many users. also on servers effected, when you study the web via search engine interesting thing is: josef@josef-maxtor-quad:~$ ls -al /dev/mapper insgesamt 0 drwxr-xr-x 2 root root 240 Dez 27 2012 . drwxr-xr-x 17 root root4840 Dez 27 00:38 .. crw--- 1 root root 10, 236 Dez 27 00:33 control lrwxrwxrwx 1 root root 7 Dez 27 00:33 via_jehhchjje - ../dm-0 lrwxrwxrwx 1 root root 7 Dez 27 00:33 via_jehhchjje1 - ../dm-1 lrwxrwxrwx 1 root root 7 Dez 27 00:33 via_jehhchjje2 - ../dm-2 lrwxrwxrwx 1 root root 7 Dez 27 00:33 via_jehhchjje3 - ../dm-3 lrwxrwxrwx 1 root root 7 Dez 27 00:33 via_jehhchjje5 - ../dm-4 lrwxrwxrwx 1 root root 7 Dez 27 00:33 via_jehhchjje6 - ../dm-5 lrwxrwxrwx 1 root root 7 Dez 27 00:33 via_jehhchjje7 - ../dm-6 ... here is an ubuntu on raid lrwxrwxrwx 1 root root 7 Dez 27 00:33 via_jehhchjje8 - ../dm-7 lrwxrwxrwx 1 root root 7 Dez 27 00:33 via_jehhchjje9 - ../dm-8 there is a link -via_jehhchjje7 - ../dm-6 while josef@josef-maxtor-quad:~$ sudo grub-probe -vd /dev/mapper/via_jehhchjje7 [sudo] password for josef: grub-probe: Info: Scanning for dmraid_nv RAID devices on disk hd2. grub-probe: Info: the size of hd2 is 1953525168. grub-probe: Info: the size of hd2 is 1953525168. grub-probe: Info: Scanning for dmraid_nv RAID devices on disk hd3. grub-probe: Info: the size of hd3 is 3907050240. grub-probe: Info: the size of hd3 is 3907050240. grub-probe: Info: scanning hd2 for LVM. grub-probe: Info: the size of hd2 is 1953525168. grub-probe: Info: no LVM signature found. grub-probe: Info: the size of hd2 is 1953525168. grub-probe: Info: scanning hd3 for LVM. grub-probe: Info: the size of hd3 is 3907050240. grub-probe: Info: no LVM signature found. grub-probe: Info: the size of hd3 is 3907050240. grub-probe: Info: Scanning for mdraid09 RAID devices on disk hd2. grub-probe: Info: the size of hd2 is 1953525168. grub-probe: Info: the size of hd2 is 1953525168. grub-probe: Info: Scanning for mdraid09 RAID devices on disk hd3. grub-probe: Info: the size of hd3 is 3907050240. grub-probe: Info: the size of hd3 is 3907050240. grub-probe: Info: Scanning for mdraid1x RAID devices on disk hd2. grub-probe: Info: the size of hd2 is 1953525168. grub-probe: Info: the size of hd2 is 1953525168. grub-probe: Info: Scanning for mdraid1x RAID devices on disk hd3. grub-probe: Info: the size of hd3 is 3907050240. grub-probe: Info: the size of hd3 is 3907050240. grub-probe: Info: Scanning for mdraid09 RAID devices on disk hd2. grub-probe: Info: the size of hd2 is 1953525168. grub-probe: Info: the size of hd2 is 1953525168. grub-probe: Info: Scanning for mdraid09 RAID devices on disk hd2,msdos6. grub-probe: Info: the size of hd2 is 1953525168. grub-probe: Info: Scanning for mdraid09 RAID devices on disk hd2,msdos5. grub-probe: Info: the size of hd2 is 1953525168. grub-probe: Info: Scanning for mdraid09 RAID devices on disk hd2,msdos3. grub-probe: Info: the size of hd2 is 1953525168. grub-probe: Info: Scanning for mdraid09 RAID devices on disk hd2,msdos2. grub-probe: Info: the size of hd2 is 1953525168. grub-probe: Info: Scanning for mdraid09 RAID devices on disk hd2,msdos1. grub-probe: Info: the size of hd2 is 1953525168. grub-probe: Info: Scanning for mdraid09 RAID devices on disk hd3. grub-probe: Info: the size of hd3 is 3907050240. grub-probe: Info: the size of hd3 is 3907050240. grub-probe: Info: Scanning for mdraid09 RAID devices on disk hd3,msdos9. grub-probe: Info: the size of hd3 is 3907050240. grub-probe: Info: Scanning for mdraid09 RAID devices on disk hd3,msdos8. grub-probe: Info: the size of hd3 is 3907050240. grub-probe: Info: Scanning for mdraid09 RAID devices on disk hd3,msdos7. grub-probe: Info: the size of hd3 is 3907050240. grub-probe: Info: Scanning for mdraid09 RAID devices on disk hd3,msdos6. grub-probe: Info: the size of hd3 is 3907050240. grub-probe: Info: Scanning for mdraid09 RAID devices on disk hd3,msdos5. grub-probe: Info: the size of hd3 is 3907050240. grub-probe: Info: Scanning for mdraid09 RAID devices on disk hd3,msdos2. grub-probe: Info: the size of hd3 is 3907050240. grub-probe: Info: Scanning for mdraid09 RAID devices on disk hd3,msdos1. grub-probe: Info: the size of hd3 is 3907050240. grub-probe: Info: Scanning for mdraid1x RAID devices on disk hd2. grub-probe: Info: the size of hd2 is
Re: [Bug 663670] Re: empathy doesn't connect to msn - blocked connection
As i can not find initial correct problem description causing the problems of connection for msn AND icq i make copy here: (the same problems i dealed with when updating a machine from 9.04 to 9.10 and to 10.04 LTS afterwards) here were the workarounds to solve problems network error at connection try: * In a terminal, run the following command: mc-tool update haze/icq/_3your uin0 bool:use-ssl=false - The extra '3' and '0' are deliberate! - For instance, if your ICQ username is '12345', run: mc-tool update haze/icq/_3123450 bool:use-ssl=false update on 28th feb 2011: it seems that update and solution not to have way found to ubuntu repositoryy. i made update from 9.04 to 9.10 and then to 10.04 LTS facing same problems like in the past LONG TIME AGO !!! neither the file is updated like described: /usr/lib/pymodules/python2.6/papyon/service/description/SingleSignOn/RequestMultipleSecurityTokens.py nor a solution for the ssl problem for icq was done againg both workaround fixed connetion problems who takes care that solutions also get in repository also for update way? Am Freitag, den 11.03.2011, 10:11 + schrieb Omer Akram: the issue was in papyon which is fixed in all supported ubuntu versions except for 9.10 because no one tested the proposed version for a few months. ** Changed in: telepathy-butterfly (Ubuntu) Status: Incomplete = Invalid ** Changed in: telepathy-butterfly (Ubuntu Lucid) Status: New = Invalid ** Changed in: telepathy-butterfly (Ubuntu Maverick) Status: New = Invalid ** Changed in: telepathy-butterfly (Ubuntu Karmic) Status: New = Invalid -- You received this bug notification because you are a direct subscriber of the bug. https://bugs.launchpad.net/bugs/663670 Title: empathy doesn't connect to msn - blocked connection Status in telepathy-butterfly: Fix Released Status in “papyon” package in Ubuntu: Fix Released Status in “telepathy-butterfly” package in Ubuntu: Invalid Status in “papyon” source package in Lucid: Fix Released Status in “telepathy-butterfly” source package in Lucid: Invalid Status in “papyon” source package in Maverick: Fix Released Status in “telepathy-butterfly” source package in Maverick: Invalid Status in “papyon” source package in Karmic: Won't Fix Status in “telepathy-butterfly” source package in Karmic: Invalid Bug description: Binary package hint: empathy I'm trying to find a bug that is related to this one, but none of the options I found matches. When opening Empathy, and trying to connect to my MSN accounts (I have two), Empathy keeps trying to connect, but nothing happens. There is no error message (so this is not the classic Network error bug that is solved by killing telepathy-butterfly), but the connection is not finalized. Checking the debug window, these are the last messages for butterfly: POST /abservice/abservice.asmx HTTP/1.0 Content-Length: 1519 Proxy-Connection: Keep-Alive SOAPAction: http://www.msn.com/webservices/AddressBook/ABFindAll Host: contacts.msn.com:80 Accept: text/* User-Agent: gnet/0.1 (Linux i686) Connection: Keep-Alive Cache-Control: no-cache Content-Type: text/xml; charset=utf-8 Accept-Encoding: gzip ?xml version='1.0' encoding='utf-8'?soap:Envelope xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/;soap:HeaderABApplicationHeader xmlns=http://www.msn.com/webservices/AddressBook;ApplicationId xmlns=http://www.msn.com/webservices/AddressBook;996CDE1E-AA53-4477-B943-2BE802EA6166/ApplicationIdIsMigration xmlns=http://www.msn.com/webservices/AddressBook;false/IsMigrationPartnerScenario xmlns=http://www.msn.com/webservices/AddressBook;Initial/PartnerScenario/ABApplicationHeaderABAuthHeader xmlns=http://www.msn.com/webservices/AddressBook;ManagedGroupRequest xmlns=http://www.msn.com/webservices/AddressBook;false/ManagedGroupRequestTicketToken xmlns=http://www.msn.com/webservices/AddressBook;t=9xCdFY6ARAad22feO5Sqed4j13RAYGkqdRKTAVZ0QoqR!uqnD2AM8UrgP2wuGwlw5PkavEKGXLq9SS!gomhwcNXVts6RgM!X3aJqqFmCKDWtdwoKwkUA*ZJ4C5xKw!zIx7sa0!L7BY!eY$amp;p=9xjATSClgG2kOi0KVdQNsQFsqqGzwFIWh3rui4kRMCcnftlp8Ctuh1SRVwIxem1A4x7mqjItHZhnuEijWP*NGwmny2ZUicbdSbLcIXyIuu8wBR2xT8!1JihxBU3P1C*jPM373hiDbuGagvBnhVgzIKrsPWYFA*YOLdUDqWNDk9Xi9uW9u8WQPGtJledRTpiUBrEjxr9r62hE*eOlz5*m3Nnw$$/TicketToken/ABAuthHeader/soap:Headersoap:BodyABFindAll xmlns=http://www.msn.com/webservices/AddressBook;abId----/abIdabViewFull/abViewdeltasOnlyfalse/deltasOnlylastChange0001-01-01T00:00:00.000-08:00/lastChange/ABFindAll/soap:Body/soap:Envelope POST /abservice/SharingService.asmx HTTP/1.0 Content-Length: 1606 Proxy-Connection: Keep-Alive SOAPAction: http://www.msn.com/webservices/AddressBook/FindMembership Host:
Re: [Bug 663670] Re: empathy doesn't connect to msn - blocked connection
I am running 10.4 LTS natty is 10.10 ? i have several installations and can upgrade one and check as soon as i have time Am Donnerstag, den 10.03.2011, 13:22 + schrieb Sebastien Bacher: is that still an issue in natty? ** Changed in: telepathy-butterfly (Ubuntu) Importance: Undecided = Low ** Changed in: telepathy-butterfly (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a direct subscriber of the bug. https://bugs.launchpad.net/bugs/663670 Title: empathy doesn't connect to msn - blocked connection Status in telepathy-butterfly: Fix Released Status in “papyon” package in Ubuntu: Fix Released Status in “telepathy-butterfly” package in Ubuntu: Incomplete Status in “papyon” source package in Lucid: Fix Released Status in “telepathy-butterfly” source package in Lucid: New Status in “papyon” source package in Maverick: Fix Released Status in “telepathy-butterfly” source package in Maverick: New Status in “papyon” source package in Karmic: Won't Fix Status in “telepathy-butterfly” source package in Karmic: New Bug description: Binary package hint: empathy I'm trying to find a bug that is related to this one, but none of the options I found matches. When opening Empathy, and trying to connect to my MSN accounts (I have two), Empathy keeps trying to connect, but nothing happens. There is no error message (so this is not the classic Network error bug that is solved by killing telepathy-butterfly), but the connection is not finalized. Checking the debug window, these are the last messages for butterfly: POST /abservice/abservice.asmx HTTP/1.0 Content-Length: 1519 Proxy-Connection: Keep-Alive SOAPAction: http://www.msn.com/webservices/AddressBook/ABFindAll Host: contacts.msn.com:80 Accept: text/* User-Agent: gnet/0.1 (Linux i686) Connection: Keep-Alive Cache-Control: no-cache Content-Type: text/xml; charset=utf-8 Accept-Encoding: gzip ?xml version='1.0' encoding='utf-8'?soap:Envelope xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/;soap:HeaderABApplicationHeader xmlns=http://www.msn.com/webservices/AddressBook;ApplicationId xmlns=http://www.msn.com/webservices/AddressBook;996CDE1E-AA53-4477-B943-2BE802EA6166/ApplicationIdIsMigration xmlns=http://www.msn.com/webservices/AddressBook;false/IsMigrationPartnerScenario xmlns=http://www.msn.com/webservices/AddressBook;Initial/PartnerScenario/ABApplicationHeaderABAuthHeader xmlns=http://www.msn.com/webservices/AddressBook;ManagedGroupRequest xmlns=http://www.msn.com/webservices/AddressBook;false/ManagedGroupRequestTicketToken xmlns=http://www.msn.com/webservices/AddressBook;t=9xCdFY6ARAad22feO5Sqed4j13RAYGkqdRKTAVZ0QoqR!uqnD2AM8UrgP2wuGwlw5PkavEKGXLq9SS!gomhwcNXVts6RgM!X3aJqqFmCKDWtdwoKwkUA*ZJ4C5xKw!zIx7sa0!L7BY!eY$amp;p=9xjATSClgG2kOi0KVdQNsQFsqqGzwFIWh3rui4kRMCcnftlp8Ctuh1SRVwIxem1A4x7mqjItHZhnuEijWP*NGwmny2ZUicbdSbLcIXyIuu8wBR2xT8!1JihxBU3P1C*jPM373hiDbuGagvBnhVgzIKrsPWYFA*YOLdUDqWNDk9Xi9uW9u8WQPGtJledRTpiUBrEjxr9r62hE*eOlz5*m3Nnw$$/TicketToken/ABAuthHeader/soap:Headersoap:BodyABFindAll xmlns=http://www.msn.com/webservices/AddressBook;abId----/abIdabViewFull/abViewdeltasOnlyfalse/deltasOnlylastChange0001-01-01T00:00:00.000-08:00/lastChange/ABFindAll/soap:Body/soap:Envelope POST /abservice/SharingService.asmx HTTP/1.0 Content-Length: 1606 Proxy-Connection: Keep-Alive SOAPAction: http://www.msn.com/webservices/AddressBook/FindMembership Host: contacts.msn.com:80 Accept: text/* User-Agent: gnet/0.1 (Linux i686) Connection: Keep-Alive Cache-Control: no-cache Content-Type: text/xml; charset=utf-8 Accept-Encoding: gzip ?xml version='1.0' encoding='utf-8'?soap:Envelope xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/;soap:HeaderABApplicationHeader xmlns=http://www.msn.com/webservices/AddressBook;ApplicationId xmlns=http://www.msn.com/webservices/AddressBook;996CDE1E- AA53-4477-B943-2BE802EA6166/ApplicationIdIsMigration xmlns=http://www.msn.com/webservices/AddressBook;false/IsMigrationPartnerScenario xmlns=http://www.msn.com/webservices/AddressBook;Initial/PartnerScenario/ABApplicationHeaderABAuthHeader xmlns=http://www.msn.com/webservices/AddressBook;ManagedGroupRequest xmlns=http://www.msn.com/webservices/AddressBook;false/ManagedGroupRequestTicketToken
Re: [Bug 663670] Re: empathy doesn't connect to msn - blocked connection
On one of my machines running 9.04 i did upgrade to 9.10 and then to 10.04 and faced the same problems like in the past on other machines. I did my discribed manual fixes then for MSN and ICQ and afterwards both chats were fine again. So maybe it just was not forseen to fix it in the upgrade process. But this is very important for my understanding. A lot of people still need or want to upgrade form older versions to 10.04 L T S !!! long time supported should be fixed in any case is my oppinion. kind regards Am Donnerstag, den 10.03.2011, 13:56 + schrieb Coalwater: @josef 10.10 is maverick, natty is 11.04 -- You received this bug notification because you are a direct subscriber of the bug. https://bugs.launchpad.net/bugs/663670 Title: empathy doesn't connect to msn - blocked connection Status in telepathy-butterfly: Fix Released Status in “papyon” package in Ubuntu: Fix Released Status in “telepathy-butterfly” package in Ubuntu: Incomplete Status in “papyon” source package in Lucid: Fix Released Status in “telepathy-butterfly” source package in Lucid: New Status in “papyon” source package in Maverick: Fix Released Status in “telepathy-butterfly” source package in Maverick: New Status in “papyon” source package in Karmic: Won't Fix Status in “telepathy-butterfly” source package in Karmic: New Bug description: Binary package hint: empathy I'm trying to find a bug that is related to this one, but none of the options I found matches. When opening Empathy, and trying to connect to my MSN accounts (I have two), Empathy keeps trying to connect, but nothing happens. There is no error message (so this is not the classic Network error bug that is solved by killing telepathy-butterfly), but the connection is not finalized. Checking the debug window, these are the last messages for butterfly: POST /abservice/abservice.asmx HTTP/1.0 Content-Length: 1519 Proxy-Connection: Keep-Alive SOAPAction: http://www.msn.com/webservices/AddressBook/ABFindAll Host: contacts.msn.com:80 Accept: text/* User-Agent: gnet/0.1 (Linux i686) Connection: Keep-Alive Cache-Control: no-cache Content-Type: text/xml; charset=utf-8 Accept-Encoding: gzip ?xml version='1.0' encoding='utf-8'?soap:Envelope xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/;soap:HeaderABApplicationHeader xmlns=http://www.msn.com/webservices/AddressBook;ApplicationId xmlns=http://www.msn.com/webservices/AddressBook;996CDE1E-AA53-4477-B943-2BE802EA6166/ApplicationIdIsMigration xmlns=http://www.msn.com/webservices/AddressBook;false/IsMigrationPartnerScenario xmlns=http://www.msn.com/webservices/AddressBook;Initial/PartnerScenario/ABApplicationHeaderABAuthHeader xmlns=http://www.msn.com/webservices/AddressBook;ManagedGroupRequest xmlns=http://www.msn.com/webservices/AddressBook;false/ManagedGroupRequestTicketToken xmlns=http://www.msn.com/webservices/AddressBook;t=9xCdFY6ARAad22feO5Sqed4j13RAYGkqdRKTAVZ0QoqR!uqnD2AM8UrgP2wuGwlw5PkavEKGXLq9SS!gomhwcNXVts6RgM!X3aJqqFmCKDWtdwoKwkUA*ZJ4C5xKw!zIx7sa0!L7BY!eY$amp;p=9xjATSClgG2kOi0KVdQNsQFsqqGzwFIWh3rui4kRMCcnftlp8Ctuh1SRVwIxem1A4x7mqjItHZhnuEijWP*NGwmny2ZUicbdSbLcIXyIuu8wBR2xT8!1JihxBU3P1C*jPM373hiDbuGagvBnhVgzIKrsPWYFA*YOLdUDqWNDk9Xi9uW9u8WQPGtJledRTpiUBrEjxr9r62hE*eOlz5*m3Nnw$$/TicketToken/ABAuthHeader/soap:Headersoap:BodyABFindAll xmlns=http://www.msn.com/webservices/AddressBook;abId----/abIdabViewFull/abViewdeltasOnlyfalse/deltasOnlylastChange0001-01-01T00:00:00.000-08:00/lastChange/ABFindAll/soap:Body/soap:Envelope POST /abservice/SharingService.asmx HTTP/1.0 Content-Length: 1606 Proxy-Connection: Keep-Alive SOAPAction: http://www.msn.com/webservices/AddressBook/FindMembership Host: contacts.msn.com:80 Accept: text/* User-Agent: gnet/0.1 (Linux i686) Connection: Keep-Alive Cache-Control: no-cache Content-Type: text/xml; charset=utf-8 Accept-Encoding: gzip ?xml version='1.0' encoding='utf-8'?soap:Envelope xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/;soap:HeaderABApplicationHeader xmlns=http://www.msn.com/webservices/AddressBook;ApplicationId xmlns=http://www.msn.com/webservices/AddressBook;996CDE1E- AA53-4477-B943-2BE802EA6166/ApplicationIdIsMigration xmlns=http://www.msn.com/webservices/AddressBook;false/IsMigrationPartnerScenario xmlns=http://www.msn.com/webservices/AddressBook;Initial/PartnerScenario/ABApplicationHeaderABAuthHeader xmlns=http://www.msn.com/webservices/AddressBook;ManagedGroupRequest xmlns=http://www.msn.com/webservices/AddressBook;false/ManagedGroupRequestTicketToken
[Bug 663670] Re: empathy doesn't connect to msn - blocked connection
Ubuntu 10.04 change mentioned in #31 worked fine for me ... did some automatic offered updates in last weeks (f.e kernel 2.6.32-27.49) - did not realize immediatly, that manual change was overwritten by updates :( ... why? i thought this change is part of new updates? did manual change again today like mentioned in #31, and again it works now. what's up with updates in lucid lynx? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/663670 Title: empathy doesn't connect to msn - blocked connection -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 676060] Re: Cannot connect to ICQ
*** This bug is a duplicate of bug 675903 *** https://bugs.launchpad.net/bugs/675903 i am just user in this case, but this is not duplicate to 675903, because this feed is related to Empathy whereas 675903 is related to pidgin. The point is, it is not solved in Empathy also in Lucid Lynx, if downloading latest version 2.30.3 I can definitly confirm, that described switch off of SSL works also on my machine(s) with 32 and also 64 bit version of Lynx. So i can not confirm to daqron, that it does not work on 64 bit system ! It definitly works also there. Therefore please deploy an update for all the other poor :) users of Lucid Lynx LONG TIME Support. Thank you for all !!:) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/676060 Title: Cannot connect to ICQ -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
