------- Comment From [email protected] 2015-08-27 15:48 EDT-------
Venkat,

Please detail your partitioning steps, and the daily build used.

I cannot create a PReP partition on the RAID1 device with the 0826
build, hitting a partitioner error, but according to your logs you could
successfully create it.

Thanks!

For the record, I did read and tried [1] :) adapting for powerpc, which 
requires a PReP partition.
The change of bootable flag is not working.

Here's what I got:

Steps to reproduce
------------------

QEMU/KVM with 2 drives (sda/sdb).
wily ppc64el daily ISO of 0826.

At Partitioner dialog..

Select sda
Create new empty partition table: Yes
Select sda's free space
Automatically partition free space

Select sdb
Create new empty partition table: Yes
Select sdb's free space
Automatically partition free space

Select Configure Software RAID
Changes written to storage devices: Yes

Create MD Device
RAID 1
Number of active devices for RAID1 array: 2
Number of spare devices for RAID1 array: 2
Select sda1 and sdb1
Continue
Write changes: Yes

Create MD Device
RAID 1
Number of active devices for RAID1 array: 2
Number of spare devices for RAID1 array: 2
Select sda2 and sdb2
Continue
Write changes: Yes

Create MD Device
RAID 1
Number of active devices for RAID1 array: 2
Number of spare devices for RAID1 array: 2
Select sda3 and sdb3
Continue
Write changes: Yes

Select Finish (instead of Create MD Device)

Under  RAID1 device #0 - 7.3 MB, Select #1
Use as: PowerPC PReP Partition

Boom:
????? [!!] Partition disks ?????
?                              ?
?           ???  ???           ?
?                              ?
?     <Go Back> <Continue>     ?
?                              ?
????????????????????????????????

Here I stopped to collect the logs, as below.
Go Back
Go Back
Go Back
Execute a shell

On another installation I tried to go without creating a PReP partition,
and the installer refuses to proceed, as required.

????????????? [!!] Partition disks ?????????????
?                                              ?
? No PowerPC PReP boot partition is found.     ?
?                                              ?
? Go back to the menu and resume partitioning? ?
?                                              ?
?     <Go Back>              <Yes>    <No>     ?
?                                              ?
????????????????????????????????????????????????

If I try to create the PReP partition, the error above always happen,
and the 'Finish partitioning and write changes to disk' always loop back
to the same partitioning main dialog.

The logs indicate a fatal error in parted-server, as the output fifo to
it is not available anymore.

