Hi,
the situation was fixed by the publication of kernel 2.6.28.11 (mid-
april of 2009).
Regards,
Thomas.
--
no block devices found after an upgrade from 8.10 to 9.04 on a soft RAID1 system
https://bugs.launchpad.net/bugs/358054
You received this bug notification because you are a member of U
This was caused because incorrect metadata in raid.
Solution was to delete old metadata and everything worked again.
--
no block devices found after an upgrade from 8.10 to 9.04 on a soft RAID1 system
https://bugs.launchpad.net/bugs/358054
You received this bug notification because you are a mem
This bug report was marked as Incomplete and has not had any updated
comments for quite some time. As a result this bug is being closed.
Please reopen if this is still an issue in the current Ubuntu release
http://www.ubuntu.com/getubuntu/download . Also, please be sure to
provide any requested in
Hi Manson,
This bug was reported a while ago and there hasn't been any activity in it
recently. We were wondering if this is still an issue? Can you try with the
latest development release of Ubuntu? ISO CD images are available from
http://cdimage.ubuntu.com/releases/ .
If it remains
** Tags added: kj-triage
--
no block devices found after an upgrade from 8.10 to 9.04 on a soft RAID1 system
https://bugs.launchpad.net/bugs/358054
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@
** Package changed: ubuntu => linux (Ubuntu)
--
no block devices found after an upgrade from 8.10 to 9.04 on a soft RAID1 system
https://bugs.launchpad.net/bugs/358054
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
There is a quite clean fix for this here:
http://ubuntuforums.org/showthread.php?t=1026461#8
Seems like dmraid is loaded at the wrong time or in the wrong way
and the script loading it was actually not made executable
Cheers
--
no block devices found after an upgrade from 8.10 to 9.04 on a sof
Ok, found my solution... but probably not for the folks that are
actually using a RAID configuration. Essentially whenever a drive has
been in a RAID configuration at one point in its life, the controller
card writes "meta data" to the last sectors of the drive. These sectors
are beyond the user-
I have this problem as well, and as the above poster commented, I do not
have any md array partitions. (The drives might have been a RAID at one
point, but they were cleaned and grub was reinstalled) I upgraded from
8.10 to 9.10... via a quick stop at 9.04. The bug appeared in 9.04 and
only by b
Hi!
I also had the same problem with a Gigabyte ga73pvm-s2h rev 1.0 mobo
previously working flawlessly with intrepid.
Now the comments above have been very helpful in understanding the
problem, and thank you for your expertise, but they actually didn't
concretely solve my problem.
I didn't have
I upgraded to ALPHA (Karmic) and the solution is not there...
¡ Do not upgrade !
I had to put the old 2.6.28-kernel image to make the system work a
little bit.
It seems that mixing 2.6.28-kernel initrd and the kernel 2.6.30 it get
so confused that can make the system work.
But this is a whol
I'm sorry. I wrote incorrect the solution. Correct spelling is dmraid.
This need a solution. Cause the whole system is unusable if you have all
your disks in RAID-1 configuration.
Have one sparse disk saved my life!
--
no block devices found after an upgrade from 8.10 to 9.04 on a soft RAID1 sy
For me this does not solve anything.
I custom compiled a new kernel and this also does not solve the problem.
I have not tried the mdadm solution. Because this is another softraid
solution. I want to use the onbios solution. dmrad.
--
no block devices found after an upgrade from 8.10 to 9.04 on
My /etc/mdadm/mdadm.conf file already listed by arrays (although using
UUID=blah instead of devices=blah). I didn't have linux-image
installed. I tried installing it but it doesn't seem to do much (I
guess because it's one of those virtual package type things?). But I
did this and it fixed my pr
Another better solution is to edit the /etc/mdadm/mdadm.conf file and add your
ARRAY variables
r...@serv02:~# cat /etc/mdadm/mdadm.conf | grep ARRAY
ARRAY /dev/md1 devices=/dev/sda1,/dev/sdb1
ARRAY /dev/md2 devices=/dev/sda2,/dev/sdb2
Then just rebuild the initramfs of the kernel you want to run,
I have _one_ idea that could explain it's gone, but I dont assume
anything: when on an old working install, you install the 2.6.28 being
running the old kernel. This runs "initramfs" on the old curent one.
When trying to boot on the new one, it brakes.
Then, after booting with the workaround, and
After the problem occured to my machine, I installed the ubuntu-package of the
vanilla-kernel
(see https://wiki.ubuntu.com/KernelMainlineBuilds)
It was Kernel v2.6.29.
After a few weeks, it worked with the ubuntu kernel, too strange.
Maybe workaround (or even solution) is to install a vanilla
Mine disappeared after a while - as I just set up this machine, I
installed some more packages and edited some configuration-files...
have no idea what caused it to go away and what caused it to appear
though.
--
no block devices found after an upgrade from 8.10 to 9.04 on a soft RAID1 system
ht
I confirm this bug.
I am using 2.6.28-11-generic on Jaunty.
I have a "/boot" on software RAID1 and the remaining FS on a software RAIDO.
I use a PackardBell Laptop with 2 HDD.
The workaround is OK, but I have to type it each boot.
Please advice.
--
no block devices found after an upgrade from
Same for me with 2.6.28-11
no block devices found
/dev/md0 does not exist
best workaround from 0815: "mdadm --assemble --scan; exit"
please post solutions, thanks!
--
no block devices found after an upgrade from 8.10 to 9.04 on a soft RAID1 system
https://bugs.launchpad.net/bugs/358054
You r
Have the same issue. Tried all workarounds I found on the web. It's
really frustrating that I can boot Ubuntu 9.04 2.6.28-11 ONLY by typing
"mdadm --assemble --scan; exit" in the busybox.
If anybody out there finds a solution please post!
Thanx
--
no block devices found after an upgrade from 8.
This is still happening for me even with 2.6.28-11. I get dropped to a
shell each time I boot. I type "mdadm -As ; exit" and it activates my
raid arrays and continues booting normally. Is this supposed to happen
automatically somewhere as part of the boot process? Is there a config
file I shoul
Doesn't work with vmlinuz-2.6.28-11-server.
** Attachment added: "output of lshw (when booted with another kernel)"
http://launchpadlibrarian.net/25990369/lshw
--
no block devices found after an upgrade from 8.10 to 9.04 on a soft RAID1 system
https://bugs.launchpad.net/bugs/358054
You receiv
For me, it wors again too, with the last kernel update it works.
I can still see the "no block devices found" for time if I switch back
to the first tty, but it boot normally.
--
no block devices found after an upgrade from 8.10 to 9.04 on a soft RAID1 system
https://bugs.launchpad.net/bugs/3580
For me it works again with the ubuntu default kernel 2.6.28-11-generic.
I changed nothing, just did an upgrade.
The disks are available with /dev/md0 and /dev/md1.
--
no block devices found after an upgrade from 8.10 to 9.04 on a soft RAID1 system
https://bugs.launchpad.net/bugs/358054
You recei
We're having exactly the same problem on a headless server.
temporary workaround: use an older kernel. Searching the net for other
solutions...
--
no block devices found after an upgrade from 8.10 to 9.04 on a soft RAID1 system
https://bugs.launchpad.net/bugs/358054
You received this bug notifi
More news:
I rebooted my system and looked in the grub menu (hit ESC) at the prompt. It
listed 2 kernels for ubuntu 9.04.
2.6.28
2.6.27
I choose the second one and got dropped into the same recovery shell.
But this time, mdadm was able to build my array WITHOUT loopback
workarounds! It does howe
!! Sorry!!
I posted a bad workaround - it should read:
Temporary workaround:
When boot fails and drops you into a shell, do this (device names will differ
for you):
losetup /dev/loop1 /dev/sdb1
losetup /dev/loop2 /dev/sdc1
mdadm --assemble /dev/md/0 /dev/loop1 /dev/loop2
And the missing
This bug happened to me also when upgrading 8.10 to 9.04 (with do-
release-upgrade). Definately a buggy kernel.
Asus motherboard (not sure of exact - can get if needed) with RAID hardware
disabled.
2 SATA hard disks as /dev/sdb and /dev/sdc
Fails to boot due to a failure to start the RAID.
Issue
I confirm this.
Mainboard is Gigabyte GA-P35-DS4, Raid disabled, ahci enabled.
2 Sata Drives:
Boot paritition raid 1 (md0)
Root partition raid 0 (md1)
I ran jaunty for some weeks. After yesterday's update, it drops to busybox
because /dev/md1 can't be found.
In /dev there are no devices. No sda
I've succeeded in booting my system like before the upgrade (with kde...) .
On busybox console,
I typed :
mdadm -As (--assemble --scan)
so that it create /dev/mdX devices.
then type exit and it resume the boot process, which succeed as the raid
device are up.
but this won't fix the problem
Also on mdadm --assemble --scan
the two first line I get before i see my mdX devices created are :
mdadm: CREATE user root not found
mdadm: CREATE group disk not found
I don't know if it's wrong or not...
--
no block devices found after an upgrade from 8.10 to 9.04 on a soft RAID1 system
https
with
mdadm --assemble --scan
I get the md 0,1,2,3 of my system
So I tryed to chroot and reinstall grub :
mkdir /mnt
mount -t ext3 /dev/md3 /mnt
mount -o bind /dev /mnt/dev
mount -t proc none /mnt/proc
mount -t sysfs none /mnt/sys
mount -t ext2 /dev/md0 /mnt/boot
mount -t ext3 /dev/md2 /mnt/var
also on setup(hd0) grub tells that he didn't find stag1 (but found the
others)
--
no block devices found after an upgrade from 8.10 to 9.04 on a soft RAID1 system
https://bugs.launchpad.net/bugs/358054
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
>I've tryed to reboot with the fake raid for windows disabled (as it was in
>troubleshouting). no change.
(disabled in the bios)
Note that gparted still saw the hard drives so maybe I've to retry with the
drives unplugged
--
no block devices found after an upgrade from 8.10 to 9.04 on a soft RA
35 matches
Mail list logo
