Linux - DistributionsThis forum is for Distribution specific questions.
Red Hat, Slackware, Debian, Novell, LFS, Mandriva, Ubuntu, Fedora - the list goes on and on...
Note: An (*) indicates there is no official participation from that distribution here at LQ.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I downloaded the SuSE 8.0 files from the net in order to install Linux from my local hard disk. The source drive is /dev/hda5 and the target drive on which i want to install Linux is /dev/hdb1. Now I ran into the following problem:
After i complete the installation settings, Yast2 tries to start the copy process but aborts with the message that the source drive could not be mounted to /tmp/mnt because it is already mounted to /mounts/extra. I have the option to 'skip' but this cancels the entire installation. Unmounting /dev/hda5 is not possible since the drive is busy. I tried making a symbolic link of /mounts/extra to /tmp/mnt but it won't help.
It seems to me that this problem must have been obvious to the people who coded the installation routines, so there must be a simple way to work around it, but i have yet to find one. Isn't it possible to tell Yast2 to just use the mount point of the source drive that is already in use since I can access the suse tree without a problem but Yast2 simply continues to try and mount the drive elsewhere?
Any suggestions on this would be greatly appreciated!
Is /dev/hda5 being mounted on /mounts/extra by SuSE or by you?
/mounts/extra does not sound like a name that SuSE would use.
If you are doing the mount in /etc/fstab then take it out.
It is indeed being mounted by the installation program. Though i can't seem to guess the reason for this as most of the installation system (if not all of it) is on ramdisks. However unmounting will not work as the drive is busy. I tried to remove all the links to /dev/hda5 in order to be able to unmount it but at some point the whole file system tree disappears. So much for ramdisk. =)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.