Re: ignite (154 Views)
Reply
Trusted Contributor
Ron Irving
Posts: 562
Registered: ‎03-13-2001
Message 1 of 24 (155 Views)
Accepted Solution

ignite

Hello again ladies and gents!!

I inherited a K570 with issues...(go figure)

First of all, there's been a host of single bit errors, so much so that the PDT has used up all 50 entries!! Scary!! I have scheduled a reboot for Jan 14, (our maintenance window,) and decided to attempt to run an iginte tape today, just to cover my bases.

I ran the make_tape_recovery command, and away it went. It finished with the error:

1761+0 records in
1760+1 records out
I/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

Should I assume a bad dds drive? (c1537a.)

Thanks in advance!!

Ron
Should have been an astronaut.
Please use plain text.
Outstanding Contributor
Pete Randall
Posts: 16,205
Registered: ‎11-03-1996
Message 2 of 24 (155 Views)

Re: ignite

Before blaming the tape drive, you might want to try doing the same dd command to a disk file:

/usr/bin/dd if=/var/tmp/uxinstlf.recovery of=/tmp/uxinstlf.recovery bs=2k

If that works, try a new tape.


Pete

Pete
Please use plain text.
Trusted Contributor
Ron Irving
Posts: 562
Registered: ‎03-13-2001
Message 3 of 24 (155 Views)

Re: ignite

Hey Pete!! Thanks for your quick response!!

On a whim, I ran a cleaning tape through it 5 times, (I heard that has magical properties.) Re-ran the ignite command, and it's running as it should...so far, at least.

I'll wait for the process to finish, and let y'all know.

Thanks again!!
Should have been an astronaut.
Please use plain text.
Trusted Contributor
Ron Irving
Posts: 562
Registered: ‎03-13-2001
Message 4 of 24 (155 Views)

Re: ignite

I knew that was going to be too easy.

make_tape_recovery unsuccessful. The error follows:

* Preparing to create a system archive

* Archiving contents of lims via tar image to local device/dev/rmt/0mn.
pax: home/jhegidus/d: emp\ditrans\TE1.DAT : No such file or directory
WARNING: The pax command returned a non-zero exit status (exit status 1)
WARNING: The pax command returned a non-zero exit status (exit status 1)
* Creation of system archive complete
NOTE: The following files are in the list of files that were on the
system, but they are no longer present. These files are not
included in the back-up:
/var/tmp/ign_configure/make_sys_image.log

ERROR: The make_sys_image command failed. The system recovery archive will
not be created.


======= 01/05/10 09:58:28 EST make_tape_recovery completed unsuccessfully


Any ideas, oh great gurus??

Should have been an astronaut.
Please use plain text.
Outstanding Contributor
Pete Randall
Posts: 16,205
Registered: ‎11-03-1996
Message 5 of 24 (155 Views)

Re: ignite

It seems to be complaining about a file that is no longer there - it was present when Ignite started but had vanished when Ignite actually tried to back it up. You could try again when there is less activity.


Pete

Pete
Please use plain text.
Trusted Contributor
Ron Irving
Posts: 562
Registered: ‎03-13-2001
Message 6 of 24 (155 Views)

Re: ignite

Again with the quick reply!! You're awesome!! (Try not to let that go to your head!)

I'll run it again tonight from home. Yay. Work from home!! My favorite!!

Regards,

ron
Should have been an astronaut.
Please use plain text.
Outstanding Contributor
Pete Randall
Posts: 16,205
Registered: ‎11-03-1996
Message 7 of 24 (155 Views)

Re: ignite

No, I won't let it go to my head - it's more boredom than anything else - one of those slow days where I almost want to go out and break something myself.

Anyway - you could also set up an "at" job so you wouldn't have to work from home - just check the results in the morning.


Pete

Pete
Please use plain text.
Outstanding Contributor
Pete Randall
Posts: 16,205
Registered: ‎11-03-1996
Message 8 of 24 (155 Views)

Re: ignite

I just noticed the name of the file that went missing:

home/jhegidus/d: emp\ditrans\TE1.DAT

The "d:" doesn't look very unix like. What all are you backing up? What does your make_tape_recovery (or make_recovery?) command look like?


Pete

Pete
Please use plain text.
Trusted Contributor
Ron Irving
Posts: 562
Registered: ‎03-13-2001
Message 9 of 24 (155 Views)

