Is this fix available in the 16.04 LTS image used by MaaS? Commissioning
fails for me and I'm wondering if this is the reason.
"Can not apply stage config, no datasource found! Likely bad things to
come!"
"Failed to start Apply the settings specified in cloud-config"
--
You received this bug no
Might be the wrong place to ask, but:
I'm using Ubuntu MaaS, will this fix be available in the 16.04 LTS
images? Right now my nodes fail to commission which I believe comes from
this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Not sure if more information is needed at this point, but this bug also affects
me. Setup:
Jaunty 64bit
kvm 1:84+dfsg-0ubuntu12.1~ppa6
no acpi or apic
1 or 2 cpus, doesn't matter
>From what Dustin says ACPI + XP has been fixed? Am I understanding that
correctly?
--
KVM eats 100% CPU, Host Hardy
Same issue, Ubuntu 9.04 i386, 2.6.28-11-generic #42-Ubuntu SMP Fri Apr
17 01:57:59 UTC 2009 i686 GNU/Linux. Since the mac 2009 hardware is
virtually identical for all configurations except for ram and harddrive
it likely happens all configurations.
--
nvidia-based Mac Mini (Macmini3,1) won't rebo
I do not have this setup anymore (9+ months, needed it operational), but
there have been other people reporting the same problem more recently.
Hopefully one of them will be able to confirm.
--
mdadm with Raid5 stuck in uninterruptable sleep
https://bugs.launchpad.net/bugs/208551
You received thi
I had to swap to Debian as this bug made the server useless. I haven't
had any deadlocks here yet, but it might still apply for all I know.
Or is Debian using different code? I'm running testing, on 2.6.25-2
I am happy someone eventually identified the cause though.
Christian
Colin King wrote:
Not sure if it is related, might be. I honestly gave up on it after
concluding that the problem was too erratic and virtually impossible for
me to debug. If I remember correctly I also got messages about the SATA
link going down, then reset and back up.
--
mdadm, Raid5 and XFS stuck in uninterrup
Exactly the same happens to me. Asus X38 Maximus formula, ICH9R. If the
jmicron controller is enabled I get the same errors as you do.
Ironically I can use the IDE part of the jmicron controller, but it even
prevents other SATA controllers (like the onboard AHCI controller)
working.
--
Jmicron AH
Was copying from a file set up with losetup + cryptsetup on a raid5
array (the one above) to a raid6 array, all of which with XFS. During
this copy I ran mdadm --examine --scan, and the raid5 crashed (the one I
was reading from), giving me input/output errors. md device is fine on
the other hand, a
mdadm -D returned after a couple of minutes, at which point it started
writing again. During the period it was running nothing was written.
--
mdadm, Raid5 and XFS stuck in uninterruptable sleep
https://bugs.launchpad.net/bugs/208551
You received this bug notification because you are a member of
Sigh. Spoke too soon. Ran mdadm -D while it was beeing copied to, hanged
again. 2TB transferred. Guess it's directly related to the number of
processes that access to the device. Won't be able to restart it until
tomorrow, but I can try any suggestions on the hanged system.
--
mdadm, Raid5 and XF
Public bug reported:
Description:Ubuntu hardy (development branch)
Release:8.04
Linux ubuntu-beta 2.6.24-12-server #1 SMP Wed Mar 12 22:58:36 UTC 2008
x86_64 GNU/Linux
mdadm:
Installed: 2.6.3+200709292116+4450e59-3ubuntu3
xfsprogs:
Installed: 2.9.4-2
Raid 5 on five 1TB drives,
Beeing somewhat new to Linux I'm not sure what constitutes a kernel
crash. Everything locks up completely, sysrq does not work. No output to
the monitor.
--
Feisty crash possibly related to mdadm/raid5
https://bugs.launchpad.net/bugs/110304
You received this bug notification because you are a mem
I can confirm that everything works as it should on 2.6.17-11
I haven't come any closer to figuring out what happens on 2.6.20-15 and
2.6.20-16. Sometimes it crashes on mount, sometimes it can work for
hours.
--
Feisty crash possibly related to mdadm/raid5
https://bugs.launchpad.net/bugs/110304
Yes I know everything seems fine now, but at boot it refused to start, I
had to manually re-add one of the drives and mdadm --run it.
The crash has happened twice. I'm currently checking if it also occurs
with the old kernel (2.6.17-11)
The reason I upgraded in the first place was to prevent data
It crashed after having been up for atleast some hours. (crashed while I
was sleeping) The raid array was mounted, but as I said I don't really
know if it's related or not.
--
Feisty crash possibly related to mdadm/raid5
https://bugs.launchpad.net/bugs/110304
You received this bug notification be
** Attachment added: "Output from mdadm --examine /dev/sd*"
http://librarian.launchpad.net/7411695/drives.txt
--
Feisty crash possibly related to mdadm/raid5
https://bugs.launchpad.net/bugs/110304
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug con
** Attachment added: "Output from mdadm --query --detail /dev/md0"
http://librarian.launchpad.net/7411694/detail.txt
--
Feisty crash possibly related to mdadm/raid5
https://bugs.launchpad.net/bugs/110304
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
I've opened up another bug for my other troubles, as they might not be
entirely related to the UUID problem:
https://bugs.launchpad.net/ubuntu/+bug/110304
--
Wrong RAID UUID on PATA RAID5 partitions after Feisty Upgrade
https://bugs.launchpad.net/bugs/107080
You received this bug notification be
This also happened to me. I managed to start it by changing the UUID in
mdadm.conf to what was reported by mdadm --examine. I still have issues
though, hard crashes etc.
--
Wrong RAID UUID on PATA RAID5 partitions after Feisty Upgrade
https://bugs.launchpad.net/bugs/107080
You received this bug n
Public bug reported:
Running Linux 2.6.20-15-server #2 SMP 32bit
First, I also had the "UUID of raid devices have changed after upgrade
to Feisty", which I "fixed" by editing mdadm.conf with the new id. After
that I started the array which rebuilt itself.
I thought everything was allright, until
Driver from http://www.nvidia.com works fine, also seem to fix the
lcd/crt swap issue. *Happy*
--
No display image on Ubuntu Feisty Fawn
https://bugs.launchpad.net/bugs/105761
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubu
Thanks that gave me a bit more info to work with. Basically it says
"Failed to initialize the NVIDIA graphics device PCI:1:0:0. no screens
found."
This can't be the original problem though, as I didn't get any display
image without the nvidia driver either.
I reverted back to "nv" (was using "nvi
Forgot to mention that I'm using the 64 bit version of Ubuntu.
** Description changed:
- I tried installing Ubuntu Feisty Beta (Xubuntu edition), but I just get
+ I tried installing Ubuntu Feisty Beta (Xubuntu edition), but I just got
a black screen on the graphical installer. I then downloaded
Public bug reported:
I tried installing Ubuntu Feisty Beta (Xubuntu edition), but I just get
a black screen on the graphical installer. I then downloaded the
alternate install CD which worked fine. After GRUB is displayed I get
nothing; everthing is black.
Computer is working fine, as I installed
25 matches
Mail list logo
