Attachment 8182 Details for Bug 15791 – further progress on RAID install

further progress on RAID install

RAIDbug2.txt (text/plain), 5.74 KB, created by Tony Blackwell on 2016-07-15 01:06:28 CEST

(hide)

Description:

Filename:

MIME Type:

Creator: Tony Blackwell

Created: 2016-07-15 01:06:28 CEST

Size: 5.74 KB

patch

obsolete

>A new day, and I'll go back to basics.
>42.  reboot, rescue, console.
>43. try and wipe any bad metadata on disks
>mdadm --zero-superblock /dev/sda   Unrecognised md component device - /dev/sda
>Maybe it was clean anyway.
>44. mdadm --zero-superblock /dev/sdb.  Got hash prompt with no complaints.
>45.  See where we're at: ls /dev/mapper.  Just shows the 'control' file.
>46. dmraid -ay   'no raid disks'
>46a. Found:
>http://www.intel.com.au/content/dam/www/public/us/en/documents/white-papers/rst-linux-paper.pdf
>47. Tried RAID creation with 'mdadm -C /dev/md/imsm /dev/sd[a-b] -n 2 -e imsm'
>48. response: mdadm: /dev/sda appears to be part of a raid array:
>level=raid0 devices=0 ctime=Thu Jan 1 00:00:00 1970
>mdadm: metadata will over-write last partition on /dev/sda.
>Continue creating array?
>y
>49. response: 
>mdadm: container /dev/md/imsm prepared.
>50. Try to create the RAID 0 volume /dev/md/vol0 within this imsm container:
>mdadm -C /dev/md/vol0 /dev/md/imsm -n 2 -l 0
>51 response:
>mdadm: array /dev/md/vol0 started.  Looks promising.
>52. See where we are at:  mdadm -E -s --config=mdadm.conf > /etc/mdadm.conf
>resulting file of form:
>ARRAY metadat-imsm UUID=(the string for that UUID)
>ARRAY /dev/md/vol0 container=(same string as UUID)      member=0      UUID=(different UUID string)
>53. reboot, install from USB, accepted licence.
>54.popup: HARD DRIVE DETECTION
>BIOS software RAID detected on disks /dev/sdb /dev/sda.  Activate it?
>Yes
>55. Now were're cooking on gas:
>'Here is the content of your disk drive  mapper/isw_dficfifgdb_vo (476GB)'  (there are 2x250GB SSD's)
>56 Custom disk partitioning.  The installer defaults to highlighting sdc.  (needs fixing?)
>changed it to mapper/isw_dficfifgdb_vol0
>57.  touch-to-click not working  :-(   
>58. Try and re-create my prior RAID0 partitioning.  
>This was after installing win8.1, deleting its drive 'D' , 
>resizing down its drive C and creating M5 partitions within that space.  
>59: Ctrl-Alt-F2.  gdisk
>bash: gdisk: command not found
>60. reboot, Rescue from USB, command prompt
>61 dmraid -ay
>62. response:
>RAID set "isw_dficfifgdb_vol0" was activated
>device "isw_dficfifgdb_vol0" is now registered with dmeventd for monitoring
>63. ls /dev/mapper
>control isw_dficfifgdb_vol0
>64. gdisk /dev/mapper/isw_dficfifgdb_vol0
>response: Creating new GPT entries
>100MiB type EF00 'EFI system partition' 
>900MiB type 2700 'Windows RE' 
>128 MiB type 0C01 'Microsoft reserved'
>83.1 GiB type 0700 'Microsoft basic data'
>105.6 GiB type 8300 'Linux filesystem'
>(Ha, this was the 5th partition, created successfully using gdisk so it seems).
>2.1GiB type 8300 'Linux filesystem'
>65. Problem:  My prior gdisk partitioning had out-of-order partitions at this point - see attached pic.
>I'll try and create them using proper sector numbers.
>265.1 GiB type 8300 'Linux filesystem'
>20GiB  THIS FAILED disk space not that big.  
>see  line 22 and 23 in RAIDbug1.txt.  Was I destroying my SSD at that point?
>Used the maximum sector available; 100223710 rather than 1000224767
>i.e. 20GiB, type 2700, 'Basic data partition'
>wrote these 8 partitions successfully to disk.
>
>66.  Reboot.  Install from USB (Why doesn't it detect it is booting from USB?)
>67.  Custom disk partitioning.  Click on mapper/isw_dficfifgdb_vol0.
>68. Problem: no partitions shown. That bar is grey'ed out.
>There are some tiny indentations at top and bottom of grey bar 
>which in fact represent the previous gdisk partitions, 
>and if I click at various points along the grey bar, the relevant partitions are displayed in text below.
>click along until select mapper/isw_dficfifgdb_vol0p5
>69. click on mountpoint tab, '/' shown, 'OK'
>70. ERROR You need a true filesystem (ext2,3,4, reiserfs, xfs or jfs for this mount point
>71. go back, toggle to expert mode, type ext4, up pops a red ext4 partition in middle of grey bar.
>72. Question - Why isn't the installer reading all the partition types I created previously in gdisk and displaying them graphically?
>It does know what they are as shown by the corresponding text below the selected partition.
>73. Clicked on vol0p6, -> Type, told it this was swap, came up green
>74. clicked on vol0p1, Type.  EFI fiesystem was already highlighted - just OK'd this, came up green.
>Why didn't it do this automatically on entry to graphical partitioning?
>75.  Had to manually assign vol0p1 the mount point of /boot/EFI.  Should have been automatic. 
>76. Just to be safe, manually formatted /boot/EFI from within expert mode at this point.
>Maybe should have left it unformatted to see what happens in next step.
>-This had failed previously and I don't recall if it has been fixed?  Possibly so.
>77. running the install on vol0p5, after it was automatically formatted uneventfully.
>78. Put in the root and user passwords.
>Got bootloader msg 'you decided to install the bootloader on a partition...//... On which drive are you booting?
>Didn't expect this with EFI boot, where grub2 location is predetermined.  Am I in EFI mode?  Must be...
>79 selected mapper/isw_dficfifgdb_vol080 network config failed.  had manually selected wifi, Intel 7260.
>popup: 'Unable to find network interface for selected device (using iwlwifi driver).
>80. backed out of network config, finsihed install
>81 reboot; it worked!  MCC -> partitioning; still most of partitions bar is grey'ed out; 
>just shows the EFI, root and swap partitions I'd told it about before.
>
>
>OK, at this point I do have a way to get M6 installed, and using gdisk outside the installer (from recovery boot) works.
>I'll detour to see whether Windows recovery disk can rebuild anything on this box given partitions are the same but empty.
>Plan is to then tear down the gdisk partitions entirely and try to do it all via installer - see what happens.
>Whould be showing the others graphically as well?
>
>
>
>

A new day, and I'll go back to basics.
42.  reboot, rescue, console.
43. try and wipe any bad metadata on disks
mdadm --zero-superblock /dev/sda   Unrecognised md component device - /dev/sda
Maybe it was clean anyway.
44. mdadm --zero-superblock /dev/sdb.  Got hash prompt with no complaints.
45.  See where we're at: ls /dev/mapper.  Just shows the 'control' file.
46. dmraid -ay   'no raid disks'
46a. Found:
http://www.intel.com.au/content/dam/www/public/us/en/documents/white-papers/rst-linux-paper.pdf
47. Tried RAID creation with 'mdadm -C /dev/md/imsm /dev/sd[a-b] -n 2 -e imsm'
48. response: mdadm: /dev/sda appears to be part of a raid array:
level=raid0 devices=0 ctime=Thu Jan 1 00:00:00 1970
mdadm: metadata will over-write last partition on /dev/sda.
Continue creating array?
y
49. response: 
mdadm: container /dev/md/imsm prepared.
50. Try to create the RAID 0 volume /dev/md/vol0 within this imsm container:
mdadm -C /dev/md/vol0 /dev/md/imsm -n 2 -l 0
51 response:
mdadm: array /dev/md/vol0 started.  Looks promising.
52. See where we are at:  mdadm -E -s --config=mdadm.conf > /etc/mdadm.conf
resulting file of form:
ARRAY metadat-imsm UUID=(the string for that UUID)
ARRAY /dev/md/vol0 container=(same string as UUID)      member=0      UUID=(different UUID string)
53. reboot, install from USB, accepted licence.
54.popup: HARD DRIVE DETECTION
BIOS software RAID detected on disks /dev/sdb /dev/sda.  Activate it?
Yes
55. Now were're cooking on gas:
'Here is the content of your disk drive  mapper/isw_dficfifgdb_vo (476GB)'  (there are 2x250GB SSD's)
56 Custom disk partitioning.  The installer defaults to highlighting sdc.  (needs fixing?)
changed it to mapper/isw_dficfifgdb_vol0
57.  touch-to-click not working  :-(   
58. Try and re-create my prior RAID0 partitioning.  
This was after installing win8.1, deleting its drive 'D' , 
resizing down its drive C and creating M5 partitions within that space.  
59: Ctrl-Alt-F2.  gdisk
bash: gdisk: command not found
60. reboot, Rescue from USB, command prompt
61 dmraid -ay
62. response:
RAID set "isw_dficfifgdb_vol0" was activated
device "isw_dficfifgdb_vol0" is now registered with dmeventd for monitoring
63. ls /dev/mapper
control isw_dficfifgdb_vol0
64. gdisk /dev/mapper/isw_dficfifgdb_vol0
response: Creating new GPT entries
100MiB type EF00 'EFI system partition' 
900MiB type 2700 'Windows RE' 
128 MiB type 0C01 'Microsoft reserved'
83.1 GiB type 0700 'Microsoft basic data'
105.6 GiB type 8300 'Linux filesystem'
(Ha, this was the 5th partition, created successfully using gdisk so it seems).
2.1GiB type 8300 'Linux filesystem'
65. Problem:  My prior gdisk partitioning had out-of-order partitions at this point - see attached pic.
I'll try and create them using proper sector numbers.
265.1 GiB type 8300 'Linux filesystem'
20GiB  THIS FAILED disk space not that big.  
see  line 22 and 23 in RAIDbug1.txt.  Was I destroying my SSD at that point?
Used the maximum sector available; 100223710 rather than 1000224767
i.e. 20GiB, type 2700, 'Basic data partition'
wrote these 8 partitions successfully to disk.

66.  Reboot.  Install from USB (Why doesn't it detect it is booting from USB?)
67.  Custom disk partitioning.  Click on mapper/isw_dficfifgdb_vol0.
68. Problem: no partitions shown. That bar is grey'ed out.
There are some tiny indentations at top and bottom of grey bar 
which in fact represent the previous gdisk partitions, 
and if I click at various points along the grey bar, the relevant partitions are displayed in text below.
click along until select mapper/isw_dficfifgdb_vol0p5
69. click on mountpoint tab, '/' shown, 'OK'
70. ERROR You need a true filesystem (ext2,3,4, reiserfs, xfs or jfs for this mount point
71. go back, toggle to expert mode, type ext4, up pops a red ext4 partition in middle of grey bar.
72. Question - Why isn't the installer reading all the partition types I created previously in gdisk and displaying them graphically?
It does know what they are as shown by the corresponding text below the selected partition.
73. Clicked on vol0p6, -> Type, told it this was swap, came up green
74. clicked on vol0p1, Type.  EFI fiesystem was already highlighted - just OK'd this, came up green.
Why didn't it do this automatically on entry to graphical partitioning?
75.  Had to manually assign vol0p1 the mount point of /boot/EFI.  Should have been automatic. 
76. Just to be safe, manually formatted /boot/EFI from within expert mode at this point.
Maybe should have left it unformatted to see what happens in next step.
-This had failed previously and I don't recall if it has been fixed?  Possibly so.
77. running the install on vol0p5, after it was automatically formatted uneventfully.
78. Put in the root and user passwords.
Got bootloader msg 'you decided to install the bootloader on a partition...//... On which drive are you booting?
Didn't expect this with EFI boot, where grub2 location is predetermined.  Am I in EFI mode?  Must be...
79 selected mapper/isw_dficfifgdb_vol080 network config failed.  had manually selected wifi, Intel 7260.
popup: 'Unable to find network interface for selected device (using iwlwifi driver).
80. backed out of network config, finsihed install
81 reboot; it worked!  MCC -> partitioning; still most of partitions bar is grey'ed out; 
just shows the EFI, root and swap partitions I'd told it about before.


OK, at this point I do have a way to get M6 installed, and using gdisk outside the installer (from recovery boot) works.
I'll detour to see whether Windows recovery disk can rebuild anything on this box given partitions are the same but empty.
Plan is to then tear down the gdisk partitions entirely and try to do it all via installer - see what happens.
Whould be showing the others graphically as well?

Actions: View

Attachments on bug 15791: 8175 | 8176 | 8182 | 8218