[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
Sorry about the linkedin spam.. I think I bombed my address book with it. Please feel free to delete comment #35. -- 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] Invitation to connect on LinkedIn
LinkedIn Bug, I'd like to add you to my professional network on LinkedIn. - Shannon Shannon VanWagner Network Administrator / IT Support at Airbiquity Greater Seattle Area Confirm that you know Shannon VanWagner: https://www.linkedin.com/e/alfvy9-h0hg05c2-9/isd/6509490604/6f-LEnoQ/?hs=false&tok=3SJK737u_n3Rc1 -- You are receiving Invitation to Connect emails. Click to unsubscribe: http://www.linkedin.com/e/alfvy9-h0hg05c2-9/h0kdSFiu9-8jrf7-iGTqW4yu8QLJwPAsKnQLHRa/goo/941874%40bugs%2Elaunchpad%2Enet/20061/I2257831682_1/?hs=false&tok=3QVqCwUqPn3Rc1 (c) 2012 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA. -- 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
>Can you try updating your initramfs and see if that helps? > >sudo update-initramfs -u I did this and I still get dropped to the busybox, just after "begin running scripts/local-top...done" shows during boot. >From busybox, ls /dev shows these (disk but not the partitions): /dev/dm-0 /dev/isw_dgjgchief_Volume0 cat /proc/kmsg shows at the end: device-mapper:dm-raid45:initialized v0.2594b >Also please make sure you are running the -ubuntu7 version of dmraid. I'm not sure how to check this. As for the dmraid command, from busybox: dmraid -V shows: dmraid version: 1.0.0.rc16 (2009.09.16) shared dmraid library version: 1.0.0.rc16 (2009.09.16) shared device-mapper version: 4.22.0 (or perhaps 4.2.2.0) Let me know if you need anything else. Cheers! -- 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
Re: [Bug 941874] Re: (fakeraid) root device not activated during boot
Ah.. disregard my previous comment.. they're just links to dm-0 thru dm-3 ls -l /dev/mapper lrwxrwxrwx 1 root root 7 Mar 18 21:05 isw_dgjgchief_Volume0 -> ../dm-0 lrwxrwxrwx 1 root root 7 Mar 18 21:05 isw_dgjgchief_Volume0p1 -> ../dm-1 lrwxrwxrwx 1 root root 7 Mar 18 21:05 isw_dgjgchief_Volume0p2 -> ../dm-2 lrwxrwxrwx 1 root root 7 Mar 18 21:05 isw_dgjgchief_Volume0p3 -> ../dm-3 I have a RAID stripe of 3 64GB sd drives on this machine. So I wonder if that's different than your configuration? hwinfo shows.. dm_log 18564 3 dm_raid45,dm_mirror,dm_region_hash, Live 0x 25: PCI 1f.2: 0104 RAID bus controller Model: "Intel Mobile 82801 SATA RAID Controller" Device: pci 0x282a "Mobile 82801 SATA RAID Controller" Attached to: #25 (RAID bus controller) -- 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
Re: [Bug 941874] Re: (fakeraid) root device not activated during boot
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 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 > -- FREE YOURSELF, Use GNU+LINUX! gnu.org | fsf.org | linux.com | getgnulinux.org | ubuntuguide.org | whylinuxisbetter.net | openoffice.org | humans-enabled.com | ubuntu.com | distrowatch.com | makethemove.net | livecdlist.com -- 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
Here's what fixed it for me: change the following line in sbin/dmraid-activate back to the same as it was in initrd.img.3.0.0.12-generic from Oneric: Change (around line 75): # array brought up in degraded mode, except in the case of striped arrays. dmraid -p -i -ay -Z "$1" To: # array brought up in degraded mode, except in the case of striped arrays. dmraid -i -ay -Z "$1" I'm curious to know the reason they decided to add the -p in this version. Does anyone know? Let me know if you need me to post the step-by-step fix.. most people probably have no idea about how to pkg/re-pkg the initrd file. Cheers! Shannon -- 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
