Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: "restarting" scsi
- To: tlug@example.com
- Subject: Re: "restarting" scsi
- From: B0Ti <9915104t@example.com>
- Date: Sat, 16 Dec 2000 23:41:10 +0900
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain; charset=us-ascii
- Organization: Kobe University, Japan
- References: <Pine.LNX.4.10.10012161724010.10739-100000@example.com>
- Reply-To: tlug@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <RjkkK.A.MbE.z53O6@example.com>
- Resent-Sender: tlug-request@example.com
- Sender: boti
Tony Laszlo wrote: > Is there a way of making Linux > shutdown and restart the scsi > services? I don't know if this is the clean way to do it, but this is what I do whenever (rarely) it becomes necessary: First make sure the the scsi devices are not busy (unmount filesystems, etc) Then remove the scsi modules in the opposite order they were loaded. After this just try to access the scsi device and the modules should be loaded again automatically, if not so then modprobe them manually. Unless you have scsi stuff compiled into the kernel, the above should do it. You can put the stuff in a script. If the scsi modules are in /etc/modules then they should be loaded automatically on boot (Debian, and Mandrake 7.2 does this at least), so there is no need for an init script. May I ask the reason why you need to do this? If you want to add another scsi device on the fly, there is a better way to do it. B0Ti
- Follow-Ups:
- Re: "restarting" scsi
- From: Tony Laszlo <laszlo@example.com>
- References:
- "restarting" scsi
- From: Tony Laszlo <laszlo@example.com>
Home | Main Index | Thread Index
- Prev by Date: Japanese search engines
- Next by Date: latex,lyx
- Prev by thread: "restarting" scsi
- Next by thread: Re: "restarting" scsi
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links