1 |
On Tue, Jun 25, 2013 at 5:51 PM, Mark Knecht <markknecht@×××××.com> wrote: |
2 |
> This is related to my thread from a few days ago about the |
3 |
> disappointing speed of my RAID6 root partition. The goal here is to |
4 |
> get the machine booting from an SSD so that I can free up my five hard |
5 |
> drives to play with. |
6 |
> |
7 |
> SHORT SUMMATION: I've tried noninitrd and noraid in the kernel line of |
8 |
> grub.conf but I keep booting from old RAID instead of the new SSD. |
9 |
> What am I doing wrong? |
10 |
|
11 |
Here are some things I would try to narrow it down: |
12 |
|
13 |
Put raid=noautodetect on your kernel commandline to prevent the kernel |
14 |
from auto-assembling the array |
15 |
|
16 |
It sounds like you are pretty sure it is at least using the boot |
17 |
sector of the new drive, so I am thinking it is possible there is some |
18 |
weird combination of using a boot sector from one drive to get you |
19 |
into the boot partition of another drive. If the old boot drive is |
20 |
still attached, you could try moving/renaming the grub config or whole |
21 |
grub folder on the old boot drive to make sure it's not getting used. |
22 |
|
23 |
If that doesn't give any clues, I would physically unplug the cable of |
24 |
every drive other than the SSD (if that is realistic based on your |
25 |
filesystem layout) and see how far it gets. Maybe if it fails you can |
26 |
figure out what it's trying to access on the other disks. |
27 |
|
28 |
As far as the RAID I think there are at least a few different ways an |
29 |
mdraid array comes to be assembled: |
30 |
- your initramfs does it |
31 |
- your kernel does it (only for a RAID with v0.90 superblock) |
32 |
- init script does it (/etc/init.d/mdraid) |
33 |
- udev does it (/lib64/udev/rules.d/64-md-raid.rules) |
34 |
- you manually do it later on using mdadm |
35 |
|
36 |
Viewing dmesg output from around the point where boot begins and the |
37 |
RAID is assembled might give you some clues about who's doing what. |
38 |
|
39 |
I recently upgraded my machine and disks and am using UUID and labels |
40 |
for everything, I can literally boot from either the old HDD or new |
41 |
HDD from my BIOS boot menu, plugging them into the motherboard in any |
42 |
order, and either one will work properly, even though the /dev/sdX |
43 |
assignments might change from boot to boot. You can use the blkid |
44 |
command (as root) to see the labels and UUIDs for all of your drives |
45 |
and partitions. |
46 |
|
47 |
Good luck, |
48 |
Paul |