J�rg Fochler@DPI
24.01.99 08:58
> Robert Johannes wrote:
>
> I've a tekram DC390F controller, and an IBM DDRS-model 4.5 gig drive.
> I've installed redhat 5.2 on it, and the controller was automatically
> detected as an NCR53C8XX. The system worked fine, until I rebuild the
> kernel with NCR53C8xx support using freshly installed sources of kernel
> 2.0.36.
>
> I tried booting to the new kernel (after installing it in the proper
> places, and running /sbin/lilo), and the system reported this:
^^^^^^^^
Did you changed /etc/lilo.conf to the right values ?
(e.g. the entry for the boot image should be correct as well as the
declaration for the install location;
Generally it's a good idea to have at least a second label witch
points to the last bootable kernel {example: vmlinuz.old} so that
you can still boot your machine even if the new kernel
wouldn't like to.....)
>
> SCSI: 0 hosts
> SCSI: detected total.
> partition check:
> VFS: cannot open root device 08:01
> kernel panic: VFS: unable to mount root fs on 08:01
>
> And the system hangs there. Does this mean that the scsi controller
> isn't being detected, or is it a problem with my drive? If it is a
^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^
That's right... I don't believe that;
0 means zero, also do you still have access to the host
called nothing ;-) adaptor and the HDD via boot floppy ?
> problem with LILO, why did it work before I recompiled the kernel?
Well, let's go a little deeper: To boot a system from a device you
need to have access to this device via the driver. The linux kernel
configuration tools allow you to select a driver as module (M) or
as linked-to-the-kernel (Y). The modules may be loaded on your own
demand (insmod/modprobe) or automatically (kerneld), but only AFTER
the kernel has been booted.
This means in short: Select your SCSI driver as fixed part of the
kernel, make it new, install it in the right places and all your
(boot)problems are gone......
(If not, put the blame on me and return to the list with more details
of your system [dmesg | bootparams | log file extractions]+ :)
>
> I've three partitions on the drive; the / file system is 2.0gig, and the
^^^^^^^^^^^^^^
Suggestion as you asked for: Better hold the "real /" in a separated
partition. This will minimize the risk for damaging your /-file system
due to hangups, resets and crashes.
Put /tmp, /var, /usr and /home on own partitions of appropriate sizes
(will fasten fsck and disk access besides less damaging risk, see above).
Last hint: Some popular software (like StarOffice, Applixware) wants
to be installed in /opt; If you aren't in the mood to create an own
partition for that, they will consequently be installed on the
/-partition. To avoid this, make a directory /usr/opt, copy the
contents of /opt, if any, to /usr/opt and link /opt to /usr/opt.
> rest is /home. The 2.0gig is well below LILO's limitations, if i'm
^^^^^^^^^^^^^^^^^^^
LILO limitation is that the bootable partition has to be in the first
1024 cylinders.
> correct, I can't figure out what else is preventing the system from
> booting through.
>
> Please make comments, suggestions, etc. All will be appreciated
> greatly. Thanks in advance
>
> Robert Johanne
Hope that helps
Joerg
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
