1833863 Members
1940 Online
110063 Solutions
New Discussion

fbackup error

 
SOLVED
Go to solution
M.Thomas
Frequent Advisor

fbackup error

i know i have used /dev/rmt/0m to backup all thses days. now it says it is not a valid device. if i try to give /dev/rmt/0mn same result. ioscan -fnC tape looks fine. what could be the issue?

Thanks

Thomas
8 REPLIES 8
Robert-Jan Goossens
Honored Contributor

Re: fbackup error

Hi Thomas,

Could you post the output of

# ll /dev/rmt/0mn

Regards,
Robert-Jan
M.Thomas
Frequent Advisor

Re: fbackup error

here it is

crw-rw-rw- 2 bin bin 205 0x010040 Jan 26 12:04 /dev/rmt/0mn

crw-rw-rw- 2 bin bin 205 0x010000 Jan 24 17:18 /dev/rmt/0m

Thanks

Thomas
ArvindMenon
Advisor

Re: fbackup error

Hi,

Could you paste the excat error message.

Regards
Arvind
A. Clay Stephenson
Acclaimed Contributor

Re: fbackup error

Ioscan is hardly a definitive test for a device. I would try doing a tar, cpio, or dd to the tape drive. If those fail, chances are that you have hardware problems. Of course, you may be doing soomething as simple as trying to write to a write-protected medium. The exact error message of dd is probably the most direct diagnostic you have. It would also be helpful to "echo ${?}" immediately after dd finishes as that will be the exit status of the command and should be the errno value of the last failed system call.
If it ain't broke, I can fix that.
M.Thomas
Frequent Advisor

Re: fbackup error

i did dd if=/etc/hosts of=/dev/rmt/0m and it comes back with /dev/rmt/0m no such device or address
dd:cannot create /dev/rmt/0m

Thanks

Thomas
Reshma Malusare
Trusted Contributor

Re: fbackup error

DCE
Honored Contributor

Re: fbackup error



You could try rmsf -H
to remove the devicefiles

Then insf -H
to recreate them
Bill Hassell
Honored Contributor
Solution

Re: fbackup error

No such device...

indicates that tyhe tape drive is not working right. Search for all tape drives with:

ioscan -fnC tape

then ask for status with:

mt -f /dev/rmt/... status

No response indicates bad cable, connectors, no terminators, bad mapping on a SAN system, etc


Bill Hassell, sysadmin