I needed to get the install done so I went ahead and did a more normal
install with '/boot/efi' in an normal partition on the first disk. After
the install, I created a matching partition on the second drive, copied the
/boot/efi partition to that and then created a (degraded RAID) on the first
drive. (At this point I had destroyed /dev/md0 and recreated it.) I then
copied the data back to the RAID partition on the first drive, unmounted
the partition on the second and added it to complete the RAID1. The
partition was created as /dev/md0 (using 0.90 metadata) and after reboot
came up as /dev/md127. Other than that, it seems to work. Surprisingly the
block ID for /dev/md127 and the original EXT4 /boot/efi matched. But this
is all after the crash that triggered the bug report.
The command used to create the RAID device would have used the same
parameters as
root@androidlx01:~# mdadm --create /dev/md0 --metadata=0.90 -l raid1 -f -n
1 /dev/sda1
mdadm: /dev/sda1 appears to be part of a raid array:
level=raid0 devices=0 ctime=Wed Dec 31 19:00:00 1969
Continue creating array? y
mdadm: array /dev/md0 started.
root@androidlx01:~# cat /proc/mdstat
Personalities : [raid1]
md0 : active raid1 sda1[0]
524224 blocks [1/1] [U]
unused devices: <none>
The existing RAID is
androidadmin@androidlx01:~$ sudo mdadm -D /dev/md127
/dev/md127:
Version : 0.90
Creation Time : Tue Oct 31 15:55:49 2017
Raid Level : raid1
Array Size : 524224 (512.02 MiB 536.81 MB)
Used Dev Size : 524224 (512.02 MiB 536.81 MB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 127
Persistence : Superblock is persistent
Update Time : Fri Nov 10 15:33:49 2017
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
UUID : 498041b2:09e636ad:d8fca355:d4d345d0 (local to host
androidlx01)
Events : 0.40
Number Major Minor RaidDevice State
0 8 1 0 active sync /dev/sda1
1 8 17 1 active sync /dev/sdb1
androidadmin@androidlx01:~$
On Tue, Oct 17, 2017 at 8:36 AM, Phillip Susi <ps...@ubuntu.com> wrote:
> Can you post the output of mdadm -D /dev/md0?
>
>
> ** Changed in: grub-installer (Ubuntu)
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1721317
>
> Title:
> graphical installer crashed.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/grub-installer/
> +bug/1721317/+subscriptions
>
--
'03 BMW F650CS - hers
'98 Dakar K12RS - "BABY K" grew up.
'93 R100R w/ Velorex 700 (MBD starts...)
'95 Miata - "OUR LC"
polish visor: apply squashed bugs, rinse, repeat
Beautiful Sunny Winfield, Illinois
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721317
Title:
graphical installer crashed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1721317/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