Re: ignite

Thanks again Pete!!

I ran:

make_tape_recovery -v -x inc_entire=vg00 -a /dev/rmt/0mn

cheers!!
Should have been an astronaut.
Please use plain text.
Trusted Contributor
Ron Irving
Posts: 562
Registered: ‎03-13-2001
Message 10 of 24 (155 Views)

Re: ignite

But wait!!

I ran a listing of that /home directory. The actual name is d:\temp\ditrans\TE1.DAT

the log is looking for:

home/jhegidus/d: emp\ditrans\TE1.DAT

Missing the \t

Is there a way to resolve this?
Should have been an astronaut.
Please use plain text.
Outstanding Contributor
Pete Randall
Posts: 16,205
Registered: ‎11-03-1996
Message 11 of 24 (154 Views)

Re: ignite

I have to wonder if that isn't an unprintable character. The file or the whole directory was obviously transferred from a PC, thus d: designation and the back slashes in the name.

I think I would try to rename it:

mv home/jhegidus/d:*emp\ditrans\TE1.DAT home/jhegidus/d:Temp\ditrans\TE1.DAT


Pete

Pete
Please use plain text.
Trusted Contributor
Ron Irving
Posts: 562
Registered: ‎03-13-2001
Message 12 of 24 (154 Views)

Re: ignite

Nope...it doesn't like the \ character.

Sigh.
Should have been an astronaut.
Please use plain text.
Acclaimed Contributor
Dennis Handly
Posts: 24,750
Registered: ‎03-06-2006
Message 13 of 24 (154 Views)

Re: ignite

>I ran a listing of that /home directory.

Can you redo this and add "-b" to your ls?

>Pete: I think I would try to rename it:

Is a backslash a valid filename char for ignite?
And if you wanted to rename it, you would need to quote the backslashes, wildcard with "." or include in single quotes.
mv something 'd:Temp\ditrans\TE1.DAT'
Please use plain text.
Trusted Contributor
Ron Irving
Posts: 562
Registered: ‎03-13-2001
Message 14 of 24 (154 Views)

Re: ignite

Ok...I ran the ls -b optoin:

006386_001.lis 022665_001.lis c:\ditrans\TE1.DAT
006670_002.lis 022665_003.lis calscss.txt
006670_003.lis 022665_005.lis calscss.txt,000
006670_007.lis 022687_001.lis calscss.txt,001
006670_008.lis 022749_001.lis d:\DC1.DAT
007205_001.lis 023932_001.lis d:\SS3.DAT
008385_001.lis 024560_001.lis d:\temp\ditrans\TE1.DAT

Not sure how it looks, but it's the last line that's offending.
Should have been an astronaut.
Please use plain text.
Outstanding Contributor
Pete Randall
Posts: 16,205
Registered: ‎11-03-1996
Message 15 of 24 (154 Views)

Re: ignite

Duh, missed the (obvious) meaning of the back slash character.

You might consider going to the owner of this home directory and asking what this junk is. It's entirely possible that it's not needed.


Pete

Pete
Please use plain text.
Acclaimed Contributor
Dennis Handly
Posts: 24,750
Registered: ‎03-06-2006
Message 16 of 24 (154 Views)

Re: ignite

>but it's the last line that's offending.

I would assume that all files with "\" would have the same problem.

Any reason you are including /home in your ignite backup?
You could always exclude this unmutual user's home directory.
Or tar them up and remove the individual files with the evil "\".
Please use plain text.
Trusted Contributor
Ron Irving
Posts: 562
Registered: ‎03-13-2001
Message 17 of 24 (154 Views)

Re: ignite

well...I'll just exclude that in my command.

Speaking of which...how do I exclude this directory in my command?

Thanks up front!!
Should have been an astronaut.
Please use plain text.
Trusted Contributor
Ron Irving
Posts: 562
Registered: ‎03-13-2001
Message 18 of 24 (154 Views)

Re: ignite

Whoa!! I think I figured it out!!

I'm holding my breath!!!!
Should have been an astronaut.
Please use plain text.
Trusted Contributor
Ron Irving
Posts: 562
Registered: ‎03-13-2001
Message 19 of 24 (154 Views)

Re: ignite

Hey...!! Look at me!! I'm back!

I ran:

make_tape_recovery -v -x inc_entire=vg00 -x exclude=/home/jhegidus -a /dev/rmt/0mn

