BTW did you mean that I adjust the selection in the install screens?
Well, that option is not available in ubiquity either. I could choose to
set root to nvidia_bfcdciea3 w.o. problems but the swap partitions
didn't follow the partition type setting. Swap partitions are shown
correctly in
Since the proper device (nvidia_bfcdciea) shows up in /dev/mapper it
seems that dmraid is working fine. If it isn't shown as a choice in the
installer, then it looks like a bug in Ubiquity, so I'm reassigning the
package.
** Package changed: dmraid (Ubuntu) = ubiquity (Ubuntu)
** Changed in:
Here are the views, see files_101001.zip
** Attachment added: files_101001.zip
https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/560748/+attachment/1664113/+files/files_101001.zip
--
Upgrade fails from 8.04 LTS to 10.04 LTS (beta)
https://bugs.launchpad.net/bugs/560748
You received this
I can't tell from the screen shot if you could scroll down in the disk
selection in the installer. See if you can scroll down and see just the
nvidia_bfcdciea or nvidia_bfcdciea[1234] disks. Those are what you want
to use, not the ones with -0 or -1 in them.
I think this boils down to Ubiquity
I think these are complete as such i.e. I took dmraid -n
pla_pla.txt and ls - la /dev/mapper pla_pla2.txt which are the
files in the attachment.
I am not familiar with internal structures of dmraid and ubiquity.
However, please let me know any detailed areas and commands, I am
prepared to
What is your raid configuration? I'm trying to figure out why it shows
a -0 and -1 disk that both seem to have the same partition layout.
--
Upgrade fails from 8.04 LTS to 10.04 LTS (beta)
https://bugs.launchpad.net/bugs/560748
You received this bug notification because you are a member of
It's raid 0 + 1. I've 4 identical discs. There is stripe across the
disks (raid 0) which is then mirrored (raid1). That's normal
configuration for that old nvidia chip and called as raid 0+1 to my
knowledge. As far I understand the -0 and -1 are the heads of those stripes.
On 30.9.2010
On 9/30/2010 3:55 PM, Pekka Hämäläinen wrote:
It's raid 0 + 1. I've 4 identical discs. There is stripe across the
disks (raid 0) which is then mirrored (raid1). That's normal
configuration for that old nvidia chip and called as raid 0+1 to my
knowledge. As far I understand the -0 and -1
Ok,
now I am tried the installation againg - and I can confirm that I can't
proceed the installation as disks are detected wrongly. Attachment
Fail100929.zip xontains two screenshots. 1.png shows the disk
configuration which is in this case raid 0+1. I can set the target /
partition as
I'm not sure why you came to that conclusion. If dmraid -ay said it
found and activated an array, and then you were able to see it in the
installer, then it DID activate the array. The question is, why didn't
it to so automatically? You aren't booting with the nodmraid option are
you?
--
Hello,
Yep, I was probably too hasty to draw conclusions. This is the long
version what happened.
I took the normal amd_64 bit desktop distro from Ubuntu site and made
usb startup disk out of that. Then I booted without any options. At
point when install was offered I opted that and found my
On 9/27/2010 11:54 AM, Pekka Hämäläinen wrote:
desktop - I found my way to disc partitions which were visible now -
however installer didn't allow me to install the system to wanted
existing partition nor it offered correctly swap. So - I could not
I don't understand this part. What do you
Ok
I created an installation media for 10.04.1. When I boot with this and
try to install I can't see any disc partitions. If I open terminal and
give direct command dmraid -ay and then try to install all disc
partitions are visible for selection.
So, I conclude that dmraid is not able to
Haven't had time to do that so far. Reason for trying to get this
upgrade working is that I have a server which has very similar
configuration as the desktop pc I am working now. I know for sure that
doing fresh install for the server would kill me. On this desktop the
fresh install is of course
Yes, it would be good to know if it is only an upgrade issue or not.
Also you should be able to check the package version by booting from a
livecd and chrooting into the hard disk. My question is whether you got
the version in 10.04 or 10.04.1.
--
Upgrade fails from 8.04 LTS to 10.04 LTS (beta)
Ubuntu is 10.04.1, thats the latest available.
I am working on burning the livecd (or usb) to see whether its upgrade
or dmraid. Probably doable during weekend.
On 23.9.2010 18:23, Phillip Susi wrote:
Yes, it would be good to know if it is only an upgrade issue or not.
Also you should be
here is the data:
dmraid:
Installed: 1.0.0.rc16-3ubuntu2
Candidate: 1.0.0.rc16-3ubuntu2
Version table:
*** 1.0.0.rc16-3ubuntu2 0
500 http://www.nic.funet.fi/pub/mirrors/archive.ubuntu.com/
lucid/main Packages
100 /var/lib/dpkg/status
On Thu, 2010-09-23 at 15:23 +,
Packages like FGLRX wont work upon upgrade if you have a card that is not
supported by the latest version of ATIs driver.
Running unsupported pacakges will give you errors.
I have a feeling your initramfs isn't being created properly.
If you are able to boot can you give us the version info of
Ok.
I have loaded 804 backup again and updated that with latest corrections.
So the from state is 804 as today. I will remove fglrx completely to
avoid those problems in upgrade. ATI chip is oldish, 2600 series, but
support in 804 is ok. There is separate bug-thread on this fglrx problem
(642518)
Ok, some data about upgrade
- fglrx removed, only libpam-runtime gave permanent error (bug 642591)
- run initramfs and update-grub as suggested
- dmraid version in to state
dmraid version: 1.0.0.rc16 (2009.09.16) shared
dmraid library version: 1.0.0.rc16 (2009.09.16)
What version of the dmraid package do you have installed? Check with
apt-cache policy dmraid.
--
Upgrade fails from 8.04 LTS to 10.04 LTS (beta)
https://bugs.launchpad.net/bugs/560748
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Unfortunately the system is again in unbootable mode i.e. I don't
get login prompt at all. However the following I recorded while I still
could log on:
- dmraid version in to state
dmraid version: 1.0.0.rc16 (2009.09.16) shared
dmraid library version: 1.0.0.rc16
Are you able to do a fresh install and have it boot correctly?
(To distinguish if this is an upgrade issue or a dmraid bug)
--
Upgrade fails from 8.04 LTS to 10.04 LTS (beta)
https://bugs.launchpad.net/bugs/560748
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hello
I tried upgrade from 8,04 to 10.04 again (latest fixes) w.o luck. 3 problems
were discovered
- dmraid don't activate raids after upgrade but drops to initramfs boot. I can
wait forever ...
- giving dmraid -ay and exiting initramfs gets boot continuing
However, upgrade was not clear
Yep, correct.
So far the installation is stable. Raid seems to be up and structures
behind /dev/disk are in place (problem reported in #378429).
Br Pekka
So were you able to run dmraid -ay then exit in the initramfs busybox
and continue to boot normally after that?
--
Upgrade fails from
On 5/17/2010 3:25 PM, Pekka Hämäläinen wrote:
Yep, correct.
So far the installation is stable. Raid seems to be up and structures
behind /dev/disk are in place (problem reported in #378429).
I don't think you understood my question. Every time you boot, do you
get dropped to the busybox shell
I waited at initramfs prompt for 5 - 10 minutes, didn't give any
commands, then I tried to exit.
This fails basically stating that root device is not there. Which is of
course true as it should come up with dmraid.
So, with giving explicitly the command dmraid -ay in initramfs the
system is
Lets activate this one.
Today I tried once again upgrade from 8.04 to 10.04.
Upgrade was dirty i.e. several warnings and errors were issued, none of them
were related to dmraid. Finally upgrade went through.
After reboot the system started but failed to boot properly and dropped
to initramfs.
So were you able to run dmraid -ay then exit in the initramfs busybox
and continue to boot normally after that?
--
Upgrade fails from 8.04 LTS to 10.04 LTS (beta)
https://bugs.launchpad.net/bugs/560748
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hello
I can confirm that for 2.6.32-20-generic kernel the dmraid -ay made
raid volumes active. I did not try to continue booting though.
However before I managed to get initramfs boot I needed to edit grup
menu.lst by hand. The maintainers version was faulty i.e.
root (hd0,0) -- should be
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/43796750/Dependencies.txt
--
Upgrade fails from 8.04 LTS to 10.04 LTS (beta)
https://bugs.launchpad.net/bugs/560748
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is probably a duplicate of bug #534743. Can you try booting with
the nosplash break nodmraid options, then when you hit the busybox
prompt, run dmraid -ay then exit. If the system boots up normally at
that point then it's that bug and I will mark this as a duplicate.
** Changed in: dmraid
32 matches
Mail list logo
