Your fstab and menu.lst look good to me same to me. And if they didn't match, I would expect the error messages to be different.
So if you boot into -19 recovery console, you see entries in /dev ? Do you at least have /dev/hda or /dev/sda entries for your drive? If so, I don't know why it is not creating the entries in /dev/disk/by-uuid. It should create entries based on the following rules:
and it gets the information it needs from /lib/udev/vol_id. I can only guess that either it cannot find the vol_id program or vol_id is returning bad information. What does it show when you run "/lib/udev/vol_id /dev/hd??" replacing ?? with letter/number for your root drive?
Your fstab and menu.lst look good to me same to me. And if they didn't match, I would expect the error messages to be different.
So if you boot into -19 recovery console, you see entries in /dev ? Do you at least have /dev/hda or /dev/sda entries for your drive? If so, I don't know why it is not creating the entries in /dev/disk/by-uuid. It should create entries based on the following rules:
# by-label/by-uuid (filesystem properties) program} ="vol_id --export $tempnode" FS_USAGE} =="filesystem| other|crypto" , ENV{ID_ FS_UUID_ ENC}==" ?*", SYMLINK+ ="disk/ by-uuid/ $env{ID_ FS_UUID_ ENC}" FS_USAGE} =="filesystem| other", ENV{ID_ FS_LABEL_ ENC}==" ?*", SYMLINK+ ="disk/ by-label/ $env{ID_ FS_LABEL_ ENC}"
IMPORT{
ENV{ID_
ENV{ID_
and it gets the information it needs from /lib/udev/vol_id. I can only guess that either it cannot find the vol_id program or vol_id is returning bad information. What does it show when you run "/lib/udev/vol_id /dev/hd??" replacing ?? with letter/number for your root drive?