Hi,
I'm going to be rebooting my box shortly to the latest (and greatest) rawhide kernel. Last time I did this, I was met with errors about drives not being found.
Having looked through the -test list, I find this is down to the way the kernel is behaving and that I need to rename my drives.
Currently, I have a pile of /dev/hdX's in my fstab file. Do I just rename these as /dev/sdX and what do I need to do in my grub file to get things to work?
TTFN
Paul
On Wed, Dec 20, 2006 at 09:57:52PM +0000, Paul wrote:
Currently, I have a pile of /dev/hdX's in my fstab file. Do I just rename these as /dev/sdX
I would rather suggest that you replace those with LABEL=<my_label_for_/dev/hdX_here> if these have ext2/ext3 file systems (or anything else which can be labelled). If you never bothered to put labels on these, or you want to change them then this can be done quickly with the following script:
#!/bin/bash
# read from stdin pairs 'volume_name label' and label ext2/ext3 # file system with these data
me=$(basename $0)
while read dev lab ; do echo tune2fs -L $lab $dev # just a visual check tune2fs -L $lab $dev done exit
You make files with lines like
/dev/hda5 home_my_home
and later you feed data from that file into the script above.
You can put also a label on a swap but for that you have to do 'swapoff -a' followed with 'mkswap -L ...' with a label you want and 'swapon -a'.
and what do I need to do in my grub file to get things to work?
Change in /etc/grub.conf 'root=/dev/hdX' to 'root=LABEL=<label_for_/>' I am not sure if anything in initrd is using particular labels. Redoing initrd after those changes seems to be prudent and at least not harmful. :-)
With that you should be able to boot does not matter how kernel is calling your devices.
OTOH I do not know how LVM will take to name changes; so if some of your partitions are on LVM volumes then booting may turn out to be "interesting". Just guessing here but files in /etc/lvm/archive/ are using "hard" names although those places are commented with "# Hint only" so possibly this is ok too.
Michal
Paul wrote:
Hi,
I'm going to be rebooting my box shortly to the latest (and greatest) rawhide kernel. Last time I did this, I was met with errors about drives not being found.
Having looked through the -test list, I find this is down to the way the kernel is behaving and that I need to rename my drives.
Currently, I have a pile of /dev/hdX's in my fstab file. Do I just rename these as /dev/sdX and what do I need to do in my grub file to get things to work?
TTFN
Paul
Yes, except for cd/dvd's. rename srX.
Or you can mess around with Label= stuff. I don't.
sean
sean wrote:
Paul wrote:
Hi,
I'm going to be rebooting my box shortly to the latest (and greatest) rawhide kernel. Last time I did this, I was met with errors about drives not being found.
Having looked through the -test list, I find this is down to the way the kernel is behaving and that I need to rename my drives.
Currently, I have a pile of /dev/hdX's in my fstab file. Do I just rename these as /dev/sdX and what do I need to do in my grub file to get things to work?
TTFN
Paul
Yes, except for cd/dvd's. rename srX.
Or you can mess around with Label= stuff. I don't.
sean
I use labels but still had problems until mkinitrd was fixed for handling labels. My awkwardness is getting used to using mount /dev/sdx instead of /dev/hdx.
If you use device names and ever boot into an fc6 kernel or earlier than that kernel, it will fail as it does for you now with trying to get fc7 kernels to boot.
I want to see if my lvm contained swap volume works with the fc6 but not the fc7 kernel. With labels, it is safe to boot either kernel version.
Anyway, for the device names, changing the /dev/hdx to /dev/sdx should work for you. If you have device entries in grub.conf referencing hdx devices, they will need revised also to sdx.
Hi,
Currently, I have a pile of /dev/hdX's in my fstab file. Do I just rename these as /dev/sdX and what do I need to do in my grub file to get things to work?
Yes, except for cd/dvd's. rename srX.
Or on my machine, hdg and hdh became dde and ddf which caught me out!
For some reason, my fstab doesn't have any entries for my DVDRW, DVD/CDRW and DVD (formerly hdc, hdd, hdf - zip drive was hde4) - it's been that long since I've looked at fstab, so should there be something there or is it an on-the-fly attribution sort of thing?
TTFN
Paul
On Thu, Dec 21, 2006 at 10:39:59AM +0000, Paul wrote:
Or on my machine, hdg and hdh became dde and ddf which caught me out!
Names like "dde" do not look right. It appears that you misread something. In a sense it should not matter.
For some reason, my fstab doesn't have any entries for my DVDRW, DVD/CDRW and DVD (formerly hdc, hdd, hdf - zip drive was hde4)
For a long while now removable media are handled by user space applications, like 'gnome-mount', communicating with dbus (unless something happens to be broken at the given moment:-) and fstab entry would roughly mean "don't do that; I am going to use something else, say 'autofs')". 'udev' is supposed to create /dev/cdrom and similar links pointing to right devices so hopefuly you should not worry about this at all.
Michal
dragoran wrote:
Neal Becker wrote:
Am I correct in assuming that LVM partitions do not require any changes?
no lvm and sw raid should continue to work.
Software raid is not working. mkinitrd does not load the raid modules.
tor, 21 12 2006 kl. 12:50 -0500, skrev Clyde E. Kunkel:
dragoran wrote:
Neal Becker wrote:
Am I correct in assuming that LVM partitions do not require any changes?
no lvm and sw raid should continue to work.
Software raid is not working. mkinitrd does not load the raid modules.
dmraid/fakeraid is also screwed, I can boot kernel-2.6.19-1.2877.fc7 but nothing more recent though I haven't tested todays kernel yet I expect the result to be the same.
- David Nielsen
-
Clyde E. Kunkel -
David Nielsen -
drago01 -
Jim Cornette -
Michal Jaegermann -
Neal Becker -
Paul F. Johnson -
sean darcy