Same error:

43470+1 records in
43470+1 records out
* Complete writing boot LIF onto tape.
* /opt/ignite/data/scripts/make_sys_image -c n -d /dev/rmt/0mn -t n -s
local -n 2010-01-05,13:31 -m t -w
/var/opt/ignite/recovery/2010-01-05,13:31/recovery.log -u -R -g
/var/opt/ignite/recovery/2010-01-05,13:31/flist -a 3101960

* Preparing to create a system archive

* Archiving contents of lims via tar image to local device/dev/rmt/0mn.
pax: home/jhegidus/d: emp\ditrans\TE1.DAT : No such file or directory
WARNING: The pax command returned a non-zero exit status (exit status 1)
WARNING: The pax command returned a non-zero exit status (exit status 1)
* Creation of system archive complete
NOTE: The following files are in the list of files that were on the
system, but they are no longer present. These files are not
included in the back-up:
/var/tmp/ign_configure/make_sys_image.log

ERROR: The make_sys_image command failed. The system recovery archive will
not be created.


======= 01/05/10 14:10:57 EST make_tape_recovery completed unsuccessfully


I'm thinking it's looking for the make_sys_image.log, which doesn't exist in the /var/tmp/ign_configure directory.

Now what?
Should have been an astronaut.
Please use plain text.
Acclaimed Contributor
Dennis Handly
Posts: 24,750
Registered: ‎03-06-2006
Message 20 of 24 (154 Views)

Re: ignite

>Same error:

Right. Is /home or /home/jhegidus a symlink?
Have you tried removing/renaming/archiving those evil files?

>I'm thinking it's looking for the make_sys_image.log

The NOTE said the file was there at the start but later removed. I.e. ignore it.
Please use plain text.
Trusted Contributor
Ron Irving
Posts: 562
Registered: ‎03-13-2001
Message 21 of 24 (153 Views)

Re: ignite

Ok...tried again, and failed again. Here's the command I ran, exactly:

make_tape_recovery -v -x inc_entire=vg00 -x exclude=/home/jhegidus -a /dev/rmt/0mn

I've attached then whole recovery.log file from that failure. It looks as though even after excluding that directory, it's still looking for those files.

Thanks guys!!!

Ron
Should have been an astronaut.
Please use plain text.
Outstanding Contributor
Pete Randall
Posts: 16,205
Registered: ‎11-03-1996
Message 22 of 24 (153 Views)

Re: ignite

Ron,

Your log shows that /home is being included in its entirety:

2 v /dev/vg00 0x00 /dev/dsk/c3t6d0 /dev/dsk
/c2t4d0
/dev/vg00/lvol1 /stand 2
/dev/vg00/lvol2
/dev/vg00/lvol3 / 2
/dev/vg00/lvol4 /opt 2
/dev/vg00/lvol5 /tmp 2
/dev/vg00/lvol6 /usr 2
/dev/vg00/lvol7 /var 2
/dev/vg00/lvol8 /home 2

** 0 - The Volume Group or Filesystem is Not included in the
System Recovery Archive
** 1 - The Volume Group or Filesystem is Partially included in the
System Recovery Archive
** 2 - The Volume Group or Filesystem is Fully included in the
System Recovery Archive




Try it again, specifying -x exclude=/home and see what happens.


Pete

Pete
Please use plain text.
Trusted Contributor
Ron Irving
Posts: 562
Registered: ‎03-13-2001
Message 23 of 24 (153 Views)

Re: ignite

Ok!! I ran it and excluded all of /home. It finished, with warnings, but finished nonetheless!!

NOTE: Could not read the /etc/resolv.conf file.
* Cleaning up old configuration file directories


======= 01/06/10 11:18:05 EST make_tape_recovery completed with warnings

So...now I have an ignite with no /home in it. Should I be afraid?
Should have been an astronaut.
Please use plain text.
Acclaimed Contributor
James R. Ferguson
Posts: 21,184
Registered: ‎07-06-2000
Message 24 of 24 (153 Views)

Re: ignite

Hi Ron:

> So...now I have an ignite with no /home in it. Should I be afraid?

No, you can backup '/home' with something other than Ignite and then if you need to use your Ignite tape, do so, and follow that recovery with a recovery of '/home' from its backup.

What you really want (and what you really have) is a viable operating system image.

Regards!

...JRF...
Please use plain text.
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation