frank cox wrote jackson byers wrote: > reinstalled f10dvd media ck said ok Any chance you could re-post your question using complete words and sentences, and a complete description of what you have done and what you expect to see, and what you actually see? I read your message four times and I still have no idea what you're actually doing. Are you trying to install F10 on a machine that already has F5 installed on it, without overwriting the F5 installation? Describe your current setup, what you want to do, and what you have tried. Include complete error messages (if any). --------------- jbyers: sorry I wasn't clearer; I was trying to not be so verbose Yes, I am trying to install F10 onto sda1 on a machine that already has Fc5 installed on it on sdb6 , without overwriting the Fc5 installation. Every install attempt of f10, I use custom partitioning, and only format sda1 as ext3. My fc5 remains available. I previously had a thread where I was trying to use a fedoraliveinstall cd to install, and never could get it to boot, even tho the install said it was successful. I won't repeat everything I tried with the liveinstall cd, because my experiences then and now are much the same, installs, but no boot. I am trying the same thing now with a f10dvd. 1)I first tried to keep the fc5 in control of the mbr on sda and hence using fc5 grub.conf to have a stanza for f10 copied directly from the f10 install grub.conf This gives me : Error 2 bad file or directory. If I instead use a stanza for f10 root (hd0,0) chainloader +1 then I get error msgs: cant access resume device (sda/sdb2) mount: error mounting /dev/root on /sysroot no such file or directory 2) I next tried allowing the f10 install on sda1 have grub install into mbr of sda, thus replacing the fc5 grub into mbr of sda5. This does not give me Error2 as in 1) above but instead the same errors as in chainloader +1 in 1) above: cant access resume device (sda/sdb2) mount: error mounting /dev/root on /sysroot no such file or directory 2a)appending "scsi_mod.scan=sync" to the kernel line did not give me those last 2 msgs, but instead flashed an entire screen of boot msgs, which then disappeared, screen went blank I hope this makes it clearer. Jack