Home > Failed To > Failed To Write Lif Onto Tape

Failed To Write Lif Onto Tape

Can you help please? ButLVM did not handle half dead disk conditions until this release. thumb below! 0 Kudos Reply EU-Admins-UNIX Regular Advisor Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content ‎08-22-2012 04:22 AM any other ideas? 0 Kudos Reply Jacob Levin Advisor Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content ‎10-19-2007 09:21 AM this contact form

Acclaimed Contributor Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content ‎08-28-2012 04:43 AM ‎08-28-2012 04:43 AM Re: Issues with Make_tape_recovery I'll try it and assign points afterwards.Robin 0 Kudos Reply Wim Rombauts Honored Contributor Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report I've tried multiple tapes including brand new ones, same error. Community Ignite-UX CommunityCategoryBoardUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.

That's why it's called the present. 1 Kudo Reply Massimo Bianchi Honored Contributor Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate And most important, read the man page for mt, specifically the details about the bizarre ATT options versus the sane Berkeley options.For something as importrant as an Ignite backup, write a It only adds new device nodes for hardware/drivers that don't already have them.If you want to rebuild the existing device nodes, the "-e" option of the insf command is needed.> Is That means it is not included, due to your "-x exclude=/extrnl1" option on the command line.The last sentence in the WARNING message above tells you what to do. "This message can

With additional options, you can restrict "insf -e" to remake the device nodes for a particular device or device class only.For example, this remakes tape device nodes only:insf -e -CtapeThis remakes Showing results for  Search instead for  Do you mean  Menu Categories Solutions IT Transformation Internet of Things Topics Big Data Cloud Security Infrastructure Strategy and Technology Products Cloud Integrated Systems Networking Showing results for  Search instead for  Do you mean  Menu Categories Solutions IT Transformation Internet of Things Topics Big Data Cloud Security Infrastructure Strategy and Technology Products Cloud Integrated Systems Networking thumb below! 0 Kudos Reply EU-Admins-UNIX Regular Advisor Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content ‎08-22-2012 04:42 AM

tar, dd, cpioif that does not work then Ignite is not going to work either.replace tape and try again.swap tape drive and try againtry tape drive on different serverif all of I have checked the drivers on each of them and they have the same ones IN and OUT. This means that not all files anddirectories on this volume group will be restored when the archive isinstalled. read: No such device or address read_blocks(lifvol): error on 1024 byte write lifls: Can't list /dev/disk/disk100; not a LIF volume WARNING: /dev/disk/disk100 is not a LIF volume.

You have only one tape drive connected to the system and I can see the current tape is at the end.You may do, rewind, forward functions as well as read/write operations The previous status with [0] means there is no tape loaded. For example:# scsimgr replace_wwid –D /dev/rdisk/disk14This command allows the storage subsystem to replace the old disk’s LUN World-Wide-Identifier (WWID) with the new disk’s LUN WWID. thumb below! 0 Kudos Reply EU-Admins-UNIX Regular Advisor Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content ‎08-22-2012 08:03 AM

Showing results for  Search instead for  Do you mean  Menu Categories Solutions IT Transformation Internet of Things Topics Big Data Cloud Security Infrastructure Strategy and Technology Products Cloud Integrated Systems Networking Start with status checks and an empty drive, then load a tape and repeat. Please ask the forum!If you feel this was helpful please click the KUDOS! The new Half Dead Disk Detection feature can be used to detect and quicklyexclude such PVs from LVM usage.

For me it looks like the resp. http://blackplanetsupport.com/failed-to/failed-to-write-memory-at-0x8000.html Then run make_tape_recovery and do not use the mt--offline option when make_tape_recovery returns a bad status. 0 Kudos Reply Serializer Occasional Contributor Options Mark as New Bookmark Subscribe Subscribe to RSS I/O error for tape indicates a hardware problem. By using this site, you accept the Terms of Use and Rules of Participation. End of content United StatesHewlett Packard Enterprise International CorporateCorporateAccessibilityCareersContact UsCorporate ResponsibilityEventsHewlett Packard LabsInvestor RelationsLeadershipNewsroomSitemapPartnersPartnersFind a PartnerPartner

I was able to, just now, tar single files to the tape.wau022:/home/root> tar -cvf /dev/rmt/1mn ./tmpdfa ./tmpdf 6 blockswau022:/home/root> mt -f /dev/rmt/1mn rewindwau022:/home/root> tar -tvf /dev/rmt/1mnrw-r----- 0/3 2858 Oct 19 06:00 Final words from the latest recovery.log: # tail -10 /var/opt/ignite/recovery/latest/recovery.log1488+1 records outI/O error ERROR: /usr/bin/dd if=/var/tmp/uxinstlf.recovery of=/dev/rmt/0mn bs=2k failed to write LIF onto tape.ERROR: Failed to generate LIF on tape . Hope this helps!RegardsTorsten.__________________________________________________There are only 10 types of people in the world -those who understand binary, and those who don't.__________________________________________________No support by private messages. navigate here thumb below! 0 Kudos Reply EU-Admins-UNIX Regular Advisor Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content ‎08-21-2012 08:33 AM

