It looks like zeroing the superblock on /dev/sdb with mdadm --zero-
superblock /dev/sdb fixed the issue with the array not assembling on
boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1164008
Tit
I'm digging into this some more and it seems that mdadm in Ubuntu 12.04
is detecting an old unused superblock on /dev/sdb that mdadm in Ubuntu
10.04 ignored.
$ mdadm --examine --scan --verbose
ARRAY /dev/md1 level=raid1 num-devices=2
UUID=5fb6928e:89f09cde:d0aebb6f:e3c24c31
spares=1 devices=
Public bug reported:
I just upgraded a working 10.04 LTS server to 12.04 LTS. The server has
two non-boot drives in a software RAID1 configuration. This array worked
fine in 10.04 LTS.
When the machine boots I should get one active array, /dev/md0
consisting of /dev/sdb1 and /dev/sdc1. Instead, I
Issue is also present when I compile 1.4.31 and 1.4.30 from source on
the affected box.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1015730
Title:
lighttpd crashes when accessed over ssl from my m
Public bug reported:
I don't know what's going on here. Fully patched system (as of June 20,
2012)
$ lsb_release -rd
Description:Ubuntu 12.04 LTS
Release:12.04
$ apt-cache policy lighttpd
lighttpd:
Installed: 1.4.28-2ubuntu4
Candidate: 1.4.28-2ubuntu4
Version table:
*** 1.4.28
Any chance we can see a fix backported to lucid?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/627789
Title:
SNI support broken in lighttpd-1.4.26
To manage notifications about this bug go to:
http
Issue no longer occurs on my Oneiric machine. I ran an upgrade today and
now everything seems fine.
$ uname -a
Linux nas 3.0.0-12-generic-pae #19-Ubuntu SMP Fri Sep 23 23:10:56 UTC
2011 i686 i686 i386 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Tags added: oneiric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/776908
Title:
mdadm arrays fail to mount
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source
Still exists in Oneiric (11.10) beta.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/776908
Title:
mdadm arrays fail to mount
To manage notifications about this bug go to:
https://bugs.launchpad.net
One of the drives in the RAID croaked yesterday. After it did I fscked
the filesystem for the hell of it. The error was fixed this time. I
think this issue may have been hardware-related. Would you agree?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
This is kind of a tricky situation. The corrupted filesystem contains
complete backups of my workplace webserver and its MySQL databases,
among other things. There's no way I could give someone from outside
access to that data. Is there really no way for me to give you what you
need without includi
** Attachment added: "dumpe2fs output"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/796717/+attachment/2167504/+files/dumpe2fs-output.txt.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
** Attachment added: "e2fsck output"
https://bugs.launchpad.net/bugs/796717/+attachment/2167503/+files/e2fsck-output.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/796717
Title:
e2fsck not fi
Public bug reported:
Binary package hint: e2fsprogs
I've got a software RAID10 in Ubuntu 10.04 that started giving me fs
errors Saturday evening. After running e2fsck multiple times and fixing
many errors, it seems there are three left that it is not fixing even
after multiple runs.
Description:
Problem is happening for me with a RAID5 array. I am mounting the array
by UUID in /etc/fstab. I get the error that the drive is not ready at
boot and I am given the option to wait, skip, or manually recover. If I
manually recover I can simply type mount -a and the array mounts
correctly. I then lo
A recent kernel upgrade fixed my issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/659296
Title:
[Maverick] No display on boot using 2.6.35-22 kernel.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
I can confirm the system is booting properly besides the whole lack of a
display thing. I can access it via ssh just fine.
--
[Maverick] No display on boot using 2.6.35-22 kernel.
https://bugs.launchpad.net/bugs/659296
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Still happening in 2.6.35-22.35 that shipped recently.
--
[Maverick] No display on boot using 2.6.35-22 kernel.
https://bugs.launchpad.net/bugs/659296
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bu
I just installed a few of the mainline kernel builds to test. Using
mainline 2.6.35.4 displays the same issue, however 2.6.35.7 works fine.
--
[Maverick] No display on boot using 2.6.35-22 kernel.
https://bugs.launchpad.net/bugs/659296
You received this bug notification because you are a member o
** Attachment added: "AcpiTables.txt"
https://bugs.launchpad.net/bugs/659296/+attachment/1688413/+files/AcpiTables.txt
** Attachment added: "AlsaDevices.txt"
https://bugs.launchpad.net/bugs/659296/+attachment/1688414/+files/AlsaDevices.txt
** Attachment added: "BootDmesg.txt"
https:/
Public bug reported:
After upgrading to Maverick, nothing appears on my display. Judging by
the hard disk activity, the system appears to be booting normally--I
just can't see anything. I have to use an old kernel (2.6.32-25) in
order for my display to work.
ProblemType: Bug
DistroRelease: Ubuntu
21 matches
Mail list logo
