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