Topic: Seagate ST220000A IDE Tape Not Recognized

[Glenn]

Does anyone know the reason why a Seagate ST220000A IDE Hornet drive would not be recognised by the e-smith 4.1.1 server. It is the only device , "Master", on the secondary IDE channel and the bios sees it fine. In the "Messages" file I can see the Kernel report the drive as being there as shown below but I can't seem to get tape backups to occur. Also performing a test,  "mt -f /dev/st0 status" reports no drive available. The only possible reason I can think of is that I installed the drive after the server had already been installed. If this was the cause, how can I get the thing recognised after the fact. Any help will be greatly appreciated!!

Glenn


Mar 30 03:39:11 e-smith kernel: PIIX4: IDE controller on PCI bus 00 dev 21
Mar 30 03:39:11 e-smith kernel: PIIX4: not 100%% native mode: will probe irqs later
Mar 30 03:39:11 e-smith kernel:     ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:DMA
Mar 30 03:39:11 e-smith kernel:     ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:pio
Mar 30 03:39:11 e-smith kernel: hda: ATAPI CD ROM DRIVE 50X MAX, ATAPI CDROM drive
Mar 30 03:39:12 e-smith kernel: hdb: ATAPI CD ROM DRIVE 50X MAX, ATAPI CDROM drive
Mar 30 03:39:12 e-smith kernel: hdc: Seagate STT20000A, ATAPI TAPE drive
Mar 30 03:39:12 e-smith kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Mar 30 03:39:12 e-smith kernel: ide1 at 0x170-0x177,0x376 on irq 15

[Darrell May]

Glenn wrote:
>
> Does anyone know the reason why a Seagate ST220000A IDE
> Hornet drive would not be recognised by the e-smith 4.1.1
> server. It is the only device , "Master", on the secondary
> IDE channel and the bios sees it fine. In the "Messages" file
> I can see the Kernel report the drive as being there as shown
> below but I can't seem to get tape backups to occur. Also
> performing a test,  "mt -f /dev/st0 status" reports no drive
> available. The only possible reason I can think of is that I
> installed the drive after the server had already been
> installed. If this was the cause, how can I get the thing
> recognised after the fact. Any help will be greatly
> appreciated!!
>
> Glenn

Check your /etc/modules.conf for these two lines, add if missing:

alias scsi_hostadapter ide-scsi
pre-install ide-scsi     modprobe ide-cd

Darrell

[Fernando]

I have the same problem, I don't understand the solution.Some people could help me.

Thanks

Fernando

[Glenn]

Hi Fernando,

    There can be many things that cause this problem. The most obvious is simply incorrect drive settings or cable connections. First of all, check that the drive's MASTER/SLAVE jumper settings are correct. I suggest leaving the drive as the only device on one of the IDE channels... makes things much more fool proof.  

 The second most common cause of this situation is the existence of a SCSI card in the system when using this IDE tape drive with IDE-SCSI emulation. This combination can be made to work if necessary but the more simple solution is to force e-smith to use the IDE-TAPE module to operate the drive. This can be done as shown below.


Hope this helps.

Glenn


  On systems which contain a SCSI controller and will utilize an IDE tape drive you must  make the appropriate changes to the e-smith configuration scripts. You can do so simply by typing the following commands :

                    /sbin/e-smith/db configuration setprop backup Device /dev/nht0
                    /sbin/e-smith/signal-event conf-backup

  These changes will configure to e-smith server to dynamically load the ide-tape.o module rather  than the ide-scsi.o scsi emulation module when a backup occurs either manually or by a cron job setup through the e-smith web manager.

  After making these changes, all relevent tape drive commands will use /dev/nht0
 instead of /dev/nst0.

 Now apply all the updated RPM's to get the system up to date with security and bug fixes. At the very least,  you must update the the e-smith-backup RPM to insure proper tape backups