*** This bug is a duplicate of bug 941874 ***
https://bugs.launchpad.net/bugs/941874
** This bug has been marked a duplicate of bug 941874
(fakeraid) root device not activated during boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
*** This bug is a duplicate of bug 941874 ***
https://bugs.launchpad.net/bugs/941874
Stefan,
Looks like it's being dealt with by the right people.
Thanks for your time,
Paul.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Stefan,
Just to let you know I'll get back to this next week -- had to be called
away with work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/948291
Title:
New 12.04 beta Kernel doesn't support
Ok, so scripts/local-top/dmraid is actually executed even sooner (right
before trying to find the root fs). So it should be the right place. If
possible, I would prefer to have a look at /var/log/boot.log instead of
syslog. That seems to contain the messages that are interesting in a
clearer form.
** Attachment added: boot.log as requested.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/948291/+attachment/2839548/+files/boot.log.zip
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/948291
Darn, seems that going through the manual stage to boot does destroy (or
at least not propagate) the information that usually is there. Seems to
basically start after the raid becomes available and gets mounted. :/
Paul, maybe you can find something when you are in the busybox shell. I
would hope
Paul, ah ok, so the RAID setup is just a JBOD one (basically glueing
together the individual parts of the SSD). That explains the boot
messages (because the partition table was created over the length of the
RAID). And just a word of warning: at least in my experience grub in the
past had no
Stefan,
You were right -- tried again and exit from busybox after 'drmaid -ay'
successfully completed the boot.
As far as the raid setup, essentially that's the end result of throwing
in the 11.10 alternative cd in the machine the day it arrived with
windows installed and following the prompts.
Paul,
have not yet looked at the syslog but wanted to give an answer right
away. First, I think the potentially dangerous layout and your boot not
completing are different issues. Whenever the layout becomes an issue I
would suspect you would not even get as far as busybox without booting
from a
Stefan,
Bot sure it makes a difference, but just to confirm that the dmraid
setup is in fact a 4-disk raid0 striped set.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/948291
Title:
New 12.04 beta
Hm, ok. So its more likely that grub2 either is more capable than I
believe or gets presented a BIOS emulated device and all is magically ok
for that stage. So we should not worry too much about that part.
The syslog is a bit confusing with respect of timing. It is probably
normal because there
dmraid -r -c produces
/dev/sdd
/dev/sdc
/dev/sdb
/dev/sda
dmraid-activate does absolutely nothing. when called with /dev/sd? it
returns to the prompt with no obvious result, and in fact with any text
('-h', sadfkljadkfah, ...) it does the same.
Without parameter it does complain.
Not sure what
Looking at /sbin/dmraid-activate (in the installed system)... There
seems to be a mismatch of expectations. dmraid -r -c prints the full
path /dev/sda and so on. But dmraid-activate seems to only expect sda
and otherwise exits. I need to check whether there have been recent
changes to the
Could you try the following change to /usr/share/initramfs-tools/scripts
/init-premount/dmraid after manually having booted the 12.04 kernel:
- dmraid-activate $dev
+dmraid-activate $(basename $dev)
Then run
update-initramfs -u (this regenerates the initrd for the currently
running! kernel)
Stefan,
That file doesn't exist on my machine (but that folder exists and
contains only brltty.)
pkh@VPCSA:/usr/share/initramfs-tools$ find . -name dmraid
./scripts/local-top/dmraid
./hooks/dmraid
The dmraid in local-top seems to be equivalent:
pkh@VPCSA:/usr/share/initramfs-tools$ grep
Oh that sounds a bit as if I might still have remainders of some
fiddling around I did for either Oneiric or earlier... :/ Ok, need to
see how that looks on a fresh install and figure out how to set it
right. local-top sounds to me like something done after local fs are
mounted and that would be
This really sounds like some problem related to the construction of the initrd.
But it would be good to have some more information. One problem is that it is
that I cannot really see how the exact setup is. I would suspect sda contains
/boot (the partition table looks suspicious there, too),
Stephan,
I'm guessing the same thing re initrd. The system is a vaio vpcsa which
has hardwired onboard 4x64GB ssd. So there's only the raid, nothing
else.
I don't know how to copy/paste out of busybox, so I've taken a couple of
phone photos -- hopefully they're clear enough.
The upshot is that
** Attachment added: output of boot
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/948291/+attachment/2831508/+files/2012-03-08%2008.00.32.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: dmraid of previous, still working kernel.
https://bugs.launchpad.net/bugs/948291/+attachment/2824205/+files/dmesg.dmraidproblem
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/948291
Title:
New 12.04 beta Kernel doesn't support booting from dmraid
To manage
apport information
** Tags added: apport-collected staging
** Description changed:
After upgrading my 11.10-alternative (due to the need for dmraid)
install, the boot process stalls at the:
ubuntu
. . . . .
page and eventually kicks me out to a partial shell.
The issue
Thank you for taking the time to file a bug report on this issue.
However, given the number of bugs that the Kernel Team receives during
any development cycle it is impossible for us to review them all.
Therefore, we occasionally resort to using automated bots to request
further testing. This is
I just did a full update, re-ran dpkg-reconfigure dmrain (just to be
sure) and rebooted.
Same problem, ended up in busybox with the kernel complaining it
couldn't find the device.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because
24 matches
Mail list logo
