New Subject (not about moving the lug)
meyer_rm at yahoo.com
Mon Mar 25 19:41:49 EST 2002
If the system is booting from SCSI drives, the module will get loaded
automatically since the system should try to load it as the drives are
accessed. If that doesn't work, then putting it in /etc/modules would be a
good stop-gap but I prefer to find the real reason and fix it.
--- Cyber Source <peter at thecybersource.com> wrote:
> Great info Bob! That one got printed for future reference :) Did you see
> my note back to Dege? Is it just enough then to put the text as "sd_mod"
> in the /etc/modules file? Hope the new job is going good for you. I will
> give you a call soon and keep you up to date on the Linux Solutions stuff.
> Robert Meyer wrote:
> >Reply interspersed within text...
> >--- Cyber Source <peter at thecybersource.com> wrote:
> >>Hello all,
> >> After a couple of days fooling around with this, I find myself needing
> >>to ask the more learned of the group for a resolution.
> >> We have a Linux server here that I am very nervous about causing harm
> >>to, so my steps to install/change the system over to scsi have been very
> >>cautious and timid at best. Here's the situation.
> >> I have an IDE based Linux Mandrake 8.1 server that I wish to change
> >>over to a scsi based system. I have installed the "adaptec 29160" scsi
> >>card and u160scsi hard drive.
> >>Mandrake 8.1 did detect the card on boot (kudzu) and said it configured
> >>it. The scsi drive was hooked up to the system while I still booted with
> >>the IDE based system. The card was recognized but the scsi drive was
> >>not, no /dev/sd?. I have tried other ways to rule out a problem with
> >>this as in doing an install with the card and drive seperately and it
> >>works fine. I then looked to the /etc/modules, /etc/modules.conf files
> >>and copied the info that was in those files (from the successful
> >>install) to that of the same files on the ide based drives to see if it
> >>would work but it has not. I also want to point out that on one boot it
> >>did pick up the drive and loaded the scsi module but has not since
> >>booting after (and not after changing any files). The reason for all
> >>this caution, is that Bob Meyer and I have a ton of time in customizing
> >>this system and it works great. We don't want to loose this
> >>customization. I have backed up the entire system, so here are my
> >>1. What are the necessary steps to get this scsi card recognized?
> >Well, Kudzu should have gotten everything. Type 'lsmod' and look for
> >and 'scsi_mod'. You cannot locate disks without sd_mod.
> >>2. Do I have to run the insmod command or is it simply enough to have
> >>the necessary file/text in the /etc/modules and /etc/modules.conf files?
> >Sometimes, unless you try to access something, it doesn't load the driver.
> >Kudzu should have made entries in /etc/modules.conf that relate to the block
> >device for the scsi drives. Any attempt to access the scsi drive should
> >the driver to get loaded. In Mandrake 8.1, it likes to stuff things in
> >/dev/scsi/host0/bus0/target0/lun0. Note that the '0' could be any number
> >the host and bus will probably be zero. Target is the actual SCSI target on
> >the bus (the SCSI ID) and the lun will probably always be zero.
> >>3. Are there more files to deal with aside from the /etc/modules and
> >>/etc/modules.conf files?
> >For configuration, it should just be /etc/modules.conf and /etc/modules.
> >/etc/modules is for stuff that you want to load automatically that might not
> >otherwise be loaded on boot such as stuff that's not used all the time.
> >>4. Is it possible to take a system that was backed up (using dump) from
> >>an ext2 partition and restore them to an ext3 partition?
> >In a word... yes. You will have to change the entries in /etc/fstab to tell
> > that the file systems are ext3 and maybe change the drive references if the
> >partition maps are different but that's about it.
> >>5. I now have Linux Mandrake 8.2 (freshly downloaded) and was thinking
> >>of just running that to do an upgrade, with all the hardware installed
> >>(scsi adapter, ide based system still) and after success at that, then
> >>do a backup of the system and then copy all to the scsi drive and change
> >>the /etc/fstab, /etc/mtab and /etc/lilo.conf files.
> >>I personally think it would be better to do number 5 above but it seems
> >>like cheating and I would really like to know what is wrong with it
> >I would get the drives recognized, copy all of the data to their respective
> >partitions, modify the fstab file to point everything to the appropriate
> >drive, rather than 'hd', remove the IDE drive, boot the install CD with
> >root=/dev/sda1' or whatever the partition is, modify the lilo.conf file to
> >point to the SD drive boot area, run LILO, reboot the machine, enabling the
> >SCSI BIOS in the process. The machine should come up and you still have the
> >IDE drive in case it doesn't work...
> >I think that gets all of it...
> >Bob Meyer
> >Knightwing Communications, Inc.
> >36 Cayuga Blvd
> >Depew, NY 14043
> >Phone: 716-308-8931 or 716-681-0076
> >Meyer_RM at Yahoo.com
> >Do You Yahoo!?
> >Yahoo! Movies - coverage of the 74th Academy Awards®
Knightwing Communications, Inc.
36 Cayuga Blvd
Depew, NY 14043
Phone: 716-308-8931 or 716-681-0076
Meyer_RM at Yahoo.com
Do You Yahoo!?
Yahoo! Movies - coverage of the 74th Academy Awards®
More information about the nflug