You're welcome, Dmitrijs.
Now that this system is finally behaving itself (for the first time in
the better part of a year!) I can now look at this properly functioning
configuration and compare it with the previously broken one. It is
becoming more clear what happened.
(Note: all of the follo
Please ignore this bug report.
I now believe this problem was caused by a configuration error in my
RAID setup. In particular, two different arrays had the same 'name' (I
think this is the 'name' recorded in the array superblocks -- IMHO,
'name' has become an over-conflated term in the context
@Atheg: (continuing previous comment)
I just had a look at the Tcl docs. I learned about the info patchlevel
command. This is what it does on my system:
me@precise:~$ tclsh
% info patchlevel
8.5.11
% exit
me@precise:~$ tclsh8.4
% info patchlevel
8.4.19
% exit
me@precise:~$ tclsh8.5
% info patc
@Atheg:
(Note that I am totally guessing about this, and all of the following
may be less than helpful)
AFAIK, installing tcl8.4 doesn't roll back anything. I just checked my
system, and I now have both 8.4 and 8.5 installed where I only had 8.5
before. I don't know if this presents any problem
@Brian, Dmitrijs:
Thanks.
I have filed Bug # 1036366 to report the symptoms not resolved by this
recent fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/942106
Title:
software raid doesn't assem
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1036366
Title:
software RAID arrays fail to start on boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mdadm/
Public bug reported:
Some software RAID arrays fail to start on boot. Exactly two of my
arrays (but not always the same two!) do not start, on every single
boot, and I have done 24 boots since I started taking detailed notes.
Have been running Ubuntu 12.04 with latest updates. Two days ago I
se
@Dmitrijs:
sudo apport mdadm does nothing. I know that apport is installed and the
service is running. Am I doing this wrong?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/942106
Title:
software
@Dmitrijs:
I must agree with your assessment. I cannot really tell which (of many)
existing bug reports are most relevant to my system, so I've been
chiming in on a bunch of them, just in case they provide clues helpful
to others :-)
This latest mdadm update does not have any negative impact on
This does NOT fix this issue for me.
My system still boots up with some RAID arrays not running. Every
single time.
This system has six SATA drives on two controllers. It contains seven
RAID arrays, a mix of RAID 1, RAID 10, and RAID 6; all are listed in
fstab. Some use 0.90.0 metadata and so
On my system, tcl8.5 is installed, but tcl8.4 is not. So:
sudo apt-get install tcl8.4
This resulted in:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
tclreadline
The following NEW packages will be installed:
tcl8.4
0 u
Following this installation failure, an error message appears at the end
of every upgrade of any software package. So affected users see error
messages almost every day, even if they never even try to run gpsmanshp.
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
*** This bug is a duplicate of bug 995445 ***
https://bugs.launchpad.net/bugs/995445
** This bug has been marked a duplicate of bug 995445
package gpsmanshp 1.2.1-1 failed to install/upgrade: subprocess installed
post-installation script returned error exit status 127
--
You received thi
*** This bug is a duplicate of bug 995445 ***
https://bugs.launchpad.net/bugs/995445
** This bug has been marked a duplicate of bug 995445
package gpsmanshp 1.2.1-1 failed to install/upgrade: subprocess installed
post-installation script returned error exit status 127
--
You received thi
Precise is using a 3.2.0 kernel. There is a known MD bug that affects
some 3.2.x and 3.3.x kernels, that seems like it might be relevant to
this problem. See:
http://www.spinics.net/lists/raid/msg39004.html
and the rest of that thread. Note the mention of possible racing in
scripts.
Unfortuna
Since my last comment, an updated kernel arrived via Update Manager.
Its changelog included the following:
* md: fix possible corruption of array metadata on shutdown.
- LP: #992038
This seems possibly relevant. I updated, and have now rebooted several
times. The RAID degradation is stil
I have now installed Precise on my system. (I had intended to install
as a multiboot, along with the existing Oneiric, but apparently the
alternate installer could not recognize my existing /boot RAID1
partition, so now I can't boot Oneiric. But that's another story...)
Note that the title of th
(Ooops, apparently hit the wrong key... continuing the previous
comment)
...shut down with Alt-SysRq REISUB. This has no effect whatsoever. The
screen doesn't change; the drive activity light does nothing.
Finally, after stewing for a while longer, I hold down the power switch
until I hear a
I am having similar problems. I am running Oneiric. I am NOT using
LUKS or LVM.
Symptoms vary in severity a lot. Sometimes it simply drops a spare, and
it's listed in palimpsest as "not attached". One click of the button
and it's reattached, and shown as "spare".
But then sometimes it gets re
This is affecting me as well. It started when I upgraded from 11.04 to
11.10.
I am identifying machines with IPs, not DNS. I set it up as per this
tutorial:
https://mostlylinux.wordpress.com/network/nfshowto/
These instructions work fine for 10.04, 10.10, and 11.04. (However, the
commands it
I just tested this on Maverick final release (AMD64 alternate
installer). Same result.
--
error while creating logical partition
https://bugs.launchpad.net/bugs/666038
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
--
error while creating logical partition
https://bugs.launchpad.net/bugs/666038
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-
Public bug reported:
Binary package hint: gnome-disk-utility
Running Maverick release candidate, with all the updates applied since
final release (which happened two weeks ago).
Ran palimpsest to add partitions to an empty SATA drive, in preparation
for from-scratch installation of Maverick fina
This bit me too. Two 500GB drives, RAID1, using 10.04.1 alternate 386
installer.
Reading through all these comments, and those on similar (possibly
related) bugs, it seems like this is caused by an arithmetic error in
some code that figures out where things ought to be on the disk.
Suddenly I am
I looked at the amarok_addaspodcast.desktop file and compared it with a
number of other amarok*.desktop files in the same folder. This one
differed in that it had no Exec line in it. I added one after the Icon
line:
Exec=amarok -a %u
I have no idea if this is actually the correct line to use, a
25 matches
Mail list logo
