1825512 Members
1893 Online
109681 Solutions
New Discussion юеВ

Tape bakup unreconozed

 
Edwin Ruiz_2
Super Advisor

Tape bakup unreconozed

Hi!

My tape backup on linux redhat 7.2 is missing...somebody turn off this device and i can not see it wit "cdrecord -scanbus" command .. what can i do for recognoze this device without reboot my server?

Pls help me

5 REPLIES 5
Mark Grant
Honored Contributor

Re: Tape bakup unreconozed

Edwin,

Sorry but I think you are going to have to re-boot. Scsi devices are not hot pluggable on a PC. Assuming you have turned the thing back on again, you got unlucky. However, try "cat" on /proc/scsi/scsi to see if the device is there.
Never preceed any demonstration with anything more predictive than "watch this"
Edwin Ruiz_2
Super Advisor

Re: Tape bakup unreconozed

yes! i can see the devices with cat /proc/scsi/scsi.. rarely i use

mt -t /dev/st0 status an i get that:


[root@salato-apl10 mail]# mt -t /dev/st0 status
SCSI 2 tape drive:
File number=0, block number=0, partition=0.
Tape block size 0 bytes. Density code 0x2e (no translation).
Soft error count since last status=0
General status bits on (41010000):
BOT ONLINE IM_REP_EN


but cdrecord -scanbus show nothing
Mark Grant
Honored Contributor

Re: Tape bakup unreconozed

Do you backup with "cdrecord" then?

Just see if the thing is working, try putting a tape in and using "tar cvf /dev/st0 and see if it writes OK.

If this works then it look like cdrecord has got a bit upset. Maybe you can do "tar" backups until you get the chance to re-boot.
Never preceed any demonstration with anything more predictive than "watch this"
Edwin Ruiz_2
Super Advisor

Re: Tape bakup unreconozed

I use tar -cvf /dev/st0 and i get that

tar: /dev/st0: Wrote only 0 of 10240 bytes
tar: Error is not recoverable: exiting now

i just use tar
Martin P.J. Zinser
Honored Contributor

Re: Tape bakup unreconozed

Hello Edwin,

IIRC kudzu is the tool used in RH for HW discovery. Maybe it will re-discover your drive. Generally it is meant to run during the boot process, so there might be a risk of a "forced" reboot. Certainly the safest would be to just schedule a planned reboot.

Greetings, Martin