| 1 |
I recently tried a badly needed kernel upgrade on my desktop system, |
| 2 |
moving from kernel 2.6.23-gentoo-r3 to kernel 2.6.29-gentoo-r5. This |
| 3 |
also required an upgrade of udev from 141 to 151-r4. When I rebooted |
| 4 |
the box there was no /dev/hda4 which is normally the root filesystem, |
| 5 |
and instead what was the root filesystem had a device name of, I |
| 6 |
believe, "rootfs" in the kernel mount table which had the same files. A |
| 7 |
number of other mounts were gone as well (there was no /dev/hda at all, |
| 8 |
which has several partitions). |
| 9 |
|
| 10 |
The boot-up stumbled to a halt at a maintenance mode prompt with the |
| 11 |
root filesystem mounted R/O and of course no gnome desktop. I could use |
| 12 |
mount -o remount,rw / to make the root filesystem RW, which allowed me |
| 13 |
to re-emerge an earlier version of udev and boot to the previous kernel, |
| 14 |
but I'm stuck with an aging kernel, and other tools depend on a kernel |
| 15 |
and udev upgrade so sooner or later I'm going to be just, plain, |
| 16 |
stuck :( |
| 17 |
|
| 18 |
The drive setup is a bit complex. The actual hard drive mounting |
| 19 |
(excluding things like proc, udev, devpts, etc.) look like: |
| 20 |
|
| 21 |
/dev/hda4 on / type reiserfs (rw,noatime) |
| 22 |
/dev/mapper/main_vg-fmouse on /home/fmouse type reiserfs (rw,noatime,notail) |
| 23 |
/dev/hda1 on /home/fmouse/win98 type reiserfs (rw,noatime,notail) |
| 24 |
/dev/mapper/main_vg-win_xp on /home/fmouse/winxp type reiserfs (rw,noatime,notail) |
| 25 |
/dev/mapper/main_vg-backup on /home/fmouse/winxp2 type ext3 (rw,noatime) |
| 26 |
/dev/mapper/main_vg-archive on /home/fmouse/archive type reiserfs (rw,noatime,notail) |
| 27 |
/dev/hda2 on /boot type ext3 (rw,noatime) |
| 28 |
|
| 29 |
The /dev/mapper/main_vg-* block devices are LVM logical volumes |
| 30 |
consisting of Linux RAID-1 arrays which contain an archive and a couple |
| 31 |
of filesystems for a VMware installation. The underlying drives are |
| 32 |
SATA drives which show up as /dev/sd[a-d]1 in /dev. |
| 33 |
|
| 34 |
This setup must be maintained in a functional state across any kernel |
| 35 |
and udev upgrades. |
| 36 |
|
| 37 |
I've been careful to use the .config from the working kernel as the |
| 38 |
start for configuring a kernel for the newer kernel, using make |
| 39 |
oldconfig. |
| 40 |
|
| 41 |
Does anyone have any idea what's wrong here? Am I required in recent |
| 42 |
kernels to identify all physical drives in /etc/fstab (and anywhere else |
| 43 |
it matters) with a UUID instead of a /dev device name? I've wasted an |
| 44 |
entire day on this problem, which I can ill afford, but I have to get |
| 45 |
past this roadblock and get my kernel up-to-date. |
| 46 |
|
| 47 |
-- |
| 48 |
Lindsay Haisley | "In an open world, | PGP public key |
| 49 |
FMP Computer Services | who needs Windows | available at |
| 50 |
512-259-1190 | or Gates" | http://pubkeys.fmp.com |
| 51 |
http://www.fmp.com | | |
Archives