1 |
Lindsay Haisley wrote: |
2 |
> I recently tried a badly needed kernel upgrade on my desktop system, |
3 |
> moving from kernel 2.6.23-gentoo-r3 to kernel 2.6.29-gentoo-r5. This |
4 |
> also required an upgrade of udev from 141 to 151-r4. When I rebooted |
5 |
> the box there was no /dev/hda4 which is normally the root filesystem, |
6 |
> and instead what was the root filesystem had a device name of, I |
7 |
> believe, "rootfs" in the kernel mount table which had the same files. A |
8 |
> number of other mounts were gone as well (there was no /dev/hda at all, |
9 |
> which has several partitions). |
10 |
> |
11 |
> The boot-up stumbled to a halt at a maintenance mode prompt with the |
12 |
> root filesystem mounted R/O and of course no gnome desktop. I could use |
13 |
> mount -o remount,rw / to make the root filesystem RW, which allowed me |
14 |
> to re-emerge an earlier version of udev and boot to the previous kernel, |
15 |
> but I'm stuck with an aging kernel, and other tools depend on a kernel |
16 |
> and udev upgrade so sooner or later I'm going to be just, plain, |
17 |
> stuck :( |
18 |
> |
19 |
> The drive setup is a bit complex. The actual hard drive mounting |
20 |
> (excluding things like proc, udev, devpts, etc.) look like: |
21 |
> |
22 |
> /dev/hda4 on / type reiserfs (rw,noatime) |
23 |
> /dev/mapper/main_vg-fmouse on /home/fmouse type reiserfs (rw,noatime,notail) |
24 |
> /dev/hda1 on /home/fmouse/win98 type reiserfs (rw,noatime,notail) |
25 |
> /dev/mapper/main_vg-win_xp on /home/fmouse/winxp type reiserfs (rw,noatime,notail) |
26 |
> /dev/mapper/main_vg-backup on /home/fmouse/winxp2 type ext3 (rw,noatime) |
27 |
> /dev/mapper/main_vg-archive on /home/fmouse/archive type reiserfs (rw,noatime,notail) |
28 |
> /dev/hda2 on /boot type ext3 (rw,noatime) |
29 |
> |
30 |
> The /dev/mapper/main_vg-* block devices are LVM logical volumes |
31 |
> consisting of Linux RAID-1 arrays which contain an archive and a couple |
32 |
> of filesystems for a VMware installation. The underlying drives are |
33 |
> SATA drives which show up as /dev/sd[a-d]1 in /dev. |
34 |
> |
35 |
> This setup must be maintained in a functional state across any kernel |
36 |
> and udev upgrades. |
37 |
> |
38 |
> I've been careful to use the .config from the working kernel as the |
39 |
> start for configuring a kernel for the newer kernel, using make |
40 |
> oldconfig. |
41 |
> |
42 |
> Does anyone have any idea what's wrong here? Am I required in recent |
43 |
> kernels to identify all physical drives in /etc/fstab (and anywhere else |
44 |
> it matters) with a UUID instead of a /dev device name? I've wasted an |
45 |
> entire day on this problem, which I can ill afford, but I have to get |
46 |
> past this roadblock and get my kernel up-to-date. |
47 |
> |
48 |
> |
49 |
|
50 |
|
51 |
I ran into this a few weeks ago. I to have the old IDE hard drives. I |
52 |
had to switch to PATA which means my drives are now sd* instead of hd*. |
53 |
I don't use LVM tho. I set LABELS on mine and use that to boot and |
54 |
mount the partitions where that are supposed to mount. It worked pretty |
55 |
well and since I'm using LABELS I can also boot the older kernels and |
56 |
hopefully any future kernels that come out. |
57 |
|
58 |
I *think* LVM can use LABELS to. If so, that would be my suggestion. |
59 |
That way you can move things around as needed and them still boot as |
60 |
they still be able to find your partitions. |
61 |
|
62 |
So far, I have not been able to get Grub to see the LABELS. I just |
63 |
haven't been able to do much testing on it yet. |
64 |
|
65 |
I'm not sure this will help you but it may be something that you want to |
66 |
check into. If LVM can work with this, it should be backward compatible |
67 |
with the kernels. |
68 |
|
69 |
Hope that gives you a idea at least. |
70 |
|
71 |
Dale |
72 |
|
73 |
:-) :-) |