The culprit is the root=UUID=ddbfffc1-731c-4931-9129-75c5f42f8ecb part which probably still has the old UUID or partition listed. If you know the specific partition you can either set it to something like root=/dev/sda1 (or whatever your partition number is) and then type ctrl-x to boot or you can substitute the correct UUID which you can find by booting with a rescue disk and running the blkid command.

If you're lucky and your root partition has been properly labeled then you could also try root=LABEL=/.

Can you explain more? as a start it says: The disk drive / is not ready yet or not present, but when i go to console, I can access all files
–
khelllApr 29 '11 at 13:53

how you access that files? you can try to check blkid /etc/mtab and grub configuration if UIDS are correct.
–
MealstroMApr 29 '11 at 13:57

I went with the recovery mode and it said it can't mount drives then it gave me the console. Using it I can access files with no problems. Not sure what to do with the commands u specified above.
–
khelllApr 29 '11 at 14:08

can you show yours /boot/grub/grub.cfg and command /sbin/blkid result?
–
MealstroMApr 30 '11 at 12:35

I am sorry to say that I have the same problem. But, unfortunately, comment from Some Guy couldn't help me because the UUID value in fstab actually matches the output of blkid. BTW I tried to use /dev/sda1 instead of the uuid, but it didn't help.
–
user79943Apr 29 '11 at 22:07