Re: [Bug 573477] Re: Mdadm array fails to assemble on boot.
It does seem like there is a timing issue here. Some sort of race condition causes the array to be assembled incorrectly, or not at all perhaps. My gut tells me it's something to do with the new upstart system that ubuntu moved to, because it never happened before they switched. I still haven't gotten around to rebuilding my entire array as suggested... I've currently got quite a bit of data on the array that I don't really want to have to spend the time to save elsewhere and copy back. I've been rebooting whenever it happens as a workaround, but I'm still hoping someone can help out with finding a full solution. On Mon, Sep 27, 2010 at 9:40 PM, Bob Blanchett <573...@bugs.launchpad.net> wrote: > I started getting an error on the ubuntusplash screen when my PATA md > array wouldnt mount. > (S)kip mounting or M for manual recovery > funnily enough goingin into manual mode and looking at dmesg didnt throw up > any errors > > /proc/mdstat showed the array as inactive partial and also named it > /dev/md_p1 whe it had always been known as /dev/md3 (it was always an > unpartitioned whole disk md component > > Skipping mounting I was always able to get the array up via "disk > utilty" by stopping the array, restarting it and then issuing a sudo > mount -a (by specified uuid in fsatb .for affected array) > > issuing a dpkg-reconfigure mdadm seemed to work through 2 reboots > > but then the system after the next reboot mounted one of the component disks > on the mountpoint where the array is > (dev/sdc1 instead of /dev/md3p1) > > unmounted did dpkg-reconfigure again rebooted and got "skip" > > mdstat showed the array as up, but umounted > > substituted the dev path for the uuid in fstab and its currently > rebooted ok.. > > Is there a timing issue somewhere? > > -- > Mdadm array fails to assemble on boot. > https://bugs.launchpad.net/bugs/573477 > You received this bug notification because you are a direct subscriber > of the bug. > -- Mdadm array fails to assemble on boot. https://bugs.launchpad.net/bugs/573477 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 573477] Re: Mdadm array fails to assemble on boot.
My RAID array still does not come up reliably upon every reboot. It seems that if I reboot once after the "not ready or present" message, it usually will come up fine the second time. I've been leaving my system on for a while to avoid having to deal with this however. Right now, I still need to find some space to store almost 2TB of data to rebuild the array fully as was suggested earlier in this thread. -- Mdadm array fails to assemble on boot. https://bugs.launchpad.net/bugs/573477 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 573477] Re: Mdadm array fails to assemble on boot.
Today it failed to mount on boot once again. I pressed "S" to skip mounting, and upon trying to mount it manually, I get: trinitr...@saturn:~$ sudo mount /media/terabyte mount: /dev/md0: can't read superblock trinitr...@saturn:~$ cat /proc/mdstat Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] md_d0 : inactive sda1[0](S) 732571904 blocks md0 : inactive sdb1[1](S) sdc1[2](S) sdd1[3](S) 2197715712 blocks unused devices: .Ok... so now it's putting one of my drives on md_d0 again??? Why? Apparently ubuntu is bringing up the drives in the WRONG ORDER! All drives [a-d] are now 1 letter incremented in the alphabet. (ie: ubuntu thinks sdb1 should be called sda1, sdc1 should be called sdb1, etc...) I'm not sure which drive it thinks is sde now, because it says there's no superblock on it. How can I fix it's mistake? Debug info below: --- trinitr...@saturn:~$ sudo mdadm --detail /dev/md0 mdadm: md device /dev/md0 does not appear to be active. trinitr...@saturn:~$ sudo mdadm --detail /dev/md_d0 mdadm: md device /dev/md_d0 does not appear to be active. trinitr...@saturn:~$ sudo mdadm --examine /dev/sda1 /dev/sda1: Magic : a92b4efc Version : 00.90.00 UUID : 7a0e5ba8:669595fc:852484a6:e390a598 (local to host saturn) Creation Time : Fri Jan 9 03:40:39 2009 Raid Level : raid5 Used Dev Size : 732571904 (698.64 GiB 750.15 GB) Array Size : 2197715712 (2095.91 GiB 2250.46 GB) Raid Devices : 4 Total Devices : 4 Preferred Minor : 0 Update Time : Thu Jul 1 00:34:29 2010 State : clean Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 Checksum : b3c7801c - correct Events : 148755 Layout : left-symmetric Chunk Size : 64K Number Major Minor RaidDevice State this 0 8 170 active sync /dev/sdb1 0 0 8 170 active sync /dev/sdb1 1 1 8 331 active sync /dev/sdc1 2 2 8 492 active sync /dev/sdd1 3 3 8 653 active sync /dev/sde1 trinitr...@saturn:~$ sudo mdadm --examine /dev/sdb1 /dev/sdb1: Magic : a92b4efc Version : 00.90.00 UUID : 7a0e5ba8:669595fc:852484a6:e390a598 (local to host saturn) Creation Time : Fri Jan 9 03:40:39 2009 Raid Level : raid5 Used Dev Size : 732571904 (698.64 GiB 750.15 GB) Array Size : 2197715712 (2095.91 GiB 2250.46 GB) Raid Devices : 4 Total Devices : 4 Preferred Minor : 0 Update Time : Thu Jul 1 00:34:29 2010 State : clean Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 Checksum : b3c7802e - correct Events : 148755 Layout : left-symmetric Chunk Size : 64K Number Major Minor RaidDevice State this 1 8 331 active sync /dev/sdc1 0 0 8 170 active sync /dev/sdb1 1 1 8 331 active sync /dev/sdc1 2 2 8 492 active sync /dev/sdd1 3 3 8 653 active sync /dev/sde1 trinitr...@saturn:~$ sudo mdadm --examine /dev/sdc1 /dev/sdc1: Magic : a92b4efc Version : 00.90.00 UUID : 7a0e5ba8:669595fc:852484a6:e390a598 (local to host saturn) Creation Time : Fri Jan 9 03:40:39 2009 Raid Level : raid5 Used Dev Size : 732571904 (698.64 GiB 750.15 GB) Array Size : 2197715712 (2095.91 GiB 2250.46 GB) Raid Devices : 4 Total Devices : 4 Preferred Minor : 0 Update Time : Thu Jul 1 00:34:29 2010 State : clean Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 Checksum : b3c78040 - correct Events : 148755 Layout : left-symmetric Chunk Size : 64K Number Major Minor RaidDevice State this 2 8 492 active sync /dev/sdd1 0 0 8 170 active sync /dev/sdb1 1 1 8 331 active sync /dev/sdc1 2 2 8 492 active sync /dev/sdd1 3 3 8 653 active sync /dev/sde1 trinitr...@saturn:~$ sudo mdadm --examine /dev/sdd1 /dev/sdd1: Magic : a92b4efc Version : 00.90.00 UUID : 7a0e5ba8:669595fc:852484a6:e390a598 (local to host saturn) Creation Time : Fri Jan 9 03:40:39 2009 Raid Level : raid5 Used Dev Size : 732571904 (698.64 GiB 750.15 GB) Array Size : 2197715712 (2095.91 GiB 2250.46 GB) Raid Devices : 4 Total Devices : 4 Preferred Minor : 0 Update Time : Thu Jul 1 00:34:29 2010 State : clean Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 Checksu
[Bug 544935] Re: netcat-openbsd exits too soon
Why does Ubuntu constantly have to mess with things that had already been working and tested before, and then subsequently release them into the repositories so it can break things for everyone? This isn't just a problem with their version of netcat. I'm also talking about pulseaudio, upstart, grub2, etc... Please fix! -- netcat-openbsd exits too soon https://bugs.launchpad.net/bugs/544935 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 485538] Re: /usr/share/mythtv/mythvideo/scripts/jamu.py returns error on success
Looks like I'm getting the jamu.py to exit some other way, as the lines in my file read: [..] # Check if this is a Scheduled and Recorded graphics download request if self.config['mythtv_watched']: self._downloadScheduledRecordedGraphics() sys.exit(0) [..] It may be another issue with how the script is exiting. I'll have to look into this later. -- /usr/share/mythtv/mythvideo/scripts/jamu.py returns error on success https://bugs.launchpad.net/bugs/485538 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 485538] Re: /usr/share/mythtv/mythvideo/scripts/jamu.py returns error on success
I tried the fix by enabling the Mythbuntu autobuilds, and am currently running version: mythvideo 0.23.0+fixes25073-0ubuntu0+mythbuntu2 I'm still getting emails every hour like: From: root To: root Date: Fri, Jun 11, 2010 at 10:17 AM Subject:Cron cd / && run-parts --report /etc/cron.hourly run-parts: /etc/cron.hourly/mythvideo exited with return code 1 -- /usr/share/mythtv/mythvideo/scripts/jamu.py returns error on success https://bugs.launchpad.net/bugs/485538 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 573477] Re: Mdadm array fails to assemble on boot.
Rebuilt again, and noticed an update for the mountall package too (not sure if this was related). Seems everything is being brought up fine now after a reboot. I just hope it stays that way -- Mdadm array fails to assemble on boot. https://bugs.launchpad.net/bugs/573477 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 485538] Re: /usr/share/mythtv/mythvideo/scripts/jamu.py returns error on success
I'm getting this message in an email from cron every hour. Using mythvideo package 0.23.0+fixes24104-0ubuntu2 -- /usr/share/mythtv/mythvideo/scripts/jamu.py returns error on success https://bugs.launchpad.net/bugs/485538 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 573477] Re: Mdadm array fails to assemble on boot.
ok, finished rebuilding it and ran "sudo mdadm --examine" on every device and partition. The info looks correct for: /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1 It reports "mdadm: No md superblock detected" for: /dev/md0 /dev/sdb /dev/sdc /dev/sdd /dev/sde So hopefully this means that no superblock is on the devices themselves, and only the partitions. (I think I must have made the mistake of adding /dev/sde rather than /dev/sde1 the very first time, which is probably what caused all this mess). -- Mdadm array fails to assemble on boot. https://bugs.launchpad.net/bugs/573477 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 573477] Re: Mdadm array fails to assemble on boot.
Here is the successful output of GParted formatting /dev/sde1 before my rebuild #5. ** Attachment added: "Try #5 Repartitioning & reformatting /dev/sde" http://launchpadlibrarian.net/48589374/gparted_details_SUCCESS.htm -- Mdadm array fails to assemble on boot. https://bugs.launchpad.net/bugs/573477 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 573477] Re: Mdadm array fails to assemble on boot.
Rebuilding my RAID for the 5th time now. Here's the complete shell session, so in case I'm doing something wrong, PLEASE point it out! Let's hope it works this time! And here we go. trinitr...@saturn:/media$ sudo fdisk -l /dev/sde Disk /dev/sde: 750.2 GB, 750156374016 bytes 255 heads, 63 sectors/track, 91201 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x Disk /dev/sde doesn't contain a valid partition table trinitr...@saturn:/media$ cat /proc/mdstat Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] md_d0 : inactive sde1[3](S) 732571904 blocks md0 : inactive sdb1[0](S) sdc1[1](S) sdd1[2](S) 2197715712 blocks unused devices: trinitr...@saturn:/media$ sudo mdadm --stop /dev/md_d0 [sudo] password for trinitronx: mdadm: stopped /dev/md_d0 trinitr...@saturn:/media$ sudo mdadm --examine /dev/md_d0 mdadm: cannot open /dev/md_d0: No such file or directory trinitr...@saturn:/media$ sudo mdadm --examine /dev/sde mdadm: No md superblock detected on /dev/sde. trinitr...@saturn:/media$ sudo mdadm --examine /dev/sde1 /dev/sde1: Magic : a92b4efc Version : 00.90.00 UUID : 7a0e5ba8:669595fc:852484a6:e390a598 (local to host saturn) Creation Time : Fri Jan 9 03:40:39 2009 Raid Level : raid5 Used Dev Size : 732571904 (698.64 GiB 750.15 GB) Array Size : 2197715712 (2095.91 GiB 2250.46 GB) Raid Devices : 4 Total Devices : 4 Preferred Minor : 0 Update Time : Sun May 16 22:13:13 2010 State : clean Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 Checksum : b38b3b34 - correct Events : 122066 Layout : left-symmetric Chunk Size : 64K Number Major Minor RaidDevice State this 3 8 653 active sync /dev/sde1 0 0 8 170 active sync /dev/sdb1 1 1 8 331 active sync /dev/sdc1 2 2 8 492 active sync /dev/sdd1 3 3 8 653 active sync /dev/sde1 trinitr...@saturn:/media$ sudo mdadm --zero-superblock /dev/sde1 trinitr...@saturn:/media$ sudo mdadm --examine /dev/sde1 mdadm: No md superblock detected on /dev/sde1. trinitr...@saturn:/media$ sudo mdadm --zero-superblock /dev/sde mdadm: Unrecognised md component device - /dev/sde - ### HERE'S WHERE I DELETED OLD PARTITION, ADDED NEW TABLE, AND REFORMATTED IN GPARTED ### - trinitr...@saturn:/media$ sudo fdisk -l /dev/sde Disk /dev/sde: 750.2 GB, 750156374016 bytes 255 heads, 63 sectors/track, 91201 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x0008b84d Device Boot Start End Blocks Id System /dev/sde1 1 91201 732572001 fd Linux raid autodetect trinitr...@saturn:/media$ sudo mdadm --detail /dev/md0 mdadm: md device /dev/md0 does not appear to be active. trinitr...@saturn:/media$ sudo mdadm --examine /dev/sde1 mdadm: No md superblock detected on /dev/sde1. trinitr...@saturn:/media$ sudo mdadm --examine /dev/sde mdadm: No md superblock detected on /dev/sde. trinitr...@saturn:/media$ sudo mdadm --examine /dev/sdb mdadm: No md superblock detected on /dev/sdb. trinitr...@saturn:/media$ sudo mdadm --examine /dev/sdb1 /dev/sdb1: Magic : a92b4efc Version : 00.90.00 UUID : 7a0e5ba8:669595fc:852484a6:e390a598 (local to host saturn) Creation Time : Fri Jan 9 03:40:39 2009 Raid Level : raid5 Used Dev Size : 732571904 (698.64 GiB 750.15 GB) Array Size : 2197715712 (2095.91 GiB 2250.46 GB) Raid Devices : 4 Total Devices : 4 Preferred Minor : 0 Update Time : Sun May 16 22:13:13 2010 State : clean Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 Checksum : b38b3afe - correct Events : 122066 Layout : left-symmetric Chunk Size : 64K Number Major Minor RaidDevice State this 0 8 170 active sync /dev/sdb1 0 0 8 170 active sync /dev/sdb1 1 1 8 331 active sync /dev/sdc1 2 2 8 492 active sync /dev/sdd1 3 3 8 653 active sync /dev/sde1 trinitr...@saturn:/media$ sudo mdadm --examine /dev/sdc1 /dev/sdc1: Magic : a92b4efc Version : 00.90.00 UUID : 7a0e5ba8:669595fc:852484a
[Bug 573477] Re: Mdadm array fails to assemble on boot.
Now that I tried to create a new partition table and repartition /dev/sde, mdadm is trying to use it strangely as a second array!! wtf? GParted failed to repartition it a second time, and now this: trinitr...@saturn:/media$ cat /proc/mdstat Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] md_d0 : inactive sde1[3](S) 732571904 blocks md0 : inactive sdb1[0](S) sdc1[1](S) sdd1[2](S) 2197715712 blocks unused devices: ** Attachment added: "GParted XFS format failure #2" http://launchpadlibrarian.net/48588088/gparted_details_2.htm -- Mdadm array fails to assemble on boot. https://bugs.launchpad.net/bugs/573477 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 573477] Re: Mdadm array fails to assemble on boot.
GParted just gave me troubles reformatting the drive again. Here are the details of that. ** Attachment added: "Gparted XFS format failure" http://launchpadlibrarian.net/48587994/gparted_details.htm -- Mdadm array fails to assemble on boot. https://bugs.launchpad.net/bugs/573477 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 573477] Re: Mdadm array fails to assemble on boot.
Attached: kernel message log ** Attachment added: "Kernel message log with working array before reboot, and nothing after reboot" http://launchpadlibrarian.net/48587404/messages -- Mdadm array fails to assemble on boot. https://bugs.launchpad.net/bugs/573477 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 573477] Re: Mdadm array fails to assemble on boot.
Attached: output of examining all disk partitions with fdisk -l ** Attachment added: "Examining partitions with fdisk -l" http://launchpadlibrarian.net/48587379/Examining_Partitions.txt -- Mdadm array fails to assemble on boot. https://bugs.launchpad.net/bugs/573477 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 573477] Re: Mdadm array fails to assemble on boot.
Looked into this more today and found that for some reason my array is not being detected and assembled correctly after a reboot. I've got a RAID 5 with 4 disks: /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1 Here's what I've accomplished so far: 1) I removed /dev/sde1 using "sudo mdadm /dev/md0 --fail /dev/sde1 --remove /dev/sde1" 2) I zeroed it's superblock using "sudo mdadm --zero-superblock /dev/sde1" 3) I zeroed the entire disk with "sudo dd if=/dev/zero of=/dev/sde bs=1M" 4) I created a new msdos partition table and added 1 partition using the full size of the disk with gparted. 5) I reformatted the partition with "sudo mkfs.xfs -f -b size=4096 -d sunit=128,swidth=384 -L mythtv /dev/sde" 6) Finally, I added the disk back into the raid array using "sudo mdadm /dev/md0 --add /dev/sde1" After rebuilding the array on all 4 disks, everything was working. I could unmount the partition, stop /dev/md0, and then restart it by doing: sudo umount /media/terabyte sudo mdadm --stop /dev/md0 sudo mdadm --assemble --scan This worked fine before a reboot. After rebooting just now, it failed to bring the array up, giving the familiar error: "the disk for/mnt/md0 is not ready yet or not present. Continue to wait; or Press S to skip mount or M for manual recovery." I logged in and tried to assemble the array, but got this: - trinitr...@saturn:~$ sudo mdadm --assemble --scan -v mdadm: looking for devices for further assembly mdadm: cannot open device /dev/sdd1: Device or resource busy mdadm: cannot open device /dev/sdd: Device or resource busy mdadm: no recogniseable superblock on /dev/sde mdadm: cannot open device /dev/sdc1: Device or resource busy mdadm: cannot open device /dev/sdc: Device or resource busy mdadm: cannot open device /dev/sdb1: Device or resource busy mdadm: cannot open device /dev/sdb: Device or resource busy mdadm: cannot open device /dev/sda6: Device or resource busy mdadm: cannot open device /dev/sda5: Device or resource busy mdadm: no recogniseable superblock on /dev/sda2 mdadm: cannot open device /dev/sda1: Device or resource busy mdadm: cannot open device /dev/sda: Device or resource busy mdadm: No arrays found in config file or automatically trinitr...@saturn:~$ cat /proc/mdstat Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] md0 : inactive sdb1[0](S) sdc1[1](S) sdd1[2](S) 2197715712 blocks unused devices: trinitr...@saturn:~$ sudo mdadm --detail /dev/md0 mdadm: md device /dev/md0 does not appear to be active. - Now, examining the superblocks on the rest of the disks shows that /dev/sde1 is missing!!! Trying to examine /dev/sde1 says that the device does not exist!! I've repeated this multiple times and cannot figure out what it's problem is. Here is the superblock information from /dev/sde1 and the first 3 disks: - trinitr...@saturn:~$ sudo mdadm --examine /dev/sde1 mdadm: cannot open /dev/sde1: No such file or directory trinitr...@saturn:~$ sudo mdadm --examine /dev/sdb1 /dev/sdb1: Magic : a92b4efc Version : 00.90.00 UUID : 7a0e5ba8:669595fc:852484a6:e390a598 (local to host saturn) Creation Time : Fri Jan 9 03:40:39 2009 Raid Level : raid5 Used Dev Size : 732571904 (698.64 GiB 750.15 GB) Array Size : 2197715712 (2095.91 GiB 2250.46 GB) Raid Devices : 4 Total Devices : 4 Preferred Minor : 0 Update Time : Sun May 16 22:13:13 2010 State : clean Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 Checksum : b38b3afe - correct Events : 122066 Layout : left-symmetric Chunk Size : 64K Number Major Minor RaidDevice State this 0 8 170 active sync /dev/sdb1 0 0 8 170 active sync /dev/sdb1 1 1 8 331 active sync /dev/sdc1 2 2 8 492 active sync /dev/sdd1 3 3 8 653 active sync trinitr...@saturn:~$ sudo mdadm --examine /dev/sdc1 /dev/sdc1: Magic : a92b4efc Version : 00.90.00 UUID : 7a0e5ba8:669595fc:852484a6:e390a598 (local to host saturn) Creation Time : Fri Jan 9 03:40:39 2009 Raid Level : raid5 Used Dev Size : 732571904 (698.64 GiB 750.15 GB) Array Size : 2197715712 (2095.91 GiB 2250.46 GB) Raid Devices : 4 Total Devices : 4 Preferred Minor : 0 Update Time : Sun May 16 22:13:13 2010 State : clean Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 Checksum : b38b3b10 - correct Events : 122066 Layout : left-symmetric Chunk Size : 64K Number Major Minor RaidDevice State this 1 8
[Bug 573272] Re: System won't boot after upgrade to 10.04
*** This bug is a duplicate of bug 507881 *** https://bugs.launchpad.net/bugs/507881 ** This bug has been marked a duplicate of bug 507881 Plymouth doesn't show messages sent before the splash screen is visible -- System won't boot after upgrade to 10.04 https://bugs.launchpad.net/bugs/573272 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 573477] Re: Mdadm array fails to assemble on boot.
Found the line it was talking about in /var/lib/dpkg/info/mdadm.postinst ---SNIP--- if [ ! -f /proc/mdstat ] && [ -x $(command -v modprobe 2>/dev/null) ]; then modprobe -k md >/dev/null 2>&1 || : fi if [ ! -f /proc/mdstat ]; then echo 'W: mdadm: failed to load MD subsystem.' >&2 fi if [ ! -e /dev/md15 ] \ && [ ! -e /dev/.static/dev/md15 ] \ && [ ! -e /dev/.devfsd ]; then echo -n 'Generating array device nodes... ' >&2 cd /dev if /dev/MAKEDEV md >&2 >/dev/null; then echo 'done.' >&2 else echo 'failed.' >&2 fi fi ---SNIP--- I haven't looked further into what that script really should be doing there however. -- Mdadm array fails to assemble on boot. https://bugs.launchpad.net/bugs/573477 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 573477] Re: Mdadm array fails to assemble on boot.
I am also seeing this upon update to mdadm_2.6.7.1-1ubuntu15 on a mythbuntu box. Luckily I can just assemble and mount the array manually afterwards, it just does not automatically do it upon boot. This would probably be a showstopper for anyone brave enough to have setup their root partition on a RAID array! -- Mdadm array fails to assemble on boot. https://bugs.launchpad.net/bugs/573477 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 348934] Re: MythTV doesn't go full screen without desktop visual effects off
Switched to gnome desktop in Mythbuntu 10.04 Beta 2 encountered this bug. Needed to do the workaround. Latest available version of mythtv on synaptic is: 0.23.0+fixes24158-0ubuntu2 Not sure if the numbering on trunk vs. fixes correlates... it still seems to appear in this 'fixes' branch however. -- MythTV doesn't go full screen without desktop visual effects off https://bugs.launchpad.net/bugs/348934 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 549593] Re: mythfrontend.real crashed with SIGSEGV in QX11PixmapData::x11ConvertToDefaultDepth()
what is the status on this bug? I am experiencing it as well on my updated Mythbuntu 10.04 Beta2 system. -- mythfrontend.real crashed with SIGSEGV in QX11PixmapData::x11ConvertToDefaultDepth() https://bugs.launchpad.net/bugs/549593 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 551147] Re: Shift Keys do not work in VNC
Can verify that adding the "-xkb" command line flag fixes the problem! Running Mythbuntu 10.04 Beta 2 with updates from apt. I've attached a very simple patch for the session script in /usr/share/mythbuntu/session.sh ** Patch added: "Simple patch for mythbuntu session.sh" http://launchpadlibrarian.net/45065827/x11vnc_session.patch -- Shift Keys do not work in VNC https://bugs.launchpad.net/bugs/551147 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 285387] Re: SoundKonverter is not called from Amarok
This package is broken in Intrepid. Out of box, amarok does not find the script, it does not have a .spec file to tell amarok to use it as a transcoder, and the script is broken until using this version. Here's how I fixed it on my system: # Create symlink for amarok to find the script sudo ln -s /usr/share/apps/amarok/scripts/soundkonverter /usr/share/apps/soundkonverter/amarokscript/ cd /usr/share/apps/soundkonverter/amarokscript/ # Replace bad script rm soundKonverter.rb wget http://launchpadlibrarian.net/18982229/soundKonverter.rb # Create spec file sudo vim soundKonverter.spec Now paste this into the .spec file: -START CUTTING HERE- name = SoundKonverter type = transcode [Transcode] target_formats = mp3 ogg flac m4a mp4 wav -STOP CUTTING HERE- Save that file. Now the next problem is that the transcode job will use "Very low" setting no matter what setting is chosen in the script's configuration in amarok. I looked at the script, and saw it was looking for a 'config' file, so I created one. It's probably a matter of having no write access to this directory to create one. I put one of the following settings on a single line: Very_low Low Medium High Very_high # EXAMPLE: set transcoding option to Very_high cd /usr/share/apps/soundkonverter/amarokscript/ echo 'Very_high' > config Perhaps the best way would be to install the script into the user's home directory like you posted before. I would think another solution would be to symlink any config files into the user's home dir, but then what happens with multiple users? Perhaps there's a way I do not know of using the debian packaging tools to set configuration files to a directory based on user. Please fix these bugs in 0.3.9 ;-) -- SoundKonverter is not called from Amarok https://bugs.launchpad.net/bugs/285387 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 137207] Re: No extract command on pop-up menu in Dolphin
I am having this issue on the Mythbuntu distribution. This distribution is based off xfce. I have installed dolphin and ark, but there is no "extract here" or "extract to" menu option in the right click menu. I think this functionality may be enabled by installation of some other package in the standard ubuntu/kubuntu distro. Is there a reason it shouldn't be in either the ark or dolphin packages themselves though? -- No extract command on pop-up menu in Dolphin https://bugs.launchpad.net/bugs/137207 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 83066] Re: no ps/2 keyboard with kernel 2.6.15-27-686-smp
Waiting on Intrepid Ibex Alpha5 to test as recommended. The machine I had this problem on stopped doing this once I switched to a USB keyboard, and I haven't tested the PS/2 keyboard lately (or even updated my Ubuntu install on that machine lately either). -- no ps/2 keyboard with kernel 2.6.15-27-686-smp https://bugs.launchpad.net/bugs/83066 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 244439] Re: missing symlinks break binary compatibility with native upstream components
I also ran into the issue with no more accounts being available :(. Too bad the new version had to wipe the old accounts off. After seeing that this fix for Ubuntu went into hardy-proposed, I was hoping to test the x86_64 build of weave in bug #442679 at mozilla bugs with this. Oh well.. guess I have to wait. In the meantime, I'm going to uninstall weave for now to do away with the wizard popup every time I open my browser :P Reference for others wishing to test... Precompiled x64 .xpi in: Bug: "Weave doesn't work on 64-bit Linux systems" https://bugzilla.mozilla.org/show_bug.cgi?id=442679 -- missing symlinks break binary compatibility with native upstream components https://bugs.launchpad.net/bugs/244439 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 129910] Re: Blank ttys when using vesafb (vga=xxx)
Hello, running a Gateway C-140x convertible tablet that includes an "ATI Mobility™ Radeon® X2300 HD" card. I initially had problems with the usplash not displaying on boot as well as the no terminal problem. I changed around the display settings in /etc/usplash.conf to be: xres=1024 yres=768 Then installed the proprietary fglrx drivers (in the process of this I had need of a terminal when X would not start, only to find that those would not work either! Only booting recovery console would get a working terminal thankfully.) Fixed it with the following steps: sudo apt-get install hwinfo sudo hwinfo --framebuffer looked through supported vga modes and found one I liked: Mode 0x0323: 1024x768 (+4096), 32 bits sudo vim /boot/grub/menu.lst found my kernel line and added vga=0x0323 Add fb modules to initramfs: sudo vim /etc/initramfs-tools/modules inserted: fbcon radeonfb sudo vim /etc/modprobe.d/blacklist-framebuffer un-blacklist the module by commenting out line: #blacklist radeonfb update the initramfs: sudo update-initramfs -u -k all -v Fixed with acceptable resolution and working usplash :D. Seriously though, how'd this bug even get into Gutsy? There's no need to break previously working framebuffer modules for the sake of power management. I'd think having a working set of ttys is more important. This is most certainly a case of: "If it ain't broke, don't fix it". I'd like to see this back to normal in Hardy. -- Blank ttys when using vesafb (vga=xxx) https://bugs.launchpad.net/bugs/129910 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 129860] Re: two xorg processes with fglrx
Same problem on Fiesty. I'm NOT running the packaged version of the drivers, but it's definitely ati's fglrx drivers doing this. This is still occurring with the NEW ones: version 8.41.7 Also note: one process seems to be spawning the other. relevant output of: ps auxf root 8892 0.0 0.0 12328 1412 ?Ss Oct12 0:00 /usr/sbin/gdm root 8893 0.0 0.1 12832 2552 ?SOct12 0:00 \_ /usr/sbin/gdm root 8894 0.1 0.6 18032 10148 tty7 Ss+ Oct12 0:21 \_ /usr/X11R6/bin/X :0 -br -audit 0 -auth /var/lib/gdm/:0.Xauth -nolisten tcp vt7 root 9340 0.0 0.6 18032 10148 tty7 S+ Oct12 0:00 | \_ /usr/X11R6/bin/X :0 -br -audit 0 -auth /var/lib/gdm/:0.Xauth -nolisten tcp vt7 1000 10121 0.0 0.7 31084 11944 ?Ssl Oct12 0:00 \_ gnome-session Looks like two gdm instances too? Also, people over at the gentoo forums (and other places) are puzzling about this: http://forums.gentoo.org/viewtopic-t-552618-postdays-0-postorder-asc-start-0.html -- two xorg processes with fglrx https://bugs.launchpad.net/bugs/129860 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 37821] Re: Regular network drops with madwifi
It is indeed a problem with Network Manager, and not the madwifi drivers. I have worked around this by uninstalling network manager, and simply configuring wpa_supplicant by hand. This involved putting a startup script in /etc/init.d that starts wpa_supplicant at bootup. If you want to make it able to start, stop, and restart it like a normal debian-style init.d script, then you'll have to create a different one. Mine's just a quick hack, and it's all I need: #!/bin/bash wpa_supplicant -Bw -qq -Dmadwifi -iath0 -c/etc/wpa_supplicant.conf Of course, adjust options to suit your interface and configuration file path, etc...After putting this script in /etc/init.d, I made a symlink to that script in /etc/rcS.d . It must come before networking in the boot process. I named it "S40iwpasupplicant" so that it came just before "S40networking". I'm sure there's a more official way of doing this that is cleaner, but this worked for me. -- Regular network drops with madwifi https://bugs.launchpad.net/bugs/37821 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76985] Re: amarok collection with mysql not working properly
I've been using the mysql database for my collection in amarok as well, and have seen the same problem happening. This has been ever since updating to Feisty. Packages used: Qt: 4.2.3-0ubuntu3 KDE: 3.5.6 Amarok: 1.4.5 (Build Date: Apr 4 2007) --- 2:1.4.5-0ubuntu7 mysql Ver 14.12 Distrib 5.0.38, for pc-linux-gnu (i486) using readline 5.2 --- 5.0.38-0ubuntu1 -- amarok collection with mysql not working properly https://bugs.launchpad.net/bugs/76985 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 107849] Crash report
Full Xgl crash report attached ** Attachment added: "Crash report" http://librarian.launchpad.net/7355682/_usr_bin_Xgl.1000.crash -- Xgl crashes to gdm upon starting amarok https://bugs.launchpad.net/bugs/107849 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 107849] Xgl crashes to gdm upon starting amarok
Public bug reported: Binary package hint: xserver-xgl This bug has been happening to me for some time now, quite randomly. Each time I attempt to start amarok, there seems to be a random chance that Xgl will crash, and I'll be greeted with my gdm login screen, forcing me to restart my desktop session, and possibly lose unsaved work. A crash report is attached. Note: I am running the current svn beryl packages from "Trevino's" repository, with these apt-get lines: deb http://download.tuxfamily.org/3v1deb edgy beryl-svn deb-src http://download.tuxfamily.org/3v1deb edgy beryl-svn ** Affects: xserver-xgl (Ubuntu) Importance: Undecided Status: Unconfirmed -- Xgl crashes to gdm upon starting amarok https://bugs.launchpad.net/bugs/107849 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 83066] Re: no ps/2 keyboard with kernel 2.6.15-27-686-smp
With my problem, the keyboard not working seems to behave like a random bug, popping up whenever it feels like it. I'm thinking that maybe this is some sort of race condition, which may or may not be related to multiple dependent threads running out of sync in the 686 kernel (But then again, I'm no kernel expert at all, just my hunch). When it happens on my PC, I am able to put the keyboard in the PS/2 mouse port (it's open since my mouse is a USB mouse), and then the keyboard will work in this port until the next reboot. I've managed to get syslogs for each case, both when the keyboard works in the keyboard PS/2 port, and when it doesn't work, forcing me to unplug it and put it into the PS/2 mouse port. I've attached a tar.gz with both logs included as separate text files. The "Working_keyboard.txt" file contains the log of 2 separate working boots, with different kernels, 2.6.17-10-generic and 2.6.17-11-generic. I've marked the places in the file where one ends and the other begins. There is an interesting line in the file entitled "Broken_keyboard.txt" on line 178 as follows: "PNP: No PS/2 controller found. Probing ports directly." The cooresponding lines in the file entitled "Working_keyboard.txt" are lines 183 and 704, which both say: "PNP: PS/2 Controller [PNP0303:KBD] at 0x60,0x64 irq 1" Hopefully this helps. ** Attachment added: "syslog files" http://librarian.launchpad.net/6392586/syslogs.tar.gz -- no ps/2 keyboard with kernel 2.6.15-27-686-smp https://launchpad.net/bugs/83066 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 67769] Re: tremulous-server starts on system startup, by default
I agree that this is a bug. My CPU usage is quite high on startup now, and as soon as I do: sudo /etc/init.d/tremulous-server stop , I get my CPU back ;). In the meantime, I'm going to disable this for my machine. -- tremulous-server starts on system startup, by default https://launchpad.net/bugs/67769 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 46475] Re: PCI USB controller causes keyboard to randomly lock up
My Desktop is a Dell Dimension XPS Generation 2. I had lost track of this post here, and forgot to update it with new info about the problem. I am now running Edgy, and still occasionally run into the keyboard locking up every once in a while, however, it seems much less frequent lately (or maybe that's just the luck of the draw and I'll end up getting it more later to make up for it... :P ) Anyway, I have found that when the keyboard locks up, I am able to unplug the PS/2 from the keyboard jack in the back, and then plug it back in to the Mouse PS/2 jack (I use a USB mouse, so that jack is free). After this, the keyboard functions fine! I think it must be some sort of weird race condition where the PS/2 ports get switched inputs for some reason randomly. When I reboot and the ports are back to normal, I must unplug the keyboard and put it back into the port meant for it, so that it will work again. -- PCI USB controller causes keyboard to randomly lock up https://launchpad.net/bugs/46475 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 32938] Re: Usb keyboard dies when gdm starts
I have just managed to get my PS/2 keyboard working by unplugging it and plugging it into my PC's other PS/2 port (labelled for use with a mouse) Please see bug #48877 for my full post, PC specs (if needed), and current xorg.conf file. Here: https://launchpad.net/distros/ubuntu/+bug/48877 -- Usb keyboard dies when gdm starts https://launchpad.net/bugs/32938 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 48877] Breakthrough Perhaps?
I have been having this bug off and on ever since using Ubuntu Breezy (pretty sure it happens in both 386 and 686... but since it's so random, and since I never really boot 386, I can't tell). I just found what I think to be a breakthrough while booting up my PC today. I started my machine up, and watched it get to the familiar gdm login screen which will decide my keyboard input's fate for the session. Again, I was greeted with the familiar sign that my keyboard was not going to work again: the num lock light was lit after the boot process finished and brought me to gdm. Absolutely no keyboard input does anything while it's in this zombie state. Then, I decided that I've been sick of this for so long that I'd try unplugging my keyboard again to no avail. Then, I realized that I had never actually tried plugging my PS/2 keyboard into my Dell PC's other PS/2 port (the one that's labelled on the back for use with a mouse). To my surprise, my keyboard was working again!! I sit here typing this with the keyboard plugged into the mouse PS/2 port! Luckily my mouse is not a PS/2 mouse, but a USB optical mouse ;), so I do have mouse input as well. I also just tested a PS/2 mouse in the keyboard port, but the port itself is zombified... I can plug my keyboard in, it gets power of course, but no input is taken. Maybe an off by 1 bug? Hopefully useful info: Computer: Dell XPS Desktop Generation 2 Processor: Pentium 4 3.2GHz w/ Hyperthreading Mobo: Dell-ified intel i875p chipset Keyboard: standard Dell brand PS/2 keyboard Mouse: Razer Copperhead USB mouse OS: Ubuntu Dapper Drake 6.06 LTS Kernel: 2.6.15-26-686 xorg.conf included as attachment ** Attachment added: "my current xorg.conf file" http://librarian.launchpad.net/4226438/xorg.conf -- PS/2 keyboard does not work https://launchpad.net/bugs/48877 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 23289] Re: Amarok 1.3.1 from breezy updates uses all available CPU
I'm getting this too, with: ubuntu dapper 6.06 KDE 3.5.2 (kubuntu-desktop package installed) Amarok 1.4.1 - official package from: deb http://kubuntu.org/packages/amarok-141 dapper main Upon starting amarok, I see my memory usage start to slowly go way up... and then amarok starts using 52% of my CPU while not playing or doing anything! Putting my mouse over the window always shows the busy cursor. I can play music and then it takes about 52-80%. After attempting to close amarok, the window exits, but i can still see 'amarokapp' running and *still* using my CPU and memory. To get it to shut down, i need to kill it. I've also noticed problems with shutting down/logging out after starting amarok, possibly from the non-dying amarokapp. -- Amarok 1.3.1 from breezy updates uses all available CPU https://launchpad.net/bugs/23289 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37821] Re: Regular network drops with madwifi
Yes I've worked around this problem magically. I'm trying to figure out what it was that I did to get this to work, and hopefully it will work for a new install of Dapper too. -- Regular network drops with madwifi https://launchpad.net/bugs/37821 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