~ # sed -n "/Menu item 'partman-base' selected/,\$ p" /var/log/syslog
Aug 27 15:21:02 main-menu[243]: INFO: Menu item 'partman-base' selected
Aug 27 15:21:02 kernel: [   87.706971] ntfs: driver 2.1.32 [Flags: R/O MODULE].
Aug 27 15:21:02 kernel: [   87.743448] Btrfs loaded
Aug 27 15:21:02 kernel: [   87.764176] JFS: nTxBlock = 2036, nTxLock = 16293
Aug 27 15:21:02 kernel: [   87.794723] SGI XFS with ACLs, security attributes, 
realtime, no debug enabled
Aug 27 15:21:02 md-devices: mdadm: No arrays found in config file or 
automatically
Aug 27 15:21:03 partman:   No matching physical volumes found
Aug 27 15:21:03 partman:   Reading all physical volumes.  This may take a 
while...
Aug 27 15:24:17 kernel: [  282.811550] Adding 5492672k swap on /dev/sdb3.  
Priority:-1 extents:1 across:5492672k FS
Aug 27 15:24:17 partman: mke2fs 1.42.12 (29-Aug-2014)
Aug 27 15:24:24 partman-md: mdadm: No arrays found in config file or 
automatically
Aug 27 15:25:21 kernel: [  346.670427] Adding 5492672k swap on /dev/sdb3.  
Priority:-1 extents:1 across:5492672k FS
Aug 27 15:25:21 partman-md: mdadm: No arrays found in config file or 
automatically
Aug 27 15:25:21 partman-md: Selected spare count: 0
Aug 27 15:25:21 partman-md: RAID devices count: 2
Aug 27 15:25:21 partman-md: Spare devices count: 0
Aug 27 15:25:21 partman-md: mdadm: Note: this array has metadata at the start 
and
Aug 27 15:25:21 partman-md:     may not be suitable as a boot device.  If you 
plan to
Aug 27 15:25:21 partman-md:     store '/boot' on this device please ensure that
Aug 27 15:25:21 partman-md:     your boot-loader understands md/v1.x metadata, 
or use
Aug 27 15:25:21 partman-md:     --metadata=0.90
Aug 27 15:25:21 partman-md: mdadm: Defaulting to version 1.2 metadata
Aug 27 15:25:21 kernel: [  346.811654] md: bind<sda1>
Aug 27 15:25:21 partman-md: mdadm: array /dev/md/0 started.
Aug 27 15:25:21 kernel: [  346.811873] md: bind<sdb1>
Aug 27 15:25:21 kernel: [  346.813197] md/raid1:md0: not clean -- starting 
background reconstruction
Aug 27 15:25:21 kernel: [  346.813200] md/raid1:md0: active with 2 out of 2 
mirrors
Aug 27 15:25:21 kernel: [  346.813228] md0: detected capacity change from 0 to 
7274496
Aug 27 15:25:21 kernel: [  346.818078] md: resync of RAID array md0
Aug 27 15:25:21 kernel: [  346.818082] md: minimum _guaranteed_  speed: 1000 
KB/sec/disk.
Aug 27 15:25:21 kernel: [  346.818084] md: using maximum available idle IO 
bandwidth (but not more than 200000 KB/sec) for resync.
Aug 27 15:25:21 kernel: [  346.818087] md: using 2048k window, over a total of 
7104k.
Aug 27 15:25:22 kernel: [  347.518131] md: md0: resync done.
Aug 27 15:25:22 kernel: [  347.604398] RAID1 conf printout:
Aug 27 15:25:22 kernel: [  347.604401]  --- wd:2 rd:2
Aug 27 15:25:22 kernel: [  347.604404]  disk 0, wo:0, o:1, dev:sda1
Aug 27 15:25:22 kernel: [  347.604407]  disk 1, wo:0, o:1, dev:sdb1
Aug 27 15:26:23 kernel: [  408.340841] Adding 5492672k swap on /dev/sdb3.  
Priority:-1 extents:1 across:5492672k FS
Aug 27 15:26:23 partman-md: Selected spare count: 0
Aug 27 15:26:23 partman-md: RAID devices count: 2
Aug 27 15:26:23 partman-md: Spare devices count: 0
Aug 27 15:26:23 partman-md: mdadm: Note: this array has metadata at the start 
and
Aug 27 15:26:23 partman-md:     may not be suitable as a boot device.  If you 
plan to
Aug 27 15:26:23 partman-md:     store '/boot' on this device please ensure that
Aug 27 15:26:23 partman-md:     your boot-loader understands md/v1.x metadata, 
or use
Aug 27 15:26:23 partman-md:     --metadata=0.90
Aug 27 15:26:23 partman-md: mdadm: /dev/sdb2 appears to contain an ext2fs file 
system
Aug 27 15:26:23 partman-md:        size=128715776K  mtime=Thu Jan  1 00:00:00 
1970
Aug 27 15:26:23 partman-md: mdadm: Defaulting to version 1.2 metadata
Aug 27 15:26:23 kernel: [  408.459252] md: bind<sda2>
Aug 27 15:26:23 kernel: [  408.459383] md: bind<sdb2>
Aug 27 15:26:23 kernel: [  408.460141] md/raid1:md1: not clean -- starting 
background reconstruction
Aug 27 15:26:23 kernel: [  408.460143] md/raid1:md1: active with 2 out of 2 
mirrors
Aug 27 15:26:23 kernel: [  408.460231] created bitmap (1 pages) for device md1
Aug 27 15:26:23 kernel: [  408.460429] md1: bitmap initialized from disk: read 
1 pages, set 1964 of 1964 bits
Aug 27 15:26:23 partman-md: mdadm: array /dev/md/1 started.
Aug 27 15:26:23 kernel: [  408.474992] md1: detected capacity change from 0 to 
131737845760
Aug 27 15:26:23 kernel: [  408.479162] md: resync of RAID array md1
Aug 27 15:26:23 kernel: [  408.479164] md: minimum _guaranteed_  speed: 1000 
KB/sec/disk.
Aug 27 15:26:23 kernel: [  408.479165] md: using maximum available idle IO 
bandwidth (but not more than 200000 KB/sec) for resync.
Aug 27 15:26:23 kernel: [  408.479167] md: using 2048k window, over a total of 
128650240k.
Aug 27 15:27:04 partman-md: Selected spare count: 0
Aug 27 15:27:04 partman-md: RAID devices count: 2
Aug 27 15:27:04 partman-md: Spare devices count: 0
Aug 27 15:27:04 partman-md: mdadm: Note: this array has metadata at the start 
and
Aug 27 15:27:04 partman-md:     may not be suitable as a boot device.  If you 
plan to
Aug 27 15:27:04 partman-md:     store '/boot' on this device please ensure that
Aug 27 15:27:04 partman-md:     your boot-loader understands md/v1.x metadata, 
or use
Aug 27 15:27:04 partman-md:     --metadata=0.90
Aug 27 15:27:04 partman-md: mdadm: Defaulting to version 1.2 metadata
Aug 27 15:27:06 partman-md: mdadm: array /dev/md/2 started.
Aug 27 15:27:06 kernel: [  451.092328] md: bind<sda3>
Aug 27 15:27:06 kernel: [  451.092668] md: bind<sdb3>
Aug 27 15:27:06 kernel: [  451.094600] md/raid1:md2: not clean -- starting 
background reconstruction
Aug 27 15:27:06 kernel: [  451.094604] md/raid1:md2: active with 2 out of 2 
mirrors
Aug 27 15:27:06 kernel: [  451.094631] md2: detected capacity change from 0 to 
5620367360
Aug 27 15:27:06 kernel: [  451.097574] md: delaying resync of md2 until md1 has 
finished (they share one or more physical units)
Aug 27 15:27:33 kernel: [  478.728257] md: delaying resync of md2 until md1 has 
finished (they share one or more physical units)
Aug 27 15:27:34 kernel: [  479.097373] md: delaying resync of md2 until md1 has 
finished (they share one or more physical units)
Aug 27 15:27:34 kernel: [  479.329679] md: delaying resync of md2 until md1 has 
finished (they share one or more physical units)
Aug 27 15:27:35 kernel: [  480.096801] md: delaying resync of md2 until md1 has 
finished (they share one or more physical units)
Aug 27 15:27:38 kernel: [  483.069130] md: delaying resync of md2 until md1 has 
finished (they share one or more physical units)
Aug 27 15:27:38 kernel: [  483.563174] md: delaying resync of md2 until md1 has 
finished (they share one or more physical units)
Aug 27 15:27:48 kernel: [  493.760479] md: delaying resync of md2 until md1 has 
finished (they share one or more physical units)
Aug 27 15:27:49 kernel: [  494.324866] md: delaying resync of md2 until md1 has 
finished (they share one or more physical units)
Aug 27 15:29:07 main-menu[243]: (process:12707): sh: 4194304: unknown operand
Aug 27 15:29:07 main-menu[243]: (process:12707): /lib/partman/visual.d/10type:
Aug 27 15:29:07 main-menu[243]: (process:12707): line 16:
Aug 27 15:29:07 main-menu[243]: (process:12707): can't open 
/var/lib/partman/outfifo: no such file
Aug 27 15:29:07 main-menu[243]: (process:12707):
Aug 27 15:29:07 main-menu[243]: (process:12707): /lib/partman/visual.d/35name:
Aug 27 15:29:07 main-menu[243]: (process:12707): line 16:
Aug 27 15:29:07 main-menu[243]: (process:12707): can't open 
/var/lib/partman/outfifo: no such file
Aug 27 15:29:07 main-menu[243]: (process:12707):
Aug 27 15:29:07 main-menu[243]: (process:12707): 
/lib/partman/active_partition/10change_name/choices:
Aug 27 15:29:07 main-menu[243]: (process:12707): line 9:
Aug 27 15:29:07 main-menu[243]: (process:12707): can't open 
/var/lib/partman/outfifo: no such file
Aug 27 15:29:07 main-menu[243]: (process:12707):
Aug 27 15:29:07 main-menu[243]: (process:12707): 
/lib/partman/active_partition/65toggle_bootable/choices:
Aug 27 15:29:07 main-menu[243]: (process:12707): line 11:
Aug 27 15:29:07 main-menu[243]: (process:12707): can't open 
/var/lib/partman/outfifo: no such file
Aug 27 15:29:07 main-menu[243]: (process:12707):
Aug 27 15:29:07 main-menu[243]: (process:12707): 
/lib/partman/active_partition/80resize/choices:
Aug 27 15:29:07 main-menu[243]: (process:12707): line 9:
Aug 27 15:29:07 main-menu[243]: (process:12707): can't open 
/var/lib/partman/outfifo: no such file
Aug 27 15:29:07 main-menu[243]: (process:12707):
Aug 27 15:29:07 main-menu[243]: (process:12707): 
/lib/partman/active_partition/85erasepart/choices:
Aug 27 15:29:07 main-menu[243]: (process:12707): line 9:
Aug 27 15:29:07 main-menu[243]: (process:12707): can't open 
/var/lib/partman/outfifo: no such file
Aug 27 15:29:07 main-menu[243]: (process:12707):
Aug 27 15:29:07 main-menu[243]: (process:12707): 
/lib/partman/active_partition/87delete/choices:
Aug 27 15:29:07 main-menu[243]: (process:12707): line 9:
Aug 27 15:29:07 main-menu[243]: (process:12707): can't open 
/var/lib/partman/outfifo: no such file
Aug 27 15:29:07 main-menu[243]: (process:12707):
Aug 27 15:29:07 main-menu[243]: (process:12707): 
/lib/partman/choose_partition/25md/choices:
Aug 27 15:29:07 main-menu[243]: (process:12707): line 9:
Aug 27 15:29:07 main-menu[243]: (process:12707): can't open 
/var/lib/partman/outfifo: no such file
Aug 27 15:29:07 main-menu[243]: (process:12707):
Aug 27 15:29:07 main-menu[243]: (process:12707): 
/lib/partman/choose_partition/30lvm/choices:
Aug 27 15:29:07 main-menu[243]: (process:12707): line 10:
Aug 27 15:29:07 main-menu[243]: (process:12707): can't open 
/var/lib/partman/outfifo: no such file
Aug 27 15:29:07 main-menu[243]: (process:12707):
Aug 27 15:29:07 main-menu[243]: (process:12707): 
/lib/partman/choose_partition/35crypto/choices:
Aug 27 15:29:07 main-menu[243]: (process:12707): line 7:
Aug 27 15:29:07 main-menu[243]: (process:12707): can't open 
/var/lib/partman/outfifo: no such file
Aug 27 15:29:07 main-menu[243]: (process:12707):
Aug 27 15:29:07 main-menu[243]: (process:12707): 
/lib/partman/choose_partition/60partition_tree/choices: line 5: can't open 
/var/lib/partman/outfifo: no such file
Aug 27 15:29:07 main-menu[243]: INFO: Menu item 'partman-base' succeeded but 
requested to be left unconfigured.
Aug 27 15:29:16 main-menu[243]: INFO: Menu item 'di-utils-shell' selected

[1] https://help.ubuntu.com/lts/serverguide/advanced-installation.html

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1487365

Title:
  Ubuntu14.04 .3 RAID installation fails on firestone

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1487365/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to