Ubuntu
dmraid package

Bug #941874
Comment #22

Comment 22 for bug 941874

Revision history for this message

Shannon VanWagner (shannon-vanwagner) wrote on 2012-03-19: Re: [Bug 941874] Re: (fakeraid) root device not activated during boot

#22

Ken,

for me, everything was in /dev/mapper and before running dmraid -ay
ls /dev/mapper/ only had the device, not the partitions:
isw_dgjgchief_Volume0

Then after dmraid -ay, ls /dev/mapper shows (p1,p2,p3 being my /, home,
swap partitions):
isw_dgjgchief_Volume0p1 isw_dgjgchief_Volume0p3
isw_dgjgchief_Volume0 isw_dgjgchief_Volume0p2

I think my machine is running with the sd drives setup as striped.

Never the less, the fix in my previous comment works for my situation.

Regards,
Shannon

On Sun, Mar 18, 2012 at 7:47 PM, Ken Persing <email address hidden> wrote:

> OK, no idea if this will help, but when I get thrown into initramfs,
> when running 'dmraid -ay', it says the raid volume is already activated,
> but in /dev I only have the raided drive (dm-0) and not any of the
> partitions (dm-1 and dm-2). Booting from a rescue disk, I have the same
> problem and after running kpartx (iirc, kpartx -a /dev/dm-0, I'm not in
> front of my pc), the devices appear and can be mounted.
>
> So, if the dmraid udev tool is supposed to take care of running
> kpartx... it's not working.
>
> btw, drives are running under "isw : Intel Software RAID" (4x120gb
> agility 3s, sda-sdd), so I'm not sure if I'm affected by the lack of awk
> and sed hooks as martin pointed out earlier...
>
> Cheers,
>
> Ken
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/941874
>
> Title:
> (fakeraid) root device not activated during boot
>
> Status in “dmraid” package in Ubuntu:
> Fix Released
> Status in “multipath-tools” package in Ubuntu:
> Incomplete
>
> Bug description:
> 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.
>
> ---
> The problems are:
>
> * 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
>
> * 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, 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)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/941874/+subscriptions
>

Ken,

for me, everything was in /dev/mapper and before running dmraid -ay
ls /dev/mapper/ only had the device, not the partitions:
isw_dgjgchief_Volume0

Then after dmraid -ay, ls /dev/mapper shows (p1,p2,p3 being my /, home,
swap partitions):
isw_dgjgchief_Volume0p1  isw_dgjgchief_Volume0p3
isw_dgjgchief_Volume0  isw_dgjgchief_Volume0p2

I think my machine is running with the sd drives setup as striped.

Never the less, the fix in my previous comment works for my situation.

Regards,
Shannon

On Sun, Mar 18, 2012 at 7:47 PM, Ken Persing <ken@persing.net> wrote:

> OK, no idea if this will help, but when I get thrown into initramfs,
> when running 'dmraid -ay', it says the raid volume is already activated,
> but in /dev I only have the raided drive (dm-0) and not any of the
> partitions (dm-1 and dm-2). Booting from a rescue disk, I have the same
> problem and after running kpartx (iirc, kpartx -a /dev/dm-0, I'm not in
> front of my pc), the devices appear and can be mounted.
>
> So, if the dmraid udev tool is supposed to take care of running
> kpartx... it's not working.
>
> btw, drives are running under "isw : Intel Software RAID" (4x120gb
> agility 3s, sda-sdd), so I'm not sure if I'm affected by the lack of awk
> and sed hooks as martin pointed out earlier...
>
> Cheers,
>
> Ken
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/941874
>
> Title:
>  (fakeraid) root device not activated during boot
>
> Status in “dmraid” package in Ubuntu:
>  Fix Released
> Status in “multipath-tools” package in Ubuntu:
>  Incomplete
>
> Bug description:
>  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.
>
>  ---
>  The problems are:
>
>  * 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
>
>  * 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, 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)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/941874/+subscriptions
>

Ubuntudmraid package

Comment 22 for bug 941874

Ubuntu
dmraid package