[Bug 1349462] Re: mw600 sony ericson doesnt work on ubuntu 14.04
This is perhaps not the exactly the same bug as affects me because MW600 shows up a sound output device but it only works as a handset (HDP/HFP) but not as audio (A2DP). It worked in 12.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1349462 Title: mw600 sony ericson doesnt work on ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1349462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1089270] [NEW] udisks does not recognize GPT partitions
Public bug reported: When clicking on an encrypted device with a GUID Partition Table in Nautilus, nautilus unlocks the device but the partitions on the unlocked device never show up or get mounted. No new device mappings show up for the partitions. Problem appears to be that udisks does not detect and add mappings for the gpt partitions. Possible workaround by adding mappings with kpartx and then mount devices manually $sudo kpartx -a LUKS_DEVICE $sudo mount LUKS_DEVICEp1 DIR etc ** Affects: udisks (Ubuntu) Importance: Undecided Status: New ** Tags: 12.04 gpt precise udisks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1089270 Title: udisks does not recognize GPT partitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks/+bug/1089270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 941874] Re: (fakeraid) root device not activated during boot
Works for me as well now, thanks! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/941874 Title: (fakeraid) root device not activated during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/941874/+subscriptions -- 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 941874] Re: (fakeraid) root device not activated during boot
Works for me as well now, thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/941874 Title: (fakeraid) root device not activated during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/941874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 941874] Re: (fakeraid) root device not activated during boot
I think kpartx, sed and awk is also missing in the ramfs, at least for me. kpartx can not mount a root partitions if kpartx is not available during boot... sed and awk is used by the dmraid-activate script in some cases as well... not for my controller though so I can not test it. I added kpartx hooks on my machine as well, which fixed the issue for me. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/941874 Title: (fakeraid) root device not activated during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/941874/+subscriptions -- 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 941874] Re: (fakeraid) root device not activated during boot
Sorry if I'm using the wrong terminology, I just called it hooks because that is what the folder is named. I mean I have added a script very similar to: /usr/share/initramfs-tools/hooks/dmraid which copies the necessary kpartx files to the initramfs as well, when doing update-initramfs -u (at least that is what I assume happens ;)). I include these for kpartx: /sbin/kpartx /lib/udev/kpartx_id /lib/udev/dmsetup_env /lib/udev/rules.d/95-kpartx.rules -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/941874 Title: (fakeraid) root device not activated during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/941874/+subscriptions -- 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 941874] Re: (fakeraid) root device not activated during boot
Attaching file: -rwxr-xr-x 1 root root 490 feb 29 18:53 /usr/share/initramfs-tools/hooks/kpartx ** Attachment added: /usr/share/initramfs-tools/hooks/kpartx https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/941874/+attachment/2898387/+files/kpartx -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/941874 Title: (fakeraid) root device not activated during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/941874/+subscriptions -- 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 941874] Re: (fakeraid) root device not activated during boot
I think kpartx, sed and awk is also missing in the ramfs, at least for me. kpartx can not mount a root partitions if kpartx is not available during boot... sed and awk is used by the dmraid-activate script in some cases as well... not for my controller though so I can not test it. I added kpartx hooks on my machine as well, which fixed the issue for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/941874 Title: (fakeraid) root device not activated during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/941874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 941874] Re: (fakeraid) root device not activated during boot
Sorry if I'm using the wrong terminology, I just called it hooks because that is what the folder is named. I mean I have added a script very similar to: /usr/share/initramfs-tools/hooks/dmraid which copies the necessary kpartx files to the initramfs as well, when doing update-initramfs -u (at least that is what I assume happens ;)). I include these for kpartx: /sbin/kpartx /lib/udev/kpartx_id /lib/udev/dmsetup_env /lib/udev/rules.d/95-kpartx.rules -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/941874 Title: (fakeraid) root device not activated during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/941874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 941874] Re: (fakeraid) root device not activated during boot
Attaching file: -rwxr-xr-x 1 root root 490 feb 29 18:53 /usr/share/initramfs-tools/hooks/kpartx ** Attachment added: /usr/share/initramfs-tools/hooks/kpartx https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/941874/+attachment/2898387/+files/kpartx -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/941874 Title: (fakeraid) root device not activated during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/941874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 899244] Re: GMA500 psb_gfx
psb_gfx is working well on my eee pc 1101ha (only 2d though). ** Attachment added: lspci -vnvn https://bugs.launchpad.net/ubuntu/+source/linux/+bug/899244/+attachment/2840501/+files/psb_gfx.eepc_1101ha.lspci_-vnvn -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/899244 Title: GMA500 psb_gfx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/899244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 899244] Re: GMA500 psb_gfx
It might also be good to make ubiquity 2d the default login when using psb_gfx..? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/899244 Title: GMA500 psb_gfx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/899244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 941874] Re: (fakeraid) root device not activated during boot
Congratulations for the new baby :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/941874 Title: (fakeraid) root device not activated during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/941874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 941874] Re: (fakeraid) root device not activated during boot
** Description changed: - I have installed Precise Pangolin Alpha 2 to a fakeraid stripe, but ubuntu fails to boot after install. - When choosing recovery option, the boot process times out waiting for root device and drops to busybox shell. - Running dmraid -ay and exiting busybox resumes boot and it continues normally. + I have installed Precise Pangolin Alpha 2 to a fakeraid stripe, but + ubuntu fails to boot after install. When choosing recovery option, the + boot process times out waiting for root device and drops to busybox + shell. Running dmraid -ay and exiting busybox resumes boot and it + continues normally. - I've added a script in /etc/initramfs-tools/script/local-top/ that run - dmraid -ay as a solution. + --- + The problems are: - I might have identified problems with dmraid-activate script. - For example, it expects a device name without /dev/ (e.g. sda) however it is being called from /usr/share/initramfs-tools/scripts/local-top/dmraid script with the full device name (e.g. /dev/sda). That does not fix the boot issue since dmraid-activate is not called befoore mounting root. + * There are no initramfs hooks for kpartx, so kpartx is not available during boot. + the following files are needed: + /sbin/kpartx + /lib/udev/kpartx_id + /lib/udev/dmsetup_env + /lib/udev/rules.d/95-kpartx.rules - There might also be antoher bug on line 100 in dmraid-activate (in the awk script): + * The hook for dmraid udev rules is wrong: + The script /usr/share/initramfs-tools/hooks/dmraid + tries to add: + /lib/udev/rules.d/85-dmraid.rules + but the existing file is called: + /lib/udev/rules.d/97-dmraid.rules + + After fixing the above two issues, system boots normally. + + * dmraid-activate is sometimes called with full device name + dmraid-activate expecte device name withouth /dev/, e.g. sda not /dev/sda. However the script + /usr/share/initramfs-tools/scripts/local-top/dmraid + calls dmraid-activate using the full device name and path. + + * There might also be antoher bug on line 100 in dmraid-activate (in the awk script): # Heximal to decimal conversion array for (i = 0; i = 9; i++) hex2dec[i] = i hex2dec[a] = 10; hex2dec[b] = 11; hex2dec[c] = 12 hex2dec[e] = 13; hex2dec[d] = 14; hex2dec[f] = 15; - - Element e and d appears to have been switched. I'm not entirely sure - what the script is trying to do though. + Element e and d appears to have been switched. I'm not entirely sure what the script is trying to do though, and that part of the script does not affect my system. --- ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: dmraid 1.0.0.rc16-4.1ubuntu6 [modified: sbin/dmraid-activate usr/share/initramfs-tools/scripts/local-top/dmraid] ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6 Uname: Linux 3.2.0-17-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 1.93-0ubuntu2 Architecture: amd64 Date: Mon Feb 27 12:59:55 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120201.2) ProcEnviron: PATH=(custom, user) LANG=sv_SE.UTF-8 SHELL=/bin/bash SourcePackage: dmraid UpgradeStatus: Upgraded to precise on 2012-02-21 (5 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/941874 Title: (fakeraid) root device not activated during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/941874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 941874] Re: (fakeraid) root device not activated during boot
dmraid-activate also use sed and awk when activating certain fakeraid types: isw : Intel Software RAID (0,1,5,01) ddf1: SNIA DDF1 (0,1,4,5,linear) I don't think awk and sed is available in the initramfs either so there should probably be hooks for that too if there is a device of that type installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/941874 Title: (fakeraid) root device not activated during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/941874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 941874] Re: (fakeraid) root device not activated during boot
I've got dmraid-activate to load the device now (/dev/mapper/pdc_chjidjcfg) but the partitions still does not get loaded. kpartx is not available in busybox, is that correct? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/941874 Title: (fakeraid) root device not activated during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/941874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 941874] Re: (fakeraid) root device not activated during boot
There are no initramfs hooks for kpartx also, in: /usr/share/initramfs-tools/hooks/dmraid it tries to add /lib/udev/rules.d/85-dmraid.rules but the existing file is called /lib/udev/rules.d/97-dmraid.rules When I fix the above and add hooks for kpartx everything works and ubuntu boots normally. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/941874 Title: (fakeraid) root device not activated during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/941874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 941874] [NEW] dmraid-activate fails to activate (fakeraid) root device during boot
Public bug reported: I have installed Precise Pangolin Alpha 2 to a fakeraid stripe, but ubuntu fails to boot after install. When choosing recovery option, the boot process times out waiting for root device and drops to busybox shell. Running dmraid -ay and exiting busybox resumes boot and it continues normally. I've added a script in /etc/initramfs-tools/script/local-top/ that run dmraid -ay as a solution. The problem seems to be with the dmraid-activate script. For example, it expects a device name without /dev/ (e.g. sda) however it is being called from /usr/share/initramfs-tools/scripts/local-top/dmraid script with the full device name (e.g. /dev/sda). Fixing that didn't solve the boot issue since the the activate_array function in dmraid-activate does not seem to work either. There might also be antoher bug on line 100 in dmraid-activate (in the awk script): # Heximal to decimal conversion array for (i = 0; i = 9; i++) hex2dec[i] = i hex2dec[a] = 10; hex2dec[b] = 11; hex2dec[c] = 12 hex2dec[e] = 13; hex2dec[d] = 14; hex2dec[f] = 15; Element e and d appears to have been switched. I'm not entirely sure what the script is trying to do though. --- ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: dmraid 1.0.0.rc16-4.1ubuntu6 [modified: sbin/dmraid-activate usr/share/initramfs-tools/scripts/local-top/dmraid] ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6 Uname: Linux 3.2.0-17-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 1.93-0ubuntu2 Architecture: amd64 Date: Mon Feb 27 12:59:55 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120201.2) ProcEnviron: PATH=(custom, user) LANG=sv_SE.UTF-8 SHELL=/bin/bash SourcePackage: dmraid UpgradeStatus: Upgraded to precise on 2012-02-21 (5 days ago) ** Affects: dmraid (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug boot fakeraid precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/941874 Title: dmraid-activate fails to activate (fakeraid) root device during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/941874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 941874] Re: dmraid-activate fails to activate (fakeraid) root device during boot
** Description changed: I have installed Precise Pangolin Alpha 2 to a fakeraid stripe, but ubuntu fails to boot after install. - When choosing recovery option, the boot process times out waiting for root device and drops to busybox shell. + When choosing recovery option, the boot process times out waiting for root device and drops to busybox shell. Running dmraid -ay and exiting busybox resumes boot and it continues normally. I've added a script in /etc/initramfs-tools/script/local-top/ that run dmraid -ay as a solution. The problem seems to be with the dmraid-activate script. For example, it expects a device name without /dev/ (e.g. sda) however it is being called from /usr/share/initramfs-tools/scripts/local-top/dmraid script with the full device name (e.g. /dev/sda). Fixing that didn't solve the boot issue since the the activate_array function in dmraid-activate does not seem to work either. There might also be antoher bug on line 100 in dmraid-activate (in the awk script): - # Heximal to decimal conversion array - for (i = 0; i = 9; i++) hex2dec[i] = i - hex2dec[a] = 10; hex2dec[b] = 11; hex2dec[c] = 12 - hex2dec[e] = 13; hex2dec[d] = 14; hex2dec[f] = 15; + # Heximal to decimal conversion array + for (i = 0; i = 9; i++) hex2dec[i] = i + hex2dec[a] = 10; hex2dec[b] = 11; hex2dec[c] = 12 + hex2dec[e] = 13; hex2dec[d] = 14; hex2dec[f] = 15; Element e and d appears to have been switched. I'm not entirely sure what the script is trying to do though. --- - root@pongo:~# lsb_release -rd - Description: Ubuntu precise (development branch) - Release: 12.04 - root@pongo:~# uname -a - Linux pongo 3.2.0-17-generic #26-Ubuntu SMP Fri Feb 17 21:35:49 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux - root@pongo:~# apt-cache policy dmraid - dmraid: - Installerad: 1.0.0.rc16-4.1ubuntu6 - Kandidat:1.0.0.rc16-4.1ubuntu6 - Versionstabell: - *** 1.0.0.rc16-4.1ubuntu6 0 - 500 http://se.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages - 100 /var/lib/dpkg/status - ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: dmraid 1.0.0.rc16-4.1ubuntu6 [modified: sbin/dmraid-activate usr/share/initramfs-tools/scripts/local-top/dmraid] ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6 Uname: Linux 3.2.0-17-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 1.93-0ubuntu2 Architecture: amd64 Date: Mon Feb 27 12:59:55 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120201.2) ProcEnviron: - PATH=(custom, user) - LANG=sv_SE.UTF-8 - SHELL=/bin/bash + PATH=(custom, user) + LANG=sv_SE.UTF-8 + SHELL=/bin/bash SourcePackage: dmraid UpgradeStatus: Upgraded to precise on 2012-02-21 (5 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/941874 Title: dmraid-activate fails to activate (fakeraid) root device during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/941874/+subscriptions -- 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
Ok. If anyone has the same issue, I filed a new bug here https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/941874 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/373520 Title: dmraid 1.0.0.rc15-6ubuntu2 amd64 + NVRAID boot fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/373520/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 941874] Re: dmraid-activate fails to activate (fakeraid) root device during boot
The activate_array function works, it's just that it runs dmraid -ay -i -p -Z and the -p option prevents partitions to be activated. Changing that doesn't work either though, since it looks like dmraid-activate is never called. I'm not sure how dmraid is supposed to activate the root device during boot in that case? ** Description changed: I have installed Precise Pangolin Alpha 2 to a fakeraid stripe, but ubuntu fails to boot after install. When choosing recovery option, the boot process times out waiting for root device and drops to busybox shell. Running dmraid -ay and exiting busybox resumes boot and it continues normally. I've added a script in /etc/initramfs-tools/script/local-top/ that run dmraid -ay as a solution. - The problem seems to be with the dmraid-activate script. - For example, it expects a device name without /dev/ (e.g. sda) however it is being called from /usr/share/initramfs-tools/scripts/local-top/dmraid script with the full device name (e.g. /dev/sda). Fixing that didn't solve the boot issue since the the activate_array function in dmraid-activate does not seem to work either. + I might have identified problems with dmraid-activate script. + For example, it expects a device name without /dev/ (e.g. sda) however it is being called from /usr/share/initramfs-tools/scripts/local-top/dmraid script with the full device name (e.g. /dev/sda). That does not fix the boot issue since dmraid-activate is not called befoore mounting root. There might also be antoher bug on line 100 in dmraid-activate (in the awk script): # Heximal to decimal conversion array for (i = 0; i = 9; i++) hex2dec[i] = i hex2dec[a] = 10; hex2dec[b] = 11; hex2dec[c] = 12 hex2dec[e] = 13; hex2dec[d] = 14; hex2dec[f] = 15; Element e and d appears to have been switched. I'm not entirely sure what the script is trying to do though. --- ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: dmraid 1.0.0.rc16-4.1ubuntu6 [modified: sbin/dmraid-activate usr/share/initramfs-tools/scripts/local-top/dmraid] ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6 Uname: Linux 3.2.0-17-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 1.93-0ubuntu2 Architecture: amd64 Date: Mon Feb 27 12:59:55 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120201.2) ProcEnviron: PATH=(custom, user) LANG=sv_SE.UTF-8 SHELL=/bin/bash SourcePackage: dmraid UpgradeStatus: Upgraded to precise on 2012-02-21 (5 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/941874 Title: dmraid-activate fails to activate (fakeraid) root device during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/941874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 941874] Re: (fakeraid) root device not activated during boot
** Summary changed: - dmraid-activate fails to activate (fakeraid) root device during boot + (fakeraid) root device not activated during boot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/941874 Title: (fakeraid) root device not activated during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/941874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 941874] Re: (fakeraid) root device not activated during boot
Stripe is on sda + sdb. When I run blkid, sdb show up but not sda, blkid -p sda identifies it as part of raid though. root@pongo:/dev# blkid -p sda sda: TYPE=promise_fasttrack_raid_member USAGE=raid root@pongo:/dev# blkid -p sdb sdb: TYPE=promise_fasttrack_raid_member USAGE=raid root@pongo:/dev# blkid /dev/sdb: TYPE=promise_fasttrack_raid_member /dev/mapper/pdc_chjidjcfg1: LABEL=SSD UUID=D6825DE9825DCF1D TYPE=ntfs /dev/mapper/pdc_chjidjcfg5: LABEL=ubuntu UUID=520af4ca-51ba-4238-a594-2d1b673f4a9e UUID_SUB=f4cdc806-21be-4943-9e6d-d6a7645f311d TYPE=btrfs /dev/mapper/pdc_chjidjcfg6: UUID=300c5e59-35ac-4654-809e-8d5d8391ce99 TYPE=swap -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/941874 Title: (fakeraid) root device not activated during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/941874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 941874] Re: (fakeraid) root device not activated during boot
If it helps: root@pongo:~# kpartx -l /dev/mapper/pdc_chjidjcfg pdc_chjidjcfg1 : 0 335544320 /dev/mapper/pdc_chjidjcfg 2048 pdc_chjidjcfg2 : 0 129296898 /dev/mapper/pdc_chjidjcfg 335546622 pdc_chjidjcfg5 : 0 112540672 /dev/dm-1 2 pdc_chjidjcfg6 : 0 16755968 /dev/dm-1 112540930 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/941874 Title: (fakeraid) root device not activated during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/941874/+subscriptions -- 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
This bug still exists in Precise. I have installed Precise Pangolin Alpha 2 to a fakeraid stripe, but ubuntu fails to boot after install. When choosing recovery option, the boot process times out waiting for root device and drops to busybox shell. Running dmraid -ay and exiting busybox resumes boot and it continues normally. I've added a script in /etc/initramfs-tools/script/local-top/ that run dmraid -ay as a solution. The problem seems to be with the dmraid-activate script. For example, it expects a device name without /dev/ (e.g. sda) however it is being called from /usr/share/initramfs-tools/scripts/local-top/dmraid script with the full device name (e.g. /dev/sda). Fixing that didn't solve the boot issue since the the activate_array function in dmraid-activate does not seem to work either. --- There might also be antoher bug on line 100 in dmraid-activate (in the awk script): # Heximal to decimal conversion array for (i = 0; i = 9; i++) hex2dec[i] = i hex2dec[a] = 10; hex2dec[b] = 11; hex2dec[c] = 12 hex2dec[e] = 13; hex2dec[d] = 14; hex2dec[f] = 15; Element e and d appears to have been switched. I'm not entirely sure what the script is trying to do though. --- root@pongo:~# lsb_release -rd Description:Ubuntu precise (development branch) Release:12.04 root@pongo:~# uname -a Linux pongo 3.2.0-17-generic #26-Ubuntu SMP Fri Feb 17 21:35:49 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux root@pongo:~# apt-cache policy dmraid dmraid: Installerad: 1.0.0.rc16-4.1ubuntu6 Kandidat:1.0.0.rc16-4.1ubuntu6 Versionstabell: *** 1.0.0.rc16-4.1ubuntu6 0 500 http://se.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/373520 Title: dmraid 1.0.0.rc15-6ubuntu2 amd64 + NVRAID boot fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/373520/+subscriptions -- 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
** Tags added: 12.04 dmraid-activate precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/373520 Title: dmraid 1.0.0.rc15-6ubuntu2 amd64 + NVRAID boot fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/373520/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 244480] Re: support AES-XTS mode
Well, the paper also says that: Use of a single cryptographic key for more than a few hundred terabytes of data opens possibility of attacks, as described in D.4.3. The limitation on the size of data encrypted with a single key is not unique to this standard. It comes directly from the fact that AES has a block size of 128 bits and is not mitigated by using AES with a 256-bit key. So it might not be a unique problem for XTS but anything using AES with 128 bit blocks? The entire partition should also be filled with randomized data before encryption. -- support AES-XTS mode https://bugs.launchpad.net/bugs/244480 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
