[->UUIDudev] 8.10>9.04 upgrade lost raid1

Here is the attachment information what I got when booting live-cd

Hey fellows...

I managed solve this problem with Google and help with a friend...

What I did is under here:

Booting from live-cd

sudo mount /dev/md0 /mnt
sudo mount -t proc none /mnt/proc
sudo mount -t devpts none /mnt/dev/pts
sudo chroot /mnt /bin/bash

sudo cp /etc/mdadm/mdadm.conf /etc/mdadm/mdadm.conf.old
grep -v ARRAY /etc/mdadm/mdadm.conf > /tmp/mdadm.conf
sudo mv /tmp/mdadm.conf /etc/mdadm/mdadm.conf
sudo mdadm --examine --scan >> /etc/mdadm/mdadm.conf
sudo update-initramfs -k all -c
exit

sudo umount /mnt/dev/pts
sudo umount /mnt/proc
sudo umount /mnt
reboot

After that Ubuntu was booted but there was problem with Gnome

Ctrl-alt-f2 I was able to go shell which tolds that I have Ubuntu 9.04

Mount command tolds me that:

/dev/md0 on /
/dev/md1 on /mnt/varmistus

uname -a told that kernel is 2.6.27-11-generic (and I believe that it should be 2.6.28....?)

ctrl-al-f1

19+0 records in
19+0 records out
kinit: name_to_dev_t (/dev/sda3) = dev(8,3)
kinit: trying to resume /dev/sda3
kinit: No resume image, doing normal boot.....

So after that:

ls /boot

I found new kernel and then:

sudo dpkg --configure -a
sudo aptitude update
sudo aptitude dist-upgrade
sudo aptitude install ubuntu-desktop
dpkg -l | grep ^r | awk '{print $2}' | xargs sudo dpkg -P

And bang.... everythis is kicking and alive...!!!

I commented on a similar bug - 330298, but probably should have commented here, since it is closer to my own situation.

I had exactly the same issue with NVidia soft RAID with a RAID1 pair.

Got the same message you got.

Realised I was still booting from kernel 2.6.27-14, but that I now also had 2.6.28-12. Asked grub to boot from 2.6.28-12 and it booted fine.

Which kernel are you using?

I managed to solve my problem:

booting LiveCD:llä and

sudo mount /dev/md0 /mnt
sudo mount -t proc none /mnt/proc
sudo mount -t devpts none /mnt/dev/pts
sudo chroot /mnt /bin/bash

sudo cp /etc/mdadm/mdadm.conf /etc/mdadm/mdadm.conf.old
grep -v ARRAY /etc/mdadm/mdadm.conf > /tmp/mdadm.conf
sudo mv /tmp/mdadm.conf /etc/mdadm/mdadm.conf
sudo mdadm --examine --scan >> /etc/mdadm/mdadm.conf
sudo update-initramfs -k all -c
exit

sudo umount /mnt/dev/pts
sudo umount /mnt/proc
sudo umount /mnt
reboot

After that Raid 1 is ok but Gnome (and X-windows) doesn't work so:

Ctrl-alt-f2 to shelliin which tolds me that Ubuntu 9.04

Mount:

/dev/md0 on /
/dev/md1 on /mnt/varmistus

uname -a: 2.6.27-11-generic (but I think it should be 2.6.28....?)

ctrl-alt-f1

19+0 records in
19+0 records out
kinit: name_to_dev_t (/dev/sda3) = dev(8,3)
kinit: trying to resume /dev/sda3
kinit: No resume image, doing normal boot.....

So... after all this:

ls /boot

I found new kernel so:

sudo dpkg --configure -a
sudo aptitude update
sudo aptitude dist-upgrade
sudo aptitude install ubuntu-desktop
dpkg -l | grep ^r | awk '{print $2}' | xargs sudo dpkg -P

And everything is ok...

Pasi

On Sat, May 9, 2009 at 3:18 PM, ggb-uk <email address hidden> wrote:

> I commented on a similar bug - 330298, but probably should have
> commented here, since it is closer to my own situation.
>
> I had exactly the same issue with NVidia soft RAID with a RAID1 pair.
>
> Got the same message you got.
>
> Realised I was still booting from kernel 2.6.27-14, but that I now also
> had 2.6.28-12. Asked grub to boot from 2.6.28-12 and it booted fine.
>
> Which kernel are you using?
>
> --
> 9.04 upgrade lose my Raid1
> https://bugs.launchpad.net/bugs/368428
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “mdadm” source package in Ubuntu: New
>
> Bug description:
> Binary package hint: mdadm
>
> I am really sorry if this bug is allready informed but I am desperate...
>
> I updated 8.10 to 9.04 via automatic update but after update process and
> restart I got this:
>
> "Gave up waiting for root device. Common problems:
>
> - Boot args (cat /proc/cmdline)
> - Check rootdelay
> - Check root
> - Missing modules (cat /proc/modules); ls /dev)
>
> ALERT /dev/md0 does not exist. Dropping to a shell..
>
> I have two Raid1 arrays md0 and md1 and I am so noob that I do not now at
> the moment what are names of the correct devices of arrays.
>
> Nothing what I can do helps!
>
> Also I am soooo noob that I have no courage to do anything now in case I am
> destroying something from the disks...
>

--

“I know it all. I just can't remember it all at once."

UUID-based raid assembly that makes mdadm.conf maintenance obsolete fixes this.