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.
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)
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
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
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
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.
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.
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
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:
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
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
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
*** 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,
.
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
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
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
** 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
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.
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.
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
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
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
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)
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
... 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
** 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
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:
/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
/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
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
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
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:
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
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 :
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
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
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)
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.
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
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
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:
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:
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
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.
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
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
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
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
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:
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
*** 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
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
52 matches
Mail list logo
