https://bugs.launchpad.net/ubuntu/+source/linux-lts-quantal/+bug/1202955
--
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
https://bugs.launchpad.net/ubuntu/+source/linux-lts-quantal/+bug/1202955
--
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
I've just installed a HP Microserver (N40L) with the latest installer
from precise-updates/main/installer-amd64/20101020ubuntu136.9/images
/quantal-netboot. The installer fails to activate the raid, so I had to
drop into a shell, write dmraid -ay, to continue the installation.
After the install,
Before running dmraid -ay, what does blkid show?
--
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
(initramfs) dmraid -ay
RAID set pdc_ebdeeaiceb-0 was activated
RAID set pdc_ebdeeaiceb-1 was activated
RAID set pdc_ebdeeaiceb was activated
RAID set pdc_ebdeeaiceb1 was activated
RAID set pdc_ebdeeaiceb2 was activated
RAID set pdc_ebdeeaiceb3 was activated
--
You received this bug notification
(initramfs) blkid
(initramfs) blkid -p /dev/sd[a-d]
/dev/sda: TYPE=promise_fasttrack_raid_member USAGE=raid
/dev/sdb: TYPE=promise_fasttrack_raid_member USAGE=raid
/dev/sdc: TYPE=promise_fasttrack_raid_member USAGE=raid
/dev/sdd: TYPE=promise_fasttrack_raid_member USAGE=raid
Without any
If /dev/mapper/pdc_ebdeeaiceb does not exist without you having to run
dmraid, then it is unrelated to this bug. Please file a new one.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
I've just installed a HP Microserver (N40L) with the latest installer
from precise-updates/main/installer-amd64/20101020ubuntu136.9/images
/quantal-netboot. The installer fails to activate the raid, so I had to
drop into a shell, write dmraid -ay, to continue the installation.
After the install,
Before running dmraid -ay, what does blkid show?
--
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
(initramfs) dmraid -ay
RAID set pdc_ebdeeaiceb-0 was activated
RAID set pdc_ebdeeaiceb-1 was activated
RAID set pdc_ebdeeaiceb was activated
RAID set pdc_ebdeeaiceb1 was activated
RAID set pdc_ebdeeaiceb2 was activated
RAID set pdc_ebdeeaiceb3 was activated
--
You received this bug notification
(initramfs) blkid
(initramfs) blkid -p /dev/sd[a-d]
/dev/sda: TYPE=promise_fasttrack_raid_member USAGE=raid
/dev/sdb: TYPE=promise_fasttrack_raid_member USAGE=raid
/dev/sdc: TYPE=promise_fasttrack_raid_member USAGE=raid
/dev/sdd: TYPE=promise_fasttrack_raid_member USAGE=raid
Without any
If /dev/mapper/pdc_ebdeeaiceb does not exist without you having to run
dmraid, then it is unrelated to this bug. Please file a new one.
--
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:
Unless you must dual boot this system with Windows, the best thing to do
is not to use fake raid. Switch to regular Linux software raid instead.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
Unless you must dual boot this system with Windows, the best thing to do
is not to use fake raid. Switch to regular Linux software raid instead.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/941874
Hi all
this is a real doozy.
I need to run 10.04 because it has userful mutiseat and can boot the
same partition on a single disk but can't on my fake raid. gpt
partitioning on the raid because it is 4tb.
I can boot 12.04 (kde) on the fake raid fine but get the same error as
above when trying
Hi all
this is a real doozy.
I need to run 10.04 because it has userful mutiseat and can boot the
same partition on a single disk but can't on my fake raid. gpt
partitioning on the raid because it is 4tb.
I can boot 12.04 (kde) on the fake raid fine but get the same error as
above when trying
Hi
I am encountering the same problems, in that I am trying to install
UBUNTU 12.04 on a Sony vaio VPCZ13C5E. But can't get past busybox.
I used boot/repair to try and fix the problem, the diagnostics and a
dscription of my system are at http://paste.ubuntu.com/1126678/
Any help would be
Hi
I am encountering the same problems, in that I am trying to install
UBUNTU 12.04 on a Sony vaio VPCZ13C5E. But can't get past busybox.
I used boot/repair to try and fix the problem, the diagnostics and a
dscription of my system are at http://paste.ubuntu.com/1126678/
Any help would be
@Path
Off topic for a bug report but I will set you straight on a few things.
Dmraid support is good but for later hardware is crappy at best but
don't blame the Ubuntu devs. The original developer (a red hat guy)
stopped developing the project a while ago and we have been trying to
get him to
@Path
Off topic for a bug report but I will set you straight on a few things.
Dmraid support is good but for later hardware is crappy at best but
don't blame the Ubuntu devs. The original developer (a red hat guy)
stopped developing the project a while ago and we have been trying to
get him to
This is because Ubuntu is a piece of shite time waster, worse than
Windows 98 and Windows 3.1. You want something solid don't go with a
distro that places importance on new themes instead of stability. It
will be 2019 and Ubuntu team will still try to fix these bugs. They're
worse than Microsoft
This is because Ubuntu is a piece of shite time waster, worse than
Windows 98 and Windows 3.1. You want something solid don't go with a
distro that places importance on new themes instead of stability. It
will be 2019 and Ubuntu team will still try to fix these bugs. They're
worse than Microsoft
Just worked around the same problem that Adi Piracalabu described.
Installed Ubuntu 12.04 release Amd64 image on fakeraid raid5. With my
boot loader, root directory and swap all on a separate disc. Then my
home directory on my raid 5. Installation completed successfully.
Rebooting fails to mount
Just worked around the same problem that Adi Piracalabu described.
Installed Ubuntu 12.04 release Amd64 image on fakeraid raid5. With my
boot loader, root directory and swap all on a separate disc. Then my
home directory on my raid 5. Installation completed successfully.
Rebooting fails to mount
Adi, dmraid is for fake hardware raid support, not the software raid you
are using. Your issue seems to be unrelated to dmraid or this bug
report.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
Adi, dmraid is for fake hardware raid support, not the software raid you
are using. Your issue seems to be unrelated to dmraid or this bug
report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/941874
Apparently I have a related problem after an upgrade from 11.10 done using
do-release-upgrade. The troubled server has all the partitions on a software
RAID 1. With the new kernel (3.2.0-24.37) it failed to mount the root
partition, dropping to a busybox shell. After booting the ol kernel I
Quick update to my previous update: after rebuilding initrd image with
dmraid kpartx it's all good, now 3.2.0-24-generic finds the root
partition and loads the OS.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in
Apparently I have a related problem after an upgrade from 11.10 done using
do-release-upgrade. The troubled server has all the partitions on a software
RAID 1. With the new kernel (3.2.0-24.37) it failed to mount the root
partition, dropping to a busybox shell. After booting the ol kernel I
Quick update to my previous update: after rebuilding initrd image with
dmraid kpartx it's all good, now 3.2.0-24-generic finds the root
partition and loads the OS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
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:
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
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:
With this release, the problem is fixed 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
With this release, the problem is fixed 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
Giving my release team nod for the FFe required to do the simple package
split in the multipath-tools branch, and sponsoring the upload (after
tidying it a bit). Thanks for looking at this.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
This bug was fixed in the package multipath-tools - 0.4.9-3ubuntu5
---
multipath-tools (0.4.9-3ubuntu5) precise; urgency=low
* Split kpartx initramfs bits into kpartx-boot for dmraid (LP: #941874)
-- Phillip Susi ps...@ubuntu.com Tue, 20 Mar 2012 15:26:22 -0400
--
You received
This bug was fixed in the package dmraid - 1.0.0.rc16-4.1ubuntu8
---
dmraid (1.0.0.rc16-4.1ubuntu8) precise; urgency=low
* Depend on kpartx-boot to pull kpartx into the initramfs (LP: #941874)
-- Phillip Susi ps...@ubuntu.com Tue, 20 Mar 2012 15:37:44 -0400
** Changed in:
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:
Giving my release team nod for the FFe required to do the simple package
split in the multipath-tools branch, and sponsoring the upload (after
tidying it a bit). Thanks for looking at this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This bug was fixed in the package dmraid - 1.0.0.rc16-4.1ubuntu8
---
dmraid (1.0.0.rc16-4.1ubuntu8) precise; urgency=low
* Depend on kpartx-boot to pull kpartx into the initramfs (LP: #941874)
-- Phillip Susi ps...@ubuntu.com Tue, 20 Mar 2012 15:37:44 -0400
** Changed in:
This bug was fixed in the package multipath-tools - 0.4.9-3ubuntu5
---
multipath-tools (0.4.9-3ubuntu5) precise; urgency=low
* Split kpartx initramfs bits into kpartx-boot for dmraid (LP: #941874)
-- Phillip Susi ps...@ubuntu.com Tue, 20 Mar 2012 15:26:22 -0400
--
You received
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/941874
Title:
(fakeraid) root device
** Changed in: dmraid (Ubuntu)
Importance: High = Critical
** Changed in: multipath-tools (Ubuntu)
Importance: High = Critical
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
** Changed in: dmraid (Ubuntu)
Milestone: None = ubuntu-12.04
** Changed in: multipath-tools (Ubuntu)
Milestone: None = ubuntu-12.04
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
** Changed in: dmraid (Ubuntu)
Importance: High = Critical
** Changed in: multipath-tools (Ubuntu)
Importance: High = Critical
--
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:
** Changed in: dmraid (Ubuntu)
Milestone: None = ubuntu-12.04
** Changed in: multipath-tools (Ubuntu)
Milestone: None = ubuntu-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/941874
I've fixed both packages to get this working and set up an isw dmraid
with my old disks and installed precise and the updated packages to
verify it works. Just waiting for a sponsor to merge the changes.
** Changed in: dmraid (Ubuntu)
Status: Fix Released = In Progress
** Changed in:
I've fixed both packages to get this working and set up an isw dmraid
with my old disks and installed precise and the updated packages to
verify it works. Just waiting for a sponsor to merge the changes.
** Changed in: dmraid (Ubuntu)
Status: Fix Released = In Progress
** Changed in:
** Branch linked: lp:~psusi/ubuntu/precise/multipath-tools/fix-dmraid
--
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
The -p is to disable dmraid's internal handling of partitions in favor
of letting kpartx take care of it. This was done because kpartx also
supports GPT, but dmraid does not.
Can you try updating your initramfs and see if that helps?
sudo update-initramfs -u
Also please make sure you are
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
What do you mean by added kpartx hooks?
--
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
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
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
Ok, kpartx has a hook rule that is supposed to do that already, but for
some reason, it is not being installed. It looks like a packaging error
of some sort.
** Changed in: multipath-tools (Ubuntu)
Status: Incomplete = Triaged
--
You received this bug notification because you are a
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
The -p is to disable dmraid's internal handling of partitions in favor
of letting kpartx take care of it. This was done because kpartx also
supports GPT, but dmraid does not.
Can you try updating your initramfs and see if that helps?
sudo update-initramfs -u
Also please make sure you are
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
What do you mean by added kpartx hooks?
--
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:
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
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
Ok, kpartx has a hook rule that is supposed to do that already, but for
some reason, it is not being installed. It looks like a packaging error
of some sort.
** Changed in: multipath-tools (Ubuntu)
Status: Incomplete = Triaged
--
You received this bug notification because you are a
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
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
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:
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
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
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
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:
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
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
This fix still works for me:
https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/247027/comments/21
--
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:
I have this same problem with Kubuntu Precise Beta1.
I installed Kubuntu Precise Beta1 successfully (using default partition setup
with a single SATA drive) and rebooted. The desktop loads without error. I run
apt-get update apt-get upgrade and then reboot. Now the boot process stops:
…
Gave up
This fix still works for me:
https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/247027/comments/21
--
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
I have this same problem with Kubuntu Precise Beta1.
I installed Kubuntu Precise Beta1 successfully (using default partition setup
with a single SATA drive) and rebooted. The desktop loads without error. I run
apt-get update apt-get upgrade and then reboot. Now the boot process stops:
…
Gave up
** Also affects: multipath-tools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: multipath-tools (Ubuntu)
Status: New = Triaged
** Changed in: multipath-tools (Ubuntu)
Importance: Undecided = High
** Changed in: multipath-tools (Ubuntu)
Assignee: (unassigned)
Wait a second, the kpartx udev rule shouldn't have anything to do with
dmraid. The dmraid udev rule takes care of running kpartx.
** Changed in: multipath-tools (Ubuntu)
Status: Triaged = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team,
** Also affects: multipath-tools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: multipath-tools (Ubuntu)
Status: New = Triaged
** Changed in: multipath-tools (Ubuntu)
Importance: Undecided = High
** Changed in: multipath-tools (Ubuntu)
Assignee: (unassigned)
Wait a second, the kpartx udev rule shouldn't have anything to do with
dmraid. The dmraid udev rule takes care of running kpartx.
** Changed in: multipath-tools (Ubuntu)
Status: Triaged = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This bug was fixed in the package dmraid - 1.0.0.rc16-4.1ubuntu7
---
dmraid (1.0.0.rc16-4.1ubuntu7) precise; urgency=low
* Fix Update initramfs hook to copy correct udev rules file with
new priority of 97 instead of 85 (LP: #941874)
-- Phillip Susi ps...@ubuntu.com Tue, 13
I just updated to 1.0.0.rc16-4.1ubuntu7, but I still end up staring at
an initramfs prompt before needing to manually issue dmraid -ay
followed by Ctrl-D to resume boot.
We still need the kpartx hook, as pointed out by the bug submitter, in
order to fix this. :)
** Attachment added: hacky kpartx
I believe I have the same problem, but I'm not sure. Please enlighten
me.
I have a Sony Vaio VPCZ13 with two SSD's striped out of the box. In the
past I succesfully ran Natty and Oneiric. Now with Precise Beta 1 I
can't boot anymore. I get dropped in a Busybox shell with the error that
the device
Additional info...
When I choose kernel 3.2 in grub I'm dropped in Busybox shell. If I
enter 'dmraid -ay' and 'exit', then normal boot procedure continues.
W
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Branch linked: lp:~psusi/ubuntu/precise/dmraid/fix-initramfs-hook
** Changed in: dmraid (Ubuntu)
Status: Triaged = In Progress
** Changed in: dmraid (Ubuntu)
Assignee: (unassigned) = Phillip Susi (psusi)
--
You received this bug notification because you are a member of Ubuntu
I've just upgraded to precise beta and had the same problem with my
intel dmraid.
http://ubuntuforums.org/archive/index.php/t-1719850.html
helped (calling /sbin/dmraid -i -ay and commenting the rest).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
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:
Oops, this is my fault. I changed the priority of the udev rules file
from 85 to 97 and must have forgot to update the initramfs hook to use
the new path. I am in the hospital at the moment since my wife had our
baby two weeks early the other day, so I'm going to ask cjwatson to make
this quick
Good work figuring that out by the way Marten. Many 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
** 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
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
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.
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.
** 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
The -p was added in precise because udev will now run kpartx to activate
partitions. Does blkid identify the drives as raid members?
--
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:
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
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
98 matches
Mail list logo