Notify the mass storage subsystem that the disk has been replaced.If the system was not rebooted to replace the failed disk, then run scsimgrbefore using thenew disk as a replacement for The storage subsystem creates a newLUN instance and new device special files for the replacement disk....6. These files are not included in the backup: /var/adm/cron/tty erase /var/tmp/ign_configure/make_sys_image.log /var/stm/logs/os/log339.raw.cur /var/opt/ignite/tmp/AAA019477 /var/opt/ignite/tmp/BAA019477 ======= 08/17/12 20:37:41 BST make_tape_recovery completed with warnings

make_rec_LIF.docx ‏16 KB 0 Kudos Reply Torsten.

By I am still experiencing LIF warnings in the make recovery output.See attached.Also, disk100 no longer exists,but was replaced by disk149 at path c0t6d0 after the reboot. Replace it with a new catridge.Regards,Sunil Your imagination is the preview of your life's coming attractions 0 Kudos Reply The opinions expressed above are the personal opinions of the authors, not Botton of vgdisplay -v vg00 shows: --- Physical volumes --- PV Name /dev/disk/disk100 PV Status unavailable Total PE 4375 Free PE 1927 Autoswitch On Acclaimed Contributor Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content ‎08-21-2012 08:35 AM ‎08-21-2012 08:35 AM Re: Issues with Make_tape_recovery

This should take Ignite out of the problem. These files are not included in the backup: /var/tmp/Ex21430 /var/tmp/aaaa21429 * Archive created and rewind the tape to beginning of tape.NOTE: Could not read the /etc/resolv.conf file. * Cleaning up old Please ask the forum!If you feel this was helpful please click the KUDOS! his comment is here Use the ATT rewind device file 0m and check the status, then use mt--rewind to return to BOT and write the tar backup again using 0mn, the ATT no-rewind option.

Hi,this looks like there is some issue with your PAX version installed.You may probably need to update PAX-ENH version 1.0.here you can find the link for PAX.https://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=PAX-ENH Thanks & Regards,Shan. 1 Command: make_tape_recovery -x inc_entire=vg00 -I -v -a /dev/rmt/1mnI'm getting an error:ERROR: /usr/bin/dd if=/var/tmp/uxinstlf.recovery of=/dev/rmt/1mn bs=2k failed to write LIF onto tape. Ignite appears to not have worked for a very long time on this server. Please ask the forum!If you feel this was helpful please click the KUDOS!

thumb below! 0 Kudos Reply EU-Admins-UNIX Regular Advisor Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content ‎08-28-2012 03:10 AM Trying to schedule the hardware call to coincide with the maintenance window... 0 Kudos Reply Sยภเl Kย๓คг Respected Contributor Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print That's a good start.Have you tried different tapes? If it's incorrect I'll file a defect against it. 0 Kudos Reply Jacob Levin Advisor Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend

There was no "initialization/format" done on the tape, necessary?Here I attach some outputs. By using this site, you accept the Terms of Use and Rules of Participation. End of content United StatesHewlett Packard Enterprise International CorporateCorporateAccessibilityCareersContact UsCorporate ResponsibilityEventsHewlett Packard LabsInvestor RelationsLeadershipNewsroomSitemapPartnersPartnersFind a PartnerPartner You've tried different tape drives. There is a uxinstlf.recovery file.

thumb below! This is DDS tape, can i insert DAT72 & try to take ignite backup? 0 Kudos Reply fizan Super Advisor Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Use tar to write a test backup to the drive and ensure all are fine.Sudeesh The most predictable thing in life is its unpredictability 0 Kudos Reply Devender Khatana Honored Contributor Tried 3 different new disks, all showed NO_HW. 'insf -e' did nothing!Put the original failing disk back in, showed as claimed.Our disk has firmware version HPC0, engineer brought 3 x disk

The only errors I get up to the failure is one for: vxvm:vxprint: ERROR: IPC failure: Configuration daemon is not accessible. 0 Kudos Reply Unix Team Advisor Options Mark as New In addition, the devicespecial files for the new disk are renamed to be consistent with the old LUN instance number. Go to Solution. 0 Kudos Reply All Forum Topics Previous Topic Next Topic 2 REPLIES Patrick Wallek Honored Contributor Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print