According to Christoph Hammann: While burning my CPU.
>
> Hello, all of you!
>
> I got myself quite a problem when I bought a second IDE drive and tried to
> install SuSE
>
> Linux 5.3 on it. The first HDD is a Samsung 2G, the second a Seagate
> Medalist 4G. By now,
>
> I must have tried everything to get a working system on the second drive:
> jumpered it as
>
> slave, tried it with yast, created fs first from the system on the first
> drive and then
>
> used yast, tried mounting the partitions on directories of the first system
> and copied
>
> everything from my old system in them (got a badly corrupted fs), then
> someone told me
This sounds suspect, if you copied one drive to another, (a way which WILL
not work as one would think) did you create a root linux ext2 filesytem
before copying the data and did you use the proper FDISK from the SAME
installation verson as drive a:
The Medalist must have documentation with it, either a label on the drive
cover itself of a small booklet, that will tell you how to set the drive
settings.
>
> there might be a conflict between those two IDE drives, so I unplugged
> the first one
>
> and jumpered the Seagate as master, no luck.
Then you did not partition the drive and/or you have not created a ext2
filesystem.
>
> In every single instance it exited with an error message quite early in
> the installation
>
> of files on the new system.
>
> What's going on, and what can I do?
I would recomend reading the install instrctions for suse first, or
possabl;y again untill you find out for yourself just what you are doing
wrong.
I have a suse installation here which i installed onto /dev/hdb# i found it
just as easy as any other system to install.
Things about "Large drives" to be carefull about are;
Make sure your bios is returning the "correct geometry" clys heads etc, some
AMI BIOS'es will return a bogus geometry when the "autoconfig" is used.
Boot your system from the origanal drive with Linux and check dmesg for
"/dev/hdb" if linux reports /dev/hdb and its partitions correctly (if they
are presant) then you should be able to reboot and then install suse from
the distribution source.
>
> --
>
> See you,
>
> Christoph Hammann
>
> #########################################################
> # (-; too freaking busy feigning computer literacy ;-) #
> #######################################################
>
>
>
--
Regards Richard.
[EMAIL PROTECTED]
