** Changed in: dmraid (Ubuntu)
Status: Incomplete => Invalid
** Changed in: dmraid (Ubuntu)
Status: Invalid => Fix Released
--
More on RAID 1 issues (RAID1 + DMRAID) = No boot possible
https://bugs.launchpad.net/bugs/396078
You received this bug notification because you are a membe
Ok then!
Thank you very very much as this was a long standing bug that drove me
crazy.
Thanks again
--
More on RAID 1 issues (RAID1 + DMRAID) = No boot possible
https://bugs.launchpad.net/bugs/396078
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
dmraid has a switch to specify which type of metadata you are talking
about ( I think it was -f, check the man page ). If you want the sil
removed, then specify that.
--
More on RAID 1 issues (RAID1 + DMRAID) = No boot possible
https://bugs.launchpad.net/bugs/396078
You received this bug notific
Yesss!!! That solved the problem.
but I was not able to remove only the sil metadata. I had to remove the
nvidia first and sil after.
I wanted to leave the nvidia metadata to be able to run it as a raid1 in
degraded mode. But that was not possible because the erase order.
But anyway I can always
As I said before, with dmraid -E. Be careful running this as you don't
want to destroy the signatures on the disks that are meant to be in a
raid, only the one you meant to be stand alone.
--
More on RAID 1 issues (RAID1 + DMRAID) = No boot possible
https://bugs.launchpad.net/bugs/396078
You rec
That's not possible as they were new disks when installed on this
computer.
Anyway, do you know how to remove those incorrect signatures?
Thank you
--
More on RAID 1 issues (RAID1 + DMRAID) = No boot possible
https://bugs.launchpad.net/bugs/396078
You received this bug notification because you
It looks like your disks have old raid signatures on the drives from
previous use in other controllers. This is a system misconfiguration.
You should remove any incorrect signatures from the disks with dmraid
-E.
** Changed in: dmraid (Ubuntu)
Status: New => Incomplete
--
More on RAID 1
yep.
in released 9.10 after upgrade from 9.04 i cannot boot :) /dev/mapper/ clean as
baby ;)
try dmraid -ay;exit in busybox in few days.
--
More on RAID 1 issues (RAID1 + DMRAID) = No boot possible
https://bugs.launchpad.net/bugs/396078
You received this bug notification because you are a member
Is the bug still there with the latest kernel and dmraid package?
--
More on RAID 1 issues (RAID1 + DMRAID) = No boot possible
https://bugs.launchpad.net/bugs/396078
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Sorry, I was out of the city for a while.
I have to say that I cannot reach gdm if I boot with current kernel
config. So I have to do a special mix of old initrd + new kernel.
I'm sorry but cannot reformat. I have currently two systems with this
problem.
Anyway I will put the output.
r...@azul
For starters it looks like you hjave used sdc in a silicon image and nvidia
RAID array.
If the array boots upto GDM (I assume you are booting off the array entirely)
then dmraid is active and something else is borking your system.
Is it possible for you to completely reformat the drives and star
It seems that vmlinuz-2.6.31-2-generic is able to boot after block some
minutes with the screen in the screenshot 1.
No longer "no block devices found" message.
But something makes the system hang after gdm startup
--
More on RAID 1 issues (RAID1 + DMRAID) = No boot possible
https://bugs.launch
** Attachment added: "This screenshot shows system booting with my initram but
strange dm-linear not found..."
http://launchpadlibrarian.net/28729869/2009-06-18%2015.56.08.jpg
--
More on RAID 1 issues (RAID1 + DMRAID) = No boot possible
https://bugs.launchpad.net/bugs/396078
You received thi
** Attachment added: "This screenshots shows sdb? blocked so no raid can be
activated"
http://launchpadlibrarian.net/28729835/2009-07-03%2012.44.44.jpg
--
More on RAID 1 issues (RAID1 + DMRAID) = No boot possible
https://bugs.launchpad.net/bugs/396078
You received this bug notification becau
14 matches
Mail list logo
