1 |
Am 14.04.2011 17:07, schrieb James: |
2 |
> Florian Philipp <lists <at> binarywings.net> writes: |
3 |
> |
4 |
> |
5 |
>> I don't think the missing partition table is your problem. |
6 |
> |
7 |
> OK, let's assume you are correct, ignoring ..... |
8 |
> |
9 |
>> However, you might be onto something with the changed sector offset. But |
10 |
>> I don't know enough of this to help you. |
11 |
> |
12 |
> Well if I have to reformat I look everything on the install. |
13 |
> Not ready to start over yet..... |
14 |
> So after a fresh reboot I see: |
15 |
> livecd ~ # cat /proc/mdstat |
16 |
> Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] |
17 |
> md125 : active (auto-read-only) raid1 sdb3[1] sda3[0] |
18 |
> 1948226512 blocks super 1.2 [2/2] [UU] |
19 |
> md126 : active (auto-read-only) raid1 sda2[0] sdb2[1] |
20 |
> 5022708 blocks super 1.2 [2/2] [UU] |
21 |
> md127 : active (auto-read-only) raid1 sda1[0] sdb1[1] |
22 |
> 262132 blocks super 1.2 [2/2] [UU] |
23 |
> |
24 |
> If you look at previous posts of mine on the md<part> |
25 |
> names, and focus on the sized, you'll see something |
26 |
> very troubling... |
27 |
> |
28 |
> The minimal CD keeps using the md125-127 names but assigns |
29 |
> them to the different partitions: |
30 |
> NOW |
31 |
> /boot is: md127 : active (auto-read-only) raid1 sda1[0] sdb1[1] |
32 |
> 262132 blocks super 1.2 [2/2] [UU] |
33 |
> |
34 |
> / is md125 : active (auto-read-only) raid1 sdb3[1] sda3[0] |
35 |
> 1948226512 blocks super 1.2 [2/2] [UU] |
36 |
> |
37 |
> swap is md126 : active (auto-read-only) raid1 sda2[0] sdb2[1] |
38 |
> 5022708 blocks super 1.2 [2/2] [UU] |
39 |
> |
40 |
> Something is morphing the numbers each time I reboot |
41 |
> with minCD.... |
42 |
> |
43 |
> So no what I put in /etc/fstab, it's going to be wrong. |
44 |
> |
45 |
|
46 |
I guess you can resort to labels or UUIDs. The real problem is the |
47 |
root=... parameter for the kernel. That's why I suggested overriding the |
48 |
auto detection and define the raids explicitly on the kernel parameter list. |
49 |
|
50 |
> grub cannot find the partition with the kernel? OR |
51 |
> is this not a problem? |
52 |
> |
53 |
|
54 |
Wild guess: Does grub maybe rely on the partition type to identify file |
55 |
system? Does it work if you change the type from 0xfd to standard 0x82? |
56 |
|
57 |
> Plus, since I'm never able to write the grub stuffage to the |
58 |
> MBR, grub nor the kernel every run..... |
59 |
> |
60 |
|
61 |
As a workaround to get your system into a usable state, you can still |
62 |
try to put /boot on a USB stick. |
63 |
|
64 |
In the past, I've also had a system where grub (whole /boot except |
65 |
kernel) was located on a floppy and then located the kernel file on the |
66 |
HDD. You could try this in order to find out whether an working grub |
67 |
still has trouble with your file system. |
68 |
|
69 |
> after rebooting I tried this step to correct for the metadata |
70 |
> problem you previously posted about: |
71 |
> |
72 |
> mdadm --create /dev/md1 --level=1 --raid-devices=2 --metadata=0.90 /dev/sda1 |
73 |
> /dev/sdb1 |
74 |
> mdadm: super0.90 cannot open /dev/sda1: Device or resource busy |
75 |
> mdadm: /dev/sda1 is not suitable for this array. |
76 |
> mdadm: super0.90 cannot open /dev/sdb1: Device or resource busy |
77 |
> mdadm: /dev/sdb1 is not suitable for this array. |
78 |
> |
79 |
> mdadm --create /dev/md127 --level=1 --raid-devices=2 --metadata=0.90 /dev/sda1 |
80 |
> /dev/sdb1 |
81 |
> mdadm: super0.90 cannot open /dev/sda1: Device or resource busy |
82 |
> mdadm: /dev/sda1 is not suitable for this array. |
83 |
> mdadm: super0.90 cannot open /dev/sdb1: Device or resource busy |
84 |
> mdadm: /dev/sdb1 is not suitable for this array. |
85 |
> |
86 |
|
87 |
Are you sure sda1 and sdb1 are not in use? Did the kernel activate the |
88 |
already present RAID? Then you have to deactivate it. Use |
89 |
mdadm --stop /dev/md* |
90 |
|
91 |
Additionally, check that you did not mount sda1 or sdb1 by accident. |
92 |
|
93 |
Hope this helps, |
94 |
Florian Philipp |