| 1 |
Florian Philipp <lists <at> binarywings.net> writes: |
| 2 |
|
| 3 |
|
| 4 |
> I don't think the missing partition table is your problem. |
| 5 |
|
| 6 |
OK, let's assume you are correct, ignoring ..... |
| 7 |
|
| 8 |
> However, you might be onto something with the changed sector offset. But |
| 9 |
> I don't know enough of this to help you. |
| 10 |
|
| 11 |
Well if I have to reformat I look everything on the install. |
| 12 |
Not ready to start over yet..... |
| 13 |
So after a fresh reboot I see: |
| 14 |
livecd ~ # cat /proc/mdstat |
| 15 |
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] |
| 16 |
md125 : active (auto-read-only) raid1 sdb3[1] sda3[0] |
| 17 |
1948226512 blocks super 1.2 [2/2] [UU] |
| 18 |
md126 : active (auto-read-only) raid1 sda2[0] sdb2[1] |
| 19 |
5022708 blocks super 1.2 [2/2] [UU] |
| 20 |
md127 : active (auto-read-only) raid1 sda1[0] sdb1[1] |
| 21 |
262132 blocks super 1.2 [2/2] [UU] |
| 22 |
|
| 23 |
If you look at previous posts of mine on the md<part> |
| 24 |
names, and focus on the sized, you'll see something |
| 25 |
very troubling... |
| 26 |
|
| 27 |
The minimal CD keeps using the md125-127 names but assigns |
| 28 |
them to the different partitions: |
| 29 |
NOW |
| 30 |
/boot is: md127 : active (auto-read-only) raid1 sda1[0] sdb1[1] |
| 31 |
262132 blocks super 1.2 [2/2] [UU] |
| 32 |
|
| 33 |
/ is md125 : active (auto-read-only) raid1 sdb3[1] sda3[0] |
| 34 |
1948226512 blocks super 1.2 [2/2] [UU] |
| 35 |
|
| 36 |
swap is md126 : active (auto-read-only) raid1 sda2[0] sdb2[1] |
| 37 |
5022708 blocks super 1.2 [2/2] [UU] |
| 38 |
|
| 39 |
Something is morphing the numbers each time I reboot |
| 40 |
with minCD.... |
| 41 |
|
| 42 |
So no what I put in /etc/fstab, it's going to be wrong. |
| 43 |
|
| 44 |
grub cannot find the partition with the kernel? OR |
| 45 |
is this not a problem? |
| 46 |
|
| 47 |
Plus, since I'm never able to write the grub stuffage to the |
| 48 |
MBR, grub nor the kernel every run..... |
| 49 |
|
| 50 |
after rebooting I tried this step to correct for the metadata |
| 51 |
problem you previously posted about: |
| 52 |
|
| 53 |
mdadm --create /dev/md1 --level=1 --raid-devices=2 --metadata=0.90 /dev/sda1 |
| 54 |
/dev/sdb1 |
| 55 |
mdadm: super0.90 cannot open /dev/sda1: Device or resource busy |
| 56 |
mdadm: /dev/sda1 is not suitable for this array. |
| 57 |
mdadm: super0.90 cannot open /dev/sdb1: Device or resource busy |
| 58 |
mdadm: /dev/sdb1 is not suitable for this array. |
| 59 |
|
| 60 |
mdadm --create /dev/md127 --level=1 --raid-devices=2 --metadata=0.90 /dev/sda1 |
| 61 |
/dev/sdb1 |
| 62 |
mdadm: super0.90 cannot open /dev/sda1: Device or resource busy |
| 63 |
mdadm: /dev/sda1 is not suitable for this array. |
| 64 |
mdadm: super0.90 cannot open /dev/sdb1: Device or resource busy |
| 65 |
mdadm: /dev/sdb1 is not suitable for this array. |
Archives