topic Re: ignite in Operating System - HP-UX

ignite

Ron Irving — Tue, 05 Jan 2010 13:56:51 GMT

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

Re: ignite

Pete Randall — Tue, 05 Jan 2010 14:23:27 GMT

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

Re: ignite

Ron Irving — Tue, 05 Jan 2010 14:29:49 GMT

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!!

Re: ignite

Ron Irving — Tue, 05 Jan 2010 15:38:47 GMT

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??

Re: ignite

Pete Randall — Tue, 05 Jan 2010 15:44:34 GMT

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

Re: ignite

Ron Irving — Tue, 05 Jan 2010 15:50:33 GMT

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

Re: ignite

Pete Randall — Tue, 05 Jan 2010 16:34:07 GMT

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

Re: ignite

Pete Randall — Tue, 05 Jan 2010 16:38:11 GMT

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

Re: ignite

Ron Irving — Tue, 05 Jan 2010 17:34:38 GMT

Thanks again Pete!!

I ran:

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

cheers!!

Re: ignite

Ron Irving — Tue, 05 Jan 2010 17:41:35 GMT

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?

Re: ignite

Pete Randall — Tue, 05 Jan 2010 17:46:56 GMT

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

Re: ignite

Ron Irving — Tue, 05 Jan 2010 17:53:32 GMT

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

Sigh.

Re: ignite

Dennis Handly — Tue, 05 Jan 2010 18:00:40 GMT

>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'

Re: ignite

Ron Irving — Tue, 05 Jan 2010 18:08:06 GMT

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.

Re: ignite

Pete Randall — Tue, 05 Jan 2010 18:13:00 GMT

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

Re: ignite

Dennis Handly — Tue, 05 Jan 2010 18:14:04 GMT

>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 "\".

Re: ignite

Ron Irving — Tue, 05 Jan 2010 18:18:18 GMT

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

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

Thanks up front!!

Re: ignite

Ron Irving — Tue, 05 Jan 2010 18:40:47 GMT

Whoa!! I think I figured it out!!

I'm holding my breath!!!!

Re: ignite

Ron Irving — Tue, 05 Jan 2010 19:39:00 GMT

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?

Re: ignite

Dennis Handly — Wed, 06 Jan 2010 09:15:57 GMT

>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.