Document ID: 18010 Title: How do you load st.conf changes without rebooting? Update Date: Fri Feb 20 00:00:00 MST 2004 Products: Solaris Technical Areas: Kernel Keyword(s):st.conf, /kernel/drv/st, tape, drive, reload, reboot, boot -r Description: Top Document Body: Top To make an updated /kernel/drv/st.conf file active, it is necessary to reload the st (SCSI Tape) kernel module. To do this, you can either do a reconfiguration reboot (reboot -- -r) or manually unload and reload the st kernel module Follow this procedure to reload the st kernel module manually 1. Get the kernel module id number: # modinfo | grep "st (" 96 60dcc000 cdb0 33 1 st (SCSI Sequential Access Driver) In this example the id is shown to be 96. Your id number may vary 2. Make sure none of your tape drives are in use and that all backup software is quisced For Solstice Backup do: # /etc/init.d/networker stop For Netbackup do: # /etc/rc0.d/K77netbackup 3. Unload the kernel module: # modunload -i 96 4. Make modifications to /kernel/drv/st.conf or place new st.conf file in /kernel/drv 5. Load the kernel module back in using the modload command: # modload -p drv/st 6. Re-start your backup software: For Solstice Backup do: # /etc/init.d/networker start For Netbackup do: # /etc/rc2.d/S77netbackup NOTES: If you change the scsi target or lun of a tape device, you must reload the st module as above, and run: devfsadm -C devfsadm -i st To re-build the device paths. The above procedure may successfully unload the st kernel module but may encounter problems on the reload. When this occurs, all tapedrives are non-functional until the next reboot is done. It is always safer to plan for the downtime and perform a reboot instead of modunloading/modloading the st driver and having to perform an unscheduled reboot to recover the tapedrives.