Tape Error on Red hat Linux Server
DUMP: End of tape detected
DUMP: Closing /dev/nst0 DUMP: Volume 1 completed at: Fri Jan 2 12:18:38 2015 DUMP: Volume 1 58128680 blocks (56766.29MB) DUMP: Volume 1 took 3:46:57 DUMP: Volume 1 transfer rate: 4268 kB/s DUMP: Change Volumes: Mount volume #2 DUMP: fopen on /dev/tty fails: No such device or address DUMP: The ENTIRE dump is aborted. what is problem in tape drive??? |
please any can advice me? why above error is happen???
|
Can you tell us anything about what kind of tape drive you have and the exact command you're running that produces this error?
|
The problem is not with the tape drive but with the lack of a tty on which to ask the user to change the tape. Is this backup being run from a cron or at job (for which there is no controlling tty)? If there are multiple tape drives available, was dump told about all of them? The only "problem" with the tape drive is that you have run out of space on the tape.
|
Quote:
Quote:
rknichols gave you as much info as anyone here can. Since you're using Red Hat, and seem to need an urgent answer, you should contact Red Hat support if you're using Red Hat Enterprise....since you are PAYING for RHEL, right???? |
How about stepping into the twenty first century and buying an electric car, whoops I mean SSD or BDRW or sever-whatever...
|
check backup code
below comman is used to take the backup into tape
<hr> <a name="Dump1">/u05</a> <pre> END dump -u$level -e 11,1015809 /u05 >>$log 2>&1 res=$[ $res || $? ] tape status SCSI 2 tape drive: File number=1, block number=0, partition=0. Tape block size 512 bytes. Density code 0x47 (TR-5). Soft error count since last status=0 General status bits on (81010000): EOF ONLINE IM_REP_EN |
power failure
Actually tape is successfully done
/u05 DUMP: Date of this level 3 dump: Mon Jan 5 06:30:02 2015 DUMP: Date of last level 0 dump: Thu Jan 1 06:30:02 2015 DUMP: Dumping /dev/mapper/VolGroup_ID_17711-LogVolU05 (/u05) to /dev/nst0 DUMP: Label: none DUMP: Writing 10 Kilobyte records DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 35726154 blocks. DUMP: Volume 1 started with block 1 at: Mon Jan 5 06:32:43 2015 DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: 1.07% done at 1142 kB/s, finished in 8:33 DUMP: 3.11% done at 1756 kB/s, finished in 5:27 DUMP: 5.64% done at 2159 kB/s, finished in 4:19 " " " " " " DUMP: 94.55% done at 3991 kB/s, finished in 0:08 DUMP: 96.79% done at 3946 kB/s, finished in 0:04 DUMP: 99.11% done at 3907 kB/s, finished in 0:01 DUMP: Closing /dev/nst0 DUMP: Volume 1 completed at: Mon Jan 5 09:04:35 2015 DUMP: Volume 1 35727030 blocks (34889.68MB) DUMP: Volume 1 took 2:31:52 DUMP: Volume 1 transfer rate: 3920 kB/s DUMP: 35727030 blocks (34889.68MB) on 1 volume(s) DUMP: finished in 9111 seconds, throughput 3921 kBytes/sec DUMP: Date of this level 3 dump: Mon Jan 5 06:30:02 2015 DUMP: Date this dump completed: Mon Jan 5 09:04:35 2015 DUMP: Average transfer rate: 3920 kB/s DUMP: DUMP IS DONE (power failure)out of battery power forthat reason Manually shut database after startup database i can't restore from the tape, it is giving below error [root@central ~]# pwd /root [root@central ~]# cd /u05/motorsc [root@central motorsc]# [root@central motorsc]# mt status SCSI 2 tape drive: File number=0, block number=-1, partition=0. Tape block size 512 bytes. Density code 0x47 (TR-5). Soft error count since last status=0 General status bits on (1010000): ONLINE IM_REP_EN [root@central motorsc]# [root@central motorsc]# mt rewind [root@central motorsc]# [root@central motorsc]# mt status SCSI 2 tape drive: File number=0, block number=0, partition=0. Tape block size 512 bytes. Density code 0x47 (TR-5). Soft error count since last status=0 General status bits on (41010000): BOT ONLINE IM_REP_EN [root@central motorsc]# /sbin/restore -i -f /dev/nst0 /sbin/restore: Tape read error on first record what is the reason !!! |
Could be a number of things. The power failure may have damaged the transport (though unlikely). Trash buildup on the read heads? It is even conceivable that the tape itself is old, and the first block flaked off the tape?
How about testing with a different tape just to see that the drive is functioning correctly. Try using dd to read the first few blocks from the "bad" tape. Cleaning the heads might help. One other thing, though this is really unlikely, is it possible the tape wasn't positioned properly before the dump was written? Sincd /dev/nst0 directs the tape to not be rewound, if it wasn't at the beginning of the tape then it is possible that there was some other junk on it at the very beginning (like a tape mark) which would cause a read error on the first record. This could be recoverable by skipping past the beginning (there should be a tape mark just before the backup - I have seen this happen with cartridge tapes, as there is no obvious way to know the real position). |
tape error
I checked one more tape
same error happen yesterday it working fine server and database not down( battery working) for reason power failuer we Manually shut the db when battery was going too low (5%-10min) |
That begins to sound like the transport failed.
|
Quote:
Without details, there is NOTHING we can help you with. If you won't answer questions, then the only real suggestion would be for you to contact Red Hat support and/or a local consultant, and pay them to solve the problem. |
We are using
SCSI 2 tape drive below command using to write to tape <hr> <a name="Dump1">/u05</a> <pre> END dump -u$level -e 11,1015809 /u05 >>$log 2>&1 res=$[ $res || $? ] tape status SCSI 2 tape drive: File number=1, block number=0, partition=0. Tape block size 512 bytes. Density code 0x47 (TR-5). Soft error count since last status=0 General status bits on (81010000): EOF ONLINE IM_REP_EN |
Quote:
Quote:
Play Bonny! :hattip: |
thanks
thanks your responces
thanks very much |
All times are GMT -5. The time now is 10:13 PM. |