> managed to mount hdc5 and hdc7 with above command Good, some hope then.
> ...would not accept hdc1 > as it was a NTFS partition and hdc6 was Linux swap. Nothing extraodinary. Now the command to use to check for any files on that partition (which you just mounted at /mnt) is called ls. Sorry I didn't point it out, but it didn't occur to me that someone who is looking for his files on his harddisk, and who manages to mount the partition the files are on, then does not even look if there are any files there... > >chroot /bin/bash /mnt # make hard disk top-level > error: can't change rot to /bin...not a directory After mounting your hdc5 at /mnt, /mnt/bin/bash must exist (assuming hdc5 is your Linux root filesystem). Use ls. > >mount /proc # you need the proc fs!! > message: proc already installed It can be dangerous to proceed running commands as root if a previous command failed and you don't understand what each command is expected to do. In this case, the command to "switch" from the rescue system to your harddisk system (chroot) failed. You therefore are still on the rescue system, which has /proc already mounted and as you found out, doesn't have yast. There's no point anyway in running yast to install a bootloader in the ramdisk ;) (The rescue system is running completely in a ramdisk, that's why you can take the CD out again - which you can't with constructions like Knoppix or the SuSE live disks.) Volker -- Volker Kuhlmann is possibly list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me.
