[Bug 1582323] Re: Commissioning fails when competing cloud metadata resides on disk
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1582323 Title: Commissioning fails when competing cloud metadata resides on disk To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1582323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1648380] Re: cloud-init fails to find CloudSigma datasource with cloud-init 0.7.8-1-g3705bb5-0ubuntu1
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 Ubuntu. https://bugs.launchpad.net/bugs/1648380 Title: cloud-init fails to find CloudSigma datasource with cloud-init 0.7.8-1-g3705bb5-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1648380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 228442] Re: KVM eats 100% CPU, Host Hardy64, Guest XP with more than 1 VCPU
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 Hardy64, Guest XP with more than 1 VCPU https://bugs.launchpad.net/bugs/228442 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-bugs
[Bug 343781] Re: nvidia-based Mac Mini (Macmini3, 1) won't reboot (but will halt)
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 reboot (but will halt) https://bugs.launchpad.net/bugs/343781 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-bugs
[Bug 208551] Re: mdadm with Raid5 stuck in uninterruptable sleep
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 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-bugs
Re: [Bug 208551] Re: mdadm, Raid5 and XFS stuck in uninterruptable sleep
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: > Hi, > > I've applied commit 6ed3003c19a96fe18edf8179c4be6fe14abbebbc and built > for testing linux - 2.6.24-20.39cking4 package - you can download the > package from my PPA at: https://launchpad.net/~colin-king/+archive > > Please can you test this fix and let me know if it works so that we can > add it to the next release of Hardy. > > To test, add the following lines to your apt sources.list: > > deb http://ppa.launchpad.net/colin-king/ubuntu hardy main > deb-src http://ppa.launchpad.net/colin-king/ubuntu hardy main > > alternatively, follow the instructions at: https://help.ubuntu.com/8.04 > /add-applications/C/extra-repositories-adding.html > > Thanks, Colin > -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 208551] Re: mdadm, Raid5 and XFS stuck in uninterruptable sleep
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 uninterruptable sleep https://bugs.launchpad.net/bugs/208551 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-bugs
[Bug 198871] Re: Jmicron AHCI controller probs...
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 AHCI controller probs... https://bugs.launchpad.net/bugs/198871 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-bugs
[Bug 208551] Re: mdadm, Raid5 and XFS stuck in uninterruptable sleep
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, and remounting (the read only) filesystem was no problem. dmesg output: [131405.242868] xfs_force_shutdown(dm-1,0x1) called from line 420 of file /build /buildd/linux-2.6.24/fs/xfs/xfs_rw.c. Return address = 0x883cdf59 [131405.242892] Filesystem "dm-1": I/O Error Detected. Shutting down filesystem : dm-1 [131405.242932] Please umount the filesystem, and rectify the problem(s) [131405.242958] xfs_force_shutdown(dm-1,0x1) called from line 420 of file /build /buildd/linux-2.6.24/fs/xfs/xfs_rw.c. Return address = 0x883cdf59 Not sure if it's related to the first post or not. Any input would be appreciated. -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 208551] Re: mdadm, Raid5 and XFS stuck in uninterruptable sleep
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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 208551] Re: mdadm, Raid5 and XFS stuck in uninterruptable sleep
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 XFS stuck in uninterruptable sleep https://bugs.launchpad.net/bugs/208551 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-bugs
[Bug 208551] [NEW] mdadm, Raid5 and XFS stuck in uninterruptable sleep
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, set up as follows: mdadm --create /dev/md0 --level=5 --raid-devices=5 /dev/sd[b,c,d,e,f] mkfs.xfs /dev/md0 mount /dev/md0 /mnt/drive md0 : active raid5 sdf[4] sde[3] sdd[2] sdc[1] sdb[0] 3907049984 blocks level 5, 64k chunk, algorithm 2 [5/5] [U] The drives are connected to a 5-1 port multiplier again connected to a 2-port SiI 3132 based pciexpress sata controller. Problem does not seem to be related to this, as I can write/read to the drives individually without any trouble. Copying data do this partition results in a permanent lock on several processes related to it, getting stuck in the D(+) state. Happened four times in a row after 10-40 GB had been copied. I can't kill any of the processes, nor am I able to reboot, have to power cycle. There are no messages related to it in dmesg or any of the logs, as far as the system is concerned nothing is wrong. After power cycling the array starts rebuilding (as it should), but this rebuild also stops because of the same error. Problem seems very related to this: http://www.issociate.de/board/post/471929/2.6.24-rc6_reproducible_raid5_hang.html As suggested by this thread, I tried to increase stripe_cache_size. Setting it to 4096 seems to have solved my hang, as I have at the time of writing this copied 1.7TB without error. http://kerneltrap.org/mailarchive/linux-kernel/2007/11/8/397727 If this is the same problem and I'm reading it right, it seems like it's supposed to be fixed already. Not sure though. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: hang hardy heron mdadm raid5 stuck xfs -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 110304] Re: Feisty crash possibly related to mdadm/raid5
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 member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 110304] Re: Feisty crash possibly related to mdadm/raid5
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 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 110304] Re: Feisty crash possibly related to mdadm/raid5
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 corruption on raid5 with cryptsetup, as reported for kernels < 2.6.19. -- 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 contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 110304] Re: Feisty crash possibly related to mdadm/raid5
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 because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 110304] Re: Feisty crash possibly related to mdadm/raid5
** 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 contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 110304] Re: Feisty crash possibly related to mdadm/raid5
** 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 bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 107080] Re: Wrong RAID UUID on PATA RAID5 partitions after Feisty Upgrade
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 because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 107080] Re: Wrong RAID UUID on PATA RAID5 partitions after Feisty Upgrade
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 notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 110304] Feisty crash possibly related to mdadm/raid5
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 a hard crash. I rebooted, array was dirty AND degraded, and I had to manually re-add a drive. (mind you, the drive that faults is random, so there arn't any real bad drive here) Even display image disappears when it crashes. I don't really know where to look for information on the crash, or even what is causing it, all I know it was not happening in 6.10 and might be mdadm/raid5 related. I'm also using cryptsetup for 128 bit AES encryption on top of this raid5. ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed ** Tags: crash feisty mdadm ** Description changed: - Running Linux desk-dfs 2.6.20-15-server #2 SMP 32bit + 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 a hard crash. I rebooted, array was dirty AND degraded, and I had to manually re-add a drive. (mind you, the drive that faults is random, so there arn't any real bad drive here) Even display image disappears when it crashes. I don't really know where to look for information on the crash, or even what is causing it, all I know it was not happening in 6.10 and might be mdadm/raid5 related. I'm also using cryptsetup for 128 bit AES encryption on top of this raid5. ** Tags added: crash feisty mdadm -- 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 contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 105761] Re: No display image on Ubuntu Feisty Fawn
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. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 105761] Re: No display image on Ubuntu Feisty Fawn
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 "nvidia") to see if it fails in a different way, and was to surprised to see that it boots fine. Problem solved I guess, as for the reason I have no idea. It does some funny swapping of the monitors too, it boots on the CRT, XFCE loads on the LCD, and if I go to a console it swaps to the CRT again :P Thanks! Now I just have to get the nvidia driver working -- 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. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 105761] Re: No display image on Ubuntu Feisty Fawn
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 the alternate install CD which worked fine. After GRUB is displayed I get - nothing; everthing is black. + nothing; everything is black. Computer is working fine, as I installed SSH from the recovery console, rebooted, and managed to log in. I've tried the following steps: syslog/dmesg doesn't have much of interest (though I don't know what I should look for) All cables etc have been tested. I also connected a second monitor to the other dvi port in case it defaulted to that one. I tried installing nvidia-glx, but it shouldn't matter for console, and it didn't I also tried swapping from "nv" to "vesa", no go (again, shouldn't matter for console) Hardware: Intel Core 2 Quad 3.2 ghz GeForce 8800 EVGA nForce 680i mainboard Soundblaster X-Fi 2x Western Digital Raptor 150 gbyte on nForce ata controller ** Tags added: display feisty -- 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. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 105761] No display image on Ubuntu Feisty Fawn
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 SSH from the recovery console, rebooted, and managed to log in. I've tried the following steps: syslog/dmesg doesn't have much of interest (though I don't know what I should look for) All cables etc have been tested. I also connected a second monitor to the other dvi port in case it defaulted to that one. I tried installing nvidia-glx, but it shouldn't matter for console, and it didn't I also tried swapping from "nv" to "vesa", no go (again, shouldn't matter for console) Hardware: Intel Core 2 Quad 3.2 ghz GeForce 8800 EVGA nForce 680i mainboard Soundblaster X-Fi 2x Western Digital Raptor 150 gbyte on nForce ata controller ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- 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. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
