[Bug 576289] Re: Jmicorn controller bad names cause installer to crash [PATCH]
I have uploaded a fixed version to my ppa for testing if anyone wants to use it: https://launchpad.net/~danwood76/+archive/ppa-testing -- Jmicorn controller bad names cause installer to crash [PATCH] https://bugs.launchpad.net/bugs/576289 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 554582] Re: Gparted does not list dmraid devices
Hi, Gparted does seem to list the dmraid partitions, but you need to make sure kpartx is installed as it is not a dependency of the gparted package. One issue I have found is to do with the partition naming. When gparted tries to format my devices that end in a letter kpartx has renamed these to XXXp1 and when gparted calls mkfs.ext4 it uses the old partition name of XXX1 so fails miserably. In addition to this the new device name is incompatible with ubiquity as an install fails when you install to a XXXp1 partition. My question is, is it really necessary to use kpartx in gparted. I removed all traces of kpartx from the DMRaid.cc file and built gparted. Gparted now works perfectly on my two dmraid RAID0 volumes, One named jmicron_HD2 and the other isw_bgafaifadd_DATA indicating that kpartx is not required at all. (two different naming formats with two different RAID controllers) I plan to post a bug report soon when I get some more free time. best regards, Danny -- Gparted does not list dmraid devices https://bugs.launchpad.net/bugs/554582 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 543008] Re: Ubiquity can't find the sata hard disk (promise 376 chip)
After erasing the metadata you need to restart your machine so that dmraid is unloaded and the disk is allowed to be sda. So boot with the live CD and erase the metadata, reboot, then install. -- Ubiquity can't find the sata hard disk (promise 376 chip) https://bugs.launchpad.net/bugs/543008 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 580406] Re: Installer resolves dmraid device node incorrectly
I have recently installed Ubuntu 10.04 to my raid drives, during the last page of the installer (page 8) it is necessary to set the advanced options to tell it to install grub to your /dev/mapper device. When I did this at that stage it installed perfectly. It might be that ubiquity has an issue with /dev/mapper devices if you try and change it after this point. Try again setting it on this last page before you start the actual installation. Further information on installation can be found here: https://help.ubuntu.com/community/FakeRaidHowto#Ubuntu 9.10 ( Karmic Koala) Though it may be a little out of date! I assume this is another bug with ubiquity and not dmraid! -- Installer resolves dmraid device node incorrectly https://bugs.launchpad.net/bugs/580406 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 577808] Re: dmraid: jmicron raid not working
*** This bug is a duplicate of bug 576289 *** https://bugs.launchpad.net/bugs/576289 Hi I had this issue and have created a patch available at this bug report: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/576289 ** Also affects: dmraid Importance: Undecided Status: New ** This bug has been marked a duplicate of bug 576289 Jmicorn controller bad names cause installer to crash [PATCH] -- dmraid: jmicron raid not working https://bugs.launchpad.net/bugs/577808 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 576289] Re: Jmicorn controller bad names cause installer to crash [PATCH]
As an update. On loading the live CD I deactivate dmraid and apply my patch and reactivate my raid arrays and the install worked flawlessly. I am very impressed with the dmraid support out of the box (almost). We just need the partitioner in ubiquity to catch up now! -- Jmicorn controller bad names cause installer to crash [PATCH] https://bugs.launchpad.net/bugs/576289 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 576289] [NEW] Jmicorn controller bad names cause installer to crash [PATCH]
Public bug reported: Binary package hint: dmraid Upon trying to install the latest Ubuntu (10.04) I find that my jmicron controller doesn't work again. When installing the installer crashes because the name in the jmicron controller has lots of white space. I would have tested sooner but my busy uni work has left me requiring my machine. I have looked into the dmraid code and realise there is a regression. Although this was present in the previous version also it didn't seem to affect the installer so much. The attached patch fixes the issue by initialising the counter that should have been initialised to start with. If you look at the code the sanitising portion of the jm.c code is never executed resulting in names like: jmicron_HD2 1 which don't seem to be acceptable for the latest installer. My patch causes the sanitiser code to run and the above name is then: jmicron_HD21 as it should be! ** Affects: dmraid (Ubuntu) Importance: Undecided Status: New -- Jmicorn controller bad names cause installer to crash [PATCH] https://bugs.launchpad.net/bugs/576289 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 576289] Re: Jmicorn controller bad names cause installer to crash [PATCH]
** Patch added: jmicron_namefix.patch http://launchpadlibrarian.net/47919576/jmicron_namefix.patch -- Jmicorn controller bad names cause installer to crash [PATCH] https://bugs.launchpad.net/bugs/576289 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 571967] Re: Lucid live-cd broke raid 0 disk array with intel ich10r controller
This is caused by the fact that you have 2 RAID0 volumes on the same disk set. I think this has cropped up before but I can't remember the bug. The normal thing to do is to have an entire RAID0 set and then partition the disk to create your separate portions for your different OS. If you were to create a single RAID0 set and partition that set it would work fine, I think this is what the other guy did in the other bug. Did this setup work in previous Linux installs? -- Lucid live-cd broke raid 0 disk array with intel ich10r controller https://bugs.launchpad.net/bugs/571967 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 509273] Re: [Lucid] Radeon Xpress 200M needs PCI quirk to fix or disable MSI
@Chase Douglas Kernel Versions: da...@danny-laptop:~$ uname -r 2.6.32-21-generic da...@danny-laptop:~$ apt-cache showpkg linux-image Package: linux-image Versions: 2.6.32.21.22 Also I know the patch is active because: da...@danny-laptop:~$ dmesg | grep MSI [0.321055] pci :00:01.0: MSI quirk detected; subordinate MSI disabled I think maybe that something else on my system (other than the graphics bridge) also has issues with bad MSI as I have looked through the kernel source and the pci id added in the quirk.c are correct for my laptop. Should I try to disable MSI for other devices to see if that helps, is there any particular devices I should be looking into or should the current patch disable it for the entire graphics chipset? best regards, Danny -- [Lucid] Radeon Xpress 200M needs PCI quirk to fix or disable MSI https://bugs.launchpad.net/bugs/509273 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 509273] Re: [Lucid] Radeon Xpress 200M needs PCI quirk to fix or disable MSI
For me this bug is not fixed. If I remove the pci=nomsi from the kernel line I get the same crash I did before the kernel update. I assume my PCI IDs haven't been added by the patch. I am running a Toshiba L30-10V. Attached to this is my full lspci. ** Attachment added: lspci.txt http://launchpadlibrarian.net/45297353/lspci.txt -- [Lucid] Radeon Xpress 200M needs PCI quirk to fix or disable MSI https://bugs.launchpad.net/bugs/509273 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 550340] Re: Kernel Panic X200M DRM (xorg-ati driver) unable to handle kernel paging request
I have not noticed this bug re occur since the update to kernel -19 so I assume that something has corrected it. Therefore I am marking it invalid. ** Changed in: linux (Ubuntu) Status: New = Invalid -- Kernel Panic X200M DRM (xorg-ati driver) unable to handle kernel paging request https://bugs.launchpad.net/bugs/550340 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 550340] Re: Kernel Panic X200M DRM (xorg-ati driver) unable to handle kernel paging request
Sorry I meant kernel -18 -- Kernel Panic X200M DRM (xorg-ati driver) unable to handle kernel paging request https://bugs.launchpad.net/bugs/550340 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 550340] [NEW] Kernel Panic X200M DRM (xorg-ati driver) unable to handle kernel paging request
Public bug reported: Crash seems to happen intermittently. System completely locks up with no response from keyboard and mouse, in addition Xorg wont restart when pressing AltGr + SysRq + K although system will reboot using AltGr + SysRq + R E I S U B It appears X is crashing the kernel radeon driver. I believe this might be related to bug #509273 in which the X200M runs out of memory. Although this seems to be mainly fixed passing pci=nomsi to the kernel. ProblemType: KernelOops DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-17-generic 2.6.32-17.26 Regression: Yes Reproducible: No TestedUpstream: No ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-17-generic i686 NonfreeKernelModules: ath_hal AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Annotation: Your system might become unstable now and might need to be restarted. AplayDevices: List of PLAYBACK Hardware Devices card 0: SB [HDA ATI SB], device 0: ALC861-VD Analog [ALC861-VD Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: SB [HDA ATI SB], device 0: ALC861-VD Analog [ALC861-VD Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: danny 1120 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xc040 irq 16' Mixer name : 'Realtek ALC861-VD' Components : 'HDA:10ec0862,1179820d,0011 HDA:11c11040,11790001,00100200' Controls : 18 Simple ctrls : 11 CurrentDmesg: [ 24.736950] ppdev: user-space parallel port driver [ 34.100967] ath0: unknown SIOCSIWAUTH flag 12 [ 35.200033] ath0: no IPv6 routers present [ 876.997032] hda-intel: azx_get_response timeout, switching to polling mode: last cmd=0x001f000a [ 878.000251] hda_intel: azx_get_response timeout, switching to single_cmd mode: last cmd=0x001f000a Date: Sun Mar 28 16:45:22 2010 Failure: oops Frequency: Once a day. HibernationDevice: RESUME=UUID=2654360a-0cc8-42c1-8066-902af4a21dd9 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) Lsusb: Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 15d9:0a33 Dexon Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TOSHIBA Satellite L30 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-17-generic root=UUID=b252a0d2-8e8d-4496-901c-1030b45f1eee ro pci=nomsi quiet splash RelatedPackageVersions: linux-firmware 1.33 RfKill: SourcePackage: linux Title: .974974] BUG: unable to handle kernel paging request at 4268 dmi.bios.date: 10/24/2007 dmi.bios.vendor: TOSHIBA dmi.bios.version: V3.10 dmi.board.name: Satellite L30 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV3.10:bd10/24/2007:svnTOSHIBA:pnSatelliteL30:pvrPSL33E-03H031EN:rvnTOSHIBA:rnSatelliteL30:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite L30 dmi.product.version: PSL33E-03H031EN dmi.sys.vendor: TOSHIBA ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-kerneloops i386 kernel-oops lucid needs-upstream-testing regression-potential -- Kernel Panic X200M DRM (xorg-ati driver) unable to handle kernel paging request https://bugs.launchpad.net/bugs/550340 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 550340] Re: Kernel Panic X200M DRM (xorg-ati driver) unable to handle kernel paging request
** Attachment added: AlsaDevices.txt http://launchpadlibrarian.net/42288044/AlsaDevices.txt ** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/42288045/BootDmesg.txt ** Attachment added: Card0.Amixer.values.txt http://launchpadlibrarian.net/42288046/Card0.Amixer.values.txt ** Attachment added: Card0.Codecs.codec.0.txt http://launchpadlibrarian.net/42288047/Card0.Codecs.codec.0.txt ** Attachment added: Card0.Codecs.codec.1.txt http://launchpadlibrarian.net/42288048/Card0.Codecs.codec.1.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/42288049/Dependencies.txt ** Attachment added: IwConfig.txt http://launchpadlibrarian.net/42288050/IwConfig.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/42288051/Lspci.txt ** Attachment added: OopsText.txt http://launchpadlibrarian.net/42288052/OopsText.txt ** Attachment added: PciMultimedia.txt http://launchpadlibrarian.net/42288053/PciMultimedia.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/42288054/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/42288055/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/42288056/ProcModules.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/42288057/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/42288058/UdevLog.txt ** Attachment added: WifiSyslog.txt http://launchpadlibrarian.net/42288059/WifiSyslog.txt -- Kernel Panic X200M DRM (xorg-ati driver) unable to handle kernel paging request https://bugs.launchpad.net/bugs/550340 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 509273] Re: [Lucid] ATI KMS causes DRM error on X200M
Ok I just had crash after my system had been on for a couple of hours. (first one since adding pci=nomsi) Below is the kernel trace: I notice radeon and drm in the output, is this related to this bug or should I open a new one? Mar 26 21:20:02 danny-laptop kernel: [15086.551703] BUG: unable to handle kernel paging request at 1187 Mar 26 21:20:02 danny-laptop kernel: [15086.551716] IP: [f822bc68] drm_mm_search_free_in_range+0x28/0xe0 [drm] Mar 26 21:20:02 danny-laptop kernel: [15086.551749] *pde = 760b5067 Mar 26 21:20:02 danny-laptop kernel: [15086.551753] Oops: [#1] SMP Mar 26 21:20:02 danny-laptop kernel: [15086.551758] last sysfs file: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT1/charge_full Mar 26 21:20:02 danny-laptop kernel: [15086.551763] Modules linked in: wlan_tkip binfmt_misc ppdev snd_hda_codec_realtek fbcon tileblit font bitblit snd_hda_intel softcursor snd_hda_codec snd_hwdep wlan_scan_sta snd_pcm_oss snd_mixer_oss snd_pcm ath_rate_sample snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi pcmcia joydev ath_pci snd_seq_midi_event radeon ttm drm_kms_helper snd_seq drm i2c_algo_bit yenta_socket snd_timer snd_seq_device snd rsrc_nonstatic soundcore shpchp pcmcia_core snd_page_alloc ati_agp i2c_piix4 agpgart video wlan ath_hal(P) psmouse output serio_raw lp parport usbhid 8139too hid 8139cp mii pata_atiixp sata_sil Mar 26 21:20:02 danny-laptop kernel: [15086.551828] Mar 26 21:20:02 danny-laptop kernel: [15086.551833] Pid: 919, comm: Xorg Tainted: P (2.6.32-17-generic #26-Ubuntu) Satellite L30 Mar 26 21:20:02 danny-laptop kernel: [15086.551837] EIP: 0060:[f822bc68] EFLAGS: 00213293 CPU: 1 Mar 26 21:20:02 danny-laptop kernel: [15086.551849] EIP is at drm_mm_search_free_in_range+0x28/0xe0 [drm] Mar 26 21:20:02 danny-laptop kernel: [15086.551852] EAX: 0001 EBX: 0001 ECX: 1187 EDX: Mar 26 21:20:02 danny-laptop kernel: [15086.551855] ESI: 1187 EDI: 0001 EBP: e6a79ca8 ESP: e6a79c80 Mar 26 21:20:02 danny-laptop kernel: [15086.551859] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 Mar 26 21:20:02 danny-laptop kernel: [15086.551862] Process Xorg (pid: 919, ti=e6a78000 task=e4cf19a0 task.ti=e6a78000) Mar 26 21:20:02 danny-laptop kernel: [15086.551865] Stack: Mar 26 21:20:02 danny-laptop kernel: [15086.551867] db490a80 e3b58500 e6b5c42c 0001 e6a79d58 Mar 26 21:20:02 danny-laptop kernel: [15086.551876] 0 f6809d14 e6a79d28 e6a79cdc f8387579 8000 0001 00285906 Mar 26 21:20:02 danny-laptop kernel: [15086.551885] 0 e6b5c42c 8000 f6a9324c 0002 0001 e6a79d38 Mar 26 21:20:02 danny-laptop kernel: [15086.551895] Call Trace: Mar 26 21:20:02 danny-laptop kernel: [15086.551910] [f8387579] ? ttm_bo_man_get_node+0x79/0xd0 [ttm] Mar 26 21:20:02 danny-laptop kernel: [15086.551917] [f83877c4] ? ttm_bo_mem_space+0x1f4/0x4d0 [ttm] Mar 26 21:20:02 danny-laptop kernel: [15086.551925] [f83865cb] ? ttm_bo_unmap_virtual+0x4b/0x60 [ttm] Mar 26 21:20:02 danny-laptop kernel: [15086.551933] [f838832e] ? ttm_bo_move_buffer+0xae/0x120 [ttm] Mar 26 21:20:02 danny-laptop kernel: [15086.551941] [f8388436] ? ttm_bo_validate+0x96/0x130 [ttm] Mar 26 21:20:02 danny-laptop kernel: [15086.551948] [f838863b] ? ttm_bo_init+0x16b/0x1d0 [ttm] Mar 26 21:20:02 danny-laptop kernel: [15086.551977] [f848b56d] ? radeon_bo_create+0xed/0x1f0 [radeon] -- [Lucid] ATI KMS causes DRM error on X200M https://bugs.launchpad.net/bugs/509273 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 509273] Re: [Lucid] ATI KMS causes DRM error on X200M
With pci=nomsi I have KMS working and no crashing so far. -- [Lucid] ATI KMS causes DRM error on X200M https://bugs.launchpad.net/bugs/509273 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 534743] Re: dmraid causes udev event feedback loop in Karmic
Do you mean Lucid (10.04) and not Karmic (9.10)? -- dmraid causes udev event feedback loop in Karmic https://bugs.launchpad.net/bugs/534743 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 428884] Re: gnome-screensaver-command --poke no longer inhibits screensaver
Applying the patch attached to this bug does fix the issue and I do not see that issue with menus popping up in open office like the other bug. Is it possible to make a dbus call from within gs-monitor.c that stimulates the inhibit correctly? I'm no dbus programmer so I haven't had a go. -- gnome-screensaver-command --poke no longer inhibits screensaver https://bugs.launchpad.net/bugs/428884 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 449876] Re: raid degraded after update to Karmic beta
It hides them so that you cannot accidentally destroy your RAID array when installing with Ubiquity or using the system in general. -- raid degraded after update to Karmic beta https://bugs.launchpad.net/bugs/449876 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 454297] Re: drag and drop images or video into subfolder will prevent folder from loading
Tom the bug is in Nautilus so I would expect it to work in dolphin! I have not noticed this since updating to the fixed nautilus package. -- drag and drop images or video into subfolder will prevent folder from loading https://bugs.launchpad.net/bugs/454297 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 490672] Re: prior mdadm raid setup not seen correctly (need 'nodmraid' kernel option)
*** This bug is a duplicate of bug 489826 *** https://bugs.launchpad.net/bugs/489826 ** This bug has been marked a duplicate of bug 489826 Raid falsely detected on upgrade to Karmic. Results in unbootable machine. -- prior mdadm raid setup not seen correctly (need 'nodmraid' kernel option) https://bugs.launchpad.net/bugs/490672 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 489826] Re: Raid falsely detected on upgrade to Karmic. Results in unbootable machine.
Dmraid is already installed it doesn't install once the system loads. If it detects metadata the libs load and disable the block devices. There isn't much of a way to detect automagically if partitions are being used as people might want to use a blank set of disks and setup partitions. The thing to do is delete the metadata from your disks if you don't use dmraid and you wont get the issue. -- Raid falsely detected on upgrade to Karmic. Results in unbootable machine. https://bugs.launchpad.net/bugs/489826 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 449876] Re: raid degraded after update to Karmic beta
There will not be a patch to dmraid as this is not really a bug. This has been discussed before. The issue is that you haven't removed the raid metadata when you destroyed the array. Normally you can remove these without issue using dmraid -E as the metadata is usually in a region of the disk that you cannot access anyhow. Also its worth going through the BIOS route to see if you can delete the array first, you may need to enable the onboard RAID to get into the nvidia / intel / whatever control panel to do it. This way dmraid wont delete anything that might be useful. -- raid degraded after update to Karmic beta https://bugs.launchpad.net/bugs/449876 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 449876] Re: raid degraded after update to Karmic beta
It's because dmraid now hides the root devices of a RAID set. This was implemented to fix a whole host of issues with block devices and udev. Also it makes the whole dmraid system a lot better. This is why you are getting issues but your issues are caused because you have the RAID metadata on your disks. Just purge the metadata and you wont get dmraid hiding your block devs anymore. The data you loose is in the last blocks on the disk and will not be used by anything, the fact that dmraid can detect the data there means it can delete it. -- raid degraded after update to Karmic beta https://bugs.launchpad.net/bugs/449876 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 383927] Re: endless loading in nautilus / some files missing
*** This bug is a duplicate of bug 454297 *** https://bugs.launchpad.net/bugs/454297 You have to kill nautilus all together. If the process is still running (it renders the desktop folders too) the bug remains so I assume it has something to do with nautilus caching. Run system monitor and kill the nautilus processes to repair the issue temporarily. -- endless loading in nautilus / some files missing https://bugs.launchpad.net/bugs/383927 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 383927] Re: endless loading in nautilus / some files missing
*** This bug is a duplicate of bug 454297 *** https://bugs.launchpad.net/bugs/454297 Ok so I looked at 454297 and it is a dupe so marking as such! ** This bug has been marked a duplicate of bug 454297 drag and drop images or video into subfolder will prevent folder from loading -- endless loading in nautilus / some files missing https://bugs.launchpad.net/bugs/383927 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 383927] Re: endless loading in nautilus / some files missing
I also get this. It happens after moving files for me but not always. As louisantoine has said completely closing nautilus (I use killall nautilus) and restarting it fixes the issue but it is very annoying if you have several folders open. This is also Ubuntu 9.10 x64 -- endless loading in nautilus / some files missing https://bugs.launchpad.net/bugs/383927 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 156085] Re: Could not open /proc/bus/usb/devices
Your problem sounds more like a bug in VMware and as it is a paid product I would ask them about it. It sounds like VMware is not passing the USB devices on. -- Could not open /proc/bus/usb/devices https://bugs.launchpad.net/bugs/156085 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 156085] Re: Could not open /proc/bus/usb/devices
Your problem sounds more like a bug in VMware and as it is a paid product I would ask them about it. It sounds like VMware is not passing the USB devices on. -- Could not open /proc/bus/usb/devices https://bugs.launchpad.net/bugs/156085 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 472681] Re: Samba returns NT_STATUS_NOT_SUPPORTED when trying to view list of shares
https://help.ubuntu.com/community/Repositories/CommandLine Just add this line to the bottom of the /etc/apt/sources.list file: deb http://gb.archive.ubuntu.com/ubuntu/ karmic-proposed main multiverse universe sudo nano /etc/apt/sources.list scroll to the bottom and add this line. save and exit sudo apt-get update sudo apt-get install samba libsmbclient then you probably want to remove that line again afterwards as some of the updates have the possibility to break your system in that repo. -- Samba returns NT_STATUS_NOT_SUPPORTED when trying to view list of shares https://bugs.launchpad.net/bugs/472681 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 472681] Re: Samba returns NT_STATUS_NOT_SUPPORTED when trying to view list of shares
https://help.ubuntu.com/community/Repositories/CommandLine Just add this line to the bottom of the /etc/apt/sources.list file: deb http://gb.archive.ubuntu.com/ubuntu/ karmic-proposed main multiverse universe sudo nano /etc/apt/sources.list scroll to the bottom and add this line. save and exit sudo apt-get update sudo apt-get install samba libsmbclient then you probably want to remove that line again afterwards as some of the updates have the possibility to break your system in that repo. -- Samba returns NT_STATUS_NOT_SUPPORTED when trying to view list of shares https://bugs.launchpad.net/bugs/472681 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 472681] Re: Samba returns NT_STATUS_NOT_SUPPORTED when trying to view list of shares
You have to enable the proposed updates but I would only update the samba packages though through synaptic. The package will get pushed into main soon though if you can be patient. -- Samba returns NT_STATUS_NOT_SUPPORTED when trying to view list of shares https://bugs.launchpad.net/bugs/472681 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 472681] Re: Samba returns NT_STATUS_NOT_SUPPORTED when trying to view list of shares
You have to enable the proposed updates but I would only update the samba packages though through synaptic. The package will get pushed into main soon though if you can be patient. -- Samba returns NT_STATUS_NOT_SUPPORTED when trying to view list of shares https://bugs.launchpad.net/bugs/472681 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 472681] Re: Samba returns NT_STATUS_NOT_SUPPORTED when trying to view list of shares
Wow, that was very fast. Was this a package already in the system? I can confirm that the package in proposed fixes the issue in both smbclient and in nautilus browsing. Good work, I have attached the output of the smbclient command so you can compare if you like. ** Attachment added: smbclient-karmic.log http://launchpadlibrarian.net/35198258/smbclient-karmic.log -- Samba returns NT_STATUS_NOT_SUPPORTED when trying to view list of shares https://bugs.launchpad.net/bugs/472681 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 472681] Re: Samba returns NT_STATUS_NOT_SUPPORTED when trying to view list of shares
Wow, that was very fast. Was this a package already in the system? I can confirm that the package in proposed fixes the issue in both smbclient and in nautilus browsing. Good work, I have attached the output of the smbclient command so you can compare if you like. ** Attachment added: smbclient-karmic.log http://launchpadlibrarian.net/35198258/smbclient-karmic.log -- Samba returns NT_STATUS_NOT_SUPPORTED when trying to view list of shares https://bugs.launchpad.net/bugs/472681 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 287751] Re: [Intrepid] dmraid 5 error: raid4-5 not in kernel
These bugs are addressed in jaunty (no more messages or raw devices) so upgrade if the messages really bother you. I dont believe any harm is caused by the kernel trying to access the raw devices but it is possible I suppose. This bug has been fixed and is closed. -- [Intrepid] dmraid 5 error: raid4-5 not in kernel https://bugs.launchpad.net/bugs/287751 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 392136] Re: package grub-pc 1.96+20080724-12ubuntu2 failed to install on dmraid (fakeraid) no mapping exists
** Changed in: grub2 (Ubuntu) Status: Incomplete = Confirmed -- package grub-pc 1.96+20080724-12ubuntu2 failed to install on dmraid (fakeraid) no mapping exists https://bugs.launchpad.net/bugs/392136 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 420015] Re: usblp Kernel module needs to be removed and /dev/bus/usb/*/* made accessible for USB printers to work with CUPS 1.4.x
Im sorry but this is not fixed. To make my printer work I have to run this each boot: sudo aa-enforce cupsd Some of the commands gave useless or no info but the ones that might be useful: My printer wasn't visible with the lsusb commands like it used to be and these were run after the above command was run. lpinfo -v serial serial:/dev/ttyS0?baud=115200 serial serial:/dev/ttyS1?baud=115200 direct scsi network lpd network ipp network beh network socket network http network smb direct hp direct hpfax direct usb://Samsung/ML-1210?serial=? device for Samsung-ML-1210: usb://Samsung/ML-1210?serial=? -- usblp Kernel module needs to be removed and /dev/bus/usb/*/* made accessible for USB printers to work with CUPS 1.4.x https://bugs.launchpad.net/bugs/420015 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 382941] Re: iPod not recognized by podsleuth
I have just been enraged by this problem also. It seems that podsleuth uses HAL to detect ipods and as HAL has been chucked for devicekit then this occurs. If you run 'podsleuth --rescan --debug' you get an exception stating that it cannot find org.freedesktop.hal. So yes its related to the removal of HAL, shame. -- iPod not recognized by podsleuth https://bugs.launchpad.net/bugs/382941 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 415588] Re: Found an iPod device, but it is not known by PodSleuth:
*** This bug is a duplicate of bug 382941 *** https://bugs.launchpad.net/bugs/382941 ** This bug has been marked a duplicate of bug 382941 iPod not recognized by podsleuth -- Found an iPod device, but it is not known by PodSleuth: https://bugs.launchpad.net/bugs/415588 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 397892] Re: Screensaver does not turn on [Ubuntu/Xubuntu Karmic]
I am also having this issue, neither gnome-power-manager nor the gnome-screensaver will activate as X seems to not be idle. I cant remember it not working until recently when I came home from work to see my PC awake and burning in my monitor. The computer seems to try to sleep but gnome-power-manager reports X as not idle and wakes the system back up. Also activating the screensaver using the command posted above activates the screensaver and manually putting the display into sleep by DPMS works also. I am reopening this bug on that basis. ** Changed in: gnome-screensaver (Ubuntu) Status: Fix Released = Confirmed -- Screensaver does not turn on [Ubuntu/Xubuntu Karmic] https://bugs.launchpad.net/bugs/397892 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 397892] Re: Screensaver does not turn on [Ubuntu/Xubuntu Karmic]
** Changed in: gnome-screensaver (Ubuntu) Status: Confirmed = Fix Released -- Screensaver does not turn on [Ubuntu/Xubuntu Karmic] https://bugs.launchpad.net/bugs/397892 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 346425] Re: Kubuntu install fails to detect software (fake) Intel Matrix RAID0 SSD volume on Alienware M17 laptop
The bootloader I am using on my RAID0 is grub v1, this is called just grub in synaptic and not grub-common, grub2, grub-pc. I had to install it seperatly once ubiquity had crashed which is a bit of a pain. You may need to install dmraid and activate manually although there could be bugs in the alpha 5 version of dmraid, this is the alpha testing stage after all! -- Kubuntu install fails to detect software (fake) Intel Matrix RAID0 SSD volume on Alienware M17 laptop https://bugs.launchpad.net/bugs/346425 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 346425] Re: Kubuntu install fails to detect software (fake) Intel Matrix RAID0 SSD volume on Alienware M17 laptop
Ubiquity does tend to crash when trying to install grub. And also grub2 doesnt work with dmraid yet. The alternate CD is still the best way for DMRAID installs so it would be nice if you could try that. -- Kubuntu install fails to detect software (fake) Intel Matrix RAID0 SSD volume on Alienware M17 laptop https://bugs.launchpad.net/bugs/346425 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 348353] Re: Pulse Audio no longer works with alsa a52 plugin (Ubuntu 9.04 Jaunty)
It is not repeatable in a live environment and I have no idea why it should be? Ubuntu doesn't ship with the A52 plugin by default as there are some patent issues I think. However this is compilable from the source available from the repos. Luke Yelavich has also reported this bug upstream and it appears to be to do with the Alsa plugin itself so this bug should be confirmed. ** Changed in: pulseaudio (Ubuntu) Status: Incomplete = Confirmed -- Pulse Audio no longer works with alsa a52 plugin (Ubuntu 9.04 Jaunty) https://bugs.launchpad.net/bugs/348353 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 346425] Re: Kubuntu install fails to detect software (fake) Intel Matrix RAID0 SSD volume on Alienware M17 laptop
Is this bug still around with the release of Jaunty and with the test of karmic? -- Kubuntu install fails to detect software (fake) Intel Matrix RAID0 SSD volume on Alienware M17 laptop https://bugs.launchpad.net/bugs/346425 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 396078] Re: More on RAID 1 issues (RAID1 + DMRAID) = No boot possible
Is the bug still there with the latest kernel and dmraid package? -- More on RAID 1 issues (RAID1 + DMRAID) = No boot possible https://bugs.launchpad.net/bugs/396078 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 420216] Re: CUPS 1.4.0, jobs stall in processing...
*** This bug is a duplicate of bug 420015 *** https://bugs.launchpad.net/bugs/420015 ** This bug has been marked a duplicate of bug 420015 usblp Kernel module needs to be removed and /dev/bus/usb/*/* made accessible for USB printers to work with CUPS 1.4.x -- CUPS 1.4.0, jobs stall in processing... https://bugs.launchpad.net/bugs/420216 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 247027] Re: initramfs prompts because of dmraid
*** This bug is a duplicate of bug 315735 *** https://bugs.launchpad.net/bugs/315735 This bug is fixed. Please read the description and if you still have a bug report a new one. -- initramfs prompts because of dmraid https://bugs.launchpad.net/bugs/247027 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 348353] Re: Pulse Audio no longer works with alsa a52 plugin (Ubuntu 9.04 Jaunty)
Ok so this has resurfaced in Karmic. Attached is a pulseaudio -vvv output when the crash happens. ** Attachment added: pulse_a52_crash.txt http://launchpadlibrarian.net/30829644/pulse_a52_crash.txt -- Pulse Audio no longer works with alsa a52 plugin (Ubuntu 9.04 Jaunty) https://bugs.launchpad.net/bugs/348353 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 415280] Re: Mishandling of error messages in /usr/share/initramfs-tools/scripts/local-top/dmraid
*** This bug is a duplicate of bug 376792 *** https://bugs.launchpad.net/bugs/376792 ** This bug has been marked a duplicate of bug 376792 dmraid not activating on boot -- Mishandling of error messages in /usr/share/initramfs-tools/scripts/local-top/dmraid https://bugs.launchpad.net/bugs/415280 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 395336] Re: ICH9: Not all partitions could be discovered
Bug with the microsoft partitioner as opposed to dmraid. Do they have launchpad? ** Changed in: dmraid (Ubuntu) Status: New = Invalid -- ICH9: Not all partitions could be discovered https://bugs.launchpad.net/bugs/395336 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 407901] Re: Raid not activated at boot
What your physical setup for the RAID? (RAID0,1,5, etc.) If it is a RAID5 there is a bug related to a typo of which a patch has been created. -- Raid not activated at boot https://bugs.launchpad.net/bugs/407901 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 403733] Re: After executing DMRAID and turn off PC - Offline Member on next boot
*** This bug is a duplicate of bug 219393 *** https://bugs.launchpad.net/bugs/219393 Sorry my mistake, I read the other bug reports and just assumed them to be correct. Either way this is a HPA issue and a dupe of the assigned bug. Read this bug for infos about the HPA in the latest kernels: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/380138 -- After executing DMRAID and turn off PC - Offline Member on next boot https://bugs.launchpad.net/bugs/403733 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 403733] Re: After executing DMRAID and turn off PC - Offline Member on next boot
*** This bug is a duplicate of bug 219393 *** https://bugs.launchpad.net/bugs/219393 This is a known issue: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/219393 I think it is also the cause for your other bug. It is the HPA bug. ** This bug has been marked a duplicate of bug 219393 HPA ( Host Protected Area ) interferes with dmraid -- After executing DMRAID and turn off PC - Offline Member on next boot https://bugs.launchpad.net/bugs/403733 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 403733] Re: After executing DMRAID and turn off PC - Offline Member on next boot
*** This bug is a duplicate of bug 219393 *** https://bugs.launchpad.net/bugs/219393 Oh and by the way your kernel command line options are wrong. It should be libata.ignore_hpa=0 note the . between libata and ignore! -- After executing DMRAID and turn off PC - Offline Member on next boot https://bugs.launchpad.net/bugs/403733 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 401713] Re: DMRAID only detect first subset on Intel ICH10R
When you wiped the disk and created the single array could you post the output of the above debug command for us. (sudo dmraid -ay -ddd -vvv) Its a bit annoying trying to debug something when you don't give the full debug output as you go. -- DMRAID only detect first subset on Intel ICH10R https://bugs.launchpad.net/bugs/401713 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 401713] Re: DMRAID only detect first subset on Intel ICH10R
Also could you try installing Ubuntu 9.04 (Jaunty) with the two array setup. It would be interesting to know weather this issue is visible in the stable release. -- DMRAID only detect first subset on Intel ICH10R https://bugs.launchpad.net/bugs/401713 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 401713] Re: DMRAID only detect first subset on Intel ICH10R
When you get to the stage of cannot be activated post the debug output for comparison. sudo dmraid -ay -ddd -vvv -- DMRAID only detect first subset on Intel ICH10R https://bugs.launchpad.net/bugs/401713 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 372170] Re: host protected area prevents detection of isw (intel matrix storage manager) raid arrays
EagleDM your issue is not to do with this bug so please file a new one and include as much detail as possible. -- host protected area prevents detection of isw (intel matrix storage manager) raid arrays https://bugs.launchpad.net/bugs/372170 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 401713] Re: DMRAID only detect first subset on Intel ICH10R
When you say you create 2 arrays why are you not creating 1 array and partitioning it? Could you post the output of 'sudo dmraid -ay -ddd -vvv' which will give a detailed version of whats going on. regards, Danny -- DMRAID only detect first subset on Intel ICH10R https://bugs.launchpad.net/bugs/401713 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 392510] Re: Dual-boot install using mdadm root fails to boot
What you have to understand is that DMRAID is just a driver for the bios raid setups. When you create a RAID from the BIOS it does a RAID1 or whatever on the entire array using all the drives you select. You cant do a partial bios raid setup as this is illogical. When you use mdadm to create a RAID on a BIOS RAID without dmraid you are effectivly corrupting the bios' RAID array as mdadm will alter the drives that the BIOS has assigned to that array. It is much simpler to just use dmraid instead of mdadm, it will gather the raid setup from the bios without you having to do anything. -- Dual-boot install using mdadm root fails to boot https://bugs.launchpad.net/bugs/392510 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 392510] Re: Dual-boot install using mdadm root fails to boot
That wiki page is a little old: https://wiki.ubuntu.com/DmraidSupport Ubuntu must support it if its in the installer CD and in the main repos so I'm unsure if that is just outdated like most of the online documentation. I have been using dmraid (and bios raid) for years and have had no issues so I consider it very stable and usable. I'm not sure how dangerous your setup is. It may work for you but someone with a different style of BIOS RAID controller may get issues if it stores metadata in special places which will mess with mdadm. Or worse if mdadm accidentally overwrites metedata for the bios raid and you loose the entire array. -- Dual-boot install using mdadm root fails to boot https://bugs.launchpad.net/bugs/392510 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 396078] Re: More on RAID 1 issues (RAID1 + DMRAID) = No boot possible
For starters it looks like you hjave used sdc in a silicon image and nvidia RAID array. If the array boots upto GDM (I assume you are booting off the array entirely) then dmraid is active and something else is borking your system. Is it possible for you to completely reformat the drives and start afresh with a clean install? can you post the output of: sudo dmraid -vvv -ddd -ay -- More on RAID 1 issues (RAID1 + DMRAID) = No boot possible https://bugs.launchpad.net/bugs/396078 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 395336] Re: ICH9: Not all partitions could be discovered
Looking at both outputs the issue is obvious. Somehow you have partitioned the extended partition larger than the disk, and this is both the physical disk size and the calculated dmraid disk size. Notice that your extended partion ends 36482 and the disk size is only 36481? To fix this you should resize partition 7 and then the extended parition to actually fit in the drive. I have noticed odd things like this before when formatting from inside vista (their partitioning tool sucks), in this case it seems to have rounded the cylinder count up instead of down and you end up with a partition off the end of the disk. actual cylinder count: 300069052416 / 16065 / 512 = 36481.318 or 36481 not 36482 -- ICH9: Not all partitions could be discovered https://bugs.launchpad.net/bugs/395336 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 395336] Re: ICH9: Not all partitions could be discovered
The original bug you speak of was mine. Basically it had to do with calculating the sector count but I assumed this was only for RAID0 as I don't believe RAID1 is recalculated. Can you post the following commands please: sudo fdisk -l /dev/mapper/isw_dbbdjdbeie_Volume_0 sudo fdisk -l /dev/sdb That will list the partitions but also the sector count. I know you provided the last one but its good to have them both taken at the same time. -- ICH9: Not all partitions could be discovered https://bugs.launchpad.net/bugs/395336 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 392510] Re: Dual-boot install using mdadm root fails to boot
A conf file might be a nice workaround and should keep everyone happy. So I would vote option 2 although support would still be fairly limited. -- Dual-boot install using mdadm root fails to boot https://bugs.launchpad.net/bugs/392510 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 381514] Re: Jaunty not Booting with dmraid Active
*** This bug is a duplicate of bug 376792 *** https://bugs.launchpad.net/bugs/376792 ** This bug has been marked a duplicate of bug 376792 dmraid not activating on boot ** Changed in: dmraid (Ubuntu) Status: New = Incomplete -- Jaunty not Booting with dmraid Active https://bugs.launchpad.net/bugs/381514 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 373520] Re: dmraid 1.0.0.rc15-6ubuntu2 amd64 + NVRAID boot fails
From the livecd Ubiquity crashes. You have to install dmraid and grub to the chroot environment (you can follow the fakeraid howto from the grub install bit) The proper way to install using dmraid is through the alternate CD. -- dmraid 1.0.0.rc15-6ubuntu2 amd64 + NVRAID boot fails https://bugs.launchpad.net/bugs/373520 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 294938] Re: dmraid activates nvidia Fakeraid with missing disk
John this is not a forum. It looks as though you have not built the array properly with the BIOS utility. Also you could have formatted the /dev/sdb to something else and erased the metadata. Try rebuilding the array and repartitioning. -- dmraid activates nvidia Fakeraid with missing disk https://bugs.launchpad.net/bugs/294938 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 294938] Re: dmraid activates nvidia Fakeraid with missing disk
Ah right may I point you to this bug: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/372170 and also: https://bugs.launchpad.net/bugs/219393 It could be to do with the HPA, there is a workaround in those bug reports: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/219393/comments/30 -- dmraid activates nvidia Fakeraid with missing disk https://bugs.launchpad.net/bugs/294938 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 315735] Re: FakeRAID fails with kernel 2.6.28
The original bug was squashed and was due to issues upstream. If you haven't updated your packages then this will be the problem. Also you will need to make sure you are using the latest kernel after the package update. Please start a new bug and provide as much detail as possible as this bug is closed. -- FakeRAID fails with kernel 2.6.28 https://bugs.launchpad.net/bugs/315735 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 392510] Re: Dual-boot install using mdadm root fails to boot
After you apt-get remove you must rebuild the initramfs (sudo update- initramfs -u -k all), as described in my post. From your post it sounds like the uninstall from apt will remove the initramfs hooks just not rebuild the array. As luke said you have one or the other, there is no advantage of using both types on one drive. -- Dual-boot install using mdadm root fails to boot https://bugs.launchpad.net/bugs/392510 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 356503] Re: [patch] Ubuntu Jaunty 9.04 dmraid fails with Kernel 2.6.28
** Changed in: dmraid (Ubuntu) Status: Confirmed = In Progress -- [patch] Ubuntu Jaunty 9.04 dmraid fails with Kernel 2.6.28 https://bugs.launchpad.net/bugs/356503 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 392510] Re: Dual-boot install using mdadm root fails to boot
After reading the bug more deeply Giuseppe states that it does invoke the update-initramfs but only on the latest kernel. The thing I dont understand is why you would want to use mdadm and dmraid together, each provides the same functionality although dmraid allows you to boot off of RAIDs other than RAID1. Mdadm and Dmraid can only cause issues when used together as they are both fighting to do the same thing. I'm fairly sure on my last install from the livecd I had to install dmraid seperately to starting ubiquity, mind you it may just be that ubiquity installs it anyway and I was being inpatient. -- Dual-boot install using mdadm root fails to boot https://bugs.launchpad.net/bugs/392510 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 392510] Re: Dual-boot install using mdadm root fails to boot
To get rid of dmraid you just don't install it. The live cd doesn't have the dmraid package preloaded and I'm sure getting rid of dmraid is as simple as un-installing it through apt and rebuilding the initramfs. (2 commands from the terminal) This is no bug in dmraid. -- Dual-boot install using mdadm root fails to boot https://bugs.launchpad.net/bugs/392510 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 392510] Re: Dual-boot install using mdadm root fails to boot
Also you could purge the fakeraid from the drives by clearing the metadata at the end of the disks and then dmraid wouldn't even load. -- Dual-boot install using mdadm root fails to boot https://bugs.launchpad.net/bugs/392510 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 356503] Re: Kubuntu Jaunty 9.04 dmraid fails with Kernel 2.6.28
I have looked through the hooks and I can see there is a typo in the dmraid hook file. Open up /usr/share/initramfs-tools/hooks/dmraid, so: sudo gedit /usr/share/initramfs-tools/hooks/dmraid look through that file, on line 23 it says force_load dm-raid45. This should of course be dm-raid4-5. So if you change that to dm-raid4-5 then save it and update the initramfs with the above command it should work. The rc14 version uses dm-raid4-5. I am attaching a patch which will hopefully get uploaded upstream. ** Attachment added: 17-fix_raid4-5_initramfs.patch http://launchpadlibrarian.net/28233395/17-fix_raid4-5_initramfs.patch ** Changed in: dmraid (Ubuntu) Status: Incomplete = Confirmed -- Kubuntu Jaunty 9.04 dmraid fails with Kernel 2.6.28 https://bugs.launchpad.net/bugs/356503 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 356503] Re: Kubuntu Jaunty 9.04 dmraid fails with Kernel 2.6.28
I will post the updated patch when I get homw from work. kind regards, Danny -- Kubuntu Jaunty 9.04 dmraid fails with Kernel 2.6.28 https://bugs.launchpad.net/bugs/356503 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 356503] Re: Kubuntu Jaunty 9.04 dmraid fails with Kernel 2.6.28
You shouldnt be running fsck on the individual drives within an array but on the devices created by the raid sets. dmraid devices are in /dev/mapper -- Kubuntu Jaunty 9.04 dmraid fails with Kernel 2.6.28 https://bugs.launchpad.net/bugs/356503 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 356503] Re: Kubuntu Jaunty 9.04 dmraid fails with Kernel 2.6.28
Is fsck being invoked by the kernel during boot when you get this error? If so it could be in your fstab possibly, I dont have a RAID1 array so I'm unsure if the UUIDs end up being the same for the array and the actual disks. This could be resolved by replcing UUIDs. I dont believe this has anything to do with this bug. -- Kubuntu Jaunty 9.04 dmraid fails with Kernel 2.6.28 https://bugs.launchpad.net/bugs/356503 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 356503] Re: Kubuntu Jaunty 9.04 dmraid fails with Kernel 2.6.28
Ok here is the debdiff for the two patches. ** Attachment added: dmraid_1.0.0.rc15-6ubuntu3.debdiff http://launchpadlibrarian.net/28253322/dmraid_1.0.0.rc15-6ubuntu3.debdiff ** Changed in: dmraid (Ubuntu) Status: Confirmed = Fix Released -- Kubuntu Jaunty 9.04 dmraid fails with Kernel 2.6.28 https://bugs.launchpad.net/bugs/356503 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 356503] Re: [patch] Ubuntu Jaunty 9.04 dmraid fails with Kernel 2.6.28
** Summary changed: - [patch] Kubuntu Jaunty 9.04 dmraid fails with Kernel 2.6.28 + [patch] Ubuntu Jaunty 9.04 dmraid fails with Kernel 2.6.28 ** Description changed: + When booting off of a fake-raid RAID5 drive boot fails due to the dm-raid4-5 module not being loaded before the device activation takes place. + This is due to a small typo in the dmraid initialization script and the initramfs hook script. + + The patch (and fix) simply changes the two occurrences of 'dm-raid45' to + 'dm-raid4-5' which then allows the module to be loaded and boot/raid + initialization to take place. + + The bug can be reproduced using a BIOS RAID5 setup, this is obviously + quite hard to simulate from a testing point of view unless you already + have this setup. + + This bug is a regression from the previous release which used dmraid-1.0.0.rc14 and had the module name spelt correctly. + The debdiff patch attached to this bug report changes the package version number from dmraid-1.0.0.rc15-6ubuntu2 to dmraid-1.0.0.rc15-6ubuntu2 + + --- + + Original Bug report: + When trying to activate my dmraid with Jaunty I get the following from dmraid -ay RAID set nvidia_iicejhch already active ERROR: dos: reading /dev/mapper/nvidia_iicejhch[No such file or directory] However in /dev/mapper the path does exist here is my output of ls /dev/mapper control nvidia_iicejhch As per the instructions sent to me from bug 315735 here is my output of dmraid -ay -vvv -d WARN: locking /var/lock/dmraid/.lock NOTICE: skipping removable device /dev/sdg NOTICE: /dev/sdf: asr discovering NOTICE: /dev/sdf: ddf1discovering NOTICE: /dev/sdf: hpt37x discovering NOTICE: /dev/sdf: hpt45x discovering NOTICE: /dev/sdf: isw discovering NOTICE: /dev/sdf: jmicron discovering NOTICE: /dev/sdf: lsi discovering NOTICE: /dev/sdf: nvidia discovering NOTICE: /dev/sdf: pdc discovering NOTICE: /dev/sdf: sil discovering NOTICE: /dev/sdf: via discovering NOTICE: /dev/sde: asr discovering NOTICE: /dev/sde: ddf1discovering NOTICE: /dev/sde: hpt37x discovering NOTICE: /dev/sde: hpt45x discovering NOTICE: /dev/sde: isw discovering NOTICE: /dev/sde: jmicron discovering NOTICE: /dev/sde: lsi discovering NOTICE: /dev/sde: nvidia discovering NOTICE: /dev/sde: pdc discovering NOTICE: /dev/sde: sil discovering NOTICE: /dev/sde: via discovering NOTICE: /dev/sdd: asr discovering NOTICE: /dev/sdd: ddf1discovering NOTICE: /dev/sdd: hpt37x discovering NOTICE: /dev/sdd: hpt45x discovering NOTICE: /dev/sdd: isw discovering NOTICE: /dev/sdd: jmicron discovering NOTICE: /dev/sdd: lsi discovering NOTICE: /dev/sdd: nvidia discovering NOTICE: /dev/sdd: nvidia metadata discovered NOTICE: /dev/sdd: pdc discovering NOTICE: /dev/sdd: sil discovering NOTICE: /dev/sdd: via discovering NOTICE: /dev/sdc: asr discovering NOTICE: /dev/sdc: ddf1discovering NOTICE: /dev/sdc: hpt37x discovering NOTICE: /dev/sdc: hpt45x discovering NOTICE: /dev/sdc: isw discovering NOTICE: /dev/sdc: jmicron discovering NOTICE: /dev/sdc: lsi discovering NOTICE: /dev/sdc: nvidia discovering NOTICE: /dev/sdc: nvidia metadata discovered NOTICE: /dev/sdc: pdc discovering NOTICE: /dev/sdc: sil discovering NOTICE: /dev/sdc: via discovering NOTICE: /dev/sdb: asr discovering NOTICE: /dev/sdb: ddf1discovering NOTICE: /dev/sdb: hpt37x discovering NOTICE: /dev/sdb: hpt45x discovering NOTICE: /dev/sdb: isw discovering NOTICE: /dev/sdb: jmicron discovering NOTICE: /dev/sdb: lsi discovering NOTICE: /dev/sdb: nvidia discovering NOTICE: /dev/sdb: nvidia metadata discovered NOTICE: /dev/sdb: pdc discovering NOTICE: /dev/sdb: sil discovering NOTICE: /dev/sdb: via discovering NOTICE: /dev/sda: asr discovering NOTICE: /dev/sda: ddf1discovering NOTICE: /dev/sda: hpt37x discovering NOTICE: /dev/sda: hpt45x discovering NOTICE: /dev/sda: isw discovering NOTICE: /dev/sda: jmicron discovering NOTICE: /dev/sda: lsi discovering NOTICE: /dev/sda: nvidia discovering NOTICE: /dev/sda: nvidia metadata discovered NOTICE: /dev/sda: pdc discovering
[Bug 356503] Re: [patch] Ubuntu Jaunty 9.04 dmraid fails with Kernel 2.6.28
I don't actually suffer from this bug (dont use RAID5), it was a mere observation due to interest. So I cannot test in either. -- [patch] Ubuntu Jaunty 9.04 dmraid fails with Kernel 2.6.28 https://bugs.launchpad.net/bugs/356503 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 356503] Re: Kubuntu Jaunty 9.04 dmraid fails with Kernel 2.6.28
Have you tried adding dm-raid4-5 to /etc/initramfs-tools/modules and then rebuilding the initramfs? (sudo update-initramfs -u -k all) -- Kubuntu Jaunty 9.04 dmraid fails with Kernel 2.6.28 https://bugs.launchpad.net/bugs/356503 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 373520] Re: dmraid 1.0.0.rc15-6ubuntu2 amd64 + NVRAID boot fails
Once you install its necessary to install the package using a chroot style environment. And make sure you update the initramfs after you install. (sudo update-initramfs -u -k all) -- dmraid 1.0.0.rc15-6ubuntu2 amd64 + NVRAID boot fails https://bugs.launchpad.net/bugs/373520 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 367553] Re: Raid is not activated automatically
Well you could download the karmic .deb files and install them manually for now: http://launchpadlibrarian.net/26333192/libdmraid1.0.0.rc15_1.0.0.rc15-7ubuntu1_i386.deb http://launchpadlibrarian.net/26333189/dmraid_1.0.0.rc15-7ubuntu1_i386.deb They _should_ install fine as I dont think the dependencies have changed. It will update to the repo version when it is available. Also you need to enable the backports repo. -- Raid is not activated automatically https://bugs.launchpad.net/bugs/367553 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 315735] Re: FakeRAID fails with kernel 2.6.28
The original bug has been fixed and cleared. Please start a new bug with relevant info (chipset, debug logs, extra infos). Jaunty's dmraid works with both my jmicron and intel fakeraid controllers. -- FakeRAID fails with kernel 2.6.28 https://bugs.launchpad.net/bugs/315735 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 376792] Re: dmraid not activating on boot
*** This bug is a duplicate of bug 367553 *** https://bugs.launchpad.net/bugs/367553 ** This bug has been marked a duplicate of bug 367553 Raid is not activated automatically -- dmraid not activating on boot https://bugs.launchpad.net/bugs/376792 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 372170] Re: intel isw raid metadata at odd offset
This isnt the HPA bug. This is actually the metadata being moved to a different location so dmraid cant find it. -- intel isw raid metadata at odd offset https://bugs.launchpad.net/bugs/372170 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 372170] Re: intel isw raid metadata at odd offset
Robert Collins wrote: On Sat, 2009-05-09 at 10:57 +, danwood76 wrote: You could do a probe for the ICH10 tag for now. That would probably be safer than guessing a dereference, then we need some more ICH10R based people to test which will take time. You could try building another RAID set with a couple of other disks and see if the meta is in the same place on those disks also. I think the ICH10 tag is actually a serial or some such; its at an odd spot there. What do you think of treating GAFR as a magic bytes, then using the sector offset following that? As long as the final location is checked for still being 0 we won't try to read negative offsets, and the followup is_isw call will fail on non-isw environments. It seems pretty safe to me to assume that: find GAFR follow a word sector offset find a 10 byte isw signature is only going to occur when someone actually has a ICH environment. re testing: I don't have any disks I can wipe I'm sorry. -Rob Sounds good, if someone else with ICH10 can test it would be great. Write a patch based on your idea and I will test it to verify it still works with ICH8 also but I obviously cannot test the ICH10. regards, Dnany -- intel isw raid metadata at odd offset https://bugs.launchpad.net/bugs/372170 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 372170] Re: intel isw raid metadata at odd offset
You could do a probe for the ICH10 tag for now. That would probably be safer than guessing a dereference, then we need some more ICH10R based people to test which will take time. You could try building another RAID set with a couple of other disks and see if the meta is in the same place on those disks also. -- intel isw raid metadata at odd offset https://bugs.launchpad.net/bugs/372170 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 369263] Re: dmraid in jaunty not started at bootup (have to do: dmraid -ay Ctrl+D in root console)
*** This bug is a duplicate of bug 367553 *** https://bugs.launchpad.net/bugs/367553 This issue has been fixed in git (see the duplicate bug). You may need to wait a while for it to propagate into the main repos. -- dmraid in jaunty not started at bootup (have to do: dmraid -ay Ctrl+D in root console) https://bugs.launchpad.net/bugs/369263 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 372170] Re: intel isw raid metadata at odd offset
Yep looks that way. I'm only on ICH8R, ICH10 is the latest Intel ICH controller from Q4 last year. (according to their datasheets) Its odd that they would have moved the metadata, I'm fairly sure the RAID sets are compatible across versions of intel matrix raid. I can't find any reference to the metadata locations in the datasheet. In the location where the metadata should be is there any reference to the area where yours is located? (could try DD dumping it, might make for a better detection routine) -- intel isw raid metadata at odd offset https://bugs.launchpad.net/bugs/372170 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 372170] Re: intel isw raid metadata at odd offset
What ICH version are you using? (couldnt read it from your lspci) -- intel isw raid metadata at odd offset https://bugs.launchpad.net/bugs/372170 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 337284] Re: dmraid fails to activate isw due to incorrect disk size (dmraid rc15)
Unfortunatly because of the workaround I did I cant actually test fully. I can obviously view the calculation. BVut to test fully I will have to dig out a couple of sata drives and build them on rc14 to test. But if it reverts what Giuseppe pointed out as the difference between the two versions then it should work fine. -- dmraid fails to activate isw due to incorrect disk size (dmraid rc15) https://bugs.launchpad.net/bugs/337284 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 337284] Re: dmraid fails to activate isw due to incorrect disk size (dmraid rc15)
I have only one of the original sets left from this bug as I had an upgrade. But the one set calculates as it did in rc14: *** Group superset isw_cjfgejeghi -- Active Subset name : isw_cjfgejeghi_HD3 size : 1953536512 stride : 256 type : stripe status : ok subsets: 0 devs : 2 spares : 0 -- dmraid fails to activate isw due to incorrect disk size (dmraid rc15) https://bugs.launchpad.net/bugs/337284 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 348353] Re: Pulse Audio no longer works with alsa a52 plugin (Ubuntu 9.04 Jaunty)
One of the updates in the last 2 weeks has broken my a52 again. I get awful breakups and so on. -- Pulse Audio no longer works with alsa a52 plugin (Ubuntu 9.04 Jaunty) https://bugs.launchpad.net/bugs/348353 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 349516] Re: Regression: Patch 15_isw_incorrect_status_fix breaks latest dmraid (no raid sets) Ubuntu 9.04 Beta
This bug has been fixed. The bug you speak of is with the nvidia dmraid and is located here: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/356503 This bug is NOT the same! -- Regression: Patch 15_isw_incorrect_status_fix breaks latest dmraid (no raid sets) Ubuntu 9.04 Beta https://bugs.launchpad.net/bugs/349516 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
